Systems thinking is the same skill in code and in life

A data pipeline, a photograph, and a trip itinerary don't look related. But building all three well requires the same move: take something raw and unstructured, find the constraints that actually matter, and construct something that makes it legible to someone else.

A pipeline imposes structure on raw events. A photograph imposes structure on a scene through framing and exposure. An itinerary imposes structure on a place through sequencing and trade-offs. The skill isn't domain knowledge — it's recognizing which structure is worth imposing and which is premature.

I used to think of engineering and creative work as different modes I switched between. They're not. They're the same instinct, pointed at different raw material.