[luord]

There were several good points both for and against the article in this comment section. I was pleasantly surprised, usually the threads caused by posts like this turn into "static typing vs dynamic typing" or "functional vs object oriented" flamewars.

As for my own opinion: yes, optimization is key, but we gotta remember not to make it premature. Take advantage of the fast hardware to actually create something; once we know that the something is viable, let's refactor and optimize.

[pdimitar]

Literally every experienced programmer would like to do this. But when you get to that last stage the shot-callers are like "nah, it's fine" and you never get to the optimisation.

I've seen many products die simply because customers get frustrated with laggy or buggy experience and leave.

By the time the businessmen wake up, it's usually too late.

[codeisawesome]

Which means that Business Analysts need to save the world by proving to the shot-callers things similar to what Amazon found (a few ms of lag in the site load caused $$$ of revenue loss). The ever improving Observability stack combined with strong analytics on the client-side can make this possible. Perhaps regulation around Climate Effects (or carbon taxes on inefficient software) might also bring about an industry-wide change of attitudes (and incentives).

[pdimitar]

Trouble is, most businessesmen I worked with would give you a blank stare if you tell them they need a business analyst.