The recent discussion of the Hub has gotten me thinking about what it means to be NGE. As a programmer, it is critical to learn where to find things. This ranges from simple queries in Google to finding the correct verbiage for grepping source code. In the wake of "Web 2.0" I started seeing a pattern surrounding these new Web 2.0 as tools. A quick trip to Home Depot will make it clear that no one has made the perfect hammer, hence, Web 2.0 has included quite a few different versions of relatively tradtional web based tools.

What does this mean in light for companies trying to be NGE? Well, it means that you have to cope with the tools. I say cope because they will never be perfect. Software is tough that way. It deals with small charges of voltage being translated millions of times over to produce basic organization of text and images by simply writing code. To the world, the cost is a laptop and person who understands the code.  But the reality is that software takes real deal engineering with a huge lack of constraints. 

I don't know if you folks have heard this before, but a big theme in the Ruby and Rails community is that constraints set you free. Think about great engineering feats. They are surrounded by seemingly insurmountable constraints that happen to be overcome in order to produce an elegant solution. The Golden Gate bridge is one great example. As amazing as the Golden Gate Bridge might be, I really doubt those commuters stuck in traffic every morning continue to be in awe of its engineering prowess after thirty minutes staring at the fog. The fact is anything that gets used is most likely going to small short, even if it is an amazing accomplishment. 

Pulling this back to the idea of NGE, companies should aim to understand the limits of tools. If you consider industries that seem to fail, the biggest problem is a lack of ability to change with the environment. When I lived in State College, PA there was a video tape factory. Needless to say, it closed not long after we arrived. At the other end of the spectrum is Ask.com. A friend of mine worked at Ask (and wrote a few good books) where he said they evaluate their entire technology base every two years. Some might consider this to be extreme, but when you are in business to sell something valuable, you have to take this kind of mentality and make it work. IBM, Sun, Oracle, Google and even Microsoft understand this, even though their success is arguable.

The point here is that as we look at our own tools, we cannot think in terms of the perfect fit. We need to consider what makes them hard to use in light of our own personal limitations. I'm a perfect example when it comes to calendering software. I can't tell you how many times I've tried to use tools to help organize my schedule and todo lists only to fail after a few minutes. Is the problem solely on the software? No, I need to tough it out and try a bit harder at using the tools. Does it mean there is not a problem with the software? Yes, there are always tons of problems with software! 

My intention in mentioning all this in light of recent discussions is not to avoid blame for mistakes or even assign blame at all. Web 2.0 teaches us that being vocal about problems can often result in solutions (think Lazyweb). The real goal is to suggest that NGE is about using many tools and getting the most out each and every one. NGE runs a pretty close parrallel to early adopters on the web. I'd say a hallmark of this mentality is to try things out completely, assume it will not change your world and see what it does change.