beecasthurlbow

If you use agents to generate formal verification, how do you tell if the properties that are verified are the correct ones?

KeyError localizes the issue to the lookup (ie “right here this key should be present and it’s not) vs later in the code where it can be hard to trace where the None value came from or how to handle it.

How would you recommend others get access to the kind of support that worked for you? Is there a specific type of therapist or coach?

They also halved API prices with GPT-6, so I think it’ll net out pretty close for sol and Luna, but much less to be used for Astra.

> I don't understand how this helps. CNAMES have TTLs like A records and they eventually have to terminate at an A record somewhere so why pay for an extra hop?

I assume the customer controls the domain DNS records here rather than the hosting provider.

CNAME record: hosting provider can change underlying IP freely.

A record: hosting provider must get in touch with customer to change DNS.

So do you still have humans doing code review? What did “sign off on code” look like in practice? (We’ve been thinking about this a lot too)

What plans did you put in place? What did you do to ensure knowledge transfer?

It seems like you're saying "This is a platform to iterate on your agents and make them better over time", but the headline of your site does not communicate that at all.

Your website is full of AI-isms, which makes it hard to parse what you're doing. (3 punchy sentence headline, "X is not Y." , "never able to claim").

Sounds like you have a cool product, try writing at least the front page of your site yourself and it'll be much much more engaging.

What does "changing the specialist" mean? changing the model? The prompt?

I’ll try it thanks! I just got good mileage out of “don’t use ‘X, never Y’ format” on a document too, but I think linear deductive flow Covers it

> I expect the gruesome writing style of LLMs to be fixed relatively soon, seeing how it can already be prevented with just a few lines of stylistic instructions

What instructions do you use to prevent the gruesome writing style? I have… not found this to be the case.

Agreed. Throwing it back into an AI tool to condense it helps, but def hard to read.

I’ve been using both, but I find 5.6 sol is faster in terms of wallclock time and far less chatty (on my small projects in non-legacy code bases).

It “feels” like Sol gets off track more easily than Fable (it’s hard for Sol to ignore a stray remark). My theory is this comes from smaller context window - Codex uses a 350K token context window (that you can’t change), even though model can handle more…

What do you mean? Could you expand on your answer?

His explanation seems pretty reasonable, no?

> He pointed out that the Connectors page featured OpenAI and Anthropic, two companies that hadn’t contributed to the WordPress project and nobody had complained about their inclusion. He said Google had contributed in the past but had stopped. > “… how ridiculous is it attacking Akismet, and Automattic, and blocking the thing the person who is our [release] lead asked for,” Mullenweg wrote.