Ross Cameron Peterson
2) What will you be doing after graduation?
I'm going to go to graduate school at Texas A&M University for a master's in computer science! (Whoop!)
I hope to specialize in CHI, AI, and graphics to strengthen my chances of getting into the video game industry.
3) List your computing interests (HCI, information retrieval, databases, etc.).
Specifically, I'm interesting in haptic sensing, wearable computing, and interactive projection areas combined with context aware intelligent systems.
4) List your computing strengths (a language, focus area, etc.).
Languages: C++, C, Java, Haskell and to some extent, HTML, XML, javascript, CSS, php
It's hard for me to identify a particular strength, but I've had a lot of experience in C and Windows programming, particularly when it comes to using sockets, threads, and GUI elements.
My greatest strength is my work ethic, though, so I can tackle anything you throw at me.
5) What was your favorite computer science project that you worked on and why?
Doing the Huffman Compression Algorithm in data structures in algorithms was particularly interesting to me. I was still very much a novice programmer at the time and creating an program to compress data (I used some Shakespeare works and Moby Dick) and analyze it was kind of cool.
Also most the programming studio assignments were pretty fun.
6) What was your least favorite and why?
hmmmmm
Probably the heap allocation program we had to make for Betatti's 313 class.
I had no idea what was going on and it was waaaay above my head, even if the idea of it was interesting.
7) What do you see as the top tech. development of the last 5 years and why?
...........
Man, that's a pretty broad question.
Microsoft's Bonfire system. It's a contextually aware laptop made possible by cameras, projectors, and internal logic. It makes the laptop much more intelligent and interactive. I have a blog entry for it in my computer human interaction blog.
8) Provide some insight into your management/coding styles. This could include your preferred coding method, how you use line breaks, what time of day you work best, or any other relevant programming-related facts.
Management:
I tend to be a "let's get things done as early as possible" kind of guy and I
usually want everyone in the same place communicating in person when we're working on a project, even if they technically aren't doing anything there. I imagine I can be pretty annoying to teammates because I'm constantly trying to manage schedules and riding everyone's tail to get things done.
Coding: I'm kind of a pack-rat with my code. I comment a lot of stuff out that I might not need anymore because I don't want to throw an idea away. Other than that I try to adhere to good coding style/conventions.
9) Make sure to include a picture of yourself.

Here's another:
No comments:
Post a Comment