Convex Guide Feedback
one of the things we're starting to work on is a big, practical guide to solving real world problems in convex. we're going to publish it to docs.convex.dev. would love feedback on it
5 Replies
this is based on a lot, lot of conversations and build outs with real users. Taking ideas from discord, from stack.convex.dev, from support threads, customer calls, architecture reviews... and distilling them all down to a first set of best practices we recommend everyone use when they're getting started
it's also based on a lot of mistakes, to be honest. places where customers got in trouble with one thing or another, and we learned we needed a better approach or more guidance to keep everyone on the happy path
This is amazing, thank you so much
Whats the estimate time to completion 😅 ?
Looks awesome! In section 3, it would be nice to define what a an “early”, “later”, and “huge” codebase looks like
this is awesome and I can't wait to read it!
I spent days experimenting with different patterns until I ultimately decided that it would be safer (since my schema is quite large) to overengineer it a little and go for repository pattern. At the time I wish there were some guides based on real world practice for non-trivial codebase
so my feedback is that I wish there were official conventions for project, folder, file, and function naming, as well as overall structure. I’d also like to understand the common pain points in large organizations and the effective patterns used at scale.
having clear conventions also make it easier to collaborate on projects. for example, I know where to find and put stuff in inside a phoenix or laravel projects (at least roughly)