GPT-5.1和Claude Opus 4.5使日常自主编码成为现实,AI工程师角色转向处理隐性决策、发现边缘案例及并行会话管理。Agent编码速度不再构成瓶颈,甚至需通过系统检查防止重复错误并控制发布节奏。
Coming back from @aiDotEngineer Code in San Francisco, I realized how much the AI Engineer profession has changed in just one year. It's wild.
A few cool talks helped me see the bigger picture.
When agents can write, run, and fix code on their own, what does the AI engineer do?
1. @simonw (interview dropping this week!) noted that GPT-5.1 and Claude Opus 4.5 made daily autonomous coding real. So engineers got freedom to move to other tasks, but the new challenge is handling all the small, unspoken decisions.
2. @lydiahallie, who works on Claude Code at Anthropic, showed how agents miss edge cases like keeping active users logged in during an auth update. The job shifts to spotting hidden assumptions, turning them into tests, and managing dozens of parallel sessions.
3. @poteto (Lauren Tan) shared how her team shipped 11,000 changes to Grok Bot in October while making it faster. The real work took ~6 months beforehand: encoding engineering experience into system checks so agents stop repeating the same bad shortcuts.
4. @Steve_Yegge proved that coding speed stops being the bottleneck. In his game Wyvern, agents shipped features so fast that players asked him to slow down and publish a roadmap just to keep up.
I packed many more insights, including the ones from Thariq Shihipar's talk, into this video to capture this new wave in AI engineering. Watch my full AIE Code overview here or on Youtube: https://www.youtube.com/watch?v=ZINu6a3kVnA
来源:Turing Post (Ksenia Se) · x.com