The rise and fall of the dungeon master on software projects
This reads like a 26 year old wrote it after supporting a toy system for two years, and has a few things to school his elders on.<p>I&#x27;m sure projects fail for many, many reasons, and inertia plus ego from an original developer that&#x27;s now powerful is certainly one of them.<p>On the other hand, the number of half-baked ORM replacements for SQL I&#x27;ve seen represents a staggering amount of wasted labor, labor that could have launched a number of great tech teams if they&#x27;d had the wisdom to learn from someone who was coding while they were in diapers.<p>I think I find the whole thing so offensive because node plus microservices are put out in the essay as the thing that a hot new dev knows better than her elders.<p>So -- computing models are cyclical; they wax and wane for social and practical reasons, and admittedly, beyond all predictions javascript has been massaged into an amazingly fast thing given where it started.<p>But, really? microservices as an approach that&#x27;s just too hard for some old fogey? The same fogey that probably could concatenate piped unix commands to get real shit done in the &#x27;80s, and had a solid understanding of awk syntax?<p>Annoying.