Home
> Uncategorized > How a tiny slip can lead to big delays
How a tiny slip can lead to big delays
A tiny slip can lead to big delays. Late yesterday evening, I had to go from the Courtyard in Foster City to the Marriott in San Mateo, a distance of only 3.3 miles according to Google Maps (http://g.co/maps/2bry9). I made one wrong turn in the dark and the 3.3 mile trip suddenly ballooned into a 22.8 mile trip (http://g.co/maps/ae7sq). Zoom out a bit in Google Maps to get a better picture. Not funny, if I only say so myself.
Notes to self for the next major production change:
- Entertain the team with the above anecdote.
- Check if we are using an SOP (Standard Operating Procedure).
- Check if the person executing the SOP has practiced it.
- Check if there is ample slack time in the change window.
Categories: Uncategorized
Leave a Reply
Recent Comments
 | Mike Boligan on Two instances with the same OR… |
 | bernard polarski on Oracle 12c Gives Fresh Life to… |
 | Iggy Fernandez on Oracle 12c Gives Fresh Life to… |
 | David Phillips on Dilbert likes Hadoop clus… |
 | Steve Karam on What’s your take on RDBMS and… |
I do recall you being geographically challenged during another luncheon we had in Oakland.
Did you have to pay for toll, on top of the unexpected scenic route?
I briefly considered zooming through the toll gates without paying but wanted to avoid being the target of a high-speed police chase across the bridge.