10
iceb
1y

Dang. I feel like I'm just not cut out to climb any ladder.

When we discovered a production bug. I feel bad about making people working on that part look bad by not catching it.

My manager has no issue with pointing out that I should have caught it. Beating a horse while it's down.

I mean no shit. Of course I know I should've caught it. How does making me feel worse about it help.

Feels like I'll always be in a tough spot no matter where I am on the ladder.

Or I'm just fragile. I acknowledge that, too

Comments
  • 9
    No, fingerpointing is bad practice.
    Your manager could've reacted way differently, stating that the team (you included) didn't catch it and will make sure, it gets resolved soon.

    Don't feel bad about it, shit happens.
  • 5
    Literally bugs are bugs because they crawl in unseen and are hard to catch.

    I've made my share of dumb mistakes despite my 7+ years of experience. And then a colleague needs to deal with it, because that's just how we rotate. So what, I learn from it and be on the lookout for similar patterns next time. No point blaming anyone, the entire Software world experience bugs all the time
  • 3
    It's a management problem if all responsibility is on one person.
  • 3
    Accept not being error free.

    The correct answer to that manager pointing out that you should have catched the bug is: No shit, Sherlock!
  • 1
    I mean that's what we all agree with. but isn't bosses like this more common and the good ones rare?
  • 3
    @iceb

    Not so that they are rare, but good bosses usually lead to low turnover so it's harder for people in a job hunt to land a spot since there are few vacancies.
  • 1
    you're ok. sounds like you care very much and that's good enough.

    don't take your manager personally.
  • 1
    I haven’t had a manager that does any finger pointing for a specific bug.
    It’s usually like: "hey team we’ve noticed an increase of bugs lately. What can we do to improve ourselves? More testing, less rushing it? etc." It’s a pretty healthy approach
  • 1
    Mandatory Code Reviews really help with the idea that a bug is never just the fault of a single person.

    But of course this isn't possible in a team where everyone is doing solo work on their own thing

    My team's motto is "if we find a problem we never call out a person. If we celebrate success we applaude a person"

    but that wouldn't be believable if everyone could merge to master without anyone having laid eyes on the core.
Add Comment