Expertise
Complex systems.
Clear thinking.
The practices and experience behind my work: event-driven architecture, Domain-Driven Design, distributed systems, and AI-assisted engineering. I care about systems people can understand, operate, and evolve.
In focus / AI-assisted engineering
Use AI.
Keep your engineering judgment.
I build tools for AI-assisted software development. Aktum, currently in beta, routes open questions in AI-written specs to a named person and commits their decisions to the repository. Whetstone is a private Rust CLI project, with deliberate practice and knowledge-retention tools planned.
- Reviews of specs, plans, and AI-generated code by a human architect.
- Deterministic guardrails around nondeterministic LLM components.
- Spec-driven development workflows, skills, and agent harnesses.
- Verification culture that keeps engineers sharp.
01Distributed systems architecture
Resilient platforms. Explicit contracts. Events you can trust.
- CQRS, event sourcing, and sagas
- Messaging with Kafka, RabbitMQ, and SQS/SNS
- Delivery guarantees, retries, and backpressure
- Tracing, metrics, and production observability
02Domain-Driven Design
Make the software speak the language of the business.
- Context mapping and bounded contexts
- Event Storming: Big Picture to Software Design
- Aggregates, value objects, and domain services
- Integration contracts and schema evolution
03Sane AI adoption
Faster delivery. Engineers who can explain what shipped.
- Independent reviews of AI-generated systems
- Guardrails around nondeterministic LLM components
- Spec-driven workflows and agent harnesses
- Review discipline and skill-atrophy prevention
04Modernization & enablement
Evolve the system. Grow the people building it.
- Strangler Fig migrations and anti-corruption layers
- Modular monoliths and clear service boundaries
- Hiring, mentoring, and engineering standards
- CI/CD, infrastructure as code, and delivery governance
05Architecture validation
An independent view of risk, reliability, and what comes next.
- Architecture and resilience audits
- Observability, SLOs, and audit readiness
- Technical due diligence and replatforming reviews
- Practical modernization roadmaps
How I approach the work
No methodology theater.
01 / Look
Understand first.
I start with code, architecture docs, and incident history before I form an opinion.
02 / Work
Build together.
I work alongside engineers, in the codebase, respecting the constraints the team actually has.
03 / Share
Keep the knowledge.
The reasoning, decisions, and documentation should stay with the people who maintain the system.
The toolbox
Boring technology.
Chosen on purpose.
Architecture
DDD, context mapping, contracts
Distributed systems
CQRS, event sourcing, routing
Messaging
Kafka, RabbitMQ, SQS/SNS
Data & storage
PostgreSQL, Redis, MongoDB, DWH
Cloud & infrastructure
AWS, Azure, Kubernetes, Terraform
Observability
OpenTelemetry, Prometheus, Grafana