Thing is, and LLM doesn't need motivation or self-discipline to start writing, which at this point I'm confident is the main slowing down factor in software development, after requirements etc.
These also have larger memory in a way, or deeper stacks of facts. They seems to be able to explore way more sources rapidly and thus emit a solution with more knowledge. As a human I will explore less before trying to solve a problem, and only if that fails I will dig deeper.
90% of writing code, sure. But most professionnel programmers write code maybe 20% of the time. A lot of the time is spent clarifying requirements and similar stuff.
The more I hear about other developers' work, the more varied it seems. I've had a few different roles, from one programmer in a huge org to lead programmer in a small team, with a few stints of technical expert in-between. For each the kind of work I do most has varied a lot, but it's never been mostly about "clarifying requirements". As a grunt worker I mostly just wrote and tested code. As a lead I spent most time mentoring, reviewing code, or in meetings. These days I spend most of my time debugging issues and staring at graphics debugger captures.
Any chance the business/product folks will be using LLMs on their side to help with "clarifying requirements" before they turn them over to the developers?
They view this task as tedious minutia which is the sort of thing LLMs like to churn out.
Cthulhu_|3 months ago
agumonkey|3 months ago
oblio|3 months ago
Agentlien|3 months ago
SoftTalker|3 months ago
They view this task as tedious minutia which is the sort of thing LLMs like to churn out.
nwienert|3 months ago
taco_emoji|3 months ago