3 ms·
> If you delivered a result that the stakeholders are happy with, that's a good outcome as an engineer. If you want to overengineer something, consider either d
by TeMPOraL 6y ago
> If you delivered a result that the stakeholders are happy with, that's a good outcome as an engineer. If you want to overengineer something, consider either doing it on your own time or switching to a job where, for example, more scalability, is actually a requirement.
On the flip side, that sounds like a fast track to making shitty products that cause financial losses to the users (or, depending on industry, loss of life and limb). There are always implicit requirements to balance that stakeholders don't think of (or sometimes can't even conceptualize). Like, "satisfy the obvious safety constraints despite them not being mentioned in the spec", or "don't ship kludges that will slow everyone else down later on". Sometimes, part of being an engineer is saving stakeholders from themselves.
Might depend on the company culture, but personally I do not want to work in the place where the engineering culture is "ours not to reason why, ours but to do and die".