By Gergely Orosz, the author of The Pragmatic Engineer Newsletter and Building Mobile Apps at Scale
Navigating senior, tech lead, staff and principal positions at tech companies and startups. An Amazon #1 Best Seller. New: the hardcover is out! As is the audibook. Now available in 6 languages.
Here’s a on Korn’s 1998 album Follow the Leader , focusing on its impact, creation, and legacy. When the Freaks Inherited the Earth: Korn’s Follow the Leader and the Day Nu-Metal Took Over August 18, 1998 — The air didn’t just change. It thickened. A low, detuned 7-string growl rolled out of car speakers, mallrat Discmans, and dorm-room stereos. A child’s whisper — “Are you ready?” — gave way to a lurching groove that felt like a panic attack with a backbeat. Then, the scream: “GO!”
Yes. Still. Always. Would you like a track-by-track breakdown, a deeper dive on the recording sessions, or an analysis of its influence on modern metal?
was something else entirely. A haunting bass intro. Davis’s whispered verse. Then the explosive chorus: “Something takes a part of me.” The middle eight broke all rules — Davis scat-singing nonsense syllables, then a guitar break that sounded like a helicopter crash. The animated video (by Todd McFarlane, creator of Spawn ) featured a silver bullet ripping through walls, a metaphor for frustration, abuse, and release. It won a Grammy (Best Short Form Music Video) and became the band’s signature song. The Bite: Why It Mattered Follow the Leader debuted at No. 1 on the Billboard 200, selling over 268,000 copies in its first week — unheard of for a band who once played to 50 people in a Bakersfield VFW hall. It went on to sell 5 million copies in the U.S. alone.
Two years earlier, the five Bakersfield misfits — Jonathan Davis (vocals), James “Munky” Shaffer (guitar), Brian “Head” Welch (guitar), Reginald “Fieldy” Arvizu (bass), and David Silveria (drums) — had released Life Is Peachy , a raw, claustrophobic follow-up to their game-changing 1994 debut. But they were still outsiders. Metal was still dominated by Pantera’s groove-metal swagger, the fading grunge of Stone Temple Pilots, and the rap-rock novelty of Limp Bizkit (whose frontman, Fred Durst, was about to become their unlikely hype man).
The book is separated into six standalone parts, each part covering several chapters:
Parts 1 and 6 apply to all engineering levels: from entry-level software developers to principal or above engineers. Parts 2, 3, 4 and 5 cover increasingly senior engineering levels. These four parts group topics in chapters – such as ones on software engineering, collaboration, getting things done, and so on.
This book is more of a reference book that you can refer back to, as you grow in your career. I suggest skimming over the career levels and chapters that you are familiar with, and focus reading on topics you struggle with, or career levels where you are aiming to get to. Keep in mind that expectations can vary greatly between companies.
In this book, I’ve aimed to align the topics and leveling definitions closer to what is typical at Big Tech and scaleups: but you might find some of the topics relevant for lower career levels in later chapters. For example, we cover logging, montiroing and oncall in Part 5: “Reliable software systems” in-depth: but it’s useful – and oftentimes necessary! – to know about these practices below the staff engineer levels.
The Software Engineer's Guidebook is available in multiple languages:
You should now be able to ask your local book shops to order the book for you via Ingram Spark Print-on-demand - using the ISBN code 9789083381824. I'm also working on making the paperback more accessible in additional regions, including translated versions. Please share details here if you're unable to get the book in your country and I'll aim to remedy the situation.
I'd like to think so! The book can help you get ideas on how to help software engineers on your team grow. And if you are a hands-on engineering manager (which I hope you might be!) then you can apply the topics yourself! I wrote more about staying hands-on as an engineering manager or lead in The Pragmatic Engineer Newsletter.
I've gotten this variation of a question from Data Engineers, ML Engineers, designers and SREs. See the more detailed table of contents and the "Look inside" sample to get a better idea of the contents of the book. I have written this book with software engineers as the target group, and the bulk of the book applies for them. Part 1 is more generally applicable career advice: but that's still smaller subset of the book.