🎀 sonya (in theory) 🐰
@sonyasupposedly
seeking expertise on vibe-coding what are your best tips for making the robot make software real good? cc @keccers.eth
9 replies
0 recast
16 reactions
keccers
@keccers.eth
Can I ask, how much experience are you coming to the table with? I would love to make educational content around this and some of my approaches but struggle a bit on where the best step 1 is given the broad range of everyone’s starting points The number one thing I would say is to write out a full spec before you get started. Plan the work, then work the plan The other thing I have found is that fully agentic app dev is not for me I’m not good enough yet. Instead I work directly with an LLM and copy paste into my IDE. This way have a firm handle on what’s going on. No code gets in that I don’t look at first. It makes the app maintainable for me
3 replies
0 recast
9 reactions
🎀 sonya (in theory) 🐰
@sonyasupposedly
the context is that I'm going to write an article about this, I don't actually want to vibe-code anything personally so maybe something useful would be, how much code fluency do you think someone realistically needs to get started? or like, to what degree does the practitioner need to be able to setup a dev environment? what does the dev environment look like for vibe-coding?
1 reply
0 recast
1 reaction
keccers
@keccers.eth
yeah this is THE question 😂 and it rly depends I think on what you are trying to do like you need 0 knowledge to open a Replit acct, use their agent, and have it make you a personal tool I think the calculus changes when you want to make products for others — you’re going to want to maybe customize things, have portability off Replit as you scale, easy to maintain code, etc — and then the knowledge burden starts to increase to having to understand what’s actually going on on some level @jrf would be interested to hear your .02
2 replies
0 recast
2 reactions
