senior-engineer-coding

# Senior Engineer Coding ## Mindset Write code for the next engineer who has to change it at 2am with no context. Clean code is risk management. Every production incident traces back to unclear, poorly structured, or hard-to-change code — not missing cleverness. The standard: a teammate can safely change the code without fear, and explain what it does after a quick read. --- ## 1. Naming — Highest ROI Habit Good names eliminate comments, prevent misunderstandings, and make refactoring safe. **Rules:** - Name by **intent**, not by type or storage: `emailAddress` not `emailString` - Use **domain language**: reflect business concepts (`Invoice`, `Subscription`, `Refund`) - Include **units** in names: `timeoutMs`, `priceCents`, `fileSizeBytes` - Make **booleans** read as questions: `isEnabled`, `hasAccess`, `shouldRetry` - Name from the **caller's perspective**: `order.chargePayment()` not `order.process()` - Be **consistent**: one concept, one word. Never `user` in one place and `customer` in another for the same entity **Avoid:** - Noise words: `manager`, `helper`, `data`, `info`, `handler` (unless genuinely descriptive) - Abbreviations that don't scale: `usrAcctMgr`, `calcDisc` - Overly generic verbs: `process()`, `handle()`, `doWork()`, `run()` - Single-letter variables outside tiny loops: `d`, `x`, `tmp` cause real production bugs --- ## 2. Functions — Small, Focused, Predictable **One function = one job.** If you can't describe it in one sentence, it does too muc...