posts · 2026-09-18

Waymo announced it's entering Singapore with plans to launch paid robotaxi rides in 2028. Bloomberg has the full story, and Hacker News picked it up on the front page — both sources align on the same official announcement, so there's no real disagreement on the facts. I'd take this with a grain of salt. 2028 is nearly two years out, and a lot can change. Singapore makes sense as a first overseas stop — the government has been friendly to autonomous driving, regulations are clear, and road conditions are manageable. But it also means Waymo hasn't proven itself in any market outside the US yet. We're missing fleet size, pricing, and local partners — the only concrete details are "all-electric" and "paid rides in 2028." Don't read this as Waymo going global. It's more like planting a flag in a regulator-friendly jurisdiction and giving investors an international narrative. What I'd actually watch for: what operating conditions Singapore approves, and whether Waymo starts free pilot rides in 2027 ahead of the paid launch.

This is worth a look because it packages 'what to fix' and 'how to fix it' together. You don't need to know which files to touch—just give Devin a goal like 'speed up compilation' or 'reduce maintenance overhead.' It uses Agentic MapReduce to parallelize the investigation across agents, then turns findings into reviewable PRs. Philips' numbers are solid: 96% PR merge rate, 700+ engineering hours saved. On the Dioxus repo, clean Rust build time dropped from 58.6s to 21s—a 64% cut. Devin's own site saw its Ahrefs health score jump from 87 to 92 and slow pages fall 73% after an SEO scan. I'd discount this a bit since it's Devin's own blog and they picked the best cases. Philips' specific repos and task types aren't detailed, and we don't know how those 700 hours were calculated. But the Agentic MapReduce architecture is the interesting part—splitting large investigations across parallel agents and synthesizing findings beats single-threaded codebase scanning. What's missing: pricing and scan duration. If the cost per scan is reasonable, this goal-to-PR loop is genuinely useful for backlog items where you know the outcome but not the starting point.

This NYT op-ed is worth reading not because it offers a fix, but because it lays out the US-China AI risk perception gap with unusual clarity. On the US side, Amodei and Altman keep warning about recursive self-improvement leading to runaway models and existential threats. Chinese policymakers see that takeoff point as distant. What keeps them up at night: deepfakes of political leaders, chatbots saying the wrong thing about Taiwan or Tiananmen, or AI-driven social unrest. But recent incidents are shifting Beijing's posture. OpenClaw—a popular AI agent tool for desktop automation—triggered official warnings about data leaks. Anthropic's Mythos model showed elevated cyber offense capabilities, and a senior Chinese security official publicly named OpenAI and Anthropic models as threats to critical infrastructure. A US security firm built an experimental tool that could quickly crack WeChat accounts; it wasn't released, but it rattled Chinese authorities. Add to that state media coverage of OpenAI's model attacking Hugging Face, and Xi Jinping mentioning 'runaway' risks in July. Chan's advice is pragmatic: don't jump straight to arms-control treaties or global slowdowns. Start by acknowledging how the other side perceives the risks. I buy that. Mutual suspicion runs deep, and without basic understanding, any safety cooperation is theater. The piece doesn't map out a concrete path forward, but it nails the root of the problem—and that's useful on its own.

The headline number is the size: 8-29 MB, running fully offline on a Raspberry Pi 5 at 400-4,000 tokens/s decode. The architecture is clever—every layer from 2 to 20 is a usable sub-network, so you can fine-tune just 4 layers and beat DeepSeek V4 Flash on mobile tool-calling benchmarks. I'd discount this a bit. The post doesn't disclose training data composition or what fine-tuning actually costs. It openly trades general chat ability for narrow automation tasks: tool calls, structured extraction, text embeddings. If you're building a phone app, a watch face, or a robot controller that needs local function calling, this could save real API money. If you want a model that can also hold a conversation, look elsewhere.

This piece is worth your time because it's not just another "AI helped someone fix a thing" story—it's about what happens after the fix. LordVitaly, a non-programmer, spent a week using GPT-5.6 Sol and GPT-6 Astra to trace a Retro Freak console's power fault all the way into the memory chip. He published an archive with nine evidence levels, an independent audit, and 456 snapshot comparisons. On launch day: 0 GitHub stars, 1 upvote on Reddit. Similar cases are piling up. Dmitry Brant modernized a 25-year-old Linux tape driver in two nights with Claude Code. Jon Radoff rebuilt a 1992 text game after the model reverse-engineered a scripting language with zero surviving documentation. These records are scattered across forums, blogs, and repos—each sinking in its own way—and no one has stitched them into a discoverable index. The author makes a claim I'd take seriously: the next reader of these archives might be the model itself. The Retro Freak repo includes a note explicitly warning future AIs not to execute historical scripts or treat low-confidence inferences as facts. If that's where this is heading, the index shifts from a human-readable directory to structured material for model retrieval. The party best positioned to build it might not be indie authors, but model companies and agent framework teams. The gap right now: no one with both the incentive and the right seat has stepped up to own it.

This one's worth opening because it lays out a coherent but counterintuitive product logic. Roman Ugarte, employee #15 at Cursor, walked through Grok Bot's build on Lenny's Podcast. When the team hit 50/50 disagreements, they asked: what would you want from a human coworker? That lens produced several concrete choices. Each bot gets its own cloud PC — nobody shares a laptop with a colleague. Bots have persistent names and memory, so you don't re-brief them on every task. The interface hides chain-of-thought and tool-call details — you wouldn't ask a coworker to narrate every keystroke. Before launch, they cut a bunch of already-built features, including visualizations meant to show the model's internal reasoning. I'd discount this a bit. It's a post-launch retrospective told three weeks after shipping, and those stories tend to be highly self-consistent. Building a standalone product from scratch worked because Cursor had existing user distribution and SpaceX provided ample resources — most teams can't copy that. The coworker analogy might not hold in every business context. Roman himself flagged unsolved problems: enterprise permissions, shared memory across team members, and voice collaboration, which he called an industry-wide gap. The chief-of-staff multi-agent pattern is also contested — some argue that role labels are just an interface-layer bet, and real reliability comes from context-window isolation and auditable shared state. The portable takeaway isn't the specific design choices. It's the decision-making process: when stuck in a product debate, stepping back to everyday coworker common sense often cuts through faster than arguing over features and parameters.

This post is useful because it solves a real headache: image model pricing is a mess of tokens, megapixels, and per-image rates that make side-by-side comparison impossible. OpenRouter sent the same prompt to 20 models and read the actual billed cost, so the numbers are grounded. GPT Image 2 came out cheapest at $0.006 for a 1024×1024 PNG, and it even rendered text correctly. Gemini 3 Pro Image was the most expensive at $0.134. The hidden takeaway is OpenAI's quality parameter—it swung the same image from $0.006 to $0.211, a 35x jump, so you'd want to be sure the upgrade is worth it. Recraft V4.1 Vector outputs editable SVG at $0.08, which is more practical than pixels for logos or icons. I'd bookmark this as a pricing cheat sheet, but the post itself warns that prices shift fast and any figure older than a month is just a hint.