Since you say you are recently a new team lead, I'd like to share something's I'd like my manager to know:
I'f I'm not committing code daily, somethings wrong. It would mean the world to me to proactively ask me if something happened. (maybe support is too high or I have a blocker that I don't know how to solve.)
Probably should ask for help more, but after asking for help once and still not solving it I tend to get frustrated (which leads back to point 1), especially if the documentation isn't easy to find or doesn't exist.
DON'T skip a 1-on-1 if there's nothing "important" to talk about, maybe if it's not work related, you now have 30 minutes to learn more about each other.
I wished my managers would do pair programming with me.
Take my code reviews to the upmost highest standard. Not truly understanding the code and approving since it solves the issue doesn't encourage me to write clean code.
Anyways, albeit unrequested I hope maybe on of these might be useful :)
Good luck in your new role as team lead!
(Curious, does your team know you make posts like these?)
Awww, seriously?! I am trying my best, but there is soooo much to learn. So that's a huge compliment for me. Thank you so much! :))
That right there is what sets you apart. Thanks for setting a great example!
Thank you, Chris:)
Since you say you are recently a new team lead, I'd like to share something's I'd like my manager to know:
Anyways, albeit unrequested I hope maybe on of these might be useful :)
Good luck in your new role as team lead!
(Curious, does your team know you make posts like these?)
Good tips, Enrique! Thank you for adding them. It's actually a good idea to "crowdsource a portrait of an ideal manager" :).
Hm, I didn't tell my team about this one. But I think I'll ask them if I hit all the points:).
And here you go: the crowdsourcing post.
dev.to/ice_lenor/crowdsourcing-a-p...