piljoong

I agree. AI clearly expanded the set of things that are worth building, especially small or previously unjustifiable work. What I was trying to say is that once those things become real systems, the old constraints show up again. You still have to understand boundaries, failure modes, and how to operate what got produced.

I've been using coding agents a lot recently.

Building got faster.

But when the system actually has to run, the same issues come back: failure modes, unclear boundaries, things going wrong in ways that are not always visible.

So it no longer feels like the problem is "can we build this".

It feels more like the real problem is whether we can still understand and operate what gets produced.

I wrote this to make that framing clearer.

Curious if others are seeing something similar.

This isn’t really a common-folk-vs-tech-bros story. It’s about one specific part of Seattle’s tech culture reacting to AI hype. People outside that circle often have very different incentives.

This is a surprisingly bold but overdue move. AWS and Google Cloud offering private, high-speed multicloud connectivity could finally clean up the DIY networking sprawl a lot of teams have been stuck with. If it works as described, latency, billing complexity, and day-to-day maintenance all get noticeably simpler.

Seven years leading AI at Apple, and Siri never meaningfully improved for most users. Leadership changes alone won’t fix that, but maybe this is finally Apple acknowledging that its voice/AI strategy needs a reset.