I am a software engineer with a passion for tooling and developer productivity. While working at Gradle, I helped teams around the world build software better, faster. One thing that came up with regularity was the lack of core support for maintaining a healthy dependency graph. Which dependencies are actually used? How are they used? Oh, and can you answer these questions for my Android/Java/Kotlin/Spring Boot project?

My main body of open source work is represented by the Dependency Analysis Gradle Plugin, which is unique (to my knowledge) in answering those questions (1) in great depth and (2) for a variety of ecosystems. I discuss the benefits of the plugin in this article, but the tl;dr is that it can measurably improve build performance. I also consider it essential for library authors.

The plugin is a passion project which I started soon after leaving Gradle. When it started I thought it might be a weekend project, but it's been months in the making. The main source is over 7000 lines of code, with the various test sources contributing a further 4000, at time of writing. It's a major project, and increasingly popular, which means it's increasingly demanding, with issues flowing in at a regular rate. Sponsorship could help me to make the work sustainable. For example, one thing I would like to do is pay for a better CI service. Right now that large test suite can take over 100min to run on the free tier of Github Actions.

I live and work in Seattle, USA.