WeSearch
Writing Rust code that's fast by asking agents to make the code faster

Writing Rust code that's fast by asking agents to make the code faster

·24 min read · 0 reactions · 0 comments · 5 views
More from Max Woolf's Blog programming Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

That was prior to the advent of robust agentic coding, but Claude Sonnet 3.5 was still able to iteratively improve on algorithmic Python code. The “better” instruction turned out to be underspecified: Sonnet abused that ambiguity to instead add a ton of useless features but the code was indeed faster. You’ve been warned.Iterative “Benchmaxxing”#At first, making software faster was a good quantitative way for me to test and compare these new agentic models.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 2,003 of its stories. Top-voted stories on Hacker News.

Original article
Max Woolf's Blog
Read full at Max Woolf's Blog →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherMax Woolf's Blog
Canonical URLhttps://minimaxir.com/2026/09/agentic-iteration/
Publication timeTue, 22 Sep 2026 15:38:24 +0000
Retrieval time2026-09-22T16:18:54.225Z
Last seen2026-09-22T16:18:54.225Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster9MX7S3qloMm4 · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Writing Rust code that's faster than state-of-the-art libraries by asking agents to make the code fasterSeptember 21, 2026 · 26 minpre code.language-txt,pre code.language-md{white-space:pre-wrap!important;word-break:normal!important}In January 2025, I had a fun hypothesis for a blog post: can LLMs write better code if you keep asking them to “write better code”? That was prior to the advent of robust agentic coding, but Claude Sonnet 3.5 was still able to iteratively improve on algorithmic Python code. The “better” instruction turned out to be underspecified: Sonnet abused that ambiguity to instead add a ton of useless features but the code was indeed faster.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Max Woolf's Blog.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Max Woolf's Blog