3 ms·

> Rather than worrying about whether they can do this, you should be wondering, "Where did I screw up that relationship?" Yeah, well, the OP might have screwed

> Rather than worrying about whether they can do this, you should be wondering, "Where did I screw up that relationship?" Yeah, well, the OP might have screwed it up, or K might have successfully backstabbed the OP. Offering the back end team one's own team members is a selfless act. I'll wager it's not the only way that the OP has demonstrated a commitment to the success of the project. A healthy organization recognizes such a commitment and rewards it with increased influence at the very least (ideally, with increased compensation as well). This is not a healthy organization, and the OP can't fix it. It's time to leave.

Jemaclus 11y ago
That may be true, but self-reflection is a win/win scenario. You can always make a situation better, even if you can't fix it. OP should definitely leave the job, but the GP is correct in that he shouldn't just say "It's K's fault" and leave it at that. The question to ask yourself is: if I ever get into this situation again, what will I do differently to effect a different outcome?
- gardnr 11y ago
  So true. I find this to be the case with all bad experiences in life, not just professional ones. It's easy to place blame and rationalize how it's not your fault. Playing through scenarios of how you could have single handedly altered the course is a great learning exercise. It's too late for this project and it is time to set it down as gracefully as possible and walk away, but it's never to late to learn how to do better in the future.
- helplessdev 11y ago
  Thank you. I agree. There is not a doubt in my mind that I could have done certain things better, and I certainly do not deny that. I still have a lot to learn.
FennNaten 11y ago
Playing the devil's advocate a bit and getting into K's shoes, I could argue that: "those front-end devs that were 'forcefully' assigned to me didn't climb the learning curve fast enough and have wasted a lot of time getting up to speed on the backend technology, while pushing bad commits that initial backend team had to fix. You know, as I already stated and as I know from experience, and you should have listened to me, throwing more people in on a late software project only adds delay. So, in fact, it wasn't a selfless act, front-end lacked work to do and just pushed their devs onto us to swallow our billable hours without touching theirs, that was sabotage, if not just incompetence." etc. Note, that's not at all what I think, but if I was playing a politics game, and if I was a malicious recognized team lead with several successes in my track record, that's what (or some variation) I could tell management to get out and put the blame on OP, the young team lead which has everything to prove. Sure, an org with clueless management unable to assess the situation may not be worth staying in, but things must be kept in perspective, and here we have only one narrative to get an idea of what really happened.

Jemaclus 11y ago

That may be true, but self-reflection is a win/win scenario. You can always make a situation better, even if you can't fix it. OP should definitely leave the job, but the GP is correct in that he shouldn't just say "It's K's fault" and leave it at that. The question to ask yourself is: if I ever get into this situation again, what will I do differently to effect a different outcome?

gardnr 11y ago
So true. I find this to be the case with all bad experiences in life, not just professional ones. It's easy to place blame and rationalize how it's not your fault. Playing through scenarios of how you could have single handedly altered the course is a great learning exercise. It's too late for this project and it is time to set it down as gracefully as possible and walk away, but it's never to late to learn how to do better in the future.
helplessdev 11y ago
Thank you. I agree. There is not a doubt in my mind that I could have done certain things better, and I certainly do not deny that. I still have a lot to learn.

FennNaten 11y ago

Playing the devil's advocate a bit and getting into K's shoes, I could argue that: "those front-end devs that were 'forcefully' assigned to me didn't climb the learning curve fast enough and have wasted a lot of time getting up to speed on the backend technology, while pushing bad commits that initial backend team had to fix. You know, as I already stated and as I know from experience, and you should have listened to me, throwing more people in on a late software project only adds delay. So, in fact, it wasn't a selfless act, front-end lacked work to do and just pushed their devs onto us to swallow our billable hours without touching theirs, that was sabotage, if not just incompetence." etc. Note, that's not at all what I think, but if I was playing a politics game, and if I was a malicious recognized team lead with several successes in my track record, that's what (or some variation) I could tell management to get out and put the blame on OP, the young team lead which has everything to prove. Sure, an org with clueless management unable to assess the situation may not be worth staying in, but things must be kept in perspective, and here we have only one narrative to get an idea of what really happened.