Spoken like an unemployed person....

Why would you sabotage or stagnate your career?

Principles or ideals prioritized above comfort and stability, fucked up you have to ask. Spoken like a hollow bootlicker

This.

I've already got my manager to tell me to not use AI on a task. I see this as an absolute win and I'm gunning for more.

He ALWAYS uses AI first when he needs to figure something out. ALWAYS tells us to use AI for the quick start. But when we do it, and it ends up wasting time, somehow it's our fault, and we didn't prompt it properly.

Also, am I mad, or does Cursor (specifically Sonnet) sometimes act dumb on purpose? Sometimes it codes a feature nearly entirely without many issues, other times it seems unable to comprehend that it's using the wrong property in a class.I feel like it's made to make us question each other's ability to use AI tools and cause internal team unrest.

8,300 lines

rookie numbers

I think my team is in the tens of thousands of AI generated "documentation".

They claim the AI can use it to code better in the project.

Bullshit. The AI can't load in a single one of these files without filling half the context.

I was recently instructed to have gander at it.

I warned that it seemed inconsistent with the actual code.

Was told I'm right and they brushed it off.

"We should update this to reflect reality"

They brushed it off and we moved on. The misleading doc is still there, waiting for its next victim.

Who's going to be blamed when the summary got it wrong though?

Plant the seed of using OpenClaw, but make sure you get no credit for it.. Once it's taken root, make sure you back up as much as you can of everything.

Wait for OpenClaw to inevitably self implode. Panic happens. Point out this is why you didn't trust AI, become hero by having the backups ready so everything's not destroyed.

People who don't know better like AI until it vibes back and bites them.

Closing tickets faster is pointless if you're introducing a bunch of new bugs.

Objectively true, but if my bonus reflects tickets rather than bugs, I'm gonna close so many tickets, anyway, because I don't own the place.

Which is also why wise companies grant their employees stock.

A popular option is to use vibe code to help run the place into the ground while looking for the next job.

Pretty soon the wave of vibe-shit code is going to be too much to clean up.

Interesting times ahead.

Step 1, update your resume.

Step 2, follow your boss' instructions until it all breaks.

Step 2.5, document everything so be can't blame you later.

Step 3, go have a beer; you don't get paid enough to give a shit.

Honestly, this is what I would do in your situation:

