Nah, our generation had to tinker with shit to get it working. Kids these days have it easy, which is good from a user perspective, but fails to train them how any of it actually works at a deeper level.
No one has to install a device driver anymore.
It's a beginners book filled with a mix of bad and good advice, which takes considerable experience to separate the two. Those who can point out all the bad advice already don't need the book, and newer developers will pick up absolutely atrocious coding advice. There's simply better books that target beginners better, like The Pragmatic Programmer.
So when you are on-boarding junior devs that have bought into the clean code/SOLID dogma, you're spending several months beating all their terrible coding habits out of them.
He's using the ancient rhetorical device of "I know you are, but what am I?".
Programming is mostly research. Researching curses to cast on the guy who wrote the Incomprehensible mess you're currently debugging.
I've used various Linux distress on a half dozen laptops over rhe last 10 years and I've never had Wi-Fi driver issues
apt remove sudo
sudo is not installed on several distributions by default, so hardly surprising it's not there or that you can remove it.
Well yeah, 100% of programming errors are programmers fault.
Meanwhile PHP quietly runs 80% of the internet by being used for WordPress.
"There are only two kinds of languages: the ones people complain about and the ones nobody uses."
Always remember, the silicon valley ethos of "break things" wasn't about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.
the tests are now larger than the thing itself
Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.
The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.
I've programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.
It's one of those things that almost should never be used, but the times it's been needed, it removed a lot of silliness.