01Build
React and Three.js on the front, Node, Express and SQL behind them, Docker and Nginx underneath. C# and ASP.NET Core when a job calls for it. I build the thing and then I run it.
The front end
Most of my thinking time on a React project goes into data flow rather than layout. Which component owns which piece of state, how it gets from the server to the screen, and what the page does on the third render when the data still hasn't arrived. I work mostly in React and Next.js.
The back end
On ChromoXplorer the Node service exists so the browser never has to deal with raw bioinformatics files. It does the parsing and shaping, and what crosses the wire is already close to what the renderer needs. I take the same approach whether the back end is Node and Mongo, SQL Server or ASP.NET Core. Do the awkward work on the server, where it is cheap to do.
In three dimensions
ChromoXplorer renders genome data as a three-dimensional structure you can move around in. Adjacency and folding are most of what the data is about and a table flattens both, so 3D earned its place there. After that it's a frame budget problem. Geometry built up front navigates quickly and loads slowly, streamed geometry does the opposite, and I spent a lot of that project watching my own scene stutter and going through draw calls to find out why.
Shipping it
ChromoXplorer runs on AWS Lightsail under Docker Compose, with container networking, environment-based secrets and HTTPS terminated at Nginx. The TUDev platform is several separately containerized services behind Nginx Proxy Manager, with Cloudflare handling DNS and CDN, and I still patch it. Most of the debugging on both has been tracing a single failure across the application, the container network and the database to work out which layer was at fault.
Client sites
A therapy practice, a model train restoration shop, a mobile personal trainer, a kennel. The brief is much the same every time: load fast on a phone, make the contact details easy to find, and don't hand the owner something they then have to maintain.
How I work
This site's whole palette lives in one custom-property block, which is a grown-up version of a CSS variables exercise I built back in 2020. I like putting a decision in one place and having everything else read from it. Same reason the CSS clock's hands are three rotation angles, and the drumkit waits on transition events instead of a guessed timeout.
Where I've done this
May 2025 — June 2026
Mitzvah Circle Foundation
I provisioned, imaged and deployed 32 Windows 11 laptops for staff and interns, standardizing the software build and the readiness checks that ran before each machine shipped — OS build, application install, Office activation, identity configuration. I configured Microsoft Entra ID, Microsoft 365 and Google Credential Provider for Windows so sign-in and device management behaved consistently across the fleet, then wrote repeatable support runbooks and trained staff on them. That brought the repeat tickets down and shortened onboarding for new staff.
Work that shows it
A full-stack 3D genome visualization platform — React and Three.js over a Node/Express API, containerized and deployed to AWS.
A containerized multi-service platform — Directus and Wiki.js behind a Next.js front end — that I designed, deployed and still operate.
A C# ASP.NET Core MVC booking application over SQL Server, with stored procedures, REST integrations and no designer.
My first professional site — built for a mobile personal training business serving the greater New York City area.
A site for a model train restoration company, built for a co-worker who restores and details locomotives.
A calm, straightforward site for a therapy practice — built for my mother's business.