About Me

PBX I'm Paul Bissex, and e-scribe.com is my consulting business. I build web applications using open source software, especially Django. 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.

Book

I'm co-author of "Python Web Development with Django", an excellent guide to my favorite web framework. Published by Addison-Wesley, it is available from Amazon and your favorite technical bookstore as well.

Colophon

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.

Pile o'Tags

Stuff I Use

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

Spam Report

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

Racebike building and software engineering

I just came across this list in an old "should blog about this someday" file. It's from a 1983 interview of legendary racing motorcycle tuner Rob Muzzy, speaking to legendary motorcycle journalist Kevin Cameron. It's about how to be smart about going fast.

I don't do a lot of work that's extremely performance-critical, but most of what Muzzy says rings true for me when applied to software systems. The engineering mindset looks remarkably similar across disciplines.

Maybe if I wrote a paragraph attached to each bullet point, explaining everything, making the parallels painfully explicit, this could turn into a boring magazine article (or at least get on the front page of Reddit). I'll spare you -- the unadorned list really speaks for itself.

Rob Muzzy's Ten Commandments of Racebike Building

Analyze the work to be done -- reliability first, performance second.
Work on jobs that pay off quickly. Don't pin down talented people on low-yield projects.
Keep away from the dyno and the flowbench unless you know what you want and why you need it.
Run combinations that work together. An engine is a system, not a parts list.
In a system of parts that must work together, choose the cheap parts to complement the expensive ones.
If there are two good ways to do a job, one simple, the other complicated, use the simple way.
Use everything you know in your work, even if it seems irrelevant.
Do everything you can in your own shop.
Have enough of the things you know you'll need.
Big numbers on the dyno are no substitute for races won.

Thursday, March 6th, 2008
engineering + programming + tips
2 comments

Some related posts: Aesthetics and computation • From PHP to Python • Understanding tuples vs. lists in Python • A MAC address regex • The twenty-minute trouble ticket system • Tim Bray: "No New XML Languages" • How to use vim, really • You really should learn regular expressions • Quick, but not dirty, PHP

• Comment from stephan , later that day

Interesting to think about how these ten commandments apply to software engineering. My favorite is #6, which I should keep in mind more often ;-) There's nothing worse than wasting even a few hours if you were able to do it in minutes! How do you think #7 applies?

• Comment from Paul , later that day

I fiind #7 one of the harder ones to parse; it reads almost as a paradox. I take it as a maxim on quality: Resist the urge to threat things as throwaways. But I might be stretching it there...