1. You don’t know anything about me, so don’t presume.
2. Which nursery rhyme? The tortoise and the hare is a fable, not a nursery rhyme. Even if you think the lesson was “faster is not always better,” which it wasn’t, faster is sometimes better. And in particular, when a machine is involved, all things being equal, faster is better. Would you rather use a fast compiler or a slow compiler, all things being equal except cost to keep the analogy with the original? Compiler A produces the same binary with the same optimization levels a compiler B, but in 1/10th the time. Assuming you can afford it or someone above you in your organization is willing to buy it for you, you take compiler A. If you can’t afford it, you lust after it. Why, because a slow compiler results in a slow iteration loop no matter what. With an instantaneous compiler, the loop is as slow or fast as the human part of it. You want to think some more, rearchitect this or that? Fine. Your code is always ready to run.
I get the sense that you’re anti-AI. That’s fine. I’m not sold myself, though I’m increasingly trending that way. For those that choose to use AI, I submit that a fast AI, all things equal (same output), is better than a slow AI for the same reason that a fast compiler is more preferable. Note that I’m not saying that faster overall development at all costs is preferable, or that we should just throw everything at the AI and stop thinking.