> I think to get good value out of it you really have to get a sense for what it's good for and what it's not. > I don't have it write my day to day code, beca

> I think to get good value out of it you really have to get a sense for what it's good for and what it's not. > I don't have it write my day to day code, because that's complicated and usually niche enough that it's not likely to give a good result. Yep totally agree. I don't think you should just treat it as a black box - throw in literally any prompt you can think of and then use the response verbatim, without even reading it, and expect to have success. You need to exercise some judgement and be a bit discerning. And think about what areas of your work are most unique to your own skills and experience, and what are the bits of work around the fringes that don't need to be done by you - and are not really part of your core "craft", and, are likely to be well suited to the capabilities of something like GPT-4. And like every other tool, using it effectively is a skill and requires perserverance, practice, and adjusting your approach as you go. Which means the user can get better at getting value of out an LLM over time. It's not a static or all or nothing thing.