Work and experiments
Professional work, personal tools, and unfinished investigations
belong here together. Each is a way of testing an idea in the world.
Selected work
Aztec and Noir developer ecosystem
Developer relations and ecosystem design
I led Developer Relations at Aztec, helping developers understand
and adopt difficult cryptographic infrastructure. The work
included education, documentation, workshops, examples, support
systems, ecosystem feedback, and team leadership. Later, I
increasingly explored AI-assisted developer experience and
agent-readable knowledge systems.
Aztec ↗ (external site)Noir ↗ (external site)Developer Relations presentation
↗ (external site)
Bank of JubJub
Privacy and programmable transfers
An exploration of private, on-chain transfers using zero-knowledge
proofs and homomorphic encryption. It asks what programmable
privacy can feel like in an application, rather than treating
privacy as a purely infrastructural feature.
Source code ↗ (external site)
On-device Aztec proving
Android, Noir, zero-knowledge proofs
A native Android proof of concept for generating and verifying
Aztec client-side proofs on the device. It explores what private
application infrastructure might look like when proving,
verification, and eventually wallet flows can move closer to the
person using them.
Source code ↗ (external site)
Can't See Past My Shades
ETHDenver 2024Private applications
A hackathon privacy application suite for ERC-20 tokens, including
sealed-bid auctions, private crowdfunding, and private token
voting. It was an experiment in giving people more agency in the
everyday applications built on public blockchains.
Source code ↗ (external site)
Personal and emerging experiments
DreamLens
developingAI and reflection
An experiment in using AI as an interpretive partner, not to
deliver authoritative answers, but to help people explore
recurring symbols, patterns, and perspectives in their inner
lives.
Visit DreamLens ↗ (external site)Source code ↗ (external site)
Nounish Blockies
archivedGenerative identity
An earlier experiment in generative identity, onchain art, and
composable visual systems.
Source code ↗ (external site)
AI-native developer experience
developingAgents, knowledge systems, developer tools
An ongoing investigation into how developer experience changes
when software is increasingly written by agents: agent-readable
documentation, MCP tools, evals, automated feedback loops, and
interfaces spanning the terminal, IDE, web, and chat.
Aztec Claude Code plugin ↗ (external site)Aztec development environment
↗ (external site)
Beyond OpenClaw
in developmentDetroit workshop
A planned workshop on agentic fundamentals beyond packaged
products: terminal-based harnesses, always-on home servers,
Raspberry Pi systems, Telegram interfaces, home automation, and
multiple persistent agent sessions.
Piano learning experiments
activeMusic, learning
Using and adapting open-source tools while learning piano and
music theory, with an interest in the feedback loops that make
sustained practice more legible and rewarding.
PianoBooster work ↗ (external site)
Back to top
Ideas and notes
This is an early assemblage. Some ideas may eventually become
essays; others may remain provisional notes or open questions.
Documentation as agent infrastructure
seedUpdated July 2026Developer tools
Documentation is increasingly used by more than a human reader. I
am interested in what makes technical knowledge legible to people
and capable agents without reducing it to a pile of retrieval
fragments.
Read the note
Good documentation carries context: why an interface exists, how
it fails, what has changed, and where uncertainty remains.
Agent-readable systems may need the same qualities, expressed in
structures that can be queried, tested, and kept current.
Privacy and meaningful choice
developingUpdated July 2026Privacy, agency
Privacy is not only about keeping secrets. It is part of the
practical space people need to experiment, change their minds,
form relationships, and make choices that are not immediately
optimized by a surrounding system.
Stewarding complexity
seedComplexity, collective intelligence
How might we design systems that help people notice, hold, and
learn from complexity rather than prematurely simplifying it into
control?
Back to top
About
I am based in the Detroit area. Much of my career has involved
helping developers engage with emerging technology, most recently
through developer relations leadership at Aztec and work with
cryptography, privacy, and developer ecosystems.
I am increasingly focused on AI, agents, developer tooling, and
knowledge systems. Outside of work, I keep returning to philosophy,
complexity, collective intelligence, dreams, music, education, and
technologies that support agency.
Across these different domains, I keep returning to the same
question: what conditions allow greater intelligence, agency, and
complexity to emerge?
Back to top