this post was submitted on 28 Jun 2023
7 points (81.8% liked)

Programming

17423 readers
25 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
7
The economic impact of the AI-powered developer lifecycle and lessons from GitHub Copilot (github.blog)
submitted 1 year ago by starman@programming.dev to c/programming@programming.dev
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Hazzard@lemm.ee 6 points 1 year ago (1 children)

Alright, guess I'll reiterate my usual beats here. AI code assistance is interesting, and I'm not against it. However, every current solution is inadequate, until it does the following:

  1. Runs locally, or in an on-prem instance. I'm not taking it up with legal or security if I'm allowed to send our proprietary code off to be analyzed on a foreign server. And I'm not doing it without asking. It just isn't happening.
  2. It has to be free, or paid for by my company. It's cool, and it might help me work, but paying a subscription fee on something that only benefits me at work is essentially the same as a pay cut. Not interested.
  3. It has to analyze the entire repo. In my current tests of ChatGPT, for most cases I've spent long enough giving it context that I could've just... solved the problem myself. It needs to have that context already.
[–] starman@programming.dev 1 points 1 year ago (1 children)
  1. I agree
  2. GitHub Copilot is free for students, and that's the way I use it
  3. GitHub Copilot takes some context from recent files, but iirc they are working on "copilot for your codebase" or something like that
[–] Hazzard@lemm.ee 1 points 1 year ago

Ah, it makes way more sense for students, absolutely. None of your code is proprietary, so that's not a concern, student pricing makes things easier.

Plus, your tech stacks are much simpler. Usually just... Java, or Python, or something. Not a python webserver using X framework for templating, Y framework for typing, and Z framework for API calls to some undocumented internal API.