Aaron Spring Email & Phone Number

Mostly as a result of dissastisfaction with the process for developing the core application platform, we agreed to a management restructure in 2017, resulting in my taking the title of CIO. Kept the Operations group and brought the Development team under my purview. Changed the Development team over from Waterfall to Scrum. Steered a major HTML5 interface component project back on track in the face of customer dissastisfaction with performance. Helped deliver the first fully localized version of the Datalliance application, in French.Throughout this I worked on the team involved in selling the company, culminating in purchase by TrueCommerce in August.

Managed the small group required to keep IT services and the Datalliance production platform going. Oversaw the SSAE 16 SOC 2 process, securing Type 1 and Type 2 reports over the course of a year. Managed various other projects required to the stringent requirements of enterprise customers, including the Datalliance platform's first implementation of SAML federation support.We were at a strategic crossroads in terms of our core database technology platform. As a result negotiated a deal with a major vendor to provide a path forward on a scalable, resilient platform which could meet the expectations of enterprise customers.

During this period I officially transitioned into leading the interface and middleware developers. I helped with the interviewing and recruiting process, and started getting some real sense of what it would be like to manage people. Most of my personal development time was focused on infrastructure, tool chains, and security features. I successfully handed most of that off to other developers by the end. The last significant piece of development work I ever did was to implement a very complicated Javascript chart using the FusionCharts library.

Wrote a web application framework on top of Apache/mod_perl we called "Ripple" that stored all its page configuration data in tables and would query the Oracle schema at run time to align HTML form constraints with table and column constraints. In a sense it had a primative object-relational mapping at the core. It was pretty cool, but we never released it or cultivated a community or anything, so eventually we had to ditch it for something that other developers could be expected to support. I think there's still an internal admin application out there running on it.Around this time I also wrote a Perl program we called "FMON" that simplified running FTP jobs and processing files with scripts and various Oracle tools. That one's still in use, much to my continued amazement. I guess commercial equivalents nowadays are called "enterprise integration" solutions.After that we decided that the web interface to the main product needed a more sophisticated interface component than for order review than we could manage in Ripple or HTML in general. I taught myself Java at that point so we could do a client/server Swing applet with J2EE on the server side. That experience led me to choose Java (pre-Sun acquisition by Oracle, ugh) as our go-forward interface and middleware platform. Near the end of this period we recruited a couple of young developers and they helped me rewrite the whole interface in Java using Apache Tapestry.

Anthropology

Computer Science