Rehiring large numbers of people after AI-motivated layoffs is not the same as getting rid of LLM-generated code and going back to hand-written code as a whole.
We don’t have a no-AI policy but I’m trying to hand roll some code, because it is useful for interviews. It is very difficult to memorize the exact syntax unless I hand write code everyday.
I don’t think that would ever happen. AI as a tool made the life so much easier removing initial inertia.
I agree that we still haven’t figured out what’s the best way to use AI tools, but over the time it would mature and people would come up with patterns, conventions, and design principles so the quality of what is produced will be maintained or increased while keeping the productivity gains.
Yeah I cant imagine my job without it anymore, in my hobby projects I dont really use it because its more about learning new stuff but for work I dont really care
In my startup, I am currently in consideration for doing this exact thing. The interesting part is it's not really the AI that's causing the issue. It's the ease of my developer to make a mess, either with messy code or feature bloat.
After figuring out the exact product we need with some very quick development cycles with AI, we now have some problems that I can't keep under control because of AI. So, currently under consideration to rewrite the core functionality without AI so we can keep it simple, understandable and slower to change.
The interesting part is that AI could do this, but managing developers with AI has become very difficult to get them to slow down and build stable simple things.
This is a leadership problem, not an AI problem. I have the opposite situation: I don't think about code "messiness" anymore. I trust my developers to ship the right thing because we communicate constantly about what our goal is and why we're doing it.
Solve the leadership problem and the AI thing becomes an advantage instead of a problem.
I'm running a startup and we deliberately don't use AI for development. We only use it for review.
We're working in a really deep area where having full understanding of our code is more important than speed.
Besides, in this area, clients getting one whiff of AI code would be an immediate deal-killer
Ford did: https://www.forbes.com/sites/joetoscano1/2026/06/30/ford-hir...
So did Commonwealth Bank of Australia and IBM: https://www.cnbc.com/2026/07/01/employers-who-laid-off-worke...
And I'm sure many others who didn't publicize it because they have to keep this circular economy going.
Rehiring large numbers of people after AI-motivated layoffs is not the same as getting rid of LLM-generated code and going back to hand-written code as a whole.
No they didn’t. Did you read either of the things you posted?
We don’t have a no-AI policy but I’m trying to hand roll some code, because it is useful for interviews. It is very difficult to memorize the exact syntax unless I hand write code everyday.
I don’t think that would ever happen. AI as a tool made the life so much easier removing initial inertia.
I agree that we still haven’t figured out what’s the best way to use AI tools, but over the time it would mature and people would come up with patterns, conventions, and design principles so the quality of what is produced will be maintained or increased while keeping the productivity gains.
Yeah I cant imagine my job without it anymore, in my hobby projects I dont really use it because its more about learning new stuff but for work I dont really care
In my startup, I am currently in consideration for doing this exact thing. The interesting part is it's not really the AI that's causing the issue. It's the ease of my developer to make a mess, either with messy code or feature bloat.
After figuring out the exact product we need with some very quick development cycles with AI, we now have some problems that I can't keep under control because of AI. So, currently under consideration to rewrite the core functionality without AI so we can keep it simple, understandable and slower to change.
The interesting part is that AI could do this, but managing developers with AI has become very difficult to get them to slow down and build stable simple things.
This is a leadership problem, not an AI problem. I have the opposite situation: I don't think about code "messiness" anymore. I trust my developers to ship the right thing because we communicate constantly about what our goal is and why we're doing it.
Solve the leadership problem and the AI thing becomes an advantage instead of a problem.
> I am currently in consideration for doing this
Try “I am considering”.
In what context would generating code faster not be a desired outcome?
Assuming of course everything else stays the same (quality, etc.)
I think most AI doomers will tell you that the quality of their code is better than LLM-generated code.
I think devs themselves won't want to work for a company that doesn't let you use Codex et al.
Best use cases are along the periphery: security checks, performance checks, test generation.
i dont know
Although code quality may sometimes suffer, no one can deny the productivity gains AI brings to software development.
Neither can anyone deny that 'productivity gains' are worthless if what's being produced is worthless.
> Although code quality may sometimes suffer
That doesn't sound like a good thing in the long term.
> no one can deny the productivity gains AI brings to software development.
What are those "productivity gains"? Rapidly building hundreds of the wrong things that people do not want?
It means you cannot stop and the competition only moves far quicker and its a forever race to the bottom.
Do you know of any company that banned IDEs and went back to plain text only editing?
Do you know of any company that banned compilers and went back to hand written assembly?
Do you know of any company that banned stack overflow and went back to figuring everything out?
Someone answered the question with some actual examples. Please refrain from the hyperbole