Content pfp
Content
@
1 reply
0 recast
2 reactions

Hirugohan pfp
Hirugohan
@hirugohan
I am not fan of vibe coding, I tried because a friend won a hackathon through fully vibe coding and we teamed up later. He taught me the hardship of vibe coding, and its tradeoff of shipping multiple features within days. I tried, I am not fond of it, maybe because I have the heart of software engineering who enjoy the process. But I've been rethinking about this, I thought that, maybe I don't have to delegate 100% all the coding works to AI. Maybe I just need to delegate the process that I don't like, which is bootstrapping the UI rather than improving the UX which I could do it myself. Since I've been using AI to brainstorm products etc. Maybe it's the time to embrace the vibe coding again, delegating the part that I want to delegate, not everything. gm founders, happy Monday
1 reply
0 recast
2 reactions

JAstra pfp
JAstra
@jastra
I vibe code a lot as a product person. Makes product prototyping so much easier than creating wireframes, mockups, user stories, requirements doc and going back and forth with the devs. That said, I'd still delegate actual development to devs so everyone can work within areas of their expertise (using respective AI tools), leaving vibe coding tool to do the tedious parts e.g. generating content, icons, UI/UX brainstorm, etc. Vibe coded systems are still clunky and difficult to maintain atm. So for sure won't 100% rely on these tools.
1 reply
0 recast
1 reaction