4 ms·
I can't help but feel that this type of workflow just took a huge step forward in https://copilot.github.com/ https://copilot.github.com/ too. A solid recogniti
by vizzier 5y ago
I can't help but feel that this type of workflow just took a huge step forward in https://copilot.github.com/ https://copilot.github.com/ too. A solid recognition that thats how most people code distilled into a product that automates that lookup by cross referencing information on the worlds largest code platform.
- cj 5y agoA step forward, but also potentially a step backwards compared to the “harder” workflow (the one without all answers on stack overflow). Just a small example, I imagine there are a lot of JS developers who know that they need to create a new function using “=>” or “.bind(this)” if they need access to “this” within the function… and if they don’t, things break, without really knowing why (even though they know the solution). TLDR: the best developers I’ve worked with go beyond “knowing the solution” to “knowing why the solution is the solution”. Understanding “why” something is the way it is becomes difficult when something like Copilot autocompletes the correct answer.