Notes on what breaks between the system and the people using it. Solo operator.
Vendor Relations
A relationship between two people across two organizations. One leaves. The contract continues — but the implicit understanding that made it work is gone, and nobody notices until something needs renegotiating.
Operations
A production system fails outside business hours. The fix requires understanding a component integrated under pressure and never properly documented. The on-call engineer pays the cost of decisions they never made.
Estimation
A scoping conversation produces a number. Both sides treat it as a price. Neither side treated it as one when it was said. The number becomes load-bearing without ever being chosen.
Operations
Building in public was meant to make solo work less lonely and more honest. Somewhere along the way it tilted: the work and the broadcast became the same activity, and one started shaping the other.
Handover
A long-tenured person leaves. Standard offboarding happens. Months later, decisions take longer and feel less confident. The thing that left was never written down — because nobody knew it was there.
Handover
A critical transition was planned, discussed, and assumed to be in progress. It wasn't. Each person had a reasonable model in which someone else had it covered. The pattern is what happens when ownership lives in the gaps.
Change Management
A return to social media, a domain that finally found its purpose, and one observation that will make or break a start-up: AI can build the product, but it cannot repair what breaks between the business and the client.
Operations
Billing. Support. Product trust. Marketing. Failures rarely come from code — they come from decisions. A record of recurring failures in modern software operations.