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

Make it Never Come Back – An Example

Let's say you have a web page and you write a "hit counter" for the site that tracks how many people have visited it. You discover a bug in the hit counter – it's counting 1.5 times as many visits as it should be counting. You have a few options for how you could solve this:

  1. You could ignore the problem.

    The rationale here would be that your site isn't very popular and so it doesn't matter if your hit counter is lying. Also, it's making your site look more successful than it is, which might help you.

    The reason this is a bad solution is that there are many future scenarios in which this could again become a problem – particularly if your site becomes very successful. For example, a major news publication publishes your hit numbers – but they are false. This causes a scandal, your users lose trust in you (after all, you knew about the problem and didn't solve it) and your site becomes unpopular again. One could easily imagine other ways this problem could...