Ranter
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
Comments
-
lotd7775259dI forgot the best part, it’s not even my code that blew up.
It just happen to coincide with my deployment, so I got flagged and assigned for production outage 😂 -
lotd7775259d@donkulator don’t have access to anything in production.
But suggested to mgmt that we should gather differences from prod and reflect down. -
tosensei8454259dobviously your staging environment is borked up, if it doesn't reflect the exact database structure of production.
regularly making sure that stage is up to spec is an important step that shouldn't be neglected. -
fullstackcircus9915259dah nice the classic hot fix in prod only, undocumented, and never reflected in the rest of the dev / staging stack
🤡🤡🤡 -
jiraTicket2272258dMakes me feel so happy I work on an application that doesn’t interface with a database directly (we go through an API managed by another team, this has greatly reduced database issues) and don’t do significant writes other than per-user - cause we can have a preprod environment which runs unshipped code + the prod database
And even then there’s been unexpected issues due to settings unique to prod (such CDN/Edge Server config - like bot prevention)
How is it, that features goes thru the entire mill of dev, staging, preview.
Then when deployed to production, things blow up..
Turns out, columns are nullable only in production DB and of course, those happen to be null in there.
If I had a dime for every time I’ve seen shit like this…
(╯°□°)╯︵ ┻━┻
rant
production blues