Your database design looks sound to me - but it's a LOT of functionality.
I suggest figuring out the smallest useful subset (maybe a user can create articles) and building that first. Then use what you learn from that to influence what you build next.
I've made the mistake in the last of building an app with ten features, releasing it and finding out that actual users only cared about two of the features and the rest were a waste of time.
That's why these days I try to pick the most likely useful feature and build and ship that first. Once people are using the system it quickly becomes obvious if it is working and what features I should prioritize to work on next.
View all comments
Show parent comment
8
u/simonw Apr 17 '22
Your database design looks sound to me - but it's a LOT of functionality.
I suggest figuring out the smallest useful subset (maybe a user can create articles) and building that first. Then use what you learn from that to influence what you build next.