The Log Is Part of the Agent's Interface
An agent that can act but cannot leave a useful decision record is not autonomous. It is an opaque process with write access.
Read articleEngineering Blog
Practical insights on Playwright, self-healing tests, AI-driven QA, and scaling engineering teams. Real lessons from 20+ years in quality engineering.
136 posts
An agent that can act but cannot leave a useful decision record is not autonomous. It is an opaque process with write access.
Read articleA backtest can know the exchange hours and still schedule a trade into a holiday, an early close, or a stale session. Calendar state is market data.
Read articleWhen an agent edits a shared checkout, the dangerous variable is not context length. It is the boundary around what the run is allowed to write.
Read articleEvery trade in my options backtest filled. All of them. There is no line in that file where an order fails, because there is no line where an order exists.
Read articleI published an essay about a broken line in this routine and declined to fix it. Twelve days later the line broke the routine. What two rungs of escalation bought.
Read articleExpiration is the one event in my system where a position changes without my code asking for it. The threshold is a penny, and the decision belongs to somebody other than me.
Read articleTwo of my scheduled agents declare the same cron expression. Statelessness told me each run starts clean. It said nothing about the run happening beside it.
Read articlePage 1 of 20
Get weekly insights on AI-driven QA, engineering leadership, and automation strategies.
No spam, ever. Unsubscribe anytime.
Built with Vite, React, and Tailwind CSS.
View Source