"Are you willing to own the risk? If so, what will it look like? Can you budget additional time for addressing these bugs, and draft contingency plans?"

[–] Bazoogle@lemmy.world 12 points 1 week ago (2 children)

"You're overthinking it" - real response from my management

[–] IcyToes@sh.itjust.works 3 points 1 week ago

"True. It'll be perfectly fine, and because of that, you won't need me on call when it all goes dramatically wrong. If you need access to the repo, I'll add you in though. Good luck."

Or, if you've worked together a while "like I overthought it when we worked on x, and y went wrong, and I called it before it happened. Turns out I'm quite good at seeing car crashes in advance."

[–] Arcka@midwest.social 2 points 1 week ago

You're not alone

[–] Diplomjodler3@lemmy.world 11 points 1 week ago* (last edited 1 week ago)

*Sticks fingers in ears* Can't hear you!

[–] IcyToes@sh.itjust.works 7 points 1 week ago (1 children)

"I only know 1 (credible) way to build it. I'll take x days. I'll go right ahead with that."

[–] Diplomjodler3@lemmy.world 8 points 1 week ago (2 children)

We need it yesterday! Just get it done!

[–] IcyToes@sh.itjust.works 4 points 1 week ago* (last edited 1 week ago) (1 children)

"Why are we only learning about this now? How long has this requirement been known? I think we need to look into the process that work comes into the team otherwise, if we don't learn, we are going to take the website down and cost the company thousands/millions. It's worth working with the business to get a batter understanding of upcoming requirements so we know what's going to be needed in a months time". There is a reason retros exist. Oh, and you have to be good at teasing out real deadlines vs arbitrary deadlines made up with no justifiable reason.

"You ask me how long it'll take, and it's 3 days. You probably need to manage expectations on this. Maybe let them know the risks of x, y and z and why it will take this long".

[–] jjjalljs@ttrpg.network 2 points 1 week ago (1 children)

I feel like every retro I've attended has been a farce.

"What went bad? We said doing it this way would be harder and more risk prone. Management insisted we do it that way, and it took longer than and caused a site outage."

"What should we do differently?'

"Listen to the team next time"

"That won't happen"

[–] IcyToes@sh.itjust.works 2 points 3 days ago

Delayed response, but raise a ticket in retros saying retros should be cancelled. Andvwhrn asked why, say nothing is followed upon or learn so there is no point doing them.

Then you can talk shit about them and make clear without change, you won't commit time to next one as there is no point.

Could be fun to see what the response is.

[–] Auth@lemmy.world 1 points 1 week ago

Thats a scheduling issue on your end. I've given the time estimate my team needs. You can adjust expectations and shift around my allocated time but it will take x hours no matter what.

There is no putting up with half of these complaints. They just arent real things that occur in a workplace.