and the engineers I know who are still avoiding it work noticeably slower

yep yep! as we all know, velocity is all that matters! crank that handle, produce those features! the factory must flow!!

and you fucking know what? it's not even just me being a snide motherfucker, this rant is literally fucking supported by data:

The survey found that 75.9% of respondents (of roughly 3,000* people surveyed) are relying on AI for at least part of their job responsibilities, with code writing, summarizing information, code explanation, code optimization, and documentation taking the top five types of tasks that rely on AI assistance. Furthermore, 75% of respondents reported productivity gains from using AI.

...

As we just discussed in the above findings, roughly 75% of people report using AI as part of their jobs and report that AI makes them more productive.

And yet, in this same survey we get these findings:

if AI adoption increases by 25%, time spent doing valuable work is estimated to decrease 2.6% if AI adoption increases by 25%, estimated throughput delivery is expected to decrease by 1.5% if AI adoption increases by 25%, estimated delivery stability is expected to decrease by 7.2%

and that's a report sponsored and managed right from the fucking lying cloud company, no less. a report they sponsor, run, manage, and publish is openly admitting this shit. that is how much this shit doesn't fucking work the way you sell it to be doing.

but no, we should trust your driveby bullshit. motherfucker.

Please, señor software engineer was my father. Call me Bob.

Thank you for saving me the breath to shit on that person's attitude :)

let me back up and try once more to respect your opinion

The point of me saying that was to imply I've been in the industry for a couple of decades, and have a good amount of experience from before all this. It wasn't any kind of appeal to authority, but I can see how you can read it that way.

jesus fuck I hope the poor bastards that under you find some other place real soon, you sound like a godawful leader

I'm sorry, do you trust junior engineers blindly? That's gonna lead to a much worse outcome than if they get feedback when they do something wrong. Frankly, I don't trust any engineer to be perfect, we're humans and humans make mistakes, that's why we do code review as a fundamental skill in this industry. It's one of the primary ways for people to develop their ability.

yep yep! as we all know, velocity is all that matters! crank that handle, produce those features! the factory must flow!!

In an industry where many companies are tightening the belt, yes it's important to perform well—I kinda want to keep my job and ideally get a good bonus. It would be pretty foolish to leave free productivity on the table when the alternative is working harder to bridge the gap, where I could spend that energy doing more productive stuff.

I agree with you on the examples listed, there are much better tools than an LLM for that. And I agree no one should be copy and pasting without consideration, that's a misuse of these tools.

I'd say my main uses are kicking off a new test suite (obviously you need to go and check the assertions are what you expect, but it's usually about 95% there) which has gone from a decent percentage of the work for a feature down to an almost negligible amount of time. This one also results in me enjoying my job a bit more now too as I've always found writing tests a bit of a drudgery.

The other big use for me is that my organisation is pretty big and has a hefty amount of code (a good couple of thousand repos at least), we have a tool that's based on GPT which has processed all the code, so you can now ask queries about internal stuff that may not be well documented or particularly obvious. This one saves a load of time because I now don't always have to do the Slack merry go round to try and find an engineer that knows about what I'm looking for—sometimes it's still unavoidable, but they're less frequent moments now.

If LOC/min or a similar metric is used to measure efficiency at your company, I am genuinely sorry.

It's tied to OKR completion, which is generally based around delivery. If you deliver more feature work, it generally means your team's scores will be higher and assuming your manager is aware of your contributions, that translates to a bigger bonus. It's more of a carrot than a stick situation IMO, I could work less hard if I didn't want the extra money.

ah but did you tell them in CP437 or something fancy (like any text encoding after 1996)? 🤨🤨🥹