TDD consulting for teams building Go, Erlang/OTP, and financial systems that can't afford to be wrong.
Embedded mentorship and workshops to move your team from test-last to test-first — for good. Covers red-green-refactor cycles, test boundary design, and fixture strategy. Available remote or on-site.
ADR-driven design sessions that catch architectural flaws before they calcify. Includes testability audits that identify seams where dependencies should be abstracted for clean unit and integration testing.
Correctness-first consulting for core banking, double-entry ledgers, and payment infrastructure. Integer arithmetic, idempotency proofs, and audit trails built in from day one.
Go beyond happy-path examples. I introduce PropEr, rapid, and custom generators that stress your invariants across thousands of inputs — exposing edge cases that example tests never reach.
Fault-tolerant system design using OTP supervision trees, Common Test suites, and "let it crash" philosophy — hardened with full integration test coverage and production-grade releases via Rebar3.
Multi-agent pipeline design that raises team productivity without sacrificing code quality. I show teams how to integrate LLMs into the development cycle with TDD gates — so output stays verifiable and maintainable.
I read your codebase before I say a word. Coverage reports, test quality analysis, architecture documentation, and a full testability audit with written findings. Starting from scratch? I design your test strategy end-to-end.
From a single architectural decision to a full development plan — research, competitive analysis, test design, observability strategy, and documentation. Technology and industry agnostic. Tailored to your stack.
Remote training sessions, ongoing PR reviews, and custom coaching. Every new feature ships test-first, with automated verification gates and manual checks you can run yourself.
Documentation, runbooks, and coaching that outlast the engagement. When we're done, your team owns the practice — equipped to ship reliable software for the lifetime of your product.
I start with discovery and a codebase audit, then define a practical test-first plan for your team. Engagements combine pairing, review feedback, and measurable delivery checkpoints so TDD becomes a reliable day-to-day habit.
Property-based testing verifies invariants across large input spaces instead of checking only a few hand-picked examples. It is especially useful for financial logic, concurrency behavior, and edge cases that escape example-based tests.
Yes. I identify high-risk paths first, add characterization tests around current behavior, and guide incremental refactors behind safety checks. This approach improves confidence without forcing a full rewrite.
Yes. Most engagements are remote and include recurring pairing sessions, PR review loops, and async guidance between sessions. On-site time is optional when a team needs focused kickoff or workshop support.
A decade of production engineering across financial infrastructure, distributed systems, and modern web. Every line I deliver ships with a test that proves it works and a refactor path that proves it's maintainable.
A test suite that does not fail when the code is wrong is not a safety net -- it is a false sense of security.
Read the codebase before you touch it. Architecture decisions made blind become debt that compounds forever.
Integer arithmetic is not optional in financial code. Floating point errors compound. So do the lawsuits.
The best documentation is a test that fails when behavior changes -- and a human-readable name that says why.
Taking select consulting engagements. Whether you need a full TDD transformation or a focused architecture review, reach out and we'll scope it together.