Same here. I run Qwen3.8 Flash Next on my local machine and combine it with Opus 5.5 for plan making. The Qwen model feels like it's around Opus 4.x level performance most of the time.
But once in a while it gets into long reasoning loops, which is annoying. It seems less with the Swift model but I haven't benchmarked the difference between that one and the original.
Interesting idea. I guess the main challenge is to create some kind of harness to make the input volume appropriate for an LLM to evaluate. Billions of the same log events from a raw stream will be cost prohibitive and not find you much interesting output. But a trend in some value changing would.
As a human I look at Datadog or Grafana plus some log searches, maybe those need to become tools for the agent.
Nice write up. I've been optimising build duration and feedback speed across a few projects recently. Agentic coding is putting more emphasis on best practices that we all dragged our feet on for many years :-)
But... Tell the AI to write more concise and remove typical AI-isms next time. The post is twice as long as it needs to be and keeps doing the "The slow linter isn't the problem" fluffy Claude thing.
That article wasn’t written using AI. I wrote it in Czech language (it’s my mother tongue); the AI translated it into English for me, but I’ll definitely choose a better translation next time.
Skimming through both, the English translation actually seems reasonably faithful, even if a little bit coarse in places. I guess it's a combination of translation and phrasing that some people would associate with AI.
One would think just some classes and forms of RAM increased in price. I have 128 GB (2 x 64GB DDR5 SO-DIMM) in my home NAS. Home NAS. Those nice ugreen DXP8800 Plus thingamabobs. It'd be over 2k euros for RAM alone now. Ridiculous. Add to that two SN850X 4TB SSDs, and 8 (+1 unpacked spare) IronWolves Pro and it's now a serious worth.
I know the only manufacturer of such 64GB modules: Crucial (Micron), but Micron doesn't sell new chips to Crucial, thus almost no chance to get them anymore (though few months ago there were some). Kingston (using Micron, Hynix and Samsung) still does not have 64GB.
Soon Zen 6 should become available (well, or not so soon). With 7200 MTs memory controller? I haven't seen such JEDEC modules at all. Are they possible without the additional clock driver (like on 6400 CUDIMMs)?
Interesting, that explains why getting 4x48 = 192gb is around 2400 euros, so 1.2x the price for 1.5x the capacity.
Speed has indeed decreased for the modules you can actually buy, while historically you would get faster and faster modules at lower prices in the years after the introduction is a new DDR standard.
For daily office use there is much more benefit in having more memory than having faster memory. Because apps all started using more memory. Especially anything Google Chrome related.
If you have some unused extra memory it will be used as disk cache, which also helps in the responsiveness of a desktop. Waiting for the disk is orders of magnitude slower than reading from memory cache.
There are, but I've seen several of those price increases in a row so you may be moving a lot. And mail deliverability to Outlook and Gmail from those hosts isn't always great.
I have a Claude plugin on there, but I now see it twice, once with an empty version number and once with 1.0.0 while the latest is actually the 1.1.0 version. Then when I click the 1.0.0 listing under versions the 1.1.0 version appears. Feels like no QA happened on this thing :-)
The plugin is for AppHaven to allow Claude to deploy containers and databases, check their build status and logs etc. So it can take all of the devops work for AI coded applications out of your hands.
I think we're going to see a huge number of small internal tools that simply wouldn't have been worth building before coding agents. Even more so in SMB, because they have less budget.
The part I don't think you can leave to the agent is everything around the application: backups, authentication/access control and vulnerability scanning. Those things aren't rocket science, but getting them wrong can have a much bigger impact than a bug in the application itself.
That's what I'm building with https://AppHaven.eu My bet is that vibe-coded apps will become cheap and almost disposable, while the platform underneath them needs to provide those boring safety guarantees automatically.
Nice idea, but this is not how flight planning works. The optimization algorithms that airlines use consider a broader range of variables than just fuel, since you also have cost per hour that the engine is running, cost per hour for the crew, and overflight fees for different airspaces.
And the output still has to be a valid flight plan route. You can't just file a flight plan for "I want this zig zag line at this altitude".
Commercial flight planning software does this optimization as well, but it only selects routes that are valid. For example you have to be at a certain altitude to go one way on a route and another altitude to go the other way. ATC can't do their job if you have planes pointing at each other in opposite directions doing 1000+ km/h.
not just cost-per-hour of the crew, but also rest schedules. A more economical flight-path is all well and good, but it's useless if it means that the crew will breach their permitted duty hours.
But once in a while it gets into long reasoning loops, which is annoying. It seems less with the Swift model but I haven't benchmarked the difference between that one and the original.
reply