3 ms·

I tried getting it to output some Go with basically little knowledge of it myself. Let's just say software developers who actually know what they are doing are

• ksaj 4y ago
  It does parts of the code really well, I noticed. It's usually toward the end that it starts messing up, and especially the inputs are bad. The descriptive text is nearly always spot on, which makes the code errors a bit wonky. I have a feeling it's because sometimes documents show the code first before describing it, and some do it the other way around, so sometimes it is actually modelling the wrong thing. Plus: I asked it to make an obfuscated Lisp function to write Hello World, and it did a reasonable job. Then I said "Make a better one" and it made some seriously spaghetti code that still wrote Hello World properly, and explained why it was obfuscated. I wouldn't really call it obfuscate, but it was really messy and bizarre as I had hoped. Minus: I asked it to make a guitar tab for an Em7 chord. It showed an Em chord, although the description was exactly correct. So I said "The D string should be open to make it a 7th chord" and it showed it again with the D string not even voiced... which would still be an Em! (Yea, it can do guitar tabs, too!)