The best I've managed is to say something to the effect of: Ok now write the end of the file starting from line "[the literal line before it cut off]". That be

The best I've managed is to say something to the effect of: Ok now write the end of the file starting from line "[the literal line before it cut off]". That being said, as with the "Try Again" function, there is no guarantee that it's what it would have written the first time around. Also it keeps breaking the blockquote formatting, I don't know why. Generally I've found it's incapable of writing large novel systems correctly if you are trying to solve a specific problem, so I found large outputs generally useless. What I do is that I cut the problem into sub-problems and have him solve them one by one. Sometimes I'll show him an example of inputs, tell him what I want the function to do and ask him to generate the output. Then I'll tell him "Generate a function to go from this input to this output" and he has a good track record of producing small and correct pieces of code. Then the context of this previous task helps him solve the subsequent tasks more easily. Another pitfall with large outputs is that he seems to give as much weight to his answers as to yours. So if he gives a large incorrect output it will be more likely to corrupt the logic on which it will base subsequent answers. Often I'll tell it to just "Answer with O.K" or just end with "Do you understand?" so it doesn't go on a long logic-corrupting answer. The problem is that eventually he starts to answer with specifications of his own and asks me if I understand and to only respond with O.K ...