But this is a positive, optimistic Twitter account, so let's go over the actionable remediations here:
-
-
Replying to @patio11
1) You don't have production DB credentials lying around in documentation. You keep those in an encrypted credential store.
1 reply 8 retweets 50 likes -
Replying to @patio11
2) If your organization is mature enough to have junior developers, you're mature enough to not have production connected to dev boxes.
2 replies 8 retweets 36 likes -
Replying to @patio11
It should be impossible at the network layer for a junior dev to connect to the production environment (perhaps "absent some ceremony").
3 replies 9 retweets 41 likes -
Replying to @patio11
3) You have a mature incident response plan. If your production database goes away, your CTO either is or is deferring to incident manager.
1 reply 8 retweets 37 likes -
Replying to @patio11
4) You trained the junior employee on incident response procedures, probably on day 1~5. They understand that company doesn't blame people.
1 reply 7 retweets 32 likes -
Replying to @patio11
5) If a junior employee exercises reasonable fear of losing their job when causing an incident, you reply "Not happening; we'll talk later."
1 reply 13 retweets 47 likes -
Replying to @patio11
6) Your training for junior employees (you have training for them) covered company confidentiality and PR procedures.
1 reply 8 retweets 28 likes -
Replying to @patio11
Incident retrospectives are a positive thing. They should generally not be posted to Reddit; if they are, that fact will be planned.
1 reply 4 retweets 28 likes -
Replying to @patio11
7) You have backups for the production database. You wargame out redeploying it from metal, approximately quarterly. Docs are up to date.
3 replies 8 retweets 40 likes
8) Since you hire a team of mutually supportive professionals, a senior engineer not doing incident response took it upon themselves to
-
-
Replying to @patio11
ping the junior engineer, ask about how they're doing, tell them a story about the last time they brought down prod, etc.
2 replies 11 retweets 43 likes -
Replying to @patio11
9) Public communications regarding the incident are signed by the CEO or CTO; identify the root cause as failure of management.
0 replies 10 retweets 50 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.