(this is page 35 of 121)





Latest

On workplace meetings

Paul Graham has a short and insightful essay on the true cost of the meeting-obssessed cultures of big companies, "Maker's schedule, Managers Schedule," where he points to the fundamental impedance mismatch in the working rhythms of engineers/creative folk and their business/managerial counterparts. The money quote:

For someone on the maker's schedule, having a meeting is like throwing an exception. It doesn't merely cause you to switch from one task to another; it changes the mode in which you work.

After two years of drowning in meetings, I've come to my own conclusion on this topic. Unfortunately meetings are unavoidable, especially when trying to coordinate large group efforts. However, I think the following three changes could boost the productivity of every hardware/software/services company in the Fortune 1000 by 2x, and in some cases maybe even 10x:

1. Have Microsoft Exchange schedule the default meeting length at 15 minutes. Require manager authorization for scheduling meetings that last more than 30 minutes— or 60 minutes more than once per week.

2. Have all virtual collaboration systems (conference call-ins, video conferencing) time out and lock if the meeting is not started on time. Lock all new participants out 1 minute after the start of the meeting. If anyone has "computer trouble" because of not preparing early enough, lock them out of the meeting as well.

3. Have an eBay-like rating system on all meetings that participants can optionally use. If a meeting organizer gets below a certain rating threshold, require manager approval for this person scheduling any further meetings.

I'm sure people would find all sorts of creative ways to game these three rules, but over enough interactions, and with enough participants, I think the overall system would weed out a lot of the crap meetings that suck up time and interrupt the rhythm of folks in maker roles.

On the other hand, Graham doesn't consider the other giant problem affecting "makers" at work these days— the constant self-imposed interruptions to "twitter this," or "check Reddit," or IM or take a peruse through Google Reader. In some ways, these continuous partial attention helpers are more insidious as they tend to draw little bits of focus down throughout the day while not actually feeling like real interruptions.

Comments Permalink

Jonathan Zittrain, of "The Future of the Internet and how to stop it" fame, had a great op-ed piece in the Times this Monday, hot on the heels of Amazon pulling a 1984 by remotely wiping purchased copies of Orwell's books from users's Kindles. In it he cautions us the get our heads out of the clouds and stop thinking about cloud computing as necessarily an improvement on what we have today. He finishes the piece with a warning that echoes the main theme of his thoughtful book:

The market is churning through these issues. Amazon is offering a generic cloud-computing infrastructure so anyone can set up new software on a new Web site without gatekeeping by the likes of Facebook. Google’s Android platform is being used in a new generation of mobile phones with fewer restrictions on outside code. But the dynamics here are complicated. When we vest our activities and identities in one place in the cloud, it takes a lot of dissatisfaction for us to move. And many software developers who once would have been writing whatever they wanted for PCs are simply developing less adventurous, less subversive, less game-changing code under the watchful eyes of Facebook and Apple.

While the Platform as Service providers like Facebook, Apple, Google, and soon to be Microsoft, will continue to push their integrated siloed stacks for hosting code and data in their proprietary runtimes, I believe most developers are smart enough to realize that they are giving up a tremendous amount of independence for the benefits of virally leveraging the social graph, tighter integration with other Google services, or the AppStore effect. As many Facebook application developers have already learned, building in these silos is at best a Faustian bargain which will someday come due.

To me the only way cloud computing works in the long term is with full portability of both data and execution context. And ironically, despite the bonehead Kindle move, Amazon's use of generic x86 instances as the unit of computation for hire is a great first step in this direction. In theory anyone with enough Xen skills could compete by the CPU hour with EC2— an quite a few folks already claim that they do!

Assuming we continue along this model in the development for the open (or as Zittrain calls it "generative") cloud, we need to then move to moving this computation around from virtualized servers to any device we want, be it the old PC connected to your cable modem, your dual core laptop, or even some future version of a mobile computing device.

In a sense this was the promise of the JVM— write the code for one virtual machine and run it on anything from a Java ring to an enterprise class server. Unfortunately the JVM ecosystem did not bring with it three decades of rich UNIX tools, millions of man years of expertise in networked OSes, and a thriving open source ecosystem upon which to build. Perhaps as projects like LLVM get tailwinds due to the aggressive move to multi-core, we'll finally get a VM-like experience that allows us to bring the whole turtle's shell of stuff that Linux and OS X make suck brilliant use of with us— a la ubiquitous EC2 instances.

I'm not sure how this is all going to turn out in the end but what continues to amaze me is that I don't think we've ever been at a point in computing where there are just so many execution context choices facing people looking to bring new functionality into the world. This week on the 40th anniversary of the moon missions, Google publicized the Virtual AGC project which contains all of the Apollo lander code and an emulator as open source. This was the state of the art in 1969— running on some proprietary computer that I'm sure cost millions in taxpayer dollars. And yet from my little Arduino board to the EC2 instance I rent from Amazon, there is not a single computational execution context in my life that couldn't run this thousands of time faster than it did when those guys bounced around on the moon thanks to it.

Amazing.

Comments Permalink

Alex Payne has a thoughtful post on the future of feed readers where he argues that the current model (as best exemplified by Google Reader) is dying, and that all of the social replacements (Digg, Reddit, Twitter, Facebook) don't quite get us back to the same place.

I agree; back in 2001 I was convinced that RSS, pub/sub, and feed readers were a chocolate and peanut butter technology combination that would someday be as mainstream as IM. People have argued that their failure to attain mass market status was a result of the geekiness and complexity of "subscribing" to new content, but having turned a bunch of people on to Google Reader only to see them abandon it in short order, I have a different take: to me, the failure in feed readers has been all around content curation. And more importantly, since the atomization of feeds in feed reading, brought about by the aforementioned social replacements, that curation task has shifted to the "wisdom of the crowds," which— while hardly perfect— does take a step forward from what we were getting from the feed reading ecosystem.

