This series explores the scalability benefits of pure domains. This post explores how pure domains reduce the rigidity of request and response timing and structure, enabling more control over our API experience.

This series explores the scalability benefits of pure domains. In this post we explore how pure domains enable sophisticated concurrency rules without modifying the domain.

This series explores the scalability benefits of pure domains. This post explores how pure domains mesh well with common system tools: async messaging, logging, and caching.

This series explores the scalability benefits of pure domains. This post introduces important terms and ideas with some examples.

I’ve been trying to identify a minimal set of factors that guide how I write self-documenting code. It seems these may be sufficient: naming, proximity, consistency, and scope.

Checklist Manifesto paints an facinating journey of a surgeon who discovered checklists. The book explores checklists across industries and applications, but one lesson pervades them all: use checklists to distribute power.

My duck docs continue to evolve as my process changes. Here are changes I’ve noticed lately.

This is my attempt at short actionable checklists to guide key moments in software process.

I read that stuckness is not a bad thing. It is avoiding our stuckness that is the problem. I think living with stuckness is part of why duck docs are so good.

I’ve started some reading lists to help people connect to good software literature.