7 Books Every Man Should Read

[Jessica Wade]

Someof the best-known authors of classic literature wrote more than a century ago, including Mary Shelley, Daniel Defoe and Miguel de Cervantes, who penned the oldest book on the list. More contemporary authors include Toni Morrison, Alex Haley, J.R.R. Tolkien and C.S. Lewis. This list covers 30 books representing the best in literature. While most of these must-read classics are older, a few are just a couple decades old and have already become beloved by multiple generations.

The author of the acclaimed memoir Black Boy first published this novel about Bigger Thomas, a young Black man in Chicago who accidentally kills a white woman, then commits another murder to cover up the crime. The book deals with racism and classism, forcing Bigger to confront the consequences of his violent acts.

The precursor to modern-day young adult novels, The Outsiders presents the conflict between teenage gangs from differing socioeconomic backgrounds: the wealthy Socials (Socs) and the blue-collar Greasers. One of the Greasers, Ponyboy, narrates the book, which perfectly captures the pain, confusion and frustration of being a teenager. It also explores dysfunctional families and friendship ties.

Like so many Jane Austen novels, Pride and Prejudice relies on humor and a relatable protagonist to critique social norms of the day, including marriage, the class system and morality. This work of historical fiction tells the love story of Elizabeth Bennet and Mr. Darcy, who nearly remain estranged due to their pride and prejudices.

Colombian author and Nobel Prize winner Gabriel Garcia-Marquez uses magical realism to trace the evolution of the town of Macondo as experienced by generations of the Buendi family. Garcia-Marquez plays with the constructs of time and the supernatural to probe themes like love and family.

The four precocious March daughters (Jo, Amy, Meg and Beth) use their talents to help their mother while their father is away. They come of age with a purpose and goals. The book plays with the 1800s idea of domesticity and explores different paths to love.

When middle school boys become stranded on an island with no supervision, anarchy reigns and paranoia follows. The tale has become a touchstone for the unfortunate tendencies of human behavior, exploring themes of groupthink and the end of innocence.

@Juan: I know Juan, I know - but there are some things that can only be learned by actually getting down to the task at hand. Speaking in abstract ideals all day simply makes you into an academic. It's in the application of the abstract that we truly grok the reason for their existence. :P

@Keith: Great mention of "The Inmates are Running the Asylum" by Alan Cooper - an eye opener for certain, any developer that has worked with me since I read that book has heard me mention the ideas it espouses. +1

While this doesn't teach you programming, it teaches you fundamental mathematics that every programmer should know. You may remember this stuff from university, but really, doing predicate logic will improve you programming skills, you need to learn Set Theory if you want to program using collections.

The idea being that there are failing parts in any given piece of software that are masked by failures in other parts or by validations in other parts. See a real-world example at the Therac-25 radiation machine, whose software flaws were masked by hardware failsafes. When the hardware failsafes were removed, the software race condition that had gone undetected all those years resulted in the machine killing 3 people.

Extreme Programming Explained: Embrace Change by Kent Beck. While I don't advocate a hardcore XP-or-the-highway take on software development, I wish I had been introduced to the principles in this book much earlier in my career. Unit testing, refactoring, simplicity, continuous integration, cost/time/quality/scope - these changed the way I looked at development. Before Agile, it was all about the debugger and fear of change requests. After Agile, those demons did not loom as large.

This book explains a lot of things about software engineering, system development. It's also extremly useful to understand the difference between different kind of product developement: web VS shrinkwrap VS IBM framework. What people had in mind when they conceived waterfall model? Read this and all we'll become clear (hopefully)

Excellence in programming demands an investment of mental energy and a dedication to continued learning comparable to the professions of medicine or law. It pays a fraction of what those professions pay, much less the wages paid to the mathematically savvy who head into the finance sector. And wages for constructing code are eroding because it's a profession that is relatively easy for the intelligent and self-disciplined in most economies to enter.

