3 ms·
Straightforward, useful advice. I pretty much do all of these when I start new Django projects. The need for a custom User model makes me a little sad every ti
by davepeck 4y ago
Straightforward, useful advice. I pretty much do all of these when I start new Django projects.
The need for a custom User model makes me a little sad every time because, well, single `name` fields (rather than `first_name`, `last_name`) and email-for-username do feel to me like more sensible defaults circa 2022.
- ethanpil 4y agoI'm curious as to why you think a single name field is better than the traditional separate first and last?
- Daishiman 4y agoPer https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... , names have far too much ambiguity to consider that two fields is necessary or sufficient to encapsulate that information.
- mdisc 4y agoMaybe for consumer apps, but for a lot of enterprise apps that have to be compatible with existing APIs or domain-specific data standard that require two name fields, that’s not really a viable approach.