Skip to main content

RE: Television networks block Google TV from accessing web-based content (update)

Google, just like Microsoft a decade ago, has butted into a highly lucrative space where the business model is paying for content access as well as selling advertising.

Google TV essentially helps kill part of the revenue stream, which is the cable subscription. Just like with books Google has gotten ahead of its skis. This is bad business planning on Google's part and poor execution of this strategy. Again they forgot that just because something is technologically possible it doesn't mean it's going to be supported by the existing businesses.

I agree that eventually content is going to be distributed via the internet and people are going to browse linked television streams with hubs that aggregate the "channels"

If Google's model is to create a wide distribution of ad-only supported TV they are in trouble. A bunch of very important content is not sold for ad revenue only. Google has a choice - do they become the souped up YouTube distributor for the long tail of low value content or do they introduce a subscription model for TV. What happened below shows that they didn't really think this through.

Broader Discussion: http://www.engadget.com/2010/10/21/television-networks-block-google-tv-from-accessing-web-based-con/
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …