man idk vibecoding is such a rollercoaster. yesterday:
- it recreated most of my project from scratch with a proper architecture, in a way that allowed proper testing and pretty much fixed all business logic bugs (yay)
- but then when i asked it to reskin it to old ui, it introduced so many bugs
this is interesting because i simultaneously see how vibe coding entire apps can be incredibly fast (i've already recreated a fat chunk of what i was working on in short time) but also it's not the kind of workflow today's vibe coding tools are following
RE:
i'm really enjoying working with React Router Data mode (for quick prototyping) but i miss true RSC. however, i also don't want to introduce an actual server (yet)
what i really want is for React Router RSC to have a mode where the "server" part runs on the client. like SPA mode
realized i made a mistake with claude iterating on a realistic app ui. it is MUCH more effective to:
- start with data model
- generate mocks for it
- generate in-memory PDS mock
- generate routes and static wireframe uis
- generate loaders and mutations that ui needs
then iterate on everything
