How to survive a toxic workplace and how to avoid creating one
Imagine going into an environment suffering some serious performance issues adversely affecting the day-to-day operations of the business.  From initial conversations it seems great.  You&#x27;re asked about how you&#x27;d handle, &quot;difficult personalities&quot; a fair bit, but aside from that, seems like you can add a ton of value.<p>In your first days, you exhaustively quantitatively measure the entire operating environment, prioritize a plan of attack based on the data, and go at it.<p>By the end of the week, you have many improvements testing successfully while still producing identical and correct results.  In one instance, runtime reduced from 200 minutes ... to 1.2 seconds.  You dutifully write up an explanation, articles, all the gory compiler knowledge, etc.  Submit pull requests.  Your team is chuffed.<p>Result?  Someone on another team calls you into a meeting, to railroad and scream at you for, &quot;making them look bad&quot;.  I mean SCREAM.  As if they&#x27;re trying to kill you with words.  You report the incident to who you are directed to report into and are told to, &quot;man up.&quot;<p>-- -----<p>This is when you ensure the termination clause is airtight.  You spend 5 minutes drafting a termination letter, print it, and hand it in.  Drop the mic.  Walk out.  Good riddance.<p>-- -----<p>Scary thing?  That&#x27;s nothing.  Ever get hired for performance tuning and then the DBA refuses to create your account, and cusses out the CTO when the CTO asks why?  Ever see a developer get punched by someone?  Have you been in an environment where there were actual cots set up for people who had to work through the night, because it happened that often?<p>I&#x27;ve.  Seen.  Things.