I mostly design and architect the systems, don’t write the code myself anymore.

I believe the important part is to keep working your critical thinking, don’t just blindly accept the output. Understand, scrutinize, consider, criticize.

Writing bad syntax and not remembering func signatures are obvious problems that will auto-resolve as you personally re-familiarize yourself with the tech you’re working with.

Malicious compliance, to some extent. The only people I can complain to are 3 levels down the AI train. Never let the AI update the git repo, review all changes it makes. I end up removing like 90% of any comments added as useless or too confusing to live; especially comments that have DO NOT REMOVE in them. Ends up taking about the same amount of time as if I just did the work myself. Quality is better, because the tool is good at what it does best.

I’m lead in my team and AI is being used to varying degrees. One colleague is a problem, but was a problem before AI as well. Me and my other three colleagues have a common understanding of you have to take ownership, understand what you’re doing, and document it.

As a reviewer, I ask for the information it lacks.

We (our company) has another project started with “AI first” too, and now still works mainly through “document features and behavior and stuff in md files and AI generates it” - so mostly about spec writing and AI generating. I don’t know how well that works, but I’ve heard bad more than good things (which may be common anyway) and it certainly hasn’t lead to meeting timelines (now more than half a year behind the original planned release).

Personally, I’m still skeptical about AI use, but do use it occasionally. Our project is simply too complex (and legacy and long history of changed dotnet technology as well). It’s more feasible on newer projects, but Blazor isn’t a straight forward framework either, mixing razor, html, css, component isolation, SAP lifecycle, render modes and whatnot.

I haven’t used AI to a degree where I feel it significantly [negatively] impacts my capabilities. Thankfully, my team hasn’t pivoted into that completely, either. I see the risk and hope pushes though. The promise of AI speeding things up. The customer saying “a bit more risk is fine”; but it’s on us to communicate the difference between risks (the bug fix missed one additional unknown place vs long term maintainability and its associated risks).

use AI to learn new stuff making sure to check stuff that smells fishy.

Same situation as OP, when I do peer reviews using AI and it reports a list of flaws I just ignore it. If the Coderabbit doesn’t catch it then I’m just allowing the human error back into the code. It still sucks but there are future bugs to fix.

By being unemployed

Find an open-source project (better if it’s noAI), then work on it manually.

Where I work we can still push back to big PRs. Our guideline is unchanged that it shouldn’t be more than 700 lines of change. The less the better. With agents it’s even simpler to deny a big PR. A manually written big PR would have meant lots of manual effort in reworking it. With agents I basically just demand the author to tell their agent to split their fucking PR up.

stop using AI?

I made a horizontal career move and accepted as a trade-off that at this time I won’t write code.

Old company: mildly toxic environment, out of touch CEO, poor leadership. Increasing AI push and wild gaps between different people’s competence. Constant arguing. The dreaded 5k loc generated PRs started appearing. My role: ~5% web programming tasks (that I actually signed up for originally) rest was design, review, and people-related work. I was not a manager. Hated it.

The project: 1 year of goal-oriented homelabbing, from a 50€ raspberry pi to hybrid cloud, gitops, kubernetes, and all the good bleeding edge stuff you need to run your own cloud. Did this completely without AI, built the resume, applied to a few places. Happens that one of the companies was looking for the exact stack I built my homelab around.

New company: Platform team, 90% hands on, competent manager, capped AI budgets, people treat each other respectfully. I quite like it. When I do coding it’s simple enough that it stays manageable even though I ask some bot to write it 90% of the time. It gets the job done, I wasn’t hired to write code anyway.

It’s probably a patch, but I’m hoping to run the wave long enough by this move. For the first time in a couple years I feel clarity. I trust that I’ll be able to pick up programming by hand if needed. Most people are in the same boat anyway, so the expectation won’t be there to perform on a similar level instantly. I trust that my ability to learn new things keeps being valuable.

