Software Engineer Career

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.

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.

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.

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

Are you getting interviews but failing to land a job? Are your technical skills sound, but when it comes to the behavioral aspect of the interview, things are falling short? Or maybe you’re fresh out of college but you’re totally unsure of how you can best prepare yourself to land a software engineering job. Regardless of what brought you here, let me say that I’m glad you found this book. Most software engineers have the technical capabilities to land a high-paying software engineering job, but in today’s competitive tech market, companies want to see more than that.

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.

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

At some point in your career, you'll realize there's more to being a software engineer than dealing with code. With more than forty stand-alone stories, Lopp walks through a complete job lifecycle, starting with the interview and ending with the realization that it might be time to move on. You'll learn how to handle baffling circumstances in your job, understand what you want from your career, and discover how to thrive in your workplace.

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.

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.

How did a simple design error cause one of the great disasters of the 1980s - the collapse of the walkways at the Kansas City Hyatt Regency Hotel? What made the graceful and innovative Tacoma Narrows Bridge twist apart in a mild wind in 1940? How did an oversized waterlily inspire the magnificent Crystal Palace, the crowning achievement of Victorian architecture and engineering? These are some of the failures and successes that Henry Petroski, author of the acclaimed The Pencil, examines in this engaging, wonderfully literate book.

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.

Until recently, infrastructure was the backbone of organizations' operating software they developed in-house. But now that cloud vendors run the computers, companies can finally bring the benefits of agile custom-centricity to their own developers. Adding product management to infrastructure organizations is now all the rage. But how's that possible when infrastructure is still the operational layer of the company?

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.

Drawing from his extensive experience in the field, Kunz showcases his own journey from a double major in Marketing and Fine Arts to a renowned sales engineer. His infectious personality and passion for technology have propelled him to build a network of individuals who have risen to executive positions, managing teams of over 150 people worldwide. With his guidance, you, too, can achieve remarkable success!

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.

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.

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.