This is my attempt at short actionable checklists to guide key moments in software process.
Mental models are foundational. They decide how we interpret information and reason about a topic. Yet mental models for writing software are immature and little discussed. Code That Fits in Your Head puts mental models front and center.
Code That Fits in Your Head collects the myriad of somthing-driven practices into a category of drivers. Drivers create a toolkit for highlighting motivations and responding to them with code.
Code That Fits in Your Head tackles a problem dear to my heart. Mark Seemann realized good software engineering practices are out there, but it’s hard to connect the dots between scattered sources.
Stable, incremental, and additive is my personal theory about what underlies effective software practices. I’m pleased to find these qualities hold up quite well for practices described by Code That Fits in Your Head.
I realized that my Software Engineering Body of Knowledge (SWEBOK) posts reference, but never define, the 15 key knowledge areas outlined by SWEBOK. I intent to fix that with this post.