“Chat GPT went down and 25% of my team could not work.”

Re:“Chat GPT went down and 25% of my team could not work.” by simonw on Thursday February 23, 2023 @08:46AM (#34910494)

I use ChatGPT all the time to generate quick example code, purely as a faster version of "Google for this API, then this other one, then figure out how to glue that together in a script".

I also use it for things like constructing jq recipes, or zsh for loops (I still can't remember how to do those without looking them up).

Recent jq example: https://fedi.simonwillison.net/@simon/109882602515468465 - see also https://til.simonwillison.net/gpt3/jq

Here's an example where I used it as a search engine and it taught me about an entirely new (to me) tool: https://til.simonwillison.net/macos/sips

[ Parent | on HN ]

Re:“Chat GPT went down and 25% of my team could not work.” by 28304283409234 on Thursday February 23, 2023 @12:19PM (#34913437)

Yup. I used to read manpages and skip straight to the examples. Don't see much difference other than less frustration.

[ Parent | on HN ]

Re:“Chat GPT went down and 25% of my team could not work.” by skugeTO on Thursday February 23, 2023 @05:04PM (#34917230)

That’s it! Chat GPT excels at reading documentation and writing prototypes of code that uses libraries, APIs, FFIs or all of them together!

It saves so much time not to have to figure out how to instantiate that random call that wasn’t mentioned in the documentation and whose code is obscured by objectionable engineering.

However I don’t think any line of chatGPTs code has yet made it to my codebase unchanged

[ Parent | on HN ]