3 ms·
During the week before Christmas, I had to rush a quick change into production that would allow us to split orders into multiple shipments. The software was fi
by edw519 16y ago
During the week before Christmas, I had to rush a quick change into production that would allow us to split orders into multiple shipments. The software was fine, but an admin accidently booted the wrong server (that had a bad test version of the software) to send feeds to the UPS label printing server.
Two days later, 272 packages arrived at one customer's house in Minnesota.
She had a good laugh, and we managed to fix the problem in a couple of days without too much additional expense.
Lessons learned:
1. If something is wrong, I'd rather have it crash than give wrong results.
2. Get a good version control system.
3. Have good policies and procedures.
4. Don't change anything after December 1.
5. Don't ask me to do a rush job if I'm busy on Hacker News.
- knotty66 16y agoI had a similar situation once where a character set encoding bug in a cron script I wrote and was told to put live late on a Friday caused one lucky customer to receive an SMS message every minute for over 60 hours. I got away with that one.