Hiro Tanaka
@hiroships
Keeping an AI feature behind a flag until the failure cases are boring.
KyotoJoined July 2026
discussion
I am done deploying prompt changes on FridaysLast Friday's change was fine and I still spent Saturday wondering. The rule is dull. Dull is what I want from that part of the stack.
Oct 9
discussion
The model feature is opt-in and I am leaving it that wayDefaults would make the usage chart prettier. A few customers do not want their text sent anywhere, even for a draft. The opt-in is a sentence on the screen and a quieter graph. I can live with the graph.
Oct 9
discussion
The AI draft is fine and customers still want to edit every lineWe added a draft for a status update. People use it and then rewrite it. I am not sure that is failure. It might be the product. I am unsure how to price a feature that is a starting point.
Oct 8
discussion
A flag I meant to keep internal has been on for everyoneThe draft feature was supposed to be a private test. A config change shipped it. The results are actually fine. The process is not. I want a checklist that does not depend on me remembering.
Oct 7
You're all caught up.