> Overworked Engineer misses semicolon. All night review session finds it, data gets loaded!
> Management insists Jira stories be routed to new Epic. Team Lead spends hours learning Jira API before giving up and doing it "the hard way"
I love this "spend hours figuring out the API" then giving up.
Maybe it's just me but I have noticed that a lot (and it mean a lot) of devs will overestimate greatly on anything manual they need to do that they don't like. And spend hours if not days trying to automate it. Which is fine if it's gonna be needed again soon or over and over. But really, what is so bad in spending literally 5 minutes doing the above manually with a Jira filter and bulk edit? And by extension sometimes there's not even a bulk edit and you need to do something by clicking the same 5 steps 50 times to acgieve something. Again 5 minutes of actual work. Just put on a nice fast song from whatever music genre you happen to love and do it. Done.
Is it just me?
Eventually gave up on the automation and resolved to spend a few weeks clicking every 15 minutes to complete the simulations. It was very hard to stay motivated, but I got two papers out of it.
The disadvantage is now my CV says I'm an expert at an FEM framework which I never want anything to do with ever again.
Sometimes problems come from trying to automate at the lowest level, when maybe screenshotting a vm and sending a click at a specific position if the pixel colors change to the error condition could be done a bit faster.
And the even realer ones will spend years coming up with a universal solution to figuring out which is more optimal.
Agile expert called in, who saves the day(night?)...