ketzo

I totally agree and think this is The New Skill of software engineering: can you steer agents well enough to get work done at the speed they will allow, while still keeping enough context/understanding to step in when it matters?

not OP but usually for me this means long verification loop; waiting 10min on CI checks, that kind of thing, rather than actual 1hr wall clock of token generation

$19B -> $30B annualized revenue in a month?

Feels like the lede is buried here!

After seeing the last few releases for GPT and Claude, I’m not sure how anyone (else) is gonna build a durable advantage on proprietary model quality.

The capabilities of the top labs’ models have improved so much in just the last few releases, and I definitely foresee a world where they gate those models away behind 1st-party harnesses/tooling.

I think the core idea here is a good one.

But in many agent-skeptical pieces, I keep seeing this specific sentiment that “agent-written code is not production-ready,” and that just feels… wrong!

It’s just completely insane to me to look at the output of Claude code or Codex with frontier models and say “no, nothing that comes out of this can go straight to prod — I need to review every line.”

Yes, there are still issues, and yes, keeping mental context of your codebase’s architecture is critical, but I’m sorry, it just feels borderline archaic to pretend we’re gonna live in a world where these agents have to have a human poring over every single line they commit.

if you're cool just writing markdown files, I really like Astro for self-hosting static content.

Meta has shown a willingness to offer 9-digit pay packages to individual researchers. Even if they completely scrap the product, an acquihire of even a handful of Manus' top engineers/scientists here is totally in line with that kind of cash.

Yes, and some people are still happier there!

Different people can have wildly different expectations for a work environment, and wildly different tolerances of social discomfort.

> While running the exploit, CodeRabbit would still review our pull request and post a comment on the GitHub PR saying that it detected a critical security risk, yet the application would happily execute our code because it wouldn’t understand that this was actually running on their production system.

What a bizarre world we're living in, where computers can talk about how they're being hacked while it's happening.

Also, this is pretty worrisome:

> Being quick to respond and remediate, as the CodeRabbit team was, is a critical part of addressing vulnerabilities in modern, fast-moving environments. Other vendors we contacted never responded at all, and their products are still vulnerable. [emphasis mine]

Props to the CodeRabbit team, and, uh, watch yourself out there otherwise!

What does your Claude code usage look like if you’re getting limited in 30 minutes without running multiple instances? Massive codebase or something?

That is indeed exactly what the article says — I’m not certain GP is right on this.

Kenji’s original tests seem to confound this as well: every 2.5min of slicing produces steadily less juice, despite the fact that the steak’s internal temp should be rising for some of that time.

In what ways is that better for you than using eg Claude? Aren’t you then just “locked in” to having a cloud provider which offers those models cheaply?