This is the fediverse, so this is probably going to be extremely unpopular, but yea here goes.
Not saying you have to love it, or trust it blindly. Skepticism is healthy. But there’s a difference between “I use it carefully and check everything” and “I refuse to touch it.”
Historically, refusing new tools has never stopped them. Coopers didn’t stop the steel drum by refsuing to make them. They just ended up out of work while the industry moved on.
The realistic threat isn’t AI replacing you. It’s a colleague who uses AI well doing your job faster. And the skill of using it properly (knowing when it’s wrong, veriyfing output, knowing what not to use it for) takes time to build. Starting late means competing with people who’ve had years of practice.
You can have legit concenrs about ethics, energy, or jobs and still learn the tool. Opting out doesn’t fix those problems. It just removes you from the people who get a say in how it’s used.
PS. Ethically trained models exist and you can run models locally.


I am exposed to frontier models, my company is so enthusiastic about AI and so of course they are providing access. I am so tired of people denying my experience in this.
They make mistakes all the time, but in many software tasks you can provide a framework for mistakes to not matter and get detected.
There’s not much of a downside of scanning a codebase, but they absolutely raise false positives.
Yes it can find issues you missed, and you can ignore when it is wrong, that’s what makes it particularly good at code review, the mistakes don’t matter. It’s also effective at compromising security, because the attacker does not care about the mistakes. Letting it generate code in a scale where the human can review and intervene can be useful, particularly around some use cases that are very obvious but very tedious, as long as the human is extra vigilant.
It continues to be a risk to go full agentic and assume that the AI will sort everything out without review in scenarios where you can’t afford mistakes.