I'd like to highlight a different part of the article:<p>> In general, when I talk to software folks about testing, I'm coming from such a different place that they immediately look at me like I'm an alien, so let's talk about how we tested at this hardware company I worked for, Centaur, which informs my biases about how I like to work. Some of the things that we did that were or are unorthodox in the software world are:<p>> Hired dedicated QA / test engineers, with testing being a first-class career path on par with being a developer - No code review by default - Virtually no hand-written tests - Constant testing via what programmers sometimes called property based testing, randomized testing, fuzzing, etc., although we just called those tests (hand-written tests were called "hand tests"). - Large regeression test suite (3 months wall clock to execute on compute farm) - No unit tests<p>Anybody here tried that (or a similar) approach? Especially going all-in on property based testing and fuzzing with no unit tests.<p>I tried that approach somewhere before and the initial results were promising, but ran into political issues so the idea was canned.
I bake MCP tools into everything now, including doing screenshots. Any LLM can run just about every function, including resizing the window. I just watched Fabel 5 do a full usability test on a new project, copying the release cycle for my agentic terminal, relaunching the app like 20 times as it went, ensuring the move to a built and signed release was working. It installed the program like 5 times (something I do daily multiple times).<p>I noticed map tiles were not working and started to tell it, but then all of a sudden they reappeared and checking the logs it had found the issue and autocorrected itself.<p>The key here is feedback loops and systems annealing.<p>As for Dan, my God I love this guy. Glad someone posted it!
I really wonder what "randomixed testing" looks like in practice. What is the measure of success/failure?<p>I undrestand for fuzzing you have a very basic "doesn't crash" metric. Property based tests.... you gotta write properties for the PBTs to work on. What is the randomized testing hitting?
The first thing I started wondering was "is this the same Centaur that comes up as 'CentaurHauls' on a CPUID (EAX=0)?"
Should be, judging by their LinkedIn from the bottom of the page (Centaur Technology - Member of Technical Staff: 2005 - 2013)<p>This is a blast from the past. Centaur was doing VIA Technology's CPUs, and I was at VIA (in Taiwan) while this author was in Centaur (in the US). I was on the embedded side, but I remember some distinct collaborations with the US team, so there's a non-zero chance to have crossed path.
OP's alt text makes it clear that by "Galapagos Island" they mean Vancouver. I assumed that this was some sort of local nickname, but all of the references to "Galápagos of Canada" I could find are talking about Haida Gwaii instead.
I think it’s just a metaphor for being isolated from the wider tech community.
Nobody calls it that.
Yeah I was like “woa a PGConf on the galapagos, i gotta get my ass to one if those!”
A lot of the crazy ideas seem to have melted away in the face of massive context sizes. Today, I can put roughly <i>a megabyte</i> of utf8 text into my system prompt before things start to get weird.<p>That is a massive amount of information even if we are being sloppy with it. You can read The Hobbit and the first Harry Potter book cover-to-cover and still have room to spare. I would deeply struggle to develop a world model this detailed for any business. Anything that needs to get more specific than these narratives can be a SQL query tool into the data warehouse, grep over the codebase, MS graph API lookup, etc.<p>Giving the business a balanced way to collaborate over this one shared model of the world is a new challenge I am beginning to engage with. I've also noticed that the world model will compound on itself in terms of self-detection of update opportunities. The more constraints there are, the more likely we appear to violate one.
You’re forgetting that keeping the context small is better economically <i>and</i> delivers better results.
I learned some nuance. Small context is important if the context isn't cachable. If most of it is the same prefix every time, the situation changes pretty significantly.
Forgetting? I think you mean to say your advice was auto-compacted to keep our context small <i>and</i> deliver better results.
> melted away in the face of massive context sizes<p>If only. There is a huge difference between "Gives good responses/can easily spot things within N context size" and "Technically works but sucks within N context size", almost all models basically become cave-people once you go beyond 50% of the "supported" context size, meaning while they may technically work with 1 million output tokens, those last 500K tokens are gonna be massively "dumber" than the first 500k tokens.
There's at least one benchmark that attempts to measure this, but it has been running for a year plus so it's quite infrequently updated now.<p><a href="https://fiction.live/stories/Fiction-liveBench-Mar-25-2025/oQdzQvKHw8JyXbN87" rel="nofollow">https://fiction.live/stories/Fiction-liveBench-Mar-25-2025/o...</a>
I don’t find that to be true?
I can agree with Dan on two things: LLMs do often produce incorrect results and that it's still useful for productivity when used in moderation. For me the wrong results actually cause some kind of ragebait response so I become much more motivated to learn more about the subject to actually generate correct response. After I've learnt the subject area enough I find I'm better off having LLM review my code instead of writing it.<p>I haven't even begun to try to comprehend how to use fuzzing testing to improve the ability to find bugs, but it sounds really interesting. I've seen mutation testing to be very useful for finding gaps in tests, so I can only imagine that fuzzing + LLMs might produce insane results.
It's really coming down to "Do we want to subscribe to a human with a salary of many ~$10000(s) ", or "Do we spend 100(s)$ on an AI subscription"<p>Even with it's issues, the latest models are going to disrupt the labor economics.
URL typo: "hange how he works](/productivity-velocity/)". (I make this kind of Markdown syntax error all the time and set up a lint for '](/'.)<p>You should talk to <a href="https://www.mechanize.work/" rel="nofollow">https://www.mechanize.work/</a> for sponsorship/credits and about environments.
There is a reasone we use left and right margin/padding.<p>This blog is quite unreadable for 27/32" monitors.
The point of a wide monitor for me is to have two 720 wide windows side by side, not a single gigantic 1440 window with impossibly long lines.
Toggle to "reader view" or resize your window. It is up to you and really isn't that hard.
There’s a reason not to maximize your browser windows. How do you handle HN threads on that monitor?
TW;DR (too wide didn't read) ;)
This seems like the beginnings of AI psychosis, tbh.
[flagged]
It's "Galapagos" or "Galápagos," not "Galapogos."
He's not referring to the real islands, but rather the state of mind imposed upon existence on Vancouver Island.
You miswrote OP’s miswriting in the third version :)
[dead]
[flagged]
Fable changes the game yet again, because it's API-only.<p>You're not likely to want to run Fable in a loop any more than you want to take a bunch of dollar bills and light them on fire. Every invocation of Fable has to be intentional, its context carefully managed. I feel like a babysitter.
Compared to Opus 4.8 I really haven't been impressed
I just had Fable run overnight in a loop, and it fixed ~150 compiler crashing bugs that Opus had kept deferring.<p>I wouldn't <i>start</i> with Fable - when I use burndown loops I tend to include instructions to document progress and set aside anything that turns out to be harder than expected, and solve the easy stuff first. When a model runs out of easy stuff and start struggling to make progress on what is left, I can let it keep churning on that - they get there eventually - or I can bump it up to a smarter model if one is available.<p>Opus had churned <i>a week</i> driving down spec failures, and did a great job. The 150 Fable took overnight were the ones Opus had kept putting aside.
Fable is supposed to return to subscription plans, unless I'm missing something: <a href="https://jacob.gold/posts/fable-5-removal-is-temporary/" rel="nofollow">https://jacob.gold/posts/fable-5-removal-is-temporary/</a><p><pre><code> Anthropic says the change is about capacity and is temporary. In its launch announcement on June 9, 2026, it says:
"After this point—when sufficient capacity allows us to do so—we aim to restore Fable 5 as a standard part of subscription plans. We intend to do this as quickly as we can."</code></pre>
Apple claims their price increases are temporary too. I'll believe it when I see it. The capacity limitations are not going away any time soon.
They can’t keep their current models working on subscriptions[1], so we’ll see if this is marketing or not in the future.
It’s smart to tease it no matter what, ”insert classic first hit is free drug reference”.<p>[1] <a href="https://status.claude.com" rel="nofollow">https://status.claude.com</a>
I agree with you that you don't <i>need</i> fable for everything, and you have to be careful on what you run it on. CRUD stuff, sure even the small models can do it. But there certainly are tasks that are very much suited for the absolute SotA and you'd leave money on the table by not using it. And how much a task is <i>worth</i> is dependant on how much it improves your bottom line. So the cost/token becomes largely irrelevant.<p>Let's take this [1] benchmark. A bit more context here [2].<p>Here models are asked to create kernels for running inference on models. This is a benchmark perfectly suited and highly relevant right now. It's easily verifiable, an active are of research, and the results are immediately useful.<p>Say you have 1 unit of compute, it costs 300k $ and serves 1x users. In comes Fable and after one session it gives you 30% speed-up on your 1 unit of compute. It can now serve 1.3x users. How much is that one session worth for you? How much is it worth for a company using 10 units? 100 units? How much is it worth for a hyper-scaler running 10.000 units? How much is it worth for a lab that trains the next frontier model and then serves it from 100.000 units? 30% is relative. And the cost for one session is really meaningless. It can cost 1m$ / session and it would <i>still</i> be worth it for someone.<p>[1] - <a href="https://kernelbench.com/mega" rel="nofollow">https://kernelbench.com/mega</a><p>[2] - <a href="https://x.com/elliotarledge/status/2072814573753975266" rel="nofollow">https://x.com/elliotarledge/status/2072814573753975266</a>
For now, I can use Fable from the web just fine.<p>> You're not likely to want to run Fable in a loop any more than you want to take a bunch of dollar bills and light them on fire. Every invocation of Fable has to be intentional, its context carefully managed.<p>Eh, that's just because it's the current frontier model. Give it a few weeks, and prices will drop.
API prices are the new normal. I doubt that prices will drop to the level of the subsidized subscriptions any time soon. Usage is growing exponentially but capacity cannot. There is no reason for them to waste their capacity on subscription users if they can sell that same capacity to API users.<p>Like with Uber and Lyft, the low prices were a fight for market share, but now they have successfully captured that market share the focus changes to balancing their books.
I suspect subscriptions will stay. But you will see more and more roadblocks that the 'barely goes to the gym' user barely notices, but that the power user will chafe under.<p>I make that prediction, because the people who pay for subscriptions but only use them moderately at best are truly profitable.
[flagged]