5 ms·
Then another hypothesis: you probably haven't found the right tools for it yet. I find myself writing biolerplate mostly around some obscure system framework ca
by mojuba 4y ago
Then another hypothesis: you probably haven't found the right tools for it yet. I find myself writing biolerplate mostly around some obscure system framework calls (iOS/macOS), but that's rather rare. But even OS API's and frameworks do evolve over time into requiring less boilerplate. Just take the evolution of CoreAudio, the modern Swift interface is so much better. So at the end of the day it's about the tools and interfaces: boilerplate is rarely absolutely necessary with the right tools.
- triknomeister 4y agoMaybe github copilot is the right tool.
- mojuba 4y agoI don't think so. A human-verified, tested and maintained code is obviously superior to a snippet blindly copied and mixed by a statistical system.
- mistercow 4y agoThat’s not how you use Copilot, any more than it’s how you’d use any other autocomplete tool. I don’t know why so many people seem to think that using Copilot is just closing your eyes, hitting tab fifty times, and then committing. You work on your code, Copilot makes a suggestion. You read that suggestion and verify that it’s close to what you were already going to do. If it is, you hit tab, then you tweak it. There’s nothing blind about this process.
- dx034 4y agoI'd rather use Copilot than including yet another library just to avoid writing one function.