On my free time I don’t currently write code, non-technical hobbies and maintaining the homelab I conjured eat it up. I don’t mind too much. I have enough interesting stuff to do. I think most of all it’s important that I get to create something. If I’m not exactly paid to do that it’s not the end of the world. Much worse situations exist, I’m still paid similar €€ than in my software position.

I don’t believe you can fight back. Don’t want to work with AI? Get replaced by somebody who will. On the other hand… work with AI and find yourself out of a job. I don’t see a good outcome either way.

Not sure how the next few years are going to unfold and it’s pretty scary tbh.

Might just go learn a trade alongside everyone else…

In a similar boat. I’ve been programming since my family got a IBM 386 in the 90s and I started dabbling in the dark arts. I’ve been a career programmer for 20+ years now. I’ve loved it, all the way up until the past year or two.

Here are some of my rambling thoughts and perspectives, for whatever they are worth.

• “Don’t try to fix someone else’s mistake while they are still in the process of making it.”. AI is both a useful tool and a giant shit show, but if your company wants the shit show, then let them have the shit show, do not carry their burden.

• Lean into hobbies that aren’t on computers. I do woodwork, gardening, arts and crafts, sewing, home repairs, camping, etc. “Go touch grass” as it were.

• “Fight fire with fire”. (I don’t understand that saying) But the point of it is to say, don’t manually review AI slop, if they are gonna slop 800 file PRs at you, AI slop review them and move on. The Titanic is sinking, you aren’t going to save it by frantically bailing with a bucket.

• Programming is both an art form and a skill and it is also like riding a bike. You may not ride for years, but if you get on a bike it will come right back to you. Don’t stress or worry that your skillset is deteriorating, it will always be there. It may get rusty and need some lube, but it won’t go away.

• When the AI bubble finishes popping, AI will still be around, but it may not be shoved into literally everything as much, and there will still be a place for talented people to do quality work. Examples from 2 of my top hobbies is that we have both automated farming and assembly line furniture factories, but handmade solid wood furniture is still around and worth doing, and there are still gardens in a lot of back yards.

• Most of the people in the top positions in our governments and companies are completely and utterly unqualified to be there. You’ll be fine. Focus on being your best self, being happy with YOU. AI is here to stay, but talented people have not lost any value at all, know what you are worth, have some confidence, don’t let the slop get you down, there is literally slop in every aspect and career, try not to worry about it, ya know? Mass produced, low quality clothing and furniture exists, but people still sew and woodwork. It’s ok, be better than the baseline slop and you will have value to those who understand.

• Being a “Jack of all Trades / Master of None” isn’t a bad thing, neither is the inverse a “Master of one thing and nothing else”. All of that is also very black and white thinking, it’s not reality. People are more than just their skills.

Final thoughts and summary: The AI slop is here to stay. As I learned in therapy “Don’t fight the current/flood/rising tide, learn to swim and float above it.”. The river is going to go where it is going to go, you can either be swept away and dragged under or you can sail along the surface and enjoy the breeze. I, personally, recommend the latter.

Good luck out there! You got this!

My job is 75% maintenance and 25% developing new app features. That 25% is really interesting and is what drew me to my current company, but maintenance is what management cares about most and what our customer service team is constantly pushing us to do.

The problem is that it’s boring and repetitive work. Ever since the company started promoting the use of AI, I’ve been delegating these tedious tasks to agents who work on separate Git worktrees, while I focus on learning new things and implementing them alongside new features that we previously didn’t have the time or budget for. Management is satisfied, and I’m learning a lot thanks to the time I’ve saved. Most importantly, I’m still writing code myself, code that I actually enjoy writing.

Could one simply write code themselves and ask the AI to make it look like it did it?

If job wants slop, I just queue up work back to back in the slop generator. While the slop generator is running, I’m reading a book or building something by hand to make sure I stay sharp. If my engineering leadership doesn’t care about quality, then why should I? Give em what they want and take care of your own needs