I'm thinking Instroduction should be an actual thing

Working out how to continue an interview when the interviewee thinks Test Driven Development is fixing bugs raised by the Test Team

Hey {restaurant}

When you find yourself mentally fixing someone else's CSS at the new interactive bus stop

Knowing that being asked to help the PM with his Client Project Status Report on a Friday evening means a) it's late, b) he has no idea what has happened since the last one and c) you'll be writing it all anyway.

Repeat each week for the rest of eternity

Inheriting someone else's CSS where every line ends with !important

Business analysts who spend more time on the format of a document than the content

When you've managed to get to +99 ok your first day on devRant but can't think of anything else to post to get you into 3 digits!

Pacific != specific

When you find out the last 3 hours of your life has been wasted finding that some numbskull confused the Round method with the Random method in the currency conversion logic

Finding out that the Project Manager and Test Manager are actually in a relationship then spending the rest of the day trying to work out what you said to each of them in confidence

Agents who try to convince you taking a job that earns less is a good idea for any reason other than them getting a recruitment fee

Salesmen who value commission over their own humanity

Emails with read receipts

People who email you then immediately walk over to check whether you've read the email yet

People who double-click hyperlinks

Having to join an emergency meeting to discuss progress of an urgent resolution the very attendance of which just delays the fix. Then repeating the meeting every 30 minutes.

Project Managers who plan on the basis that weekends are part of the project plan, but specifically only for tasks that do not require them to be present

Use of the term reach-out in anything other than a Four Tops song

Testers who find an issue that prevents execution of an early step common to many scenarios, who then dutifully create 150 tickets to fail each scenario individually, crowing on about how many issues they've found

Requirements that start with "There is a requirement to..."

"Agile" customers who insist on signed off specs, fixed price and 150% of the original scope

People who think that emailing, texting, voicemailing, whatsapping and skyping are acceptable alternatives to raising a ticket/defect/issue

Project Managers who stand next to you whilst you are attempting to patch a critical issue