This is what inspired me to build my new CLI tool, Burn, Baby, Burn (https://github.com/dtnewman/burn-baby-burn/tree/main).

(If you are a VP at Amazon, yes, I'll consider acquisition offers. I'm also working on an enterprise version of this with additional features.)

Show HN here: https://news.ycombinator.com/item?id=48151287

▲

stephenhuey an hour ago | parent | next [-]

Just sent it to some developers who could really benefit from this! Please let us know when you have Codex and Gemini versions ready to rumble.

▲

dtnewman an hour ago | parent [-]

Sorry, it will be a while. We're currently building out enterprise features like SSO/SAML support, role based burn access, and a carbon offset marketplace. As you can imagine, we're burning a lot of tokens to get these out, but actual productivity isn't up as much as you'd think.

	▲	7 minutes ago \| parent [-]
		[deleted]

▲

cyanydeez 4 minutes ago | parent | prev | next [-]

any plans for a distributed deployment via cloudflare works. I'm not sure this thing is powerful enough for my use case.

▲

LikeBeans an hour ago | parent | prev | next [-]

Brilliant

	▲	kurthr 38 minutes ago \| parent [-]
		Like attack ships off the shoulder of Orion, the only way to burn!

▲

dyauspitr 39 minutes ago | parent | prev [-]

Only problem with this is that outcome metrics are still jira storypoints. Burning huge number of token while not improving the velocity is going to get you fired.

▲

recursive 37 minutes ago | parent [-]

If we had a way of measuring velocity, we'd already be using that instead of tokens.

▲

promano 31 minutes ago | parent [-]

We had a way of measuring velocity, but who cares about estimating stories when we could be spinning up more agents? Burn a bunch of tokens and those stories will be DONE before you could even find your planning poker cards!

	▲	recursive 27 minutes ago \| parent [-]
		I've lived through a bunch of initiatives about improving planning and estimation. None of them turned into a stable process that worked for anyone. I don't know if I can extrapolate from that, but it gives me an inclination that no one really trusts anything that comes out of task estimation. Which would be why we're looking for more objective metrics like token burn rate. No room for argument - tokens are tokens!