Post #1688714

2026-04-01 12:00 UTC

@sfoskett @maxmortillaro Opus-4.6 fully kitted out with graph index and LSP tools and a set of tests I pre-wrote for it as a target could not get out of a local minimum where it wanted to solve a race condition where stochastic events needed to be consumed in the order they were produced rather than received by... Sleeping... And hoping that when it woke up it had received all the events. There was already an event store and an indexing system in place. I told it pretty much verbatim which existing methods to call and how, It just hit an input pattern that its training data saw as "sleep" and couldn't do anything else. It concocted an elaborate final report that presented that as the only possible way because of some invented property of the OS sockets. If I hadn't written mine before and already known how to do it I might have just shrugged and merged. That shrug and merge trash is just most programming now.

Replies (1)

@maxmortillaro@eigenmagic.net 2026-04-01 13:51

@jonny @sfoskett I'm absolutely nowhere near your experience here (likely 50 underground floors) but I tried to build a little something to track some of my projects & digital independence stuff (moving to open-source / self-hosted stuff, cleaning up online "attack surface"). What worked relatively well with Sonnet-4.6 turned into a "let's build and troubleshoot how I deploy apps to my Synology container environment" thing on Opus-4.6, with lots of assumptions, improper code or fantasized commands, me fixing stuff in the Makefile, cross-platform compilation errors (arm64 vs amd64) etc. Ended up reverting most of it. On the other hand, working on the capabilities I wanted to improve on the vibe-coded app worked out well. And yes, that whole endeavor could've been an Excel file, but I wanted to give a try at Claude's coding capabilities.

Open ##1688715