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@programming.dev 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.

[–] Prunebutt@slrpnk.net 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.

[–] themusicman@lemmy.world 13 points 3 months ago

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