Wow, its been awhile since I posted anything.  And what a post I get to make.  This will be my last entry under the topic of being a Software Engineer.  At least for the foreseeable future.  I am now officially a Program Manager for Microsoft.  I plan to keep blogging here, but I may focus more on the personal side of things and let any professional content go to my new MSDN blog at http://blogs.msdn.com/jeremykelley  I'll try and get something started over there soon.  I can't imagine I have that big an audience that this news will mean anything to, but it may give me enough reason to try and get my website upgraded to the latest version of DotNetNuke, it won't matter as much if I break everything.

-Jeremy

Robert Scoble is performing an interesting experiment to track the various search engines out there.  The test is simple, convince a bunch of people to put the same wacky string into a blog post.  In this case the string is: brrrreeeport  By participating in this I don't know if that makes me a real part of the blogosphere or just another bored engineer who doesn't mind being a lab rat.  Either way this should be an interesting test.

-Jeremy

I knew way back in high school that I was going to end up being a software engineer.  I had a pretty good aptitude for computers and I enjoyed playing around in Pascal and learning C++.  I was pretty far ahead of a lot of people in my early programming classes, although WAY behind my really smart friends. 

When it came time to start picking colleges it was getting a little rough.  My grades in school were not what they should have been.  And it was my own fault.  But it was starting to limit my choices of where I thought I could go.  It came down to going to a state school in another state for Creative Writing, or going to the Rochester Institute of Technology to study Computer Science.  Thankfully I got in to RIT.

So what's the point of all this?  I love being a software engineer.  Designing architectures, learning new technologies, writing code.  I enjoy every ...

So I asked someone what may have been a dumb question.  Dumb only because I didn't exhaust my resources on my own before asking.  Since I get frustrated when people do it to me I figure I owe it to the person I asked to get the info out there in another spot just in case someone reading over here is interested.

The question at hand was about good sources for interviewing tips.  The big mistake I made was not fully reading the website of the person I was asking the question of.  In this case I got lazy, I forgot that looking at the latest posts in Bloglines doesn't show all the other important content on the site.

Today's site in question: http://blogs.msdn.com/jobsblog  The team over there provide a TON of information about all aspects of recruiting, and specifically interviewing.  Gretchen (of the afore mentioned JobsBlog)  ...