Introduction
When it comes to growth in our careers, the best outcomes come from having a deliberate plan. In 2025, I’ve decided to take a strategic, question-first approach to my learning. Instead of chasing trends or trying to consume as much content as possible, I’ve outlined the core questions I’m currently wrestling with in this stage of my career. These questions represent the gaps in my knowledge and the areas where I want to see the most growth.
With this approach, I’ve selected the best books from my reading list to help guide me in answering these questions. This post will walk you through my plan, how I’ve structured it, and why these topics matter to me—and potentially to you if you’re on a similar journey in software development or technical leadership.
If you're looking for strategies on how to become a better software engineer, enhance your technical leadership skills, or master modern software development methodologies, this post might resonate with you.
The Strategy Behind the Plan
Before diving into the specific areas I’m focusing on, let me explain the strategy behind this learning plan. I structured my plan around questions, not topics. Each question reflects a real challenge or curiosity I’ve encountered in my day-to-day work. By starting with questions, I’ve ensured that my learning will be focused, actionable, and directly relevant to my career.
To answer these questions, I’ve paired each one with a book or resource that I believe offers the best insight into solving that particular problem. My plan spans two broad areas:
Technical Leadership: As a relatively new Tech Lead, I’m seeking to become more effective in leading teams and delivering value. Software Development: Staying hands-on with technical skills is critical for me. I want to deepen my understanding of programming concepts and practices. Finally, I’ve added a bonus goal to master TypeScript and learn a new programming language, ideally a functional one. I believe continuous exploration of tools and paradigms is key to understanding how to become a senior software engineer and beyond.
Let’s dive into the specifics.
Technical Leadership: From Questions to Mastery
1. When Will It Be Done? Agile Forecasting
One of the biggest challenges I’ve faced as a Tech Lead is dealing with estimates. Honestly, I hate them. Estimates are often wrong, create unnecessary pressure, and can derail a team’s focus. Yet, stakeholders want to know: When will it be done?
A growing movement in the Agile community argues that we can live without estimates. While this makes sense on a weekly or sprint level (especially in agile software development with Scrum), I struggle with understanding how to create a roadmap without relying on estimates.
To tackle this, I’ve chosen “When Will It Be Done? Agile Forecasting” as my guide. This book delves into probabilistic forecasting, an approach that replaces traditional estimates with data-driven predictions. By learning this method, I aim to improve how I communicate timelines and build trust with stakeholders—without sacrificing the team’s focus on delivering value.
2. Peopleware
Building a productive team is hard, and it’s even harder to do so without losing effectiveness. As a Tech Lead, I want to foster a culture where people can do their best work, but I also need to balance individual productivity with the team’s overall performance.
The classic book “Peopleware” is my go-to resource for this challenge. It explores the human aspects of software development and offers timeless advice on creating an environment where teams can thrive. From minimizing distractions to cultivating trust, I’m looking forward to applying these lessons to create a team culture that prioritizes collaboration, innovation, and well-being.
This aligns with my broader goal of understanding how to become a great software engineer, not just individually, but as a leader who enables others to succeed.
3. Talking with Tech Leads
Being new to technical leadership, I often wonder: What am I missing? There’s so much to learn, and I believe one of the best ways to grow is by learning from others who’ve walked this path before me.
That’s why I’m turning to “Talking with Tech Leads”, a book that captures the experiences and lessons of real Tech Leads from various industries. Through their stories, I hope to gain insights into the challenges and triumphs of technical leadership, as well as practical advice I can apply to my role.
This book represents a critical step in my journey to how to become a better software engineer—not just through technical skills, but through leadership and mentorship.
Software Development: Expanding Technical Excellence
4. Trunk-Based Development
As teams scale, managing work-in-progress becomes a major challenge. One of the techniques I’ve been exploring is Trunk-Based Development—a version control strategy that emphasizes frequent integration to reduce the risk of merge conflicts and stale branches.
However, I’m still looking for more techniques to hide work in progress effectively while adhering to this approach. My goal is to master Trunk-Based Development in 2025 and understand how to balance short-term productivity with long-term maintainability.
This focus is part of my commitment to mastering software development methodologies and staying on the cutting edge of modern practices. For this reason, I plan to study the main book about this practice: "Trunk-Based Development And Branch By Abstraction".
5. From Objects to Functions
In recent years, I’ve become increasingly interested in mixing Object-Oriented Programming (OOP) and Functional Programming (FP) principles—especially in TypeScript. I believe combining these paradigms can lead to cleaner, more expressive code. But how do I get better at functional programming?
The book “From Objects to Functions” is my roadmap. It explores the transition from OOP to FP, helping developers adopt functional principles without abandoning everything they’ve learned in OOP. Through this book, I aim to improve my functional programming skills and apply them effectively in TypeScript.
Learning functional programming is also part of my long-term goal to explore how to become better software engineer and expand my problem-solving toolbox.
6. Technical Agile Coaching with the Samman Method
As a Tech Lead, one of my responsibilities is to coach the team on technical skills. But how do you coach effectively without micromanaging?
I’ve decided to dive into “Technical Agile Coaching with the Samman Method”, a book that outlines a hands-on, collaborative approach to coaching. By using techniques like ensemble programming (formerly known as mob programming), I hope to create an environment where the team learns together and grows collectively.
This aligns with my goal of fostering a culture of continuous learning and improvement, a key component of how to become a good software engineer and build high-performing teams.
Bonus Goals: Master TypeScript and Learn a New Language
In addition to the six main areas above, I have two bonus goals for 2025:
-
Master TypeScript: As my primary programming language, I want to deepen my expertise in TypeScript, focusing on advanced features and best practices. This will help me write more robust and maintainable code.
-
Learn a New Programming Language: I’m considering a functional programming language like Clojure or Haskell. Exploring a new language will not only broaden my technical skills but also give me fresh perspectives on problem-solving and design.
By pursuing these goals, I hope to continue my journey toward how to become a senior software engineer and stay adaptable in an ever-changing industry.
Closing Thoughts
My learning plan for 2025 is more than just a list of books—it’s a strategy for growth. By focusing on the key questions I’m grappling with and pairing them with the best resources, I’ve created a roadmap that’s both targeted and actionable.
Whether you’re looking to enhance your technical skills, step into a leadership role, or explore new software development methodologies, I encourage you to take a similar approach. Start with the questions that matter most to you, and let them guide your learning journey.
Here’s to a year of growth, discovery, and continuous improvement!
Happy learning, and let’s make 2025 the year we all become better software engineers—together.