<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>Keith's Web Blog RSS Feed</title>
<language>en-us</language>
<link>http://www.keithwatanabe.net/index.php</link>
<description>Keith Watanabe's Website</description>
<item>
<title>Advocating Elimination of the 5 Day Work Week
</title>
<link>http://www.keithwatanabe.net/blogs/2007/7/15/5fd57180eb04ae0f312d4331e5429b39.html</link>
<description><![CDATA[I've never quite understood the idea of the &quot;5 day&quot; work week (I probably should look up the origins on wikipedia).  These days to me it's a formula for mental and physical burnout.  I've seen people on 6 day work weeks and I can't believe they're still alive (if we talk about office jobs).  But I find the 5 day work week to be offensive and unnecessary.  It's physically and mentally offensive in that you easily can burn out from your job.  People are engrained into the system from an early stage only to continue throughout most of their adult life.  One's body and mind can easily break down from the wear and tear.<br />
<br />
So why continue?  I see this as something that might progress a part of society but isn't overly useful.  Some may argue that removing one day would hurt  global productivity.  I thought it might improve things.  Let's see:<br />
<br />
- Reduce mental and physical fatigue, ensuring that people's attendance will improve<br />
- Improve morale as people would have that extra day to do other personal business<br />
- Possibly allow for companies to increase their workforce by attempting to fill in the gaps that a person on  leave takes<br />
- Change the mentality of companies from simple 9-5 shops to 24/7 support spots (this applies to large organizations that can afford such a thing)<br />
- Doubling the knowledge of an organization by providing duplicate representatives on key areas.  That is, to fill in for the extra day (or three if we want to change things), we could use one day as a knowledge transfer day between the counterparts in order to proceed with certain tasks<br />
- Improve the support models for companies in all areas<br />
- Increase the job market and usher in a new era of competitiveness<br />
<br />
One concern that might come up is pay.  How can a company compensate for this situation for individuals?  Also, would a person in this loop be deducted from pay, thus reducing their ability to afford things?  My response to this is the following:<br />
<br />
- Companies can reduce the overall wages of people on such a program, but should receive some for of tax reduction initially to compensate from the government (there are more jobs, thus more taxes that a company will payout, so the government ought to provide some help there).<br />
- There needs to be a kind of deflation for affordability.  Things like cars, rent, etc. ought to be reduced.  I can see huge problems in places like California.  But these are the places that also require this type of system since the commuting and type of work tend to be more intense.<br />
<br />
At any rate, I think society has progressed to the point where we need a new system of employment to help in improving the quality of life for people.]]></description>
<pubDate>Sun, 15 Jul 2007 00:50:25 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2007/7/15/5fd57180eb04ae0f312d4331e5429b39.html</guid>
</item>
<item>
<title>Yahoo's Open Strategy, Not Bad, Not Great Either</title>
<link>http://www.keithwatanabe.net/blogs/2008/4/30/24dcb135b13a6aee7663adcf3d1a455c.html</link>
<description><![CDATA[I was reading about the new potential <strong>Yahoo</strong> with regards to their <em><strong>strategy of openness</strong></em>.  I like basic concept because it's what I've been saying for years that <strong>Yahoo</strong> needs (needed) to do.  Of course with the pending <strong>Microsoft</strong> deal, it's hard to say whether or not this strategy will have legs, but let's ignore that possibility for now and focus on this current core strategy.<br />
<br />
In <strong>Techcrunch's</strong> article, it's mentioned that:<br />
<br />
<em>Yahoo wants to turn itself into one big social network-driven site, and simultaneously open many of its core services to get users and developers thinking of Yahoo as their Internet hub.</em><br />
<br />
I think <strong>Yahoo</strong> should avoid utilizing the buzzword &quot;social network&quot; at all cost.  It's passe and screams to me of lost revenue.  They had long lost the grounds on this to other competitors, most notably <strong>Facebook</strong> and <strong>Myspace</strong>.  The whole &quot;let's share&quot; and &quot;add as friend&quot; thing are just fancy groupware motifs re-packaged for investors.  And <strong>Yahoo</strong> doesn't need investors at this point (well, they need a missile to hit Seattle for their sake, but that's a different story).  However, opening their core services is the start of where they should be going (and probably if they pushed it about 4-5 years ago, they could've had a huge leg up <strong>Facebook</strong> and <strong>Google</strong>).<br />
<br />
The other part in the <strong>Techcrunch</strong> article that's good to point out is this quote:<br />
<br />
<em>There are three components to the additional news announced today - platformization, opening services, and portability.</em><br />
<br />
These ares are definitely the direction they want to move in.  Unfortunately, <strong>Google</strong> has already done these things whereas <strong>Yahoo</strong> is in the proposal stage and this screams of &quot;they just copied <strong>Google</strong>!&quot; I do like the fact that <strong>Yahoo</strong> is focusing on PHP (actually <strong>SecurePHP</strong>) as it will help a PHP guru like myself actually be able to get started quicker than say with <strong>Google</strong> (and again make someone like me more apt to use Yahoo than <strong>Google</strong>).  They call their engine <strong>YAP</strong> (<strong>Yahoo Application Platform</strong>).<br />
<br />
It seems the chief purpose in this is primarily for user retainership.  Not sure if that should be the chief purpose, but it's what they want.<br />
<br />
Now, let me show you a counter strategy to <strong>Google's</strong> based on my limited view of what <strong>Google</strong> is doing with things like <strong>Google Apps Engine</strong>, etc.<br />
<br />
Originally, I was saying that <strong>Yahoo</strong> needed to become an infrastructure platform for businesses, kinda like what you're seeing <strong>Amazon's EC2</strong>, <strong>Google Apps Engine</strong>, <strong>Sun's N2</strong>, etc.  The problem is that the majority of businesses trying to use the internet as a platform just have bad practices.  Too many outages, the high cost of setting, maintaining and improving that infrastructure to scale and (here's the key point for myself) <em><strong>simply re-inventing the wheel each time</strong></em>.  Companies that do provide this level of scale can eventually monetize that knowledge through re-selling their platforms.  As a side effect, you get to reduce your IT department size, since you no longer have to worry about dealing with a data center and can hopefully focus on business development by outsourcing the infrastructure component to a competent entity that utilizes best practices.<br />
<br />
That's the start of the future for <strong>Yahoo</strong>.  But there's more....<br />
<br />
I view Yahoo's future strategy as <em><strong>inverting their existing system</strong></em>.<br />
<br />
Right now, as users, we land on their homepage and utilize only certain aspects.  A lot of the crud that goes on their homepage is unnecessary cruft whose value and mileage varies on a per-user basis.  And a lot of the current stuff seems like legacy portal content.  In opening up <strong>Yahoo</strong>, they need to reverse that aspect and expose all that content for developers like myself.<br />
<br />
They've partly accomplished this through some feeds.  But we need more as I have been saying.  I think <strong>Yahoo</strong> needs to leverage the numerous partnerships with whomever they're getting their content from and allowing people to access that content without fear of repercussion  from a  lawsuit.  Imagine if someone wants to develop a music application.  That person could utilize Yahoo's service and create something without getting <a href="http://www.news.com/8301-10784_3-9930419-7.html?tag=bl">sued by the RIAA</a>.  That's a move that <strong>Google</strong> clearly has not implemented (yet).  We need to be able to access deep, specialized levels of information and reutilize existing things on <strong>Yahoo</strong>.  Imagine for instance, a developer/homepage creator being able to take images, audio and video from <strong>Yahoo</strong> to create a fanpage for their favorite artist.  If a developer can host such an application on <strong>Yahoo</strong> but legally be able to  utilize such resources without fear of a lawsuit because of some legal clause Yahoo can provide as part of their service offering, that means <strong>Yahoo</strong> services can potentially be revenue, socially and technologically driving.  I see this as a positive pro-active stance on what so many companies shy away from.<br />
<br />
I mean people talk about <strong>Mashups</strong> all the time, which to me are nothing more than something like a DJ splicing together bits and pieces to create a mix.  But for this to work there needs to be something protecting people so that these services can truly flourish.  Can <strong>Yahoo</strong> be the key to provide this type of service for developers?  Perhaps <em>cut a revenue sharing deal with those artists, studios, producers, and content producers to allow developers to do such things.</em><br />
<br />
Another part, and I think this is a key piece to <strong>Yahoo's</strong> long term survival (without <strong>Microsoft</strong>) is empowering the users on the ad front.  The big problem I have with ads is that people who want to use them are powerless to the randomness of context based algorithms.  Certainly what <strong>Overture/GoTo.com</strong> originally did was innovating and helped create an industry of its own.  But the fuel for those days is depleted and they must find a new source.  My major complaint about context ads simply is this: they suck.  I never feel like there's enough control and that web programmers are forced into some stupid SEO madness that really has no ROI, except for those who have high traffic.  It's always just been up to the webmasters to manage this.  Of course, the argument for this area is that people simply don't have time to manage these things (it's almost like managing being a day trader).  But at the same time the automation algorithms used to analyze one's site sucks and it's mostly what seems to be pure chance and high traffic where one can earn money for this.<br />
<br />
But in the end, people just aren't clicking on ads and people instead are turning to other solutions (some which are nefarious) to handle this aspect.  Which in the end implies that the solutions provided by <strong>Yahoo Search Marketing, Google AdWords, Microsoft AdCenter</strong> only can survive because of the size of these companies, not by the quality of the ad service provided.  Thus for me at least, control and the ad quality are what <strong>Yahoo</strong> need to improve upon.  If they can open up these services and allow developers to better tune ads to their advantage rather than relying on <strong>Yahoo's</strong> algorithms, there's a better chance for Yahoo to excel in this aspect.<em><strong><br />
<br />
Opening search is a must.</strong></em>  <strong>Google</strong> shot themselves in the foot by killing their old web service and forcing everyone to move towards their branded AJAX search.  I know what <strong>Google</strong> was thinking, but it was a bad long term move.  It is true that I use <strong>Google</strong> as my primary search engine, which naturally makes me inclined to prefer <strong>Google</strong> as the number one candidate if I would want to write some search function.  However, closing search and limiting it to a branded AJAX search just sucks.  <strong>Yahoo</strong> easily can compete here by providing unlimited queries with an XML response.  I don't think the results returned are going to be that much different in quality either these days.<br />
<br />
And here's some radical but (<strong>Google</strong>) killer ideas for <strong>Yahoo</strong> in terms of being innovative:<br />
<br />
They need to not impose any limits on queries returned from their results.  I think Google's use as an <strong>Apps Engine</strong> is limited simply because they impose limits.  Some of <strong>Yahoo's</strong> services, like search, already does this.  <strong>Amazon</strong> has limits too but they're smart enough to understand how to monetize their services for the enterprise (which to me means of the three, they'll survive in the long term).  Still some of their services are limited like <strong>Amazon's Web Service</strong> function has a limit of 1 second per query per IP address.  For a site that intends to be high volume one day, this imposes a huge restriction on being able to do things like threading queries, this is an impractical limit.  It's like what I said about <strong>Google's DB</strong> only being able to return 1000 results at a time: the most serious application you can write in truth is a local pizza ecommerce site.<br />
<br />
Here's where <strong>Yahoo</strong> can easily differentiate themselves again from the competition by removing such limitations on their services.  If <strong>Yahoo</strong> could provide the equivalent of <strong>Amazon's Web Service</strong> search for their content without the limited query response, I'd switch in a second.  The natural goal for any website is to scale up; so if the bottleneck becomes these services' limitations, then developers will end up being forced to shop around for someone who offers a better version.  And that's a great place where <strong>Yahoo</strong> or some major content providing company can enter.<br />
<br />
Finally, and here's the most radical idea that I think companies like <strong>Yahoo, Google and Microsoft</strong> need to move towards in attracting us developers is that they need to become something like <strong>VC funds</strong>.  I'm certain that many developers like myself dream of the day that our little service will one day get bought out by <strong>Yahoo, Google, Microsoft, AOL,</strong> etc..  I've known people personally who had this happen.<br />
<br />
What has been killing someone like myself is simply that I can't focused all my energy on my own stuff.  I've got to take a day job and can only put in 4-10 hours maximum a week on my own projects.  And even those hours are not guaranteed.  <br />
<br />
I'd love to see someone like <strong>Yahoo</strong> or <strong>Google</strong> just toss money at me to develop the next <strong>killer application</strong>.  And there's no doubt in my mind that others feel the same way.  This would be crazy as the flood of applications would be unlimited and you'd be creating a huge hot zone for an even faster push on the technology side.  This would be like a renaissance of computing (things are already happening like this but a lot of what we get is crap).  But given the potential of services provided by <strong>Yahoo</strong>, the openness of their feeds and usage of infrastructure, etc. the quality level might be a lot higher.<br />
<br />
There are some catches to my idea, but as with everything, there's a method to my madness.  And there's a nice way for <strong>Yahoo</strong> to monetize this nutiness:<br />
<ul>
    <li>The venture money would come in tiers.  So it all depends on the ambitiousness of the project.  It might range from $50 for a silly localized pizza site, to $1500 seed money per week/month all the way up to $60,000 for a one year contract on a project.  I'm certain Yahoo already does something like this internally where budgeting for projects get proposed and then later killed.  This probably is a far cheaper solution.</li>
    <li>There would be a review process on applications based on the scale of the project.  People who want the highest ($60k) tiered project must receive a review of their site/business plan with their business development groups.  This helps potential businesses work with people who specialize in growing businesses.</li>
    <li>Periodic code reviews with internal Yahoo developers will go on consistently. </li>
    <li>Now, here's where <strong>Yahoo</strong> gets the money back: depending on the success of the site, <strong>Yahoo</strong> would get an automatic level of ownership of the business/application, revenue sharing, etc. guaranteeing that they would get a return on their investment.  Again, it's a <strong>VC fund</strong> so <strong>Yahoo</strong> essentially gets first dibs.</li>
</ul>
The thing is that this is a new form of ecommerce, risk taken to the extreme.  There's too many punk kids like myself who just don't want to deal with the ego slamming of venture capitalists (in my case because we've seen how typical VCs operate and simply because most of us don't have an MBA).  But you gotta ask yourself (that is YOU <strong>Yahoo!</strong>) did Steve Jobs, Bill Gates, Paul Allen, Larry Ellison, Steve Wosniack, Sergie Brin, Larry Page, and even your own <strong>David Filo</strong> and <strong>Jerry Yang</strong> have MBAs when they formed some of the most powerful companies around?  No, they just had dreams like myself.  A lot of it was talent and there certainly was tons of luck involved in all of that.  Now, as a fellow tech dreamer, I want the same and many of my friends do too.  But we're all scared of leaving our day jobs in doing something crazy.  Still we want it.  And we need guarantees.<br />
The thing is that this type of thinking is <strong><em>socially changing</em></strong>.  It's social engineering at its best.  It's the thing that's needed by <strong>Yahoo</strong> to inject into it's public image as being friendly and appealing to the common man.  Think of the benefits:<br />
<ul>
    <li>A monstrous new playing field of applications and technology that will driven by the sheer competition.</li>
    <li>Switching the landscape of venture capital.</li>
    <li>Practically guaranteeing the success and expedient adaptation of <strong>Yahoo's</strong> services.</li>
    <li>A definite win on both sides in terms of ROI; <strong>Yahoo</strong> gets money and control back for their services; punk kids like myself don't have to go to an office every day and might make it big.</li>
    <li>The creation of new industries as a result.</li>
    <li>The continual elevation of importance of developers within Yahoo.</li>
    <li>Providing best practices to the industry at large.</li>
</ul>
This is real innovation at its best.  I mean, why should <strong>Yahoo</strong> spend several hundred millions of dollars in acquisitions when they can pay independent developers a few thousand a month to do this?  The money translates to the same thing so rather than on focusing on an existing acquisition strategy with and unforeseen return on investment, you're getting immediate control for what people want and helping to mold it.<br />
<br />
I see this strategy as being a monstrous success for the sustainable growth of <strong>Yahoo</strong>.  It's my analogy of selling cigarettes/marajuana to minors; gradually, you upgrade them to crack and heroin.  But the difference is that the heroin is socially beneficial.<br />
<br />
So <strong>Yahoo</strong>, make <strong>THIS</strong> happen.   This is the real vision for what you want.  This is partly what you're doing through your overpriced acquisitions.  This is what poor starving developers (rather than poets as the proverb goes) like myself want.  This is what the industry needs.  And most importantly, this is <em><strong>SOCIAL.....SOCIALLY CHANGING</strong></em>.]]></description>
<pubDate>Wed, 30 Apr 2008 13:08:28 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2008/4/30/24dcb135b13a6aee7663adcf3d1a455c.html</guid>
</item>
</channel>
</rss>
