Is this what driving an F1 car feels like?
The article explores the evolving landscape of software engineering, likening it to the high-performance world of Formula 1 racing. It discusses the challenges and skills required to manage multiple AI agents in software development, emphasizing the importance of effective management over raw output. The author reflects on the new grading metrics for developers in this context, highlighting the collaborative nature of modern engineering teams.
- ▪The author reports a significant monthly token bill related to AI usage in software development.
- ▪Managing 10-15 concurrent AI agents presents challenges similar to scaling a product organization.
- ▪New metrics for software engineers focus on effective management of AI agents rather than just raw output.
2 outlets in our directory ran this story, first to last over 36 hours. All of the coverage we found sits in one bucket: lean left. That one-sidedness is itself worth noticing.
- ▪ It might feel like layoffs are soaring. They’re not. — Washington Post — Tech
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 publisher | Cameron Westland |
| Canonical URL | https://cameronwestland.com/is-this-what-driving-an-f1-car-feels-like/ |
| Publication time | Fri, 22 May 2026 20:47:32 +0000 |
| Retrieval time | 2026-05-22T21:02:03.031Z |
| Last seen | 2026-05-22T21:02:03.031Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | H5WqLETpGD8D · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
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
Is this what driving an F1 car feels like? May 20, 2026 My 30-day token bill is $11,232.54. Fourteen billion tokens, almost all of it GPT-5.5 on a ChatGPT Pro 20x plan. Yesterday alone I put $1,157.78 and 1.4 billion tokens through the harness. Today, mid-afternoon, I’m already at $226 and 270M. That’s nothing next to Peter Steinberger: $1.3M and 603 billion tokens against the OpenAI API in 30 days. Peter noted in replies that disabling fast mode would cut that ~70%, so the comparable number is closer to $390k. Either way, a different category: Peter has described his stack publicly, running ~100 Codex instances in the cloud doing PR review, security scans, issue de-duplication, performance benchmarks, meeting listeners that auto-start PRs.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Cameron Westland.