Hi, I am the builder behind .
This site is my portfolio and build journal: a place to show what I ship, how I think about problems, and what I learned along the way. It covers web apps, iOS experiments, and AI tooling I make because I enjoy the craft—not because anyone assigned them to me.
The name comes from my creative process. Flint is the spark: the moment an idea feels worth chasing, usually backed by a scrappy spike or a rough prototype. Forge is where that spark becomes something durable—structure, polish, accessibility, and the unglamorous details that make software usable for someone other than me.
I like small surfaces done well, honest write-ups when a build goes sideways, and tools that respect the person on the other side of the screen. If that resonates, wander the portfolio for case studies or the blog for longer notes on naming, process, and dead ends.
What you will find here
- Portfolio — per-project pages with context, constraints, approach, and outcomes. Each entry is a real build, not a mock-up gallery.Browse projects →
- Blog — lighter, longer-form notes: naming, trade-offs, and lessons from shipping side projects. More technical posts will land there over time.Read the blog →
Flint
Curiosity, sketches, spikes, and proofs. I stay here long enough to learn whether an idea has legs—then I move on or commit.
Forge
Execution: architecture, UI fit and finish, performance, and the kind of testing that catches embarrassing bugs before users do.
What guides me
- Ship often, even when the first cut is rough.
- Prefer clear and useful over loud and clever.
- Write down decisions so future-me knows what I was thinking.
- Treat side projects with enough rigor that they could become real products—without pretending they are bigger than they are.
- Respect attention: fast loads, sensible defaults, and copy that sounds like a human.
If you want the short version of the naming story, there is a post for that too.