@emirayaz This is great advice, letting the client shape the direction of the project at the start is helpful for getting to the point where both you and the client are really happy with the result at the end
@alessiapacca Thereโs too many stories! Iโm glad future generations wonโt have to debug a program for hours only to find out it was a missing semicolon the entire time haha
@shirshakchavan Iโd build in public early, but only share what Iโm learning as I ship. Keep the half-finished product quiet until itโs ready. That way the process stays honest and the launch is done the right way
Agent instructions age like code. Every model upgrade is a reason to delete rules that were compensating for an older model.
If a skill only applies to migrations, say that. If a doc only matters during deployment, load it then. Less context can be better context.
This has changed how I maintain my own setup and develop with new models going forward.
https://t.co/oFTvxyFqsO
The easiest billing setup is usually the one that reuses the identity model you already have. If your auth already knows the user and organization, billing should map plans and feature access to those same records. Thereโs less glue code and fewer IDs to keep in sync.
@clerk has been a lifesaver because auth, organizations, plans, and feature access all share the same context.
@ZinoLang@thsottiaux Awesome! A short reason next to each proposed change would help to make it easier to tell which rules are outdated and which ones are still there for a reason