all 18 comments

sorted by: hot top controversial new old
[–] 17 points 1 year ago (3 children)

That exains a lot...

I do use AI to assist my programming, but I always take what it suggests as likely highly flawed. It frequently sends me in the right direction but almost never is fully correct. I read the answers carefully, throw away answers frequently, and never use a solution without modifying it in some way.

Also, it is terrible at handling more complex tasks. I just use it to help me construct small building blocks while I design and build the larger code.

If 30% of my code was written by AI it would be utter trash.

  • source
  • hideshow 3 child comments
  • [–] 8 points 1 year ago* (1 child)

    AI is like a utils library: it can do well known boilerplate like sorting very well, but it’s not likely to actually write your code for you

    AI is like fill down in spreadsheets: it can repeat a sequence with slight, obvious modifications but it’s not going to invent the data for you

    AI is like static analysis for tests: it can roughly write test outlines, but they might not actually tell you anything about the state of the code under test

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 1 year ago

    And presumably must developers at Microsoft take a similar approach (all the 'this explains everything' comments notwithstanding, so it's ridiculous that they're even tracking this as a metric. If 30% is AI generated, but the devs had to throw away 90% of it, that doesn't mean you could get rid of the developer, as they did a huge amount of work just checking the AI and potentially fixing stuff after it.

    This is a metric that is misleading and will cause management to make the wrong decisions.

  • source
  • parent
  • [–] 14 points 1 year ago

    we can tell

  • source
  • [–] 12 points 1 year ago (3 children)

    That’s like, not a good thing dude

  • source
  • hideshow 3 child comments
  • [+] 2 points 1 year ago (2 children)
  • [–] 9 points 1 year ago* (last edited 1 year ago) (1 child)

    They're saying it's not a good thing because code produced by AI is riddled with problems, today.

    Edit: AI code could explain the unstable experience in some recent updates to Microsoft Teams...

  • source
  • parent
  • hideshow 1 child comment
  • [–] 10 points 1 year ago

    I mean, autocorrect has written about 50 percent of this comment, but that doesn't mean my phone is writing it for me as much as it accelerates what I wanted to type in the first place.

    Maybe that's how they got to a 30% estimate, cause ain't no other way that would have worked

  • source
  • [–] 9 points 1 year ago (1 child)

    I wonder how they measure that. Writing 30% of loc with AI seems like it will be terrible. Writing 30% of each loc with AI (i.e. autocomplete) seems feasible

  • source
  • hideshow 1 child comment
  • [–] 5 points 1 year ago* (last edited 1 year ago)

    Yeah, what percentage of their code was previously written by Intellisense, because I suspect this is just copilot replacing intellisense/resharper plus a little more.

    Copilot is great for:

    a) replacing intellisense

    b) minor refractors / and very short method writing

    c) writing out boiler plate / test code

  • source
  • parent
  • [–] 7 points 1 year ago (2 children)

    I could believe this.

    But how is their OS or any other product even close to functional at that point?

  • source
  • hideshow 2 child comments
  • [–] 7 points 1 year ago

    Given they made a big hoohah a few years ago of getting rid of most of their QA—this in combination is a particularly bad look

  • source
  • [–] 5 points 1 year ago

    I wonder if Microsoft has a model that learns from their own source code. I have tried having copilot write sql queries and they work (without modification) about 10% of the time

  • source
  • [–] 3 points 1 year ago