code-that-fits-in-your-head

Solid

Software engineering heuristics from Mark Seemann's book Code That Fits in Your Head (2021). Use when writing new code, reviewing code, refactoring, designing APIs, handling validation and invariants, writing unit tests, debugging defects, performing security review (STRIDE), or setting up a new code base. Covers decomposition (cyclomatic complexity, 80/24 rule, cohesion, fractal architecture), encapsulation (invariants, parse-don't-validate, Postel's law), outside-in TDD (walking skeleton, AAA, triangulation, devil's advocate), API design (affordance, poka-yoke, CQS), git/PR hygiene (50/72 commits, small commits, code review), feature flags, Strangler pattern, bisection debugging, logging with decorators, and STRIDE threat modelling. Not for language-specific syntax, framework tutorials, production incident response, or performance profiling.

Code & Development 109 stars 8 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Code That Fits in Your Head Engineering heuristics for sustainable software, based on Mark Seemann's 2021 book. ## Philosophy (Why This Skill Exists) Software development is principally a **design activity**, not construction. Code is written by people, read by people, and endures far longer than any "project". These heuristics are rules of thumb (not scientific laws) that make software sustainable — that is, cheap to change and resilient to the next 10,000 small decisions. Core mental model from Chapter 1: | Metaphor | What it gets right | What it misses | |----------|-------------------|-----------------| | **Building a house** | Plans, structure | Software endures; there's no construction phase (compiling is free); dependencies can start anywhere | | **Growing a garden** | Pruning, refactoring, tending | Code doesn't grow by itself — someone writes it | | **Art / craft** | Skill, mastery, situational knowledge | Doesn't scale; leaves newcomers without guidance | | **Engineering** (the target) | Heuristics, review, sign-off, checklists | We're not there yet — physical-construction calculations don't apply | > "The act of describing a program in unambiguous detail and the act of programming are one and the same." — Kevlin Henney **Practical implications for a code agent:** 1. **Successful software endures.** Prefer changes that don't lock the future; avoid "finish-and-forget" thinking. 2. **Heuristics, not laws.** Every rule in this skill has context. Understand *w...

Details

Author
CodeAlive-AI
Repository
CodeAlive-AI/ai-driven-development
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category