[{"_1":2,"_68":-5,"_69":-5},"loaderData",{"_3":4,"_38":39,"_66":-5,"_67":-5},"root",{"_5":-5,"_6":-5,"_7":8,"_22":23,"_24":25,"_26":27,"_30":31,"_36":37},"user","shoppingCartId","shoppingCart",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":20,"_21":14},"id","no-cart","count",0,"free",true,"updatedAt","","paymentGateway","STRIPE","cartItems",[],"loading","locale","en","readerTheme","light","constants",{"_28":29},"paypalClientId","AX53Cwz8jR6rVVzzZiZNWWXl0dGagi-GZrjG-S3Ua14E5nrKMn7DxDQ730O4R8LusLPp49ALn6aRVaEy","publishers",{"_32":33,"_34":35},"companies",[],"universities",[],"needsLocaleCookieSync",false,"routes/_store+/_readers+/email_author.$slug/route",{"_40":41,"_65":-5},"book",{"_9":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNzczNjc","title","Raising the Level of Abstraction","state","published","contactAuthorMethod","email","aboutText","

This book is about building software systems at the right level of abstraction.

In many codebases, the structure of the system is buried in implementation details—classes, methods, and glue code that obscure how data actually flows and how components interact.

Over time, this makes systems harder to understand, harder to change, and more fragile than they need to be.

Instead of starting with code, we describe the system using a simple, domain-focused model. That model defines the data, the flow of that data, and the components that transform it. From that description, we generate the implementation using explicit, deterministic rules.

The result is a system where:

the architecture is visible and intentional
the implementation follows a consistent pattern
repetitive infrastructure is generated instead of hand-written

This is not about generating code faster. It is about generating code correctly and consistently, in a way that preserves the structure of the system over time.

The techniques in this book use simple tools—YAML, Python, and Jinja2—but the goal is not the tools themselves. The goal is to move from programming at the level of syntax to designing at the level of systems.

This approach is especially relevant for embedded and systems software, where control, predictability, and long-term maintainability matter.

If you have worked on systems that became difficult to reason about as they grew, this book offers a different path.

","authors",[53],{"_9":54,"_55":56,"_5":57},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci84Mjc3MQ","name","Mark E. Wilson",{"_58":59},"avatar",{"_60":61,"_62":63,"_64":14},"url","https://d39qdlcrvnra4b.cloudfront.net/avatars/3631613/medium/avatar.jpg?1775143504","styleName","medium","exists","currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author