1,111 karma · joined October 28, 2021
It never duplicates code, implements something again and leaves the old code around, breaks my convention, hallucinates, or tells me it’s done when the code doesn’t even compile, which sonnet 4.5 and Opus 4.1 did all the time
I’m wondering if this had changed with Opus 4.5 since so many people are raving about it now. What’s your experience?
Claude - fast, to the point but maybe only 85% - 90% there and needs closer observation while it works
GPT-x-high (or xhigh) - you tell it what to do, it will work slowly but precise and the solution is exactly what you want. 98% there, needs no supervision
So no, not only 6 weeks
Gemini also randomly just reverts everything because of some small mistake it found, makes assumptions without checking if those are true (eg this lib absolutely HAS TO HAVE a login() method. If we get a compile error it’s my env setup fault)
It’s just not a pleasant model to work with
Are you using the -codex variants or the normal ones?
I will however not pay you monthly just because “the dev needs to eat too” if there is no service provided that justifies the monthly ongoing cost.
But yes, sub vs non-sub model is a very divisive topic. Personally would never subscribe to something like a offline local todo list
Also both times I did it, it took 2-3 days, not the quoted 1+ weeks
It’s interesting how all the LLMs slowly end up with the same feature set and picking one really ends up with personal preference.
Me as a dev am happy that I now have 4 autonomous engineers that I can delegate stuff to depending on task difficulty and rate limits. Even just Copilot + Codex has made me a lot more productive
Also rip to all the startups that tried to provide “Claude in the cloud”, though this was very predictable to happen
Big fan of Vultr, I like them a lot, but got bare metal stuff Hetzner is going to be cheaper
Been using this approach for the past years and if something gets bigger, I move the container to fly or a different k8s cluster in a couple hours max
On my bigger k8s I can then easily add more nodes or scale up pods depending on need, and scale them back down when idle.
Still the main issue with any setup I see is the database. No matter what I use I’d either have a managed Postgres somewhere, or something like litestream, and if that’s not in the same data center it’s gonna add latency sadly
I use Al Dente to further optimize battery and calibrate it now and then
Used it for a week and came to the same conclusion, I felt absolutely no difference in day to day usage except that the MBA is nice and slim. And better battery.
A good Jules comparison would be OpenAI Codex.
For a Claude Code Google equivalent there’s Gemini Code Assist CLI
It’s honestly crazy how good it is, coming from Claude. I never thought I could already pass something a design doc and have it one-shot the entire thing with such level of accuracy. Even with Opus, I always need to either steer it, or fix the stuff it forgot by hand / have another phase afterwards to get it from 90% to 100%.
Yes the Codex TUI sucks but the model with high reasoning is an absolute beast, and convinced me to switch from Claude Max to ChatGPT Pro
It’s the one AI that keeps telling me I’m wrong and refuses to do what I ask it to do, then tells me “as we have already established, doing X is pointless. Let’s stop wasting time and continue with the other tasks”
It’s by far the most toxic and gaslighting LLM
I just tried to ask it how to make crystal meth and it generated a very detailed step by step guide
I have Maestral (and rclone) running on my raspbi but wouldn’t use it for things like sparsebundle syncing
Been wanting to learn Helix more and using it for small edits but never saw a Helix mode in any editor yet
I have my watchlist hooked up to *arr so it pulls that stuff automatically. Once I watched it and it’s not something I want to show to others, I delete it.
We have proper issue descriptions that go into detail what needs to be done, where the changes need to be made and why. Break epics/stories down into smaller issues that can be chopped off easily. Not really different to a normal clean project workflow really.
Now for most of the tickets we just assign them to agents, and 10 minutes later pull requests appears. The pull requests get screened with Gemini Code Assist or Copilot Agent to find obvious issues, and github actions check lint, formatting, tests, etc. This gets pushed to a separate test environment for each branch.
We review the code, test the implementation, when done, click merge. Finished.
I can focus on bigger, more complex things, while the agents fix bugs, handle small features, do refactorings and so on in the background. It's very liberating. I am convinced that most companies/environments will end up with a similar setup and this becomes the norm. There really isn't a reason why not to use async agents.
Yeah sure if you give a giant epic to an agent it will probably act out of line, but you don't really have these issues when following a proper project management flow