Project Leader is explaining to teammate how their UI will call my API and it'll run asynchronously in the background. UI guy asks: about error handling? I said the callback listener will be notified if anything goes wrong. I ask the PL, what next? just log and forget about it (that's my sarcasm)? How would anyone know this has failed?

PL says: good point and can worry about this later. Lets first focus on getting things to work.

You know later never comes. Well, except when the customer reports a problem. Its like every disaster movie you've ever seen before

Ever feel like you've got a two headed coin, but keep calling heads?

When your co-worker is told to implement something, and insisted it is the wrong way to go:

It's how you train a puppy David. He poops, you rub his face in it, then toss him outside. I'm afraid you're the puppy. However .. It's not your poop 😳

Weblogic Server won't start, broken build was auto-deployed. How does a broken build even get deployed? 🙄

Told "till the server is fixed work on your next-release bugs". Sure, can investigate, maybe even code fixes, but with a broken dev environment how do we test anything?

" Hmm..Oh yeah, right" 🤔

When some one else checks in code by merging a class you wrote, but now they've broken the build .. And some how it's now my problem 😳

First they make it difficult to do your job. "Only use this server for your testing with twenty other engineers". And when you adjust to that, they change it to impossible. "The server is off limits while demos are on going" .. But you're expected to continue working at full speed ahead.