jerDev
Unless there is a business requirement for something to be 10x faster, and that is rooted in $’s, there is no reason to be more than 1x.
Performance criteria should only be measured by whether or not you lose money/customers from it.
It’s not an EM’s job to have performance criteria themselves. That should be dictated by business needs
However, I’m on the opposite side of the fence.
In summary, there are two fundamental ideas in software engineering that people constantly grapple with especially new grads:
1) If it works, it’s not broken.
Or
2) It’s broken until it’s not.
( also can be seen as “right” vs. “right now” )
Let me explain further; - first point refers to the idea that if the constraints provided are achieved, there are no tasks to be done.
- second point refers to the idea that there is a correct way to do something.
I’m not going to take long, but i strongly stand in the first camp. There is no value in building kingdoms in details that aren’t required. Could we have it run in 010ms vs 250ms? Could we make this look better? Could we do this in a different way? Etc. none of this matters if it works.
Now; you might ask the following questions: - what about scalability? What if I’ve done this before and I know pitfalls of xyz?
And my answer is, politely, iterative improvements after a working model if those improvements become necessary. Those improvements are not defacto necessary. And when I say necessary, I mean customers are returning the product, not an engineer can’t sleep at night because of his/her neurosis.
In summary, the world you live in was at-best designed with an acceptable tolerance for error. I call that, “good enough”. There is no other measure than “good enough” when it comes to acceptance criteria of anything.
Want more money? Study for an interview and then return to your minimal effort process. Believing that you need to give more is the company winning. Treat yourself like a shrewd startup business.
Software engineering interviews do not value authenticity, typically. They want you to say what they want to hear. I purposely go in the opposite direction. I am always myself, say how I feel, and challenge the interviewer.
My girlfriend ( soon to be wife ) has no issues getting any job she wants in software engineering. She will recite exactly the words they want to hear, and they love her. I will say exactly what I want to say in an interview and they will love or hate me. I have no intention of changing.
My best advice? Leave for a smaller company that lets you do whatever you want to do and perform at an exceptional level. You get the same satisfaction, same pay, and you may only be 1 step down from VP. You can grab VP's, C's for a comment, you can do whatever you want ( as long as you perform ).
That's the way. For me at least.