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
) used for prototyping. claude is pretty good at generating those, and it's way easier to iterate on the UI and the model without worrying about actual network
if i want to associate some data with some other record, what's the play?
1. using (did,rkey) as my rkey, somehow escaping it. this guarantees there's 1:1 mapping
2. tid as rkey, but content includes a link to primary record. the convention would be "most recent match"
is there an atproto record etiquette? e.g. is it better to do cascading deletes (when there's two types of entities and one depends on another), or is it better to just leave orphaned records (and ignore them on app view level)
