Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
6. Defend your opinion
This is a bit of a mix of rules 4 and 5 to help foster higher quality posts. You are expected to defend your unpopular opinion in the post body. We don't expect a whole manifesto (please, no manifestos), but you should at least provide some details as to why you hold the position you do.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
view the rest of the comments
I'm just amazed whenever I hear people say things like this as I can't get any model to spit out working code most of the time. And even when I can it's inconsistent and/or questionable quality code.
Is it because most of your work is small iterations on an existing code base? Are you only working with the most popular tools that are better supported by models?
Llama 4 sucked but with scaffolding could solve some common problems.
o1/3 was way better less gaslighting
Grok4 kicked it up a notch more like a pro coder
GPT5 and Claude able to solve real problems, implement simple features.
A lot depends on not just the codebase but on context, aka prompt engineering. Does the AI have access to relevant design docs? Interface definitions? Clearly written, well-formed bug? ... but not so much that context is overwhelming and it doesn't work well again
Okay, that's more or less what I was expecting. A lot of my work is on smaller problems with more open ended solutions and in those scenarios I find the AI only really helps with boiler plate stuff. Most of the packages I work with it only ever has a fleeting understanding or mixes up versioning so badly that it's really hard to trust it.