Not every generative app problem can be solved by a better model
Five categories of production gaps a more capable model will not close on its own — and what to check before you trust it with real work.
Read log →Signals, experiments and field notes from the useful side of AI. What we're building, what we're testing, where AI breaks, and what small teams should know before giving machines more work.
Five categories of production gaps a more capable model will not close on its own — and what to check before you trust it with real work.
Read log →Ideas worth keeping. Mistakes worth documenting. Systems worth questioning.
A simple photo-sorting example shows when a fixed process is enough, and when a task needs an agent's judgement instead.
Read log →
Three questions to ask before you build an agent, and three techniques that cut the bill even further once it's running.
Read log →
Five prompt structures that make agreement structurally unavailable, so you get a usable second opinion instead of your own view reflected back.
Read log →
Five assumptions about AI agents that quietly degrade the work, and the guardrails that catch each one before it gets expensive.
Read log →
A working checklist for the failure modes AI coding agents do not flag on their own, with before/after code examples.
Read log →
Meta-prompting — asking a model to interview you and draft the instruction, then spending your time checking whether it describes the real task.
Read log →
From zero-shot to decomposition — six practical techniques, when each one earns its keep, and where each one falls short.
Read log →
A practical note on why workflow clarity beats premature autonomy.
Read log →
Look for frequency, friction, clear inputs, and a measurable before state.
Read log →
The signs that a process is ready for AI assistance, and the risks that should slow you down.
Read log →
Proposal work improves when AI supports structure, reuse, and review rather than replacing commercial judgement.
Read log →
Three useful words that often get blurred together in AI planning conversations.
Read log →Bring a repetitive workflow, a messy handoff, or a team question about AI. The first conversation is about whether there's a practical, safe starting point.