you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 1 year ago (3 children)

except programmers are gonna continue with what they were already doing, at most putting a script on copilot to get the metrics

don't forget that if you don't turn in the project in time you're fired, the issues always get thrown at the coder, it's never the company's fault

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

    Company I'm at also does the forced AI and it's all but mandatory now. Problem is as code monkeys we're past the point of heading down to the Winchester for a pint until it blows over. They're pushing so hard in order to "not fall behind" that you literally can't escape it. I think even malicious compliance won't cut it. And when 8/10 companies that dictate the market say that "this is the future", then this is the future they'll make whether we like it or not.

    Edit: the silver lining is that we're working with tools that are better than copilot at generating menial work like generating boilerplate code, unit tests, release notes, walls of text for app documentation etc.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 1 year ago (1 child)

    release notes and app documentation:

    memes aside, are they blaming the coders or the ai on the slower project turnout?

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

    We're in the honeymoon phase, shit didn't hit the fan yet. Problem is we devs are fucked either way. If productivity does increase, then workforce demand will go down especially for entry level devs and seniors will be relegated to vibe coding and fixing AI bugs. If it all goes south then layoffs, because line must go up!

  • source
  • parent