News for hackers. Stuff that matters.
Re:Five months treating bugs like patients and coding agents... by rafiss on Monday October 12, 2026 @11:26AM (#50057813)
Rather than per-day costs, I think it might be more meaningful to look at per-result costs. It took us about 9 months (and $160k using our napkin math) to add support for Oracle. Adding Db2 support using this agent pipeline took 2 days and $4,172 in tokens.

One caveat to the number for DB2 is that it doesn't consider review costs. We weren’t reviewing the hospital’s code during that sprint. Since we’re still confirming correctness for Db2, a more accurate comparison would add the human time to verify this.

I’m not going to claim this tripled our revenue. But revenue is also a function of time to deliver too. When a missing feature in the migration tool is what’s blocking a customer’s migration or a deal, shipping it in days instead of months can move revenue directly if it means the customer doesn't choose a different alternative.

Re:Five months treating bugs like patients and coding agents... by tujux on Tuesday October 13, 2026 @05:17AM (#50068871)
Thank you for the reply. My question is - will you be able to charge the same amount for work done in days instead of months? Or even a proportional amount?

If its work that was blocking an existing deal, I can see this playing out in your favour. Whereas, if you were trying to negotiate a deal where you wanted the customer to pay x$ for a feature you have yet to develop, you might now have to charge lesser.