Skip to main content

How To Win By Not Mattering

This is all about the strange and confusing state of win we see repeatedly today, where a brand or concept gains such control and mindshare that no one even recognizes them as a thing anymore. Few people think of Q-tips as a brand versus just being the name of a thing. Pepsi Co executives probably grind their teeth thinking about movie goers ordering "just a coke" when Pepsi products are prominently and solely for sale. Most Internet Explorer users go beyond not understanding what IE is, they don't even understand what a browser is!

Today, I want to talk about something newer and more specific, and less sure. The direction is visible that Mercurial is being given steps (it is important to phrase it this way, as I'll explain) to not matter, and that is precisely why they will win.

CVS still matters, which is precisely why it has lost so utterly in the imaginary battle for geek mindshare. If you are using CVS, it is important to remember that along the way, because it affects how you work and what you can do. Subversion still matters, but less so, as it stays largely out of your way.

None of the layers in the DVCS arena matter very much, because none of them are very different from the others. Git and Mercurial and Darcs? They all behave similar enough that none of them offer anything different, beyond community and how to deal with failures. Now, Google announces upcoming Mercurial support for Google Code, but the real thing that stood out to me is that they built their own implementation over Bigtable. They are not supporting Mercurial, they are supporting the mercurial format.

It wouldn't be difficult to do the same thing and implement any one of them in any one of the others. I think by next year you'll see git and mercurial doing push/pull between one another.

Note: This was a crappy post and I try to stay away from posting just to post, but I'm getting back into the swing of things. Give me a break, yeah?

Next Post: How To Give Up to Succeed (Maybe public commitments will force me to write, lest I be publically humilated!)

Comments

Paddy3118 said…
You've made me think now about how they have done it. I had thought they had took Hg's interface to the filesystem and then mapped it to Bigtable - like the duck-typing substitution of StringIO for a file object in Python.

If they don't have a clean, maintainable, interface to the originam HG codebase, then the two could diverge!

- Paddy.
Paul said…
I don't know how similar Mercurial and git are, but darcs is certainly not very much like git. Darcs operates on patches and does not really care about their ordering -- you can selectively push and pull patches so long as there is no conflict. This is very difficult to do with git.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro