No post body was provided.
Ask HN: How often do you use GitHub Copilot at work? If not, why not?
1–6 of 6 posts
Re: Ask HN: How often do you use GitHub Copilot at work? If not, why not?
#2I copy past code blocks into chatgpt web interface but I remove any company specific stuff first. Like I'll even change variable names to "foo" vs. using the very MyCompanyNameVar in the example code.
Re: Ask HN: How often do you use GitHub Copilot at work? If not, why not?
#3I copy past code blocks into chatgpt web interface but I remove any company specific stuff first. Like I'll even change variable names to "foo" vs. using the very MyCompanyNameVar in the example code.
And that's faster than just typing the code yourself in the first place?
Re: Ask HN: How often do you use GitHub Copilot at work? If not, why not?
#4I don't use it, I refuse to. To me, the most important thing is to write code I understand in a way that will be understood by other humans. Copilot is here to make me produce code faster, that's a different goal.
I do spend a lot of time reading about the functions I call (to make sure I understand what they are meant to do and how to use them) and then, once my code works, to make it more readable. I believe it is a skill that requires practice. Copilot removes that, and therefore prevents me from getting better at what I believe is important.
Re: Ask HN: How often do you use GitHub Copilot at work? If not, why not?
#5I copy past code blocks into chatgpt web interface but I remove any company specific stuff first. Like I'll even change variable names to "foo" vs. using the very MyCompanyNameVar in the example code.
And that's faster than just typing the code yourself in the first place?
only if I'm stuck on something that I know gpt can handle. I use it like a Sous-chef.
Re: Ask HN: How often do you use GitHub Copilot at work? If not, why not?
#6It's an integral part of my workflow now. I love it. My common use cases are
- generating doc comments that are 99% correct
- completing boilerplate like error handling (f- you golang)
- write a "quick start" skeleton for unknown libraries and frameworks