After getting licenses to cover every engineer, some at the cryptocurrency exchange warned Armstrong that adoption would be slow, predicting it would take months to get even half the engineers using AI.
Yeah it’s not a miracle, but it’s probably useful. I find the most common scenario for when the LLM wasted my time was when I was asking it how to do something which can’t be done. Like I would ask it how to use library X to do operation Y, where in truth library X doesn’t support operation Y. Rather than responding that I should find a different library, it would just make up some functions or parameters. When it works well, it’s faster than hunting down the docs or finding examples/tutorials.
I tried using it as reference, but it lied more than the datasheets.
Yeah it’s not a miracle, but it’s probably useful. I find the most common scenario for when the LLM wasted my time was when I was asking it how to do something which can’t be done. Like I would ask it how to use library X to do operation Y, where in truth library X doesn’t support operation Y. Rather than responding that I should find a different library, it would just make up some functions or parameters. When it works well, it’s faster than hunting down the docs or finding examples/tutorials.
Or you could just bookmark the documentation
If you’re a senior coder who can’t search the documentation fast enough, I don’t consider you to be a senior.
There are other things that are very important, but this is one of the most basic cornerstones.
Level 1: read the documentation
Level 2: figure out which parts are lies
Level 3: ???
😱