|
|
|
|
|
|
by rybar
1151 days ago
|
|
|
Nothing it produces is that many lines. How is that not debuggable? If you can’t, you’re having it do things you don’t even understand and blindly implementing and seems like a user issue. Additionally, take the code and ask it to write tests and validation scripts with your expectations. |
|
|
Today's programming is not SICP in scheme, it is more plumbing between very large bodies of code. Using GPT is a great way to short cut needing to learn lots of details about code bases you only need for one specific feature. Recently though, by integrating two pieces of code I do know a lot about, I lost a lot of confidence in GPT coding.
For example, I asked it to implement a small script in emacs that would loop through org text files in emacs, and run some commands based on keybindings. That's it.
It messed up the usage of recursive-edit (which is a complicated feature itself), it produced many bugs in how Org utilizes indirect buffers, it sends windows around instead of buffers in the variables, and it wrote lots of contradictory code.
I understand how all these features work, and I went through and started fixing all the bugs. I would tell it about each bug, but it was producing so many subtle bugs with org-mode, inventing functions that didn't exist and it couldn't define... I gave up and just re-implemented it myself.
So no, I do not understand 100% of all code I refer to when I write code, that's why APIs actually exist.