The title of this article is weird. If it compresses code production but not engineering judgement, if your judgement/architecture is doing fine, won't that lead to increased velocity? That doesn't seem like an illusion. Compressing code production sounds like an actual increase in velocity if the engineer was spending a significant amount of time writing code.
That is the weird part of this all AI coding, you would think that was the case, but in reality, you found all kind of architectural gaps due to lack of constraints enforcement. The article describes in more details about this high believability software phenomenon.
The title of this article is weird. If it compresses code production but not engineering judgement, if your judgement/architecture is doing fine, won't that lead to increased velocity? That doesn't seem like an illusion. Compressing code production sounds like an actual increase in velocity if the engineer was spending a significant amount of time writing code.
That is the weird part of this all AI coding, you would think that was the case, but in reality, you found all kind of architectural gaps due to lack of constraints enforcement. The article describes in more details about this high believability software phenomenon.
Interesting, nice article.
Thank you.
[flagged]
[flagged]