Earlier quoted context omitted.
It's called "conversational programming" and it was all the rage in the '60s or '70s. Maybe it's time for a resurgence?
SQL grew out of that trend btw :)
Show HN: ChatGDB – GPT-Powered GDB Assistant
51–57 of 57 posts
Re: Show HN: ChatGDB – GPT-Powered GDB Assistant
#52Re: Show HN: ChatGDB – GPT-Powered GDB Assistant
#53Earlier quoted context omitted.
Oh my god, if SQL is the “conversational” option what other design did they consider? Binary?
It's been 50+ years and still nobody has invented anything better that people actually use.
It’s not a universal solution, as it’s specific to my data architecture, but if I were to devote a month to it I’m fairly sure I’d make a big dent in a generalized solution. And I’m VERY sure somebody else already 90% done we’ll see it on GitHub soon!
Re: Show HN: ChatGDB – GPT-Powered GDB Assistant
#54Earlier quoted context omitted.
It's been 50+ years and still nobody has invented anything better that people actually use.
I mean, I’m using ChatGPT to render natural language down to executable SQL for a project right now. It’s not a universal solution, as it’s specific to my data architecture, but if I were to devote a month to it I’m fairly sure I’d make a big dent in a generalized solution. And I’m VERY sure somebody else already 90% done we’ll see it on GitHub soon!
Re: Show HN: ChatGDB – GPT-Powered GDB Assistant
#55Re: Show HN: ChatGDB – GPT-Powered GDB Assistant
#56Earlier quoted context omitted.
I’m sorry, but these arguments are terrible. I see them boiling down to this: “Use GPT to do this thing!” “But GPT is notorious for confidently getting things wrong” “That’s ok! Because you’ll know it’s wrong!” Maybe I’m a little sore right now because I literally just finished trying to have GPT write code for me and it gave me code with all kinds of syntax errors and mistakes. Yes, I know not to trust it because th…
It gets it wrong maybe as often as I do on my first shot, but it does it much faster -- MUCH MUCH faster if any of the tech involved is something I'm not familiar with. And no matter who writes the code, me or the machine, I still quickly read it right after it's written. Look, I've been doing this for 25 years, both as a career and continuously on the side for fun, and I am definitely an expert in a lot of things at…
I had one bad experience last week where I burned 20 minutes as ChatGPT gave me one invalid approach after another. Then I consulted the docs and learned that waht I wanted to do explicitly couldn't be done with that library. Tens steps forward and one step back. Totally worth it.