Cows Look Like Maps@sh.itjust.works to Programmer Humor@programming.dev · 9 months agoBill is a pro grammersh.itjust.worksimagemessage-square98fedilinkarrow-up1804arrow-down197
arrow-up1707arrow-down1imageBill is a pro grammersh.itjust.worksCows Look Like Maps@sh.itjust.works to Programmer Humor@programming.dev · 9 months agomessage-square98fedilink
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up12arrow-down1·edit-29 months agoI’ve seen code that look like this: int delay = 15 * 60; // 10 minutes Even if the comment was on the same line someone forgot to update it. People just ignore comments. Better solution is to write (in C#): TimeSpan delay = TimeSpan.FromMinutes(15) Much more obvious what the code actually means.
minus-square18107@aussie.zonelinkfedilinkarrow-up8arrow-down1·9 months agoA better comment would be delay in seconds as that is the one thing not obvious from glancing at the code.
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up13·9 months agoOr just name the variable delaySeconds if you really want to store it as an int. Bonus is that every use of the variable perfectly communicates what it is.
minus-squareCCatMan@lemmy.onelinkfedilinkarrow-up1·9 months agoIs the better way is a runtime performance hit. Does the compiler optimize this?
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up1·9 months agoIt’s probably a little bit slower, but there are other things more worth to optimize than to shave off a few microseconds from a 15 minute delay.
minus-squareCCatMan@lemmy.onelinkfedilinkarrow-up1·9 months agoYeah, it adds up eventually when working with embedded platforms, but for PC stuff I agree.
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up2·9 months agoIf you’re working in embedded I guess you can probably make an inline function or a macro so it’s taken care of at compile time.
I’ve seen code that look like this:
int delay = 15 * 60; // 10 minutes
Even if the comment was on the same line someone forgot to update it. People just ignore comments.
Better solution is to write (in C#):
TimeSpan delay = TimeSpan.FromMinutes(15)
Much more obvious what the code actually means.
A better comment would be
delay in seconds
as that is the one thing not obvious from glancing at the code.Or just name the variable
delaySeconds
if you really want to store it as an int. Bonus is that every use of the variable perfectly communicates what it is.Is the better way is a runtime performance hit. Does the compiler optimize this?
It’s probably a little bit slower, but there are other things more worth to optimize than to shave off a few microseconds from a 15 minute delay.
Yeah, it adds up eventually when working with embedded platforms, but for PC stuff I agree.
If you’re working in embedded I guess you can probably make an inline function or a macro so it’s taken care of at compile time.