I am now being required by my day job to use an AI assistant to write code. I have also been informed that my usage of AI assistants will be monitored and decisions about my career will be based on those metrics.

I gave it an honest shot today, using it as responsibly as I know how: only use it for stuff I already know how to do, so that I can easily verify its output. That part went ok, though I found it much harder to context switch between thinking about code structure and trying to herd a bullshit generator into writing correct code.

One thing I didn't expect, though, is how fucking disruptive it's suggestion feature would be. It's like trying to compose a symphony while someone is relentlessly playing a kazoo in your ear. It flustered me really quickly, to the point where I wasn't able to figure out how to turn that "feature" off. I'm noticing physical symptoms of an anxiety attack as a result.

I stopped work early when I noticed I was completely spent. I don't know if I wrote more code today than I would have normally. I don't think I wrote better code, as the vigilance required is extremely hard for my particular brand of neurospicy to maintain.

As far as the "write this function for me" aspect, I've noticed that I tend to use the mental downtime of typing out a function I've designed to let my brain percolate on the solution and internalize it so I have it in my working memory. This doesn't happen when I'm simply reviewing code written by something else. Reviewing code and writing it are completely separate activities for me. But there's nothing to keep my fingers and thoughts busy while I'm coming up with what to write next.

I didn't think we were meant to live like this.

I quit my high paying job mostly because I was pigeonholed into developing with
OpenAI/LLM/agents RAG and all of that. I was even good at it, but it is all so stupid to me.
Across the company they were starting to make us use copilot.

It got to the point that writing good code and developing cohesive systems
was not even on the radar. It was all just vibe code BS. I couldn't do it.

I guess I'm a luddite, but I don't care. I am one of those people that
thinks deleting code is usually of higher value than adding code.
I've always worked with mostly programmers that kinda just went along,
but usually the lead programmers were at least decent to good.
Not anymore at the job I was at. It was all hype, BS, and garbage code.

I worked for a while doing maintenance kind of work on large java projects.
I know how painful it is to fix code where people just added and added and added.
It's like the US tax code.

Anyways good luck :P

@pkw @uberduck This! Deleting code on legacy systems tends be of higher value in the long run than adding.

Illusions of progress now -- leading into technical debt -- will just crash & burn later.