A human-powered relevance engine for Internet startup news

Here’s a fun experiment in crowdsourcing. I’ve been getting overwhelmed by all the startup news coming out of the many sources tracking the interesting ideas and new companies hunting for Internet gold. Many of these companies are really smart. Many are just, well, gold diggers.


And with so many ways to track new and interesting companies, I’ve lost the ability to identify the difference between companies that are actually attacking a problem that matters and companies that are combining buzzwords in hopes of getting funding or getting acquired or both.

There must be a way to harness the collective insight of people who are close to these companies or the ideas they embody to shed light on what’s what. Maybe there’s a way to do that using Pligg.

While shaking my head in a moment of disappointment and a little bit of jealousy at all the new dotcom millionaires/billionaires, the word “flipbait” crossed my mind. I looked to see if the domain was available, and sure enough it was. So, I grabbed the domain, installed Pligg and there it is.

It should be obvious, but the idea is to let people post news of new Internet startups and let the community decide if something is important or not. If I’m not the only one thinking about this, then I can imagine it becoming a really useful resource for gaining insight into the barage of headlines filling up my feed reader each day.

And if it doesn’t work, I’ll share whatever insight I can glean into why the concept fails. There will hopefully at least be some lessons in this experiment for publishers looking to leverage crowdsourcing in their media mix.

Scaffolding web sites with Ruby on Rails

I started messing around with Ruby on Rails for the first time on Sunday. This was after spending all day Saturday tearing down kitchen cupboards, tiled sinks and entire walls for a friend who is remodeling his house, so I got my fill of building last weekend whether real or virtual.


Photo: bruce grant

Trying to figure out how Ruby on Rails worked, I felt like I was remodeling my brain. It was as if I walked into Ikea with just a basic idea of what I wanted my new kitchen to look like and then walked out with design schematics and new appliances an hour later. I suddenly had confidence that I could create a really nice web site with a lot of functionality that was basically inaccessible to me before because of my limited programming background.

The “Ah hah!” moment came for me when I added two words to one of the scripts: “scaffold mydatabase”. When I refreshed my web site, I was adding, editing and deleting data in my database via a web interface. It all automatically just worked. Then literally 15 minutes later I had 2 databases talking to eachother.

It’s mindblowing how much power this environment gives to people who aren’t true coders.

I have a feeling I’ll get stuck and frustrated with what I’m trying to build. But I’m very hopeful Ruby on Rails will get me closer than I could with open source PHP tools. If nothing else, I’ll get a sense for this new trend.

Programming seems to have about a 3 year fashion cycle that also intersects with influxes of new ideas for web applications and a full cycle of students coming out of university. Now we’re at the early stages of a creative explosion on the Internet enabled by things like Rails, open APIs, storage solutions like S3, and JSON. And you can also wrap an idea in any number of different business models in even less time than it takes to build the product itself.

Maybe instead of LAMP (Linux, Apache, MySQL, PHP), we now have RASH (Rails, APIs, S3, Hosted).

There must be similar reactions to breakthroughs in the construction industry when things like cross-linked polyethylene (PEX) hit the market. Of course, construction suffers from bad naming as much as any other trade. Not everything can be as cool as a sawzall or funny pipe.

Screencasts mature…now with advertising!

I’m liking some of the innovations coming out of IDG’s InfoWorld these days (my old digs). I’m told the podcast advertising is working really well for them, but I’m particularly interested to see that they have begun screencasting in earnest…and it’s sponsored, to boot.

The InfoWorld home page now has the rotating feature box which yesterday included a link to a series of AJAX instructional screencasts. Among several related pieces, Peter Wayner produced a 7 minute instructional screencast on the Yahoo! user interface javascript libraries.

He begins by pointing out which libraries he likes and then proceeds to build a web page that utilizes the code. You can watch the screencaster type out his code and then demonstrate how it works.

Though raw in quality, the content was exactly right. The viewer is able to watch over the shoulder of someone who is at their computer working. It’s the online equivilent of Jacques Pepin…well, the finished product didn’t look all that tasty, but I learned something nonetheless.

Editor Steve Fox describes how screencasts answer the creative writing mantra ‘Show, don’t tell‘:

After all, if you’re reading about how something works, you want to see it in action. That’s where the Web’s presentation capabilities open up stunning possibilities.

Now, here’s the best part of the innovation…it has a video preroll…yes, an ad! A very brief video was baked into the beginning of the episode. Of course, I doubt Microsoft paid for this exposure being that it is so experimental, and they will be unable to measure success through traditional means, as there will be no clicks.

But show me an ad anywhere on the Internet that can capture my undivided attention better than this. And tell me how you could find a more targeted viewer than someone wanting to learn how to accomplish a specific task. It’s the best of both worlds – targeting and brand marketing.

What if this video clip was socializable (is that a word?) and caught fire around the web? InfoWorld should offer the embed script with each screencast so that someone can post it to their blog or their favorite video sharing site. And even better than that, the InfoWorld screencaster should actively post his screencasts to every video sharing site he can find and try to get some comment love from the people he’s connected to out there. Each screencast could live a contagious existence as people socialize it in different ways. InfoWorld already baked in the logo into the video stream, so any loss of control in the distribution is automatically mitigated by guaranteed brand exposure.

I’m sure critics will say that video on the Internet and video ads have been around for a long time, and podcasting already acts this way. I’d argue that this is actually really new.

Not only is the screencast format easier to produce than live action video and more compelling than podcasting, but the instructional nature of it gives the viewer and the screencaster a uniquely engaging relationship. As a result, the advertising in this environment can be much more relevant than your typical preroll video ad on news or entertainment content.

Of course, they can be fun to make, too. I’ll bet the editors are much more excited to narrate a screencast they can edit and produce on their own and distribute through the proven web page and RSS methods than they would be to sit in a mock studio with the marketing team telling them how to look good for the camera. It can’t be fun acting like you’re on TV fully aware that your webcast video audience will be a few hundred people at best after the clip gets posted behind an awkward lead capture wall.

Well done, guys. This is the kind of investment that could kick your online growth path well beyond the revenue tipping point.

Measuring success through innovation

Product roadmaps can often become innovation roadblocks. If the roadmap gets translated into a timeline, then the team is forced into an the awkward position of having expectations against which they can only fail.


Photo: Baron von Flickrhoffen

The time required to meet most project deadlines is usually underestimated. There are ways to fight that like padding estimates and shifting resources, but deadlines are meant to be missed. And there are always new challenges and opportunities that popup midstream that you’ll never be able to predict.

As a result, the team gets rewarded for cutting out work and reducing the scope of a project in order to meet the goal. Hold on. That doesn’t make any sense. People get rewarded for delivering less?

In a discussion about Yahoo!’s tendency to focus on time-driven roadmaps with some colleagues yesterday, one person suggested that Product Managers should be rewarded for the number and quality of the features that make it into production. The roadmap then becomes more like a strategy or possibly just an approach to driving toward a vision.

I really like the idea that innovation is the goal rather than beating the clock. I can imagine the lively discussions happening up and down the management hierarchy, too. How much more interesting would it be watching a weekly report that showed all the cool stuff in development rather than a big timetable of all the projects that are running late?

No doubt it would be a lot more fun to congratulate your staff for the bright ideas that they’ve come up with and delivered rather than for the all-nighter they pulled to push out the same old s*#!t.