572
Developer stages of grief (kbin.melroy.org)
submitted 2 years ago by to c/programmerhumor@lemmy.ml
28 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 105 points 2 years ago* (7 children)

If you can fuck up a database in prod you have a systems problem caused by your boss. Getting fired for that shit would be a blessing because that company sucks ass.

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] 51 points 2 years ago (5 children)

    What if you're the one that was in charge of adding safe guards?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 5 points 2 years ago (2 children)

    If you are adding guardrails to production... It's the same story.

    Boss should purchase enough equipment to have a staging environment. Don't touch prod, redeploy everything on a secondary, with the new guardrails, read only export from prod, and cutover services to the secondary when complete.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 10 points 2 years ago

    Small companies often allow devs access to prod DBs. It doesn't change the fact that it's a catastrophically stupid decision, but you often can't do anything about it.

    And of course, when they inevitably fuck up the blame will be on the IT team for not implementing necessary restrictions.

    Frequent snapshots ftmfw.

  • permalink
  • fedilink
  • source
  • parent