←back to thread

120 points cl42 | 1 comments | | HN request time: 0s | 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 #
crazygringo ◴[] No.45075490[source]
> How many times...

Literally all the time? Every single month?

I am struggling to understand your perspective. In my existence, the bottleneck is always the coding.

The development team has a backlog that could keep them busy for years. Meanwhile, everyone else -- QA, localization, whatever -- operates at whatever pace the code gets delivered.

Never in my entire life have I been in the situation where the engineering manager said, "well folks, localization is backed up so we've got no more code we need to write. Go home and check in next week to see if we have any work?"

The only exception I can think of might be videogames where the bottleneck is the art and then maybe the testing loop. But gaming isn't representative of software development generally at all.

replies(7): >>45075516 #>>45075531 #>>45075599 #>>45075617 #>>45076502 #>>45081051 #>>45086644 #
1. mrbombastic ◴[] No.45075531[source]
I find it is either coding or design but yeah not sure where the perspective of the GP come from, that has not been my experience. I have actually vented with other devs about too many brainstorming meetings, ideas of what to do we are never short on. Maybe where I agree slightly is the devil is in the maintenance, ai can maybe? help with that but i think you will quickly reach a saturation point where you have more than you can manage.