Using stories from his time at Netscape, Apple, and Slack, Michael Lopp presents a series of small but compelling practices to help you build leadership skills. You’ll learn how to create teams that are highly productive, highly respected, and highly trusted. The essays in this book examine the practical skills Lopp learned from exceptional leaders - as a manager at Netscape, a senior manager and director at Apple, and an executive at Slack. You’ll learn how to apply these lessons to your own experience.

In this insightful and comprehensive guide, Addy Osmani shares more than a decade of experience working on the Chrome team at Google, uncovering secrets to engineering effectiveness, efficiency, and team success. Engineers and engineering leaders looking to scale their effectiveness and drive transformative results within their teams and organizations will learn the essential principles, tips, and frameworks for building highly effective engineering teams.

This book provides the first comprehensive overview of software architecture’s many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics. Mark Richards and Neal Ford—hands-on practitioners who have taught software architecture classes professionally for years—focus on architecture principles that apply across all technology stacks.

In Modern Software Engineering, continuous delivery pioneer David Farley helps software professionals think about their work more effectively, manage it more successfully, and genuinely improve the quality of their applications, their lives, and the lives of their colleagues.

At most technology companies, you'll reach Senior software engineer, the career level for software engineers, in five to eight years. At the career level, your company's career ladder won't require that you work towards the next promotion; being promoted further is an exception rather than expected. This is also when many engineers are first given an opportunity to move into engineering management.

A lot of Engineering Managers and leaders studied for years and years to become the best Engineer they possibly could be... and then they were promoted. It can be very tough for those of us who didn't go into Engineering with the distinct concept that we would become managers, but still want to do our best to support our teams. I wrote this book because there's so much no one told me about management that I wished I would have known. There's a lot to be purposeful about that many of us learn on the job, and worse: learn on people.

Getting to the good solutions of complex management challenges can make the difference between fulfillment and frustration for teams, and, ultimately, the success or failure of companies. Will Larson's An Elegant Puzzle orients around the particular challenges of engineering management - from sizing teams to technical debt to succession planning - and provides a path to the good solutions.

For years, companies have rewarded their most effective engineers with management positions. But treating management as the default path for an engineer with leadership ability doesn't serve the industry well—or the engineer. The staff engineer's path allows engineers to contribute at a high level as role models, driving big projects, determining technical strategy, and raising everyone's skills. This in-depth book shows you how to understand your role, manage your time, master strategic thinking, and set the standard for technical work.

Tech Leadership is a detailed blueprint for career development in a dynamic industry. If you like empowering others, accomplishing big things, and gaining insights from today’s visionaries, then you’ll love Andrew Swerdlow’s seasoned wisdom and mentorship.

In this book, author Will Larson shows you ways to obtain your first executive job and quickly ramp up to meet the challenges you may not have encountered in non-executive roles: measuring engineering for both engineers and the CEO, company-scoped headcount planning, communicating successfully across a growing organization, and figuring out what people actually mean when they keep asking for a "technology strategy."