Includes index.

As simple as possible, but no simpler -- Bugs are contagious -- A good name is the best documentation -- Generalization takes three examples -- The first lesson of optimization is don't optimize -- Interlude: In which the previous chapter is criticized -- Code reviews are good for three reasons -- Eliminate failure cases -- Code that isn't running doesn't work -- Write collapsible code -- Localize complexity -- Is it twice as good? -- Big teams need strong conventions -- Find the pebble that started the avalanche -- Code comes in four flavors -- Pull the weeds -- Work backward from your result, not forward from your code --- Sometimes the bigger problem is easier to solve -- Let your code tell its own story -- Rework in parallel -- Do the math -- Sometimes you just need to hammer the nails -- Conclusion: Making the rules your own -- Appendix A. Reading C++ for Python programmers -- Appendix B. Reading C++ for JavaScript programmers.

"This philosophy-of-programming guide presents a unique and entertaining take on how to think about programming. A collection of 21 pragmatic rules, each presented in a standalone chapter, captures the essential wisdom that every freshly minted programmer needs to know and provides thought-provoking insights for more seasoned programmers"-- Provided by publisher