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.

Managing people is difficult wherever you work. But in the tech industry, where management is also a technical discipline, the learning curve can be brutal - especially when there are few tools, texts, and frameworks to help you. In this practical guide, author Camille Fournier (tech lead turned CTO) takes you through each stage in the journey from engineer to technical manager.

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.

Having managed dozens of teams spanning tens to hundreds of people, Julie Zhuo knows the most important lesson of all: Great managers are made, not born. The Making of a Manager is a modern field guide packed with everyday examples and transformative insights you need to be the kind of manager you wish you had.

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.

Scaling People is a practical and empathetic guide to being an effective leader and manager in a high-growth environment. The tactical information it puts forward—including guidance on crafting foundational documents, strategic and financial planning, hiring and team development, and feedback and performance mechanisms—can be applied to companies of any size, in any industry.

The essential skill of creating and maintaining new businesses - the art of the entrepreneur - can be summed up in a single word: managing. In High Output Management, Andrew S. Grove, former chairman and CEO (and employee number three) of Intel, shares his perspective on how to build and run a company. Born of Grove’s experiences at one of America’s leading technology companies, this legendary management book is a Silicon Valley staple, equally appropriate for sales managers, accountants, consultants, and teachers, as well as CEOs and start-up founders.

Bill, an IT manager at Parts Unlimited, has been tasked with taking on a project critical to the future of the business, code named Phoenix Project. But the project is massively over budget and behind schedule. The CEO demands Bill must fix the mess in 90 days, or else Bill’s entire department will be outsourced. With the help of a prospective board member and his mysterious philosophy of the Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined.

Developing and implementing a strategy is the central task of a leader. A good strategy is a specific and coherent response to - and approach for - overcoming the obstacles to progress. A good strategy works by harnessing and applying power where it will have the greatest effect. Yet, Rumelt shows that there has been a growing and unfortunate tendency to equate Mom-and-apple-pie values, fluffy packages of buzzwords, motivational slogans, and financial goals with “strategy”.

How can we apply technology to drive business value? For years we've been told that the performance of software delivery teams doesn't matter - that it can't provide a competitive advantage to our companies. Through four years of groundbreaking research to include data collected from the State of DevOps reports conducted with Puppet, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance - and what drives it - using rigorous statistical methods. This book presents both the findings and the science behind that research, making the information accessible for listeners to apply in their own organizations.

Listen to hilarious stories with serious lessons that Michael Lopp extracts from his varied and sometimes bizarre experiences as a manager at Apple, Pinterest, Palantir, Netscape, Symantec, Slack, and Borland. Many of the stories first appeared in primitive form in Lopp’s perennially popular blog, Rands in Repose. The third edition of Managing Humans contains a whole new season of episodes from the ongoing saga of Lopp's adventures in Silicon Valley, together with classic episodes remastered for high fidelity and freshness.

Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity. In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help listeners choose and evolve the right team patterns for their organization.

Dave Thomas and Andy Hunt wrote the first edition of this influential book in 1999 to help their clients create better software and rediscover the joy of coding. These lessons have helped a generation of programmers examine the very essence of software development. Now, 20 years later, this new edition re-examines what it means to be a modern programmer. Topics range from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse.

Tony Fadell led the teams that created the iPod, iPhone and Nest Learning Thermostat and learned enough in 30+ years in Silicon Valley about leadership, design, startups, Apple, Google, decision-making, mentorship, devastating failure and unbelievable success to fill an encyclopedia.

In The Unicorn Project, we follow Maxine, a senior lead developer and architect, as she is exiled to the Phoenix Project, to the horror of her friends and colleagues, as punishment for contributing to a payroll outage. She tries to survive in what feels like a heartless and uncaring bureaucracy and to work within a system where no one can get anything done without endless committees, paperwork, and approvals. One day, she is approached by a ragtag bunch of misfits who say they want to overthrow the existing order, to liberate developers, to bring joy back to technology work.

After two decades in the trenches of helping companies design and build better, more efficient operations, Karen Martin has pinpointed why performance improvement programs usually fail: Chaos, the sneaky but powerful force that frustrates customers, keeps business leaders awake at night, and saps company morale. In The Outstanding Organization, Karen offers a toolbox for combating chaos by creating the organizational conditions that will allow your improvement efforts to return greater gains.

