My Online Portfolio
I have worked in this industry my whole life. Over the years I have written or led teams and produced millions of lines of code. Most of this code is the property of those I worked for.
I have always taken intellectual property seriously. Only on occasion do I feel I can post work I've contributed to with a clear conscience.
If sharing the code is not possible I include links, or screenshots, or other documentation.
I have a github account, in fact many, but I lose track of the projects over the years, and only actively participate in a few that I have an interest in, and contribute mostly as a mentor.
My public github account is in the links at the footer, but I dont put anything revolutionary there because I want to keep my rights to the content and concepts.
This page is under development. This is a gulp based project hosted on AWS.
At MHE I was a Software Engineer: Lead, responsible for development teams. I worked on two large projects.
MHE premier project is Connect, a product designed to assess, track and manage college curricula. I led a team to replace the assessment architecture, a natural follow on from my widget framework work at GE Fleet. This evolved into Ember widgets and components.
The results of our work is available online at Connect.
The second project was to build an ontology of learning using MHE 500 peta-bytes of high quality content as source material. This involved many steps.
This product was to assist other MHE projects among them Create, an ebook initiative
One of my projects at McGraw-Hill Higher Education (MHE) my team developed several prototypes of a machine learning application to create subject taxonomies which were used to populate a graph database on Allegrograph.
I led a team to gather requirements, data models, and assess existing technologies. Final stages of my involvement were to build a prototype tool to manage the machine learning, taxonomy creation, and ontology architecture.
I will post the taxonomy machine learning app, sans the proprietary content, and early ontology user interface prototype.
This is not the actual data model, but in general.
At GE Fleet I was hired as technical lead for architectures and team lead and mentor. The environment was Agile in a very pure form and it was challenging to develop a replacement system with the team spread over the northern hemisphere.
The objective was to replace a mainframe system to manage the leasing of large fleets of automobiles which had been developed on IBM mainframes. The 'lore' was that the system was so hard to use that an agent completing a leasing contract for Mary Kay had mistakenly ordered 50 pink pickup trucks with manual transmissions. I am not sure if that is true or not.
The framework needed to be simple, and it needed to be simple to write widgets. The framework I created was in two parts: a container and a widget. I have a long history with web components and most of them are neither, and have serious security issues, mostly because people break the rules. This framework was simple, under 2 k in total, and had no security issues, and you could cut an paste html to create a new widget.
I kept the code for this but I dont publish as I'm not sure who owns it since GE Fleet was sold a few years ago. The framework I build was very good, built from the ashes of a former framework that no one could get to work. I take a bit of pride in this.
My work part of the book "Lean UX" Page 45
I have many other projects for AI pacemaker diagnostics, rule driven and efficient in C# -- quite proprietary. I have worked on a couple defense related projects that I shouldnt even talk about. I will continue to augment this page as seems reasonable, keeping in mind intellectual property, and federal law.
Often when I apply I'm asked to do tests for compentency. I have been doing this all my life, there is little I havent done already. I understand the attraction of tests, and why in some cases its a prudent choice. I think I may have proven myself already, please dont ask me to do any more.
Some examples of 'tests' I've completed lately:
I think these are a waste of time, mostly mine but also yours. I have often interviewed engineers, and I can tell in 5 or 6 questions whether they are competent or not, none of which involve writing code in an impossibly stressful situation.
I want to know if they think, if they know how to do research not just start writing a loop, if they are patient, if they are smart, if they are personable.
After a lifetime in software, these are some of the things that matter.
Still, I have done too many of these tests, so please dont ask me to do any more :)
Please check the ephemera below before you ask, I've probably already done it anyway.
I have a test and experiments page at More stuff