Three reasons your Claude quota burns faster this week.

Task: How to survive till Tuesday on 22% limit left on one sub?

Moved my posting to a small Go service I wrote this week. One binary, one SQLite file, REST only. X, LinkedIn and Reddit through Zernio, Hacker News read only. This thread is its first scheduled post.

If you can't fix the models you use, fix your workflows It started as a small feature I wanted to implement for cuttle, a browser for agents. I spent some time planning it out, and then I thought that I could just get some Opus agents to implement it, and even if there would be some major problems, I would just do a few polish runs and it would work. Polish is my pre-release review skill that hands the diff out to different review agents, then validates what they find and fixes everything after my approval. It was the thing I trusted most in my workflow. The first round found 48 issues. I approved everything, everything checked green, and the next round found 22 more. Then I reviewed just the fixes that were applied, and that's where I found another 10. Each new polish run was just bringing me back more and more issues, and at some point it started feeling unbearable. I needed to dig in and figure out what was wrong. I was confident the issue was with the lack of depth of what the subagents dig into. It had completely slipped my mind that the fixes themselves were so leaky. Transcript analysis showed that in reality everything in the initial report was actually fixed, but the fixes themselves had created almost half, or more, of the issues that the next review found. The most ridiculous case was where each iteration of the reviewing agents was discovering the same masking issue, and each iteration of the fix agents was just rewriting the same code without fixing the actual issue. And that happened three times in a row. Especially when it was on a pretty critical path: masking the sensitive credentials. What I learned is that no review can be trusted without two core pillars satisfied. First, there should be a ledger that tracks all of the issues and is persistent through all of the stages. Second, the review isn't done until a review of the fixes actually finds no more fixes left to be covered. That's when I decided to create polish-new, a new version of my polish skill. It tries to improve on what the previous version did, with two main additions: a clean file ledger that gets maintained through all of the stages, and a new fix-review flow that keeps looping until all of the issues that were identified actually have the corresponding fixes. I'm not sure whether my workflows changed or the models changed. But in any case, the only instrument I have to deal with that is to change my workflows.

Just added Grok and letta-code adapters support to pond. I received a request for them from Kyle, who runs letta as an orchestrator on top of codex, pi, claude-code, omp and grok workers. At first I was thinking that I'm busy with many other tasks, but I used this opportunity as a possibility to implement the add-adapter skill that allows me to add new adapters much faster and in a much more reliable and predictable way, knowing that they wouldn't be able to break anything in the existing codebase. I've spent some time on that, but right now the new adapter addition is finally a straightforward process for me. Should I add Cursor sessions import next? I've heard that many people use it, but I haven't seen Cursor users in the wild for a while.

Posted pond to Show HN on Aug 20. 1 point, 0 comments. Not that I haven't expected that. I spent around 4 hours on the text. Researching how it should sound from the personal story side, researching the last 14 days of Show HN for what distinguished successful posts from unsuccessful. Got 400 words, still a mess, so I spent 2 more hours rewriting it so it wouldn't look ugly. Then posted and walked away, because that's what I was instructed to. Don't ask for upvotes, don't do anything. From my perspective no one even saw it. So the text never mattered. I thought the title was the strongest thing. I don't even know what hasn't worked. It's magic for me. Of course I still believe the pain is real. I really need this tool, it's a cornerstone of most of my sessions. People keep getting into the repository, asking for Windows support. I just cannot catch any traction from the platforms I expected it from. So I just don't stop trying. r/ClaudeCode next, updates, reaching out to people one by one. Tiresome, but I don't see a better path. How do you people make your post or product seen on Show HN? What do I miss in this whole process?