Skip to content

Book a call

Eugene, Oregon · one person, whole builds

Tagged

Case study

7 posts on case study.

Grace Tarnasky's site, from launch-ready to public

Her palette arrived as a document she had written herself, the headline on the home page is her own sentence, and the fork carried three themes before the quiet one won. Here is what the site is made of, and what ten gated days bought before anybody outside her family could see it.

A native investing app in Rust that vetoes its own orders

For the first week of this project's life, an account that came back empty read as approved. Every percentage rule in the risk engine was guarded against dividing by zero, and a guard like that carries a second meaning nobody intends. The trading terminal I open-sourced in June is one long argument that a check which cannot run has to answer no.

What a therapy practice website should never ask for

The federal definition of individually identifiable health information covers anything a provider receives that relates to a person's mental health or condition and can be tied back to them. Not diagnosis, not treatment: condition. So the website for my own counseling practice never asked for a history, never held a calendar and never took a card. Every other decision on it followed from that one word.

StayEugene: when one house is five bookable listings

StayEugene sells five short-term rentals direct, and four of them are the same building cut at different sizes. That makes availability a question about a set of listings rather than a row in a table, and it is the part of a booking site that a marketplace was quietly doing for you all along.

Twelve neighborhood guides and one valuation form

A market report is accurate and generic; a neighborhood guide is specific and goes stale. Grace Tarnasky's site runs both and joins them with a five-digit number. What each half is for, where the data comes from, what a guide is not allowed to say, and why the valuation form refuses to guess.

One engine, three client sites: the fork per client model

Three live sites share one CMS engine and share nothing at runtime: separate repositories, separate keys, separate databases, separate hosting accounts. The bill for that isolation arrives every time I fix something in the engine, because a fix lands in one copy and has to be carried to the rest. Here is the ritual, the path a real security fix took, and the four ways the sweep has quietly failed on me.

Building a real estate site for a realtor in The Dalles

Grace Tarnasky messaged me on a Thursday and had a working site on Saturday. A walkthrough and a look at the decisions: why her listings are real pages instead of an IDX iframe, why six neighbourhood guides matter more than a search box, and what a fork of an engine buys you.

← All insights