1. 5
  1.  

  2. 5

    I read this, waiting for some kind of story payoff, and it never hit. Basically, instead of fixing an error it was embraced and became a joke. As far as I can tell, it was never fixed. I didn’t get any insight into even trying to find the error, nor did I get much about the culture, that is, how it became a joke.

    In short: huh?

    1. 3

      Thanks, Geoff.

      Yeah, the error was never fixed, mostly because it was not a single error. It was a group of errors: -0// was the symptom of something going terribly wrong and totally untrapped somewhere.

      I’m not really interested in discussing how we debugged the many different situations in which -0// appeared and of course I don’t even remember most of them.

      Nevertheless, I’m super happy to expand on how it became a joke as much as needed. I’m just not sure what to say. So, what would you recommend I add to make the culture part more complete and interesting? Any particular questions you think I can answer to give a better view of the cultural implications of -0// would be much appreciated.

      Thanks, again.

    2. 3

      I don’t know why, but I found this story really heartwarming. I’m left wondering if I’ve forgotten to love my squashed bugs. I definitely remember some eureka moments with some of them.