Lessons from the Campaign Pressure Cooker
The following article is the text of this week's SuitWatch, Doc's biweekly newsletter about Linux in business.
I've been on a mission lately: to see what IT workers in the pressure-cooker conditions of political campaigns might teach IT professionals everywhere about the resourceful use of Linux, free software and open-source development methods. What works best? What doesn't work at all? How do you develop and apply solutions to problems all over the country with widely varying participants and circumstances? What are the advantages and limits of open-source models? How do you embrace workers and volunteers accustomed to other platforms and methods? And how do you get stuff done when the deadlines are absolute and the costs of failure are extreme?
My plan from the beginning has been to visit or at least talk to the headquarters of leading candidates who were known to be using Linux and other open-source platforms. Notably, those included the Howard Dean and Wesley Clark campaigns, although I've also heard from other campaigns, such as Bush's and Edwards', that they're using plenty of open-source stuff too.
My timeline was on the long side as the final story would run in the June issue of Linux Journal, which has an early March all copy deadline. By that time, the primary season would be well underway and the pressure cookers would be hissing at full volume.
As Burlington, Vermont, is only a few hours' drive from New York City, I decided to hit the Dean campaign first, right before the Iowa caucus primary (this past Monday) and Linux World Expo (this Wednesday-Friday). The timing seemed propitious as well as convenient. Also, the Dean campaign was and still is, by all accounts, successful at pioneering extremely effective use of the Internet--for organization, fundraising and much more.
As a reporter I have to be nonpartisan. Still, it's hard not to like a campaign that liked you before you ever heard of them. That's what happened with the Dean campaign, which is run by Joe Trippi, who used to work for Debian co-founder Ian Murdock. Joe urged the campaign to follow the lead of its own growing constituency and practice what he calls "open-source politics". Many members of the team also are fans of The Cluetrain Manifesto. In fact, one of my Cluetrain co-authors, David Weinberger is the campaign's Senior Internet Advisor. While I was there, volunteer staffer Tom Limoncelli asked me to sign his copy of Cluetrain. Some of you may know Tom as an author of books on network and system administration. He's helping design the system plumbing required to handle a Niagara of incoming e-mail.
During my time with the Dean team, I heard Cluetrain quoted a number of times. There was my "markets are conversations" line and David Weinberger's "hyperlinks subvert hierarchy." But the one that made the most sense for the campaign itself was Chris Locke's "networked markets get smarter faster than most companies". Exactly that principle, they said, applied in electoral politics today. That's why they were building or applying technologies that embraced their own networked markets.
Sitting in the server room, IT Manager Harish Rao waved at racks of machines and said:
Very little in here is not open-source-based. The accounting system runs on Microsoft, for example. And we have a NAS--network attached storage box--that's proprietary but also Linux-based. The back end is completely accessible. We could have built our own box and saved a little bit of money, but I'd rather have my people working on what the box is supposed to do, which is important for backups. It's just an easy file server that we can drop in to some of our field offices. It does NATting, firewall, Postfix, Sendmail, if you want it.
Rao's team is adrenalized to make choices that are pragmatic, resourceful and either inexpensive or free. "We recognize two things in our development here", he says. "One is that pretty much everything we do has been done before, by somebody, somewhere. The other is that we're here because of our supporters." And those supporters help. While the organization is busy developing a voter file system to send out to the field offices, it's also embracing the systems already in use by some of those offices. While I was there I also heard talk about how to open-source some of the team's development work and release it under a Creative Commons license.
The organization also takes advantage of outside commercial products where they make sense as well. Some are open source, such as BestPractical's RT request tracker. Some are not. While I was there, Dave Winer drove up from Boston and installed Channel Dean, "an RSS feed that's like a clipping service for people interested in US politics". It's based on Userland's Manila, a commercial product that runs on OS X and Windows.
"We're very pragmatic", Harish Rao said. "We do what works. You need a balance. I think for most back-end services and infrastructure, open source is the way to go. For the desktop, we believe in choice. Use what you want. Most of the services you're accessing are off the Net anyway. If you're used to Outlook, hey, it does some good things. So we take a practical approach. But we're members of the Open Source community, and that's our context."
So is the pressure-cooker environment. "Everything around here is a scaling issue", Rao said. "Even going to the bathroom. Everything here has to do with scaling. We have to do a really good job of doing a lot with a little, in a quarter of the time. We've been able to do that."
"I believe in three principles", he said. "First I always make sure I hire people I can trust 100%. Second, I always try to hire people who are smarter than I am. Third, I give them the independence to do as they see fit as long as they communicate about it to their other team members. We've had a lot of growing pains, a lot of issues; but we've been able to deal with them because we have a high level of trust, skill and communication."
Of course, a political campaign is a special case, isn't it? They self-select people who are at the high end of the motivational bell curve. No pointy haired bosses or lazy Wally characters from the world of Dilbert. Can you expect the same inside less extreme organizations?
I think so. Most enterprises have at least some high-pressure jobs that require high levels of motivation. The extreme examples forge our ideals. Seems to me that the DFA experience applies.
Doc Searls is Senior Editor of Linux Journal. His monthly column in the magazine is Linux for Suits, and his biweekly newsletter is SuitWatch.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide