asyncrosaurus

There is no dropping out, and there's no replacement. All political donations have been to the Biden campaign, it is illegal to transfer those funds to a new candidate. The only person who could run for president in his place is Kamala, since she is the other person on the ticket.

It's extremely clear no one talking has any clue how any of this shit works.

Well yeah, 100% of programming errors are programmers fault.

Most can't, but that's why clandestine cyber-intelligence firms like NSO group exist.

Awesome you say? Sounds like a good candidate for being discontinued by Google.

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.

async/await was introduced in version 4.5, released 2012. More than a few releases at this point!

Powershell

/s

The opinion is not "cherry-picked", nor are the highlighted examples from the book unique or lacking context. It is a long, thoughtful and articulate criticism of multiple passages from "Clean Code", and display a fundamental problem with the advice it gives. It's not to pretend there's no good advice in the book, but that the bad advice is really bad and very prominent. Also, it's impossible to finish since the back half is Java-centric, a relic of the era it was written.

Certainly not everything in his books is bad, and not everything that is bad today was bad when it was originally written. The biggest problem with the quality of his books, is that there's a mix of good, bad, and out-dated advice in there, and for the beginners/Juniors reading his books, it's genuinely hard to tell the difference. I think people would be better off looking for sources that avoid some of the mistakes that he made, amd speak to a more modern audience who are working with recent technologies and in work environments as they exist today.