Live data from Hacker News

GitHub Copilot

copilot.github.com

391–400 of 1001 posts

Re: GitHub Copilot

#391
This looks pretty impressive and I'd like to play with it, but it's disappointing that you're forced to accept telemetry to enlist on the waitlist. I guess I'll wait for general availability.

Re: GitHub Copilot

#392

I've been using the alpha for the past 2 weeks, and I'm blown away. Copilot guesses the exact code I want to write about one in ten times, and the rest of the time it suggests something rather good, or completely off. But when it guesses right, it feels like it's reading my mind. It's really like pair programming, even though I'm coding alone. I have a better understanding of my own code, and I tend to give better na…

What's your estimate of the productivity boost expressed as a percentage? I.e. if it takes you 100 hours to complete a project without Copilot, how many hours will it be with Copilot?

Having been a TabNine user for a while I can say that it's less of a productivity boost and more of a quality of life win. It's hard to measure - not because it's small, but because it's lots of tiny wins, or wins at just the right moment. It makes me happy, and that's why I pay for it - the fact that it's probably also saving me some time is second to the fact that it saves me from annoying interrupts.

Re: GitHub Copilot

#393

Earlier quoted context omitted.

How many jobs have developers helped displace in business and industry? I don't think it's controversial that we become fair game for that same automation process we've been leading.

> How many jobs have developers helped displace in business and industry? How many? > I don't think it's controversial that we become fair game for that same automation process we've been leading. This is not correct. A human (developer) displacing another human (business person) is entirely different than a tool (AI bot) replacing a human (developer). Regardless, this is the Lump of Labour fallacy ( https://en.wikip…

> SWE is a complex field, way more than typing a few routines. In best case (technologically speaking) this will be an augmentation.

If there is a pathway to improving this AI assist efficiency say by restricting the language, methodology, UI paradigm and design principles, it will happen quick due to market incentives. The main reason SWE is complex is it's done manually in myriad subjectively preferred ways.

Re: GitHub Copilot

#395

Earlier quoted context omitted.

> and the rest of the time it suggests something rather good, or completely off In what, proportion roughly?

Hard to say, really. When writing React components, Jest tests and documentation, it's often not very far. I found it off when writing HTML markup (which is hard to describe with words).

Seems like it's best classed (for now) as an automated tool to generate and apply all the boilerplate snippets I would be creating & using manually, if I weren't too lazy, and/or too often switching between projects, to set all those up and remember how to use them (and that they exist).

Re: GitHub Copilot

#396

So if it was trained using "source code from publicly available sources, including code in public repositories on GitHub." was it also GPLv2? So everything generated also GPLv2?

IANAL, but my interpretation of the GitHub TOS section D4 would give give GitHub the right to parse your code and/or make copies regardless of what your license states. This is the same reason the GitHub search index isn’t GPL contaminated.

Re: GitHub Copilot

#397
I absolutely hate whenever I see patterns in my code. The first thing I think is "There has to be a way to automate this" This is not what I had in mind, but if it's as good as people seem to say, it might be a good step. I can't believe I am considering a Microsoft product after 15 years of avoiding them as much as I could.

Re: GitHub Copilot

#398
I don't think we need to start looking for new career paths yet. This example has a few bugs and it took me longer to track them down than it would have to write it myself:

  #!/bin/bash
  # List all python source files which are more than 1KB and contain the word "copilot".
  find . \
    -name "*.py" \
    -size +1000 \
    -exec grep -n copilot {}\;
"-exec grep -n copilot {}\;" needs to have a space before the semicolon otherwise find fails with "find: missing argument to '-exec'".

The "1000" in "-size +1000" has a unit of 512 byte blocks so it is looking for files that are greater than 512000 bytes, not 1KB. This would be very easy to miss in a code review and is one of those terrible bugs that causes the code to mostly work, but not quite.

https://linux.die.net/man/1/find

Re: GitHub Copilot

#399

Earlier quoted context omitted.

What's your estimate of the productivity boost expressed as a percentage? I.e. if it takes you 100 hours to complete a project without Copilot, how many hours will it be with Copilot?

I'm not sure I spend less time actually coding stuff (because I have to review the Copilot code). But the cost of the code I write is definitely reduced, because: - the review from my peers is faster (the code is more correct) - I come back less to the code (because I have thought about all the corner cases when checking the copilot code) - As I care more about naming & inline docs (it helps copilot), the code is act…

Check out how it helped me write a React component: https://twitter.com/francoisz/status/1409919670803742734

I think hit the Tab key more than I hit any other key ;)

Re: GitHub Copilot

#400

Earlier quoted context omitted.

Pack it all up, boys, programming's over. Hello, AI. Anyone want to hire me to teach your grandma how to use the internet?

Few days back, Sam Altman tweeted this "Prediction: AI will cause the price of work that can happen in front of a computer to decrease much faster than the price of work that happens in the physical world. This is the opposite of what most people (including me) expected, and will have strange effects" And I was like yeah I gotta start preparing for next decade.

https://twitter.com/sama/status/1404100794245214215
Post reply on HN