Mostly Unprompted

a software engineer's journey into the world of AI.

The Useful Detour

Why the indirect route can reveal the shape of the work.

Plans are good at getting us to destinations we already understand. The trouble begins when the destination is only a hunch.

In that kind of work, a detour is not necessarily a delay. It can be an instrument: a way to encounter constraints before we have learned how to name them.

Follow the resistance

When a supposedly simple step keeps producing friction, the instinct is to push harder or work around it. Occasionally that is correct. Often the resistance is information.

It may reveal that two ideas we grouped together want to be separate. It may show that the tool has begun dictating the result. It may simply tell us that the question is not interesting enough yet.

The useful detour starts with asking what the friction knows.

Return with evidence

Wandering alone is not a method. A detour earns its place when it changes what happens next. Bring something back: a sketch, a contradiction, a sharper question, or one small decision that is now easy to make.

Then the indirect route becomes legible. It was not time away from the work. It was how the work found its outline.