> Google Maps should have a Low Stress mode
Maps finds the fastest route. The best route depends on who's driving, and a few minutes is often worth fewer hard decisions.
Maps finds the fastest route. The best route depends on who's driving, and a few minutes is often worth fewer hard decisions.
How you charge changes how people use what you built, so decide the behavior you want first. Cursor and Cline showed me the difference.
Chat is the obvious way to add AI, and it demos well. The one I keep finding useful is quieter: AI sprinkled through the product, doing a step the user used to have to think about.
Moving recurring PM checks into Linear made them something the whole team could see and change. How I set up the loops, and what it suggests about where agents belong.
Encode the correction as a check instead of repeating yourself. It runs on every change while the agent is still working, so the mistake gets caught before you ever see it.
Building CLIs, APIs, and MCPs for agents works a lot like building for people. Watch them use it, see where they get stuck, and fix that.
A Jenga rule from an old office: fix a bug without a test, pull a block. Why the follow-up after an urgent fix gets lost, and why it's easier to keep now.
Calendly turned availability into a link. But links were built for humans. When agents book the meeting, the whole model changes.