this post was submitted on 15 Aug 2023
87 points (88.5% liked)
Technology
59392 readers
3091 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
I've experimented a bit with chatGPT, asking it to create some fairly simple code snippets to interact with a new API I was messing with, and it straight up confabulated methods for the API based on extant methods from similar APIs. It was all very convincing, but if there's no way of knowing that it's just making things up, it's literally worse than useless.
ChatGPT has been helpful in being an interactive rubber duck. I used it to help myself breakdown the technical problems that I need to solve and it helps to cut down time taken to complete a difficult ticket that usually take a couple of days of work to a couple of hours.
"just good enough to be dangerous"
I’ve had similar experiences with it telling me to call functions of third party libs that don’t exists. When you tell it “That function X does not exist” it says “I’m sorry, your right fucking X doesn’t not exist on library A. here is another example using function Y” then function Y doesn’t exist either.
I have found it useful in a limited scope, but I have found co-pilot to be much more of a daily time saver.
So? You should be testing the code it generates, a few lines of code at a time, and writing unit tests where appropriate.
By doing that, you'll quickly identify anything that it does wrong, and you can just tell it "this line didn't work". Normally you don't need to tell it how to fix it, but you can do that too.
Except that in code, you can write unit tests and have checks that it absolutely has to get precisely correct.
If you have to write the code and tests yourself... That's just normal coding then
You don't, you get it to write both the code and the tests. And you read both of them yourself. And you run them in a debugger to verify they do what you expect.
Yeah, that's half the work of "normal coding" but it's also half the work. Which is a pretty awesome boost to productivity.
But where it really boosts your productivity is with APIs that you aren't very familiar with. ChatGPT is a hell of a lot better than Google for simple "what API can I use for X" questions.
You might have to rewrite all of it. The code and the tests.
Hell even the structure/outline it took might not be correct.
Yeah but I don't. That's the whole damn point.
I really suggest you guys try it.
It's really really bad very often.