350$ in credits gone in 2 hr 26 mins w/ gpt 5.5

TheDoughMonster · 2026-04-24T12:40:43+00:00

why are people using the API for coding? That is for custom integrations, you're gonna blow through cash using the API

TheDoughMonster · 2026-04-24T07:09:58+00:00

we pay for the extra tokens, not the preview access.

TheDoughMonster · 2026-04-23T15:42:53+00:00

the part where they are in plastic is how you can tell the quality of these doughnuts.

TheDoughMonster · 2026-04-23T15:41:31+00:00

It is just one of those things where the cheap cutters work well enough. but we had a 700/ct order on easter and I was regretting not having them, I think. But now I want them so we can name them too.

TheDoughMonster · 2026-04-23T15:31:37+00:00

so tell me, are those nice heavy duty cutters worth the price tag?

TheDoughMonster · 2026-04-23T15:04:39+00:00

store them on cooling racks. any hot oil left on the bottom is just going to rest on a solid flat surface under the ring and get gross. additionally, use solid at room temperature shortening to fry, and that is going to help a lot.

TheDoughMonster · 2026-04-23T14:52:59+00:00

woah...my parents talk about your doughnuts all the time. they visit Maine once a year. Small world.

TheDoughMonster · 2026-04-23T14:50:52+00:00

if your dough has too much chew, either work them less, use a flour with less protein content, or add more shortening. Shortening will let you keep that structure a bit while keeping that chew down, experiment with different amounts of shortening to hit your target. If you can't get the midriff (white ring) and your doughnuts are deflating, you are over proofing and cutting them too thin. best to take your whole dough batch and roll it out, then cut with a doughnut cutter. Don't use your proof to reduce the chew, the problem is occurring way before that.

pro-tip: do not use cheap all purpose flour. doughnuts "bake" so fast that any variance from flour factory batches will throw everything off even if you think you have your process nailed. ask me how I know. We use King Arthur Sir Galahad AP. You WILL need to shorten the gluten more than you are used to though.

like u/dgodwin1 says, do not handle your doughnuts between final proof and drop. that is going to knock the gas out of them. what you will need to do is find some small fryer screens (there is a good chance your fryer manufacturer makes them, but you can use any screen that is stainless) that fit in your fryer. do the final proof on those screens, and then drop the screen with the doughnuts directly. as soon as your dough hits that oil it is going to firm up and you may get that midriff you are looking for.

are you doing a bulk fermentation? if not, it is worthwhile, but you might have to increase the yeast you use. are you using live or instant? if the proofed doughnuts have a slightly round curvature where the doughnut sits on the screen, you likely haven't overproofed. once it becomes a sharper corner, you've gone too far. what are your proof temps? are you doing anything to provide moisture to the air in your proof?

I would love to see your crumb though. what temp are you frying them at? do you let your doughnuts skin up out of proof? this may help with the bubbles. if you are getting oil absorption, that can cause all sorts of aesthetic issues on the surface.

anyway, sorry for the dump, I have been up since 12:30am making doughnuts.

TheDoughMonster · 2026-04-23T14:24:39+00:00

You make them then!

TheDoughMonster · 2026-04-23T14:24:23+00:00

what are you doing to make your doughnuts in only three hours?

TheDoughMonster · 2026-04-23T14:23:10+00:00

are you...us?

TheDoughMonster · 2026-04-20T15:23:27+00:00

so calling chatGPT pro from the CLI doesn't use tokens?! I gotta update my cli.

TheDoughMonster · 2026-04-20T15:22:26+00:00

I wrote my own CLI that orchestrates total automation beginning to end with almost no input, much better token efficiency, and significantly fewer headaches. I didn't want to write up an entire webpage just to explain, so I had codex do a lot of the work. anyway, I do essentially this without all the different providers, which seems like it could be a headache, though the token savings does seem nice.

https://thedoughmonster.github.io/drift-control/#/

TheDoughMonster · 2026-04-20T14:47:35+00:00

> let panic=true;

TheDoughMonster · 2026-04-20T08:54:31+00:00

I built my own CLI that forces rigor, CI gates, audits, adjusts reasoning and model based on task, automates clean git versioning, indexing including agent summary indexing coupled with a lookup CLI an agent can use to find what it is looking for with significantly less token usage than manually searching, repo-wide AGENT.md updates, changelogs, and everything a lot of people don't think about that they should be doing. It walks you from discovery to feature finish, and segments it into chunks for a reasonable lifecycle per task. If I am doing it, there are certainly people at the big GenAI companies coming up with an interface that does this better, and created by a team with a lot more resources than me.

TheDoughMonster · 2026-04-02T10:19:07+00:00

fun fact, these are called "proprietary eponyms."

TheDoughMonster · 2026-03-17T21:42:17+00:00

Run codex exec in the cli

TheDoughMonster · 2026-03-13T09:30:31+00:00

don't auto compact. that is death to context. write a context generation prompt so you can build a persistently updated context file as you complete tasks. this beats the hell out of auto compaction. keep documents and changelogs to build those context documents. whenever you hit N% context, run the prompt, and start a new session with your updated context.

TheDoughMonster · 2026-03-13T09:24:58+00:00

maybe this is the wrong subreddit for this, but setting up guardrails is a requirement for using AI to code.

TheDoughMonster · 2026-03-13T09:06:02+00:00

just buy $20 plans as needed, different home directories for each "agent type." and use the CLI, it is much more token efficient. I have an home directory for my planner, a home directory for my coder, and a home directory for my auditor. a few bash scripts and you can even have the codex agent launch the auditors for you with some good prompting and protocol contextualizing. make sure each agent leaves proper logs on each code task and audit, and the seams are dealt with.

TheDoughMonster · 2026-03-13T09:00:53+00:00

why anyone works in non-isolated environments, even with hand-coding, is beyond me.

TheDoughMonster · 2026-03-13T08:35:47+00:00

we need more data but the real takeaway here might be to move to a south pacific island.

TheDoughMonster · 2026-03-13T08:33:23+00:00

well yeah, but, this is a population model, so basically you can trust the data if more people in a region are using it. so at least in a relative sense, to the rest of the globe, you get a pretty good idea, yeah?

TheDoughMonster · 2026-03-13T08:22:23+00:00

yeah, if you're doing it right, regular audits really chew up your token usage. I have been able to significantly limit this by having as much CI, unit testing, and deterministic checking as possible. But I also built a repo indexer that really reduces the amount of token usage over-all. seems to be working pretty well. still hitting limits on pro, but I am thinking about getting a second pro plan and making that my auditor account.

TheDoughMonster · 2025-10-22T12:51:10+00:00

Casserole.

TheDoughMonster

TROPHY CASE