Projects

I really like working on different projects and below are a few that I found to be particularly enjoyable.  Please don’t judge me too much for the code quality on these…I’ve learned a lot since even the most recent project here.
  • http://www.mcirclek.org/ I was the technology committee chair for the 2012-2013 Circle K Year and served on the technology committee since I got to college up to the end of that term.  In my time on the committee, I completely redid the back end of the calendar resulting in major (100x+) speed improvements across the entire site.  The fun part of the site (and the part I have put the most work into) can be directly accessed at http://mcirclek.org/calendar.php.
  • http://www.micirclek.org/ I was the district technology committee chair from 2011-2013.  I did not make any major improvements to the website itself during my time with the committee, instead focusing on more fun projects such as an online monthly report form for club secretaries or a calendar that any Circle K could use (see below).
  • Circle K Calendar Framework (https://github.com/micirclek/ck-calendar) This is a calendar framework based upon the University of Michigan Circle K’s calendar that allows any Circle K club to get a calendar set up very quickly.  Right now I am finishing development on it and working to promote it within Circle K.
  • Circle K Portal (https://github.com/micirclek/cki-portal) This is a simple site that handles collecting MRF submissions from different clubs within Circle K.  It’s a replacement for a much earlier project I did (that had even more embarrassing code) and is now designed to handle multiple clubs and districts (but only one organization so far)
  • Simple Operating System (https://bitbucket.org/jpevarnek/sos) This is an operating system.  I worked on it mostly at the end of my freshman year and have been meaning to find time to get back to it and pretty much redo the entire thing.  It includes its own (very simple) filesystem, the ability to run other programs (kind of a pre-requisite to it doing anything), and a very basic form of memory protection.  Once I redo the basic libraries it has now, I will most likely start working on adding support for virtual memory.
  • Automated Nerf Turret This is a project that I worked on for my Engineering 100 class freshman year.  Using a DE2 microprocessor and the E100 assembly language (designed by Peter Chen) my group constructed an interface to a Nerf Vulcan EBF-25 Blaster that could either have the firing be manually controlled through a user interface or be automatically controlled based upon color detection.  I took the lead roll for software design, user interface design, software-hardware integration, documentation, and reporting as well as playing a minor roll in hardware construction.  In addition to working on the project, I also put together an assembler for the E100 language as well as a simulator for non I/O dependent items (it started as me wanting the computer to do a ridiculously simple simulation for me and then just expanded to making the entire system) that is available at https://bitbucket.org/jpevarnek/e100.