E-Scribe : a programmer’s blog

About Me

PBX I'm Paul Bissex. I build web applications using open source software, especially Django. Started my career doing graphic design for newspapers and magazines in the '90s. Then wrote tech commentary and reviews for Wired, Salon, Chicago Tribune, and others you never heard of. Then I built operations software at a photography school. Then I helped big media serve 40 million pages a day. Then I worked on a translation services API doing millions of dollars of business. Now I'm building the core platform of a global startup accelerator. Feel free to email me.


I co-wrote "Python Web Development with Django". It was the first book to cover the long-awaited Django 1.0. Published by Addison-Wesley and still in print!


Built using Django, served with gunicorn and nginx. The database is SQLite. Hosted on a FreeBSD VPS at Johncompanies.com. Comment-spam protection by Akismet.


Pile o'Tags

Stuff I Use

Bitbucket, Debian Linux, Django, Emacs, FreeBSD, Git, jQuery, LaunchBar, macOS, Markdown, Mercurial, Python, S3, SQLite, Sublime Text, xmonad

Spam Report

At least 237138 pieces of comment spam killed since 2008, mostly via Akismet.

Enforcing Style

Browsing some programming blogs this evening I came across Ken Arnold's provocative "Style is Substance" post from October 2004. In it, he argues that coding style variants should be eliminated by including style in the language definition:

...the only way to get from where we are to a place where we stop worrying about style is to enforce it as part of the language.

This isn't that shocking to Python programmers (perhaps that's why he mentions Python twice in his list of "mature" languages?). Python enforces whitespace style. To me this is one of the great joys of working with Python -- my code from two years ago, or somebody else's code in an open-source project I'm looking at, uses exactly the same indentation "conventions" that I do -- because they're not conventions, they're requirements.

After reading Guido's "Stricter Whitespace Enforcement" document last April 1, I thought, "I know this is a joke, but bring it on anyway!"

Sunday, April 30th, 2006

0 comments pending approval
Comment from Bob , 2 days later

"In it, he argues that coding style variants should be eliminated by including style in the language definition:"

Why? There really is NO good reason to do this. In many languages there are already ways to enforce this.

Comment from Paul , 2 days later

Sorry -- I left out the link to the article! It's there now. I think you'll see that his reasons for suggesting it, and for thinking it's good, are pretty clear, though certainly controversial. I think he'd likely say that "ways to enforce" equates to a voluntary system, and if it's voluntary then there will be style wars.

Comments are closed for this post. But I welcome questions/comments via email or Twitter.