Weekend Link-o-mania

For the last few weeks, things have been crazy at work. I have not been able to devote as much time to blogging as I would like. Although this will continue for some time, I thought of doing something different. So, taking a leaf out of Sam Gentile's "New and Notable" posts, here are few pointers that will keep you and myself even more busy. All of these are excellent reads. So here we go:

  • Microsoft Corp. Chairman Bill Gates testimony before the Senate Commerce Committee against the evil of SPAM.

  • Kevin Werbach is anticipating a post-Web, post-PC world,
    Technologists just can't stop thinking about tomorrow. The future always looks bright; the question is who and what will help get us there. Even the grinding downturn of the past three years has hardly dampened this belief among entrepreneurs, technology executives and investors. Will broadband be the hot new development that lifts us out of the doldrums? Will it be Wi-Fi? Online gaming? Web services? Homeland security? Those are the wrong questions.

    If you want to know where you are, you don't study a map to determine where you're going. You trace back the steps from where you've been. Over the past several years, "where we've been" in the technology world has changed. While we were all focused on the dot-com bubble and the subsequent bust, "yesterday" shifted. It used to be the PC revolution and client-server computing in the enterprise; now it's the Web.

  • Rob High of IBM talks on Service Oriented Architectures (SOA). This is another acronym buzzing around the industry and this conversation highlights the basics of SOA. I missed attending a talk on the same topic last month by Drew Robbins in the Columbus .Net Developers Group meeting. He has posted the presentation on his blog.

  • Kalsey provides a web interface to the Bill Zeller's button maker application. Cool. While at Kalsey's website, Check out the CSS tabs with Submenu's blog which is the best I have also seen.

  • Wes Haggard shows how to determine the .Net Framework version by retrieving the current Framework Directory. Also check out the comments for even more straight forward way of doing the same.