Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Related Rants
So, today timestamps within my database saved me. I have one titled "created_at" to indicate when the item was originally created.
Today a large client called up to complain that they have 296 bookings but only 288 menu choices (each booking has a menu choice). Basically, saying I'd "programmed it wrong [sic]" :(
After taking a quick look at the date the client originally added the menu and the date the missing bookings were created, I made a discovery.
It turned out the client was at fault. They had set an event (customers book events and bookings have a menu choice) live without associating the menu. This meant the event had been live without a menu for customers to book.
I simply compared the timestamps of the missing bookings to the date the menu was originally added. The customer most likely made the event live for period (I estimate ~45 mins), realised they hadn't associated a menu and then added it afterwards. Of course at this point it was too late as people had already booked.
No need for a huge email either. I condensed the above into a 5 sentence email.
Timestamps are soooo useful
rant
clients
timestamps
mysql