AI should only run as fast as we can catch up

Re:AI should only run as fast as we can catch up by Yoric on Monday December 08, 2025 @07:05PM (#46199508)

Exactly that.

I suspect that we're going to witness a (further) fork within developers. Let's call them the PM-style developers on one side and the system-style developers on the other.

The PM-style developers will be using popular loosely/dynamically-typed languages because they're easy to generate and they'll give you prototypes quickly.

The system-style developers will be using stricter languages and type systems and/or lots of TDD because this will make it easier to catch the generated code's blind spots.

One can imagine that these will be two clearly distinct professions with distinct toolsets.

[ Parent | on HN ]

Re:AI should only run as fast as we can catch up by OptionOfT on Monday December 08, 2025 @07:30PM (#46199761)

I actually think that the direct usage of AI will reduce in the system-style group (if it was ever large there).

There is a non-trivial cost in taking apart the AI code to ensure it's correct, even with tests. And I think it's easy to become slower than writing it from scratch.

[ Parent | on HN ]

Re:AI should only run as fast as we can catch up by Yoric on Friday December 12, 2025 @04:29AM (#46242390)

FWIW, I'm clearly system-style. Given that my current company has an AI product, I'm dogfooding it, and I've found good uses for it, mostly for running quick experiments, as a rubber duck, or for solving simple issues in config files, Makefiles, etc.

It doesn't get to generate much of the code I'm shipping, though.

[ Parent | on HN ]