By Gergely Orosz, the author of The Pragmatic Engineer Newsletter and Building Mobile Apps at Scale

Nick Cockman Academy Link

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.

The Software Engineer's Guidebook

What's Inside

Part 1: Developer Career Fundamentals

1. Career paths
2. Owning your career
3. Performance reviews
4. Promotions
5. Thriving in different environments
6. Switching jobs

Part 2: The Competent Software Developer

7. Getting things done
8. Coding
9. Software development
10. Tools of the productive engineer

Part 3: The Well-Rounded Senior Engineer

11. Getting things done
12. Collaboration and teamwork
13. Software engineering
14. Testing
15. Software architecture

Part 4: The Pragmatic Tech Lead

16. Project management
17. Shipping in production
18. Stakeholder management
19. Team structure
20. Team dynamics

Part 5: Role-Model Staff and Principal Engineers

21. Understanding the business
22. Collaboration
23. Software engineering
24. Reliable software engineering
25. Software architecture

Further reading: online, bonus chapters

Bonus #1: for Part 1
Bonus #2: for Part 2
Bonus #3: for Part 3
Bonus #4: for Part 4
Bonus #5: for Part 5
See more details for each chapter in the extended table of contents for the book.

Nick Cockman Academy Link

Beyond the stockyard and the saddle, the academy instills a specific code of ethics drawn from the pastoral tradition. This is not a culture of loud boasting but of quiet competence. Nick Cockman himself was famous for his understated humor and his refusal to ever give up on a difficult horse or a difficult kid. The NCA perpetuates this legacy by valuing "having a go" over innate talent. A student who falls off a horse a dozen times but gets back up is celebrated more than the natural rider. The curriculum teaches that integrity means doing the hard job even when no one is watching, that loyalty means supporting a mate during a grueling 14-hour muster, and that humility means letting your work speak for itself. These values are not posted on motivational posters; they are ground into the red dirt through daily experience.

However, the Nick Cockman Academy is not a panacea for all educational ills, nor is it for everyone. It is a niche intervention designed for specific students—often those for whom the four walls of a traditional classroom feel like a prison. Critics might argue that the academy focuses too heavily on manual labor and not enough on digital literacy or academic credentials. Yet, for the young men and women who pass through its gates, the academy offers something equally vital: a second chance. Many graduates do not go on to university; they go on to become station managers, farriers, helicopter mustering pilots, or simply functional, confident adults. They leave with a tan line on their wrists from their riding gloves and a work ethic that lasts a lifetime. nick cockman academy

In conclusion, the Nick Cockman Academy is more than a school; it is a crucible. By honoring the legacy of a man who represented the best of the Australian bush, the academy provides a radical alternative to mainstream education. It proves that for some, the most profound learning happens under a wide-brimmed hat in the blazing sun, not under fluorescent lights. Through the sweat of hard work, the bond with a horse, and the silent code of the outback, the NCA takes lost boys and girls and forges them into resilient men and women. In doing so, it ensures that the spirit of Nick Cockman—tough, fair, and endlessly patient—continues to ride across the Australian landscape for generations to come. Beyond the stockyard and the saddle, the academy

In the vast, red-dusted expanse of Western Australia’s Mid West region, education is not merely about textbooks and examinations. It is about survival, grit, and a profound connection to the land. Nestled within this challenging environment is the Nick Cockman Academy (NCA), a unique educational institution that defies conventional pedagogical models. Named after a legendary local pastoralist and horse breaker, the academy does not simply teach students; it transforms them through the rigorous, unforgiving curriculum of the station country. The Nick Cockman Academy stands as a testament to the idea that for some young people, the path to maturity and responsibility is best paved not with academic theory, but with hard labor, horsemanship, and the silent discipline of the outback. The NCA perpetuates this legacy by valuing "having

