this post was submitted on 10 Aug 2024
591 points (97.3% liked)

Programmer Humor

19656 readers
830 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 30 points 3 months ago (2 children)

Personally I have been around longer than him but I used to like his stuff at first.

As I've coded more and more on stuff that is built not only on legacy code but specifically legacy code by coders influenced substantially by clean code... damn has this single author given me a headache like nothing else ever has.

The level of inane unmaintainability and complexity achieved by younger coders being encouraged or forced to code "clean" is remarkable.

[–] pkill 8 points 3 months ago

personally I'd sum it up this way: it is usually enough to abstract two parts of your code: the repetitive stuff and the stuff that can be separated from external dependencies like db or network. That should be enough to ensure readability and that you can test it properly and not have to deal with rewriting half your codebase when you decide to change an external dependency.

[–] [email protected] 5 points 3 months ago (1 children)

Can you give examples? I genuinely can't think of how the principles applied with proper restraint not to overdo it make code hard to maintain. But I've only watched his talk a few years ago - not the book.

[–] [email protected] 14 points 3 months ago

There are a fair few examples in the book itself. https://qntm.org/clean