It's ten years since we launched Amazon CloudFront! Building it was super fun, my first day at Amazon was spent getting stuck into the CloudFront routing software and making it actually work. A few weeks later, but before we launched, we hit my favorite bug ever ...
-
-
The bug affects 75% of the Earth's surface, but by geographic coincidence or Greenwish winning the meridian wars, it just happened that our entire dev team was unaffected. Both Seattle and Dublin are in the "positive, positive" quadrant of the world!
Show this thread -
So we never experienced it ourselves, or our test cases, and we didn't notice it until we really started looking at other locations. I always think of that when I remember that even "dumb" and "obvious" bugs can be subtle and invisible because of your perspective.
Show this thread -
*Greenwich in my previous tweet. Anyway, fun bug! CloudFront had an incredible launch team, including 8 then-or-now Principal Engineers, which is staggering!
Show this thread
End of conversation
New conversation -
-
-
It clearly was a bug in the product but was it a bug or a feature of the parser?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's glorious. Reminds me of one of my favorite bugs caught just before deployment: SQL> select convert(datetime, '2005-03-09 00:00:00.000') 2005-09-03 00:00:00.000 This particular Microsoft SQL oddity only triggered when the locale DATEFORMAT was 'dmy'.
-
Development was done in the United States, but production was in the United Kingdom. It would parse ISO dates properly if the separator was omitted within the date spec or if a 'T' delimiter was placed between the date and time portions.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.