Joe Johnson (@joerjohnson) header
Joe Johnson (@joerjohnson) profile picture

vice president @NxDevTools | investor | 3x startup vet | family first

Phoenix, AZ
Joined July 2007
Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)Photo by Joe Johnson (@joerjohnson)
In just a few weeks, for me, the idea of agents talking to each other has gone from ominous to expected behavior.
Replying to @ycombinator
Claudes generally established democracies, GPTs formed hives. In our seven match run, GPTs split factory ownership from the start and were very willing to supply resources towards shared goals. They also communicated more than the Claudes. Claudes operated on a “+1” system, under which their leader (who came to power after a dispute) and others needed many +1s in the team chat, without disagreements, to pass a proposal. They held this system for all ~9.5hrs of the series.
54
Joe Johnson retweeted
Nx 24 is out! • task-based affected is now the default • e2e specs get cached by the code they test • tasks can wait for a dev server to be ready • agents run your migrations step by step • ... Full release article 👇 nx.dev/blog/nx-24-release
1
10
2
53
4,788
Always great to see results like this!
Turned on @NxDevTools dynamic task packing in our CI: no more fixed --parallel, tasks land on agents by measured CPU + memory. Full runs (~3.6k tasks): ⏱️ 15.8 → 12.9 min 💸 −18% agent-min 🔥 Agent CPU 37% → 51% 🧠 Peak RAM 57% → 77%
58
Joe Johnson retweeted
Monorepos have become like TypeScript or Docker. They’re no longer a big statement, just a normal choice for many orgs and projects. Most teams don’t even call it a monorepo. That’ll only become more common, because keeping projects in the same repo is good for agents.
2
5
2
59
4,067
As token prices fall from efficiency gains, demand for compute increases, which drives compute prices higher.
I can't emphasize enough how important this @a16z chart seems and how few have internalized it.
1
53
Joe Johnson retweeted
Task-based "affected" is a big deal. Not because of what's there today, but because of what will be there in two weeks. Our next-gen cache is becoming GA. It gives you much more precise inputs and, as a result, a much more precise "affected." For example, most changes will only affect some atomized e2e tests => Huge compute savings.
🚀 Nx 23.3 is out. - Task-based nx affected - Agent-friendly task output - Batched Oxlint runs - Faster project graph creation - Cypress 16, Vitest 5, pnpm 12 And more. All the details 👇 nx.dev/blog/nx-23-3-release
6
3
1
37
3,905
Joe Johnson retweeted
🚀 Nx 23.3 is out. - Task-based nx affected - Agent-friendly task output - Batched Oxlint runs - Faster project graph creation - Cypress 16, Vitest 5, pnpm 12 And more. All the details 👇 nx.dev/blog/nx-23-3-release
1
8
2
54
7,564
Joe Johnson retweeted
We figured out how to make your CI burn A LOT less compute (and also make a lot faster). Quick video explaining the core insights. #monorepos @NxDevTools
1
4
1
16
2,261
Joe Johnson retweeted
Victor Savkin doing his best to “make software factories boring” at @WeAreDevs World Congress
3
3
21
2,108
Legora is one of the most AI-focused development teams I’ve seen. The volume of PRs they create is impressive, and their platform team has been great to work with. Together, we’ve kept CI fast as their team and output grew 6x, while cutting CI maintenance in half with Nx Agents. One of my favorite examples of how to scale the right way.
A 3-person platform team runs CI for a 600+ project Nx monorepo. With Nx Agents on Nx Cloud they: - maintain half the CI config and don't re-shard as new projects land - trust the cache again, thanks to task sandboxing How @WeAreLegora got there: nx.dev/blog/legora-success-s…
1
2
183
Joe Johnson retweeted
You can add Nx to an existing pnpm workspace without restructuring anything. Install nx at the root, add a small nx.json with your targetDefaults, and run tasks across every project with nx run-many. Caching and task ordering come from there.
3
6
1,142
🤩
Given the current explosion of PRs, distribution on CI is a must. But when hundreds of tasks spread across machines it can get tricky to stay on top of what needs your attention. Now you can, introducing the new Timeline View. nx.dev/blog/nx-cloud-timelin…
1
101
Coding agents can deliver working code in minutes — and break your architecture just as fast. This Thursday, I’ll show how to prevent that: rules, hooks, skills, Loop Engineering & MCP reviews. 📅 Sep 24 · 3 PM CEST 🌐 Free webinar + Q&A 👇 Details & registration in comments
4
2
1
13
2,850
Joe Johnson retweeted
Haven't tweeted in weeks. I've been heads down with my team on some key improvements to Nx Cloud. The result: the same workload needs less than 50% of compute than traditional CI (compute is a polite word for $$$), and it runs much faster. #monorepos @NxDevTools
2
4
12
1,187
I hope he’s ok.
This quoted post is unavailable.
2
86
Exciting additions coming soon!
We've got some huge CI performance features coming to Nx Cloud soon, but @victorsavkin won't let me talk about them yet, so all I can do is tweet this censored graphic of one feature.
3
112
“.. S&P 1500 Software revenue per employee has gone parabolic. If you are looking for evidence that AI is starting to impact the real economy, this is exhibit A.” (via OpCo desk) @3F_Research
24
34
6
204
74,853
Joe Johnson retweeted
The @NxCloudApp team is dropping something big for Nx Agents users next week 🥳 ✨
1
2
1
4
629