Re:Ask HN: How do you keep up with changing technologies?
by WesleyJohnson on Monday November 16, 2009 @04:16AM
(#944207)
Thanks for the link, I've added it to my bookmarks for stuff I wanted to review in the coming weeks and will definitely be checking it out.
I also see what you mean about being too quick to jump onto the bandwagon. I realize it's in debate right now, but there IS talk that Linq to SQL will be replaced by Linq to Entities. So with that (and the comments people are posting about learning the meat and not the seasoning), not diving into it a year ago when I first heard about it may not have been such a missed opportunity after all.
Some of our shipping products are based on VB6, while some of the others are .NET 3.5. Generally, if some new technology adds an edge, like Entity Framework (the shiny new name for "linq to whatever"), then we use it. Also, for internal tools, any new technology is fair game. So our internal tools have all sorts of bizarre stuff in them, and if that new stuff is useful, we end up using it elsewhere.
I don't blog, but I'm thinking of doing it for some educational projects. Making a public promise to do something generally makes you more likely to go through with it and do it: whether it is a project or losing weight. One example is the "build your own CAB" [composite application block] series. http://codebetter.com/blogs/jeremy.miller/archive/2007/07/25... Something like this project might be what you're looking for to push yourself out of your "comfort zone."