ZILtoid1991@lemmy.world to Programmer Humor@programming.dev · 5 days agoUncle Bob becoming even worse:lemmy.worldimagemessage-square211linkfedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageUncle Bob becoming even worse:lemmy.worldZILtoid1991@lemmy.world to Programmer Humor@programming.dev · 5 days agomessage-square211linkfedilink
minus-squareZILtoid1991@lemmy.worldOPlinkfedilinkarrow-up0·5 days agoA guy, who made programming worse, especially in enterprise settings.
minus-squaresiftmama@lemmy.worldlinkfedilinkarrow-up0·5 days agoDepends on which parts you look at. There is plenty that he wrote about that have made coding enjoyable, but yes, also plenty that is the opposite. I never saw his book as a bible though. I always thought of it as a “here are possibly good ideas, see which you and your team likes”.
minus-squarepivot_root@lemmy.worldlinkfedilinkarrow-up0·5 days agoPeople don’t like tracing what something is doing across seven 12-line functions spread through multiple files?
minus-squareNoxy@pawb.sociallinkfedilinkEnglisharrow-up0·5 days agoWhat suggestion of his is related to that, just out of sheer curiosity?
minus-squarecbazero@programming.devlinkfedilinkarrow-up0·5 days agoHe says a function should never be longer than 4 lines (in his Clean Code book).
minus-squarePrunebutt@slrpnk.netlinkfedilinkarrow-up0·5 days agoHe’d probably say that 12 lines is waaaay too much!
minus-squarevanillama@programming.devlinkfedilinkarrow-up0·5 days agoYeah, he’d break it into 12 methods that call each other one after the other instead
minus-squareFeyd@programming.devlinkfedilinkarrow-up0·5 days agoThe code had the single responsibility to waste your time
A guy, who made programming worse, especially in enterprise settings.
Depends on which parts you look at. There is plenty that he wrote about that have made coding enjoyable, but yes, also plenty that is the opposite.
I never saw his book as a bible though. I always thought of it as a “here are possibly good ideas, see which you and your team likes”.
People don’t like tracing what something is doing across seven 12-line functions spread through multiple files?
What suggestion of his is related to that, just out of sheer curiosity?
He says a function should never be longer than 4 lines (in his Clean Code book).
He’d probably say that 12 lines is waaaay too much!
Yeah, he’d break it into 12 methods that call each other one after the other instead
The code had the single responsibility to waste your time