Engineering and technical consulting

Developer tooling

Design languages, SDKs, and interfaces that make complex systems easier for other engineers to use.

Who this is for: Developer-platform teams, infrastructure builders, and founders whose users are other engineers.

A developer tool is a product with a technical interface. Its users need predictable behavior, helpful errors, and a clear route from their first example to a real integration. I work across language and compiler design, typed APIs, and contract-driven interfaces, connecting implementation choices to the experience of the person building on top.

Discuss your project

Problems I can help solve

Decisions that shape the implementation

Contracts and compatibility

Define the supported inputs, outputs, and failure modes before expanding the surface area. Treat versioning, diagnostics, and migration guidance as part of the interface.

Separation of responsibilities

Keep reusable semantics distinct from environment-specific mechanisms. Kelft separates compiler work from native host boundaries; an SDK similarly benefits from clear transport and API responsibilities.

Adoption and maintenance

Provide a minimal useful example, realistic integration guidance, and a release path. A tool should be understandable to its next maintainer as well as its first user.

What an engagement can deliver

How we begin

  1. Identify the developer task, existing interfaces, compatibility constraints, and supported environments.
  2. Build a usable vertical slice with examples and explicit failure behavior.
  3. Validate the integration experience and prepare documentation, release boundaries, and handoff.

Related engineering work

Kelft

An AI-native, intent-first language with a self-hosted native compiler.

Multicall SDK

TypeScript tooling for batched EVM contract reads.

ABI Page Builder

A contract ABI becomes an interface for reading and writing functions.

Common questions

Can this be an architecture engagement rather than a full build?

Yes. We can focus on API boundaries, compiler or platform architecture, an SDK design, or a review of the developer integration path, with concrete decisions and next steps.

How do you approach compatibility?

Start with the consumers and versions that must continue working. Define the contract, exercise representative examples, and make breaking changes and migration work explicit.

Bring the problem and the constraints.

We can define a focused build, an architecture review, or ongoing technical collaboration.

Start a conversation

Hiring for a senior or lead role? Read my engineering profile.