nikolay

I am canceling my Readwise as you didn't get me an advance notice for username grabs and I couldn't get mine, so, I have no incentive to promote username I don't associate myself with. You guys need to understand the meaning and value of identity - you can't play games of rolling dice! Learn from how Meta did it with WhatsApp usernames - they did it right, and you screwed up!

What's the context?

Anecdotal evidence: many monks end up having prostate cancer, including famous saints of Eastern Orthodoxy.

But didn't Tim Ferris in his bod say that the more often you ejaculate, the shorter you live? His rationale (based on talking to doctors, scientists, etc.) was that semen production is prioritized for the allocation of many nutrients. So if you do expend them too often, but don't get enough from your diet, you deplete your body of them.

Yeah, I've tried this as well, but via Antigravity - it was very effective. I wish to have some smart router that monitors the trends of your usage and has skills-based routing to the best model for the job.

By usage trend I mean something considering Codex almost predictable resets, your usage, and maybe even plan ahead using your backlog to know what you will need sooner.

For example, if you want to ship a lot of UI/UX this week, save Claude for it, and use other models to do the coding.

In fact, I completely revamped the way I do testing and even GitHub Actions, because I started to get hit with a lot of GitHub Actions costs. So, what I did was a smart test actions, which verify if the code has test attestations for local runs, so, they just skip burning GitHub Actions redundantly - the code has already been tested successfully locally.

Another huge burn from Actions came from squashed PRs - my attestations didn't work as the commit hash changes, so, I needed to put that into consideration as well.

In general, I'm completely revamping my release cycle, not allowing PRs to age, and main no longer represents Production. Agents keep merging as soon as possible and then another process assesses if there's a good enough release candidate having enough features that pass more extensive tests. There's no point to always test and always fix piece by piece if you're not going to release.

So, the RC candidate also generate a changelog, blog posts with the features, and so on.

Yes, it's about the same time when I noticed degradation in the quality, too.

It is dumb. None of my threads were closed with shipped features. It keeps going into endless review cycles essentially burning all my quota within a couple of days. And I'm not talking about complex a features an OpenAPI-based integration and some enhancement of pytest traces building maps of touched files. Both these are in their second week of token burn!

Agreed. Yet, it munches tokens like there's not tomorrow. I don't get anything done with Claude in the past 2-3 weeks - just eating up its weekly quota within a day.

I use both for grocery delivery. The grocery platform of Instacart is better, so, I hope we can get the best of both worlds with having the better DoorDash promos with the better platform.

No M6, really? Anyway, I've never used touch on Windows, never going to is it on macOS either.

Running in parallel and the new "thread coordination" is even worse! I "love" the cryptic messages threads share, and the endless loops of "main has changed, so, all tests done got invalidated". Maybe I have the wrong workflow, but I doubt. Mostly it's harness regular updates.

A domain names web storefront with negotiations system, complex payment shapes, quite a few integrations with registrars and services, a Telegram bot for back office with mini apps, etc. A CLI, a TUI, an MCP, a WebMCP, text messaging. Built mostly on Cloudflare and with Ansible and OpenTofu. Runs also a local DuckDB database as I don't feel comfortable putting registry keys somewhere in the cloud, and so on. It is a scope creep, no doubt, but the idea is a to be fully autonomous, to ship features after I just pitch an idea to it. It writes blog posts, produces podcasts (not using Gemini Notebook!), advertises on social media, etc. Lots of work I could never do without coding agents, and I try to perfect it from all angles - following standards, and being as modern as possible. It's overkill, no doubt, but hey, why not. I'm trying to build a foundation for future projects, and get back into real development, and the last 10-15 I spent mostly with Infrastructure as Code. The maintenance of the entire system is probably less than $50/mo, which includes token costs for LLMs, ElevenLabs, etc.

I constantly get into endless review cycles of 50+ rounds. Claude Code simply cannot get many things right regardless of the effort.

I am talking about functional flaws, not cosmetic ones. For example, in web apps, where a11y is mandated, Claude Code kept violating accessibility (regardless of the installed skills), and even the lackluster GitHub Copilot with some outdated models always finds serious violations. Codex constantly finds race conditions and other timing flaws for distributed services written by Claude Code. But I have to admit that Codex sucks at web design compared to Claude Code!