Distributed systems developer with experience in the FinTech, Ad Serving, and E-Commerce spaces.

Most recently I spent 3 years and 9 months as Platform Software Engineer at WildFire systems.

While I won't go into too much detail about what I actually implemented there, I did take a few screen captures of my GitHub contributions graphs which provide a nice visual. I feel that this is important since my own graph outside of work isn't quite as pretty.

You can be sure that these weren't just a bunch of documentation and comments slapped into existing files.

That being said good documentation specially about how business logic is implemented is truly worth its weight in gold and sadly I didn't quantify how much documentation I did publish to the wiki-like system we used there.

It's interesting to see that my average was around 600 contributions per year.

Given that there's ~260 working days a year, that works out to an average of 2.30 contributations per workday.

See GitHub's explanation on how they count contributions.

PR reviews are a part of it and I do think one of my more important contributions at WildFire was making sure the code from the team kept flowing while at the same time not bringing down quality.

As I got busy in 2025 I neglected to keep taking screen shots of my contribution graph, so the last this one at the top only covers January and February:

The beginning part of 2025 involved paying down some tech debt, maintaining a lot of the already built systems, and making gradual improvements. In my time at the company we easily doubled the number of code deployments. Half of them dealt with injesting data from partner APIs which meant that we need to respond often to external changes, often on short notice.

The latter part of the year was a bit more fun as I began working on updates to various parts of Opensearch (an Apache-licensed fork of Elasticsearch) index updates and downstream consuming systems.

A large part of 2024 was spent automating our partner billing system which previously lived as separate manual processes could take more than 24 hours to complete due to the volume of end user data that had to be processed. The old way was problematic because it relied on humans to get all the steps executed correctly and to be able to maintain uninterrupted connections to production systems.

Obviously, this was less than optimal. We managed to replace it with a new API wrapping the previous steps in several CRUD endpoints. Due to the execution running within the same network infrastructure as the database, the execution time was whittled down to 30 minutes. More importantly, as a service, we now had proper logs and the rest of expected scaffolding that typical production systems are supposed to have.

After a few months at WF, I noticed that our testing infrastructure was lacking when it came to the full life cycle of user transactions. I decided to go mildly rogue and put together a demo of how this could be done by using ephemeral databases. Leveraging the database was a hard requirement because of the reliance on triggers which I did not want to simulate in mocks.

It helped that soon after I started developing this in my off hours, the company had sponsored hackathon which gave me the time to polish up the proof-of-concept. As of the writing of this document, those resulting integration tests execute with every push to GitHub (thanks to the dedicated DevOps staff). This is probably what I'm proudest of all the things that I worked on while at WF.

It played an important role in proving Wildfire's industry leading approach to UDAAP compliance.

My first year kicked off with a bang. Initially I began tackling a backlog of tech debt resulting from the team having been so small for so long. Soon though I got my first greenfield project which was to build our offer translation system. This system ensured that we only presented offers with translation in all of a given country's official languages to end users, which was a legal requirement from a certain partner.