3 ms·
It's more than the fear of over-engineering. For example, with startups the time to market, pivots, and not owning your decisions long term (which often happen
by mfer 2y ago
It's more than the fear of over-engineering.
For example, with startups the time to market, pivots, and not owning your decisions long term (which often happens) leads people to move fast and not consider consequences.
It's about goals and following the money. If a bridge fails there's significant legal liability, guilt over lost lives, and more. If software doesn't scale is can be rewritten or a company is hacked and customer info gets out there is a marketing black eye. It's different.
I say this as a classically trained engineer who thinks more engineering needs to be layered into software development. We need to justify it to the business.
- zelphirkalt 2y agoWith long term probably being longer than 2y, it will be pretty difficult to make most of software engineers do that (owning their decisions), because many are at a new job every 2y or even shorter time. Most do not see how the results of their work pan out in the end. Also it is difficult to own it, if you got no comparison. Say you build some system in way A. You are likely never going to get to build it in way B. This will forever stand as an argument, that you cannot know what would have happened had you gone the way B route. So even if some decisions cause a business to need to hire additional people, just to keep that bad decision alive, the business usually does not stop and take a step back, to think "Wait a moment, if we hadn't done that, could we have avoided all this time spent on XYZ?" and then correct itself.