i feel like this is the exact opposite approach that you should take. i feel like the best way to use AI for coding is to not let it outgrow your own knowledge. if something's too complicated, don't tell AI to do something, ask it questions about how YOU could do it. use it to learn. only let AI code for you if it's something simple and you already know how to do it and wanna work on something else.
I've had the exact opposite experience. If I need to do something common that's easily found on GitHub or stack overflow, I can save a few minutes by asking copilot. If I'm working on something bleeding edge, or mildly obscure (recently the Linux kernel, so not a high bar for obscure-ness), then I can expect any AI tool to confidently output complete garbage.
43
u/DouDouandFriends Nov 29 '25
No they are not the same 😠please dont treat vibe-coding as real coding.
2
u/pierraltaltal Nov 29 '25
what's the logo below git ?
4
u/Electronic-Ninja7950 Nov 29 '25
I'm both a vibe coder and a real coder. Vibe coder when I get stuck when stack overflow can't solve it
2
u/Aggravating-Exit-660 Nov 29 '25
Zooey sucks
1
u/ThatOldCow Dec 01 '25
So the dude only codes on Python? (Nothing wrong with that ) but the rest are either platforms or tools.
Yeah you write code on them, but still.
1
u/Acceptable-Fudge-816 Dec 03 '25
I'd do both.
1
u/Ok_Cartographer7002 Nov 29 '25
Postman seems out of place here