|
|
|
|
|
by seba_dos1
1159 days ago
|
|
The thing is - how often do you end up needing such snippets? How much more useful is receiving it from ChatGPT than looking it up in a search engine? Continuing with the theme of your example, at least in my experience most of the programmer's time is spent on figuring out which endpoint do you need, why and when does that endpoint sometimes return something you don't expect and how to deal with that happening. Writing JSON serializing in a language your head got rusty with may be faster with ChatGPT than it would be otherwise, but the overall benefit seems negligible, especially when you need to watch out at every step for convincingly-looking nonsense. |
|
I am now experimenting with ChatGPT parsing our own historical documentation, such as API references, and even basic markdown notes. When it comes to API endpoints I can get 80-90% accurate boilerplate. Admittedly, ChatGPT cannot provide assistance in understanding unexpected behavior, unless perhaps it is due to a misunderstanding of the language. And, though it is true that resolving API endpoint issues can be a time-consuming task, this does not negate the time savings that ChatGPT can provide in other situations.
I would urge you to try it out in your own workflow before calling shots on if the usefulness is negligible or not. And even then, I'd say not every tool is for everyone. This thing is really helping me out and I'm seeing long-term viability for it in my workflows.