Why not program right?
I used to love these kinds of articles three decades ago. Then you get a programming job with budgets and deadlines and even stupid decisions based on politics and you hate all that at first until through experience you realize that even poorly engineered cars can get product from point a to point b and do so all over the world. Free markets eventually only have time for perfect solutions. And a perfect solution according to markets is the solution that does the job for the lowest cost over time. For a website that will support a two week marketing campaign, you don&#x27;t need anything talked about in this article. In fact the only responsible decision is to ignore this type of approach and just build the damn thing with someone that has a track record. And then throw it out and move on. Based on empirical evidence, there isn&#x27;t really a problem at all with the way people program. Markets have already mostly figured out the rare cases when such robustness is really needed. And it&#x27;s rare. The only &quot;right&quot; way to program is to take as many stakeholder requirements into consideration as possible. And those requirements are rarely around program correctness. So this article is good (although I think you&#x27;re really looking at functional programming by this time in history) but first make sure a top priority is program correctness before getting into the mode suggested by the article. One final stakeholder requirement that&#x27;s always a priority: you have to be able to find qualified developers, and what developers learn is based on popularity and fashion. It&#x27;s a real world constraint even if it&#x27;s distasteful to the idealist and well intentioned types who write these articles.