3 ms·
Exactly as I suggested, you've tossed non-coding activities into the coding category. Planning is not writing code. Imagine an architect who never writes a lin
by nitwit005 1y ago
Exactly as I suggested, you've tossed non-coding activities into the coding category. Planning is not writing code.
Imagine an architect who never writes a line of code. Under your accounting, they're doing coding, because it's the planning for code.
- crazygringo 1y agoYou seem to be having a different conversation. The root comment was about coding vs "design, quality assurance and debugging, art assets, localizations", etc. Not coding vs planning coding. It's the same way the art department both plans the art and draws it.
- deleted 1y ago[deleted]
- nitwit005 1y agoThe root conversation began with: > 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"? And you quoted "how many times" contradicting it. Yes, the art department plans the art and draws it, but an AI tool for generating art could only help with the actual drawing. The possible productivity improvement directly relates to the portion spend actually making art. Your department or job-role style view of things doesn't make sense for this conversation.