23 ms·
For now, I mostly use AI as a "faster typist". If it wants to complete what I wanted to type anyway, or something extremely similar, I just press tab, otherwis
by miki123211 2y ago
For now, I mostly use AI as a "faster typist".
If it wants to complete what I wanted to type anyway, or something extremely similar, I just press tab, otherwise I type my own code.
I'd say about 70% of individual lines are obvious enough if you have the surrounding context that this works pretty well in practice. This number is somewhat lower in normal code and higher in unit tests.
Another use case is writing one-off scripts that aren't connected to any codebase in particular. If you're doing a lot of work with data, this comes in very handy.
Something like "here's the header of a CSV file", pass each row through model x, only pass these three fields, the model will give you annotations, put these back in the csv and save, show progress, save every n rows in case of crashes, when the output file exists, skip already processed rows."
I'm not (yet) convinced by AI writing entire features, I tried that a few times and it was very inconsistent with the surrounding codebase. Managing which parts of the codebase to put in its context is definitely an art though.
It's worth keeping in mind that this is the worst AI we'll ever have, so this will probably get better soon.
- zeroonetwothree 2y agoOne off scripts do work very well.
- blitzar 2y agoReminds me of how I use the satnav when driving. I don't close my eyes and do whatever it tells me to do. If I think I know better I don't "turn right at the next set of lights" I just drive on as I would have before GPS and eventually realise that I went the wrong way or the satnav realises there was a perfectly valid 2nd/3rd/4th path to get to where I wanted to go.
- DeathArrow 2y agoYes, for simple boring tasks like converting a JSON to C# classes, it does wonders. For everything clever it kind of needs baby sitting which doesn't make it faster than writing the code myself. Even for the glorified use case of writing unit tests it sucks unless the code is very simple with few dependencies.