|
|
|
|
|
by freehorse
370 days ago
|
|
I have caught my self a few times do this repeated prompting "fix the bugs" out of mere laziness to go down on the code and actually read it. Actually fixing the bugs oneself requires a certain kind of effort and focus that you are not into while "vibe coding", and this increases the less familiar you are with the language/code. If I do this on anything serious, as in anything I will need to maintain or reuse, I end up losing more time than gaining. If it is something I am gonna throw away anyway, I do not care as much. I don't know what the context in this example is. I would say that the main reason to not do this for any actual code you work on is that you will need to go into the code and fix bugs anyway when the LLM will, at some point inevitably, start consistently failing certain tasks. All the time you (think you had) saved by avoiding actually delving into the code will come back as technical debt then. |
|