Understanding Software: Max Kanat-Alexander on simplicity, coding, and how to suck less as a programmer

Key Features
Read and enjoy the superlative writing and insights of the legendary Max Kanat-Alexander
Learn and reflect with Max on how to bring simplicity to your software design principles
Discover the secrets of rockstar programmers and how to also just suck less as a programmer

Book Description
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 a status as a code guru, and his ideas will inspire you and help refresh your approach to the challenges of being a developer.

What you will learn
See how to bring simplicity and success to your programming world
Clues to complexity - and how to build excellent software
Simplicity and software design
Principles for programmers
The secrets of rockstar programmers
Max's views and interpretation of the Software industry
Why Programmers suck and how to suck less as a programmer
Software design in two sentences
What is a bug? Go deep into debugging