Apr-23-2018, 09:52 PM
I come from a background in database development (primarily SQL Server and MS Access) and while I have a basic grasp of Python and JavaScript, I've found it a bit difficult to transition more towards web/full stack development.
I think about applications very much in terms of a normalized relational database (I conceptualized tables, columns, PK/fK relationships). A user interface/forms are then created to interact with that database.
However, most of the online learning geared towards web applications (that I've found) take a very different approach in that an object model is created first and then the database is created based off of it. This "code first" approach has proven a challenge to wrap my head around as I've always taken the "database first" approach.
Is there a reason one approach is used/preferred over the other?
What are some good resources that would help me grasp the relationship between the database and object model when the object model is developed first?
My stronger suit is absolutely on the database side (thinking in tables, views, queries), but I'm really trying to strengthen my understanding of OOP, interfaces & abstract classes. Roughly 80% of my coding experience is based on event-driven VB6 and VBA, while the rest is a mix of basic HTML, CSS, and JS. Any wisdom or guidance you may provide to ease my path is greatly appreciated.
I think about applications very much in terms of a normalized relational database (I conceptualized tables, columns, PK/fK relationships). A user interface/forms are then created to interact with that database.
However, most of the online learning geared towards web applications (that I've found) take a very different approach in that an object model is created first and then the database is created based off of it. This "code first" approach has proven a challenge to wrap my head around as I've always taken the "database first" approach.
Is there a reason one approach is used/preferred over the other?
What are some good resources that would help me grasp the relationship between the database and object model when the object model is developed first?
My stronger suit is absolutely on the database side (thinking in tables, views, queries), but I'm really trying to strengthen my understanding of OOP, interfaces & abstract classes. Roughly 80% of my coding experience is based on event-driven VB6 and VBA, while the rest is a mix of basic HTML, CSS, and JS. Any wisdom or guidance you may provide to ease my path is greatly appreciated.