Skip to main content

The Software Prosumer

The affects of prosumerism are well documented in the evolving economy of content, but the pattern applies equally well and valuably to software creation.

You are most likely a consumer, and if you're an American you think that is a Really Good Thing, most likely. The producers pushed that, and benefit from it. That is not to say we don't benefit from the relationship. Have you seen the price of tube socks at Wal-Mart? I can live with that.

Nonetheless, someone always has to complain, attack the norm, and think they know better. Anyone betting on the dominate future of the “prosumer” is likely right on that current negativity. We don't just read the news. We filter, amend, and combine it. Every novel today spawns even more words of fan fiction. Slashdot1 would be completely worthless without their prosumer users. The barriers between those who produce and those who consume are blurring and the two are mingling. The party is just getting started.

Prosumerism in Software Development

We already are seeing the affects and benefits of adapting the prosumer identity to software developers. Things like free software and Greasemonkey, which allows anyone with a little JavaScript know-how to alter existing websites, are good examples of the software prosumer. Ideally, the prosumer will consume more than produce, and what is produced can be consumed on the same level by peers. I think we have seen this with Greasemonkey and user scripts. I might not even use Firefox if it were not for the user scripts I employ. Obviously you can't say Firefox is somehow above or better than extensions to it which are more important to the user than the product itself.

There is an obvious lack of interest and motivation to promote the prosumer by software developers. You can attribute that to a subtle fear by developers in providing the users with a way of replacing them. The more development can be done among the users, the less real developers we need. However, we can also realize that the more development can be done among the users, the more can be done for the product by all. The more flexible we make our products, the more work the users will do for us. Prosumer software cultures are also great ways to get free marketing, dedicated users, and to satisfy user needs you could never find time for or even be aware of.

Plugin systems are a great way to encourage prosumerism. Some products are developed almost entirely as extendable frameworks, with all the “real” work done all in plugins. When the traditional producers work in the same environment as their prosumer base, the ability of those prosumers will rise. When the traditional consumers' only path to prosumerism is wrought with difficulty, hackish patching, and little or no producer support, the results do nothing but harm both sides of the equation.

The next time you're doing a project, keep some things in mind. If you need a new component and you could open the plug-in API a little to allow making it an extension, do so. If you can develop in an accessible (not compiled) language, do so. When you have some spare cycles, set up a repository of user contributions. A few small steps can go a long way.

Some examples and references:

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…