Accidentally Destroyed Production Database

Accidentally destroyed production database on first day of a job, and was told to leave, on top of this i was told by the CTO that they need to get legal involved, how screwed am i? Today was my first day on the job as a Junior Software Developer and was my first non-internship position after university. Unfortunately i screwed up badly. I was basically given a document detailing how to setup my local development environment. Which involves run a small script to create my own personal DB instance from some test data. After running the command i was supposed to copy the database url/password/username outputted by the command and configure my dev environment to point to that database. Unfortunately instead of copying the values outputted by the tool, i instead for whatever reason used the values the document had.

A junior software developer describes accidentally destroying the production database on the first day of a job by using the document’s example database credentials instead of the generated credentials for a personal test database. The CTO says legal action may be necessary, turning a beginner’s setup mistake into an absurdly catastrophic workplace disaster. This is shared as a reaction to a terrible first day, a disastrous technical mistake, or anxiety about making an irreversible error. EN: A junior software developer describes accidentally destroying the production database on the first day of a job by using the document’s example database credentials instead of the generated credentials for a personal test database. The CTO says legal action may be necessary, turning a beginner’s setup mistake into an absurdly catastrophic workplace disaster. This is shared as a reaction to a terrible first day, a disastrous technical mistake, or anxiety about making an irreversible error.

• @gentoomemes / 7241 2023-11-09