ChatGPT: It was early on in my career as a software developer, and I was working on a web …

The C++ experts here will be able to confirm, but if my memory serves, I think the story about virtual destructors doesn't make sense: > Specifically, the class had a virtual destructor, but the derived class failed to declare its own destructor as virtual. The derived class doesn't have to declare its destructor as virtual. What matters is that the base class does so. > This led to undefined behavior when deleting objects of the derived class, which in turn caused the program to crash. No; the undefined-behavior case arises if the base class destructor is not declared as virtual, and you then try to delete a derived class via a pointer-to-base.[1] So this is a nice example of ChatGPT producing something that looks plausible, yet on examination, betrays the fact that it has no actual "understanding" of the topic. [1] https://en.cppreference.com/w/cpp/language/destructor

I know it's well-known and because it's a statistical model, but I like how ChatGPT basically fills in a Mad Lib with these replies. > ChatGPT: I was working on a [project] that [description]. > One day, a user reported a strange issue where [issue description]. At first, I assumed it was a problem with the [feature], but as i dug deeper, I realized that the issue was actually caused by a very strange bug. > It turned out that [bug cause]. This led to [problem]. > To fix the bug, I had to [solution]. It was definitely one of the weirdest bugs I've ever encountered, and it taught me the importance of [lesson]. Third example deviates from this template a bit but still has the key components ("strange issue", "To fix the issue, I had to" "It was definitely one of the weirdest bugs I've ever encountered, and it taught me the importance of")