Software Engineering Daily

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.

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.

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.

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.

Want to know the secret to becoming an expert software engineer and getting any job you want? The answer is simple: experience. In this book, I will show you the system I use to design, develop, and deliver open source software; steer you away from the mistakes I’ve made along the way; and help you build an impressive résumé of projects that’ll get you that job you’ve always wanted, and in time, will earn you the right to call yourself an expert.

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.

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.

What happens when resources become scarce and society starts to crumble? Soft Apocalypse follows the journey across the Southeast of a tribe of formerly middle-class Americans as they struggle to find a place for themselves and their children in a new, dangerous world that still carries the ghostly echoes of their previous lives.

Effective Software Testing teaches you a systematic approach to software testing that will ensure the quality of your code. It’s full of techniques drawn from proven research in software engineering, and each chapter puts a new technique into practice. Follow the real-world use cases and detailed code samples, and you’ll soon be engineering tests that find bugs in edge cases and parts of code you’d never think of testing! Along the way, you’ll develop an intuition for testing that can save years of learning by trial and error.

Starting a career as a software engineer without a computer science degree is a long and difficult journey, Hasan Armstrong discovered this whilst attempting to switch from a career in healthcare to software engineering. He now works as a software engineer and incorporates all the lessons he has learnt in this book. This book will provide a road map to getting a job as a software engineer without a computer science degree, as well as providing solutions to the obstacles you may face along the way.

A complete guide on how to get your first programming job from a hiring manager, even if you are changing careers, a transitioning military veteran, don't have a degree, or want to make more money. I made a career switch from sales and with no coding experience to becoming a software engineer (with no degree) and am now a senior software engineering manager (hiring manager) at the largest tech company in the world leading teams of dozens of engineers. This is how I did it.

The audiobook is focused on providing the listeners with a precise and concise understanding of what agile methodology is, how software testing is done under it and the key points by which a software professional can succeed in such work environments. As the goal of this audiobook is to quickly provide information to the listeners about the respective topics covered, the very intrinsic details of the respective topics are only covered to some extent.