I’ll share key insights and essential strategies that will help you navigate the thrilling but challenging transition to tech lead seamlessly.
New to leading or managing? Here's a list of great books on leadership recommended by leaders at Atomic Object.
I recently participated in the Magnify program, which presented an approach to assessing and building a thriving environment.
In the last two years, I’ve been part of a much larger team, on a single project, operating as a tech lead.
In the end, if you ensured that the problem was addressed, you were a good leader, no matter how you did it.
The most successful startup founders focus on the right things: the problem, the market, and past patterns of success.
Writing a mini-project doesn’t have to be time-consuming; the goal is to delegate and let someone else run with it.
While it's not the developer's job to remove the cognitive load from the Lead, it is greatly appreciated when the developer helps lighten it.
It’s common knowledge that teaching something is a great way to reinforce your own understanding of it. That definitely has held true for me.
The uncomfortable part of change is inevitable. My advice won't make that discomfort go away, but I do believe some practices can make it manageable.
Software teams encounter new challenges across people and technology. That means the development of project and team leaders is more critical than ever.
Delivery leads are the client’s proxy, and we often create value in ways that other roles on the team, like project manager, don’t fulfill.