Software Engineer Career

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.

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. 

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.

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.

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.

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.

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.

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.

The vast majority of writers begin the storytelling process with only a partial understanding of where to begin. Some labor their entire lives without ever learning that successful stories are as dependent upon good engineering as they are artistry. But the truth is, unless you are master of the form, function, and criteria of successful storytelling, sitting down and pounding out a first draft without planning is an ineffective way to begin. Story Engineering starts with the criteria and the architecture of storytelling, the engineering and design of a story....

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?

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. 

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