• Carighan Maconar@lemmy.world
    link
    fedilink
    arrow-up
    31
    arrow-down
    1
    ·
    1 month ago

    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.

    • anti-idpol action@programming.dev
      link
      fedilink
      arrow-up
      8
      ·
      1 month 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
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 month ago

      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.