Introduction

I am Matt Moss. I've been to Germany. I can set things on fire with my mind.


Post Graduation: I will be doing... things. Current plot is an odd (and likely painful) combination of Grad School and continuing current dual employment at the Energy Systems Lab and at CCG.

Computing Interests: Physical Computing, Circuits, Robotics, Distributed Systems, SkyNET

Computing Strengths: Systems, Databases, Backends, Thick Client UI, Distributed/Networked Systems, Physical Computing, Microcontrollers, Basic Electronics; Language wise: C#, C, C++, Python, Java, Erlang, to variable degrees.

Favorite CS Project: Freshman year, in a 221 class with 4 students; I implemented Ticket To Ride on top of GLUT. The large range of work (data representation, simple AI, supporting tools for capturing polygons and paths in the image of the game board), combined with the relatively fun final product makes this my favorite.

Least Favorite CS Project: The Logisim Processor in CSCE 312. The project itself was interesting, and something I learned alot from. I'm glad we did it. But Logisim is an awful simulator for complex circuits. It'd come to 'undecidable outputs' because we included a sub circuit. That was also a group project, where in it was largely impossible to merge what different people did into a single file. The project wasn't as well thought out as it needed to be.

Top Tech of past 5 Years: Consumer level Multi-Core processors (and eventually Many-Core). This has forced a rethinking of how applications are written, and is leading into a rethinking of how systems are designed.

Alternatively, as far as Tech Product, I think the Arduino represents a 'top tech product'. It's lead to a surge in DIY electronics, which has many interesting implications.

Management Style: Here is a task. I'll nag you about it incessently until it is finished and working. If you can't do it to my standards I'll do it myself.


Coding Style: If starting in a fresh system, get a functional prototype of each 'I have no idea how to do this' component, to get an idea of 'this is how I do this'. Then begin work on the full scale system, integrating and designing as you go along.

On an existing system: If its unusable, or more painful then its worth, scrap it and rewrite it. Otherwise try to follow the conventions and patterns of the existing system.

Misc: Best/Most_Productive Development time has been statistically proven to be from 10pm-2+am. Outside of these hours, my mind has a strong tendency to wander off onto Hulu, random reading, or etc.