What commit insertions and deletions might tell you
Commit insertions and deletions can reveal churn, unfinished work or oversized commits. I look for patterns rather than treating volume as achievement.
Lynn Cole / Writing
Writing
Essays, thoughts, and technical notes.
Contribution guidelines are constraints for coding agents
Clear contribution policies, reviewable changes, and rejection feedback that tells coding agents what went wrong.
Let the agent own the loop
An agent should start and deliberately continue its own tool loop. This design reverses the usual procedural loop and gives the actor control over continuation.
The fjords came back
A joking instruction about Nordic engineering turned into fjord poetry across the codebase—and returned when one old file was restored.
When outputs become cheap, taste still matters
When outputs become cheap, organizational abstractions start to lose their grip. Governance, memory and taste remain.
When an AI-generated voice becomes an instrument
A generated voice can melt directly into an instrument. I enjoy the strange precision of that effect, even when it complicates a live-performance illusion.
The word agent is losing its precision
The word agent now covers too many different kinds of systems. More precise terms would make the work easier to discuss.
Reasoning bandwidth and recursive depth
Reasoning bandwidth and recursive depth explain failures that token counts alone do not. Context and task complexity need case-by-case treatment.
Thinking sideways about hyper-connections
A way of thinking about manifold-constrained hyper-connections: richer sideways information flow, with geometric guardrails that preserve stability.
Predictions for 2026, written in December 2025
My predictions for 2026, written in December 2025: small models, edge compute, changing tooling, creative technology and the structures of power.
What a vending-machine experiment says about role and memory
The vending-machine experiments leave me wanting better role boundaries, session management and memory. Running out of context should never threaten the business.
Two questions before building an AI application
Before building an AI app, answer two questions: why use AI, and what are you optimizing for? Dirty, adaptive problems offer a different value proposition from rigid workflows.