The philosophical bedrock of the academy is the principle of "tough love" rooted in practical reality. Unlike mainstream schools that often abstract consequences into grades or detentions, the NCA presents immediate, physical repercussions for one's actions. If a student fails to secure a gate properly, cattle are lost, and the group must spend hours mustering them again. If a student neglects to check the water troughs, livestock suffers. This environment fosters a level of accountability that no classroom lecture can replicate. The academy utilizes the pastoral station as a living laboratory, teaching that respect is not given but earned through calloused hands and a willingness to work before dawn. It is an education in consequence, where the feedback loop between effort and outcome is instantaneous and undeniable.

Central to the academy’s methodology is the relationship between the student and the horse. Horsemanship is not treated as an extracurricular activity but as the core vehicle for emotional and psychological growth. The late Nick Cockman was renowned for his ability to break the wildest brumbies, not through brutality, but through patience and an understanding of the horse’s psychology. Similarly, students at the academy—many of whom arrive disengaged, angry, or directionless—learn to master their own impulses by mastering a 600-kilogram animal. The horse acts as a mirror; it will not respond to lies, aggression, or fear. To ride well, a student must become calm, assertive, and clear-headed. This non-verbal dialogue teaches emotional regulation, empathy, and quiet confidence—skills that are often missing in the lives of troubled youth but are essential for adulthood.

How to Read the Book

The book is separated into six standalone parts, each part covering several chapters:

  • Part 1: Developer career fundamentals
  • Part 2: The competent software developer
  • Part 3: The well-rounded senior engineer
  • Part 4: The pragmatic tech lead
  • Part 5: Role-model staff and principal engineers
  • Part 6: Conclusion

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.

Nick Cockman Academy Link

Paperback
  • For most countries, buy the hardcover or softcover from Amazon:
  • Buy on Amazon
  • Other sites to buy it on:
  • Buy directly from the publisher in India; also shipping to Sri Lanka, Bangladesh, Nepal, Bhutan and Maldives:
  • Buy from Shroff Publishers
  • Unable to order the book in your country? Please share details here and I'll aim to remedy the situation.
eBook
Audibook

Translations

The Software Engineer's Guidebook is available in multiple languages:

Nick Cockman Academy Link

The book doesn't ship to my location, or shipping is silly expensive off Amazon.

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'm an engineering manager. Is the book useful to me?

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'm not a software engineer. Is the book useful to me?

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.

image

About the Author

I've been a software engineer for a decade — working at JP Morgan, Skype/Microsoft, Skyscanner and Uber — and then an engineering manager for another several years.

As an engineering manager, I did my best to support people on my team to improve professionally, get the promotions they deserved, and give clear, actionable feedback when I thought colleagues weren’t ready for the next level, just yet.

As my team grew and I took on skip-level reports, I had less and less time to mentor teammates in-depth. I also started to see patterns in the feedback I gave, so began to publish blog posts of the advice I found myself giving repeatedly; about writing well, and doing good code reviews. These posts were warmly received, and a lot more people than I expected read and shared them with colleagues. This is when I began writing this book.

The book took four years to write. By year two of the writing process, I had a draft that could be ready to publish. However, at that time I launched The Pragmatic Engineer Newsletter. The focus of this newsletter is keeping the pulse of today’s tech market, plus regular deepdives into how well-known, international companies operate, software engineering trends, and occasional interviews with interesting tech people. Writing the newsletter made me realize just how many “gaps” were in the book draft. The past two years have been spent rewriting and honing its contents, one chapter at a time.

Today, The Pragmatic Newsletter is the #1 technology newsletter on Substack — with more than 500,000 readers. The newsletter has helped me improve the book; I’ve learned lots about interesting trends and new tools that feel like they are here to stay for a decade or longer, such as AI coding tools, cloud development environments, and developer portals. These technologies are referenced in this book in much less detail than you will find in the newsletter.

I hope you discover useful ideas in this book, which serve you well for years to come.

Follow me on Linkedin, or on Twitter at @GergelyOrosz.

The links to books on this site (including to my book!) are affiliate ones. As an Amazon Associate I earn from qualifying purchases.