Four short links: 2 March 2011
Python Unicode, Cognitive Enhancement, Journal Balk, Engineering SaaS
- Unicode in Python, Completely Demystified — a good introduction to Unicode in Python, which helped me with some code. (via Hacker News)
- A Ban on Brain-Boosting Drugs (Chronicle of Higher Education) — Simply calling the use of study drugs “unfair” tells us nothing about why colleges should ban them. If such drugs really do improve academic performance among healthy students (and the evidence is scant), shouldn’t colleges put them in the drinking water instead? After all, it would be unfair to permit wealthy students to use them if less privileged students can’t afford them. As we start to hack our bodies and minds, we’ll face more questions about legitimacy and ethics of those actions. Not, of course, about using coffee and Coca-Cola, ubiquitous performance-enhancing stimulants that are mysteriously absent from bans and prohibitions.
- Copywrongs — Matt Blaze spits the dummy on IEEE and ACM copyright policies. In particular, the IEEE is explicitly preventing authors from distributing copies of the final paper. We write scientific papers first and last because we want them read. When papers were disseminated solely in print form it might have been reasonable to expect authors to donate the copyright in exchange for production and distribution. Today, of course, this model seems, at best, quaintly out of touch with the needs of researchers and academics who no longer desire or tolerate the delay and expense of seeking out printed copies of far-flung documents. We expect to find on it on the open web, and not hidden behind a paywall, either.
- On the Engineering of SaaS — An upgrade process, for example, is an entirely different beast. Making it robust and repeatable is far less important than making it quick and reversible. This is because the upgrade only every happens once: on your install. Also, it only ever has to work right in one, exact variant of the environment: yours. And while typical customers of software can schedule an outage to perform an upgrade, scheduling downtime in SaaS is nearly impossible. So, you must be able to deploy new releases quickly, if not entirely seamlessly — and in the event of failure, rollback just as rapidly.