My Photo

FIRST-TIME VISITOR?

ANALYSIS: APPLE'S 'TABLET' DEVICE

WHAT I'M READING NOW

  • Arthur C. Clarke: Childhood's End

    Arthur C. Clarke: Childhood's End
    What amazes me about Clarke is that his writing is unbelievably compact without losing any punch. This is the first book that I have read from him, and it's a great read, surprisingly not overly dated, which is amazing given how much time has passed since he wrote it.

  • Mr. Scott Eyman: The Speed of Sound: Hollywood and the Talkie Revolution, 1926-1930

    Mr. Scott Eyman: The Speed of Sound: Hollywood and the Talkie Revolution, 1926-1930
    Excellent read so far; looks at the rapid transition of the film industry from the silent era to talkies, seeing it not as evolution but as mutation that wiped out its predecessor. Classic disruptive innovation but compelling, engaging story, excellent narrative.

  • Cory Doctorow: Little Brother

    Cory Doctorow: Little Brother
    I very much enjoy Doctorow's writing style. His book, Down and Out in the Magic Kingdom, introduced the concept of the Whuffie, or reputation score. This book deals with security, privacy, hacking, terrorism and the police state. Fictional, fun read.

  • Steven Johnson: The Invention of Air

    Steven Johnson: The Invention of Air
    Really good read on Joseph Priestley, a Zelig-like inventor who is credited with "discovering" oxygen, and being a huge influence on Ben Franklin, Thomas Jefferson, et al. The book is as much an allegory for the value of being cross-domain, the power of nuance/iteration, the leverage afforded by open/social networks and the role of game changing tools in innovation. The book loses steam in the last 1/3.

  • Professor Richard E. Foglesong: Married to the Mouse: Walt Disney World and Orlando

    Professor Richard E. Foglesong: Married to the Mouse: Walt Disney World and Orlando
    This is the first book that I am reading via the Kindle reader on my iPod touch. Great book that shows how Disney maneuvered its way into establishing Disney World as it's own pseudo government, free from the oversight and controls of traditional city, county and state control. Hardly, a slam piece, it shows how centralized planning can lead to a better, more fully conceived product (think: Apple), but also shows the pitfalls for eager cities and states willing to agree to any and all pre-conditions to secure major corporate patronage.

  • Robert B. Cialdini: Influence: The Psychology of Persuasion (Collins Business Essentials)

    Robert B. Cialdini: Influence: The Psychology of Persuasion (Collins Business Essentials)
    One of my recurring interests is better understanding how to influence the actions of others. This book looks at the psychology and underlying trigger mechanisms, such as reciprocity, that drive people to act in the way that you want them to. Relevant to people in sales, marketers and pretty much anyone who wants to turn the gravity of persuasion to their advantage.

  • George Friedman: The Next 100 Years: A Forecast for the 21st Century

    George Friedman: The Next 100 Years: A Forecast for the 21st Century
    Provocative, enjoyable, compelling read that makes the somewhat counter-intuitive argument that the next 100 years is destined to be the American Age (US), replacing the European Age, which has been the locus of gravity for the past 500+ years, and that our emerging counter-challengers will be Turkey, Mexico, Japan and Poland - not China or India.

  • Jessica Livingston: Founders at Work: Stories of Startups' Early Days

    Jessica Livingston: Founders at Work: Stories of Startups' Early Days
    Not since I read Accidental Empires many years ago have I had so much joy and insight reading about the AHA moments, the blood, sweat and tears, the mistakes, the victories and the lessons learned in the birthing of tech startups like Apple, Lotus, Hotmail and a couple dozen other seminal companies. If you are an entrepreneur or want to know what being one feels like, this is a must read.

  • Ian Williams: Rum: A Social and Sociable History of the Real Spirit of 1776

    Ian Williams: Rum: A Social and Sociable History of the Real Spirit of 1776
    The history of rum, with the exotic spirit as a key character in the founding of the United States. Next book in my Chatopic group, and a fun read so far.

  • Pip Coburn: The Change Function: Why Some Technologies Take Off and Others Crash and Burn

    Pip Coburn: The Change Function: Why Some Technologies Take Off and Others Crash and Burn
    I have been ruminating a lot about the relationship between user experience and user adoption. Coburn is one of my favorite writers/analysts from back in the days of Red Herring, and this book focuses on the user experience/user-centered approach to solutions thinking. Personally, Inmates are Running the Asylum is a better book.

Grab my RSS feed

« Decomposing Google News and Making it Social | Main | Own It. Own the Outcome. »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c285b53ef00e5538369218833

Listed below are links to weblogs that reference On Life as Art, Poetic Truths & Getting Rich:

Comments

John "Z-Bo" Zabroski

Regarding the interview question...

The real world isn't so cut and dry, and I'm not interested in the motivation behind your actions so much as your ability to see the consequences of your actions.

I want to know WHY you are catering to a smaller market. WHO is requesting these features? Is it because 5% of the customers are really loud, and 95% of the customers are really quiet? Give me a customer I can identify with, and convince me that customer is representative of where you will get your profit margins from.

