Gregory's Server@yac @ploum I'd rather let it write the code, then the tests. If it fucks up the tests, you would either miss the bugs, or have flaky tests being an extreme pain leading you to step 5. If you write decent tests, you would catch it on writing poor code. But TBH, it shouldn't write either of those, unless you treat it as a templating engine to write some very simple boilerplate for you.
|
2 comments
So far i've had good experience with chatgpt, even its bug fixing skills are pretty decent, but i haven't coded anything complex so far just basic api tools, userscript, wordpress themes and plugins. |
@tymwol @ploum Exactly, I use it as a templating engine on steroid. For instance in golang things like data := []struct {...}, the loop on data, the t.Errorf etc. The danger is to let it generate false tests complacently.