claude-code

Garry Tan's gstack arrived at the same architectural decisions I did, independently. The convergence matters more than either implementation.

I left an AI coding pipeline running overnight with 21 monitoring cycles. 5 features merged, 10 specs dispatched, 3 root causes found. Here's what worked, what broke, and the quality of the output.

ANTHROPIC_API_KEY vs ANTHROPIC_AUTH_TOKEN — how a single wrong environment variable made an AI coding pipeline silently fail for hours, and the debugging journey that found it.

Five skill repositories, a day of reading code, and a significant correction I had to make the same afternoon.

I ran an autonomous agent loop overnight — 43 waves, ~270 dispatches, ~250 vault files produced. Here's what I learned about building systems that work while you sleep.

In AI agent systems, use the most reliable trigger mechanism that fits — most builders default to skills for everything, which is using the weakest mechanism as the default.

The governing principle for structuring knowledge in AI agent systems isn't 'always atomic' — it's matching how knowledge is stored to how it's accessed.

The most dangerous failures in AI scaffolding are the ones that look like nothing happened.

Every AI coding platform has mechanisms designed for specific purposes. Using them as intended beats clever hacks — and the reason is deeper than cleanliness.

Your AI already knows things that would make it better at helping you. The trick is extracting that knowledge and making it permanent.

The real ROI of AI coding isn't doing the same work faster. It's doing work that wasn't worth doing before.

The simplest agent architecture might already be the right one: give the agent a file explaining how to do something, and let it read when needed.

Tool enthusiasm is often net-negative. Context pollution degrades performance faster than features improve it. The principles that actually work.

I published three Rust CLI tools to crates.io before noon — none existed at breakfast. The interesting part isn't the speed. It's that the bottleneck moved.

When AI can execute complex setups through conversation, learning shifts from reading documentation to observing execution.

When AI coding assistants become workflow orchestrators, the most powerful compiler processes reality, not code.

AI becomes most powerful when it helps you discover what your ideas actually are. Cognitive partnership over replacement.

When implementation becomes automated, human intelligence reallocates to purpose and strategy. The cognitive hierarchy inverts.