Assembling Boeings out of text files

The Google Chrome browser has way more “details” and therefore complexity than a Bieing 787 (excluding nested complexity of the on-board computers). This puts into a perspective how complex modern software became.

Notice that just like an aircraft, the Chrome browser is a product built by a corporation which organizes labor of thousands or people, while no one understands the whole in its entirety, not even approximately.

This, if you think about it for a while, has a lot of implications, including that in requires a whole industry to produce software and that one has to be part of this industry, a sub-contractor at least, to make a living.

Eventually, like everything else, it boils down to taking your small cut when other people are willing to spend because of what they want for some reasons. The demand (the want) is what drives everything in a society.

A burnout everyone is talking about nowadays is just burden of the amount of complexity and seemingly irrelevant details one has to be aware of in order to understand and understand in order to make a decision.

What started 70s and 80s as systems which could, with lots of effort, be understood in its entirety became a fucking mess which requires huge organizations to manage and maintain it.

This, after some thinking, implies that only a niche programming in a well-designed, very high-level languages (Ideally - almost perfect DSLs like MATLAB) is the only viable option for an old-school “garage mechanics”.

I absolutely do not want to have anything to do with modern “coding” in Java or C++, leave alone doing webshit, with all its “stacks” and frameworks. This means out of industry and out of money flows.

My things are Erlang and Haskell, Ocaml and Scala 3, even F#.

The main problem is that I have no idea what to program. Yes, it seems, that one should program “trading systems”, but once you do some actual research you will realize that there is nothing much to program, because all the theoretical bullshit is just theoretical bullshit - predictions are impossible in principle.

So, it should be a simplest reactive system (instead of a predictive one) that works (and only simplest systems works reliably), and a such system is “automation”, which is the only viable use for small software.

I know what, why and how, but the very process of accumulating this knowledge has burned me out, and I have literally no desire to actually do it anymore.

Even if Scala 3 is beautiful and Erlang is a miracle.