I'm a big fan of your blog simonw, and it's interesting to see how a few of the people you've responded to here aren't receptive at all to your responses.
I have become somewhat convinced that the 'ai doesn't help with programming crowd' is a little bit obtuse / entirely unwilling to experiment with new tools. It seems too much of a coincidence to see the same crowd that you've responded to struggle to perform basic website navigation and take anything away from your blog posts.
I keep experimenting because of comments like this and they still always have the same problems:
- Inability to stay self-consistent
- Random extra unused and unreachable code
- Constant wack a mole with issues they have
- Random opposite or adjacent thinking
- Assuming that how things work in one library or language must work the same in another
I then had someone say well... Just break up the work, but, that's also not what people say works for them, and also, you still have to side-eye the smaller stuff and it just gets exhausting.
A ton of studies show that if you know less than 80 about a field it'll get you to that 80 percent. And if you know more than that it'll bring you back down to 80% due to randomness, lack of data in the training, incompleteness in the model that your incomplete prompt amplifies, and just automation bias errors where you trusted something it did that you shouldn't have.
I would say that anyone claiming these things do everything are just simply new to systems.
I have become somewhat convinced that the 'ai doesn't help with programming crowd' is a little bit obtuse / entirely unwilling to experiment with new tools. It seems too much of a coincidence to see the same crowd that you've responded to struggle to perform basic website navigation and take anything away from your blog posts.