<story><title>Accidentally destroyed production database on first day of a job</title><url>https://np.reddit.com/r/cscareerquestions/comments/6ez8ag/accidentally_destroyed_production_database_on/</url></story><parent_chain><item><author>Rezo</author><text>Sorry, but if a junior dev can blow away your prod database by running a script on his _local_ dev environment while following your documentation, you have no one to blame but yourself. Why is your prod database even reachable from his local env? What does the rest of your security look like? Swiss cheese I bet.&lt;p&gt;The CTO further demonstrates his ineptitude by firing the junior dev. Apparently he never heard the famous IBM story, and will surely live to repeat his mistakes:&lt;p&gt;&lt;i&gt;After an employee made a mistake that cost the company $10 million, he walked into the office of Tom Watson, the C.E.O., expecting to get fired. “Fire you?” Mr. Watson asked. “I just spent $10 million educating you.”&lt;/i&gt;</text></item></parent_chain><comment><author>_jal</author><text>Seriously. The CTO in question is the incompetent one. S&amp;#x2F;he failed:&lt;p&gt;- Access control 101. Seriously, this is pure incompetence. It is the equivalent of having the power cord to the Big Important Money Making Machine snaking across the office and under desks. If you can&amp;#x27;t be arsed to ensure that even basic measures are taken to avoid accidents, acting surprised when they happen is even more stupid.&lt;p&gt;- Sensible onboarding documentation. Why would prod access information be stuck in the &amp;quot;read this first&amp;quot; doc?&lt;p&gt;- Management 101. You just hired a green dev just out of college who has no idea how things are supposed to work. You just fired him in an incredibly nasty way for making an entirely predictable mistake that came about because of your lack of diligence at your job (see above).&lt;p&gt;Also, I have no idea what your culture looks like, but you just told all your reports that honest mistakes can be fatal and their manager&amp;#x27;s judgement resembles that of a petulant 14 year-old.&lt;p&gt;- Corporate Communications 101. Hindsight and all that, but it seems inevitable that this would lead to a social media trash fire. Congrats on embarrassing yourself and your company in an impressive way. On the bright side, this will last for about 15 minutes and then maybe three people will remember. Hopefully the folks at your next gig won&amp;#x27;t be among them.&lt;p&gt;My take away is that anyone involved in this might want to start polishing their resumes. The poor kid and the CTO for obvious reasons, and the rest of the devs, because good lord, that company sounds doomed.</text></comment>
<story><title>Accidentally destroyed production database on first day of a job</title><url>https://np.reddit.com/r/cscareerquestions/comments/6ez8ag/accidentally_destroyed_production_database_on/</url></story><parent_chain><item><author>Rezo</author><text>Sorry, but if a junior dev can blow away your prod database by running a script on his _local_ dev environment while following your documentation, you have no one to blame but yourself. Why is your prod database even reachable from his local env? What does the rest of your security look like? Swiss cheese I bet.&lt;p&gt;The CTO further demonstrates his ineptitude by firing the junior dev. Apparently he never heard the famous IBM story, and will surely live to repeat his mistakes:&lt;p&gt;&lt;i&gt;After an employee made a mistake that cost the company $10 million, he walked into the office of Tom Watson, the C.E.O., expecting to get fired. “Fire you?” Mr. Watson asked. “I just spent $10 million educating you.”&lt;/i&gt;</text></item></parent_chain><comment><author>champagnepapi</author><text>I agree, it&amp;#x27;s the fault of the CTO. To me, the CTO sounds pretty incompetent.  The junior engineer did them a favor. 
This company seems like it is an amateur hour operation, since data was deleted so easily by an junior engineer.</text></comment>