wrapping up
Acomplishments
I have been keeping a blog of my work through out the semester, which is a good thing because much of the work I did produced no tangible results. One of my greatest accomplishments this semester was to convince the SWITCH team to use the Mambo C.M.S. (content management system) instead of Plone. Plone is written in python, Mambo is written in php and SQL which are languages I am much more comfortable with, and by the way are highly sought after job skills. But I did not push for this change as a selfish act of not wanting to work in a new language; I pushed for the switch because it is a better system plain and simple. The modularity of Mambo allows us to create multiple issues of the SWITCH journal with a single C.M.S.. As part of my responsibilities this semester I also created an informative “how to” document to instruct future semesters how to build the essential elements required to create more issues. Aside from some technical troubleshooting and installation of custom modules, I also helped Aaron Siegel with the backend data base side of his Pacific Rim Visual Directory Project. I build a small application to store the data his visualization would run off of. I worked with him to get his project to submit data directly to the database and creating a text output file that his flash application would read its data from.
Over the course of the semester I have worked a lot with creating custom skins for the software I am working with. Skinning software, the practice of applying a customized style or interface to a program. It does not affect the functionality but it can increase effectiveness of a product to perform a specific task. Skinning software is kind of like changing clothes. Some are merely for aesthetic value, the kind you would wear for a night out on the town. Some skins promote a specific type of interaction, like a uniform the skin may help make the purpose of the program more apparent. Additionally some skins may alter the configuration of the interface and increase efficiency in the end user. The skin is proof of our culture effecting software development. There is a natural desire for variety, the software skin allows us to break the often drab and boring appearance of the software we have incorporated into our lives.
