this post was submitted on 28 Oct 2024
1536 points (98.8% liked)
Technology
59569 readers
3825 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Honestly, he's wrong though.
I know tons of full stack developers who use AI to GREATLY speed up their workflow. I've used AI image generators to put something I wanted into the concept stage before I paid an artist to do the work with the revisions I wanted that I couldn't get AI to produce properly.
And first and foremost, they're a great use in surfacing information that is discussed and available, but might be buried with no SEO behind it to surface it. They are terrible at deducing things themselves, because they can't 'think', or coming up with solutions that others haven't already - but so long as people are aware of those limitations, then they're a pretty good tool to have.
It's a reactionary opinion when people jump to the 'but they're stealing art!' -- isn't your brain also stealing art when it's inspired by others art? Artists don't just POOF, and have the capability to be artists. They learn slowly over time, using others as inspiration or as training to improve. That's all stable diffusors do - just a lot faster.
AI can give me a blueprint for my logic. Then I, as a developer, make the code run. Cuts my scripting time in half.
Rofl. As a developer of nearly 20 years, lol.
I used copilot until finally getting fed up last week and turning it off. It was a net negative to my productivity.
Sure, when you're doing repetitive operations that are mostly copy paste and changing names, it's pretty decent. It can save dozens of seconds, maybe even a minute or two. That's great and a welcome assist, even if I have to correct minor things around 50% of the time.
But when an error slips through and I end up spending 20 minutes tracking down the problem later, all that saved time vanishes.
And then the other times where my IDE is frozen because the plugin is stuck in some loop and eating every last resource and I spend the next 20 minutes cursing and killing processes, manually looking for recent updates that hadn't yet triggered update notifications, etc... well, now we're in the red, AND I'm pissed off.
So no, AI is not some huge boon to developer productivity. Maybe it's more useful to junior developers in the short term, but I have definitely dealt with more than a few problems that seem to derive from juniors taking AI answers and not understanding the details enough to catch the problems it introduced. And if juniors frequently rely on AI without gaining deep understanding, we're going to have worse and worse engineers as a result.