Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com to Programmer Humor@programming.devEnglish · 5 months agoHow programmers comment their codelemmy.dbzer0.comimagemessage-square145fedilinkarrow-up11.55Karrow-down19file-text
arrow-up11.54Karrow-down1imageHow programmers comment their codelemmy.dbzer0.comAndromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com to Programmer Humor@programming.devEnglish · 5 months agomessage-square145fedilinkfile-text
minus-squareToribor@corndog.sociallinkfedilinkEnglisharrow-up17·5 months ago“What does this section of code do?” Run it and find out, coward.
minus-squareMaalus@lemmy.worldlinkfedilinkarrow-up2arrow-down1·5 months agoNah. It should be obvious by just looking at it in code. If it isn’t, you haven’t extracted single purpose methods out of it yet.
minus-squaremagic_lobster_party@kbin.runlinkfedilinkarrow-up2·edit-25 months agoJust having clear and concise variable names often goes a long way. Avoid using abbreviations. Breaking out the code into functions helps limit the number of variables within a scope, which makes it easier to name them.
“What does this section of code do?”
Run it and find out, coward.
Nah. It should be obvious by just looking at it in code. If it isn’t, you haven’t extracted single purpose methods out of it yet.
Just having clear and concise variable names often goes a long way. Avoid using abbreviations.
Breaking out the code into functions helps limit the number of variables within a scope, which makes it easier to name them.