#Coding

AII think Tibo @thsottiaux is OpenAI's 雨宫阳平 (Yohei Amemiya). Whatever new Codex feature he talks about no longer matters; everyone is just waiting for that one line: Codex Reset "Chinese cold noodles are now being served!"

AIThe article explains how a software factory combines agents, tools, and engineering practices to take work from intent to verified output. It argues that teams should enforce domain rules, workflow gates, and tool permissions independently, version shared guidance and checks, and review lessons before reuse.

AIA Chinese podcast transcript argues that Opus 5.5 makes code generation, game modding, and language migration much faster and cheaper. It cites examples such as game remakes, Photoshop clones, and ESP32 firmware projects, and says legal and open-source barriers are struggling to keep pace.

AIAdo Kukic, who works at Anthropic, says he had his most productive coding day of the year so far on the weekend after Opus 5.5 launched. The post gives no details on the tasks, measured output, or specific features he used.

AIBen Tossell says "slop" is now also used to describe something just made that works, leaving its use to the reader. A reply from @forgebitz argues that much pre-AI code was also low quality.

AILauren Tan argues that with frontier AI agents, anyone can produce code at machine speed, so PR volume now signals productivity alongside impact. She says the bottleneck is trust in agent output, and that higher token costs are worth it compared with hiring many engineers. She frames the engineer's job as building the software-producing machine rather than writing code directly.

AITessl argues AI code review is slow because generated code outpaces trust, and proposes executable specs that let agents check preview environments against product intent. Its spec reviewer splits work between a planner agent that extracts requirements and parallel verifier agents that test each one against the code and base branch.

AISoftware developer Gergely Orosz questions why he is working more despite AI tools, quoting Sam Newman's view that AI was meant to free developers from drudgery. Newman says most developers are doing more work, with more context switching and a loss of the big picture. The quoted post adds that AI assistants are not human partners and that pairing with them fragments the shared mental model of a program.

AILucas Beyer says he learned Python around 2004 as Blender's scripting language, long before deep learning. He calls it a full-circle moment, as the linked post shows LLMs writing Blender Python code to generate 3D scenes.

AIThe author argues that in agent workflows, the real bottleneck is whether users can precisely express requirements, not the model or agent capability. When people work outside their expertise, they lack the precision needed for prompts and plans, forcing many imprecise iterations that waste time and tokens. The suggested fix is to have the model first teach the unfamiliar domain knowledge before acting.

AIThe author repeatedly asked Claude whether to rewrite all their Go applications in Rust. Claude discouraged the move, arguing a rewrite is unnecessary and Go is more than sufficient, though the author still feels the urge.

AIBlock's AI capabilities lead describes using Claude Fable to plan large code migrations and direct smaller models like Opus and Sonnet on individual tasks. He says Block routes frontier and smaller models by task and keeps merges and production deploys behind human dual approval.

Why it matters: Block's engineering lead describes how frontier models orchestrate large migrations and how access, effort levels, and safeguards are managed across an organization.

AIThariq, of Anthropic, says the most common failure in AI coding is users working outside their domain who cannot write precise prompts and plans. As a result, they spend many turns iterating imprecisely. The quoted post contrasts this with programmers' advantage in vibe coding.

AIThis Next Token episode discusses Personal Agents, including Dots in Codex, memory and cloud computer permissions, and whether agents should act as assistants or digital twins. The hosts also cover Instinct's booking and business-travel model, hands-on projects built with Opus 5.5, and whether software, games, and hardware could become open source as AI makes rewriting easier.

AIBoris Cherny, who owns the Anthropic account, says a feature was built from one prompt and Claude verified it well. He reports no bugs so far.

AILauren Tan (@poteto) proposes "time to (fully automated, hands-off) rewrite" (TTR) as a rough thought-experiment heuristic for how well a codebase is set up for agents. She suggests asking how long a single engineer would need to rewrite the code in another language, framework, or architecture, since the answer surfaces gaps like missing verification that agents can use to confirm user-visible behavior matches. The post also raises questions about whether a rewrite would improve, maintain, or regress performance and maintainability over time.

AIAnthropic's Lydia Hallie says Claude Haiku 5.5 suits mostly reading, small edits, and tool calls that need little reasoning. The quoted @claudeai post introduces Haiku 5.5 as Anthropic's cheapest, fastest, and most capable small model, costing around 75% less to run than Claude Haiku 4.5.

AIA startup's founders report that a single engineer built polished, reliable web, desktop, iOS, and Android apps in six months using AI. The post argues AI is turning 10x engineers into 100x engineers, a capability it says was not possible last year.

AISantiago reflects that prompt engineering once seemed poised to become a profitable career. The post is short and adds no further detail, so the summary stays brief. The quoted @bcherny post adds the main context: prompting Claude should resemble talking to a coworker, and it matters most to state the goal, effort level, and verification method.

