I'm Paul Bissex, and e-scribe.com is my consulting business. I build web applications using open source software, especially Django. I teach photographers web design and professional skills. In the '90s I did graphic design for newspapers and magazines. Then I wrote technology commentary and reviews for Wired, Salon.com, Chicago Tribune, and lots of little places you've never heard of. Feel free to email me.
I'm co-author of "Python Web Development with Django", an excellent guide to my favorite web framework. Its strong points include an introduction to Python, and better coverage of Django 1.0 than nearly anybody else. Published by Addison-Wesley, it is available from Amazon and your favorite technical bookstore as well.
Built using Django, served by Apache and mod_wsgi. The database is SQLite. The operating system is FreeBSD, on a VPS hosted at Johncompanies.com. Comment-spam protection by Akismet. Vintage topo imagery from the Maptech archive. The markup engine is Markdown.
Akismet, del.icio.us, Django, dpaste.com, Emacs, FreeBSD, Freenode, jQuery, LaunchBar, MacPorts, Markdown, Mercurial, OS X, Postfix, Python, SQLite, Subversion, TextMate, Trac, Ubuntu Linux, wmii
At least 67592 pieces of comment spam killed since January 2008, mostly via Akismet.
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!"
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.
Thanks for reading! Please note: Your comment will not appear until approved, which may take a few hours or more. Spammers will be torpedoed.
Branching and merging in real life
7 comments
Summer Spam
1 comment
SPF-enabled spam domains
1 comment
Chess via iPod
2 comments
Aesthetics and computation
2 comments
Brett Spurrier
Software for determining image similarity?
24 days ago
nizamfarooq
eBay, fraud, filtering, and Web 2.0
60 days ago
Derek
World's ugliest Django app
91 days ago
sagar
Sort tables with sorttable.js
110 days ago
Paintball Kolbudy
Summer Spam
117 days ago
Copyright 2010
by Paul Bissex
and E-Scribe New Media
"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.