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

Being Effective

So what is it that you want to do? Well, usually, what you want to do is pick a feature that you want to get implemented, and figure out what you could refactor that would make it easier to implement that. Or you find an area of the code that is frequently being worked on and get some reorganization done in that area. This will make people appreciate your work. It's not just about that – it's really about the fact that they will appreciate it because you are doing something effective. But getting appreciation for the work that you've done – or at least some form of polite acknowledgment – can help encourage you to continue, can show you that other people are starting to care about your work, and hopefully help spread good development practices across your company.

Is there ever a time when you would tackle a refactoring project that doesn't have something directly to do with the work that you have to do? Well, sometimes you would refactor something that has to do indirectly...