howmanysmall

Contact

Based on Mountain time. Either route reaches the same inbox.

Useful context beats polished outreach.

I'm selectively open to relevant engineering roles, open-source collaboration, and concrete technical ideas. A short message with the actual problem is plenty.

Write

Your message is checked in the browser, checked again at the edge, and delivered straight to my inbox. No mailing list and no CRM handoff.

Start with the actual problem.

A useful first message needs context, not ceremony. Every field has a job.

Choose the closest fit. It only helps route the context.

Specific beats formal. Three to 120 characters is plenty.

Include constraints, links, or timing when they matter.

Protected by Cloudflare Turnstile. No tracking puzzle required.

Good reasons

A few ways this can be useful.

  • Tooling and platform work

    Roles where fast tools and reliable systems matter.

  • A scoped collaboration

    Bring a repository, a real problem, and a plausible contribution.

  • A bounded experiment

    Bring an implementation question or something concrete to test.