Once, I had a horrible gig. Because it was so bad, I wrote down this list, so that I would never forget how awful a gig can be–and, by contrast, how good I have it now.
To those who knew me then: I have changed names to avoid lawsuits, but if the shoe fits…
I have NOT changed names for tools, whose reputations precede them.
I am thankful that I have no more of this to deal with after I left That Horrible Gig (THG):
1. All-night deployments. (10 PM to 6 AM, baby.)
2. Lack of Systems Analysis by people who should have done it already.
3. Big boss blustering. (And thinking that he actually accomplished anything by it.)
4. VersionOne sucks. (And management abandoned JIRA, which is so much better.)
5. Even so, nobody uses VersionOne, so we lost critical details. All the time.
6. Email threads. (Lost critical details? Yep.)
7. “Waterfragile.” (I coined this term, but you can use it, too.)
8. Too many walls: the IT Paranoia Department, Linux Admins, Server Management Teams who don’t have root (seriously!).
9. Systems Analysts and Project Managers doing architecture.
10. One hotshot Junior Developer refactoring everything. (Beware coders who never push their changes until it’s a huge pile of commits.)
11. The best people leaving because THG doesn’t recognize/reward greatness.
12. Microsoft Lync overwriting my status update.
13. Management making crappy decisions.
14. Management not consulting the technical people who know better.
15. Monolithic legacy framework built by monkeys…in knickers.
16. Hiring people then…not training them.
17. Hiring crazy people. (Who drop off the face of the planet with hardware that contains copies of proprietary software. Until you sue them to get it back…maybe.)
18. Rootless installs, and…
19. Compiling packages, and…
20. Manually managing dependencies, because of…
21. So-called “Linux admins” who are scared of linux package managers.
22. Long-time employees laughing about having to miss holidays with family due to work deadlines. (Beware people who call themselves “crazy” all the time–they might be!)
23. Having to watch a server admin run manual commands that I give them, because I’m not allowed to run them myself.
24. Not having root access to all the servers I support.
25. All sudo access expires after 10 days max. (Just plain stupid.)
26. Thick accents that are hard for me to understand. (I’m not opposed to working with people from different linguistic backgrounds. But I got tired of fighting to understand people who just didn’t care if I understood them or not. It’s a real refresher to work with people who know how to communicate clearly–whatever language they use.)
27. Microsoft Lync’s sucky screensharing.
28. Contract renewals.
29. Reporting hours against projects that don’t match what I’m working on. (I was commanded to report my hours that way, because it made other numbers match in some report I never saw. I had to finally give up and do what they wanted. I hope they stop that particular shell game.)
30. A username that consists of a letter and 5 numbers. (Welcome to THG, “x12345″! Nothing says, “You’re replaceable,” like that kind of username.)
31. Trip reimbursement torture. (3 hours to file one trip reimbursement request. No joke.)
32. Staffing Agency often asking for hours worked because THG’s Sucky Time System doesn’t talk to Staffing Agency’s systems. (It’s an “IT” staffing agency, right?)
33. Too many layers, too little information sharing at a high level (aka, Chapter 5 Resources). (So many of the failings listed here are directly resultant from this one.)
34. Microsoft Lync dying and losing conversation history.
35. Bad data everywhere and nobody takes responsibility for fixing it.
There were a few positives that are worth mentioning:
1. My immediate supervisor watched out for me and trying to give me space to innovate.
2. There was one shining star on our team who learned and grew at an astounding rate; it was a joy to work with him and watch him take off.
3. Fat paychecks.
Was it worth it to leave? Absolutely. If this sounds like where you are, get out ASAP. Thank me later. :)