Skip to main content

Happy Halloween! 👻

Being a developer it’s definitely not for the faint-hearted: to be a good one, you need to think on your feet, have a great memory, know several programming languages and so on. 

It doesn’t sound scary right? 

Oh, but we all know that there are days (or nights) when no ghosts, no zombies and no witches are as scary as a bad day working as a dev: bosses who want you to release updates that are not ready yet, colleagues who rename new fields in database tables and make the whole project disappear. 

A friend of mine worked in a food delivery app and his team brought down the whole Asian market for a few hours. It was the longest day of his life according to him, and he stills shudders when he thinks about it. 

So, what are your developer horror stories? Share them in the comments… if you dare! 

 

I was once given WAY too much control of a production database for an automotive advertising solution while learning just enough SQL to make me dangerous.  I confidently fixed a dealership’s data to reflect his stores Cadillac inventory and left for lunch, only to return to a firestorm of angry customers whose non-Cadillac inventory now identified as such.  Turns out, “Cadillac Rav-4” and “Cadillac Taurus” doesn't look great on a website!

I learned a very valuable lesson that day that’s stuck with me some 20 years later

 

Laughing at the “just enough SQL to make me dangerous”. 🤣 

The silver lining of these horror stories? The lessons learned. That fear never goes away and keeps us alert and humble!! 

Reply


Terms & ConditionsCookie settings