[AnotherGoodName]

Shrug If you are being told by your boss to use AI or quit and you absolutely refuse to use AI yes you should quit.

The end. No anger at you or your boss. It's an incompatibility.

I understand why some companies mandate usage these days. Especially for programming. The honest truth is that it does speed up development. The other honest truth is that there's resistance to change that harms productivity at times like this and the only way around that is for leadership to be very direct on this point.

To use a metaphor employers don't want weavers who refuse to make use of the loom. https://en.wikipedia.org/wiki/Luddite

[tonfa]

> To use a metaphor employers don't want weavers who refuse to make use of the loom

it's funny to reference that, since the luddite movement was about working conditions, pay, and quality of goods produced. It wasn't ideological opposition to technology (They didn't destroy machines when acceptable conditions were agreed)

[bgwalter]

You are a good employee!

> To use a metaphor employers don't want weavers who refuse to make use of the loom.

The loom actually produced something, as opposed to mediocre coders who ingratiate themselves with management by pushing "AI" because they hate all productive people.

The loom also did not steal other people's IP.

[AnotherGoodName]

I see this attitude a lot. The idea that people finding value from AI are mediocre programmers.

I've been staff level at Meta and Google and many other companies in my career. I've been in the industry over 20 years now. I can talk to peers in the industry at that level and above and the sentiment is pretty universal. "This saves a lot of time, we need engineers to learn to use this asap". Such decisions are not coming from a vacuum. It's literally your most senior engineers advising management that leads to these mandates.

[reseasonable]

It’s a skill just like any other. Without practice people will absolutely waste time. But knowing which problems are appropriate for an LLM can save days of labor.

As an engineer in the field for 30 years, this tech beats every man page, sdk, google search, stack overflow post or head banging situation by light years.

The rebuke of it is surprisingly antithetical to the progress of the industry. It reminds me of the decade+ of those who refused to use an IDE and favored notepad[++] or vanilla vim instead. I suspect in 5 more years those similarly-minded folks will finally adapt in the same way we’ve all grown accustomed to IDEs today. Or those who adapt will just outpace those who don’t.

[happytoexplain]

The rebuking is largely focused on using AI-written code (and other content) in ignorant ways, not on using AI to learn or to get example code upon which to base your own, or for simple objective code you can confidently audit, which are in fact more reliably good and less depressing/degrading/market-damaging use cases.

[happytoexplain]

>No anger at you or your boss. It's an incompatibility.

I am allowed to be angry at a person for their opinions or actions.

>Luddite metaphor

Metaphors are already a weak and oversimplifying rhetorical hammer, this one particularly so.

[p0w3n3d]

The loom however does not make t-shirts despite you asking it for the shorts. The loom does not confabulate, create four handed sleeves and tell you this is the correct way...

[techpineapple]

Just like, thinking about how bad early machines were, I bet early looms made a whole bunch of annoying mistakes that required cleanup. I think one of the biggest jobs of the early Industrial Revolution was like babysitting machines.

[HPsquared]

Most technical jobs today are still babysitting machines, in some form.

[frizlab]

> The honest truth is that it does speed up development.

That is a highly controversial statement! It depends on what you’re working on, how you work, and so many other factors than just laying it out as just a fact is close to dishonest.