AI has automated my favorite part of the job: coding.

Gone is all the experience in clean code, good idioms, etc. All replaced by easily generated shitty code that can be removed and generated again as we please, until it works. No thought about the quality of code itself. Some companies are straight up forcing programmers to live in Claude Code and never even see the code, just write the spec.

It’s disgusting. And the worst part is that you can’t opt-out. If you give even the slightest hint that you don’t like AI you’re seen as a Luddite and you’ll be put next in line for the upcoming layoff.

I think you do a good job capturing an actual microcosm of the real problems here at an emotional level - why people "hate" it.

(a) loss of fulfillment (b) lower quality of output and nobody will care so the world will just "degrade" and (c) a perceived lack of autonomy ("forcing", "you can't opt out") around how adoption itself is executed

This is surprising to me because I found that I am able to invest even more of my time in considering the good abstractions and idioms that I want to employ for a particular problem, and now most of my day is spent in discussing patterns and architecture rather than what brackets I have left to close.

Although, full disclosure: I have quibbled with Gemini quite a bit over the trailing comma, which clutters the diff, and buries the lede at code review.

But it's been very gratifying to refer to modules entirely by their role in a given design pattern (eg "driven adapter") and be understood. To define the idiom, and see it adhered to.

But am I operating still at too low a level? Would I be penalized, at these "some companies" for not producing shitty code?

Ah, but in my particularly forward-deployed line, there's always an element of showmanship compelling me to write demonstrable code.

But, also, how can I specify the behavior if I can't name the component? Is it really possible to "vibe" code à sophisticated piece of software entirely from the user's domain terminology? Without any intermediate abstractions in mind? Inconceivable, frankly. There are invisible walls, invisible shapes beneath the surface.

Then again, I'm young enough to have never allocated memory manually in my professional life.

I've experienced myself that even if you explain to your AI-loving boss in a well reasoned manner that an LLM is not the right tool for the job he wants you to use it for, you simply get labeled as anti tech and your chances of advancement plummet (he was explicit about that). But I still do it, because dammit I'm still a human with a brain. The thought of being a corporate drone who just falls in line with any demand no matter how asinine is worse than the thought of being unemployed.

Just because tractors are here doesn't mean you can't garden as a hobby. I'm also tired of the slop, but this is a culture and management problem. Every software job I've had there was tension between speed and maintainability.

> It’s disgusting. And the worst part is that you can’t opt-out. If you give even the slightest hint that you don’t like AI you’re seen as a Luddite and you’ll be put next in line for the upcoming layoff.

So we found something much worse than crypto.

You can opt-out of crypto, but you cannot opt-out of AI and have no choice but to participate.