I was going to jump in on the "discussion"/disagreement between whether or not the stats claimed by Windows Live Spaces are "real" blogs. (Heck, I can’t even decide which posts to link to.. just go to this post and read forward.) Just what is a blog anyway?
It’s fun reading all the flame wars that happen in the virtual realm of things (it happens everyday on Slashdot), but it takes a lot of energy out of you too. Arguing about numbers really isn’t that interesting anyhow–I myself do have reservations on how WL Spaces calls itself #1, but I’ll leave that for later. I’m not an expert anyway.
Anyway, I like making trips down memory lane better. So spurred by Dare’s "Intern Experiences" post, here’s my impressions of being an intern (twice) in MSN.
For the first internship, I think those "initial feelings of awe" really never wore off. It was my first time far away from home (it was 5h by flight instead of 5h by car to school), first time touching any ‘real-world’ software, and surrounded by Waterloo interns that were on their second (if not third) internship–and they were all 21+. 😐
The truth is that an internship isn’t just about the work you do. Sure, it’s a 3-4 month long interview, but a big portion of your time here is spent enjoying the weather (unless it’s a fall/winter/spring internship), meeting other interns from other schools, driving your rental car, exploring the Pacific Northwest, having evenings and weekends free to spend the cash you’re earning, etc.
So I was having a hard time coming up with work-related stuff to write about in this post. There was that time a couple of Messenger interns and I pulled an (almost) all-nighter pulling together stats and other stuff from an informal survey we sent out to friends and other interns for a presentation on MSN Messenger competition and on how Messenger just couldn’t stand up to the college crowd. That was fun. People on Messenger didn’t understand that no one in college used MSN.
But the *one* thing that I did as an intern that had lasting impact on me? It hit me this morning as I was driving to work. It was obvious. It was the same spiel I give to everyone when I talk about my internships.
During my second internship, I worked on a feature known as "TOU." I think Danny may have said something (in tongue-in-cheek fashion) to the effect of, "I hear that you’ll be working on something that will actually make us money!" on my first day. It wasn’t a bad project. But it never shipped. It came close several times, but it wasn’t to be. In fact, it took 3 years before the code was actually removed by Steve a month or so back.
The ‘cool’ part, though, was a subset of that feature, known as "Service IMs." Essentially I managed to hack in a way for our Operations folks to send an instant message to every single online user. Call it spam (or spim) or whatever you will, but that was power. In fact, the feature was so useful, that they shipped it as part of a service pack to upgrade everyone to MSN Messenger v5. (Remember those IMs from .NET Messenger Service Staff?) Annoying, yes.. but it was still a better experience than suddenly getting a pop-up telling you that you had to upgrade right then and there or forego a connection to the network. Friends would tell me how super annoying that ‘feature’ was (since it kept IM’ing you everytime on sign-in if you didn’t upgrade) and I would gleefully let them know that I did that. The ability to send unsolicited IMs to hundreds of millions of people worldwide? Hell yeah!
So what would I do if I was a mentoring an intern now? I guess I’d try to get him (99% of devs are male) a self-contained project (so he could hack away at it) that was cool (so he would have fun), had customer-exposure (so he could point it out to all his friends–this is difficult when working on a back-end service), would ship soon (ditto), and allowed him to understand the architecture and complexities behind running one of the biggest services on the planet. Working on the thing from design to implementation to testing to shipping would certainly be nice, but is often difficult due to the length of a 3-4 month internship. I would also try my best to hide any cynicism from my intern. I did a horrible job of that with one of the interns last year (who came back a second time, funny enough; but will be coming back as a PM for his third internship.. oops). I think I’d have a pretty high bar too; if he didn’t impress me, I wouldn’t waste my effort.
Interns tend to have their heads in the clouds (definitely true for me), so it’s not that tough to impress–especially first-time interns.
Interesting tid-bit/tip: I have it from an inside source that I came *this* close =><= to not getting hired as a full time employee (and things would be very different today). HR had their reservations about me, due to me not answering a question to her satisfaction. What I would give to see that interview feedback today. Just goes to show that even if an internship (or two) are 3-4 month long interviews, exit interviews are still important.