We don’t share enough of our experiences as technical leaders.
That’s why our fate is to continue making the mistakes others already did because we won't learn from each other if we don’t share our mistakes and our learnings.
One of the main reasons I started this newsletter is to share with others those learnings I had during my journey as a developer and later on as a technical leader.
I have been writing Aleix’s learnings for more than two years already, and the posts that I got more traffic from and people reached me for advice are about:
Engineering Strategy
Team Topologies in practice
Lucky me, two topics that I enjoy a lot and I’m passionate about.
Indeed, I started an awesome list about engineering strategy and it has been growing constantly overtime, showing me that there’s a continuous need to learn from others how to do good engineering strategy.
Recetly, Will Larson made a post called “Solving the Engineering Strategy crisis”. Larson is a person that I learned a lot about Engineering Stategy from him via his books and posts.
I have been able to adapt those materials based on my experience and other methodologies and disciplines such as Domain-Driven Design and Wardley Mapping to design and execute engineering strategies with my own style and approach.
Today, I start a new post series on engineering strategy on my full journey during Creditas, starting as Engineering Manager with 0 engineers to Head of Engineering with 6 teams and 40 engineers.
I hope you can learn from different scenarious we went though and adapt them to your own context.
Of course, I will create a story that will show the point of our decisions and the context at hand without sharing confidential information.
If you want to join me on the journey of sharing your experiences as technical leader, reach me at [email protected] and we will find out how to share those learnings!
I hope all the best in your engineering strategy journey! See you next week with the first post. :)
