A true FP programmer would make it apply instead of run…

Wake up Nee-Oh!

Good luck getting there on a wheelchair… Or under influence of C2H5OH.

That’s what she said!

Talk to the manager Karen! Do it!

Dad, is that you?..

One person downvoted? Are they stupid or something? Asking for a friend.

Obviously, that’s what the “arms race” refers to. Birds used to have very strong arms which they used while racing in their super-fast arm bikes.

On a serious note, I really enjoy yerba mate-based (or should I write flavoured) elixirs. Or even yerba mate itself. Just saying! 🤷

That’s like… Your opinion, sis…

Do you eat them too? Asking for a friend!

Could someone explain how they’re going to drive 407 km/h in traffic jam? Or in a city, in general?

I definitely agree that too many comments is often a bad sign, esp. when large part of them is obviously generated.

As mentioned in my other comment, names will rarely explain the reasons why a given solution was chosen. These reasons are important from maintenance perspective and should be recorded next to the relevant code.

You’re definitely not the only one.

In my opinion the important information we should record in comments is WHY, because the code can only explain HOW, maybe WHEN, but never WHY. If we don’t know WHY, any refactoring done in the future could break the logic by ignoring assumptions made by the authors.

What’s the font used in the heading? Is it some flavour of Helvetica?

What is he holding? An ancient dildo or a shit stick?

I suspect it’s related to USA current affairs and have no clue what it’s referring to. Any hints for us outsiders?

I’m beginning to feel we’re no longer talking about Clean Code being bad, but about people following ideas they don’t understand, which is not related or caused to any particular book.

I hope your book won’t have a table of context and those stupid indexes. If they read it, they should know where you mention topics, right? Tables of contents considered harmful! /s