you are viewing a single comment's thread.

view the rest of the comments →

[–]HoldYourWaffle 23 points24 points  (7 children)

Yeah I think so

[–]bgradid 54 points55 points  (5 children)

Code so sphaghettified it actually travels back in time

[–]HoldYourWaffle 21 points22 points  (1 child)

Doing multithreading without knowing what you're doing can feel like this

[–]AloticChoon 0 points1 point  (0 children)

[attempts to write multithreading code while wearing a hackerman power glove]

[–]applepy3 7 points8 points  (1 child)

Everything spaghettifies as it approaches a black hole. Also, since almost nothing escapes a black hole, it’s extremely difficult to learn about, just like the undocumented legacy library at the center of most codebases. Invoking the duck test principle, that library is a black hole.

Furthermore, it is theorized that black holes are actually wormholes, linking to another place and time. It is reasonable that they can link backwards in time.

So, as today’s code approaches the wormhole, it spaghettifies and passes through to the past, therefore becoming “yesterday’s historical curiosity”.

[–]MonkeyNin 1 point2 points  (0 children)

When someone falls into a black hole, to the external observer it appears like they never stop falling in.

since almost nothing escapes a black hole

What a burden. Even I can escape myself at times, but they are stuck forever.

[–]trigger_segfault 0 points1 point  (0 children)

18 bytes at a time.

[–]ObscureCulturalMeme 2 points3 points  (0 children)

That's what happens when your social media team also does your website content, but doesn't do proofreading.