Different Vibes
Different Vibes
Different Vibes
So no joke, vibe coding has other real world equivalents.
I always struggled to explain how my ex cooked because it was always a toss up if it ended well, but she was definitely a "vibe cook."
Recipe calls for searing? Fry it on a pan, flip it over fry it on the other side until cooked all the way through. Recipe calls for cream of potato? Cream of celery is fine. The only seasoning is pepper and salt? Eh, can't hurt to use mixed seasoning salt used for burgers. Saute? Nah, just throw it in a pan.
Braised? Broiled? It's cooked.
Ribs call for 18 hours on Low heat? 4 hours on high will do it.
Vibe coding is a way to generate crap for people who are crap at coding and for users that are used to crap.
I mean, some of those things are just because online recipes are usually shit. You can pretty much always use a spice blend instead of salt and pepper, you can always add Chile powder at any concentration you desire, and you should always double the garlic (at least). Granted, some of this is because most recipes are written by AI nowadays.
Vibe-reaping what you vibe-sow
I have a friend who is trying to vibe code a unity project. I don't have high hopes for him, but I'm doing my best to support him and help him out.
I mean if he's genuinely interested in learning Unity and just using AI to help with learning that's good, but yeah if he's just making the AI do all the work and relying on it then yeah probably not gonna go good.
Don’t. Let him drown. Bring the popcorn.
As long as you can keep the vibe coded pieces tiny and modular you’d probably be fine. But that takes a robust knowledge of Unity and gamedev architecture, and at that point you should probably just write it yourself.
Complex, math-heavy stuff like gaming usually is too much for an AI. It’s better at like, basic Python scripts or writing a bunch of dirty CSS.
It can help out a lot in writing base systems. I wanted to learn rust and made gpt write a game with me, it really could handle more complex things than I thought. For example it wrote a diablo style rotatable inventory system (cli, no graphic) which impressed me a lot.
Another game prototype i had lying around in react i asked Jules to refactor to use event sourcing rather than mutating values and I only had to give it a few pointers on what it had missed. It even found an old bug I had missed.
I guess nothing of it was really math heavy but that inventory grid was really solid
I don't think he's gonna need much math. He will need complicated editor things set up though, and I'm doubtful that the AI will understand much.
So my backyard is a utilities easement and it pretty much looks like this.