Michael C. Riehle Software Developer
aikimcr@gmail.com 3419 Pioneer CT
http://github.com/aikimcr Stockton, CA 95212
https://codepen.io/aikimcr (209)403-2562
https://www.linkedin.com/in/aikimcr/
PRIMARY SKILLS!
JavaScript
HTML5
CSS3
SASS
NodeJS
GIT
BackboneJS
jQuery
Test Driven
Development!
JOB EXPERIENCE
June 2022 - Present
As a result of layoffs at TogetherLabs, I have been working on skills development. In particular I’ve been working on
a couple of projects aimed at bringing me up to speed on React. These can be found at my GitHub:
•
https://github.com/aikimcr/CurrencyExchangeList
•
https://github.com/aikimcr/bombay_server
•
https://github.com/aikimcr/bombay_client
Technical Skills:
JavaScr
ipt/
HTML5/
CSS
SASS
React
NodeJS
GIT
January 2015 - June 2022 IMVU, Inc.
Redwood City, CA
Software Development
Technical Skills:
Javascript
HTML5
CSS3
IMVUJS
BackboneJS
Handlebars
jQuery
SASS
GIT
PHP
Electron
Test Driven
Development
Senior software engineer on the IMVU desktop line of products including IMVU Studio, where I took a lead role for the
last few years I was there. I was instrumental in implementing strong but not intrusive code review practices using
GIT pull requests. I helped to encourage and enforce Test Driven Development. I actively maintained not only our
primary code base, but our infrastructure libraries. I was responsible for significant improvements to our internal
testing and UI libraries.
I did do some work in development on the PHP backend for the IMVU product although it was not a primary part of
my duties. As a result I can read and make simple changes to PHP code.
July 2008 – December 2014 Aruba Networks, Inc.
Sunnyvale, CA
Software Development
Technical Skills:
HTML
CSS
Perl
Javascript,
NodeJS
Unix (Linux)
SQL
Google
Closure
I started out at Aruba doing backend development on the Airwave Network Management product. This was largely
focused on SNMP management of an assortment of networking equipment. I later moved the fronted after a brief
period in a Voice Of the Customer position.
In the frontend I was responsible for helping to implement the beginnings of our new UI using Google Closure. As our
frontend became increasingly responsible for API development to retrieve information from the database, I
championed the use of NodeJS to develop APIs. This allowed us to use Javascript in both the browser and APIs
which, in turn, allowed sharing common code, particularly with regard to internationalization (i18n).
November 2005 – May 2008 Vindicia, Inc.
San Mateo, CA
Software Development
I developed and maintained a network based interface between Vindicia’s CashBox product and various Payment
Processor services. These services all had a different approach to authorizing and settling transactions and the
interface needed to make these differences transparent to anyone using the system. Requests and responses were
formatted in either flat file formats or XML, depending on the provider.
May 2001 – November 2005 New School Aikido
Stockton, CA
Training and Teaching
I left Tivoli Systems as of June 1, 2001 to concentrate on my training in Aikido. As part of this I took on
responsibilities for teaching at New School Aikido in Stockton.
August 1997 – May 2001 Unison Software/Tivoli Systems Inc.
Santa Clara, CA
Product Development
I was an architecture level engineer on the Maestro product which ultimately became Tivoli Workload Scheduler. I
was a key player in transitioning responsibility for the product to the Tivoli team in Rome, Italy.
Education
1979 Chaminade University Computer Science
1980/1981 Kapiolani Community College Accounting
1984 American Management Association Project Management
1984 Hewlett Packard Systems Programming
1985 Hewlett Packard System Operator
1985 Hewlett Packard System Programmer
1995 UCSC Extension C++ Programming
Other Relevant Items
Over the years I’ve generally been the quick study in the group who saw opportunities to improve the use
of tools or ways to implement new tools effectively. This is in part because of my constant exposure to a
wide range of tools. I have occasionally been responsible for System Administration tasks as an
incidental part of my day to day responsibilities although I would certainly not describe myself as a
System Administrator. Many of the products I’ve helped to build have endured in day-to-day use long
past what people expected of them.