Programming has already eroded to the point of paying less than, say, plumbing. Plumbing can't be "offshored." You don't need to pay $2395 to attend the Professional Plumber's Conference every other year for the privilege of receiving an entirely new set of plumbing technologies that will take you a year to learn.

If you live in North America or Europe, are young, and are smart, programming is not a rational career choice. Businesses that involve programming, absolutely. Study business, know enough about programming to refine your BS detector: brilliant. But dedicating the lion's share of your mental energy to the mastery of libraries, data structures, and algorithms? That only makes sense if programming is something more to you than an economic choice.

If you love programming and for that reason intend to make it your career, then it behooves you to develop a cold-eyed understanding of the forces that are, and will continue, to make it a harder and harder profession in which to make a living. "The World is Flat" won't teach you what to name your variables, but it will immerse you for 6 or 8 hours in economic realities that have already arrived. If you can read it, and not get scared, then go out and buy "Code Complete."

Each book was amazing but the Innovator's Dilemma by Clayton Christensen (1997!!!) is really a fantastic book, and it got me really thinking about the modern software world. The challenge addressed is disruptive technology, and how disk drive companies and non-technical companies are always disrupted by new, game changing technology. It gives one a new perspective when thinking about Google, probably the biggest 'web' company. Why do they have their hands in EVERYTHING? It's because they don't want to have their position disrupted by something new. The preview on google is plenty to get the idea. Read it!

I think that "The Art of Unix Programming" is an excellent book, by an excellent hacker/brilliant mind as Eric S. Raymond, who tries to make us understand a few principles of software design (simplicity mainly). This book is a must for every programming who is about to start a project under Unix platform.

While I agree that many of the books above are must-reads (Pragmatic Programmer, Mythical Man-Month, Art of Computer Programming, and SICP come to mind immediately), I'd like to go in a slightly different direction and recommend A Discipline of Programming by Edsger Dijkstra. Even though it's 32 years old, the emphasis on "design for verifiability" is highly relevant (even if "verifiability" means "proof" instead "unit tests").

The essence of the whole book is about structuring code so that it is simpler to read and understand by humans. It teaches me strongly that the code that I write is meant for my colleagues and successors to consume and possibly learn something good out of it. It inspires me to consciously program in a manner that leaves people praising my name, and not cursing me to damnation for all eternity.

What's so special about it? Well, clearly everyone has heard the term "Agile", and it seems most are believers these days. Whether you believe or not, though, there are some deep principles behind why the Agile movement exists. This book uncovers and articulates these principles in a precise, scientific way. Some of the principles are (btw, these are my words, not Alistair's):

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

2. Influence, by Robert Cialdini. The classic book about how to persuade people to do things, how to defend against persuasion attempts, and the underlying evidence. I have been using this in class at Stanford for over 25 years, and I have had dozens of students say to me years later "I don't remember much else about your class, but I still use and think about that Cialdini book." I also am impressed with Cialdini's 2016 bestseller, Pre-Suasion, which adds wonderful new evidence-based twists. And while some of the examples in the original book are getting a bit dated, I suggest starting with the classic and then reading the new one.

3. Made to Stick, by Chip and Dan Heath. It is already a classic after just a few years. The Heath brothers dig into surprising nuances of how to design ideas that people will remember and act on. I still look at it a couple times each month, and buy two or three copies at a time because people are always borrowing it from me. I often tell them to keep it because they rarely give it back anyway. And, for my tastes, it has the best business book cover of all time -- the duct tape even looks and feels real.

4. Thinking, Fast and Slow, by Daniel Kahneman. Even though the guy won the Nobel Prize, this book is surprisingly readable. It about how we humans really think and make decisions. And although it isn't designed to do so, Kahneman also shows how and why so much of the stuff you read in the business press is crap. I also recommend Michael Lewis' 2017 book The Undoing Project, which describes the complex relationship between Daniel Kahneman and his colleague the late Amos Tversky (who would have shared the Nobel with Kahneman if he had lived).

3a8082e126