It's live! Thanks to @jessicraige and the team at @firstround for all their work on this, and my colleagues at Nitid for their support. If you've made a similar career transition, I'd love to hear your story and feedback.
After a legendary run leading engineering teams at Amazon, Twitter and eero, @dloft traded in his mantle to take on a role as a developer — and manager of none.
Over a year in, he’s found the experience equal parts challenging, humbling and rewarding.
Some years back on The Review, he shared a 90-day plan to help engineers step into management. Now, he’s put together a guide for the flip side: pivoting back to IC. He has advice for navigating each step of the transition, from advocating for an equal level to dusting off rusty coding skills to settling back into the maker schedule.
@MitashaSingh Thanks so much, Mitasha. Building processes that work fairly for people across the full spectrum of confidence and assertiveness is an unsolved problem. And another reason why great managers matter.
Working on a followup article to "This 90-Day Plan turns Engineers into Remarkable Managers" about the flip side -- giving up management and going back to being an engineer. Anyone who's done this have advice to share? https://t.co/rCZEElgC5c
It’s a common question from ICs: How do I know if I’m ready to manage? “You’re ready if you understand from the beginning that you’re going to be managing in three directions,” says @dloft.
-Your team
-Your peers
-Your manager
https://t.co/E5tiaEtY2v
Just listened to the first episode of #TechnicallyOptimistic by @raffi -- really well done! A great primer on the past, present, and future of AI / IA.
@a_a Love this. Any suggestions for how to get better at reading code besides just spending more time on it? Perhaps shadowing code reviews by more senior engineers?