[{"_1":2,"_58":-5,"_59":-5},"loaderData",{"_3":4,"_7":8},"root",{"_5":6},"nowPlaying",["P",6],"routes/posts/route",{"_9":10},"posts",[11,36,48],{"_12":13,"_14":15,"_16":17,"_18":19,"_22":23,"_24":25,"_32":35},"title","GitHub Copilot is... Good.","summary","This is my experience using GitHub Copilot.","publishedAt","2023-05-11","tags",[20,21],"development","ai","content","I was recently asked about my experience with [GitHub Copilot](https://github.com/features/copilot) (just Copilot from now on) privately, and I decided to turn it into a blog post instead.\n\n**Copilot has completely changed the way I work as a developer**. It is capable of writing boilerplate code, suggesting variable names, and even generating entire functions. My experience with Copilot has been incredibly positive, and I can't imagine working without it. In this post, I'd like to share some insights that may not be immediately obvious when using it.\n\n## Boilerplate-y code\n\nCopilot is pretty good at generating boilerplate-y code, such as tests. This is good news for developers since writing tests can be a tedious task, especially after modifying 48 files to implement a feature. Copilot is not perfect, as I'll explain in the third point, but anything that can help us write mundane code is _always_ welcome.\n\n## Understanding your intention\n\nI'm used to writing long, descriptive variable names. This works extremely well with Copilot since the suggestions improve with more context. When I'm writing something and the suggestion I'm getting doesn't solve the problem, a small comment like `// only execute this method if the foo variable is not null` usually does the trick. The more context we give Copilot, the better the suggestions.\n\nAnother underrated aspect of Copilot is the instant gratification you get when you and Copilot agree on something. Sometimes I found myself stopping mid-sentence and waiting for Copilot to suggest the next piece of code. It makes writing complex code a bit more playful.\n\n## Is not perfect\n\nCopilot may generate slight \"off-by-one\" type of bugs if you're not careful, but to be fair this can happen even without it. Many wise tech people advise against executing code snippets you don't understand, and the same applies to Copilot. We’re not strangers to that practice though, _cough_ Stack Overflow _cough_. In fact, I think this marks the end of Stack Overflow as we know it.\n\nIn conclusion, I recommend any developer to try Copilot. It provides a productivity boost by suggesting code in a timely manner and reducing the burden of writing boilerplate-y code.\n\nWe need to keep in mind that Copilot is classified as a Generative AI, so sometimes it may try guess its way out of a problem... But don't we all do it? Don't we all do things like “let's add a space to see if this fixes the issue” or “lets add an `as any` here so the typescript compiler stops yelling at me”? Copilot sometimes is not different but it's an amazing tool that is only getting better.","_meta",{"_26":27,"_28":27,"_29":30,"_31":32,"_33":34},"filePath","copilot-is-good.md","fileName","directory",".","extension","md","path","copilot-is-good","

I was recently asked about my experience with GitHub Copilot (just Copilot from now on) privately, and I decided to turn it into a blog post instead.

Copilot has completely changed the way I work as a developer. It is capable of writing boilerplate code, suggesting variable names, and even generating entire functions. My experience with Copilot has been incredibly positive, and I can't imagine working without it. In this post, I'd like to share some insights that may not be immediately obvious when using it.

Boilerplate-y code

Copilot is pretty good at generating boilerplate-y code, such as tests. This is good news for developers since writing tests can be a tedious task, especially after modifying 48 files to implement a feature. Copilot is not perfect, as I'll explain in the third point, but anything that can help us write mundane code is always welcome.

Understanding your intention

I'm used to writing long, descriptive variable names. This works extremely well with Copilot since the suggestions improve with more context. When I'm writing something and the suggestion I'm getting doesn't solve the problem, a small comment like // only execute this method if the foo variable is not null usually does the trick. The more context we give Copilot, the better the suggestions.

Another underrated aspect of Copilot is the instant gratification you get when you and Copilot agree on something. Sometimes I found myself stopping mid-sentence and waiting for Copilot to suggest the next piece of code. It makes writing complex code a bit more playful.

Is not perfect

Copilot may generate slight \"off-by-one\" type of bugs if you're not careful, but to be fair this can happen even without it. Many wise tech people advise against executing code snippets you don't understand, and the same applies to Copilot. We’re not strangers to that practice though, cough Stack Overflow cough. In fact, I think this marks the end of Stack Overflow as we know it.

In conclusion, I recommend any developer to try Copilot. It provides a productivity boost by suggesting code in a timely manner and reducing the burden of writing boilerplate-y code.

We need to keep in mind that Copilot is classified as a Generative AI, so sometimes it may try guess its way out of a problem... But don't we all do it? Don't we all do things like “let's add a space to see if this fixes the issue” or “lets add an as any here so the typescript compiler stops yelling at me”? Copilot sometimes is not different but it's an amazing tool that is only getting better.

",{"_12":37,"_14":38,"_16":39,"_40":39,"_18":41,"_22":43,"_24":44,"_32":47},"hung up process? no problem","why i didn't know about this trick","2022-07-11","updatedAt",[42],"personal","why didn't I know about thissss\n\n```bash\nlsof -ti:3030 | xargs kill -9\n```",{"_26":45,"_28":45,"_29":30,"_31":32,"_33":46},"kill-process.md","kill-process","

why didn't I know about thissss

lsof -ti:3030 | xargs kill -9\n

",{"_12":49,"_14":50,"_16":51,"_40":51,"_18":52,"_22":53,"_24":54,"_32":57},"if not now, when?","This is literally my first rodeo. Welcome to my space.","2022-07-10",[42],"I'm a sharer. I'm always sending tweets, reddit posts or whatever rant I have that day to my friends. I mean, what's the joy of finding something cool on the internet and not having anyone to enjoy it with?\n\nI have wanted to start a blog to share my thoughts with a broader audience for a long time now, but… maintaining a healthy blog is just too much work. I mean, I enjoy sharing interesting bits I find but when I find the least friction I can become a full time procrastinator (I guess that’s my super power?)\n\n> Writing content is easy. Writing **good** content? That’s another story.\n>\n> — Somebody, probably\n\nThat’s the reason this is not a “blog” per se. My intention with this space is... mumbling about anything, really. Somewhere safe where I can share my thoughts with my friends and family without having to copy/paste messages all over telegram/whatsapp/twitter. Somewhere where I can write without thinking too much or feeling the pressure of having to write a “formal” blog post (what is such thing anyways?)\n\n> Twitter is too ephemeral. blogs are too permanent. I want something in-between.\n>\n> — [@jlongster](https://twitter.com/jlongster)\n\n[Brian Lovin](https://twitter.com/brian_lovin) wrote a great piece about [why you’re not updating your personal site](https://brianlovin.com/writing/reasons-you-arent-updating-your-personal-site) (his blog is amazing, you should read it). In summary, he’s using an array of tools to reduce all of the points of friction he encounters when writing content. In my case having to think and write in a foreign language is one of those eventually discourages me to write content. English is considered the universal language when working in tech, I wonder how many non-english speaking folks want to start blogging but are discouraged because how much harder is to write english blog posts for them.\n\nAnyways, if I want this to become a new habit I want to I have to make it as easy as possible for me. Less is better. Prefer progress over perfection. I’ll prioritize sharing “thoughts” frequently over sharing long, formal, well research “articles” every once in a while. If you’re along for the ride, you have been warned.\n\nWish me luck.",{"_26":55,"_28":55,"_29":30,"_31":32,"_33":56},"if-not-now-when.md","if-not-now-when","

I'm a sharer. I'm always sending tweets, reddit posts or whatever rant I have that day to my friends. I mean, what's the joy of finding something cool on the internet and not having anyone to enjoy it with?

I have wanted to start a blog to share my thoughts with a broader audience for a long time now, but… maintaining a healthy blog is just too much work. I mean, I enjoy sharing interesting bits I find but when I find the least friction I can become a full time procrastinator (I guess that’s my super power?)

\n
Writing content is easy. Writing good content? That’s another story.
\n
— Somebody, probably
\n

That’s the reason this is not a “blog” per se. My intention with this space is... mumbling about anything, really. Somewhere safe where I can share my thoughts with my friends and family without having to copy/paste messages all over telegram/whatsapp/twitter. Somewhere where I can write without thinking too much or feeling the pressure of having to write a “formal” blog post (what is such thing anyways?)

\n
Twitter is too ephemeral. blogs are too permanent. I want something in-between.
\n
— @jlongster
\n

Brian Lovin wrote a great piece about why you’re not updating your personal site (his blog is amazing, you should read it). In summary, he’s using an array of tools to reduce all of the points of friction he encounters when writing content. In my case having to think and write in a foreign language is one of those eventually discourages me to write content. English is considered the universal language when working in tech, I wonder how many non-english speaking folks want to start blogging but are discouraged because how much harder is to write english blog posts for them.

Anyways, if I want this to become a new habit I want to I have to make it as easy as possible for me. Less is better. Prefer progress over perfection. I’ll prioritize sharing “thoughts” frequently over sharing long, formal, well research “articles” every once in a while. If you’re along for the ride, you have been warned.

Wish me luck.

","actionData","errors"]