Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Honestly I used to cowboy code and figure it out as I went, but I've found that the more I diagram the less headaches I have later. It's much easier to change the arrows on a diagram / shift things around visually than rewrite sections of my app. And if you use a diagramming system like the C4 model, the code will practically write itself. You can start at the highest level and be abstract, and slowly get more and more refined in each level until you're practically stubbing out mock function calls.
I use a RDD approach - README Driven Development. (I think some would call this Documentation Driven Development [https://gist.github.com/zsup/9434452], but its way more simplified, in order to get started quicker.) I like to use a good template so I can track my progress. As more features are added, the template gets more filled in. And tbh, i get a bit more driven when i see more and more of the template filled in with screenshots, logos, guides, etc. A good template for me is https://github.com/othneildrew/Best-README-Template.