Don't be. There are some use cases that fit very well. For example, we plan to use GPT-4 for generating text that ends up being seen and read by our customers.

Don't be. There are some use cases that fit very well. For example, we plan to use GPT-4 for generating text that ends up being seen and read by our customers. (Can't disclose the details, as it's near to core of our business model.) We need a _lot_ of text, and its in style that is time-consuming to think and write by hand. However, all the generated data is checked for correctness by humans. I think that these tips are excellent for designing the generating process so that the end result is of as high quality as it could reasonably be expected to be. Edit: Oh, you mean coding work as for generating code for developers? Not in the sense of using it as a component of a data-generating/transforming system? In that case, I pretty much agree. Edit2: Oof, I just realized that I mistook this whole thread for another thread that was posted earlier on Hacker News. So I thought we were talking about engineering systems that has GPT-4 as a subsystem: https://platform.openai.com/docs/guides/gpt-best-practices https://platform.openai.com/docs/guides/gpt-best-practices