Make every release reversible
Keep the current artifact until a new release has passed its health checks. A small, explicit rollback procedure is easier to trust than a late-night reconstruction.
Read the note →Engineering field notesBuild thoughtfully.
Build thoughtfully.
Ship with confidence.
A compact engineering notebook about predictable releases, clear interfaces, and the small decisions that keep websites easy to maintain.
Explore the notes →Small ideas, practical improvements.
Treat HTTP as an interface
Use status codes that explain the result, cache directives that match the resource, and error pages that give readers a useful next step.
Read the note →Keep the dependency budget small
Static content and a little carefully chosen CSS go a long way. Every additional runtime needs updates, monitoring, and a recovery plan.
Read the note →Before releasing
Build once, retain the previous artifact, and validate configuration before switching traffic. After the switch, check the same public URL your readers use. A successful process exit alone does not prove that a page is reachable.
↑ Back to all notesDesign the failure path
A missing page should return 404, retain the site navigation, and offer a way home. Avoid returning a successful status for a broken request; caches and monitoring tools depend on accurate semantics.
↑ Back to all notesChoose a smaller surface
Start with the simplest delivery path that satisfies the reader. Add a dependency when it solves a measured problem, and record who will update it and how it can be removed.
↑ Back to all notesA quieter place for useful ideas.
A focused companion to GitFlare Lab. These short notes are written for people who build and use the web. This site uses no analytics, advertising, third-party fonts, or account system.