
Dear developers: Your next programming language is marketing. Good luck.

Full time apprentice human.

Dear developers: Your next programming language is marketing. Good luck.

I’ve always thought you could tell how clearly a company thinks by reading its code. When I see things named file, document, contract, and agreement used interchangeably, I wonder if the teams agree on what they’re building. It's all agents writing now, but it means someone prompted this way and the agent didn't want to be fired and just slopped it. Am I being too pedantic now and just let the agents cook because it's gotten worse? Does it even matter anymore?

The @expo Exact team buried the lead. It’s not about startup speed. I’m 99% through porting an app I’ve spent 3.5 years building, in 4 days with Expo’s Exact. Faster, better-looking, easier to iterate on. Cost $1000 of tokens ~7M output tokens (compared to the 140M for the C compiler rewrite). I’m using it against our production APIs now. We’re dogfooding with it. 🤯 The main takeaway is that we built our developer tools around human clock speed. The Exact team are showing what happens when you rethink that from first primitives. The combination of clock tools, css and contracts as a ui language fundamentally is the unlock. Exact does what it says, it gives you exactly what you asked for and usually better. Unfortunately, I’m running out of engineering excuses to avoid joining the marketing team now.

Watching us build these amazing dev envs for “agents” is us having reached the “I want a better life for my kids” phase
Coding agents write mobile code faster than any team can review it. 🙌 Introducing Expo Simulators: cloud simulators built for agents. Your agent runs its change on a cloud simulator or emulator and brings back the recording before it asks for your attention.


5. Localhost hides network, so added a localhost proxy to throttle to 200ms to see the fetch/load pains.

4. Every screens data seemed to load on restart, added a gate to say "this tab is now open" as by default it looks to be triggered by a resource load and not visible. This works in RN with hooks only running on component mounts. Maybe the agents didn't have the right tools.

2. The default agent behavior is to put all resources in the root and the data sources would all initialize together. 3. Looks like intersect says that all elements are on the screen, so a lot of over fetching. Had to work around this.

Did not look at the code, but had to drive the agents around a few sticky areas. Very impressed. Compile times fast, and agents did their thing very well. 1. Fetch seems to be serialized across the entire app and Promise.all in a data source runs serially as well. Spent a lot of time on finessing how images/videos/data sources are fetched or app loaded too slowly.

👋🏼 @ccheever our rewrite mostly completed. Memory before/after 547MiB vs 131MiB, bundle 98MB vs 55MB.
I want to share a preview of something I've been working on called Exact. It's a new Agent Native app framework written in Rust. It's extremely fast and tries to let you build exactly the experience you want with no compromises.

Wow, one of the best ideas and execution I’ve seen in a while. I’m migrating today to test.
I want to share a preview of something I've been working on called Exact. It's a new Agent Native app framework written in Rust. It's extremely fast and tries to let you build exactly the experience you want with no compromises.

Been taking my son to Senator games since he was little. Now we’re both software devs, and we just did a hackathon together, building software to help our fav NHL team. The work is under NDA but proud dad is under no such restrictions 😆 Doesn’t get better than this.

I've got two developers on my team. One is shipping at a speed he never thought possible. The other wants to know who the fuck approved this code... and unfortunately we share a keyboard.

A CEO recently called me the "both" guy. He said that when ever he asks me about two options, most often than not, I'll say do "both". There's a lot of cargo culting around extreme focus, and not doing too many things at once. "Put more wood behind fewer arrows"... but they didn't say "one arrow". Imagine a tradeoff between going to the gym and having a great family life. Do both. If you want to ship crazy quickly and be creative but also build infrastructure. Why not both? If you want to talk with your team with absolute clarity or more nuance. Do both. This is the Paradox mindset... accepting and engaging with competing demands. Demands that seem contradictory, are connected, and keep recurring. Remove one option today does not permanently remove the tension. So learn to live with them vs illiminating one. In a company, you have to setup the structures and culture to have two very different types or styles of work. But you have to learn to do that earlier than you think. I know CEOs are known for running after shinny projects or ideas all the time and the teams often complain "we need to focus". That's also true. But it doesn't mean do one thing. Or be one kind of leader. Or just because you like ice cream, you can't have a six pack ;) I'm not advocating for doing "everything", and you do have to practice subtraction... but if two ideas or skills seem important, do both.

The secret to speed is almost always clarity, including making it clear that we will decide without clarity. The irony is delicious, I know. But it works.

I’ve spent the last month chiseling our UX. It' great to have the time and it's what my agents suck at so it feels like we're working with our respective strengths. They offer good ideas, but can't invent the path we're going. Coding feels 100x sped up, but design is just 2x and most of that is idea generation not finished products. I’m a UXer now? Didn't see that coming.