I started off, writing my own operating systems in assembly

Basically, "divide and conquer." Big things are composed of small things. I don't think this is the controversial part or the difficult conclusion, the challenge is how exactly to do that.

> fact, Jared Diamond posited that we're actually a bit stupider Please don't enable this man when there are literally millions of trained historians you can talk to.

It is my understanding this is how Apple does their development. Everything is home grown and not a hodge podge of dependencies from outside the company. I do like Mac products but just can't get passed their walled garden. However, to have the quality they do I guess it kind of makes sense to have the garden. I personally like the idea of few-to-none outside dependencies, solid testing and solid, up-to-date documentation. I need to work on being more disciplined and motivated to do it.

> Large codebases are inevitable. I vehemently disagree. New codebases might be built on top of large stacks of framework code and infrastructure code, but source repositories ought to actually be tighter and more business-focused than they used to be. But they're often bloated monstrosities, filled with resume-padding architecture astronaut bullshit, or contorted to fit the latest hip framework's requirements. Apologies ahead for this long-winded rant, but this exact issue has been boiling my blood for weeks now because I've been wading through the neck-deep mess that a customer has made, such as writing an astonishing three megabytes of source (typed by hand, not generated!) for a single web form . One! Especially in the era of modern web frameworks, we can avoid most of the "ceremony" of older systems like C or C++ where just making a call to a database was pages of fiddly boilerplate…