I design and ship software where correctness is non-negotiable: on-chain contracts that move value, and backend services that keep organizational data consistent. My approach is simple, and it shows in my pull requests:
Specify it. Implement it. Document it. Prove it with tests.
Most of my recent work is open-source contribution to production-grade projects, where every merge has to survive code review, CI, and maintainers who care about quality.
| Domain | What I do |
|---|---|
| Smart Contracts | Rust contracts on Stellar's Soroban: escrow-style job flows, bidding, deliverables, state machines |
| Contract Engineering | Structured event emission, explicit error handling, snapshot-tested behavior, Rustdoc-level documentation |
| Backend Services | Modular feature work (e.g. company-level settings and configuration modules) in TypeScript codebases |
| Open Source | Scoped, review-ready PRs that close real issues, with docs and tests included |
|
A decentralized freelance job marketplace (JobRegistry contract) A full job lifecycle, implemented function by function: |
Asset management platform
|
ISSUE ──▶ DESIGN ──▶ IMPLEMENT ──▶ DOCUMENT ──▶ TEST ──▶ MERGE
│ │ │ │ │ │
scoped edge cases typed events Rustdoc snapshots reviewed
to one & failure over ad-hoc + docs/ + 90%+ by
concern modes first tuples guides coverage maintainers
Principles I hold myself to
- Typed over ad-hoc. Structured events and explicit errors beat tuples and panics.
- Docs ship with code. If a function is public, it is documented in the same PR.
- Tests are the spec. Behavior changes must show up in the snapshots.
- Small, reviewable diffs. One issue, one PR, one clear story.
Contribution graph
I'm open to contract-based smart contract work, backend roles, and meaningful open-source collaboration.
"Ship less, but ship it right."