I talk about this frustration a little here:<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=-qHwL8C9UoA" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=-qHwL8C9UoA</a><p>and also (more pithily) here:<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=zVUPmmUU3yY" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=zVUPmmUU3yY</a><p>There&#x27;s nothing more frustrating than people telling you &#x27;I wouldn&#x27;t start from here&#x27; when you are the one that has written the productive software.<p>There are tremendous advantages to monolithic software architectures, but for some reason they are seen as impure. It reminds me of the Java&#x2F;object orthodoxy of ca. 2000 when everything had to be a class.<p>Meanwhile procedural code came back with a vengeance, because it&#x27;s advantages are those that can be used by people trying to write useful software on a budget.