|
|
|
|
|
|
by toastmaster11
13 days ago
|
|
|
All that stuff you mentioned is derived from a core set of principles established by decades of software best practices applied to a new means of generating code. Like quite literally those instruction files/skills essentially just reiterate the practices themselves. To your last paragraph, I never say that nor do I imply it. I find that as a pretty disingenuous interpretation of what I said actually. The practices I mentioned were derived from hard learned lessons and designed as a means of mitigating the human tendency to write bad code. |
|
|
The whole point is that the problem was already here, and the solutions were developed over a decade ago because the old time way of developing software was exemplary in the volume of shit it generated and had to be reigned in.
It's disingenuous to blame AI for yesterday's problems.
> The practices I mentioned were derived from hard learned lessons and designed as a means of mitigating the human tendency to write bad code.
That's the whole point. It's silly to pretend that AI invented bad code. It was already here, and in high volume. Ironically, AI is contributing to greatly improve the quality of existing code, but as the same shit coders are at the helm of course you still get the result of the same level of oversight.