A place for developers to talk about building on Farcaster.

/dev

Typical with "Vibe Coding" and any dev is probably guilty of

We create programs in a day, but products can't be created in one day. It requires a lot more than that. Distribution, error handling, making sure it works on most devices, branding, UX, etc.

Have you went beyond vibe coding and created a product beyond a simple program?

Typical with "Vibe Coding" and any dev is probably guilty of

We create programs in a day, but products can't be created in one day. It requires a lot more than that. Distribution, error handling, making sure it works on most devices, branding, UX, etc.

Have you went beyond vibe coding and created a product beyond a simple program?

https://dylanbeattie.net/2025/04/11/the-problem-with-vibe-coding.html?utm_source=tldrwebdev

Building /moxito 🍃for health, mindfulness, fitness, @tipothehat for funding bangers ~ Full-stack mobile dev (iOS, React Native, AWS), parent, musician 🎹

I agree with you. It helps a lot up to a point and in the end we need a team of people to make it easier, maintainable and fun too

Vibe Coding can do those things that the dev knows better and faster. But sometimes in the projects there's a need for the dev to learn about new things and scout for new tech and information. Most of the time that vibe coding goes wrong is because the dev wants to do too many things that they cannot fathom even in 100 years.

Yeah, totally true. Vibe coding is fun, but turning that into a real product takes way more work—testing, design, user feedback, fixing edge cases, and actually getting people to use it. I’ve pushed a few things beyond just code—turned them into actual tools people use. It’s a whole different level.