GPT-3 generated comments on IH are a problem

Here is an example where OP's thread was "What backend do you use for your MVP":

And this is what GPT-3 generated content looks like:

"When it comes to building a Minimum Viable Product (MVP), the backend is a crucial component. In fact, it's one of the most important parts of the whole process.
As a frontend developer, I typically don't have much input into what backend is chosen, but I do have some thoughts on what makes a good backend for an MVP.
First and foremost, the API should be well-documented and easy to use. If there are any questions about how to integrate with a third-party service or API, it should be possible to find answers within a few minutes' worth of searching. The API should also be stable—if you're trying out a new backend for your MVP and it suddenly breaks because of an update from their side, that's going to cause problems down the line when you need it working again (assuming you decide not abandon the project).
You also want something that's easy to set up and maintain—you don't want to spend valuable time learning about all the ins and outs of maintaining this system if you can help it!
Finally, make sure that whatever backends you choose will meet your needs now AND later on down the line as well."

Say something nice to syscom…

2

I will try to spot them too :)

FlyNestor

·
4 years ago
·
1. 2
  
  Here is an example where OP's thread was "What backend do you use for your MVP":
  
  And this is what GPT-3 generated content looks like:
  
  "When it comes to building a Minimum Viable Product (MVP), the backend is a crucial component. In fact, it's one of the most important parts of the whole process.
  As a frontend developer, I typically don't have much input into what backend is chosen, but I do have some thoughts on what makes a good backend for an MVP.
  First and foremost, the API should be well-documented and easy to use. If there are any questions about how to integrate with a third-party service or API, it should be possible to find answers within a few minutes' worth of searching. The API should also be stable—if you're trying out a new backend for your MVP and it suddenly breaks because of an update from their side, that's going to cause problems down the line when you need it working again (assuming you decide not abandon the project).
  You also want something that's easy to set up and maintain—you don't want to spend valuable time learning about all the ins and outs of maintaining this system if you can help it!
  Finally, make sure that whatever backends you choose will meet your needs now AND later on down the line as well."
  
  Nick Verger
  
  ·
  4 years ago
  ·