Clean code habits I wish I learned sooner

After a few years on the job, I realized clean code doesn't come from clever tricks, but from small habits repeated every day.

# Naming beats commenting

A good name for a variable or function usually removes the need to explain it. If you need a comment to decode a name, rename it first.

# Small functions, one job

A function should do one thing and do it well. When a function grows, it's a signal to split it so it's easier to test and reuse.

• Prefer readability over cleverness
• Delete dead code instead of commenting it out
• Refactor in small steps, guarded by tests

Clean code is a gift you give to your future self six months from now.