I build software and make it look right.

A minimal Jekyll publishing template for people who want to write rather than configure. Fork it, edit one commented file, push. All personalizable settings live in one commented _config.yml, so a fork can change identity, color, typography, and metadata without touching template code.

The engineering position is that a reading page should cost the reader almost nothing. The stylesheet is one unminified 17.3 KiB file, and the entire client-side JavaScript payload is 1,619 bytes — a 600-byte inline theme script and a 1,019-byte copy button, the second of which only loads on pages that contain code. There are zero third-party requests: no web fonts, no CDN, no analytics, and therefore no cookie banner to dismiss.

The core reading experience works without JavaScript. The table of contents and heading anchors are generated in Liquid, footnotes are rendered by Kramdown, and optional theme and copy controls disappear cleanly.

DESIGN-PRINCIPLES.md documents the major decisions with named usability laws and measurements, so a fork can distinguish structural constraints from taste.

A communication coach designed for a local data path: Ollama for inference and SQLite for history, with no account or hosted API key. The default configuration stays on the machine; pointing OLLAMA_URL at another host changes that privacy boundary and triggers a warning.

The model proposes; the code decides. The app parses model output defensively, caps reported confidence using observable signals such as message length, tone clarity, and missing context, then applies six deterministic rules. The generative layer drafts; the tested rules layer constrains the final action.

The prompts draw on Nonviolent Communication, DBT's DEAR MAN, and a cool-off rule informed by conflict research. Parsing and deterministic rules are covered by tests.

The biggest system I've put together so far: a React application that reads a body of canonical planning documents and renders a reconciled queue and decision record from them. It is a derived surface that never outranks its sources — if the app and a source document disagree, the document wins and the app is the bug.

There is no third-party UI kit — no shadcn, Radix, or animation library. The repository implements its own interface primitives; I chose that constraint to study accessibility and motion behavior directly.

It is deliberately not deployed. A loopback-only Node HTTP server fronts the local SQLite store; deployment is a standing policy decision, not a backlog item. The local boundary is deliberate and tested.

Privacy boundaries are enforced in code and verified by guard suites. The shareable-kit build uses an explicit allowlist and SHA-256 manifest; separate endpoint, embedding, and path-traversal guards reject disallowed paths and destinations. The copy pipeline validates before replacing its live output.

A personal brand system built the way a product design system is built: one source of truth for color, type, space, radius, elevation and motion, shipped as CSS custom properties with a JSON mirror for non-web surfaces. Two type families, four radius tokens, and five duration tokens.

Contrast ratios and WCAG levels are documented alongside text-color tokens, with AAA body text in both light and dark modes. Motion uses an overdamped easing curve and a near-critically damped JavaScript spring, both designed to avoid overshoot.

Ten versioned revisions, each documented in the changelog. Six internal reference kits — site, deck, résumé, social, case study, and documents — consume the shared token foundation and add surface-specific styling.

This page is built on it. Same tokens, same two faces, no third family.

An archived local Mac voice-assistant prototype that connected speech-to-text, a local language model, speech synthesis, and a SwiftUI orb through a WebSocket bus. It was an interface experiment, not a hosted service.

The default configuration put an explicit confirmation gate before proposed shell, file-write, or AppleScript actions. That boundary mattered more than making the assistant feel autonomous.

Project notes record roughly 2.5 seconds end-to-end on an M4 Pro. That is a machine-specific measurement, not a general performance promise.

It remains offline because it depends on a local microphone and local models, and because publishing its machine-action surface would change the safety model.

Plain HTML, CSS, and JavaScript, published through the repository's Jekyll build. No application framework or client runtime dependencies; no third-party requests on initial load beyond the hosting provider serving the page.

The brand faces are self-hosted and subset to the characters this page uses, which took 1.14 MiB of source TTF files down to 94.2 KiB of WOFF2 across five weights. The wordmark is real outlined path geometry rather than text set in a font, so it renders identically whether or not Inter loads. Theme resolves before first paint, so there is no flash of the wrong palette.

Interactive controls use native HTML — links, buttons, inputs, <details>/<summary>, and <dialog> — rather than div-based widgets. The platform supplies baseline semantics; JavaScript adds palette behavior and focus restoration. Motion respects prefers-reduced-motion; project disclosures remain readable without JavaScript, and document order remains sensible without CSS.