Software Development Engineer

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

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.

The battle with the Iron Legion has left The Last Horizon battered and broken, drifting in space. Varic needs an exceptional engineer to fix his ship, and there’s only one person for the job: Mell, the master Aether technician. But first, they have to break her out of prison. Mell has been captured by the Advocates, a group of superpowered vigilantes who dominate their corner of the galaxy. They are led by Starhammer, an invincible champion with a personal obsession with Mell.

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.

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.

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.

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.

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.

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.

1881 - Special Agent Gillian Hamilton is a magic caster with the Federal Bureau of Magic and Steam. He’s sent to Shallow Grave, Arizona, to arrest a madman engineer known as Tinkerer, who’s responsible for blowing up half of Baltimore. Gillian has handled some of the worst criminals in the Bureau’s history, so this assignment shouldn’t be a problem. But even he’s taken aback by a run-in with the country’s most infamous outlaw, Gunner the Deadly.

Is your organization relying on the passive illusion of "assurance" when it desperately requires the rigorous discipline of "engineering"? In Philosophy of Software Quality Engineering, IT/IS architect and veteran engineer Martin J. Lammer delivers a groundbreaking philosophical treatise that dismantles traditional Software Quality Assurance (SQA) paradigms. Rebuilt from the ground up, this text establishes a new foundation based on rigorous engineering, ontology, and pragmatism. The software industry is currently in an epistemological crisis.

Vince and his co-workers were waiting to catch a plane back from their business trip when aliens turned Earth into the setting for a deadly reality show.

Author Brendan Burns demonstrates how you can adapt existing software design patterns for designing and building reliable distributed applications. Systems engineers and application developers will learn how these long-established patterns provide a common language and framework for dramatically increasing the quality of your system. This fully updated second edition includes new chapters on AI inference, AI training, and building robust systems for the real world.

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.

Bridge the gap between writing basic code and landing a high-paying role as a professional software engineer. Perfect for your daily commute, this empowering tech career guide cures imposter syndrome by transforming messy scripts into maintainable, production-ready systems. Stop endlessly...

This audiobook is a highlight reel of content revolving around the software developer's life.

In Understanding Software, Max Kanat-Alexander, Technical Lead for Code Health at Google, shows you how to bring simplicity back to computer programming. Max explains to you why programmers suck, and how to suck less as a programmer. There's just too much complex stuff in the world. Complex stuff can't be used, and it breaks too easily. Complexity is stupid. Simplicity is smart. 

Practical techniques for writing code that is robust, reliable, and easy for team members to understand and adapt. In Good Code, Bad Code you’ll learn how to: Think about code like an effective software engineer, write functions that read like well-structured sentences, ensure code is reliable and bug free, effectively unit test code, identify code that can cause problems and improve it, write code that is reusable and adaptable to new requirements, improve your medium and long-term productivity, and save yourself and your team time.