The race is on to become a digital enterprise. Every organization has a plan for updating products, technologies, and business processes. But that's not enough anymore. With disruptive startups outperforming industry stalwarts, executives everywhere are pushing greater growth and innovation. Staying competitive demands a complete digital transformation.

Through her global consulting projects, keynote speeches, and work with thousands of leaders, Karen has seen first-hand how a pervasive lack of clarity strangles business performance and erodes employee engagement. Ambiguity is the corporate default state, a condition so prevalent that “tolerance for ambiguity” has become a clichéd job requirement. It doesn’t have to be this way.

It's when you're stuck in the day-to-day, putting out fires and cleaning up messes, that passion turns to frustration. Freedom seems somewhere between elusive and impossible. The secret to getting unstuck is process. This inspiring, informative field guide will prove it's possible to establish rigor and discipline for process while also increasing creativity, flexibility, and innovation. Process! will help you identify a handful of core processes that make your business uniquely valuable.

4DX® is not theory. It is a proven set of practices that represents a new way of thinking essential to thriving in today’s competitive climate, making this 2nd edition a book that no business leader can afford to miss. The 4 Disciplines of Execution (4DX) is a simple, repeatable, and proven formula for executing your most important strategic priorities in the midst of the whirlwind. By following the 4 Disciplines, leaders can produce breakthrough results, even when executing the strategy requires a significant change in behavior from their teams.

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.

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."

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.

Managing people is difficult wherever you work. But in the tech industry, where management is also a technical discipline, the learning curve can be brutal - especially when there are few tools, texts, and frameworks to help you. In this practical guide, author Camille Fournier (tech lead turned CTO) takes you through each stage in the journey from engineer to technical manager.

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.

Over the past five decades, the tech industry has grown into one of the most important sectors of the global economy, and Silicon Valley - replete with sprawling office parks, sky-high rents, and countless self-made millionaires - is home to many of its key players. But the origins of Silicon Valley and the tech sector are much humbler. At a time when tech companies’ influence continues to grow, The Big Score chronicles how they began.

Over a 60-year career in public affairs, Vannevar Bush—engineer, inventor, educator, and public face of government-funded science—sought to eliminate roadblocks to innovation in science and technology. In Pieces of the Action, a collection of memoir-essays, he reflects on his role in shaping the policies and organizations that powered American research and development in the mid-20th century.

Tap into the wisdom of experts to learn what every engineering manager should know. With ninety-seven short and extremely useful tips for engineering managers, you'll discover new approaches to old problems, pick up road-tested best practices, and hone your management skills through sound advice.

How can we apply technology to drive business value? For years we've been told that the performance of software delivery teams doesn't matter - that it can't provide a competitive advantage to our companies. Through four years of groundbreaking research to include data collected from the State of DevOps reports conducted with Puppet, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance - and what drives it - using rigorous statistical methods. This book presents both the findings and the science behind that research, making the information accessible for listeners to apply in their own organizations.

There are no easy decisions in software architecture. Instead, there are many hard parts—difficult problems or issues with no best practices—that force you to choose among various compromises. With this book, you'll learn how to think critically about the trade-offs involved with distributed architectures. Architecture veterans and practicing consultants Neal Ford, Mark Richards, Pramod Sadalage, and Zhamak Dehghani discuss strategies for choosing an appropriate architecture.

So rich was the scientific harvest of the early 20th century that it transformed entire industries and economies. Max Planck laid the foundation for quantum physics, Barbara McClintock for modern genetics, Linus Pauling for chemistry - the list goes on. In the 1970s, the nature of scientific work started to change.

How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization.

In the years following her role as the lead author of the international best seller, Limits to Growth - the first book to show the consequences of unchecked growth on a finite planet - Donella Meadows remained a pioneer of environmental and social analysis until her untimely death in 2001. Thinking in Systems is a concise and crucial book offering insight for problem-solving on scales ranging from the personal to the global. Edited by the Sustainability Institute's Diana Wright, this essential primer brings systems thinking out of the realm of computers and equations and into the tangible world....

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.

Few books on software project management have been as influential and timeless as The Mythical Man-Month. With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system.