Book Image

Understanding Software

By : Max Kanat-Alexander
Book Image

Understanding Software

By: Max Kanat-Alexander

Overview of this book

In Understanding Software, Max Kanat-Alexander, Technical Lead for Code Health at Google, shows you how to bring simplicity back to computer programming. Max explains to you why programmers suck, and how to suck less as a programmer. There’s just too much complex stuff in the world. Complex stuff can’t be used, and it breaks too easily. Complexity is stupid. Simplicity is smart. Understanding Software covers many areas of programming, from how to write simple code to profound insights into programming, and then how to suck less at what you do! You'll discover the problems with software complexity, the root of its causes, and how to use simplicity to create great software. You'll examine debugging like you've never done before, and how to get a handle on being happy while working in teams. Max brings a selection of carefully crafted essays, thoughts, and advice about working and succeeding in the software industry, from his legendary blog Code Simplicity. Max has crafted forty-three essays which have the power to help you avoid complexity and embrace simplicity, so you can be a happier and more successful developer. Max's technical knowledge, insight, and kindness, has earned him code guru status, and his ideas will inspire you and help refresh your approach to the challenges of being a developer.
Table of Contents (50 chapters)
Understanding Software
About the Author
Customer Feedback
The Engineer Attitude
The Singular Secret of the Rockstar Programmer
Software Design, in Two Sentences
Clues to Complexity
Ways To Create Complexity: Break Your API
When Is Backwards-Compatibility Not Worth It?
Complexity is a Prison
The Accuracy of Future Predictions
Simplicity and Strictness
Two is Too Many
What is a Bug?
What is a Computer?
The Components of Software: Structure, Action, and Results
Software as Knowledge
Simplicity and Security
How We Figured Out What Sucked
Why Programmers Suck
Developer Hubris
"Consistency" Does Not Mean "Uniformity"
Success Comes from Execution, Not Innovation

The Wrong Way

Imagine that you were building this all by yourself, and that you had to make the bars yourself out of raw metal. Here's the wrong way to build it:

  1. Make one tall lead bar, and lay it flat on the ground in your workshop:

  2. Cut a hole through the tall bar, and measure that hole.

  3. Make a new bar that will fit through that hole:

  4. Put that new bar through the hole and weld them together permanently:

  5. Cut two holes in the horizontal bar, measure them, and make two new lead bars that will fit in those individual holes:

  6. Insert the two bars into the horizontal bar, and weld them together permanently:

  7. With a forklift, put this into a truck to move it to the location where it's supposed to be. (It's too heavy to move by yourself.)

  8. With a pulley, make the construction stand upright and put it into the ground.

  9. Discover that it won't stay up by itself, but if you put some blocks next to it as an emergency solution, it doesn't fall over:

  10. Three days later, watch the structure fall over and break because...