Categories
AI Learning Photography

Autopilot

“Superb photographs are not just taken with cameras. They come from within you, your eyes, your mind, your heart, not ice cold equipment.” Fan Ho

There’s a half-second on the street, somewhere between seeing a frame and shooting it, that used to take me whole minutes. Early on, with a camera in my hands on the streets of San Francisco or on the subway platforms in New York, I’d see something — light falling a certain way, a gesture about to resolve into a gesture — and I’d think my way through it. Assess the composition or the angle. Worry about the background. By the time I’d worked it out, the moment might be gone, replaced by some lesser version of itself.

That doesn’t happen to me anymore, and I couldn’t tell you when it stopped. Somewhere along the way the thinking disappeared and the shooting stayed. I see the frame and the shutter goes, and only afterward, looking at the file, do I understand what I saw. I didn’t explicitly decide to skip the thinking. It just stopped showing up, the way a habit eventually stops asking your permission. Or how driving a car becomes second nature.

I think about this because of a problem the AI labs have been calling continual learning. The AI models we use are like brilliant interns. They can solve a hard problem at nine in the morning and a harder one by five, and they’ll astonish you doing it. But every session starts over from zero. Whatever they got right on Tuesday evaporates by Wednesday, the way a dream is gone by the time you’ve found your slippers.

The industry’s first answer was to give them a longer memory — let the window hold the whole case file in front of them, all the time. This works for a while, the same way it would work for me on the street if I stopped and re-derived the exposure math for every frame. But that isn’t how I shoot anymore. I don’t have the math open. I have what’s left after thousands of frames did the math for me and then got out of the way.

Based on some exploration I did this morning using AI I found three different AI research efforts that are now chasing that gap, from different angles, none of them all the way there.

A team out of Stanford and NVIDIA built something called TTT-E2E, which lets a model keep adjusting its own internal weights while it reads — not just holding the page in front of it, but being changed by the page, a little, as it goes. It runs thirty-five times faster than the brute-force method of remembering everything, because it isn’t remembering everything.

Google’s research arm published something called Nested Learning around the same time, built on the idea that a mind isn’t one system learning at one speed, but several systems nested inside each other — some updating by the minute, some by the year.

And a scrappier strand of work called self-distillation has models teaching cheaper versions of themselves, not by handing over a transcript, but by training the cheaper model to arrive on its own at whatever the well-informed version would have concluded.

None of this is what happens when I make a photo. Not yet. But it’s aimed at the same gap I live in every time I shoot before I understand what I’m shooting. The gap between having the math and having the eye.

I once asked Doug, a good friend who’s spent as many days on the street as I have, how he knew when to press the shutter. He didn’t have an answer, not really — just a shrug, and something about the moment feeling complete before he could explain why. That shrug took him years to earn. He didn’t keep the years. He kept the shrug.

And then a few years ago Doug did something I still don’t fully understand. He abandoned digital and went back to film. Not for any project, not for the look of it — he could get that in post if he wanted it. He went back to the actual mechanics: loading a roll, metering by hand, often using a tripod, etc. I needled him about it some, the way you’d needle a cigarette smoker who’d taken up a pipe instead, as if the inconvenience were the point. He told me he wanted to slow down, and that film was the only thing that reliably made him do it. Twelve frames and then you stop and reload and you can’t fix it later. The very friction he’d spent decades shooting his way out of, he went looking for again, on purpose.

I don’t know what to do with that, except to notice that he’s the same man who can give me the shrug and also the man who walked back toward the thing the shrug had replaced. Maybe that’s the part the labs haven’t gotten to yet, underneath all the vocabulary of weight updates and meta-learned initializations. Compression is the whole point, until the day it isn’t.

Note: This line of thinking started with a recent essay by Dwarkesh Patel on what he calls continual learning. It’s become a real focus of his thinking about how we get to a better future with AI.

