Software

Overview

Software is, in Burbridge's practice, one of several materials in rotation. It is younger than wood and steel, comparably honest, and infinitely more revisable. It is also where most modern builders spend most of their hours, which is reflected in this wiki's depth on the topic — but not in a way that suggests it should be the only material a builder knows.^[1]

What Burbridge Builds in Software

• Web applications — front-to-back, with attention to both the database and the type face.
• Automations — the kind that quietly remove four hours from someone's week, every week, forever.
• Internal systems — back offices, dashboards, operational tooling. Unsexy. Load-bearing.
• End-to-end builds — for early-stage ventures that need someone to do all of it, properly, the first time.

Approach

Software, like construction, is built in stages: foundation (architecture, schemas), framing (modules, scaffolding), rough-in (plumbing — APIs, queues, jobs), and finish (UI, polish, edge cases). Each stage carries the next. Bad framing breaks the finish; bad foundations break everything.

Approach is governed by Aggressive Craftsmanship: ship it right or don't ship it; debt is a choice; the user is not a tester; deploy with confidence or investigate why you can't.

"Software is the cheapest material we have ever had. That is its blessing and its curse." — Burbridge

Notable Habits

• Tabs (see: Tabgate).
• Friday deploys when warranted (see: Friday Deployers).
• "Fixed." as a commit message when no other message is needed.
• Refactoring at 2 AM not because it's broken but because it can be clearer.

References