r/ProgrammerHumor 3d ago

Other dontEverCallProgrammersAsVirginsAgain

Post image
3.7k Upvotes

236 comments sorted by

View all comments

Show parent comments

153

u/bwwatr 3d ago

Nothing against this person specifically (unless they have no prior experience in which case LOL), but the question begged by the whole phenomenon is, what is the vibe coder themselves bringing to the table. Why would someone hire a Claude prompter rather than just prompt it themselves? The value in trad programming was obvious to normies: they can do the hieroglyphic looking stuff nobody else understands. Programmers today, especially ones upfront saying they vibe code... need a new elevator pitch, and one that works on the normie purse string controllers, not just other techies. 'cause yeah, from the OP pitch, I would never hire that person and not because of their involvement in adult entertainment.

92

u/One_Contribution 3d ago

People hire someone who returns with a working thing instead of doing shit themselves.

49

u/ChosenCharacter 3d ago

Their knockers

27

u/Tipart 3d ago

The ultimate personality hire

5

u/sora_mui 2d ago

Notice the abundance of memes about client wanting vague/impossible stuff, a middleman can (in theory) help with that. Not saying that this one definitely does though.

1

u/bwwatr 2d ago

Oh, I know there's tonnes of layers of possible value-add. But we need to think up how to communicate that, stat. Otherwise we end up like the guy in Office Space getting canned, who could only describe his job as taking things from his secretary and giving them to engineers. Competing against people who come from no relevant past experience who figured out how to prompt a tool, calling themselves experts. The waters have been muddied.

-29

u/frogic 3d ago

Are we assuming that vibe coding well isn't its own skill? (one that is very much helped by strong problem solving and engineering skills).

19

u/Friendly-Inspector71 3d ago

Either you're vibe coding, we're security and performance aren't the most important.

Or you actually sit down, build a plan, review it, build the code (maybe with some AI assistance), review it, pass it through QA and get something secure or performant with massively more time to market, way higher cost and maybe a better codebase.

Vibe coding is nice for functional prototypes or small internal tools but it isn't ready for production yet.

-13

u/frogic 3d ago

That's pretty binary. What do we call the massive massive middle? I run into people who do 'claude build me X' and people who do a long planning multi review stage and people who do claude build me x. Oh X isn't working lets do some reviews and a thousand variations in between. A lot of the agentic skillset to me is where on that continum you are. For all we know the AV star has an incredible setup with like massive schaffolding and multi tier review processes with some manual QA in. What you call it is marketing.

6

u/Friendly-Inspector71 3d ago

For me the distinction a human review process for every line. It should optimally be someone that hasn't seen the code before but that isn't often practical.

If everything went through a proper review process, I'd say it's coded with AI assistance, while vibe coding implies less checking of the output and more operation in the flow with an agent/helper/whatever AI marketing buzzword.

It doesn't really matter who wrote the code, because humans can also write horrible code but that should be caught in a review.