See: https://www.dwarkesh.com/p/the-next-paradigm

Categories
AI Apple History iPhone

An iPhone in 1900?

This morning I was listening to one of Dwarkesh Patel’s latest podcasts when he happened to muse about why an iPhone wasn’t possible in the year 1000. A crazy idea or so it seemed to me!

But it got me wondering about that same question in years closer to when the iPhone was actually introduced in 2007.

I opened up Google Gemini (using the new 2.5 Flash model) and had a fascinating conversation. “A conversation like no other!” as Mark Halperin likes to say on his 2Way conversations.

Here’s the final result – after I asked Gemini to summarize the conversation a bit and put it into Markdown format for blog posting. To be clear, I asked the questions and Gemini did the educating and writing. Enjoy!

Building an iPhone Through Time: Why 1900, 1950, and Even 2000 Couldn’t Do It

We take our smartphones for granted today. These sleek, powerful devices fit in our pockets, connecting us instantly to the world, housing vast libraries of information and entertainment, and performing complex computations. But have you ever stopped to wonder what it would take to build something like an iPhone in a different era?

Let’s take a little journey through time and see just how science-fiction the iPhone would have seemed not so long ago.

The Utter Impossibility of 1900

Imagine walking into a workshop in 1900 and asking them to build you an iPhone. Their reaction would likely range from utter confusion to thinking you were stark mad. In 1900, the concept was not just difficult; it was fundamentally impossible.

  • Computing: The most advanced computing devices were mechanical or early electromechanical machines like punch-card tabulators. There were no vacuum tubes yet for practical electronics, let alone transistors or integrated circuits. Building anything with the processing power of an iPhone, even using room-sized 1900 tech, was unimaginable.
  • Display: Visual output was limited to mechanical indicators or basic light bulbs. The cathode ray tube (CRT) was still experimental. A high-resolution color touchscreen was pure fantasy.
  • Connectivity: Wireless communication was in its absolute infancy (Marconi’s transatlantic signal was Morse code). Mobile voice communication was decades away. The idea of connecting a personal device to a global network was beyond comprehension.
  • Storage: Data storage meant punch cards or paper tape – storing a single song, let alone thousands, would require a library-sized collection and complex machinery to read it.
  • Power: Batteries were bulky and low-capacity. Powering complex electronics wasn’t feasible for a portable device.
  • Size: Components were large, assembly was manual. Miniaturization to pocket size was impossible due to the fundamental physics and engineering available.

In 1900, an iPhone was not just science fiction; it was magic. You couldn’t build it because the scientific knowledge and engineering capabilities simply did not exist.

Closer, But Still Impossible in 1950

Fast forward 50 years to 1950. We’ve made incredible strides!

  • The transistor has been invented (1947), a crucial step beyond vacuum tubes.
  • Early electronic computers exist, albeit massive, expensive, and less powerful than today’s simplest chips.
  • CRTs are common (the television era is beginning), allowing for monochrome displays.
  • Radio communication is much more advanced, and early, very limited forms of mobile radio-telephony (like bulky car phones) are being experimented with.
  • Basic magnetic storage (tape, drums) exists.

So, could you build an iPhone now? Still impossible, but for slightly different reasons.

  • Integrated Circuits (Chips): The ability to put thousands or millions of transistors onto a single piece of silicon – the foundation of modern electronics – hadn’t been invented yet (that came in the late 1950s). Building an iPhone’s processor or memory still required assembling thousands of individual, relatively large components.
  • Miniaturization: While better than 1900, components were still too large and power-hungry for a handheld device with complex functionality. A computer capable of iPhone-like tasks would still be room-sized.
  • Display: While you could have a small monochrome CRT, it would be bulky and fragile. A flat-panel, color, high-resolution, touch screen was completely out of reach.
  • Connectivity: Mobile communication existed, but not in a cellular format, and certainly not for high-speed data like internet Browse. Connecting a personal device to a data network wasn’t feasible or even conceived of in the modern sense.
  • Storage: Storing gigabytes of data in a portable way was impossible.
  • Operating System & Software: Programming was done at a very low level, and the concept of a sophisticated, user-friendly operating system running rich applications on a personal device didn’t exist.

