AI Changed How We Build. It Did Not Change What Matters
1–5 of 5 posts
Re: AI Changed How We Build. It Did Not Change What Matters
#2Building 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.
Re: AI Changed How We Build. It Did Not Change What Matters
#3Re: AI Changed How We Build. It Did Not Change What Matters
#4But it did. What used to be unworthy of building is now totally doable. I can roll out one off ad-hoc UIs for our customer to navigate their bespoke data sets without having too much worry about expending a lot of development time to throw up a visualization page that may get discarded when its usefulness expires. So it has expanded the realm of the worthwhile if not necessarily the realm of the possible. At least no…
Re: AI Changed How We Build. It Did Not Change What Matters
#5But it did. What used to be unworthy of building is now totally doable. I can roll out one off ad-hoc UIs for our customer to navigate their bespoke data sets without having too much worry about expending a lot of development time to throw up a visualization page that may get discarded when its usefulness expires. So it has expanded the realm of the worthwhile if not necessarily the realm of the possible. At least no…
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.