After you had to learn to use spice, matlab, VHDL, all the weired stuff of physics (Quantum mechanics, physical stats, relativity...), english and german ... then computer new technologies are laughably neither complex nor disrupting.

Most of the new techs are fraud like angular; like in science a new tech should be something that simplifies the world with a simplified view : a map.

A map should always be simpler than the stuff you want to describe. Angular for instance is kind of the string theory of JS development; formalism is complex, it makes a lockin for incompetent devs but it brings nothing new.

But still, I can do angular fairly well, because I like to rant, and it is funnier to rub your despise into people's face when you outsmart them.

Computer language when you had to learn thousands of words to be understood and complex grammars for foreign languages are freaking easy; python is around 50 core words. Perl 300 ...

Most of what computer science are proud of is scam. No critical thinking and no building up of intuition makes people looks like headless chicken yelling «new tech, new tech» and bumping into each other.

Me on the other hand, I can guess where the flow of circuitry will bring the data into memory, if their will be localisation if the L1, L2 cache will be used. I can feel the unstability of the sequencer with page fault or OOP missing.

Why?

Because computer is still a dumb automata that is part of my formation; I learnt how to build microchips.

But electronics also learns you how to face complexity.

You don't see the world bottom up or top down. You are like a go player. You embrace the world's complexity by building up 2 pictures of complexity one for the bottom the other for the top and you try to make them converge in the middle.

high level abstractions like CSS and files (yes a file that has the open/read/write/seek/tell/close/ioctl is an abstraction, it does not exists on the silicium level) requires to be careful. But still they are never new. They are built up on other layers of abstraction (geometry for CSS)

Some abstractions are insanely more complex than the world they describe (CSS). Happily for me I learnt Tk/Tcl that gave the packing geometry understanding (the so called boxing model).

Angular is shit, but I learnt xmlhttppartialrequest a long time ago, so I know how to circumvent this horror.

I can quote a lot of example where focusing on the basics on the core of knowledge (what does the GIL do, how to bind on a library with python, who does the PCI bus works) finally makes you outsmart the competition of the stupid devs throwing themselves in new technology in the hope they can cut corners.

There is no lazyness possible. Computer programming requires a lot of knowledge, rather focus on learning the basics :
- what is an OS (especially POSIX);
- network programming;
- algorithm;
- CPU architecture;
- a tinge of ASM;
- bus specification;
- memory allocation;
- physics (only physicists understand why distributed MUST not use timestamps or any global clock and why «acausal» events might occures);
- math: linear algebrae, proba and especially geometry (yep even for CSS);
- theory of measure;
- signal processing and the theory of dectection of errors

When you have the basics, no frameworks or new technology are either intimidating or out of grasp.

Most of the so called new techs are fraud.

If a map is not simpler and as accurate as the world it tries to describe, then throw it away. That's how I deal with new techs; by discarding most of them.