xia@lemmy.ca to Programmer Humor@lemmy.mlEnglish · 1 year agodo as i say...lemmy.caimagemessage-square15fedilinkarrow-up19arrow-down10
arrow-up19arrow-down1imagedo as i say...lemmy.caxia@lemmy.ca to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square15fedilink
minus-squareIphtashuFitz@lemmy.worldlinkfedilinkEnglisharrow-up3·edit-21 year agoMany years ago I had to try to debug a memory manager written by a really talented software engineer, with an interesting take on naming things… He referred to blocks of memory as “cookies”. He had a temporary variable named “handy” because it was handy to have around. He had a second temporary variable that referenced the first one that he called “son_of_handy”. If corruption was detected in a block of memory then it would set the flag “shit_cookie_corrupt”. If too many cookies were corrupt then the system would halt by calling the function “oh_shit_oh_shit_oh_shit”.
minus-squaredhtseany@lemmy.mllinkfedilinkarrow-up1·1 year agoTo be honest I’d like to see his resume, kinda wanna hire him
minus-squareVictoria@lemmy.blahaj.zonelinkfedilinkarrow-up1·1 year agoproposal to rename exit() to oh_shit_oh_shit_oh_shit()
minus-squareDrew Belloc@programming.devlinkfedilinkarrow-up1·1 year agoI will keep this legacy alive within my code
Many years ago I had to try to debug a memory manager written by a really talented software engineer, with an interesting take on naming things…
He referred to blocks of memory as “cookies”.
He had a temporary variable named “handy” because it was handy to have around.
He had a second temporary variable that referenced the first one that he called “son_of_handy”.
If corruption was detected in a block of memory then it would set the flag “shit_cookie_corrupt”.
If too many cookies were corrupt then the system would halt by calling the function “oh_shit_oh_shit_oh_shit”.
I like him already
To be honest I’d like to see his resume, kinda wanna hire him
proposal to rename exit() to oh_shit_oh_shit_oh_shit()
I will keep this legacy alive within my code