Co-founder and technical lead for a cloud-based service provider targeting the Veterinary Practice Management software industry. I brought to production quality a prototype web site which enables Veterinary Doctors to submit patient referrals to larger and/or more specialized care providers. The site enables real-time electronic communication between referring doctor and the care provider, including insight into procedures performed such as labs, imaging, prescriptions, etc. The site is based on MVC5/C#, with connections to the Practice Management software via proprietary API's and direct SQL access.Currently developing a synchronization tool which enables the web site to interoperate with a wider range of Practice Management products by translating and synchronizing information between differing database schemas. This is being developed using a combination of technologies which includes C#, Windows Services, ASMX, SQL, and various proprietary APIs.

Co-founder, and lead engineer for entire lifecycle of Tactical Software's COM Port Redirector product line. Performed software design, coding, test, and release engineer tasks. Managed a small team of contract developers and a test engineer to bring each new product revision to a successful release.The drivers are written in C++, and shared a common core codebase that is portable across Window 9x, NT->10, and some Linux systems. I am responsible for most of the GUI implementation, also written in C++ above MFC (remember this product started in 1996!). I am also responsible for the build system (originally implemented in bash, but recently ported to PowerShell), as well as the installation kits which are implemented using Windows Installer.The drivers require Microsoft Authenticode Signatures to work in more recent version of Windows, the process for which I was responsible for integrating into the build system. I am responsible for keeping it up to date in a rapidly changing landscape of signing requirements from Microsoft.

Worked under contract to prototype an embedded ethernet switch using the Micrel KSZ8999 chip.The purpose of the prototype was to test out non-standard connectors and electrical couplings on Ethernet ports. The final goal being to use HDMI jacks rather than RJ45, and to bypass magnetic coupling if possible.As the lead prototyping resource, I worked with the lead hardware engineer to:* Evaluate different chip designs* Define a design roadmap for scaling port count for production units* Perform Circuit and PCB design* Fabricate the prototype PCB using milling technology* Populate the prototype using surface mount/reflow techniques* Debug the final prototypeTo aid in configuring multiple units, I developed a prototype SPI EEPROM burner, based on a Raspberry PI and custom circuit board containing a ZIF socket capable of holding two EEPROMs. This was housed in a custom-designed 3D-Printed enclosure.The EEPROM burner contained custom C# software to track Ethernet MAC addresses, allowing the user to program up to two EEPROMs at a time, with a single button press ensuring that each EEPROM would contain a unique MAC.

Worked under contract to prototype an embedded controller to monitor a mesh-connected power and water meter product. The "Caching Server", as it was nicknamed, integrated a Raspberry Pi, LiPo powered 5V UPS, and a I2C RTC shim board. Those components were then connected together inside an off-the-shelf acrylic case.It was intended to be a proof-of-concept to address several shortcomings in the ease of use and reliability of the mesh-networked meters. It worked in the background to frequently poll the meters on the network, interpolating information when any given meter was inaccessible. It also served a set of web pages to provide usage reports from the network of meters.Skills Involved in this product included:* C#/.NET 4.0 on Mono* ASP.NET* Embedded Linux (Raspbian)* Node.js* Redis* REST APIs

Worked under contract to prototype a portable diagnostic/configuration device for a mesh-connected power and water meter product. The "pod", as it was nicknamed, integrated a Raspberry Pi, I2C-connected 2-line display and button pad, plus a USB battery for power. Those components were then connected together inside a custom-designed 3D-Printed enclosure. It greatly improved productivity in deploying meters, providing an easy way to perform firmware updates, collect diagnostic information, and re-configure installed meters.Skills Involved in this product included:* C#/.NET 4.0 on Mono* Embedded Linux (Raspbian)* Shell scripting for turnkey updates to the pod firmware* Windows Installer for product installation

Worked under contract to develop a PC Application (WatterView) for a mesh-connected power and water meter product. The meter implemented USB for configuration and calibration purposes, and ZigBee mesh connectivity so that it could be polled for consumption data by WatterView. WatterView derives much of its functionality from WattView, but with a workflow intended for the target market of power metering for docks at marinas:* Maintain an inventory of meters in use, include dock location information* Periodically poll usage data from the inventory of meters into the database* Maintain a customer database, and from that generate invoices for power and water consumptionSkills Involved in this product included:* C#/.NET 4.0 using WPF* Database Design* Entity Framework for projection of database contents into C# entities* Visual Studio Blend and Adobe Illustrator for creation of graphic design elements* Windows Installer for product installation

Worked under contract to develop a PC Application which configured and calibrated a Viscosity Measurement Instrument using a MODBUS interface. The hardware was accessible via USB, RS-485, and Ethernet.As with previous clients, I employed custom Graphic Design to give the UI a professional look in line with the client's brand.Skills involved with the product included:* C#/.NET 4.0 using WPF* Visual Studio Blend and Adobe Illustrator for creation of graphic design elements* Windows Installer for product installation* MODBUS* XML

