I typically don't go past the point of jotting down the structs. If we're just talking about getting ideas out, it only needs to include what's necessary for selling the idea.
Edit: by which I mean a fairly simplified bullet-point list of, say, ThingFoo with attrs fizz, buzz, bar, and baz.
This is a great point. I forgot about this. People who have no background in programming can find it easier to follow along if you just tell them you're gonna have this multiple different black boxes that does a specific thing (different function/methods/classes)
Comments
For UI/UX draw it on paper. Then get inspiration from an expert's work who's design is similar to your drawing on a sites like behance, dribbble, etc.
I use my blog post for my go-to list for prototyping.
[Prototyping](https://medium.com/free-stuff/the-entrepreneurs-list-b53ff53...)
[Look at design resources section](https://medium.com/free-stuff/500-free-things-on-the-interne...)
For data structures, database schema, software dev; MOOCs are your best friend. (MIT,Coursera, etc.)
I've found more formal database schemas are often lost on people that don't work with relational data. Any ideas on how to avoid that?
I typically don't go past the point of jotting down the structs. If we're just talking about getting ideas out, it only needs to include what's necessary for selling the idea.
Edit: by which I mean a fairly simplified bullet-point list of, say, ThingFoo with attrs fizz, buzz, bar, and baz.
This is a great point. I forgot about this. People who have no background in programming can find it easier to follow along if you just tell them you're gonna have this multiple different black boxes that does a specific thing (different function/methods/classes)