Connect your Claude, Codex or OpenClaw for full transcripts on millions of podcasts. Two week free trial, cancel anytime.
Start free trial →devtools.fm: Developer Tools, Open Source, Software Development · Hands-On Engineering Podcasts · November 2026
A host had described a coding harness that shows a dollar amount per session, and a feature that ended up costing $400. Tarun argues against managing engineering at per-task cost granularity and explains why Traces doesn't surface token counts by default.
…you can get to here. That, you know, it's, it's really up to you as an engineering leader or manager or developer to act on that in some way, shape, or form. Like, you know, it's a question on whether or not that's data you should use to change something or it's just interesting to observe. So
yeah, the coding harness I use at work recently added a dollar amount to each like session. And seeing that dollar count go up as I like iterate more and more, I'm like, oh, this will just be like a nice little feature I can fire off. And it was like $400 later. Sheesh.
Yeah. Yeah. You know what? I think this is like a really interesting conversation that you're bringing up, man. Like, I think the idea of attaching dollars to every task at that level of granularity is, you know, for engineering is not like, you know, unless you can also attach the like the dollars that that could potentially generate.
Yeah.
Right. Is not a complete view of the story, right? Like, I think it's, it's really, I think engineering and software is a, it, it's a, it's the ultimate form of leverage. Andrew Lisowski to only focus on the cost associated with a task is, I think, probably not the best form of engineering…
Yeah, just on time savings alone. Like if I prompted $400 away, but I saved three months of my own life like going down different paths and finding like the dead ends. Like it's kind of hard to quantify that upfront. There's a lot of, yeah.