What is clean code? - Uncle Bob

[@perfectionbox]

Clean code is that which causes the fewest number of WTFs/minute when read 🤣

[@jarlfenrir]

Not "the fewest". Zero WTF/minute.

[@riten]

@@jarlfenrir I dont think you code

[@MrEliteXXL]

Classic meme

[@jarlfenrir]

@@riten I don't think you've watched the video

[@mannig.faltigkeit2341]

Isn't this included in his book 'Clean Code' in form of a comic?

[@SeriousAlexej]

Clean code is in viewer's eyes but I'd say it should not invoke the "fight or flight" feeling. Ie: 1. It's not repulsive. 2. You feel minimal to none desire to add or change something about it.

[@kudorgyozo]

Clean code is something I have yet to witness in my 17 years as a software developer. For me it is almost a myth or legend at this point.

[@johnsmith-ro2tw]

it's funny that SW companies have raised the bar so high at job interviews, with 3 or more rounds of interviews, and live coding exercises and sh**, and yet, we have veterans in the SW industry like yourself who have failed to see clean code. It's almost as if the SW hiring process was broken. The owner of the "the internet of bugs" YT channel has even more XP than you and he says he has yet to see evidence that someone who passed those silly types of interviews end up being better programmers.

[@SufianBabri]

@@johnsmith-ro2tw the interview process is indeed rotten, and yet people are saying that if Google is following it then it should be the best one for anyone out there. Funny world we live in.

[@bobchannell3553]

I've followed a few highly praised programmers who wrote code almost nobody could understand. I always took twice as long to write the same code, but I included comments to document things that were unclear and I used descriptive function and variable names.

[@pdgiddie]

Unfortunately many of the "super productive" programmers are actually terrible team players, and basically farm praise from bosses at the expense of their team mates' sanity.

[@yapdog]

When I worked in a startup, the other programmers remarked at how "neat" and "easy to understand" my code was. I mean, I'm a cynical old dude, too, but it *is* possible to write code in the care of others.... and to have them notice.

[@GordonRoland]

Hemingway's "Old Man and the Sea" should be everyone"s model for clean code.

[@Drudge.Miller]

Well, I got the idea but good luck fulfilling everyones expectations.

[@magnusmalmborn8665]

Clean code is code that doesn't raise you mythos score...

[@adambickford8720]

If I wrote it? Clean. If I inherited it, not so much. The code itself is a MacGuffin.

[@roslin8060]

There's a third option, although technically a combination of the first two. You wrote the code, then came back to it half a year later.

[@mowinckel10]

Code is for humans. If it was for the computer, then all code would be machine code. Code is for humans. Please write code like you understand that.

[@Cadet1249]

uncle bob sucks

[@CounterFragger]

Why ? Because you use to write unreadable code ?

[@m13v2]

as in „the vacuum cleaner of software engineering“ keep on sucking bob! keep on sucking!

[@SufianBabri]

@@CounterFragger see the glass as half-filled. He just saves few CPU cycles by writing obfuscated code, and you're making fun of his code obfuscation and deobfuscation skills? Unfair!?

[@personalaccount1515]

Fisrt