The bigger issue I see is that it also results in less experienced coders creating code that might work, but that they don't understand.
this post was submitted on 11 Jul 2025
19 points (88.0% liked)
Technology
7330 readers
71 users here now
News community around technology, social media platforms, information technology and governmental policy surrounding it.
What doesn't fit here?
The core of the story has to be technology focused.
- If article mentions "AI" in a sentence and then talks about business economics that doesn't make it tech news.
- Gaming is too many layers removed from technology. There are many dedicated communities that are a better fit for it.
- Transporation is too many layers removed from technology. EVs while use many cool technologies have many dedicated communities that are a better fit for it.
- Entertainment is too many layers removed from technology. While sometimes it can fit here, business or cultural aspects of it are a better fit for dedicated communities.
- Cybersecurity. While it heavily focuses on technology, most of the time it's too technical for most people who are not already invested in it. Should be posted in a dedicated communities unless it has broader connection to other tech areas.
Post guidelines
Title format
Post title should mirror the news source title. If you don't like the title of article, look for an alternative source instead of editorializing it.
URL format
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
[Opinion] prefix
Opinion (op-ed) articles must use [Opinion] prefix before the title. Opinion articles refer to articles that their publisher doesn't explictly endorse.
Country prefix
Country prefix can be added to the title with a separator (|, :, etc.) if the news is from a local publisher who doesn't clearly mention the country.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
founded 2 years ago
MODERATORS
Just like Stack Overflow then haha. It's usually either
"I copied this persons code exactly, why doesn't it work in my completely different codebase?"
or
"I copied this persons code exactly and it works in mine! I don't want to touch it in case I break it cause I don't get it"
haha
And in reality it doesn't work, or only works in very specific scenarios and thus fails with no one who wrote it around to understand why it might have failed.
If you already know what you're doing, AI generating code is redundant. If you don't know what you're doing, it might work for you, up to the point you're spending all your time debugging hallucinatory code.
If you already know what you’re doing, AI generating code is redundant.
Nah, it can be really useful for people who do know what they're doing as it can be used to generate the "charlie work" (IASIP reference if you don't know) things like unit tests and documentation and things like that pretty damn well.
Yup, yesterday I decided it was finally time to write unit/feature tests on a project that had gotten way to far aling with 0 tests. Just over an hour of babysitting Codex and now I've got 800 tests covering 16 models and 60+ endpoints (8000 lines of code) in the exact code style I wanted based on my AGENTS. Honestly, reading through the tests, I wouldn't know that I didn't write them!
Now, trying to use AI to solve a novel problem, or even a not so novel one with any logical complexity, and hours can easily be wasted trying to guide it, correct it's mistakes, and then eventually roll it all back and do it yourself because your smart enough, just being lazy! 😬
Sorry but a study of 16 developers isn't a big enough sample to get any meaningful data, especially given the massive range of skills and levels of development.
I'm a developer and I use AI - not much, but when I think it can help based on the suggestions that it gives me since it's integrated into visual studio. It doesn't slow me down, it speeds me up. It could slow you down if you rely on it to do everything, but in that case you're just a bad or lazy developer.
AI is a tool to use. Like with all tools, there are right ways and wrong ways and inefficient ways and all other ways to use them. You can't say that they slow people down as a whole just because they slow some people down.
It's a very small sample, so there may be biases. If the sample were larger and more generalized to programmers, there would be some support. For now, we only have more questions than answers in this study.