There is no surplus of good opportunities for technical folks to co-found something they can believe in. There are plenty of other opportunities of course.

I think the article is solid in that you have to sell the potential technical co-founder that you have a great idea and will add value to the relationship. "decent salary" will get you a contractor for hire, not a co-founder.

You don't have a lot of choice than to network and try your pitch.

I was going to say something about this being flame bait, but I went back to MS's marketing material and it does seem like their vision marketing is at great odds from their execution: http://www.microsoft.com/softwareplusservices/software-plus-...

Unless by services they means software updates, CDDB updates, and downloading Office templates...

definitely should have been "skeptical on collaborating with Facebook"

Number one on any of these lists should be empathy for users. If you don't care about and understand those using your code, you will never be great, only good.

Old media WSJ and nytimes...

I am not up on this but in XML world I would have used XPath. I see there are both JsonPath and JsonQuery gems that seem to be geared for this kind of stuff.

I thought they just query...? Actually, I was just prototyping this in Ruby for porting to C#... I couldn't find anything in c# to do this either. I basically have .NET objects I'm serializing out to JSON then I want to take that JSON and use what I did here and then bring it back into .NET objects. This may not be my final solution (I may opt for reflection in the end) but I want to see this solution through.

They return the objects meeting the criteria and you set the property blindly. The query API I saw has a clone and replace API too which is good if concurrency is a concern.

Oh crap, in .Net there is a OSS Linq to JSON provider I see.

I think the original Team System pricing which was probably there to compete against IBM Rational in the enterprise ignoring they had a much broader customer base.

They eventually folded it into most of the MSDN freebie programs for partners and startups...

If this isn't a nearly $1b testament for real patent reform (not what is going through Congress now), I don't know what is...

A poster child for the Innovator's Dilemma of how traditional management excellence kills disruptive innovation: http://en.wikipedia.org/wiki/Disruptive_technology

I have to agree from my experience at IBM. Those rewarded tend not to be rewarded much by industry standards (years salary at best) and the entire team or even the most meritorious contributors are rarely rewarded.

I know of at least one team that came up with something major that asked for their compensation to be tied to their product success having their idea moved to another team because "they should do it for IBM purely". Of course that product failed for lack of vision and focus.