Yeah I'm not convinced. As usual with most pro-ChatGPT posts I see, there is little to no actual useful information on how to use ChatGPT practically. When I read one of these articles or posts, I usually expect to see concrete prompts, their output, and how they can be used to speed up development. Instead all I see is generic vagueisms; "it helps me write unit tests", "it helps me code faster", or in the case of th…
As a weekend project I did a DSL for helping to interact with LLM's called Prompt (prlang.com), kinda like an declarative LangChain. The language is unimportant, what is important is that syntax highlighting is just one of those things that people expect a language to have now, and every editor wants to do it differently. Figuring out syntax highlighting is one of those super tedious things that makes writing a DSL very boring. ChatGPT4 is very good at translating from one language to another though, and so I could use it to help me write the vim syntax file (I don't know VimScript at all) and then translate it to other editors as necessary.
To get specific, it helped me write this vimscript file:
https://github.com/PromptProgrammingLanguage/prompt/blob/mas...
and then with almost no editing from me turned it into another syntax highlighting file (for hljs) that's used on the website.
https://github.com/PromptProgrammingLanguage/PromptProgrammi...
I don't know how long that would have taken me to figure out on my own, but diving into VimScripts docs, and then the HL.js docs, and fully reading and comprehending them would have been a total slog. Doing it with ChatGPT4, I could keep open the docs for Vim, ask it questions about how to do something, then quickly reference the docs to cross check if it was telling the truth, write, and then test the syntax in a very quick loop. Then the process of translating what I had to another library was incredibly fast, if I recall it misplaced one line while translating, which was thankfully obvious, and that was it. I didn't read the docs for hl.js at all.
ChatGPT is definitely better at some tasks than others. Anything that takes shallow knowledge of your specific code base, but broad knowledge of the wider languages ecosystem, is a good fit for it's use.
I could give a more impressive example of where it helped me tackle a super specific bug in my code that had to do with the wider Rust ecosystems libraries, it really blew me away with that one, but the above was easier to document. You wanted specific though, so there ya go :).
And of course ChatGPT4 is leagues ahead of ChatGPT3.5, so if you're not getting good results you really want to pay for the better model.