The art of readable code: simple and practiclal techniques for writing better code

"Simple and practical techniques for writing better code"--Cover.

"Nutshell handbook"--T.p. verso.

Includes bibliographical references (p. 182-184) and index.

Code should be easy to understand -- pt. 1. Surface-level improvements. Packing information into names ; Names that can't be misconstrued ; Aesthetics ; Knowing what to comment ; Making comments precise and compact -- pt. 2. Simplifying loops and logic. Making control flow easy to read ; Breaking down giant expressions ; Variables and readability -- pt. 3. Reorganizing your code. Extracting unrelated subproblems ; One task at a time ; Turning thoughts into code ; Writing less code -- pt. 4. Selected topics. Testing readability ; Designing and implementing a "minute/hour counter."

As programmers, we've all seen source code that's so ugly and buggy it makes our brain ache. Over the past five years, authors Dustin Boswell and Trevor Foucher have analyzed hundreds of examples of "bad code" (much of it their own) to determine why they're bad and how they could be improved. Their conclusion? You need to write code that minimizes the time it would take someone else to understand it -- even if that someone else is you. This book focuses on basic principles and practical techniques you can apply every time you write code. Using easy-to-digest code examples from different languages, each chapter dives into a different aspect of coding, and demonstrates how you can make your code easy to understand. Simplify naming, commenting, and formatting with tips that apply to every line of code; Refine your program's loops, logic, and variables to reduce complexity and confusion; Attack problems at the function level, such as reorganizing blocks of code to do one task at a time; Write effective test code that is thorough and concise, as well as readable. - Publisher.