Am trying to compare this to reports that people are not reviewing code any more.
For me this is a huge boost in productivity. If I remember how I was working in the past (example of Google integration):
Before:
* go through docs to understand how to start (quick start) and things to know
* start boilerplate (e.g. install the scripts/libs)
* figure out configs to enable in GCP console
* integrate basic API and test
* of course it fails, because its Google API, so difficult to work with
* along the way figure out why Python lib is failing to install, oh version mismatch, ohh gcc not installed, ohh libffmpeg is required,...
* somehow copy paste and integrate first basic API
* prepare for production, ohhh production requires different type of Auth flow
* deploy, redeploy, fix, deploy, redeploy
* 3 days later -> finally hello world is working
Now: * Hey my LLM buddy, I want to integrate Google API, where do I start, come up with a plan
* Enable things which requires manual intervention
* In the meantime LLM integrates the code, install lib, asks me to approve installation of libpg, libffmpeg,....
* test, if fails, feed the error back to LLM + prompt to fix it
* deployThe docs used to be good enough that there would be an example which did exactly what you needed more often than the llm gets it right today.
1) Do that inside their IDEs, which is less funny
2) Generate blog post about it instead of memes
from stackoverflow import quick_sort
https://github.com/drathier/stack-overflow-importIf not, then you’re not close to the cutting edge.
So the good old days before search engines were drowning with ads and dark patterns. My assumption is big LLMs will go in the same direction after market capture is complete and they need to start turning a profit. If we are lucky the open source models can keep up.
Arguably this solution is "better" because you don't even really need to understand that you have specific problems to have the agent solve them for you, but I fail to see the point of keeping these people employed in that case. If you haven't been able to solve your own workflow issues up until now I have zero trust in you being able to solve business problems.
I disagree with "always".
This is only the recent wave of brogrammers who care nothing about the quality of the tech and are only in this industry for the gold rush.
They aren't inherently technically minded, they just know how to schmooze their way around and convince decision makers to follow capricious trends over solid practices.
I've seen lots of people say AI can basically code a project for them. Maybe it can, but that seems to heavily depend on the field. Other than boilerplate code or very generic projects, it's a step above useless imo when it comes to gamedev. It's about as useful as a guy who read some documentation for an engine a couple years ago and kind of remembers it but not quite and makes lots of mistakes. The best it can do is point me in the general direction I need to go, but it'll hallucinate basic functions and mess up any sort of logic.