Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
I've seen similar but for me it was: I get asked to take over from someone who left to get a pull request approved and then realise that the ONE unit test that they added is actually an end to end test that fails 3/4 of the way through in some overly complex code that uses multithreading for limiting requests to an API.
The tests return an empty file, the code was never approved, yet the branch was used in a production Jenkins job.
SomeNone41410dWho said 'straightforward feature?' Bet it was either the client, or a manager; surely not a dev…
You should slap them around a bit with a large trout.
Or else say, 'If it's so straightforward, why don't you implement it yourself?'