Journal

Field notes on software, proof, and building better sites.

Writing from the Outlyne team on taking existing sites and making them work harder.

The Outlyne editor, whose React interface is protected by compiler linting

React Compiler Linting Just Got a Rust-Native Speedup in Oxlint

Oxlint’s native React Compiler rules cut Outlyne’s lint time from about 29 seconds to 9, without giving up bailout protection.

Read article
Desert sand ripples beneath a starry night sky

React Compiler’s Silent Failures (And How to Fix Them)

Depending on React Compiler means knowing when it fails—and making those silent bailouts break the build.

Read article
A redesigned service-business website generated in Outlyne

Stop paying a developer to change a sentence.

Routine website edits should feel routine. Save specialist help for the work that actually needs a specialist.

Read article
A service-business website shown beside the reviews earned on its Google listing

Your best proof is stranded on a listing.

Five stars on Google and none of them anywhere a customer is deciding. Proof works hardest on the page where the decision happens.

Read article
A website page ending in a clear call to action

Every page needs a next step.

A visitor who runs out of page should never have to invent what to do next. The next step is content, not chrome.

Read article
A business website moving from draft to published

Publish before it feels finished.

Waiting for perfect costs weeks of a good-enough site doing real work. Live pages improve faster than drafts.

Read article
Search results showing a local service business

Getting found is part of the job.

The website does not create demand by itself, but it decides how much of your existing attention converts, and search is where that attention starts.

Read article

Try it yourself

Your current website is enough to begin.

Paste the URL. Get a stronger first draft.