selected work / notes / experiments
Software engineer / systems, tooling, and verification
I work on software where the surface and the internals both matter: study tools, privacy-heavy systems, verification paths, and machine learning with a clear job to do.
selected work
A correctness harness for BIP 352 Silent Payments implementations, with differential adapters, replayable regressions, and release-verification lanes.
Maintainer-acknowledged upstream bug reports across multiple implementations, with one reduced case later folded into merged BIP-352 test-vector coverage.
An exam-prep platform that turns scattered study material into a more usable learning system with OCR, adaptive practice, and collaborative tools.
Open-source exam-prep platform connecting OCR ingestion, structured question banks, practice flows, analytics, and discussion in one system.
A 4-bit RISC-inspired microprocessor with banked memory, a custom ISA, and a verification workflow built in public.
Custom ISA, assembler tooling, and a simulation-first verification workflow that make the architecture testable rather than decorative.
writing
On narrative foreclosure: when pain stops being one chapter and starts deciding which futures still feel possible.
On the overjustification effect, reward, and how a private reason can be replaced while the hand still keeps moving.
what stays consistent
The domains can change. The standard does not: understand the problem fully, choose the shape with restraint, and make the engineering stand up in real use.
Note 01
Make the product easy to trust before trying to make it impressive.
Note 02
Let the architecture do the heavy lifting quietly.
Note 03
Keep choosing work that stretches judgment, not just output.
