Related Posts
Bowl Leader
Any openings for health care professionals?
Anyone else pace while taking calls?
Enthusiast
Enthusiast
yeah my pain
Additional Posts in Tech
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Reviewing code from multiple resources tends to mean a step up in responsibility, as opposed to being a truly individual contributor. Not sure what you mean by fixing bugs - why are you fixing other’s bugs?
I followed the same path of software e -> senior dev (reviewing code) -> architect/manager. I think what you’re describing is a pretty normal transition along that path.
If you were fixing trivial bugs that other people could just as easily fix, that's a step down. If you're the guy they call when somebody else can't fix a bug, that's a step up.
Yes, as a technical lead, I reviewed code before system releases so the bugs wouldn’t happen. Are you actually troubleshooting? If so, unless those bugs or issues are assigned to you, why do you troubleshoot? The developer responsible should be doing it or in agile world, you can volunteer to fix open bugs to close a sprint.
Slightly unstructured right now but I hop on a call to help or just volunteer to help us I get pinged. Also not a technical lead.
Yes, in fixing bugs hell. I've brought it up before and if it doesn't change I'm moving on. It's not the job I'm being paid to do.
I've been in a situation that's similar where I got stuck on things that should have been siphoned off to other people. I did have to bring it up, but I presented it as affected my productivity/the project flow and what I'd be able to work on otherwise. It sort of depends on what size and maturity your company is to. I know at a lot of startups, especially if they don't have everything totally together yet, people get stuck with weird hats.