100 Books Like How to Write for the World of Work

In my consulting gigs, I come across plenty of clueless remarks. Here's a classic one: “We're falling behind schedule, so let's hire more coders.” Or a more recent gem: “We'll be ten times more productive if we generate code with AI.”

When I encounter such nonsense, I don't facepalm or cringe. Instead, I put on my poker face and drop a quote from The Mythical Man-Month.

In an industry where last year’s book is already outdated, Fred Brooks' collection of essays has been a guiding light for nearly half a century. His aphorisms have become legendary. “The bearing of a child takes nine months, no matter how many women are assigned.” “Adding manpower to a late software project makes it later.” “There is no silver bullet.” The list goes on and on.

John Carmack, one of the greatest programmers of our times, used to revisit this book every year or… show more.

Yes, it’s a textbook, albeit a particularly well-written one. You may already have it on your shelf, if you’ve taken a programming class or two.

I’m way too old to have used CLRS as a textbook, though! For me, it’s an effectively bottomless collection of neat little ideas—an easy-to-describe problem, then a series of increasingly clever ways to solve that problem. How often do I end up using one of those algorithms? Not very often! But every time I read the description of an algorithm, I get a nugget of pure joy from the “aha” moment when I first understand how it works.

Software engineering involves several phases such as requirements gathering, design, programming, testing, and deployment.

This book explains techniques that allow you to build quality and robustness into every phase of the process. It discusses design, classes, defensive programming, collaboration, refactoring, and more.

The book uses many examples in an assortment of languages but the concepts apply to any programming language. In fact, the main themes like building error detection into every step of the process generalize to even non-programming parts of the development process.

If you’re an experienced developer, you may have discovered some of this book’s ideas elsewhere or even on your own, but you only need to pick up one or two new tidbits to make the book worthwhile.

As you might have guessed from the title, Josh Bernoff calls it like he sees it. And he sees a lot of sloppy business writing! Let this be your direct wake-up call to clean up your writing act. The book is a terrific guide to effective business writing, filled with stories and concrete examples. 

I believe firmly in Bernoff’s Iron Imperative: “Treat the reader’s time as more valuable than your own.” Invest a little time in this book to serve your readers better.

David Ogilvy said, “Drayton Bird knows more about direct marketing than anyone in the world,” and you can see why he said it in this book.

At some point in your marketing you need to get your potential customers to become paying customers. To actually part with their hard-earned cash. This book is a masterclass on how to do that in print – either on your website or in letters, adverts, brochures, or flyers. Bird’s writing has that amazing quality of charm, of being able to get you to buy without feeling you’ve been sold to. The book shows you how to get something similar yourself and is chock full of examples to learn from.

This book (an update to Software Tools by the same authors) codifies and instructs the principles by which the Unix / Linux toolset was designed. It emphasizes clear, robust code, and the building of tools, reusable, general purpose software components that can be hooked together to solve many kinds of programming and data management tasks. The lessons it teaches are timeless, and the current generation of programmers would be well served to try and learn them.

The original Software Tools was perhaps the single most influential software book that I ever read. It taught me how to think with the Unix mindset, how to make the best use of what the Unix system (and now Linux) offers, and how to focus on readability and maintainability in my own software.

Robert Glass is one of the foundational leaders of the discipline of software engineering. He’s done it all and seen it all. This book includes 55 facts and 10 fallacies about many aspects of software engineering, grouped into the major categories of management, the life cycle, and quality. Based on my own experience, I can vouch for the validity of all the points Glass makes.

These timeless truths can help you avoid going down an ineffective path, wasting time only to rediscover the same facts on your own. There’s no need to retrace the missteps from the past. Books like this can keep your energies focused where they will provide the most value to your customers.

I’ve always been a big fan of books that explode the “great man” myth and lift the curtains to show all of the unsung heroes behind history’s greatest accomplishments. The sociologist Howard Becker’s classic Art Worlds did this for creative professions, and Kathy Kleiman’s Proving Ground does the same thing for digital computers.

The birth of modern computing is usually credited to the mathematician Alan Turing. But the actual work of programming the world’s first general purpose digital computer, named ENIAC, was undertaken by six remarkable women mathematicians (Kathleen McNulty, Jean Jennings Bartik, Frances Elizabeth Snyder, Frances Bilas Spence, Marlyn Wescoff Meltzer and Ruth Lichterman Teitelbaum) whose names were left out of the history books.

Author Kathy Kleiman has made it her life’s work to restore these trailblazers to their rightful place at the beginning of the data revolution that has radically changed global society over the past 80 years.… show more.

When trying to become a better Java developer, there is so much to learn.

97 Things covers, well 97, of them in a series of brief essays. What’s cool is that the essays were written by different people so you get lots of points of view on what is important. Topics range from language (comments, fat jars) to the ecosystem (benchmarking, frequent releases) to the language-agnostic (definition of done and breaking down problems.)

Note that two of these are mine. The book is thin at just over 200 pieces. And since each “thing” is short, it’s easy to read on the go.

Wow! This book is exactly what every programmer has always wanted to know or even felt guilty about not knowing and it’s all presented in an extremely simplified and fun way. 

This is one of those books where you get excited in the morning when you wake up because you know you are going to be able to read more in the book and you are hoping the book will never end.

It’s rare to find a big book that I enjoyed reading so much and felt so short. This book covers almost everything you ever wondered about computer science. After reading this book, I felt like I finally understood everything a programmer was supposed to know and I no longer felt that nagging feeling of being an imposter.