yoak
The coder wasn't completely getting our explanation, but the code was so "boring" or "clear" that we opened up an editor, copy-and-pasted some blocks around added a few if statements and expected it to be basically functional. This was a complex algorithm and a complex change, and we offered provisos that we didn't know what that function returned so a "not" might have to go in front, and a variable name would have to be changed and one piece was going to have to operate on a new key in memcache, but it was basically there.
The point is, the code was so well-written that we could read it well enough to do this never having seen it moments before, and our resulting chopping was clearer to the original coder than 20 minutes of histrionics on a whiteboard full of formulae. That's how it should be. :-)
And for any haters in the crowd, it was all in Perl. So much for "write-only" complaints. :-)
I agree with wave that it looks like something that should have worked so far, and one can presume they're getting better at what they're doing and hopefully will have a better economic environment for these current startups.
It's really cool that this happened.
inflammable, flammable: http://ngrams.googlelabs.com/graph?content=inflammable%2Cfla...
regardless, irregardless: http://ngrams.googlelabs.com/graph?content=inflammable%2Cfla...
Calling it a violation of free speech waters down the impact of the phrase as it covers real governments doing it with real violence. I went to college during during the height of the political correctness bubble and was exposed to nuts who called holding a door open for a woman "rape." I couldn't imagine any more crass or insensitive action with respect to real rape victims.
She set out to learn how. Over the span of about two years with a lot of work she got to be amazing at it, and painting as well. She now all the time hears how she has such an amazing (previously undeveloped) talent.
This issue is complex and I don't have great overall answers. It isn't clear how search results should bias based on sentiment. (That's discussed on the blog and here.) One thing I am sure of is that I respect discovering a result they consider bad and looking at the algorithms that caused the result and I don't respect deciding that you got egg on your face for the results of your algorithm in this case and jiggering the results.
Of course, we don't know that Bing didn't come up with algorithmic improvements, but the comment you're replying to isn't refuted in any way by the fact that the result has disappeared (or greatly diminished) in Bing. To the contrary, in addition to my bias to agree with the OP on Google / Bing, when one company says, "We've taken a look, made small improvements already that have some impact, and we're looking to make more" and the search result simply disappears in the other case, I'm inclined to take that as specific evidence of the former doing the better job.
In an attempt to explain what it means, it comes up with things like:
Ensure that users and those who will be affected by a system have their needs clearly articulated during the assessment and design of requirements; later the system must be validated to meet requirements.
I don't write requirements of that sort, nor do validation testing in the sense implied. If I want to be in the ACM, this leaves me with the choice of either concluding, "Ah, I know what they mean and I'm there in spirit" or not participating. That sorta sucks. If I agree to a set of principles, I want to diligently follow it. I prefer a high-level "Don't be a jerk" approach to such things and sound human judgment entrusted to make calls if needed about propriety or identifying jerks.
I wonder if the same thing could happen with innovative startup markets.
You may be assuming that the strike price is fairly pegged at a real value of the company and thus you can make assumptions about real growth of the company in terms of multiple. Short of public markets, this is always a questionable assumption, but in the case of new startups it is almost completely arbitrary. When you start a new one, there is no reason to differentiate between choices in the number of shares varying by a factor of 10,000x or more, and strike prices are almost as flexible.
Perhaps the best reason to pick any number is to pick a large one because of the (irrational) psychological impact that your large absolute number of shares will have in option grants.
I suppose this emerges out of people's naive appreciation of public markets. Smaller companies often have stock prices in the teens. Mature, stable companies tend to hold prices closer to a hundred. Blockbusters like Google go to 400! Etc. These prices are managed with splits and have little to do with the return captured by owners of the stock, but people looking at it from the outside sometimes miss this. That's why I appreciated the article so much. It goes beyond these simple matters.
In my admittedly limited experience, just realizing that there are a number of shares out there (fully diluted or not!) and that this grant translates to a percentage of the company and that the strike price implies a valuation is beyond a solid majority of people I've seen receive stock option grants. Articles like this one are certainly needed to improve education on these matters.
I would say my number one rule is to pick something that is a deeply personal itch that I can scratch. It is hard to have as much motivation to tackle something because I think there might be a market for it as something that I really just want to have exist so I can use it.
In smaller organizations, it is worthwhile to occasionally take stock and realize the extraordinary number of things that you're doing that you have no idea why you do them. Most of those have no value.
They're just awesome.
At first blush, this looks like a way to extend that useful aspects of new teams further by increasing the bandwidth for tracking, communicating priorities and dynamically organizing without losing things. That's how it is different from bug trackers, etc., mentioned in the other comments. It would be interesting to use something like this in a project as mature as 37signals and see what happens.
I will look into it further if it becomes a product.
Another way to look at it is that this looks small in comparison to early equity positions in startups that go on to work out. It sounds like a good way to combat a desire on an engineer's part to roll the dice on that.
It's like working with people who carp about having "a sense of urgency." I always want to set them on fire. We'd then see a genuine sense of urgency. Most of what they actually do is just pestering people.
You should see dollar bills purchased for hundreds of dollars at least.
"The only way to win is not to play the game." </wargames>
We tried buying them a thousand at a time from banks. One time a manager came out to talk to us about it and asked what we wanted them for. We explained and his response was, "So we're going to get them all back."