27 books like Proving Ground

JL Borges is, in my view, the greatest literary mind of the 20th Century.

This is a book of stories, philosophical essays and parables, but even when he is writing fiction, his favoured form is that of the mock critical essay about a non-existent book or writer.

What I especially love about him is his wit, subtle and easily missed since it often takes the shape of philosophical rumination when he is actually debunking something held very highly. My natural mode of expression is irony, and Borges’s irony is inimitable.      

My friend Jesse Gilbert handed me his copy of Chaos in 1992 or 1993, shortly after he read it for a college class. “You have to read this book,” he insisted. “I need to talk about it with you.”

Chaos theory, which is the subject of Gleick’s nonfiction book, has become such a dominant trope in global fiction, the popular imagination, and meme culture that younger folks probably don’t realize how completely new this way of thinking was for most of us when the book was first published in 1987.

In the 1980s, science fiction and popular tech narratives were all about robots and spaceships, with a heavy dose of late-Cold War nuclear anxiety. Then Gleick published Chaos. Suddenly, it seemed like everyone was interested in fractals, parallel universes, and virtual worlds. The concepts of bounded infinities and multi-dimensional topographies opened up not just new types of narratives but… show more.

Full disclosure: Laura DeNardis is a good friend and former colleague of mine. But I was a fan before I was a friend, and thus far, The Internet In Everything is her crowning achievement, so I feel very comfortable listing it here as an absolute must-read.

When Laura told me she was going to write this book, my first thought was, “I wish I’d thought of that!” and my second thought, a nanosecond later, was, “Thank goodness I didn’t because she’ll do it a million times better.”

DeNardis is the reigning monarch of Internet Governance Studies, meaning she researches all the weird laws, policies, technologies, businesses, agencies, and practices that have built the internet and keep it ticking. You’d think the subject would be boring or impenetrable to us mere mortals, but her genius is in making it not only understandable but downright fascinating.

She understands the internet the way… show more.

André Brock gives no fucks and takes none. As an academic, so many of the books I read—even the good ones—are couched in cautious language and speak from an imaginary non-place of dispassionate objectivity. Brock throws all that out the window and writes an impassioned, embodied, joyful, agitated, confusing, brilliant, opinionated, insightful, and ultimately, empirically supportable book, in his own unmistakable voice, about how and why Black people use the internet.

Though the book has many valuable findings and has already changed the practice of internet studies since its publication, the thing I love most about it is Brock’s own playfulness and his celebration of the social and political value of playfulness.

His key point is that data aren’t objective or neutral and that computing machines aren’t cold and calculating (even if that’s their job). Data and computers, he argues, are made by people and used by people, and the… 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.

Suarez’s debut novel focuses on an all too real possibility of our future—and the dangers we could face.

Daemon warns of our reliance on computers as he tells a fast-paced story about a massive software program that awakens and initiates a terrible plan no one can decipher. We seem to accept that computers are programmed with our best interest in mind, though few truly know everything hidden in those endless lines of code.

Suarez shows the dangers of that near-blind acceptance. Knowledge is power. In Daemon, this tenant is taken to the extreme, with an artificial intelligence holding all the cards. It’s a future we might already be facing but don’t realize yet. 

When people think about software engineering they mostly think about programming, but that’s not where a project starts. It starts with requirements.

(Really it sometimes starts with company politics, bickering, excuses, and backstabbing, but requirements gathering is often the official start.)

A good set of requirements keeps developers pulling in the same direction; a bad one can make the team inefficient, cause endless arguments, set developers against each other, and make the project feel like Lord of the Flies. I’ve seen projects scrapped and restarted from scratch or even canceled due to poor documentation.

Every software developer should know at least a little about writing so they can produce clear requirements and documentation.

This book isn’t specifically about writing documentation (which is something of an art in itself), but it can help you learn how to make your business writing more effective. This book won’t turn you into Shakespeare,… show more.

Robert (Uncle Bob) Martin is the recognized go-to person for books on creating quality code. This is the first in a series of books that include The Clean Coder, Clean Architecture, and a number more. His advice and guidance in Clean Code have made a significant difference in my personal coding habits and best practices. This is an indispensable book for all programmers, no matter what they are coding or how much experience they have

I’ve read a lot of books about programming; very few of them have made me laugh. None made me laugh as much as this book.

There’s one chapter where… nah, I don’t want to spoil it for you. Plus it has cartoons! Obviously, none of that would matter unless it also had interesting things to say about the practice of programming, but it’s packed full of interesting perspectives on all sorts of issues, from team dynamics to thinking about your career to an explicit consideration of the ethics of programming.

When we make games at Sucker Punch, we aim to “surprise and delight” the player—and that’s exactly what this book did for me.