Notes on Overnight Software Delivery at Tilt
Notes from my current Tilt workflow: why I run bounded overnight work locally on a MacBook, how the tools fit together, and where human review remains.
Practical notes from backend engineering and building products, plus occasional writing about business, family, and ambition.
9 notes for “Engineering”
Notes from my current Tilt workflow: why I run bounded overnight work locally on a MacBook, how the tools fit together, and where human review remains.
Why abstraction helps me connect systems quickly, where compression errors become dangerous, and how I separate creative synthesis from cold validation.
What started as a personal memory app is becoming a context layer for people and AI agents, without abandoning the personal product that exposed the real problem.
Giving an AI assistant more text is easy. Giving it current, permitted, traceable, and testable context is an engineering problem.
Why AI-assisted development gets safer when agents can read the operational runbooks before they make code or deployment decisions.
Why agent memory is only useful when every durable fact points back to a source, a date, and a reason it should still be trusted.
A practical structure for giving coding agents useful context without turning every task into a giant prompt dump.
PLAYGRND is my practical example of how a small team can move faster with AI without letting AI replace product and engineering judgment.
Why the long-term advantage in AI-assisted software work is not picking the winning model, but building reliable context systems around any model or tool.