Field notes from building useful digital systems.

Detailed, reusable thinking on workflow design, static-first delivery, deployment verification, and product reliability.

Focus
Practical implementation
Format
Long-form field notes
Cadence
Evidence over volume

Four foundations worth getting right.

No trend summaries or filler. Each note documents a decision framework that can be applied to real project work.

01Internal systems7 min read

From spreadsheet workflow to internal system

A practical framework for deciding when a spreadsheet has become operational infrastructure and how to replace it without losing the workflow knowledge inside it.

  • Map decisions and exceptions before screens.
  • Preserve useful workflow knowledge instead of recreating the spreadsheet literally.
Read article
02Delivery8 min read

How to verify a deployment automatically

A deployment should prove which commit is live, whether critical routes work, and whether performance and SEO stayed inside agreed thresholds.

  • Verify the deployed artifact, not only the local build.
  • Tie production checks to a commit identifier.
Read article
03Web architecture8 min read

Static-first Next.js without unnecessary runtime

How to use the App Router as a build-time composition system while keeping public pages deployable as plain HTML and CSS.

  • Server Components are the default for content-heavy public pages.
  • Runtime removal must fail closed when application client modules exist.
Read article
04Product architecture7 min read

Architecture for a reliable local-first product

Design principles for operational software that must keep working locally while still supporting exports, dashboards, and controlled recovery.

  • Offline availability changes persistence and recovery requirements.
  • Atomic writes and validation protect operational state.
Read article

Turn one recurring problem into a clear project boundary.

Use the project brief to describe the current process, constraints, and result the business needs.