First of all, congratulations for the article.
The good thing about sharing experiences is that it's uncontestable. There's no right or wrong, but only what you lived in your career.
It makes the discussion open on top of the subject and not a war of opinions related to a mindset.
I don't have anything to add related to leadership. Today it's evident that during my career, I had fewer leaders than bosses, which serves me as inspiration to improve my leadership skills every day.
Two points that in my experience were different are the fact that in my opinion, tech leaders are usually responsible for making proof of concepts/spikes and also share their knowledge with the team.
It's tough to manage the time to code and take care of all other responsibilities, but it's a way to continue evolving as a developer and also getting involved with the teamwork.
The second is that it's tough to separate technical management and product management. Tech Leaders and Product managers must be entirely aligned, so all nonfunctional requisites are mapped, and the priorities and expectations shared with the whole team.
I agree that the tech leader doesn't necessarily need to be involved in all code decisions, like being a bottleneck on the Code Review phase. Regularly, they must evaluate the code to get a sense of how things are going and how the team can improve its quality.
As it's the first article, I guess there is much more to come, and I'm excited to read it.
Thank you for sharing it with us.