The market is not easy right now. I would not leave unless you have something definite lined up.

> 1. Be pushed into a workflow that will cause my technical growth to stall or degrade

Whether your growth stalls or degrades is up to you, but in my country your employer's ability to tell how you how to produce/deliver the work (not just the outcome desired) is the difference between being an employee and contractor

You should remain open to new things in this industry. Hate it or not, AI is currently the new thing in our line of work.

> 2. Be overseeing a bunch of AI-generated spaghetti 2-3 years from now

How you implement code, including human review and understanding of code, is key. I have never copy and pasted code into development from an LLM/AI helper. I've certainly asked it questions about the code, tested the code output, had it add comments to help me understand the code it wrote and produce alternate methods that better fit my needs, etc.

"No spaghetti" in the codebase will prevent having to take care of it, but that doesn't mean small modular components, troubleshooting, general ideation of different approaches to see what can scale, etc. isn't going to be really helpful.

> I'm a 'senior engineer' with ~5 years of industry experience and am considering moving on from this company

5 years is not what I would consider a big bargaining chip in today's market full of seasoned developers, including those who started when they were in middle school and are applying for the same jobs as you would be.

Can you work with your employer to effectively introduce some AI tools and workflows to help ideas, changes, revisions, new features, or even documentation?

Don't jump until it is safe, and remember the next place is likely just slower or one leadership away from asking their employees the same thing your employer is.

▲

NotAnOtter 8 days ago | parent | next [-]

>You should remain open to new things in this industry

I'm open to new things. I've seen demo's, attended presentations, and spent a long time toying around with it myself. I have not been convinced there is any meat there, not in it's current iteration. LLM's are designed to make things that "look" like human output and thus are very good at hiding bugs. It's ok at getting the first 20% of the project done, but that was never the hard part. It's always been the last 20%, and modern LLM's simply cannot do it. Not on large scale projects.

New things have come and gone. So far the only thing I'm convinced of is, it's easier to get funding when you can claim you use AI. That's it.

> I have never copy and pasted code into development from an LLM/AI helper

Well that's simply a different reality from what my employer is encouraging. So not relevant. They not only want us to copy-and-paste, they want us to delete otherwise functional code to make it easier to paste in AI generated stuff.

Asking questions is fine, that's much much closer to an augmented search engine than prompt engineering. You're describing something different from what this post is about.

>5 years is not what I would consider a big bargaining chip

I'm not bragging. I'm giving context. If I was 0 yoe or 20 yoe, those would be relevant too. And for what it's worth, I also started in middle school.

>one leadership away from asking their employees the same thing your employer is

Yeah that's probably true

▲

leakycap 8 days ago | parent | next [-]

>I'm not bragging. I'm giving context.

I didn't think you were bragging, and I hope I didn't come across as trying to put you in your place.

I'm responding with market context. The market is upended right now with no end in sight. Also, most employers if not meaningfully all, will or are involving AI. Many, if not most, people applying for decent positions right now have 3x the experience and are very willing to do whatever.

Don't let your principles end you up sleeping in your car.

> LLM's are designed to make things that "look" like human output and thus are very good at hiding bugs.

This can be true, definitely was more often true in the past. But there is a time and a place for human expression, and probably isn't in code. Your human expression is likely helped by tools. I doubt you're writing in Notepad, but your IDE doesn't get thrown out the window because it can't fully replace you or write code for you.

IF you are being blindly told to copy/paste from an LLM, then use that as part of your ideation and work from there, using AI tools as much as you can in ways that work. Become a leader in this new frontier by delving in (just kidding, that's meta about another article trending on AI)

> They not only want us to copy-and-paste, they want us to delete otherwise functional code to make it easier to paste in AI generated stuff.

Your post needs more detail if you want people to reply to your exact situation, but I think you can make clear arguments against doing this, then do this for 3 weeks, followed by the obvious: backtracking.

Leaders are by nature often encouraged to try new things. Standing in their way won't help you, but you can warn them, do it, then help them get back on track. By being a team member in this way, you are not in charge, but you can build trust equity if these leaders stick around and have techy ideas in future. In my experience, I usually outlast bad leadership (and their associated ideas). You have to be correct and not act like you're the boss to survive it, though!

▲

kasey_junk 8 days ago | parent | prev [-]

Feel free to make your own decisions about this stuff but know that there are people with lots of experience and success in the industry using llm coding tools successfully (I’m one).

I am in a situation where ai was mandated, I was skeptical, but took it as a chance to try it out. I now can’t imagine going back.

	▲	danielbln 6 days ago \| parent [-]
		Yep, if you know what you're doing, if you have good software dev and review practices and if you manage to aim the AI foot gun away from the body, then the productivity boost is absolutely gigantic.

▲

mattl 8 days ago | parent | prev [-]

But also don’t give up your principles and use AI stuff if you’re against it.

Hiring people who haven’t used it will be a marketable skill too

▲

leakycap 8 days ago | parent | next [-]

I think it is easy to give that advice if you are somehow shielded from the reality of the market right now.

Which companies can you point to with openings on their careers page that specifically mention "no AI" or don't mention AI as part of the toolchain/expectations?

	▲	tuesdaynight 8 days ago \| parent [-]
		You are 100% correct. And I can't understand why some company would want someone who never used AI. What's the advantage? Honestly, it sounds like wishful thinking.

▲

qualeed 8 days ago | parent | prev [-]

>"Hiring people who haven’t used it will be a marketable skill too".

Can you explain your thinking on this?

Obviously there will be jobs where AI isn't required, so omission of experience would be fine, but I can't think of any reason why it would be marketable to advertise "I've never worked with AI".

In fact, I don't think I've ever seen a resume that contains anything along the lines of "I haven't used X". You would just omit the lack of experience. Otherwise it risks signaling other negatives (not comfortable with change, etc.).

▲

muzani 8 days ago | parent [-]

It's a moral stance. But AI isn't as bad as say, biological weapons. It's closer to piracy.

So it's like I've never used a gun. Which isn't really a strong point. At the very least, even if you don't plan to use guns, you'd know how guns work and where they don't.

▲

qualeed 8 days ago | parent [-]

I can understand the stance, I'm just saying that it's not something that I would ever describe as "marketable".

No one is saying "I've never used a gun" or "I've never pirated a movie" on their resume to market their morals. Resumes are to market the skills you have that match the job you're applying for, not for marketing your moral stance.

▲

mattl 8 days ago | parent [-]

A while ago I had to hire people who'd never used Flash (and therefore agreed to the EULA of Flash Player) for a project.

▲

qualeed 8 days ago | parent [-]

That's certainly interesting!

But I doubt those people put "never used Flash" on their general resume (or literally any other resume except the one tailored to that position, if they even put it on the resume instead of their cover letter). I also doubt they thought of it as a "marketable skill" considering it was applicable to ~1 job.

In any case, this seems like an incredibly niche situation that probably has no business being extrapolated to all AI tools.

	▲	mattl 8 days ago \| parent [-]
		There are plenty of cleanroom-type jobs for developers, they just might not always be the sexy big companies offering them.