Software English

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.

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. 

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.

This audiobook is a summary of the advice I’ve given to software engineers over the years–and then some more. This audiobook follows the structure of a “typical” career path for a software engineer, from starting out as a fresh-faced software developer, through being a role model senior/lead, all the way to the staff/principle/distinguished level. It summarizes what I’ve learned as a developer and how I’ve approached coaching engineers at different stages of their careers.

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.

Salary surveys worldwide regularly place software architect in the top ten best jobs, yet no real guide exists to help developers become architects. Until now. This updated edition provides a comprehensive overview of software architecture's many aspects, with five new chapters covering the latest insights from the field. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming architecture, governance, data, generative AI, team topologies, and many other topics.

A decade ago, developers built information-sharing software by writing a lot of custom code in a single code base, then adding layers of caching. Now we build information systems: interdependent software and services, data platforms, and event streams. Many of our software-to-systems initiatives fail, though, and when they do, we double down on traditional linear approaches. But linear thinking cannot resolve systems challenges. We need to shift to systems thinking.

Every SaaS company on earth is careening towards its next revenue plateau. It’s called a Growth Ceiling—a moment in time where growth stops, and you’re losing just as many customers as you’re bringing in. It’s not an opinion—it’s just how recurring revenue businesses work.

Success isn’t a clear road for software developers. There’s too much information, and it can feel overwhelming. Many developers get stuck and have no idea what to do next. Soft Skills aims to solve this. To give you a clear path with actionable steps for your career (and life). So you can get back to what you enjoy doing...solving unique puzzles and fun problems.

Master software architecture and tame tangled legacy code by aligning your development team with real business needs. Follow a struggling cross-functional team at a fictional logistics company as they transform late projects and fragile systems into clean, evolving models. Perfect for your...

Software startups make global headlines every day. As technology companies succeed and grow, so do their engineering departments. In your career, you'll may suddenly get the opportunity to lead teams: to become a manager. But this is often uncharted territory. How can you decide whether this career move is right for you? And if you do, what do you need to learn to succeed? Where do you start? How do you know that you're doing it right? What does "it" even mean? And isn't management a dirty word? This book will share the secrets you need to know to manage engineers successfully.

Author Andrew Harmel-Law shows you how architects and development teams can collaborate to create and evolve more efficient architectures for their systems. Techniques in this book will help you learn how to create a mindset that allows everyone to practice architecture and build the best systems they've ever experienced.

Technical knowledge alone isn't enough - increase your software development income by leveling up your soft skills Early in his software developer career, John Sonmez discovered that technical knowledge alone isn't enough to break through to the next income level - developers need "soft skills" like the ability to learn new technologies just in time, communicate clearly with management and consulting clients, negotiate a fair hourly rate, and unite teammates and coworkers in working toward a common goal.

The software engineering landscape is constantly evolving, and the demands on engineers intensify with each technological and methodological shift. In such an environment, being a good coder isn't enough—true effectiveness goes beyond technical skills. This book is designed as a guide for...

Learn how to master Agile software development practices. This book teaches you how you can adopt Agile development practices into your organization the right way.

Written by an expert who has created systems ranging from DNA scanners to children's toys, this book is ideal for intermediate and experienced programmers, no matter what platform you use. This expanded second edition includes new chapters on IoT and networked sensors, motors and movement, debugging, data handling strategies, and more.

Engineering isn’t broken because people stopped caring. It’s broken because product thinking got lost. In a world where shipping is fast but impact is rare, Product Driven offers a new model for engineering leadership. One built on outcomes, not output. If you’ve ever led a software team and wondered why the work feels disconnected, why your best engineers start coasting, or why everything still flows through you no matter how senior your team gets, this book is your roadmap out.

Grokking Simplicity is a friendly, practical guide that will change the way you approach software design and development. Distributed across servers, difficult to test, and resistant to modification - modern software is complex. Grokking Simplicity is a friendly, practical guide that will change the way you approach software design and development. It introduces a unique approach to functional programming that explains why certain features of software are prone to complexity, and teaches you the functional techniques you can use to simplify these systems.

The book explains what it takes to build and manage partner channels in the software industry. The book uses the business model framework introduced by Alexander Osterwalder. It provides a practical guide for organizing the activities required to design productive partner programs as well as implement these programs for the recruitment and management of partners that will find, win, make, keep, and grow happy customers on our behalf.

What if your technology organization stopped defending its cost and started proving its value? Profitable Engineering is a leadership book grounded in the realities of software delivery. It examines the organizational system behind engineering performance: how work is funded, prioritized, structured, measured, and led, and why those decisions often matter more than the framework teams follow. Most software organizations do not struggle because their people lack talent or because they chose the wrong methodology.