It will probably surprise you to find out that we actually have no dedicated support personnel inside of New Relic!  Each and every support request is handled by a development engineer who has full access to our entire source base, and the full authority to do whatever is necessary to make things right. This includes agent tweaks, production patches and – on rare occasions when we mess up – free upgrades to RPM Gold.

New Relic is doing development right. Because they have no support staff, their development engineers are supporting the customers. This means that the people designing the software are put right in contact with the people using the software, and thus can easily hear feedback about the product. If a common problem occurs, the engineers know it and can make a change to eliminate it.

We have our engineers take support calls because engineers like to code their way out of the support queue rather than execute manual repetitive tasks. Instead of coming up with one-off workarounds for specific customer issues, our team is more likely to implement solutions that the entire customer base can benefit from. Some of our best product ideas come out of support cases. If we can avoid future support issues by adding a feature or fixing a bug that makes the product easier to install, use, or manage, then everybody wins.

If more companies were able to get this type of information from their support calls to their engineering staff, we’d see an improvement in software. However, this isn’t enough. The reason New Relic is able to encourage engineers to fix the bugs as soon as possible is because every time the engineer needs to respond to a user about an issue, that engineer feels the weight of the issue. The engineers don’t want to respond to a dozen users with the same thing, so it is just easier to code a fix for the issue and not have to worry about it anymore.

Klassio is very focused on content. The home screen prompts a large text box ready for a new post to be entered, or you can also select from one of the other supported media types.
In the future, I would hope to see a lot of polish put into this product. As of now, there are really only 4-5 pages in the entire admin backend. This is fine, for simplicity is very user friendly. However, if there is going to be a minimal amount of feature, each feature needs to flow with the other features. Think of how Apple does their products. They don’t have a lot of features, but the features available are polished and highly usable.

The custom CSS might be a little much for most users. I’d suggest putting in some sort of wizard, similar to how Twitter allows users to style their profile pages, to make it easy for users to change the look of their page without needing to know CSS.

Overall the service is usable, put definitely needs polish.

A Blogging Network

Teens In Tech was first founded as a blogging network. Using WordPress MU, they wanted to create a community for young teens in the tech industry to blog under, similar to the WordPress.com brand. According to Techcrunch, this happened around August of 2008, and, might I add, never caught on.

A Conference

After failing to attract the teen market through the blogosphere, Teens In Tech tried once again in January of 2009 by starting the Teens in Tech Conference. Sponsored by Google and other companies, it supposedly was a huge success. When speaking to a member of Teens In Tech, they said that they believed their conference was such a big success that it was now their main product, and that they were planning on taking the conference audience and expanding that presence into an online community.

A Network

Having at least one victory under their belt, Teens in Tech decided to acquire Youth Bloggers Network. While it was only a very nicely done BuddyPress installation, Youthbloggers.net had 100 members when the deal occurred, and now has 1,000 registered users. However, there has been very little activity on the site for the past month, and it looks like posting has been scattered for the past few months. 2 Strikes, 1 Hit.

So Whats Next?

So, with a successful conference, and two failed communities, Teens In Tech is going for another round at the youth market. What can we expect from them? Well, my guess is not anything interesting. They’ve tried the community gig twice, and both times can’t seem to garner a sustainable audience. And even if they do get an audience, chances are they will have a very hard time monetizing it. Young people tend to be unendingly cheap, mainly because a large majority aren’t controlling their own purse strings.

Maybe they’ll surprise us, but don’t count on it.

While I agree with a lot of this post, there is one clear item that is being misrepresented. The Verified Account System:

At the time of writing, Twitter has verified just 2,808 users – a number that’s probably just a little shy of the bonafide famous people who sign up every month.

Okay, so it’s a big ask. But there are some major, longstanding celebrities, power-users and brands on the network who have never been given the stamp of approval, including @wossy, @glinner, @jimmycarr, @problogger, @copyblogger and @cnnbrk. The latter which, of course, was the #1 most-followed account on the network for the early part of 2009.

The point of the Verified Account System was never to be a famous person list. The original intent was to be a way to make a distinction between a real person and impostors. As far as I know, no one is trying to pretend they are Copyblogger, or Problogger, or CNN Breaking News. All of those people are very well established and most people aren’t going to confuse them with other accounts. So why verify them?

The author further backs up my point by pointing out that Twitter founders don’t have their accounts verified:

To be fair, @biz, @jack and @ev aren’t verified, either, but that just supports my theory that they’re imposters.

This person, and probably many other people, are way off base when it comes to the intent of the Verified Account System. Maybe that is the hole they need to fill?

36 companies have been sued for patent infringement in Marshall, Texas (of course) for supposedly violating a patent (6,018,761) on spam filtering. The companies sued represent a who’s who of corporate America, including Apple, Google, HP, RIM, Citigroup, Capital One, Alcatel Lucent, AIG, AOL, JP Morgan Chase, McAfee, Symantec, Yahoo, IBM and many others.

For some strange reason, I don’t think this lawsuit will be going anywhere.

So I go to the hardware store to buy the tools, and I ask the sales clerk where I can find a hammer.

“A hammer?” he asks. “Nobody really buys hammers anymore. They’re kind of old fashioned.”

Surprised at this development, I ask him why.

“Well, the problem with hammers is that there are so many different kinds. Sledge hammers, claw hammers, ball-peen hammers. What if you bought one kind of hammer and then realized that you needed a different kind of hammer later? You’d have to buy a separate hammer for your next task. As it turns out, most people really want a single hammer that can handle all of the different kinds of hammering tasks you might encounter in your life.”

“Hmmmmmm. Well, I suppose that sounds all right. Can you show me where to find a Universal Hammer.”

“No, we don’t sell those anymore. They’re pretty obsolete.”

If you read through the post, you’ll find that the sales clerk keeps describing more and more products that are designed to make wider variety of tools. First a tool factory that can build all the tools you want, and then a factory to build that factory, and so on and so forth.

While this post is a very humorous, it is a look something that is all too real today. There are so many frameworks out there thats’ purposes are to be a general as possible so as many people as possible can use them. While the post itself is dated (2005), the problem of overgeneralized frameworks are still very much a problem today.

Instead of building a framework that tries to solve every problem in the world, it would be a lot more useful to some people if there was a framework tailored to a specific niche. (Especially if you excelled at that niche)

The fact that Techcrunch has made a campaign against Associated Press, and other delusional companies, is one of the top reasons they are a part of my RSS reader.

This model works well for businesses, but Google is finding out that a lot of people use Google Apps as a personal service. Users with their personal sites use Google Apps to handle their email and other apps. And now, those users are tired of switching back and forth between a regular Google Account, and their Apps account. So, with this merge, they can have their cake and eat it to.

However, this is bad for businesses. More specifically, this is bad for employees. If your company uses Google Apps and you decide you are going to use Google Voice for absolutely everything, your connection with people via telephone is at the mercy of your employer. If they turn off your Google Apps account, you loose your Google Voice number, as well as anything else you put into the system with the Google Apps account.

Note: Google has thought of the Google Voice scenario, and have provided a form to transfer ownership.

I’d be careful about where you put your data. It might come back and bite you in the butt.