By the time you get to need to learn Kubernetes, people are usually too far deep in their engineering careers and already have this 'not even more shit' fatigue.

"This happens because ES module import statements result in an object with immutable properties while CommonJS require calls result in an object with mutable properties (for the reasons already described above)." 🤮

Getting an existing NodeJS project up and running on Windows IS A FUCKING NIGHTMARE

OOP is all about code reusability until you really want exactly the code Foo with non-pure functions in all your classes. You end up almost rewriting all subclasses' properties into the superclass to silence typecheckers. Is there no "I know what i'm doing, please just transpile/compile this piece of logic into these 20 places I need?" You end up doing it the functional way, dumping refs and params into some shared util function and have it do the job. I know, might as well have that one inherited also, but what's the point of adding more mess just for that ?

'Complicated is easy, but simple is hard☝️ '

- Robert Virding, the inventor of Erlang. You can never not apply this quote to anything in software engineering.

Typescript is a PIECE OF SHIT that adds 3 problems for every 1 it solves! Messing with so much shit from its linter and builder just so some OOP fools can code JS like *TAB* *TAB* *TAB* again!