The people who provide the best customer service are the people who can best identify with the customer.

Otherwise, I'd say your question is testing pretty much nothing but someone's ability to B.S. and the results you are seeing are a placebo effect.

John "Z-Bo" Zabroski

By the way... just to hammer home the point with a book you and I have both read... "Dreaming in Code" by Scott Rosenberg. Now, there is a book about a software project with an unlimited budget that failed. However, why did it fail? Should the developers feel proud, simply because they've been told it was a "dream" project? That's what is so horrifyingly awesome about the book... it captures a train wreck in motion, step-by-step.

The problem with Mitch Kapor's dream project Chandler was nobody ever actually defined what "revolutionary" actually meant. It was supposed to revolutionize the way people organized and accessed information relevant to their daily life. Yet, when it came down to it, the developers would have long debates over how to execute "revolutionary". Nobody sat down and coded it.

Mark Sigal

Hey John,

My experience is that very few technical types have a deep understanding of margins and markets, and while such knowledge is hugely welcome, setting that as the bar would filter out ALOT of great programmers.

Hence, I want people who aspire to things like customer adoption, engagement and heavy usage over artistic perfection and self indulgence.

To your point, nothing is ever so cut and dry, but the goal of such tests are to get a binary enough of a read to decide whether a given hire will age well in battle, and will have the right type of instincts necessary for growth and survival, as assumptions often prove terribly wrong in startups, especially early stage ones, and those early adjustments are often the forking points between life and death.

On some level, sales and marketing types are an open book. They have either driven specific outcomes or they haven't, and they are much better at gaming their responses so either way, that group is always much more data driven (from an interview assessment perspective).

As to Chandler, I think that the failure there is more basic. It's pure 1.0/3.0 paradox; namely, never getting arms around a realistic set of 1.0 deliverables that met a target market's 1.0 needs.

Kapor was all about an abstract 3.0 vision without any sense of 1.0 pragmatic realities, which is pretty universally a recipe for death, especially when you don't have the hard pressures of CASH RUNWAY and you have a LEGEND driving the ship (especially one who is decidedly not a tactical product guy) since the predominantly tech oriented team tends to be reticent about saying BULLSHIT. I DON'T GET IT.

Such companies regularly shift between vision, strategy and tactics, never differentiating what is what, and what has to happen in what order for the company to succeed.

John "Z-Bo" Zabroski

All good points... but if we're targeting basic stuff, then isn't the most sensible reply, "Do I get to pick who my team members are?" I guess this is another way of phrasing my complaint: Where are the people in this question? Who am I working with? How unique is my target user?

At the end of the day, your question doesn't matter to me if my team sucks. Software is a contact, team sport.

Truly great programmers don't just listen, they take feedback and use it as a tool to educate design.

Also, there is no more "basic" failure than saying you are going to build something revolutionary and not even settle on whether e-mails should be stored in the calendar, or calendar dated should be stored in e-mail. Instead, there was this abstract "silos" concept with no definitive meaning. There was no 3.0 vision. It was hand-waving.

Focusing too early on a 3.0 vision is just entropy and the natural tendency for things to increase in complexity.

Mark Sigal

Well, I can only speak for my own hiring experience, and post-mortems on good and bad hires.

Part of your point is what interviewees should be trying to grok before deciding if the company is the right team company for them.

In this thread, I am wearing the company hat and team builder perspective.

As to Chandler group, it somewhat reminds me of an old Steve Martin joke about how to become a millionaire. He says, firmly tongue in cheek, "First, get a million dollars."

Vision and ideas are cheap as Dennis poetically notes:

Ideas? We've had 'em
Since Eve deceived Adam,
But take it from me
Execution's the key.

Mark

John "Z-Bo" Zabroski

Sure, you are the team builder, but I am the pig who gets to select his waller. There are many places for me to immerse myself in mud, but I'm still going to pick the waller I like the most.

Interviewing is a two-way street, and really good programmers aren't concerned about passing the interview so much as determining if his/her coworkers are the kinds of people he wants to roll in the mud with.

Yes, "execution's the key", and that means getting the right people.

FWIW, you are right on about people being afraid to say, "BULLSHIT. I DON'T GET IT." It takes someone with true power - either financial power or expert power - to say that aloud. And only the expert can say it without looking stupid. It's rare where someone with financial power will say it e.g. Mark Cuban.

John "Z-Bo" Zabroski

...and of course, there are CEOs who literally don't want people who can think for themselves. Charles Simonyi of Intentional Software is a good example... he wrote a thesis about a management principle he called Metaprogramming, which was basically Taylor-istic management applied to software engineering.

By the way, it might sound tacky, but my recommended book for getting rich is The Richest Man in Babylon.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

READ MY COLUMN @ O'REILLY RADAR

READ THE 9 TRUTHS

READ MY MICRO-BLOG: TWIT-WORTHY BITS

Search My Blog

  • Loading

FOLLOW MY TWEETS

Twitter Updates

    follow me on Twitter

    Enter your email address:

    Delivered by FeedBurner

    Blog powered by TypePad
    Member since 07/2005