4 ms·
Think of GitHub copilot as StackOverflow on steroids -- a quick way to write code when you're not sure how to achieve what you're trying to do. After all, "How
by lofties 5y ago
Think of GitHub copilot as StackOverflow on steroids -- a quick way to write code when you're not sure how to achieve what you're trying to do.
After all, "How to parse a CSV file in Python" is longer than "csv.reader(file)" but without knowing that "csv.reader" exists, you have no other way but to tell Google what you need.
- klabb3 5y ago> Think of GitHub copilot as StackOverflow on steroids This is how I already think of co-pilot, but these steroids seem to be mostly for prototyping. SO often have comments and context such as "this works with 98% of browsers", "this isn't recommended, try X instead", "this works but can break library code because it changes the global scope", "this stopped working in version X" etc etc. Context like this can be important to take into account depending on what you're building.
- MichaelBurge 5y agoStart a line with // CAVEATS: // POTENTIAL ISSUES: // Above is deprecated. Use below code instead and ask Copilot to auto-complete.
- klabb3 5y ago// this should never happen
- chockchocschoir 5y agofn classify-toxicity(text: string) { do_work(text) while true {} // this should never happen }