As the first integration developer at Stack Exchange it was my job to fix any pebbles that got in the way of our team's ability to climb the proverbial mountain. My primary role was sales support development, lubricating the integrations between several homegrown systems and the salesforce.com crm. I worked with our executive team to determine project requirements and design solutions and with our development team to see them executed successfully.
In my two years I led a variety of projects, including a trello-like board tracking deals as a better front-end for salesforce, an overhauled commissions accounting system, a sales dashboard showing our team up-to-the minute status information and realtime data replication from salesforce.
While a technical consultant I translated customer requirements into well-tested and maintainable code. The projects varied considerably – I'd be designing responsive and accessible user interfaces one day and complex yet bulletproof business logic the next.
I led the implementation of a continuous integration server based on jenkins and the development of build plugins for grunt and ant, though I also spent time supporting our business analysts with utilities to ease the burdens of salesforce.com configuration.
In mid 2012 I took on leadership of our developer book club from Will Saunders, and I played an active role mentoring junior developers of Beyond to ensure they have the skills they need to succeed.
I designed and built a portal to enable bioinformatics students to run command-line utilities over the web. The legacy system ran a tomcat server and jsp but the rest of the stack at IT Services is lamp, so I was brought in to rewrite it in php.
I developed an active interface based on metadata for each of the cli tools. The binary's location, parameter types and various modes of operation are all configurable for admins, as is the help text and associated tutorials. Users are given a role based on single-sign on with their university login.
We were able to introduce a number of valuable features in iterations after the initial release. After speaking with the developer who took over for me, it seems the system has been flexible and resilient since.
Researchers on Dr. Morton's team look at the mechanisms of the nervous system response to changes in environment, with a particular focus on adaptations to trauma and injury. A significant portion of the quantitative data studied comes from a realtime motion tracking system.
I developed programs supporting a variety of the lab's interactive motion tracking experiments. Because the public api is rudimentary, I designed an object-oriented facade that the lab's researchers (who know some c++) could then use to construct novel experiments.