Playing the devil&#x27;s advocate a bit and getting into K&#x27;s shoes, I could argue that:<p>&quot;those front-end devs that were &#x27;forcefully&#x27; assigned to me didn&#x27;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.<p>So, in fact, it wasn&#x27;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.&quot; etc.<p>Note, that&#x27;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&#x27;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.<p>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.