Software design & testing

TDD, domain modelling, and the boundaries that make code safer to change.

8 published entries

Begin with a path

These series give this subject an intentional reading order.

TDD & Software Design

A path through tests, boundaries, and the design decisions that make code safer to change.
See the 8-part reading order →

All writing

1 Aug №40

TDD in the Age of AI: Who Tests the Tests?

I use Codex and Pi daily. They write code faster than I can read it. Lines appear on my screen in seconds that would have taken me twenty minutes to type.

Software design & testing 8 min

29 Jul №38

The Result Pattern: Why I Stopped Throwing Exceptions

Every production Node app has seen an Unhandled Exception crash the process. If exceptions are so great, why does every function have an invisible contract that says “I might throw, good luck figuring out what”?

Software design & testing 10 min

26 Jul №36

I Stopped Mocking Everything in TDD

I once spent three hours debugging a test that was 80% mock setup.

Software design & testing 12 min

21 Jul №33

DDD Aggregate Boundaries and Persistence in TypeScript

The previous articles — Value Objects & Entities and Aggregates & Repositories in TypeScript in particular — made a few choices without naming them: Order owns its lines, only OrderRepository persists them, and a customer appears in an order as an ID rather than as a loaded object.

Software design & testing 10 min

16 Jul №31