4 ms·
I think it depends on what intuitions you start out with. If you teach yourself programming as a kid like I have, and get to know about object-oriented program
by miki123211 2y ago
I think it depends on what intuitions you start out with.
If you teach yourself programming as a kid like I have, and get to know about object-oriented programming very early on, normalization is more intuitive. "of course the addresses go in a separate table from the users, just as you'd have an `address` object instead of just putting all the fields inside `User`."
If you start out using Excel a lot, and learn programming much later, the Excel way probably seems right at first. "Of course there's going to be a table with customer information, one row per customer, with separate fields for street, city, zipcode etc."
- somethingsome 2y agoYou are right, now that I think about it, I was using php prior to their implementation of object oriented. So I had no objects, the users were entities in my head, I had to keep track of their data, so a multi column entry in a database made totally sense to me at the time.
- petalmind 2y agoAhh true, object oriented approach certainly helps making sense, and I assumed it by default. I'll think about that.
- Ekaros 2y agoAlso not stopping to think of further scenarios like shipping addresses. Like what if customer wants to store multiple addresses for shipping. How many of those they need? Is 10 enough? Do I now need street1 through street10?