I build products end to end across backend, web, desktop, mobile, deployment, and AI. My personal projects are used by 100,000+ people.
Selected Work
Open-source desktop AI assistant for real-time interviews and calls. It combines screen/audio capture, an always-on-top overlay, and live model responses into a tool that people could actually run locally.
The edgy name came from a joke among friends; I never expected the project to blow up.
The project grew to 90,000+ downloads and 5,300+ GitHub stars with zero paid marketing, and was sponsored by Recall.ai.
It also became a public open-source licensing story. A YC-backed company cloned the project into Glass, removed the original history and attribution, relicensed GPL code as Apache, and presented it as their own product. After my Hacker News post reached 947 points and 506 comments, they corrected the license, apologized to me and the open-source community, and credited me on their project page.
Open-source Notion-style workspace and document editor built with vanilla JavaScript and Web Components. I built the editor core, block system, plugin architecture, themes, templates, and document interactions without a frontend framework or build-heavy stack.
Wisk supports rich document blocks including LaTeX, charts, canvas, code blocks, citations, and custom plugins. It works offline as a PWA, autosaves locally, and can import/export Markdown, JSON, ZIP, PDF, and DOCX through LaTeX-backed export flows.
The open-source frontend is fully functional standalone, while Wisk backend services power sync, real-time collaboration, publishing, sharing, and AI writing assistance. The project led to document-editor work at Context.ai after their CPO found it. GitHub
Mobile app for controlling dev environments running on your own infra. The app is an Expo/React Native client paired with a local Node.js CLI, Bun manager/proxy services, and a Rust PTY binary for real terminal sessions.
The hard part was making a phone feel like it was sitting inside the developer's machine. Lunel Connect handles QR/session pairing, dual control/data WebSocket channels, filesystem operations, git commands, process management, system monitoring, and terminal spawning without making users set up SSH.
We also built a custom mobile UI on top of OpenCode and Codex, so remote agents could be used from a phone without forcing the desktop terminal workflow onto a small screen.
It also has browser port forwarding: a dev server on the computer at port 8000 can be opened on the phone by visiting localhost:8000. No router changes, no ngrok setup, no manual tunnel. The mobile browser includes custom DevTools, and terminal access is tunneled end-to-end encrypted instead of exposing SSH.
Reached 7,000+ downloads in 6 weeks and 1,000+ GitHub stars with zero paid acquisition. GitHub ยท App Store
Background
Professionally, I spent 2.5 years working on backend systems and DevOps in Go across two companies. Outside work, I learned by building and shipping my own tools, many of which became real products used by thousands of people.
I have used Arch Linux as my daily environment for 6+ years, which is where I picked up a lot of my open-source, systems, and developer-tooling instincts.
What This Means
I have shipped backend systems, frontend apps, mobile apps, desktop apps, AI products, DevOps infrastructure, and production deployments used by thousands of real users. These were not isolated tickets; I owned the full path from idea to working product.
I am also an extensive user of AI in daily engineering workflows, and I have built products around AI rather than only experimented with it. I started with ChatGPT and Claude in their web apps, spent months building with Cursor and Claude Code, and now use Codex heavily. I treat these tools like an extended working brain: I keep the product ownership, architecture, and design decisions in my head, then use AI to prototype faster, explore alternatives, and ship polished products that still feel intentional.
I also care about product design. The projects above are not just technical demos; they are intentionally designed tools that people installed, used, shared, and built workflows around.