106

I will be getting nightmares about this now. The guy fucked up real bad.

Comments
  • 26
    @g-m-f this is totally true, I mean it looks like he was framed actually...
  • 16
    @g-m-f Also Who the hell doesn't see the obvious flaw in the documentation, and use fake URL/UN/pass... what they did was just idiotic
  • 33
    If you don't have backups for something like this then it's your fucking fault.
  • 7
    Backups or it didn't happen
  • 2
    If the company name was mentioned they would have closed shop ran away by now. That dude should have posted to devRant should've been even more awesome
  • 5
    Not the guys fault at all.
  • 4
    Not his fault, it was the company 🙄
  • 2
    The guy made a mistake, by giving a junior dev this access the company made a massive fuck up.
  • 6
    Who puts the actual server url with the credentials in the documentation

    I'm guessing they don't do frequent backups. And even if they don't, they should have it in the documentation to make backup before doing devops.

    The CTO isn't letting the guy help because he doesn't want his side of the story heard
  • 8
    I think that HE should have legals involved, for unfair termination..setting up the dev env following a written guide and fucking production up should have the documentation head AND the CTO terminated immediately
  • 4
    Yeap, if I were him/her, I would look into suing the company for causing me distress and potentially ruining my future chances ...

    No orientation, no supervision, no redundancy, no disaster recovery, no backup, fucking hell ...
  • 0
    and what about a backup? full access to him, really?. they deserv it. =)
  • 0
    Yeah it was bound to happen at some point if they had prod credentials in the Docs. They should have at least mentioned to him not to use those. They messed up on their own part.
  • 1
    They put productions credentials in the setup-docs AND had no working backups. Hardly OPs fault
  • 1
    Not the guys fault at all. What kind of idiot CTO puts the prod DB credentials and connection on the documentation for initial setup??
  • 0
    I kind of don't buy it. That story relies on a lot of things happening that no one with even mediocre experience would do. Definitely no legal implications.
Add Comment