Slashdot Mirror


Bringing Tech to Market: The Rules of Innovation

Everyone knows that best-quality plus first-to-market doesn't always equal success. A Harvard prof who specializes in this stuff has a great article in Technology Review that digs a lot deeper, called The Rules of Innovation. It's a look at why some technologies are marketplace success stories and some are forgotten failures -- and more, an attempt at rules which predict which will be which. There are lessons here for the entrenched companies (e.g. Sony) as well as for the disruptive upstarts (e.g. Sony 50 years ago). You have to understand the battlefield to win the war.

8 of 170 comments (clear)

  1. First Post? by nybble_me · · Score: -1, Offtopic

    First Post? By accident too.

    --

    reenigne
  2. first poem by sulli · · Score: -1, Offtopic

    I think that I shall never see
    a first post lovely as a tree.

    A post so delicate and short
    Compared to the comments of sllort;

    A post that reads slashdot all day
    But has but two brief words to say;

    A post that may in BSD
    Say Kreskin you don't have to be;

    A post that in Your Rights Online
    Will never stop its endless whine;

    My Karma surely will be toast,
    but only I can get first post.

    --

    sulli
    RTFJ.
    1. Re:first poem by sllort · · Score: -1, Offtopic

      What, are you calling me longwinded?

      That's an unfair characterization. I'm more offtopic than longwinded. Sheesh.

    2. Re:first poem by sulli · · Score: 0, Offtopic
      fair enough. how about:

      A comment that will knock the socks
      Off any statement of FortKnox

      ?

      --

      sulli
      RTFJ.
    3. Re:first poem by sllort · · Score: 0, Offtopic

      That's pretty good. I mean, you should actually make fun of me; I deserve it. But if you wanna go after him, perhaps:


      A comment that sucks manly cocks
      Just like that blowhard FortKnox


      Or something.

  3. Re:How about... by Anonymous Coward · · Score: -1, Offtopic

    Christians are evil. They are responsible for the most horrific atrocities in the history of man. Christianity is responsible for the Dark Ages, the various Inquisitions, the Crusades, the Pogroms, the Holocaust, the rewriting of American history, and worst of all: the notion that you should believe something in spite of evidence to the contrary because it somehow makes you a better person. Christianity is the age-old enemy of science and reason. It proposes the existence of a God that has no meaningful characteristics, and it proposes the possibility that such a "being" can have a human son, despite the fact that there is no non-Christian historical evidence to support the fact that he ever existed, and the strong correlation of the events of Jesus' life with the myths of the Mithras cult of Rome. When confronted with these facts, Christians first fall into a ridiculous world of baseless, liberal biblical interpretations; then they fall into a world wherein "faith" can serve as a useful tool of determining truth in the absence of reason. They fail to realize that reason is the only possible way of determining truth, and the whole concept of knowledge is meaningless if it is based on anything but reason. Christianity is a thoroughly invalid and silly concept, and I refuse to read any slashdot postings by anyone who is so weakminded that he values comfort over intellectual honesty.

  4. but not *nixs luck by Anonymous Coward · · Score: -1, Offtopic

    Ahhhh - the easy low-end gets fat, while the complex elitists starve ... hehe ... thus the article certainly explains why/how/when Linux is totally fscked.

  5. Explained: Why FreeBSD is dying by Anonymous Coward · · Score: -1, Offtopic
    The End of FreeBSD

    [ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

    When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

    Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

    FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

    It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

    So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

    Discussion

    I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

    From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

    There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

    Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

    Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

    Shouts

    To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

    To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the nd, we need you all; in order to go forwards we must first avoid going backwards.

    To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.

    To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.

    To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.

    Future

    I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.

    However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.

    You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.

    = Mike

    --

    To announce that there must beno criticism of the president, or that we are to stand by the president, right or wrong, is not nly unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt