←back to thread

120 points cl42 | 1 comments | | HN request time: 0.206s | source
Show context
xenotux ◴[] No.45075415[source]
Coding as such is seldom a bottleneck to begin with. How many times have you been in a conversation along the lines of "we have every detail of the product figured out, but we need another month for the coders to finish writing the code"?

The bottlenecks are almost always elsewhere. Design, quality assurance and debugging, art assets, localizations, hiring, performance management, you name it. And to be fair, AI can streamline some of that.

replies(4): >>45075460 #>>45075490 #>>45075564 #>>45075643 #
1. crystal_revenge ◴[] No.45075564[source]
> quality assurance and debugging

This is still part of “coding”. It doesn’t make any sense to say you’ve “finished coding” when the program doesn’t actually work as required.

I’ve been aghast to see developers present an unequivocally broken product and try to argue making it not visibly broken is “scope creep”.

I mean, that’s why we argue so much about the best ways to write code: we want to reduce the incidence of bugs and make it easier to correct unexpected errors.