this post was submitted on 25 Jan 2024
317 points (97.3% liked)
Asklemmy
43950 readers
144 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
... Yes, it does in the tech sector. If you're wrong it doesn't work.
I've tried the tools out. You go from writing code for an hour and debugging for half an hour to writing code for 15 minutes and debugging for three hours.
Half the time you've ripped out literally every bit of code the AI wrote by the time you're done making it work.
Get better at the prompts you use. My entire team uses it daily, and it has made us probably 600% more effective. Learning to prompt AI is a valuable skill right now.
What's your metric that you improved 600%?
He's pulling it out of his ass. They might use github's code completion tools, but that's the closest thing to "ai coding" now. AI is notoriously stupid for continuity in its tasks. It's basically just parroting other things it's seen; it doesn't know if it fits together or not half of the time because "AI" doesn't understand.
Oh, I know how to prompt AI. Getting it to spit out workable code doesn't mean you don't have to review the code, or make sure it's integrated correctly.
You also have to make sure it's not generating blatantly braindead code, which makes the review and debugging cycle take longer.
I remain unconvinced that it's suitable for domains where there is a right and wrong answer, like engineering or law.
I've found more value in the systems that do a good job understanding the problem description and then returning references to documentation and prior art on techniques, as opposed to the actual code.
I don't need a virtual junior dev I need to hand hold, I actually have those and mine get better. I want a virtual "person who worked on something like this once and knows the links to the good articles".
Imagine training what's going to replace you lol
It's going to happen regardless of what you personally do. You might as well get some benefit from it while you can.
Nah, I have standards
You have standards, but the companies firing all these people don't.