The first thing you notice on a construction site is the noise. Not one noise. Layers of it. Grinders on steel somewhere above you. A concrete pump running steady on the street side. Radios from three different crews bleeding into each other. Diesel exhaust and cut metal and the chalky smell of fresh drywall dust settling on everything.

My father was a general superintendent for general contractors in New York. Bovis, Gotham, Engel Burman. Skyscraper-scale jobs. His mornings started at six, walking the site before any trade showed up. He’d move through it floor by floor, reading what happened the day before, seeing where the next problem would be. By the time the electricians and ironworkers and plumbers arrived, he already knew what he was going to say to each of them.

I was a kid on those sites. I didn’t understand anything about what was being built. What I understood was what was being coordinated. Fifty trades, each one an expert at their thing. A glazier knows glass. A plumber knows pipe. None of them are responsible for how it all comes together. That was my father’s job. He held the whole picture while everyone else worked their piece.

I didn’t know I was learning anything. I thought I was just hanging around.

What comes apart

The thing about being a kid on a construction site is that you see things in a different order than the people building them. The trades work bottom up. Foundation, structure, skin, systems, finish. I wasn’t following that sequence. I was wandering through a building that was half there, looking at exposed framing and open walls and ductwork that would eventually disappear behind drywall. I was seeing the layers before they got sealed up.

That turned out to matter. When you see a building with its guts exposed, you understand that the finished wall is a lie. A convenient one, a necessary one, but a lie. Behind every clean surface is a set of decisions about how things connect, and those decisions are invisible by the time anyone moves in.

Years later, doing color separation for screenprinting, I recognized the same structure. You never work on the image. You work on a channel. One color at a time, each screen built in isolation, the whole composition only existing in your head until the layers register on the substrate. I’d been trained for that without knowing it. Every building I walked through with exposed framing was a decomposed image waiting to be printed.

The joints

My father’s real skill was not coordination. Coordination is logistics. His real skill was knowing where things fail.

A building doesn’t fail in the middle of a trade’s work. The plumber doesn’t mess up the plumbing. The electrician doesn’t mess up the electrical. It fails where one trade’s work meets another. The joint between the ductwork and the framing. The transition from foundation to structure. The place where the waterproofing has to hand off to the flashing. Every failure he anticipated was at an intersection.

I carry that. When I look at any system, software or otherwise, the first question I ask is: where does this fail? And the answer is almost always at the joints. Where one person’s responsibility ends and another’s begins. Where one layer meets the next. Where the handoff happens.

The gap

My father read constantly. History, trade journals. He thought about his work at a level that didn’t match the setting. The guys on the site respected him because he could solve problems on the ground, with his hands if necessary, in the weather, under pressure. But the reason he could solve them was that he’d already thought through the whole structure before the problem arrived. Blue collar setting. Intellectual operation.

I didn’t have language for that when I was young. I just knew that the adults around me were doing sophisticated work without performing sophistication. Nobody on a job site talks about systems thinking. They talk about getting the steel up before the concrete crew shows up on Thursday. But the planning underneath that conversation is as rigorous as anything happening in an office with whiteboards and post-its.

That’s where I learned to work. Not in a classroom, not from a book. From watching someone hold a building in his head while standing in mud, and from the fact that when he left a site, the picture left with him. Everything I’ve built since has been shaped by both of those facts. The holding, and the leaving.

When he walked off a job, the next person had to reconstruct the whole picture from scratch. The knowledge lived in him, not in the system. I watched that happen enough times to know it was a problem worth solving. Not because my father did anything wrong. He did it exactly right, for a job that only one person was doing at a time. The problem was the format. A building’s worth of coordination stored in one head, with no way to hand it off intact.

I didn’t know I was going to spend the next twenty years trying to fix that. I just knew it bothered me.