With the latest security updates (including WMF out-of-band release) a lot of discussion has been going around on the web about "how long does it take to code a fix" and "how long does it take to test it".
If you come from a small scale software shop, or only have a couple of customers, it might seem like all fixes take about 2 hours and can be released the afternoon after you compile it. After all if it doesn't work just apologize and try something else the next day. Ahhh the good old days.
When I used to work on a compiler used by only a few dozen people, it took several hours just to run the automated test suite on just one platform, and gearing up for release took weeks of testing. If there was a bug, if we were lucky we could turn it around in 24 hours. Realistically we took weeks to fix most bugs.
One time when I wrote an online commerce site (many years ago) I had a bug go live that could reveal personal information (VERY VERY bad bug). I stayed awake for about 2 days testing the fix to the bug (I fix the symptom in about a minute but I wanted to be very sure that my real fix worked). It was terrible, as I knew there was no way to sleep until it was fixed.
But things are of a bit of a different scale if your site or software works in different languages, runs on different systems, support millions of users, etc.
Here's an interesting article about how much work can go into a "five-lines of code" feature.
http://blogs.msdn.com/ericlippert/archive/2003/10/28/53298.aspx
Interestingly, none of this thinking is really new - Brookes wrote the Mythical Man Month some time ago and really not a lot has changed in that time. Old hands in software development know about this stuff. But maybe entire generations have grown up without learning the complexities of large projects. I personally think it would be instructive
Another good article here on fixing bugs:
http://headblender.com/joe/blog/old/001280.html
And a video on "bug triage" - how do you decide what to do with bug reports when they come in thick and fast?
http://channel9.msdn.com/ShowPost.aspx?PostID=26641
Ahh... all that complexity... it's almost enough to stop me from missing late night code writing sessions... :-)