I went from intern to lead on the same team, first job out of college. (Unheard of practically and frowned upon by a lot but that's not the point). You're spot on. Intern, part time, intro dev, sr dev, was all about churning code faster, cleaner, better, and bigger. I hit lead and BOOM I barely code any more unless I stay late for it but I can't actually own any tickets myself anymore due to time constraints. The rest is just as you said.
1 thing I'd add is learning first hand that teams are air craft carriers not jet skis when it comes to process change. I tried directing their attention to too many places we needed improvement on at once and the fumbled them all. Limiting it to 1 or 2 things until they get it down and then adding 1 or 2 more worked a lot better. I'm talking about things like better code coverage, better sad path testing, resiliency considerations, those kind of things.
Great point. It's tough to change culture and process, especially as a new team lead. Starting with some basic changes that the entire team can understand is a good philosophy.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I went from intern to lead on the same team, first job out of college. (Unheard of practically and frowned upon by a lot but that's not the point). You're spot on. Intern, part time, intro dev, sr dev, was all about churning code faster, cleaner, better, and bigger. I hit lead and BOOM I barely code any more unless I stay late for it but I can't actually own any tickets myself anymore due to time constraints. The rest is just as you said.
1 thing I'd add is learning first hand that teams are air craft carriers not jet skis when it comes to process change. I tried directing their attention to too many places we needed improvement on at once and the fumbled them all. Limiting it to 1 or 2 things until they get it down and then adding 1 or 2 more worked a lot better. I'm talking about things like better code coverage, better sad path testing, resiliency considerations, those kind of things.
Great point. It's tough to change culture and process, especially as a new team lead. Starting with some basic changes that the entire team can understand is a good philosophy.