Why Avoid Unnecessary Indentation and Nesting? Boost Code Clarity and Early Bailout

Ash Furrow once remarked on the importance of avoiding unnecessary code indentation, a practice he adopted after a senior student demonstrated it during his first year. He now refrains from correcting existing code—since it doesn’t affect performance—but consistently applies the habit in new programs.

He also follows a similar principle regarding nesting: while both indentation and nesting affect visual structure, the core issue differs—indentation concerns code layout, whereas nesting concerns semantic clarity.

Eliminating deep nesting encourages an "early bail" style: instead of nesting statements that increase both logical depth and visual indentation, you simplify logic so that the final executable statements are as few as possible. Simpler code is easier to understand.

Readers may notice that the second example, although longer, is more readable. Imagine having five conditional checks before the main method runs; nesting would make the code terrifyingly complex.

The combined nil and length checks in the example are deliberately redundant to illustrate the point: returning nil yields a zero pointer, and calling [s length] on an empty string or nil also returns zero.

While the early‑bail style improves readability, it can introduce memory‑management concerns. Developers may need to use autorelease more frequently or duplicate release code across the program to prevent object‑allocation leaks.

Such scenarios are rare in real‑world projects, but the trade‑off is worth remembering.