5
LLAMS
6y

Spent most of this week busting my ass working on a hotfix that came out of nowhere with mega high priority. This annoys me greatly because the hotfix wasn't even fixing a bug, it was adding new functionality because certain customers were being blocked from testing without this specific feature. In my humble opinion, given that we release every weekend, hotfixes should be reserved for actual critical bugs. But anyway, as I probably could have predicted, the code got to QA and exploded. Literally nothing works.
This is what happens when you try to rush out features to satisfy customers. If you try to rush something that is late, you WILL make it later.
Meanwhile there's an issue I'm supposed to be fixing for our next release which goes out this weekend and I've had no time to even look because of this hotfix. And now it's the end of the day and I just feel worn out from stress, tomorrow will no doubt be similar.

Comments
  • 3
    blaming analysts and the whole business unit is usually appropriate :D

    i don't know if in you company they profile devs according to metrics coming out of jira (or equivalent).
    in mine they do, and normally i don't move a finger unless things are correctly named, it's all about being fair with the whole team.
    CR, small enhanchement, analysis flaw.... call it whatever, but not *fix
Add Comment