Maxing out the available disk space on a server, crashing the database, and bringing down our web app. It was a catch-22, I couldn't reduce the database size. It caused a day of downtime.
Or the rookie dev move where I expanded all the objects everytime a page was requested. The tree was some seven layers deep, and made a request for each object one at a time. Uh, there were better ways to approach it. lol, the dev server nearby our desk would literally whine (power up) when that happened.
But these experiences do help you gain empathy for that next dev who makes a blunder.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Maxing out the available disk space on a server, crashing the database, and bringing down our web app. It was a catch-22, I couldn't reduce the database size. It caused a day of downtime.
Or the rookie dev move where I expanded all the objects everytime a page was requested. The tree was some seven layers deep, and made a request for each object one at a time. Uh, there were better ways to approach it. lol, the dev server nearby our desk would literally whine (power up) when that happened.
But these experiences do help you gain empathy for that next dev who makes a blunder.