Close but it's more extreme vibe coding is putting all ingredients into shit hole mixing them up, drinking all and smiling. Just like advertising.

That's unfair to microwaves.

Man, don't you be dragging down microwave cookery like that. People who depend on LLMs are not like people who cook with the microwave; they're more like people who don't know how to cook, refuse to learn, eat takeout for every single meal, and still demand you address them as "chef".

And now I'm going to talk about microwave cookery.

I think people who object to microwave cooking and see it as 'lesser' are either snobs, or people who have never used anything less than 100% power and get food that's both scalding hot and still frozen.

If you're in the second camp, try cooking for twice as long at 50% power. For most foods you'll get an even heat well beyond anything a convection oven could manage. In some dishes the unevenness (e.g. crisping) is desirable, but in most it's not.

Does anyone here actually cook in their microwave? I don't mean reheat things or defrost and heat a pizza pop, but like actually cook something with the varying temperatures and all that shit they can do. Like is anyone making raw meatballs, saucing them and cooking them in the microwave?

I remember my parents cooking onions with butter in the microwave to put on subs, but I've never done anything like that.

Good analogy as most people don't understand how a microwave is working either.

That being said, at least microwaving isn't on fast track to pollute our entire ecosystem so...

Vibe coding is to coding what ordering takeout from a shady ghost kitchen is to cooking

One of my co-workers, maybe oversold his capabilities and experience. That or whoever told me what he was capable of oversold him. Doesn't matter at this point. Not that long ago, he basically was never submitting any merge requests, and when he did there were a ton of issues. Then one week, everything changed. He was writing code and a style that didn't match what he had done the week before, there was an excessive amount of documentation where before there was none. It was co-pilot. He had gotten access to copilot, which we all have. But it was obvious that he's been leaning heavily into it.

And a short-term yeah it looks like he's doing really well. But I fear he's not actually learning anything by doing this. Which means if there's a mistake, for a major change that needs a happen, He's not going to get there on his own. One time he tried to submit a merge request and I was like, there's an obvious flaw here because this could be null and you're not handling that. If the company ever decides that we're not going to use co-pilot anymore, cuz I think we're still on a trial run, He's going to find himself right back where he started. And that's going to hurt his career in the end.

I would say it's more accurate to say that vibe coding is to coding what microwaving a ready meal is to being a restaurant chef.

I only downvoted this because it's an insult to microwave cooking.

don't understand what they've written

Well first of all, they didn't write it.

vibe coding is when you promised your boss a nice steamed ham but you get some burgers from the nearest fast food instead and call it your cooking. and at the end you end up burning your house.