You're viewing a single thread.
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”.
340 1 ReplyI like him already
149 0 ReplyTo be honest I'd like to see his resume, kinda wanna hire him
46 1 ReplyThat was close to 30 years ago - a DOS memory manager written prior to Windows 3.0. He’s likely retired now…
46 0 Reply
proposal to rename exit() to oh_shit_oh_shit_oh_shit()
55 0 Replyscrew_you_guys_im_going_home()
43 0 Replyfuck_this_shit_im_outta_here()
12 0 ReplyIn the 90s there was a Redhat distro called Cartman.
6 0 ReplyRed Hat 6.1, that was my first Linux distro.
4 0 Reply
screw_you_im_gonna_go_play_minecraft()
3 0 Reply
I will keep this legacy alive within my code
45 0 ReplyOkay yeah but I know what all those variables do
30 1 ReplyUgh.
17 2 Reply
-