Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I was super nervous AI would replace me, a programmer. So i spent a long time learning, hosting, running, and coding with models, and man did I learn a lot, and you're spot on. They're really cool, but practical applications vs standard ML models are fairly limited. Even the investors are learning that right now, that everything was pure hype and now we're finding out what companies are actually using AI well.
There are a fair number of "developers" that I think will be displaced.
There was a guy on my team from an offshoring site. He was utterly incompetent and never learned. He produced garbage code that didn't work. However he managed to stay in for about 4 years, and even then he left on his own terms. He managed to go 4 years and a grand total of 12 lines of code from him made it into any codebase.
Dealing with an LLM was awfully familiar. It reminded me of the constant frustration of management forcing me to try to work with him to make him productive. Excrpt the LLM was at least quick in producing output, and unable to go to management and blame everyone else for their shortcomings.
He's an extreme case, but in large development organizations, there's a fair number of mostly useless developers that I think LLM can rationalize away to a management team that otherwise thinks "more people is better and offshoring is good so they most be good developers".
Also, enhanced code completion where a blatantly obvious input is made less tedious to input.
I'll give you that one. LLMs in their current state help me write code that otherwise I would be putting off or asking someone else to do. Not because it's hard but because I've done it 1000 times and I find it tedious, and I'd expect an entrylevel/jr to take it with stride. Even right now I'm using it to write some python code that otherwise I just don't want to write. So, I guess it's time to uplevel engineers. The bar has been raised, and not for the first time in our careers.