Software Developer in Boulder, CO, United States

Drivetrain is an internal system used by The Pro's Closet to improve operational efficiency, control workflows and collect operational data. It provides the rails for the whole lifetime of an inventory item.

It starts with purchasing it from a customer via online submission, giving our purchasers the ability to make offers, see history, generate shipping labels and complete a submission upon arrival, automatically generating a SKU, a vendor and a PO for that purchase.

It also provides the operations department with an interface for the inspecting mechanics to evaluate the condition of a bicycle, the servicing mechanics with a screen to service it based on the inspection, the photo department with the ability to automatically upload photos, and it helps the posting department by automatically injecting known data and notes into the catalog. Meanwhile, it creates events for every touch-point, allowing us to create reports and dashboards.

Drivetrain also helps our accounting department by showing which POs need to be paid, and gives the option for bulk payouts. I designed and developed Drivetrain from scratch along with the help of my co-worker who is the front-end developer.

The Pro's Closet's website is in Shopify's ecosystem but we have customized it a great amount. For example, it has custom collection pages that load products from our servers increasing loading speed, allowing for filtering by multiple filters in a category (e.g. size small or medium) as well as filtering by price. We also implemented the ability to save a search. It allows a customer who has used a filter set and not found the bike he is looking for, to save his search and receive daily emails with products matching the criteria. This helps customers find their dream bicycle but it also helps the purchasing department identify what bikes customers are looking for.

Additionally, we have built a custom page for the customer to submit their bikes and thanks to the automation provided by Drivetrain, our internal system, a few buyers are able to process around 1,000 submissions per week.

Lastly, the account page provides customers with the ability to check the status of their submissions, and accept or decline their offers. Also, CPO customers can see their bike's buy-back value and start the submission process.

My role was to collect, store and retrieve the data needed for these processes, as well as to write the REST API.

The Apheresis portal is a system for communicating with aphaeresis medical devices. It collects procedure data from devices, providing filterable reports and dashboards, giving hospital staff the ability to see performance metrics and drill down by ward, operator, and device.

The system establishes 2-way communication with devices in order to monitors live data about currently running procedures and to send patient's data to devices to get them set up for a new procedure.

It also sends webhooks to subscribed servers/listeners when events happen, allowing hospitals to subscribe to their own internal systems.

The portal was broken down into sections, with roles and permissions allowing different users access to resources based on their privileges. I started with Fresenius in the middle of the project lifecycle but found many opportunities for improvement such as using asynchronous programming in order to reduce resources and improve performance, add local and AD authentication, and even wrote a driver to support one of the legacy devices. I came up with a clever way to communicate with the device increasing the possible concurrent connections from 10 (on the old system) to a few thousand.