Welcome - idmontie's Portfolio

A monorepo has many advantages in the modern era of computing - a single engineer can make cross-domain and cross-platform changes in a single PR, LLMs and agents can access context of the entire stack in order to make code changes, and it is easier to determine the impact of a change to consumers.

But a downside to the monorepo is that the amount of Pull Requests can become unwieldy. The sheer number of engineers writing code, making Pull Requests, and asking for reviews a day is growing even faster now that a majority of code is being written with at least some help by AI agents.

As I was reading through the Petar Maymounkov and David Mazières paper "Kademlia: A Peer-to-peer Information System Based on the XOR Metric", I was interested in the application of this XOR metric on work I had previously done on clustering embeddings. When implementing the Infer API for Clarity Hub, we focused on using the distance between vectors as a way to cluster utterances together into a topic. We did this via Euclidean distance between vectors, which we had to compare against all other vectors within the space.

My philosophy when designing APIs and libraries is to make it as easy to use as possible, but as difficult to use INCORRECTLY as possible. When I used to make plugins with jQuery, there would often be guards on functions to ensure that the data passed in met the function's expectations:

I recently published a utility Human Agent Review Tool that helps keep track of the code I've actually reviewed while working with coding agents.