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.


Yeah I’ve started accepting this as well, begrudgingly. As a programmer I hate it, but the world I lived in isn’t coming back. I’ve been playing with local models and it’s been fun.
Somehow I kinda learn something about myself. They’ll keep going in circles or diving head first into development without properly planning, and I’ll have to correct them. But in doing so I kinda recognize the irony that I would absolutely do the same myself. I hate planning, I tend to start as quickly as possible with programming. And because of that, I tend to get stuck in similar ways. Maybe I should start operating more like a multi-agent setup myself. Have a “planner me” logically split up the work before “executor me” mindlessly ticks off the tasks one by one. Sure beats the absolute chaos that’s going on in my brain usually.
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.
That’s also what makes this annoying though. With these tools I’ll probably be spending more time doing the things I’m not good at, while the LLM can do the exact thing I’m good at. I just need someone to treat me like a silly LLM the whole day and get paid for it. Think about it: you can spout nonsense, write silly code, and just solve fun problems. I want to be the LLM