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.


Same. I struggle to know where to start, and find if I just start, I eventually figure it out. A colleague of mine has nailed this. He begins with the documentation. Outlining all the functional requirements, then reviewing and iterating. It helps to have multiple sets of eyes review, including the stakeholders/customers. Once that’s locked in, the development is super smooth. It’s clear where to start, what the architecture looks like, and who needs to be involved. In fact, once the documentation is locked in, it’s very easy to get an LLM to build it competently. Plus no surprises because the stakeholder/customer has approved all the requirements.