↓ Skip to main content

workflow

explorations of how we work, covering systems, processes, and the practical habits required to maintain high throughput without burning out

anything i can imagine

ai is excellent at helping me produce anything i can already imagine clearly enough to describe, guide, and evaluate. that does not make human creativity obsolete. it makes human creativity the starting point, because the model still needs a person to frame the work, lead the process, and decide what good looks like.

room to breathe

ai removed the natural pause between improvements, so it always feels like there is one more optimization to squeeze out. but unless your system is fully autonomous, you are still the bottleneck, and your real rate of shipping work you understand has not changed. i argue that the fix is deliberate room to breathe, letting a solution run in production and settle in your head before you start the whole improvement loop again, both to avoid burnout and to actually understand what you built.

the guardrails i actually use with ai agents

in ai liberty i argued that capable models take more liberties and need robust guardrails, but i did not show them. this is the concrete kit i actually use to keep speed without losing control, namely read-only and ask modes, command allowlists, scoped database credentials, branch protection, and human-in-the-loop gates for the few actions that are genuinely hard to undo.

ai liberty

as ai models become smarter and more capable, they also become more confident, making them increasingly likely to take autonomous actions such as running terminal commands and executing sql injections without explicit instructions. i share recent examples of this behavior and discuss why robust guardrails are essential before unrecoverable damage is done.

working with an ai model mirror

after a major release, i finally had some room to breathe, so i jumped into some repo maintenance and deployment improvement work. i used gemini 3.5 flash for this, and the experience was hilarious and revealing. this model is fast, highly self-complementary, and ready to take major liberties with the command line, reminding me a lot of my own worst habits of moving fast and leaping before i look.

back at it

i am finally out of the weeds on a recent heavy lift. i stuck with it the way i wrote about in stick with it, then moved the way i should have from the start, in smaller pieces that add up to the larger change. there is still testing and user acceptance ahead, but a stable baseline gives me room to step back, reset, and continue with a clearer head.