4 ms·
I haven't tried copilot yet. I have tried Claude 3.5, which is unexpectedly brilliant. I use it very regularly. But almost entirely useful for writing new code,
by rerdavies 2y ago
I haven't tried copilot yet. I have tried Claude 3.5, which is unexpectedly brilliant. I use it very regularly. But almost entirely useful for writing new code, not fixing old code.
I take your point with respect to understanding large existing codebases. AIs don't yet seem to deal well with strategic large-context thinking. But things are changing at such a furious pace, so that may change sometime much sooner than either of us expect. But you are right. At the present moment in time, AIs are not particularly good at that.
But overall, I am much more optimistic than you are. I think AIs will save us time, so that we can spend more time on issues of overall structure that make "spending months to understand a codebase" a thing of the very distant past. I have certainly worked on codebases that require "months to understand". But I would (perhaps naively) like to think that's a symptom of a disease that codebases shouldn't have, and that modern codebases usually don't have anymore (but sometimes do).
- phonkytown 2y agoCo-Pilot is, surprisingly, a great competitor [in certain situations]. Imo
- rerdavies 2y agoUpdate: I did my first "find the bug" today. I fed it a thousand lines of code, described my bug, and asked Claude to fix it. It did. (putting a dropdown menu inside a button means that clicks in the menu are propagated to the button too. click on the menu item, the menu closes, but then the button gets the event as it propagates (because the menu is structurally inside the button, and re-opens the menu again. Hence why my menu wouldn't close). Wow.
- QuantumGood 2y agoAnecdata: Claude 3.5 sometimes nails on the first try something that I can't GPT4 (any version) to ever complete without errors. Most recently, an AHK 2.0 script concatenating some strings.