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.
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.
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.
![Chris Langan - The Interview THEY Didn't Want You To See - CTMU [Full Version; Timestamps]](http://i.ytimg.com/vi/9miVG2xT5jY/mqdefault.jpg)
![[MV] A leap of faith...ความเชื่อใจครั้งสุดท้าย (From "Petrichor the series")](http://i.ytimg.com/vi/U1piZH2CNXA/mqdefault.jpg)
Clean code is that which causes the fewest number of WTFs/minute when read 🤣
Not "the fewest". Zero WTF/minute.
@@jarlfenrir I dont think you code
Classic meme
@@riten I don't think you've watched the video
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.
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.
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.
uncle bob sucks
Fisrt