General


14
May 10

Mobilicity Launches… on GoDaddy

Mobilicity, a new mobile phone carrier is launching in Canada on May 15th, 2010. Starting in Toronto, then covering other major cities like Vancouver, and Montreal, the service is competitively priced with unlimited plans for calling and text messages at around $35 dollars (CAD) a month, which is pretty sweet.

After seeing some buzz on Twitter about Mobilicity, I went to their website, which was so slow I thought I was on dial-up.

This amateur stuff from a Telecom?
No… It can’t be.

But after seeing a database connection error (This means shit is broken for all your non-techies) I realized something was really up.

Check this out:

# host www.mobilicity.ca
www.mobilicity.ca has address 173.201.38.96
# host 173.201.38.96
96.38.201.173.in-addr.arpa domain name pointer ip-173-201-38-96.ip.secureserver.net.

Huh? Secureserver.net is….

# whois 173.201.38.96
 
OrgName:    GoDaddy.com, Inc.
OrgID:      GODAD
Address:    14455 N Hayden Road
Address:    Suite 226
City:       Scottsdale
StateProv:  AZ
PostalCode: 85260
Country:    US
 
NetRange:   173.201.0.0 - 173.201.255.255
CIDR:       173.201.0.0/16
OriginAS:   AS26496
NetName:    GO-DADDY-SOFTWARE-INC
NetHandle:  NET-173-201-0-0-1
Parent:     NET-173-0-0-0-0
NetType:    Direct Allocation
NameServer: CNS1.SECURESERVER.NET
NameServer: CNS2.SECURESERVER.NET
NameServer: CNS3.SECURESERVER.NET
Comment:    Please send abuse complaints to abuse@godaddy.com
RegDate:    2009-09-18
Updated:    2009-09-18

Its GoDaddy. A telecom that hosts its website on GoDaddy.

Yikes.


2
May 10

This man is my Hero

Yvon Chouinard has got a pretty amazing story. This video is him speaking at UC Santa Barbara about turning Patagonia into a more sustainable business.


30
Apr 10

Clouds and The Fate of the Help Desk

As an efficiency nut there’s one thing that makes me really happy about Tablets:

The Help Desk will be going away.

It’s important to understand the meaning of the term “Help Desk”. I don’t just mean people who sit around all day with headsets, answering phone calls. It turns out there are a *lot* of people employed in IT whose job it is to just keep the lights on. Vendors, Integration specialists, Sysadmins, and the guy whose entire job it is to  click the right button to clear the printer queue. Entire countries have devoted a lot of resources to greasing the gears of computers. They all work in a Helpdesk somehow.

CTO’s and CIO’s are starting to appreciate that their function at a company isn’t about technology implementation – it’s about how technology can help their business. Who cares if your OS is running Windows or Linux if all you need is a Word processor (and Solitaire). It’s become totally irrelevant.

What matters is the applications that are delivered to the end user; everything else is just implementation dogma. The people doing these implementations are Help Desks too, they’re just a few degrees removed from the end-user and prefer snazzier titles like ‘Application Services Engineer.’

It’s gonna take awhile. The PC will be around for a long time and people still need to type. But as we shift to tiny, integrated, crash-proof devices we need help desks less and less. The intuitive nature of the computer will suggest that it’s no longer important to be adept at using them. Not only that, but as we cycle through generations of people, the technical citizens will supplant the technical immigrants


12
Apr 10

The Dangers of Building on Someone Else’s Platform

Sometimes we hear about how M&A is the new R&D.

Sometimes I wonder if Embrace & Extend is the new R&D.

A lot of startup business models involve building products that fill gaps in existing platforms. There is absolutely nothing wrong with that, and there have been a few success stories. But if you don’t own the platform, or if you aren’t wildly successful at filling the gap you’re taking a really big risk.

If you fill a gap in someone elses platform and you are moderately successful, then it means there is demand. You have done a fantastic job of demonstrating peoples willingness to pay for something. Twitter needed search functionality and acquired the company that was doing that, but instead of buying an existing control panel, Amazon just built their own. There isn’t a reason why the platform itself will buy you rather than implement the features you’ve spent all your time building.

The issue seems to be the massive amounts of startups going after ‘low hanging fruit’. It’s one thing to be lean and get a product out the door, but it’s entirely another to be able to sustain your market for any reasonable amount of time. Perhaps one of the issues with the low hanging fruit, is that they are problems which are (relatively) easily solved, but the market hasn’t been proven, or a set of ‘best practices’ has not yet been established.

The new model for services & platform companies (which includes companies like Twitter and Apple) seems to be

1) Create an ecosystem
2) Let the ecosystem figure out what your product is and how its being used
3) Cannibalize the features your ecosystem created for you.

It goes without saying that if you want to solve an Easy problem then you’re going to have a lot of competition (link shorteners, anyone?), and your chances for acquisition are actually much much lower. If you’re trying to solve a Hard problem then you will have less competition but you have to be careful – if you build your solution using someone else’s platform, what’s to stop them from taking your idea and just using it themselves? Does your idea work better as a Feature in an existing product, or would stand on its own? There’s nothing wrong with being a feature, but it’s really important that you know the answer.