Software Complexity Is Killing Us
To me, this was the money quote:<p>&gt; <i>You might say, “But event sourcing is so elegant! Having a SPA on top of microservices is so clean!” Sure, it can be, but not when you’re the person writing all ten microservices. It is that kind of additional complexity that is often so unnecessary.</i><p>It&#x27;s very easy to be wasteful when:<p>1. It&#x27;s not your time that&#x27;s being wasted<p>2. It&#x27;s not your money that&#x27;s being wasted<p>One of the best learning experiences I had, was building and launching an entire application API, purely by myself, in my free-time while juggling a full-time job. It really helps you accurately evaluate the cost-benefit tradeoffs for various flavor-of-the-month technologies&#x2F;methodologies, when you&#x27;re the one who has to shoulder every one of those costs.<p>I&#x27;ve had far too many team-leads whose assessments of these cost-benefit tradeoffs are intensely skewed by the fact that it&#x27;s other people who have to work on those things, and it&#x27;s other people&#x27;s money that is being burnt while working on these things. We think these are technical debates, but really, it&#x27;s a organizational problem. Under the right organizational structure and incentives, people are exceedingly bright at optimizing for their personal success. The principal-agent problem is a crippling handicap that hobbles every medium&#x2F;large business today. The day we find better ways to solve this problem, is going to be a transformational day in the history of our civilization.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Principal–agent_problem" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Principal–agent_problem</a>