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
-
@C0D4 I gave this rant the - - because there is no way they have it set up badly. This story is either faked or OP messed up wayyyyy worse than the dev with the ego.
-
@C0D4 exactly.
-
@jeeper
doesn’t add up 😕
no test environment should ever be able to call production DBS. also if that dev was doing any preliminary testing, the dev was sandboxing against production??
also how is win 98 a bad thing?
they could enjoy the day playing SkiFree, Chips Challenge or Tetris at the speed of SSD, and that’s after you get the drivers to work with a modern pc. -
@C0D4 That's the first thought that came to my mind. Plus usually credentials being different for production and QA DB's, also prevents these problems.
-
@avitron our Prod and QA databases require one to check out a password from CyberArk, and Prod CyberArk is separate from QA. Additionally, only specially designated Prod Support peeps can actually make Prod changes. I don't get this rant at all.
A dev decided to overwrite the master branch with his code saying its better. That it fixes the major bugs that all of us couldn't solve.
Against my better judgement of firing him, I decided to test it.
Firing up the testing site, we made test databases to use and we went to house.
In the middle of testing, I noticed the test DBs weren't being changed. While everyone was still testing, I looked at the code. It wasn't made to test on any databases, it was specifically designed for the actual production server.
However the damage was done. In a secret dashboard in the code, someone sent instructions to drop the tables, effectively ruining the production server.
We had the dev go to an offline backup site that only went online every 10 minutes a day to make new backups. So we shut down the production server, setup a maintenance page. I get my ass chewed out again, and we were sitting ducks.
I don't think the dev had enough punishment, so I grabbed his laptop and made a full backup of his data, and locked the SSD in a safe.
I downloaded a Windows 98 and put it on a flash drive. And installed it all on his SSD. The dev is now a proud (pirate) owner of Windows 98.
He came back and started balling on his desk. We all looked at him with a pity, but he deserved it.
I'll give him the drive on Monday.
Do you think he learned his lesson?
undefined
windows 98 is not a bad os
he deserved it
im evil