Triple Shot Links # 9
I’m finally recovered from my 10th marathon in New York this last weekend, which means I’m no longer walking down the stairs like a 90 year old man.
Although I was disappointed that there was no prize money for 15,083rd place (out of 40k runners), I still had a great time at the world’s largest marathon. I even managed to run my second negative split ever, which I attribute to not wanting to run behind Borat anymore (pictured to the right).
You can curse my running partner for capturing Borat in all his bare-butt glory on her camera phone right before we passed him.
- How Hard Could It Be?: The Unproven Path - An interesting behind-the-scenes look at the making of StackOverflow from Joel Spolsky’s perspective. You can find more interesting tidbits from this Hanselminutes podcast with Jeff Atwood, such as the confession that they are running both the database and web server as well as dev, test, and production environments all on one hosting server! You’ll especially appreciate the shoestring budget, fly-by-the-seat of your pants approach to building this popular site if you’ve currently stuck in some heavily regulated, corporate development hell.
- Deep Zoom Version of 4.0 .NET Framework - Even if you know you will be stuck in legacy mode for the rest of your life and therefore don’t give a hoot about the 4.0 framework, you’ll still want to check this site out. I nearly wore my mouse scroller out playing with the zoom feature. It’s mesmerizing.
- Microsoft kills Linq to SQL - Oren stirs up an interesting discussion on his blog by commenting on ADO.NET teams’ recent announcement that they were basically ditching Linq to SQL in favor of the Entity Framework. I thought at first that he was just reading too much into the post, but then I saw Damien Guard’s follow-up post on the topic, which seemed to confirm Ayende’s interpretation (albeit with slightly more spin control).
When you just need to
Spin control?
[...] Triple Shot Links #9 (Russell Ball) [...]
@Damien,
Sorry if spin control sounded harsh. I didn’t think that you were being disingenuous or even that MS necessarily made a bad decision from a strategic standpoint in deciding to consolidate their efforts and redirect most of the resources to the Entity Framework.
I do, however, think that many developers who decided to invest time in learning the technology and building it into existing apps probably gave a collective groan after they got the news.
Even with promises of future support, it’s hard to feel like you haven’t wasted a bunch of time when your technology of choice doesn’t make the strategic cut.
Choosing a technology that will help your career and existing applications flourish already feels a little bit like playing the stock market. What you guys now are experiencing is emotionally driven “sell off” that follows suspicious news in the market place.