When you live close enough to know that if your power went out there was definitely an interruption of some kind at work, so have to set the alarm for 5.30 to get in first and deal with any mess there it :(
Hopefully that expensive, site wide, backup generator that was installed actually works!

17 hours, trying to prepare for a live demonstration, never did figure out what was wrong with it (luckily the guys in the office managed to find the issue) but didn't make the deadline:(

return ((variable == 1) ? true : false)

So this embedded product is already a year late as cutting a task from the schedule didn't make the problems it would have addressed go away.
Now there's a performance issue (turns out to be how the customer had configured something) after we've been stumped for over a month and not got any closer, theres a meeting with the design authority, project manager, systems engineers etc, we say we can't tell where the issue is exactly, can't easily tell what Linux is doing all the time etc etc, so this product does a lot of IP processing, the project manager asks - do we even need an OS?
Are you having a laugh?! We barely took him serious before this meeting, we still don't now and it was three years ago! I mean, who wants to write their own OS and associated infrastructure themselves? 1 year late already, think you can add another 20 man years onto that!

When being at work for just after 7am is considered normal by the entire team :(

Trying to dual boot windows 10, won't allow me to install to the hard drive I select, tells me to see the log. Look in log, won't let me install to that drive because it's not my primary drive, why not just tell me in the error message then wasting my time finding how to find the logs!!!

When a customer decides they want half of what you delivered last time and half of something new to be used at the same time.
Ah, I think that'll take us a year to make that mess work!!
Makes me want to scream!!!
(all comes about because they're not happy with the original thing - does exactly what it needs to do to specification)

When a build is rushed out at 3.30 on a Thursday ready for weekend testing, gets to Friday morning when everyone goes to install it to find the package didn't get created and there isn't really a build available. Best bit is, the build manager works from home on Fridays (can't do builds remotely) and the engineer that broke it isn't in till Monday

Would you like to hear a TCP joke?