Link tags: django

3

sparkline

Let’s talk about usernames

This post goes into specifics on Django, but the broader points apply no matter what your tech stack. I’m relieved to find out that The Session is using the tripartite identity pattern (although Huffduffer, alas, isn’t):

What we really want in terms of identifying users is some combination of:

  1. System-level identifier, suitable for use as a target of foreign keys in our database
  2. Login identifier, suitable for use in performing a credential check
  3. Public identity, suitable for displaying to other users

Many systems ask the username to fulfill all three of these roles, which is probably wrong.

I’m a designer who learned Django and launched her first webapp in 6 weeks | Limedaring.com

I love hearing stories like this. Anything that breaks down the perceived designer/developer divide is a good thing, in my opinion.

Morethanseven » Why the webstandards world appears to be choosing Django

Gareth tries to figure out why Django seems to strike a chord with standardistas. It may that the separation of concerns resonates with the methodology of progressive enhancement. Some good comments follow