Hirugohan
@hirugohan
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
1 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
2 reactions
2 replies
1 recast
5 reactions
0 reply
0 recast
1 reaction
1 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
0 reply
0 recast
1 reaction
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
2 replies
0 recast
0 reaction
0 reply
0 recast
4 reactions
0 reply
0 recast
1 reaction