←back to thread

177 points foxfired | 1 comments | | HN request time: 0s | source
Show context
vanschelven ◴[] No.43619010[source]
Personally I've never found it a problem to just fix things that I see are broken, as a dev, without PM approval, even in very dysfunctional organizations. Sometimes it even goes noticed and people applaud you for it.

In other words: though I acknowledge that the phenomenon described in the article is real, I sometimes feel it's just because developers accept a reality that doesn't need to be accepted.

replies(6): >>43619157 #>>43619671 #>>43621509 #>>43629303 #>>43630100 #>>43631697 #
dakiol ◴[] No.43619157[source]
But fixing a bug requires time from your side (mainly doing the investigation) and from others (code reviews). So if the whole team is working on an “important” epic (this is, one with a deadline, like any other epic) and you come out of the blue with a bugfix unrelated to the epic without telling anyone: well, that’s weird isn’t it? Your EM/PM will ask you why you didn’t prioritise the epic’s tasks, and your colleagues could say that they cannot switch their focus or gather time for reviewing your fix (more so that it’s something that the EM/PM hasn’t approved).

So unless you are overworking (e.g., you work in your jira tasks AND on top of that you fix bugs) I don’t see it.

I would love to work on things that make sense like stabilising the system and all, but I work on whatever sells or whatever the EM/PM wants. These days unfortunately, shipping >>> fixing.

replies(5): >>43619239 #>>43619260 #>>43619299 #>>43622268 #>>43626631 #
vanschelven ◴[] No.43619260[source]
If you're temporarily in a "let's ship before the deadline" mode, sure.

And if you're _always_ in deadline mode, I'd argue you have a bigger problem.

replies(1): >>43636157 #
1. mrguyorama ◴[] No.43636157[source]
And yet it's called a "Sprint"