JackbyDev@programming.dev to Programming@programming.devEnglish · 3 months agoIt's probably time to stop recommending Clean Code @ Things Of Interestqntm.orgexternal-linkmessage-square44fedilinkarrow-up1121arrow-down17file-text
arrow-up1114arrow-down1external-linkIt's probably time to stop recommending Clean Code @ Things Of Interestqntm.orgJackbyDev@programming.dev to Programming@programming.devEnglish · 3 months agomessage-square44fedilinkfile-text
Seeing that Uncle Bob is making a new version of Clean Code I decided to try and find this article about the original.
minus-squareKache@lemm.eelinkfedilinkarrow-up15arrow-down1·edit-23 months agoI really dislike code like that. Code like that tends to lie about what it says it does and have non-explicit interactions/dependencies. The only thing I can really be certain from that is: doAnything(); if(doAnything2()) { doAnything3(); } I.e. almost nothing at all because the abstractions aren’t useful.
minus-squareKogasa@programming.devlinkfedilinkarrow-up5arrow-down1·3 months agoYou realize this is just an argument against methods?
minus-squareKache@lemm.eelinkfedilinkarrow-up7·3 months agoAll methods? Of course not. Just methods like these.
minus-squareKogasa@programming.devlinkfedilinkarrow-up4arrow-down1·3 months agoNo, your argument is equally applicable to all methods. The idea that a method hides implementation details is not a real criticism, it’s just a basic fact.
I really dislike code like that. Code like that tends to lie about what it says it does and have non-explicit interactions/dependencies.
The only thing I can really be certain from that is:
doAnything(); if(doAnything2()) { doAnything3(); }I.e. almost nothing at all because the abstractions aren’t useful.
You realize this is just an argument against methods?
All methods? Of course not. Just methods like these.
No, your argument is equally applicable to all methods. The idea that a method hides implementation details is not a real criticism, it’s just a basic fact.