←back to thread

120 points cl42 | 2 comments | | HN request time: 0.4s | 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. sitkack ◴[] No.45075643[source]
> quality assurance and debugging

Saying the quiet part out loud. What kind of engineering org outsources this? 80% of engineering is confirming your design works, otherwise it is just LARPing.

replies(1): >>45081870 #
2. another_twist ◴[] No.45081870[source]
My thoughts exactly. Most of my coding is actually writing the tests or coming up with a proper harness to check behaviour of the code. Then of course there's other stuff like operations playbook if you are introducing new infrastructure. I have usually worked in environments where ops, q/a, design, code was the full job. First time I worked with explicit SREs it was a bit weird to give people specific commands to run without an overview of the system.