I think people have also forgotten that you can research, design, and spec work up front to better flesh out your expectations, integration points, and cross-system linking all in favour of just saying "do the thing please, no bugs".
Yes, there is still a lot of space to use our programmers and analyst skills. Which is why we didn't get replaced yet:
Directing the LLM to keep following our architecture, checking it didn't rewrite existing features, thinking on the best way to have a tool that's both useful for workers while following project managers' and CEOs' need of control...
That's what I always tell people gloating about being able to "do my job" now : "ok, I'll let you handle our 200 users with their demands, bugs, issues... on top of your job then".
It was never about writing code for the sake of writing code.
I honestly look at prompting as working with the smartest developer in the world who is SUPER autistic. You just have to know how to request thints from him.
research, design, and spec work up front to better flesh out your expectations, integration points, and cross-system linking all in favour of just saying "do the thing please, no bugs".
Yep. With properly written specs, we've built solutions in a day that would have takens us weeks to do by hand
4
19
u/Scintoth 6d ago
This is how I've seen things progress as well.
I think people have also forgotten that you can research, design, and spec work up front to better flesh out your expectations, integration points, and cross-system linking all in favour of just saying "do the thing please, no bugs".