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.
Another iconic acapella is "So Many Tears," a song that showcases 2Pac's ability to blend introspection with social commentary. His vocal performance is soulful, and his lyrics tackle themes of love, loss, and redemption.
The 1990s was a pivotal time for hip-hop, with West Coast and East Coast rap scenes thriving. Two artists stood out during this era: 2Pac Shakur and The Notorious B.I.G. Their lyrics, styles, and contributions to the genre continue to inspire new generations. In this article, we'll explore their acapellas and the art of patching.
The Notorious B.I.G. was a giant in the hip-hop world, and his acapellas are a testament to his storytelling ability and charisma. One standout example is his acapella of "Juicy," a song that details his rise to fame and his experiences growing up in Brooklyn. Biggie's vocal delivery is smooth and confident, and his lyrics are infused with humor and wit.
An acapella is a vocal performance without instrumental accompaniment. In hip-hop, acapellas are often used to showcase an artist's vocal skills, lyrical prowess, and emotional delivery. Acapellas can be performed live or recorded in a studio, and they're a great way for artists to connect with their audience on a deeper level.
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.