Clean by Default: Coding Standards
The rules — and the reasons behind them — that separate code a team can maintain from code only its author can. TypeScript and Python.
Start reading →01Chapter 1: Why Coding Standards Matter: Readability, Onboarding, Defects, Consistency at Scale02Chapter 2: Naming Conventions03Chapter 3: Formatting and Style04Chapter 4: Comments and Self-Documenting Code05Chapter 5: Error Handling Conventions06Chapter 6: Code and Project Organization (Files, Modules, Packages)07Chapter 7: Writing Testable Code08Chapter 8: Commit Hygiene: Atomic Commits, Messages, PR-Sized Changes09Chapter 9: Language-Specific Idioms and Anti-Patterns Across TypeScript and Python10Chapter 10: Security-Conscious Basics: Input Validation, Secrets Handling, Injection Risks11Chapter 11: Enforcing Standards Automatically: Linters, Formatters, CI Gates12Chapter 12: Creating, Documenting, and Evolving a Team Style Guide (Exceptions and Legacy Code)13Chapter 13: Worked Example: Refactoring a Messy Function to Standard14Chapter 14: Worked Example: Drafting a Style Guide Section From Scratch15Chapter 15: Common Interview Questions About Coding Standards and Code Quality
Other tracks
Python DSA — CoursePython DSA — Interview PrepPython DSA — BeginnerPython Syntax & DSA ReferenceGit MasteryCognitive Skills & Mental ToolsCode Optimization RulesObjects First: OOP FundamentalsPatterns of Good DesignUnder the Hood: Operating SystemsHow the Bytes Travel: NetworkingData at Rest, Data in Motion: DatabasesSharing Time: Concurrency & MultithreadingThe Review: Code ReviewFrom Idea to Production: the SDLCDesigning at Scale: System DesignWhiteboard to Blueprint: HLD & LLDBuilt to Last: Reliability & ScalingTell Me About a Time: Behavioral Interviews