2 ms·
I find that it depends very heavily on what you're up to. When I ask it to write nix code it'll just flat out forget how the syntax works half way though. But
by __MatrixMan__ 2y ago
I find that it depends very heavily on what you're up to. When I ask it to write nix code it'll just flat out forget how the syntax works half way though. But if I want it to troubleshoot an emacs config or wield matplotlib it's downright wizardly, often including the kind of thing that does indicate an intimacy with the details. I get distracted because I'm then asking it:
> I un-did your change which made no sense to me and now everything is broken, why is what you did necessary?
I think we just have to ask ourselves what we want it to be good at, and then be diligent about generating decades worth of high quality training material in that domain. At some point, it'll start getting the details right.
- esafak 2y agoThat doesn't work in the tech industry, because almost nothing is decades old, for obvious reasons.
- __MatrixMan__ 2y agoWhat languages/toolkits are you working with that are less than 10 years old? Anyhow, it seems to me like it is working. It's just working better for the really old stuff because: - there has been more time for training data to accumulate - some of it predates the trend of monetizing data, so there was less hoarding and more sharing It may be that the hard slow way is the only way to get good results. If the modern trends re: products don't have the longevity/community to benefit from it, maybe we should fix that.