Write Code You Can Still Read 6 Months Later

Short summary

A junior high student shares practical lessons on writing readable code: use full variable names instead of abbreviations, split functions that need 'and' to describe them, write comments that explain why not what, flatten nested conditionals with early exits, and split large files by topic. The guiding principle is whether you can understand a random function in 30 seconds six months later.

• •Use full descriptive names instead of abbreviations like cnt, sz, ptr
• •Split functions that require 'and' to describe them; keep them screen-length
• •Comments should explain why, not restate what the code already says

Generated with AI, which can make mistakes.