3 ms·

> thus I'm often stuck with OOP messes. Where I'm usually "superstar" (sorry for shitty expression) in team. Maybe this is your problem. You should try not to

by rb808 9y ago

> thus I'm often stuck with OOP messes. Where I'm usually "superstar" (sorry for shitty expression) in team. Maybe this is your problem. You should try not to be the team hero. Stick to your little part of the app, do a good job and go home early. If the rest of the team is screwing up - it isn't your job to fix.

scalatohaskell 9y ago
problem is, it is (will be) my problem to fix. I don't want to be hero, but I will get assigned to those places to fix it up. Because it worked before, and managers were happy with my work before.
- rb808 9y ago
  It sounds like you need to learn to say no- or at least negotiate what you work on. If you hate it so much tell your boss - they'd prefer you happy and working on something else rather than quitting.
  - scalatohaskell 9y ago
    that's actually good idea. I never considered negotiating this part. I thought if they pay me... I've been called "programmer-whore" by friends (in joking manner :) ). Because I go in and fullfil wildest manager's dreams for money. Huh. Some truth to it I guess. I hope that expression is not too vurglar to use here... sorry I'm not native English speaker.
    - rb808 9y ago
      Yeah it took me a long while to learn this. If you're doing the work and not complaining managers will think you're happy. If you're working overtime to get this done they'll think you're very happy. If you aren't enjoying it you need to tell them. They aren't mind readers.
- BlackjackCF 9y ago
  I've been there before/see a lot of my friends in that position. It really is a matter of not being able to say no and wanting to swoop in and save stuff. It's not good for you. Ultimately, it creates this terrible mentality at the workplace where you're expected by your manager to come in and save things all the time. This also means that your coworkers don't step up to learn more of the stack and troubleshoot, because they know that they will always have you to fall back on. It might be easier to say no when you reframe things with this perspective. If you never say no, no one else will ever learn, and therefore you will ALWAYS be stuck in this position.
dasmoth 9y ago
Stick to your little part of the app I agree this is good advise when it's feasible, but a lot of the current management trend (collective code ownership, everyone working off a single "backlog", etc.) can make it quite hard to follow.

by rb808 9y ago

scalatohaskell 9y ago

problem is, it is (will be) my problem to fix. I don't want to be hero, but I will get assigned to those places to fix it up. Because it worked before, and managers were happy with my work before.

rb808 9y ago
It sounds like you need to learn to say no- or at least negotiate what you work on. If you hate it so much tell your boss - they'd prefer you happy and working on something else rather than quitting.
- scalatohaskell 9y ago
  that's actually good idea. I never considered negotiating this part. I thought if they pay me... I've been called "programmer-whore" by friends (in joking manner :) ). Because I go in and fullfil wildest manager's dreams for money. Huh. Some truth to it I guess. I hope that expression is not too vurglar to use here... sorry I'm not native English speaker.
  - rb808 9y ago
    Yeah it took me a long while to learn this. If you're doing the work and not complaining managers will think you're happy. If you're working overtime to get this done they'll think you're very happy. If you aren't enjoying it you need to tell them. They aren't mind readers.
BlackjackCF 9y ago
I've been there before/see a lot of my friends in that position. It really is a matter of not being able to say no and wanting to swoop in and save stuff. It's not good for you. Ultimately, it creates this terrible mentality at the workplace where you're expected by your manager to come in and save things all the time. This also means that your coworkers don't step up to learn more of the stack and troubleshoot, because they know that they will always have you to fall back on. It might be easier to say no when you reframe things with this perspective. If you never say no, no one else will ever learn, and therefore you will ALWAYS be stuck in this position.

dasmoth 9y ago

Stick to your little part of the app I agree this is good advise when it's feasible, but a lot of the current management trend (collective code ownership, everyone working off a single "backlog", etc.) can make it quite hard to follow.