Hey 👋 this is Luca! Welcome to a 🔒 weekly edition 🔒 of Refactoring.

Every week I write advice on how to become a better engineering leader, backed by my own experience, research and case studies.

You can learn more about Refactoring here.

To receive all the full articles and support Refactoring, consider subscribing 👇

Become a better tech leader ✨

As a founder and CTO, I have seen my company grow from when I used to write all the code, to the point I wrote almost none.

I have also had frequent conversations with other founders and peers about how much tech leaders should still be coding, or anyway stay technically involved.

My take is: it's very important to stay technical, but it's not trivial to find an effective way to do so.

If you do it the right way — your skills become an asset that improves your decision making and makes your team more effective.
If you do it the wrong way — your involvement actually slows down your team, undermines trust and creates resentment in the long run.

So let's try to figure this out 👇

Refactoring

Staying Technical as an Engineering Leader 👔

Comments on this post are for paid subscribers