Needed a parking pass at work so I asked Grok in my Tesla to get one. It created a @bot to search notion, find the form, and fill it out. Grok even setup a routine to watch for any messages about the pass. Was ready by the time I left work tonight. Continually amazed by how productive Grok has become over the last few months.

Grok Bot in Tesla is so damn good. Just used it to publish npm libraries, review github notifications, run some evals, and close out stale PRs. Perfect continuity across mobile, desktop, and now my car.

GROK BOT JUST FOUND $986 IN MY EMAIL 🤯 I asked Grok to get a parking spot for the car it bought me, and on the way it discovered nearly a thousand dollars of extraneous charges from my apartment and emailed them asking for a refund.

I absolutely love Apple SDKs. My first language was Objective-C, I won a scholarship to WWDC, and I started my career as an iOS dev. I firmly believe the best apps feel native to the OS, using platform primitives and human interface guidelines. But we need to stop it with the class wars. Apple's tooling has atrophied and practices have become hostile. Developers expect web-like iteration speed, and want to ship the same high-quality apps on multiple platforms with small teams. I love my toolchain. We use React Native because I feel like it allows our teams to ship the level of polish and quality I've come to expect from excellent mobile apps at a fraction of the effort. I might not have the same opinion in 6 months, and you don't have to agree, but I'm tired of the tool being the measure of the developer. Use the best tool for the job, build a great app and let your work speak for itself.

Between this and the new request routing through your own device, Grok is quickly becoming the most capable agent for my most laborious tasks. In hindsight, it’s crazy how much I was letting less useful agents automate the more enjoyable things like deep-research, while I took on the repetitive work. With Grok Bot, I think more carefully about the work I enjoy doing and let my agents do everything else.

I hate how imprecise the term “native” has become. Is a UIKit app that mostly displays WebViews, such as Apple News, not a native app? What about an app that’s entirely rendered with UIKit or SwiftUI, but orchestrated by a bytecode file, as with React Native? How about a social network app that’s so server-driven it makes network round-trips before navigation? Do you trust that an app built with UIKit is doing concurrency better than the reasonable defaults of SwiftUI? Today, software is developed in natural language. When you use imprecise prompts, you get sloppy results. I ban my agents from using the term “native” to describe technical details. Your agent will inherit your principles, so why allow any room for ambiguity? Reject technical imprecision. Be curious about performance characteristics, and strive for data-backed answers.