Four Years in the Construction Trailer

Before I wrote production software, I spent four years working in construction, and years alongside that on film sets starting as an unpaid production assistant. Neither place looks much like a technology company. Both taught me more about how complex systems stay honest under pressure than anything I later read about software architecture.

Walk into a construction trailer at seven in the morning and the first thing you see is a set of drawings unrolled across a plywood table, covered in red ink, coffee rings, and dated clouds. Nobody in that trailer believes the original architectural drawing is reality. Everyone knows the drawing is a hypothesis that meets dirt, utility lines, municipal inspectors, weather, and budgets the moment excavation starts.

Software culture often treats reality the other way around. Engineers fall in love with clean schemas and automated pipelines, then treat every messy human exception in the field as user error.

Why physical industries invented the submittal and the RFI

In a construction trailer, I was usually one of the youngest people in the room, listening to superintendents, foremen, and subcontractors who had been building for thirty years. Most of the time, their instincts were right because they had seen concrete crack and schedules slip in every conceivable way.

At the same time, sitting in those meetings showed me two distinct things at once. First, seniority can sometimes close a valid question too early when “that is how we have always poured it” stands in for an explanation. Second, the industry’s core paperwork rituals exist for deeply rational reasons that outsiders constantly underestimate.

Take three ordinary artifacts from a job site:

1. The Request for Information (RFI): When a crew opens a wall and finds field conditions that contradict the plan, they do not quietly improvise a structural change and hope nobody notices. They pause that narrow scope, document the discrepancy, and route a written question to the engineer of record.
2. The Submittal: Before critical material is fabricated or installed, its exact specification is put on the table and stamped reviewed by a named person with the authority to accept it.
3. The Change Order: Scope, cost, and schedule do not drift silently in the background. If a decision alters money or commitments, both sides sign a dated record explaining what changed and why.

From a distance, Silicon Valley looks at those steps and sees “friction” begging to be disrupted. Up close, you realize those boundaries are the only reason a building stands up without endless lawsuits. They separate everyday execution, where crews move fast with autonomy, from irreversible thresholds where human judgment and legal responsibility must attach to a name.

Film sets run on the same contract

Film sets look chaotic to visitors: C-stands moving down narrow hallways, gaffers running cable, daylight fading outside a motel window while twenty people wait on a single camera reset. Yet a good set has remarkably low ambiguity about authority.

Every morning begins with a call sheet. Everyone knows who owns camera, who owns sound, who calls a safety hold, and who approves moving on from a setup. When I took production assistant gigs early on, hauling gear and locking down sidewalks on shoots that had nothing to do with my own creative taste, I was absorbing how a temporary institution coordinates dozens of specialists who may have met forty-eight hours earlier. Later, working on Matchmaker Motel and directing my own films, I relied on that exact spine.

Notice what makes both a film set and a job site work:

• Roles are explicit, not implied. Nobody wonders whether an assistant editor is authorized to lock picture for a client, or whether a delivery driver can approve a structural substitution.
• State transitions happen in public. “Picture is up,” “rolling,” “cut,” and “moving on” are spoken aloud so every department updates its mental model together.
• Speed comes from clear boundaries, not missing ones. Because everyone trusts that safety and sign-offs are guarded at the right gates, crews can move fast everywhere inside those gates.

Where software gets governance backward

Most institutional software fails at one of two extremes.

Legacy enterprise software confuses governance with exhaustion. It sprays permission checkboxes, modal warnings, and twenty-field forms across trivial tasks until staff click through warnings reflexively just to get their afternoon back. When everything requires a ceremony, nothing actually receives scrutiny.

Newer “agentic” software often swings to the opposite mistake: it tries to dissolve boundaries altogether. An autonomous workflow drafts an email, updates a financial classification, or submits a filing in the background because minimizing clicks looked good in a product demo. That feels effortless right up until the day an automated action misstates restricted grant funds or sends an unreviewed commitment to a board chair or foundation officer.

The lesson I carried out of construction trailers into Mind Light is simple: automate the legwork, never the signature.

Let software do the exhausting mechanical work that burns people out: parsing messy CSV exports, cross-checking totals against ledger rows, surfacing upcoming grant obligations before they slip, assembling the exact source citations behind a draft report, and checking our own engineering changes through deterministic gates before anything reaches production.

Then, at the exact moment where money moves, an external promise is made, a public surface changes, or sensitive records are touched, stop the machine cleanly. Unroll the drawing on the table. Show what changed in red ink. Name the human with the authority and the context to decide, and wait for their word.

Good tools do not replace human responsibility. They clear enough noise out of the trailer that people can actually read the blueprint before they sign it.