Quick share: I got tired of bouncing between 10 different sites every time I needed a simple arrow or calendar icon. Felt like such a dumb waste of time.
Is anyone else here documenting their vibecoding journeys from ideation to launch? I'm especially interested in process & workflow description, pivots & fails, and lessons learned.
There s just something magical about bots no UI, no App Store bullshit, no onboarding friction. Just clean logic, instant results, and users who actually use the damn thing.
I ve been coding little bots for fun for a while now, and recently I turned that into a real project Zapis BOT.
It s a Telegram bot for booking appointments aimed at solo pros like barbers, lash techs, nail artists, massage therapists, etc.
Is it crazy to use Windsurf and Cursor both together?
drag tabs between both IDEs
use the same workspace
use all the AI models
There seems to be no moat for AI IDEs, for me it's not a problem though! I've recently been convinced to give Windsurf another go, but keeping Cursor open too like that:
Since late 2023, I ve posted over dozens of bite-sized Cursor coding posts on Reddit some gloriously bug-ridden, some surprisingly useful. The motivation? I wanted to prove (mostly to myself) that I could build small features people actually care about, and maybe make some friends along the way.
Vibecoding matters because it encourages coders to think outside the box. It challenges the norm of purely functional, cookie-cutter websites and apps. It's about bringing soul to the screen and taking digital experiences beyond utility, creating something that resonates with users on a deeper level.