AIThe newsletter argues that AI competition is shifting toward completed workflows, citing OpenAI's September 29 DevDay announcements on cost and infrastructure and Google's September 30 introduction of Gemini 4 Argon for longer, more demanding reasoning tasks. It says coding agents must inspect repositories, edit code, run tests, and deliver reviewable work, so cost, context, and supervision matter alongside model intelligence.

AIGergely Orosz argues that rapid AI change is real and not mere FOMO, because companies that ignore it risk business damage. He cites JetBrains missing out on agentic harnesses as an example. A quoted post reports that JetBrains recorded its first net financial loss in its tracked history.

AIAmjad Masad says AI-powered reverse engineering and decompilation are progressing rapidly, and predicts that soon all software will be de facto open-source. He frames this as part of AI's broader reach into everything.

AIMIT's 6.S950 "Agency with AI" course has released Lecture 4, "The Abstraction Ladder (of Programming)," which compares today's prompt-driven coding with the 1957 FORTRAN paper by Backus et al. The lecture argues that the objections to vibe coding echo the arguments once raised against compilers, but natural-language "compilation" differs because the same prompt can yield different programs each time, unlike deterministic translation.

AIswyx asks readers what coding agent they currently use as their default workhorse in October 2026. The post is a brief question with no further detail on tools, models, or results.

AIThariq argues that working at a higher level of abstraction has always required understanding the levels beneath it. He says coding agents do not change this requirement.

AIAt a recent AI workshop, switching the desktop app from ChatGPT to Codex drew the loudest reaction of the day from subject-matter experts who use ChatGPT daily. Allie K. Miller argues that enterprise AI knowledge is overestimated, suggesting AI training for SMB and enterprise teams is a lucrative opportunity.

AITibo of OpenAI advises users to switch from full-access to auto-review mode. He says the change is no longer a trade-off and offers greater peace of mind.

AIHarrison Chase, founder of LangChain, endorsed a post on harnesses with the brief comment "Good take on harnesses." The post, from @zeeg, argues that general coding harnesses like Codex will be superseded by specialized ones and that local models will handle most daily tasks within five years.

AIThariq (@trq212) says he particularly likes the call stacks feature and the ability to annotate code snippets. He credits the call stacks idea to @dillon_mulroy. The post does not specify the product or tool in which these features appear.

AIAlexander Doria argues that sandboxes are the new tokens, a claim presented without elaboration. The post quotes Reflection AI's introduction of Beam, an agentic open model with 501B total parameters and 23B active, with full weights to be released this month.

AIAdo Kukic, an Anthropic-affiliated account, posted an enthusiastic one-line message saying Go plus Opus 5.5 means "shipping." The post gives no details on features, benchmarks, or specific use cases.

AILewis Tunstall reports that when Claude and Codex review each other's PRs, Claude's reviews are packed with blockers and nitpicks, while Codex usually approves with LGTM. He suggests this could mean Opus 5.5 is the strongest coder right now, or that GPT 6.1 Sol is simply more lenient.

AIDex Horthy argues there will always be an advantage in reviewing AI output, since unreviewed work tends toward generic "AI slop." He adds that the reviewed object may not always be code, and speculates that once models far surpass humans, human interference could make results worse.

AIVercel completed migrating Turborepo from Go to Rust, which Rauch says was chosen for better low-level OS access despite controversial returns on human migration costs. He argues that what is best for humans is no longer necessarily best for business now that agents are writing code, and suggests Rust may not be the final toolchain.

AIJerry Liu says ChatGPT/Codex currently has the best agent interface for deep work, unifying coding and knowledge work in one place with forking support that Claude's app lacks. He still prefers Claude Code CLI as close to the best a CLI can be, and uses Opus 5.5 mainly through it for product demos, while noting a GUI is sometimes nicer.

AIThe poster calls GPT-6.1-Sol their go-to model for both work and personal use, saying it is "all you need." Citing Arena's real-usage cost-per-task data, they claim users should get about 5x more usage from GPT-6.1-Sol than from Astra.

AIThe author tracked token usage over three days and estimated that a $200 Claude plan delivers about $3,400 of API-equivalent value per week, versus about $1,700 for a $200 Codex plan. With cache hit rates of 98.94% for Claude Code and 98.34% for Codex, the author says GPT-6 Astra costs roughly five times more than Claude Opus 5.5, making the Claude weekly quota last about ten times longer.

AIThe post argues that in the agent era, AI-driven PR review has become a tool for malicious office politics. Because AI reviews can be used to wear down targets' tokens and positive sentiment, malicious intent is harder to detect than in human review.

AIYuchen Jin argues that terminals, built around files, commands, and processes, are giving way to AI agents where users state intent and the agent operates the machine. He says understanding Linux and systems fundamentals remains valuable as a moat. In a follow-up, he calls the terminal era over for coding agents, saying persistent context matters more than tabs, and names the Codex desktop app as the best agentic UI for now.

AIA post from Anthropic's Ado Kukic says Opus 5.5 at medium and high effort has never hit the 5-hour limit, with the closest single session reaching about 74%. He says this has significantly changed his workflows and asks others about their experience.