1. Update your resume and start responding to LinkedIn messages and possibly looking at least possibly.
2. Take those workshops for LLMs, there might be useful stuff to learn there, auto-completion, code search and examples of how to use certain features are very good uses of LLMs.
3. Don't be overly vocal about it, but point at issues when you see them, e.g. those large messages that you're expected to read point out how they're way longer than need to be and how using LLMs to give you a summary said the wrong thing (even better if you have an actual example of this, by for example invoking TLDR bot or something similar on those messages every time they come up)
4. Look at code that was vibe coded in areas you're working and start creating tickets for the stuff you see, unless they're vetting everything the LLM produces (which would be slower than writing it yourself) there will be issues there, start documenting those. The thing most managers and other "AI enthusiasts" don't get is that LLMs are trained with stack overflow and thousands of random GitHub projects written by inexperienced devs for every one good piece of code, so they have thousands of bad or incomplete examples for every good one. This means they end up not doing things like verifying you're logged in to use an API, sanitize SQL queries, etc. Because when you ask how to do something in stack overflow you will get an answer that is not meant to be used literally things like `query = f"SELECT * FROM {table_name}"`` is an okayish example on how to build queries with validated data, but it's a TERRIBLE example to use with user provided data, but the LLM doesn't know that, it just copy pastes the code that gets things from a table where it needs it.
5. Prepare yourself, using LLM to write code has a short lifespan in most companies, but the damage takes twice as long to clean up. If you stay you will be seen as the naysayer and might even get fired for it, but eventually this will blow up so gigantically that they'll start to regulate or even ban LLMs. And then there will be lots of garbage to clean up. In your shoes I might look elsewhere while possible as I wouldn't want to be associated with the company that had all of their data leaked or similar, because if they're using vibe code in prod it's a matter of when.

Everyone. One person is too lazy to write a message, the others can't be bothered to listen to the whole thing 🤷‍♂️

The transcription should be attached to the audio recording so if the sender cares about it being correct they should be able to comment or add correction.

Sounds like I walked into reddit antiwork crowd! Always black and white with you lot... If you're in industry and market that allows that? I'm happy for you.

This but without the backups. Then walk out of the building towards the camera when it all explodes behind you.

I'm starting to form a conspiracy theory that the "let AI write the email" concept is, in itself, an ad for AI. Not for people writing them (they are easy to convince), but now the people reading them have a bunch of bullshit to deal with. The best tool is an LLM summary to undo the LLM bullshit. They get double the usage from people (well, if the manager gets many subordinates to do this, it's well more than double), and nothing of value was added.

I think you're gonna have to kill them

You're the one who crashed in with the judgment, name calling, and confrontational attitude. You couldn't be more thoroughly shaped by your "industry and market" and I'm not sure if it's more gross or sad. Corporations might be people now but they're sure as shit not gonna cry at your funeral, get a life outside your job

Jokes on em, I don't read work emails. Partially because I refuse to dedicate any time of the day using Outlook, especially in a web browser, because the oh-so-wise IT departnent does not allow to use a different client, and as I can't use Outlook on Linux, fuck em.

And no, IMAP or POP3 are not available. Trying to login via Thunderbird just triggers a message to contant IT dept to allow me using it. It's Teams or nothing.

Some very bold assumptions.

Reality is, attitude like that doesn't get you hired. I don't hire based on people's view on AI and LLM, but I do hire on attitude and one's ability to be molded to fit the job I'm hiring for. Hasn't failed me for 20 years and this is far from the first fear mongering in tech.

Ability to be molded as a primary virtue is completely alien to me man. Maybe it's a cultural thing. "Reality is," I see forming your self to fit the needs of this system as a tragic waste of life. There are ways to sustain yourself beyond blind acquiescent compliance, and basic human needs a career can never meet. I would feel like a failure having spent the last twenty years of my life guided by what was best for a business.

You should try it yourself. See what it can, see what it can’t instead of just arguing with your boss about something you don’t really know anything about

And then you can actually bring the facts to your boss.

Never forget that it isn't thinking, at all. It comprehends nothing. It's just a very big, expensive autocomplete. It didn't understand when it was using the right property, it just rolled its d10000 and got something that fit requirements, but on the time it failed, it rolled outside of the desired range. No thought, just numbers.

I'm not sure where your belief that work somehow defines me come from... Maybe it's something from "your culture".

You make so many assumptions is wild and tiring to even bother to repute them. I'll leave it here as I'm not convinced you're actively engaging in any sort of conversation anyway.

Yeah, you'll soon see the boundaries of what it's useful for and will then be able to make informed decisions.

Vibe-coding UI for a one-off questionnaire? Why not. Vibe-coding something you need to maintain? Oof.

I'm reasonably sure that's what's happening with resumes largely now. People get AI to write their resumes because it's a boring task to do, and then employers are using AI to read the resumes they receive and provide summaries. So it's pretty much just AIs talking to each other about who should get the job.

Having seen a code base written by humans over ten years, it's overrated.

mostly joking.

To complete this 2 sentence horror story:

Such code bases are what the Vibe coding AI is trained on.

At least Claude agrees that interfaces for almost every Java class is a little overkill, and if there's only one implementation, it's a code smell. It's harder to convince the architect who learned it at uni and blindly follows suit.

Have you been to one of the workshops? It CAN be very useful when used right, setting up an MCP server pointing at internal docs/best practices made a huge difference etc.

Any criticism of AI you give will have a lot more weight if it comes from a base of knowledge. That means learning how it does (and doesn't) work so you can critique it without coming across as "that anti AI guy".

Make sure you go through everyone else's PRs carefully and pull out all the stupid AI stuff, it's great fun ripping them to shreds sometimes.

It can be maintainable, but I only if you are actually reviewing what it spits out and correcting it (either manually or with more AI).

That removes a lot of the benefit in a lot of cases.

It is nice to be able to have it scaffold thousands of initial lines before you dive in though!

My advice is to stick to making specific observations as not to sound hyperbolic.

Yet at the same time what is needed is a counter-narrative to "AI can do the job". My observation is the industry cycles between agile and waterfall development and people (who are the loudest) are using AI to do waterfall development. This is a bad idea for the same reasons waterfall development is bad: trying to write a spec that covers all situations is counterproductive.

The alternative I see is that we borrow from Agile and treat AI as a pair developer that you outsource small (or largely repetitive) tasks to. This is not vibe coding nor is it TDD as you are still actively developing all levels of the code, but your feedback loop (OODA) is kept short.

Exactly, but if you review it, it's no longer vibe-coding. At least as far as I know, vibe-coding means specifically to not look at the code at all.

That's fair, I'm not sure there is a nice snappy term for using it properly though.

I work in consulting big corporate, it's AI all the way down.

I work in a GenAI team building mostly LLM powered applications. I use LLMs to work, they can be useful if you pick thr the largest model available. with smaller models it's just a waste of time.

My boss is very technical (theoretically) but he sold his brain to LLMs and do hard vibe coding of whole apps by himself and the pushes the on the team to do bugfixing...

Fun fuct, he always downsize estimates, since "he can do in 1/5 of the time".

yep, welcome!