In 1950, you could build pieces of the puzzle (a basic computer, a radio), but combining them into a compact, interactive, networked personal device was still beyond the technological horizon.

On the Brink? The Year 2000

Now, let’s jump to the year 2000. We’re only 7 years away from the first iPhone launch. Surely, we could build it now? Almost, but still extremely difficult and not the iPhone as we know it.

By 2000, most of the fundamental components did exist:

  • Powerful Microprocessors: Processors capable of running complex software were common.
  • Color LCDs: Standard in laptops and high-end mobile devices.
  • Wireless: 2G cellular networks were widespread (GPRS offered slow data). Wi-Fi existed (802.11b). Bluetooth was available. GPS was available for civilian use.
  • Batteries: Lithium-ion batteries were standard for portable electronics.
  • Flash Memory: Available, but expensive and lower density per chip compared to 2007.
  • Basic Sensors & Digital Cameras: Existed and were being integrated into some phones/PDAs, albeit low-resolution.

So, what was still missing or not mature enough to build the iPhone?

  1. Capacitive Multi-Touch Screen: This was the key missing piece for the iPhone’s revolutionary interface. While resistive touchscreens (used with a stylus) were common on PDAs, large, reliable, capacitive screens capable of registering multiple finger touches were not ready for mass production and integration into a consumer device.
  2. Affordable High-Density Flash Memory: While flash existed, putting 4GB or more into a phone was still prohibitively expensive for a mass-market product.
  3. Required Chip Integration & Miniaturization: While processors were capable, packing all the necessary components (CPU, GPU, wireless, memory, sensors, etc.) so tightly and efficiently into a thin, integrated System-on-a-Chip required manufacturing advancements still underway.
  4. Mobile OS Optimized for Touch & Data: Existing mobile operating systems (like Palm OS, Windows CE, Symbian) were designed around styluses, keyboards, and less data-intensive use. An OS built from the ground up for a finger-driven multi-touch interface and seamless internet use (like iOS) didn’t exist yet.
  5. Network Readiness: While GPRS offered data, the speeds weren’t truly conducive to a rich mobile web experience. Widespread 3G networks, necessary for faster data, were just starting to roll out or hadn’t launched yet in many areas.

In 2000, you could build a smartphone (like a BlackBerry or a Pocket PC phone) – a device combining calls with email, calendar, and basic web Browse, likely with a physical keyboard or stylus. But the seamless, touch-driven, media-rich, always-connected experience of the iPhone wasn’t possible yet because the critical enabling technologies and the specific level of integration weren’t mature or affordable enough.

When Did It All Come Together?

The technologies that were missing or immature in 2000 converged and matured rapidly in the years leading up to the iPhone’s launch in 2007:

  • ~2004-2006: Capacitive multi-touch display technology became viable for mass production. Flash memory density increased and prices dropped dramatically. 3G networks rolled out more widely.
  • ~2004-2007: Apple internally developed iOS and perfected the integration of hardware, software, and the multi-touch interface. Chip manufacturing allowed for the necessary miniaturization and power efficiency.
  • 2007: The culmination of these advancements arrived as the first iPhone, combining these previously missing/immature pieces into a revolutionary product.
  • 2008: The App Store launched, solidifying the software ecosystem that became central to the smartphone experience.

Looking back from 2025, it’s incredible to see how quickly technology evolved. What was pure fantasy in 1900 became a bulky, impossible dream in 1950, a collection of nearly-ready parts in 2000, and finally, a reality in 2007. The journey of the iPhone isn’t just a product story; it’s a testament to the accelerating pace of scientific discovery and engineering innovation over the last century.