Keystone要石
Desktop app for benchmarking post-quantum cryptography and hybrid encryption workflows. Native performance where it counts.
ElectronC++TypeScriptReact
Portfolio ·
MIKOSHI
Product Engineer
Surface and spine, one pass.
- Stack
- Next.js·TypeScript·Supabase·Postgres
- Systems
- PQC·Electron·C++
- Sector
- Bucharest·Remote EMEA
»SELECTED.WORKS04 / 04
Built to survive handoff.
Product surfaces, secure tooling, and platform interiors — recent and current.
Scroll to traverse. Follow the work when something holds.
»SHRINE.LOG / RECENT.ACTIVITY07 entries
Shipping.
Enough branch history to show the concept doesn't outlive the build.
07 recent entrieslatest ca4958fmain active
chore: ignore local worktrees
10h ago
updated creative tech landing page design
10h ago
fix: react server components CVE
9w ago
style: updated mercenary theme
3mo ago
feat: create theme system
3mo ago
feat(entry): real preload + stable audio handoff
3mo ago
style(loading): overhaul loading screen
3mo ago
Brandon Aron
a.k.a. Ishmael — Product Engineer, systems-oriented full-stack.
Bucharest · Available · Async / Remote / Embed
Product engineering from the Bucharest sector. I build the surface and the spine in the same pass — authored interfaces on top of the backend, data, and systems work that keeps them honest.
Taste is the spec I hold hardest; the rest is daily craft. Typed stacks, tight migrations, interaction detail that survives first contact with a real user. Next.js, Postgres, and the interior kit — whatever the shape actually is.
Design-led, not design-only. The work ships, stays shipped, and reads like someone cared.
»CONTACT·OPEN CHANNEL
Open for precise work.
Available for contract, full-time, and embed work.
I read everything. Reply within two days.
PRIMARY CHANNEL
Brief first.
Build after.
Contract, full-time, or embed. Send the scope, timeline, constraints, and the decision you need help making; I will answer with fit, next questions, and a clean path forward.
Need a call or private channel? Ask in the first email.
» SECONDARY
Adjacent
proof.
Source is public when it helps the conversation. Private channels come after the first fit check.
Email starts the thread. Private channels follow fit.
RITUAL / AVAILABILITY
Specific briefs, clear scope, and the kinds of product or systems problems that benefit from close authorship over long meetings.