Let's take an example from a related space, photo sharing: when Flickr first upended the traditional photo sharing category, people were quick to claim that it was their social dimension or their "default to public" attitude that made all the difference. And while these features were important to its success, I think the real innovation of Flickr was the atomization of the traditional "photo album" metaphor that everyone until them had taken for sharing photos online. By allowing and expecting people to share one photo at a time (and then making most of the other "open" feature differences), Flickr made itself a much more dynamic system for discovering and consuming relevant photo content quickly.

This is the same thing that a social news site like Hacker News achieve with feeds. Most of the content exposed in the top 10 list is actually pumped out in RSS by individual bloggers, but by atomizing it and using the community to curate the day's best content, the general user doesn't have to bother managing relationships with the individual subscriptions.

And if if that was good enough, I'd be the first one to let classic feed readers like Google Reader fade into the sunset. But all of these social aggregators seem good at getting me the B/B+ content that overlaps sufficiently with everyone else's interest— just not the A content that really makes me think. For that I think the right approach requires knowing too much about me and my particular tastes and reading habits.

Which by the way, a properly instrumented version of Google Reader could do more easily than any social app. If you've ever looked at the metrics page of Reader, you'll get a glimpse of the power of collecting this type of data: what you read, when, and for how long. If I were the PM on Reader, I would forget about all of this social sauce they are trying to port over from Facebook, Twitter, and Friendfeed, and focus instead on algorithmic curation of the atomized feeds in a given subscriber's account. Some of these tasks would be basic, such as intelligent de-duplication or time-based views of the newest content ("when I am at work, I only want to read 4-hour work week-ish stuff"), but others would require the level energy being applied to things like the Netflix recommendation algorithm with its associated $1MM prize.

Because one thing is very true: Google Reader with 200 subscriptions takes way too long to get through, and about 30% of the time is wasted on tasks that algorithms could cut out of the process for us.

When everyone zigs you should zag. As the rest of the web descends to a least common denominator social orgy for surfacing good content, Google would do well to remember its strengths and double down on making machine curated feed reading suck less.

Comments Permalink

The hoopla about whether Mike Arrington, of TechCrunch fame, is really about to launch a piece of consumer hardware is the most exciting thing to happen in the TechCrunch ecosystem since Google bought YouTube.

If he does launch it, and it doesn't tank, the following two implications are likely to redefine the landscape of the consumer computing industry forever:

1. It means that most of the hardware "value add" really does take place outside of the big companies like HP and Dell and inside the ODMs in Taiwan and the supporting ecosystem of far east software/services companies (TechCrunch it would seem is using one in Singapore for both bringing up the hardware and getting the bits to run). If a non-VC funded startup can pull this off, all of the big companies with their leagues of non-engineer program managers should take a moment to be horribly embarrassed.

2. It also means that what will be increasingly relevant in this new world is access to an audience who is willing to buy based on the media relationship you've established with them. TechCrunch probably has 5-10,000 really passionate folks who would take a risk on a gadget like this (out of the million and a half that come to the site), and in the end, that may be all that is needed to jump start a hardware product with these kind of build economics.

I don't know if this project will succeed in the end but I applaud Arrington for taking the risk. If he does pull it off (by which I mean if he manages to sell 5,000 of these), you can bet that everyone will take notice— both big and small— and we may yet see a new era of hardware-led innovation born.

Comments Permalink

Work and meaning

After two years at a big company, I think I've come to understand the way in which people work here. I've come to know it as the 20-20-60 rule.

20% of the people in a big company are operating above their skill/will level. These are the folks who make up the Peter principle bucket— promoted beyond their abilities. They are also the folks who are living true to the famous jazz edict: always be the worst guy in the ensemble. God love them for taking that risk— and that is despite how miserable they may make the rest of us.

20% of the folks are the real A players. When you read about Microsoft stealing XYZ away from Google or Amazon, these are the folks they are talking about. They have the skills to get things done, the passion, and perhaps most importantly, the patience required to make elephants dance (big companies get stuff done). Every time I meet one of these gems, I walk away believing a little more in the human condition.

The other 60% of folks are what most people mean when they talk about the "fat" in corporate America. They generally only good at producing and consuming meetings and at looking good in front of their bosses. They don't take risks, but not because they are to limited (these are not Peter principle folks), but because they are optimizing for a different outcome: their own career advancement. Knowing that most products and services fail, these folks prefer to be "in" with some senior exec that will always take care of them. And when the shit hits the fan they've got their story down pat as to why everything that was outside of their purview was what "went wrong."

I hate these people.*

They are what makes working in a big company completely intolerable. The are what has given Powerpoint a bad name. And perhaps most importantly, they are the detritus that has to be cleaned out if we are to get our economy to a good place again.

I've just finished reading Alain De Botton's The Pleasures and Sorrows of Work, a somewhat lyrical description of 10 "professions" that range from transportation logistics to electric transmission to airplane manufacture. It's a fun read because at its best, the book provides a very candid look at how the folks in these industries find meaning in their work, no matter how mundane.

My favorite bit happens to be the "biscuit manufacturing" chapter (for us Americans, crackers & cookies) where we get to meet a couple of people that are passionate about getting just the right mix of dough, packaging, and marketing around one of the most basic experiences we humans share. It is in describing this quest for the perfect biscuit that De Botton shows us why it's important to never get caught in that fat 60% belly of the workplace: because if you are there, you will never get more than a paycheck, and certainly not the meaning that most of us deserve from what will be the single biggest time investment of our lives.

* Not personally per se but certainly in the work context.

Comments Permalink