162
"Code was never the hard part" is an insult to all programmers
(blog.senko.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Aug 2026
162 points (88.9% liked)
Programming
28283 readers
124 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
One thing to know about Clean Code is that the author is a hard right MAGA dickhead now, so if that is important to you then seek a more modern source of advice. A lot of the things he advocates for about code obviously aren't dripping in right wing rhetoric, but if you look at his socials you might feel quite turned off.
Worth saying the comment I'm replying to is not wrong IMHO
the advice still checks out though imho. dont treat it as dogma, but as useful guidelines.
maybe dont buy the book though
The finer details of the coding advice in Clean Code is also insane. There's a good summary of it but I forgor where
Possibly you're thinking about https://qntm.org/clean
Yes thank you!
See
https://github.com/johnousterhout/aposd-vs-clean-code
By the way, "Uncle Bob"s prime number generator example discussed there (which Bob Martin, as he admits himself, does not understands any more in spite of that he himself published it in "Clean Code") was originally designed and published by nobody less than Edsger Dijkstra and was used as an Example of Literate Programming by Don Knuth.
They are giants on whose shoulders we are standing. It is totally worth it reading first Dijkstra's Chapter, then Don Knuth's text, and then John Ousterhout's discussion of Martin's rewrite (linked above).
Or perhaps starting with Martins code and see if you understand it....
https://gist.github.com/pooya-raz/59aa46460f72f994f204a861c7342b4b (Bob Martins Code, which he can't explain when interviewed by Ousterhout)
https://www.cs.tufts.edu/~nr/cs257/archive/literate-programming/01-knuth-lp.pdf (Knuths beautiful explanation of the algorithm invented by Dijkstra, using and demonstrating Knuth's fantastic "Literate Programming" method)
https://pure.tue.nl/ws/files/2408738/252825.pdf (Dijkstra's original code and explanation, a gem of computer science history, where among other things he introduces the concept of invariants)
https://github.com/johnousterhout/aposd-vs-clean-code (Ousterhouts interview with Martin, after publishing A Philosophy of Software Design)
Fascinating
I have been happy to recommend Sandi Metz books instead.
99 Bottles of OOP and POODR are excellent books and include many of the same ideas.
Good Books on the essence of OOP!
I now think that useful OOP is mostly about invariants.