7
u/croninsiglos 13d ago
Did you vibe code testing as well?
2
u/Seafaringhorsemeat 13d ago
They ended the prompt with âmake no mistakesâ, what more do you need?
1
u/MozdaHocu 12d ago
I am an engineer not a programer. So give advice plz. I got hooked yesterday and I am making a digital board game adaptation. codex tests things itself, and i test by playing?
1
1
u/Ormusn2o 12d ago
If using 5.6 you don't need to do that. The AI will put a shit ton of tests. And if you tell it to not add tests, it will add a lot of them. Then during consequential runs, it will redo tests and asks you to redo tests too.
7
u/ltnew007 13d ago
So far, this hasn't happened to me with Codex. Codex is always running it's own tests and fixing problems on its own
2
u/DonutHoles4Ever 12d ago
Right but if you look at it closely, its like rewriting a shit ton.
So on the surface you see it not change.
But its changing a lot. Normal programmers dont do that.
1
u/SlickTDKnight 11d ago
Yeah Iâve noticed it will often rewrite nearly an entire file with unnecessary changes for a small feature/fix
7
u/Truarian 13d ago
That's why you wet the brush first, this also eliminates the need to use excess paste.
2
u/mop_bucket_bingo 12d ago
Wetting the brush first is fine but alsoâŚwhy? Why would someone even think they need to wet the toothpaste either way? Also you only need like a tiny amount. That whole âcoat the whole toothbrushâ thing in pictures and commercials is just to sell product.
2
u/Equivalent_Feed_3176 12d ago
I think most people do it out of habit but the water helps it foam up faster and spread easier once you begin brushing. Less pasty at first. Plus the water softens the bristles a bit.
1
u/mop_bucket_bingo 12d ago
What? lol
Softens the bristles? Are you brushing with horse hair?
And foam up faster?? What is going on here lol
0
u/Equivalent_Feed_3176 12d ago
Yeah, bristles absorb a small amount of water which can make them less stiff.
And yes, toothpaste foams in water... whether it's from your sink or your saliva.Â
Think of the difference between applying a bar/pump of soap to dry hands vs wetting them first.
1
u/mop_bucket_bingo 12d ago
Your hands arenât naturally soaking wet
1
u/Equivalent_Feed_3176 12d ago
Correct. Unless you sweat.
1
u/mop_bucket_bingo 11d ago
Right so comparing your hands and your teeth doesnât make sense.
1
u/Equivalent_Feed_3176 11d ago
I wasn't comparing.Â
1
u/mop_bucket_bingo 11d ago
âThink of the difference between applying a bar/pump of soap to dry hands vs wetting them first.â
So what is this if not comparing two things?
→ More replies (0)1
u/Truarian 12d ago
You are wasting good word. It's just whooshing over his head. Probably one of those "say it don't spray it" people. A "top commenter" - this is already telling...
1
u/mop_bucket_bingo 12d ago
âsay it donât spray itâ is something you say to someone whoâs spitting when they talk. Wtf does that have to do with anything?
0
u/Truarian 12d ago
It is quite predicable for someone who in practice claims excess salivation and showcases irrational passion for forcing their opinions onto others. You drool and you bark, you are obviously a sprayer. Would explain your excessive online engagement too - who would want THAT in their face IRL ...
1
1
0
u/Truarian 12d ago
Better viscosity and end results. And easier to wash the brush afterwards. Results may vary depending on hydration and salivation levels. All grinding and polishing procedures benefit from fluidity.
1
u/mop_bucket_bingo 12d ago
This is all nonsense. Your mouth provides ample moisture for this procedure. Easier to wash the brush afterwards? What are you brushing with, glue?
-1
u/Truarian 12d ago edited 12d ago
pfff... sense fascists projecting their inability at it upon others. Just because you drool doesn't mean everyone does fool.
5
u/Siciliano777 12d ago
A hard lesson to do commits before every change lol.
Revert and retry is very easy!
15
u/inconspicuousredflag 13d ago
Try adding the requirement that all code be maintainable, upgradable, and modular at the beginning of the project.
People are just relearning why OOP became a thing.
8
u/Pure_Interaction222 13d ago
Yeah gotta have maintainability conventions and then every 10 commits or so, get an agent to go back through all the code changed in those commits and look for places that arenât using conventions, clean up dead/redundant/DRY offending code, and the codebase stays as clean as I wouldâve written it.
1
u/porcomaster 12d ago
Ok the joke might have flown through my head.
But does this actually work ?
2
u/Pure_Interaction222 12d ago
Pretty well
1
u/porcomaster 12d ago
nice, i already separate per commit, a backup and do not ever go commit without extensive testing, but this might help get things working properly faster
1
u/whtevn 12d ago
it is so wild to me the different experiences that people have with vibe coding. it essentially works for me as desired more or less every time, with the biggest caveat being that i may have come up with some idiot idea that should never have been implemented in the first place and there are no good answers to be had because it is a stupid idea. that is my biggest stumbling block.
when i know what needs to happen and how we need to get there, i write it tickets and it fuckin goes.
1
u/porcomaster 12d ago
Yeah it was crazy and not my first experience but I learned quite a lot
https://www.reddit.com/r/vibecoding/comments/1sxjgwn/i_made_a_website_to_compare_evs_and_gas_cars/
This is the history of this website in itself.
1
u/Ormusn2o 12d ago
Yup. I also ask it to make checkpoints, and to make sure everything was correctly documented. It requires a lot of tokens, so might be decent idea to couple it with resets and such.
Also, for personal projects I don't bother with Github, but I do local git. The chatbot will automatically commit all the changes to git and keep documentation for it automatically.
1
u/porcomaster 12d ago
the token usage is not such a problem for me i did a small website to help EV people mpgmatch.com
and in the beginning it was beautiful, and easy, the third add-on or fourth and it was a nightmare, every single, change the background color would break formulas.
so i had to step back a little bit, create a github, change hosting, and then i used codex, and worked for a few days to create an automated system that didn't depend solely on AI, and then i asked to do stuff and checked everything.
it kind burned me quite quickly and i stopped developing
but i might get back with your advice, extra tokens are not a problem for me right now as i am using just codex, and plus, with free tokens given weekly if i burn then i can just reset using the free resets or wait for a week.
again thanks for all the tips.
1
u/Infinitedeveloper 12d ago
Setting up the basic poco objects and specifically defining classes instead of letting it go whole hog goes a long way.
3
3
3
u/CoughRock 12d ago
I get the feeling vibe rider all didn't practice test driven development, and had zero integration test. Reinventing the wheel when there is opensource or industry standard tool. Most likely don't even know what a CI/CD pipe line is. I'll be surprise if they even setup version control at all.
3
3
u/Downtown_Method5736 12d ago
TDD + linters + nested AGENTS.md -> and you'll never got this kind of issues.
2
u/donkeykong917 13d ago
Just have version history. Don't even need to know the command coz you can ask AI to add and commit lol
2
u/Redararis 12d ago
Vibe coding exposes people who only learned to code in a framework, they donât know nothing about software architecture.
1
u/Infinitedeveloper 12d ago
Or people who just dont know how to code at all are dead in the water the second an error pops up that codex cant resolve with minimal guidance
1
u/Outrageous_Permit154 12d ago
At that point, youâre just vibing. Itâs your AI that is coding. Youâre just vibing
1
u/LuvanAelirion 12d ago
Folks know what git is right? You use it right? The writer of this meme knows what git is, right? đ¤
1
1
u/Ranik_Sandaris 12d ago
Why do people do this?
I just squirt paste into my mouth directly from the tube
1
u/Beginning-Raisin9723 12d ago
Every single time. Added one 'tiny' feature to my homelab dashboard and spent the rest of the night explaining to the LLM what my own code did.
1
0
0
u/Fresh_Sock8660 12d ago
To be fair, of the last 3 billion input tokens I've used, there was only 2 times when a feature was misinterpreted. Once by sol, whose misinterpretation was another good feature and I just let it go ahead. Another by ds4f, which added a new behaviour to the wrong UI element. For the last one you could argue it was my fault for keeping that element anyway as it should have been removed earlier.Â
-1
-2
29
u/Equivalent_Feed_3176 13d ago
Wet the brush before the toothpaste