Martijn FaassenFeb 19

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.

Show threadBram

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.”

Feb 19 at 10:40amWeb