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.
Bitbucket, Debian Linux, Django, Emacs, FreeBSD, Git, jQuery, LaunchBar, macOS, Markdown, Mercurial, Python, S3, SQLite, Sublime Text, xmonad
At least 237132 pieces of comment spam killed since 2008, mostly via Akismet.
A little-known bit of trivia about our book, Python Web Development with Django: we wrote the manuscript in Markdown.
I think it was my idea. One of the major motivations for using a text-based format -- versus the unfortunate de facto standard, Microsoft Word -- was integration with good developer tools and workflow.
Our manuscript and all our project code was in a Subversion repo, so each author always had the latest updates. HTML generated from the Markdown files was great for generating nice printed/printable output too.
We could have used any number of similar formats: Markdown, Textile, reStructuredText. If we did it again we'd probably use reST plus Sphinx. That would grant all the same advantages, plus give us a little more formatting flexibility and tool support.
This workflow enabled certain kinds of programmatic action on our text, notably two things: automated testing of the interactive examples within the text, and automated extraction of example snippets from source code files.
I wrote scripts for each of these tasks. I've cleaned them up a little, to try to make them a little more general-purpose, and published them (with minimal example files) in a bitbucket repo: http://bitbucket.org/pbx/booktools
There's a little documentation in the docstrings of the scripts. Here's the summary:
To test code snippets in the manuscript file: test_snippets.py example/text.txt
To extract code from source files into the manuscript file: try_excerpt.py example/text.txt
Authors, make use of this if you can -- or maybe even better, take inspiration from the idea and implement a system of your own.
It's a good thing, eh? The first time I ran the example tester I found a slew of easy-to-fix errors.
261-character git one-liner of the day
How things get better after you screw up at work
How I became a software engineer, 8-bit version
My 100x ROI as accidental domain speculator
Jacinto
Neo4J and Graph Databases
792 days ago
ANOTHER SPAMMER WITH BROKEN SOFTWARE
How to install the open source application Darktable on OS X
1797 days ago
SPAMMER WHOSE COMMENT GENERATOR IS BROKEN
How to install the open source application Darktable on OS X
1808 days ago
Alfred Nutile
Switching from OS X to Ubuntu
1849 days ago
Spammer
The story of dpaste.com 2.0
2027 days ago
Copyright 2019
by Paul Bissex
and E-Scribe New Media
Very cool. I've been doing the same thing with reST (generating pdf, docs and presos) and having all the code tested. How many people have coverage reports for their docs?