After many years working as a chemist and a software engineer, I still have to work hard at adopting, and adapting to, computer based systems. Of course, this can be put down to age (but I've noticed that no one is getting younger), but I still cling to the notion that the systems might be better designed and easier to use. But, hey, that's just me.
I have to admit that my experience in software engineering and product development colors my appreciation of the use of "2.0" as part of a name. And it started with the publication of the magazine Business 2.0 in the 1990's. Maybe it's my own aversion to using version nomenclature as a shorthand name for ideas that actually require explanations. When a software system's version changes from "1.0" to "2.0" that usually means that most of the software is new, the design may be new, and the way the product is used may also be new. And as a definition this fits very well with the summary presented in Tim O'Reilly's September 2005 article "What is Web 2.0: Design Patterns and Business Models for the Next Generation of Software".
However, one problem with tagging "business", "office", "enterprise", and "web" with version numbers is that after a while we actually believe that we are using something new. I do believe that much has changed, but, also, that much remains the same. One of the challenges in actually talking about a 21st century organization is that organizations today are largely made up of people born in the 20th century, and they will remain so for another, say, 15 years. And even more importantly, people born in this century won't be in positions of power in these organizations for another 25 years or more. Furthermore, the technology that we're so keen on using is based on 20th century science, engineering, business, and practice, and this will remain so for some time. So things are new, but maybe not that new.
What stands out for me as the most generative ideas in Tim O'Reilly's article are those dealing with people: participating with the users and harnessing collective intelligence. The bulk of the article is about the technology, and while it's interesting, technology is changing way too fast to really keep up. And that's true for the technologist too. Recently, Nick Carr posted a critique of 2.0 architecture and implementation. I have my own engineering concerns about "The end of the software release cycle". But don't get me wrong; changes are afoot. One day, and maybe quite soon, we will be faced with a computer that has a kind of native machine intelligence. This will be a remarkable, fascinating, and possibly frightening event. And especially so if such a machine has some reliable electro-mechanical connections to an airplane navigation system, or an emergency room ICU system. But until then it looks like I'll be having fun learning to use robotic vacuums. I know I should buy one, but still, I resist ....
So I hope to use this week to look a bit at what we know about people participating and collectively thinking ... what's new, what's borrowed, and what we might look forward to. Maybe we'll get to talk about what our tacit understandings are that both help and hinder our adoptions and adaptations. The other day Jenny blogged about continuous partial attention. Is this a real skill to learn? Do I need it? And if I'm good at that will I still be able to spend five years focusing on a single problem in thermodynamics or mathematics? Can I be a "live node on a network" while I'm sitting for 40 minutes attending to my breathing?
Finally, by way of introduction I'll say that I'm definitely a child (and an adult) from the 20th century. A child, in fact, of the 1960's when I was optimistic and naïve enough to believe that it would be easy to change how the world was and how things were done. Now I'm older and I know that whatever isn't working for us, collectively, today, is going to take some real effort to change. However, I'm an optimist and an empiricist, so I think I'm ready for our experiment in using the world-wide web to do things differently. Whether I am ready or not isn't really important; we're experimenting right now.
- Bill
Recent Comments