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
-
@kwilliams yep.
Or sorting suddenly doing not what the dev expected when he wrote an nondeterministic function -
If all else fails, you'll have to push a load of debugging information to prod (without loading the actual feature), then pour through logs to work out what's different. When you've worked it out, you'll need to fix your nonprod environments to behave properly.
That's not at all a job for a junior though - at this point a senior should be taking it off your hands and managing it.
Started a new job as junior developer. One of my first task was to sent a simple notification on an event in out product. Write the code, test that it works, push to devops.
Code compiles, tests pass, it’s deployed to internal test env. Check that my notification works in the test env. No problem.
It’s deployed to the customers test environment. It works and customer accepts it for prod.
We release to prod and of course it fails. Seems to be a simple string.Format that fails for god knows why. After 3h of debugging on prod without success we decide to roll it back.
Today we decided to try it on a backup of the prod db since one of the strings was taken from the db. Still working. No matter what data I input when trying it locally it still wont reproduce the issue we saw on prod.
Fuck this
rant