I been trying to figure out, what i hoped is a simple problem, but am yet to land with an answer.
How do you go about designing an entity relationship diagram when doing code first development?
The people I've spoken to and things I've seen on google usually refer to the approach of designing for a specific db type (e.g. PostgreSQL, MSSQL, etc.) then working backwards. To me it doesn't make sense doing it this way, as I've always seen code-first design being an essentially a abstraction i.e. you design the pattern, and you let the code figure out the rest, which is the direction I see software engineering going towards faster and faster.
Is there a proper approach to this? If so what is that approach? What is proper approach to code first entity relationship design?