Internship: Week One (Continued)

In which I actually go to work.

I refuse to actually read the previous post, because I'm sure I was word-vomiting like a fifteen year-old girl with a Xanga. Maybe I'll get back into the swing of writing and create something approaching prose.

At any rate, I said I would continue the saga of week one. I left out that on Sunday we walked to all three entrances of National Instruments, attempting to scout out the best way in on our first day. At all three, we found eight foot tall gates with ID scanners. As none of us had IDs yet, this presented something of a problem. Fast-forward to Monday morning, and all the gates are wide open; one less thing to worry about. National Instruments hired 220 interns this summer, and 88 of them started that day, so there were quite a few of us. We got ID badge photos taken and were shepherded off to breakfast with our mentors/managers. My mentor's name is Mark, and he seems like a pretty swell guy. He (and a lot of NI) seems pretty young, probably under thirty. He told me (finally) what group I would be working with--PXI. Essentially, PXI is a modular instrument system consisting of a PC motherboard (controller) and a series of instrument modules communicating to the controller over PCI (now PCIe), just like expansion cards in a desktop computer.

After meeting Mark, I was put back into the general population of interns for orientation. As you can imagine, this was a bunch of PowerPoint presentations and forms and a tour--nothing exciting. After being oriented, we were reunited with our mentors for lunch. Mark, a two other guys from the group, and I went out to a burrito place across the highway called Freebirds. It's a chain that apparently started in California. Imagine Qdoba or Chipotle, but with bigger burritos and they serve beer. The pork burrito I had was pretty good, but oddly cylindrical.

After lunch, it was time for something new and exciting: LabVIEW training. (This is not actually exciting.) I've been programming in LabVIEW for almost three years now, and I probably had more experience going into training than anyone else in the room except for the instructor. Needless to say, day one of training was wasted on me. They let us out of training around 4:30 so we could go back and set up our computers and whatnot. I went back up to my cubicle to find that my computer would be an actual PXI chassis, which is kind of cool. It's got more horsepower than any desktop they could have scrounged up for me (~Core i7 at 1.7Ghz). I started setting things up, then finally got out at around six, making for a ten hour day.

When I got home, we went on another shopping expedition so that one of my roommates (I never mentioned this in the last post, but he didn't arrive until late Sunday night) could get some food. I spent the evening reading more of Odyssey Two before going to bed in preparation of another day.

Tuesday was pretty uneventful. More LabVIEW training (I did actually learn a thing or two), and setting up things on my computer. Wednesday was a bit more exciting. Once every quarter(?), NI buses all their employees down to a big auditorium for a Company Meeting. There just happened to be one on Wednesday, so LabVIEW training ended after lunch and we went down to the Company Meeting. Essentially, it was a bunch of keynote address-type things and speeches by assorted higher-ups in the company. Some of it was pretty interesting, some of it less so. Afterward, I went back and finished setting up my computer and whatnot, then clocked out for the day.

Garrett will be pleased to hear that I've started watching Doctor Who. I never had anything against it, I just never really had the time. Now that I've got scads of time, I'm working my way through the second season. I've seen bits and pieces of seasons 1-3, but I've missed quite a few episodes. I think there are actually a few episodes of season 1 that I've missed too. I should go back and check.

On Thursday, I LabVIEW training until lunch. I now know how to do a lot of things in LabVIEW that I didn't before, including event-based programming and multi-process/multi-thread control. I don't know that any of this will ever be useful, but now I know it. After lunch, I spent a few hours going through assorted slideshows on assorted policies and practices, then went to the deck party. The deck party was in honor of the previous day's company meeting. Lots of free fried things, beer, wine, soda, and music out on the patio between buildings B and C. It would have been a lot of fun if I had friends around here, but even so, free food is free food.

At this point, I guess I should touch on the friends bit. I'm not really trying to make friends here. I know that's cold and antisocial and unhealthy and whatnot. It's not that I'm actively avoiding people; I'm just not putting forth the energy to be social. Having friends is great and all, but I'm here for twelve weeks, and I'm here to do a job. It's a lot less stressful (for me) if I don't have to think about the social aspect. I'm sure most of the human race would disagree, but for the most part, life is easier on my own. There are times when I wish I had people to hang out with, but I that doesn't mean I'm about to get chummy with a bunch of people I don't know just because I happen to live or work with them. If I meet some interesting people, I won't avoid them (much), but in the mean time, I'm fine by myself, thank you very much.

Somewhere between Tuesday and Thursday, I finished Odyssey Two. It's a good book, and I'll leave it at that. I've heard the other two in the series are not as good as the first two, which is a shame. I'm deciding what else to read this summer. I may invest in a Kindle account and read on my laptop (that's how I read 2001 and 2010, although I read them in PDF form). I figure if I go with a Kindle account, I can either buy a Kindle some day or just use my phone/laptop/future tablet and the Kindle app.

In other news, I discovered on Thursday that my laptop really cannot handle Fallout 3. The lag is just terrible. This is sad, but not entirely unexpected. I'm going to build a new desktop at the end of the summer so I have something to game with. In keeping with my tradition of naming my computers after fictional intelligent machines and AIs, I'm thinking her name will be Athena. If anyone wants a new desktop, I'd love to make her a twin (Boomer).

On Friday I finally learned exactly what it is I'm doing this summer. Without going into too much detail, I'm essentially designing a breakout board for a PCIe controller chip that's being used as a load-tester for PCIe/PXIe. I'll be doing the schematics and layout for this load tester, which will spam packets across the bus to the controller to test how it can handle full loading, even at PCIe 3, which isn't out yet. I cut out early because I'd already worked 42 hours this week.

I'm once again tired of typing, so I'll stop here, but as promised, I got through the week. Don't expect a blow-by-blow of my life in future posts. I imagine that would get very boring very fast. I just figured I've had enough people ask about my week that there was some interest. I'm going to go eat now (yes, at quarter after nine).