I got a recruiter mail in my inbox that they were looking for a "vibe coding" role as if this was something exciting.

They were looking for an experienced dev who could evaluate code quality of AI output and help juniors learn to evaluate it too. Um, that's actually not vibe coding?

I suspect they had been vibe coding for too long and realized they needed an actual programmer to clean up? Good they had this insight..

I said "no" to the role though. There will be many opportunities of this nature in the future, I suspect.

#programming

P.S. I think using AI for software engineering has many interesting applications. But this "vibe" is interesting. I was going to complain they shouldn't put the tool to use in the job description but then again they always do this with programming languages.

@faassen good job saying no. The better thing, is taking on the rebuild later as a contractor, just like we did when they employed people in other contries for such a cheap rate that those people had no chance of ever building skills + a load of non-working stuff got built that needed replacing.

@64kb I wasn't going to say yes to the type of job even without the "vibe coding" label. I guess it did make it more interesting than the usual "we seen you have experience with Python/JS" that I tend to get.

I've been doing Rust full-time for 4 years now but one gets typecast.

Got the same mail, I reacted with:

“I'm not interested in “vibe” coding.
Yes, I use AI in my work, but I won't let a machine take away the fun parts of my job and leave me with the boring stuff (reviewing).

Besides, I don't trust companies that are switching their entire workflow to AI. Especially when they are fully immersed in the AI ecosystems of American tech companies.

Hard pass on these kinds of assignments.”

@faassen that sounds more like they were looking for a vibe *janitor*. Pretend-Coding sucks and being hired to fix it sucks even more.