[memoriuaysj]

before coding I just ask the model "what are the best practices in this industry to solve this problem? what tools/libraries/approaches people use?

after coding I ask it "review the code, do you see any for which there are common libraries implementing it? are there ways to make it more idiomatic?"

you can also ask it "this is an idea on how to solve it that somebody told me, what do you think about it, are there better ways?"

[hansmayer]

> before coding I just ask the model "what are the best practices in this industry to solve this problem? what tools/libraries/approaches people use?

Just for the fun of it, and so you lose your "virginity" so to speak, next time when the magic machine gives you the answer about "what it thinks", tell it its wrong in a strict language and scold it for misleading you. Tell it to give you the "real" best practices instead of what it spat out. Then sit back and marvel at the machine saying you were right and that it had mislead you. Producing a completely, somewhat, or slightly different answer (you never know what you get on the slot machine).

[manmal]

Both the before and after are better done manually. What you are describing is fine for the heck of it (I‘ve vibe coded a whisper related rust port today without having any actual rust skills), but I’d never use fully vibed software in production. That’s irresponsible in multiple ways.

[skydhash]

Do you also light candles and chant?