Worked under contract to develop a PC Application which configured and controlled a 802.15.4-based mesh network of controllers for industrial LED lighting. The mesh network was controlled by a central gateway with access via USB, utilizing SD storage to retain configuration and control settings.As sole developer of the primary UI to the system, I played role in enhancing the overall product, including:* Custom Graphic Design to give the UI a professional look in line with the client's brand* Streamlined workflow, suggested and implemented enhancements to the feature set of the product.In addition to PC development, I aided in embedded development to allow the firmware to process XML in a CPU and memory-efficent manner.Skills involved with the product included:* C#/.NET 4.0 using WPF* Visual Studio Blend and Adobe Illustrator for creation of graphic design elements* Windows Installer for product installation* Design and implementation of a USB HID protocol

Worked under contract to develop a PC Application (WattView) for a high-precision, connected power meter product. The meter implemented USB and Ethernet connectivity, using SD card storage to retain usage data until it could be collected for processing by WattView. As sole developer of the PC technology, I played many roles in order to help bring the product to market:* Led the evolution of the UI/UX organization of WattView over time per feedback from product management and sales.* Graphic Design to generate custom imagery and graphics used by WattView* Optimized and streamlined the workflow of WattView to meet the sometimes-conflicting needs of the various target markets.The high-level functionality of WattView is as follows:* Maintain an inventory of meters in use, including location and configuration* Periodically poll usage data from the inventory of meters into the database* Generate several styles of graphs of usage over time* Generate textual reports of usage, meter deployment information, and moreIn addition to WattView, I developed a Provisioning/Calibration tool to streamline final testing, provisioning, and calibration of the meters before being made available for sale.Skills Involved in this product included:* C#/.NET 4.0 using WPF* Database Design* Entity Framework for projection of database contents into C# entities* Visual Studio Blend and Adobe Illustrator for creation of graphic design elements* Windows Installer for product installation

Worked as a Software Engineer under contract to enhance the Talaris product. Talaris was a deployment system which enabled designers of highly-parallel signal-processing applications to establish data pipelines and load-balance the algorithms across Mercury's high-performance hardware.I was responsible for implementing a GUI front-end to a text-based, declarative language that defined the deployment of the programs and modules that comprised a signal-processing application. The GUI supported multiple views of the system, from the source text to Directed-Graph representations of the application, to allow the developer to more easily understand how the application would be deployed.One critical feature was that a change made to any view would propagate to all other views instantly, include the source text. The system maintained the source text in such a way that changes were highly incremental, retaining formatting, comments, etc.The product was implemented using Java 0.9, performing equally well on Windows as well as SPARC systems.

Sole Proprietor and Lead Engineer where I developed, marketed, and sold two shareware products that ran on Windows 3.1 through Windows 98. The first was a product called RFD Mail, which was unique at a time when the Internet was not pervasive, and many email systems were closed systems, accessible only by per-minute-fee dial-up, and had cumbersome text-based interfaces. RFD Mail provided a graphical, universal front-end to these systems (anyone remember CompuServe, Delphi, Prodigy, The World, etc?). This enabled the user to compose and read email while offline (avoiding per-minute fees) with a user-friendly GUI, and to batch upload/download mail much faster than the user could do so manually. The product was compatible with multiple online systems of the day, and in fact could be used with several simultaneously, dialing each as needed. Eventually TCP/IP support was added, with support for SMTP/POP systems, which became the predominant mail back-end for most customers.The code was implemented in Borland Object Pascal for Windows, using SourceSafe for version control (yes, I'll admit to that), and a simple Microsoft Access database for customer tracking and order fulfillment. The second product was called COMt, which is the Windows 3.1 precursor to the COM Port Redirector product line developed at Tactical Software. COMt created one or more virtual COM ports, that fooled application programs into thinking they were communicating with a modem. The difference was that when it came time to dial, an IP address or hostname was used in place of a phone number, and COMt would create a TCP/IP connection to that endpoint on the network.This product helped bridge the gap between legacy software that used modems with increasingly pervasive networks and Internet connections. It instantly "Internet-enabled" any modem-based application with requiring changes to the application code.COMt was written in C using Visual C/C++ 6.0.

Worked in a small team as a contract software engineer on the DEC FUSE product, another early CASE product. I was responsible for the underlying messaging layer that allowed the various components of the system (visual editor, visual debugger, visual code analysis, etc) to communicate and stay in sync. As per the Apollo product, the core was extremely object-oriented, using an object schema to registered each component to the messaging layer.The GUI was implemented in DEC Motif on Ultrix, the core code was implemented in C but using a dynamic object library originally implemented at MIT.

I was a member of a five-person team building a CASE system. The core of the system was intensely object-oriented (novel at that time in the industry, though had its inspirations in Smalltalk).I was responsible for a dynamic dialog builder which allowed the user to edit fields for arbitrary data sets in the system. All information required to generate the dialog was derived from the data itself, and generated using Apollo's proprietary GUI technology.This was the first job in which I was exposed to serious Version Control processes, using Apollo's DSEE, which has evolved over the years to become ClearCASE.