It's mentioned towards the end of the blogpost, but I think the real blessing in disguise might be the ability to identify similar code from elsewhere on Github and linking to it. Too many libraries have you wading through pages of documentation in search of a single usage example.
Some other ideas:
- Look for libraries with similar code and suggest them
- Deobfuscating minified variable names? Or just suggesting better ones for your source code
- Speculatively running things. If the model predicts importing a certain library, start indexing it before I even type it
- Estimate how long it thinks a block of code will take to write, based on the predicted code + past usage patterns (like the kindle reading progress estimate)
Just spitballing but all of these things feel more helpful and pair programming-y than trying to fabricate code out of the blue.
I would be happy of my IDE could throw me to the relevant topic on cppreference.com from a type or variable. Or still show the function signature after I started typing the function arguments.
Some other ideas:
- Look for libraries with similar code and suggest them
- Deobfuscating minified variable names? Or just suggesting better ones for your source code
- Speculatively running things. If the model predicts importing a certain library, start indexing it before I even type it
- Estimate how long it thinks a block of code will take to write, based on the predicted code + past usage patterns (like the kindle reading progress estimate)
Just spitballing but all of these things feel more helpful and pair programming-y than trying to fabricate code out of the blue.