> Senior engineer looks under the hood, sees 500k lines of incomprehensible spaghetti mess with emoji comments everywhere, runs out the door and never looks back.

Senior engineering _consultant_ looks at those 500k lines of incomprehensible spaghetti mess and sees $$$: months or years of contracts and likely very dysfunctional management that is willing to pay multiple times the cost of full time employees to keep the burn on a non-payroll line and/or keep the “AI first” story rolling on.

> Senior engineering _consultant_ looks at those 500k lines of incomprehensible spaghetti mess and sees $$$: months or years of contracts and likely very dysfunctional management that is willing to pay multiple times the cost of full time employees to keep the burn on a non-payroll line and/or keep the “AI first” story rolling on.

That's not been my experience. Even pre-AI, when I was asked to find a bug in some hacked-together codebase, sticker shock was often the result.

"What do you mean, billing for a week? The guy who created this is an actual software engineer and you're billing just as much as he did!"

I've got a list of small ex-clients who won't get work from me anymore, unless they are happy with "Here's my weekly rate, 1 week minimum".

Hourly rates don't work on a client who considers $200/m to be overpaying for s/ware development services.

If that’s how this works out then perhaps Accenture will be okay after all.

I clean up vibe code as a senior engineer consultant, it's quite lucrative actually. I specifically offer this service because I know how to do it.

This could be a superinteresting field in the future, I guess?

But how do you land contracts? Nobody will post on LinkedIn like "Hiring consultant to cleanup or AI-mess-codebase"? :-D So, nobody will admit that they are in trouble already,so how do you find out?

I've been thinking of jumping into this sooner rather than later because I see this becoming a Thing eventually. Are you enjoying it?

It's fine, I suppose. It's like a puzzle, and you really need to be comfortable with banging your head against a wall trying to make work what is essentially immediately created legacy code by the LLM.

Works it (edit sp: Would it) help if the coders' prompts were available (checked in)?

If code is your documentation I assume it is hard to divine intent?

Prompts wouldn't really help, no. You'll have a high level description based on what you're being hired for then the code tells the story.

Well in 2 years AI will have so advanced that none of this matters.

Are you sure that AI companies will keep the current progress?

No, they're going to stop now, yeah that makes a lot more sense.