26
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 May 2025
26 points (81.0% liked)
technology
23800 readers
155 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
In my experience, LLMs can often pump out perfectly fine starting code for very basic problems. If you're coding up some tiny blog it'll probably be good enough that someone with some coding experience can unfuck the places where it screwed up.
That's not what professional software engineering
is about though. You want a codebase built in a coherent, consistent, repeatable way that can be independently worked on by dozens of people often at the same time, and LLMs cannot do that in any real capacity. It might serve as a decent tool for spinning up quick proof-of-concepts (I've poked it to figure out a new framework before, mostly due to terrible documentation making it difficult to figure out how to use specific features) but none of it was production-worthy and never would be.
Furthermore, if you're using it to figure out entire languages/frameworks for you, you're quickly finding yourself in a position where you don't see where it's fucking up, which is going to hit you down the line when you're playing whack-a-mole with a bug or severe performance issue in a giant codebase.
I still think you are talking about an architect and principal engineering level - which AI is not going to replace for a long while. It’s a productivity multiplier and maybe will replace junior developers at most. But that still seems another year or so away if not longer
I'm not advocating for using it to attempt and write a new feature end to end. Use it to help with your code function by function
It's great for syntax, not good for the where