1. Playful yetintrusive tinkering
“Congratulations! Mine was intentional, back in college, where all PCs had open telnet … we discovered it was easy to seize someone's computer for a while, and then watch them look around for the culprit, which we thought was hilarious.” — ihaveajob
2. Distrust of unreliable code
“My first ever fork bomb was in the 90s, running Microsoft own example code for OLE (or was it COM?). … a great early lesson to never trust code you read online. Even if it is from Microsoft’s own developer portal.” — hnlmorg
3. The uncanny speed of badly written code
“The realization that even badly running code is still faster than the average human is rather terrifying.” — siruwastaken