Creates drafts of database schema based off the project requirements #2
Conversation
…-- subjected to review
e01159d to
c3db3b8
Compare
…ctive` attribute for tracking job listings
There was a problem hiding this comment.
Wow you're ahead already.
I think to keep things simple we should align with the scope defined in the requirements.
For now let's make a lovable product (beautiful UI, simple process) that's all we need for now.
Doing so will give us the momentum we need to add any enhancements down the line.
Could you please do a simplified version aligned with the MVP's scope ?
Exhaustive information about on the job description, Exhaustive information about the company and simple information about the user (more can be added later inside another entity like profile).
I think this shift is necessary cause as builders, having a product that no one cares about it's more discouraging that closing a skill gap. So keeping things simple will helps us think as a team.
|
Thanks for your feedback @7H3XXX, I will look into this while waiting on what the product design team will come up with and adjust the schema based on the design. In the meantime, the schema is just a rough draft of what the data organization could look like on the backend. |
|
Were you able to review it already ? |
No description provided.