Developer Workflow

Reading my feed on July 2 and 3 — Hacker News, X, blogs, WeChat — five engineering tips connected themselves into a single line in my head. The line used to live scattered across sources without anyone naming it. When it surfaced in 24 hours, it became hard to ignore. I am not going to write an “agent tool roundup” today — I did that on June 28 with a five-layer stack. That was the map. This piece wants to be the signposts. The thesis is simple: five teams that actually use agents in production hit the same wall in early July. They each gave their own answer. I want to put those answers on the same page and see what is shared. ...

If you only read feature comparison tables, Codex and Claude Code differ in thirty places: model choice, browser support, rate limits, phone handoff. That is not what I want to write about today. Today I want to write about a 350-like tweet, and the two core maintainers standing next to it. The tweet that broke the silence Peter Yang (@petergyang) writes the Practical AI tutorials newsletter, 150K+ subscribers. At 3:32 AM UTC on June 20, he posted: ...

The most expensive thing about being an AI engineer is not the model calls. It’s the meetings about the model calls. On 2026-06-18, Anthropic pushed out Claude Code Artifacts, and the timing feels deliberate. The product story they tell is small: a developer kicks off an incident investigation in Claude Code, and the agent publishes a page as it works. By the time standup starts, the page has refreshed twice, and the team is staring at the same URL instead of asking someone to walk them through what the agent found. That pitch is the entire reason I wanted to look at this. ...

On June 16, Vicki Boykis’s “Running local models is good now” hit Hacker News at #4 — 1044 points, 437 comments. Her machine is a 2022 M2 Mac, 64GB of RAM, 1TB of storage. Not an M3 Ultra workstation. The boring developer default. But Vicki did one useful thing in the post: she defined a personal vibe metric — “am I still double-checking against a cloud API?” — and then admitted that after GPT-OSS she does that “a lot less often,” and with the latest Gemma 4 release she can finally run local agentic coding loops at roughly 75% the accuracy and speed of frontier models. ...

A clear signal showed up on GitHub Trending today: agent skills are having a moment. On the daily chart, obra/superpowers reached rank 2 with an agentic skills framework and software development methodology. K-Dense-AI/scientific-agent-skills reached rank 3 with ready-to-use skills for research, science, engineering, analysis, finance, and writing. The monthly chart is even louder: mattpocock/skills, multica-ai/andrej-karpathy-skills, ComposioHQ/awesome-codex-skills, addyosmani/agent-skills, NousResearch/hermes-agent, zilliztech/claude-context, and rohitg00/agentmemory all appear in the same cluster. This is not just another batch of prompt templates. ...

OpenAI recently brought Codex into the ChatGPT apps for iPhone, iPad, and Android. At first glance, that sounds simple enough: now you can use Codex on your phone. I do not think that is the interesting part. Honestly, who wants to review code diffs on a phone for half an hour? That sounds more like punishment than productivity. The real point of Codex Mobile is that it turns the phone into a remote control for AI coding agents. The code still runs on your laptop, Mac mini, devbox, or remote environment. The phone is there for checking progress, answering questions, approving commands, changing direction, and dropping in a new task when an idea shows up. ...

Lately I have been feeling more and more strongly that one of the most overrated things in AI is the release of a new model itself. Not long ago, every new version triggered the same reaction: how much smarter is it, how much stronger is it, how high will it climb on the charts. That reflex is starting to wear out. It is not that models no longer matter. It is that users, especially developers, have become much more practical. Fine, you shipped an upgrade. But the real question now is: so what? ...