Up to this point, most of my living has been made with computers. It seems a natural fit with my skills, and when times are good it pays the bills pretty well. But all too often it's just business. People with money making more money. Too often I feel reduced to a cog in the machine, enhancing nothing but the company's bottom line. In contrast, the last really good gig I had was making software that helped engineers determine how much steel was necessary to reinforce a building during a sizable earthquake; buildings designed with our system survived the Northridge quake in 1994 and very likely saved hundreds of lives. Yes, of course I want to make enough money that my family is comfortable. Of course I'd like to be able to afford a home, and to educate any children I might have. But I don't need to be rich; let me support my family and have a positive effect on people's lives, and I'm a happy man.
Where do you go when you care about saving lives but don't care much about money? Non-profit work, of course. Non-profit technology workers are in as short supply as teachers in this county, and that's saying something. There are wonderful people working in both fields, but they have an incredibly difficult job to do, with very few resources. Ever notice how Microsoft routinely donates software 'valued at' huge amounts of dollars as evidence of Mr. Gates's philanthropy? Quick quiz: If I donate 2,000 copies of Microsoft Windows and Office to your kids' school system or the humanitarian organization where you work, and the programs retail for $495 a seat, but cost me $5 each to make (the research and development costs being already sunk and budgeted for my multi-billion dollar business), did I really just make a donation valued at the equivalent of $1 million, as will surely be reported in the papers
, or did I simply guarantee myself a revenue stream of four hundred thousand dollars (that's money from you to me, of course, and now it's money that you can't use to buy books for the kids, feed the hungry or protect battered women) when the software 'needs to be upgraded' in two years for $200/seat? (What a deal you're getting, that's more than half off the retail price!) Not bad for a $10K investment.
And where do you go if you care about making useful software but don't care much about money? Perhaps you've heard of a little fad called open source
. (If you know and love a socially-minded techie, you may have also heard the term free software
, usually accompanied by an explanation of the form "free as in speech, not free as in beer.") A bunch of freaky-idealist, not-terribly-socially-brainwashed
geeks decided that computer programs were meant to be shared and studied, like literature or traditional scientific inquiry. So they invented something called copyleft
, which basically says: I share my work with you, you share any improvements you make on my work with whoever asks you for them, and you get them to agree to do the same with their improvement on your work. Copyleft is not, as might be assumed, the opposite of copyright. It is rather a use of copyright to ensure that future generations are able to study the work, build on it, and pass on their improvements to it.
You'd think this would be a natural fit with people who want to save lives but don't have a lot of money to spend, wouldn't you? After all, a homeless shelter in Detroit needs e-mail
, and web access
for its clients so they can apply for jobs and public services online in the same way as a homeless shelter in San Francisco does. A food bank in Dallas needs to track and manage which restaurants and grocery stores can do donations on which days
just the same way a food bank in Portland does. A human rights organization in Jordan needs the same kind of secure, distributed, portable method of reporting on human rights abuses
as one in Kosovo.
The software doesn't even need to be developed, in these cases. It's already out there, at the end of those links, ready to be downloaded and installed, free of charge. So what's the problem? Tomorrow I'll write about some of the obstacles in the way of wide use of copylefted software by non-profits.(This is a series I'm thinking of promoting to places like the Non-Profit Open Source Initiative, as well as the Non-Profit Technology Enterprise Network and TechSoup, a service of CompuMentor. Comments and suggestions gleefully encouraged; I'd like to make this series as tight and well-crafted as I can before I pitch it to them. More pairs of eyes can only help.)