$work: Ey @Root, make this super simple thing.
$work: No, not like that.
$work: It also needs to do A, B, and C.
$work: No, not there. You should build it somewhere else, but I won't tell you where.
$work: You need to build out F and G, too.
$work: What do you mean you don't have the data? Just ask support drone #3. (who directs me to #2, and that one to #8 who doesn't know, and that one to #12 who won't answer)
$work: Why can't I do K, Y, or S? You should be able to infer these from the mind of whoever wrote the ticket by its wording, despite no mention of them whatsoever.
$work: Are you done yet? It's a super simple ask!

Dang. You really need to put your foot down on some of these things. Make it imperative that you cannot begin working on task until all parts of the issue are presented.

@root being overloaded with work and people wonder why she doesn't integrate to Corp social events when she's just try'na have a rest.

Classic.

Eurgh, frustrating as hell.

Whenever I face idiots that do this I create a story, then ask them to check *all* the details are there. When they approve , but come back with other requirements, I'll note a comment underneath saying "Bob has now informed me that x, y and z are also in scope." and ask them to verify. This continues whenever they change anything, and then it gives me a paper trail when a manager comes along and wonders what's happening.

It then should become painfully obvious they're the idiot, not you. Of course though, this does rely on having someone above them that also sees sense, and doesn't just assume "dev bad, middle manager good".

Root gets a reply from Support Drone in Chief!

SDIC: <non-committal answers>
SDIC: <incoherent babbling>
SDIC: <contradictory statements>
SDIC: I really photosynthesize with this. (Paraphrased)
SDIC: Go get SD#2 to work with me.

We speak the same language, supposedly, but fucking hell I can’t understand much of this.

ARGH. WHY CANT PEOPLE JUST FUCKING TELL ME WHAT THEY WANT?!

I want to build your shit. MAKE IT EASY AND TELL ME! IF YOU DON’T KNOW, FUCKING SAY THAT.

I believe business still does not understand that software development is iterative. Things can be added later. Think "epics" and "stories": not every story has the same priority. Stop embracing waterfall and big design upfront. Just require the one thing that will improve one aspect of the product. Afterwards, we can build on top of that. Continuous improvement in small steps. It is not rocket science.

My dad works as a recording engineer and editor at a very successful orchestra in my country.

Every time he finishes a recording and sends it to his boss, the boss needs to listen and point out things he doesn't approve of and that need fixing.

For the last year, he hasn't listened to anything he sent, not even once.

About a month ago, he got so mad at his boss and told him that he is quitting (and he really did, he found another job as an electrical engineer).

About 3 weeks later, someone from the orchestra said that "someone else is in charge of listening now" and that he can come back, since they eliminated the issue. They also raised his pay. He is now back in the orchestra, while ALSO being an electrical engineer (time allows him to do both at the same time).

**Make some noise**. Noise is the key with annoying companies today. Not patience.

@OmerFlame If I wanted to stay, I might make an effort.

Right now I’m just trying to survive.