But I find your comment funny because it ironically has the same “not that, this” pattern in a more verbose and less polished & less formulaic pattern.
But I find your comment funny because it ironically has the same “not that, this” pattern in a more verbose and less polished & less formulaic pattern.
I basically have two modes
1. "Snipe mode"
I need to solve problem X, here I fire up my IDE, start codex up and begin prompting to find the bug fix. Most of the time I have enough domain context about the code that once it's found and fixed the issue it's trivial for to reconcile that it's good code and I am shipping it. I can be sniping several targets at anyone time.
Most of my day-to-day work is in snipe mode.
2. "Feature mode"
This is where I get agents to build features/apps, I've not used this mode in anger for anything other than toy/side projects and I would not be happy about the long term prospects of maintaining anything I've produced.
It's stupidly stupidly fun/addictive and yes satisfying! :)
I rebuilt a game that I used to play when I was 11 and still had a small community of people actively wanting to play it, entirely by vibe coding, it works, it's live and honestly I've had some of the most rewarding feedback from making that I've had in my career from complete strangers!
I've also built numerous tools for myself and my kids that I'd never of had time to build before, and I now can. Again the level of reward for building apps etc that my kids ( and their friends ) are using, is very different from anything I've been career wise.
A more valid design would be randomly assigning some cities to institute congestion pricing, and other cities to not have it. Obviously not feasible in practice, but that's at least the kind of thing to strive toward when designing these kinds of studies.
In any case, not every policy change needs to be an academic exercise.
Well, in a hundred years they should be able to afford a couple of new subway stations.
https://www.nytimes.com/2017/12/28/nyregion/new-york-subway-...
Apple doesn't need to solve AI. It's not core to their business in the same way that search engines aren't core to their business.
What Apple does best lies at the combination of hardware, software, physical materials, and human-computer interface design. This is why they're spending so much more on mixed reality than AI, even knowing that a product like the Vision Pro today isn't going to be a big seller. It's why they're investing in their own silicon. This strategy tends to yield unexpected wins, like the Mac Mini suddenly becoming one of the hottest computers in the world because it turns out it's amazing for sandboxing agents if you don't want to use the cloud, or the Mac Studio becoming arguably the best way to run local AI models (a nascent space that is on the cusp of becoming genuinely relevant), or the MacBook Pro becoming by far the best laptop in the world for productivity in the AI age (and it's not even close).
Your conclusion is that they're going to be left behind, but the evidence is that they're already well ahead in the areas that are core to their business. They can trivially pay Google a billion a year for Gemini. Nobody else can do what they can in the fusion of hardware, software, and materials as long as they stay focused.
Where they genuinely slipped up was their marketing -- an unusual mistake for Apple. And that does indeed lie with the CEO.
This was true maybe a decade ago, but not so now (under the watch of Tim Cook).
You listed Mac hardware becoming popular in the age of AI as examples of "unexpected wins". Maybe that's true (I don't know if it is) - but Macs were only 8% of Apple's 2025 revenue. Apple has become an iPhone company (50% of revenue) that sells services (26% of revenue).
And AI can eat away at both. If Siri sucks so hard that people switch away, that would also reduce Services revenue from lost App Store revenue cuts. If Google bundles Gemini with YouTube and Google Photos storage, people might cancel their iCloud subscriptions.
I think the parent comment was making the point that Tim Cook's Apple has missed the boat and it doesn't show signs that it's going to catch the next wave.
I have an iPhone 16 and I'm locked in because of all my photos being on my iCloud subscription. But in 2030, if my colleague can use their Pixel phone to record a work meeting, have it diarized, send out minutes, grab relevant info and surface it before the next relevant meeting, and Siri can still only set a timer for 5 minutes, then I might actually switch.