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.
Toontrack Superior Drummer has a long history dating back to 2001, when the first version was released. Since then, the software has undergone significant updates and improvements, with each new version offering more features, better sound quality, and enhanced user experience. The latest version, V3.3.3, is the culmination of years of development and refinement, and it's clear that Toontrack has pushed the boundaries of what's possible with drum sampling software.
A comprehensive mixing console featuring 35 studio-quality effects, including vintage compressors, delays, reverbs, and EQs.
You do not need to be a drummer to create realistic drum tracks. Superior Drummer 3 includes a massive core MIDI library with over 1,640 grooves and fills recorded by professional session drummers. Features like allow you to tap a rhythm on your keyboard, and the software will find all matching MIDI grooves from its library instantly.
235 GB for the full installation (though it can be installed in stages). Final Thoughts
The V3.3.3 update focuses heavily on optimization, stability, and seamless integration with modern DAWs and newer computer operating systems. Feature Area Enhancements & Fixes in V3.3.3
If you're ready to upgrade your production, exploring the Toontrack website for the latest updates on Superior Drummer 3 is highly recommended.
Create complex sub-mixes, parallel compression setups, and bus routing. 4. Tracker: Powerful Drum Replacement
What sets this software apart is the mixing capabilities. Users have access to a fully modeled studio environment where they can:
The heart of the is its factory sound library. This is not a collection of pre-mixed, "polished" samples. Instead, Toontrack recorded world-class drummers in the legendary Allaire Studios (upstate New York) using a Neve 88R console and a pristine selection of microphones.
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.