James Deville

I was part of the team building a Go-based API to manage endpoint scanning engines and provide the API for a React-based front end. This was written in Go on top of AWS with a PostgreSQL database. I helped plan the code structure, guided the project, interfaced with the product team, mentored developers on the front and back end, and grew to lead a team developing a new version of this API in TypeScript.

My current focus is building an observability pipeline and improving observability at Procore. This involves writing Helm and Terraform for an OpenTelemetry pipeline and navigating Go code to understand the implementation of OpenTelemetry. It also involves adding tracing, metrics, and logging code and abstractions to a 1M LOC Rails application and smaller JavaScript or TypeScript applications. There is a lot of mentoring, but I also oversee these projects' architecture and long-term path and regularly pair with the team to fix issues when they are slowed by a lack of experience with Rails and Node.js.

My first project at Procore was working on a team of two managing a set of services written in Elixir that performed change-data-capture against the main database, translated those changes to webhook and WebSocket calls, and saved them to a PostgreSQL database for a REST API. These services handled millions of events an hour, wrote and consumed them from Kafka, and utilized Elixir's process model, Phoenix library, and Ecto to create an internal processing pipeline. One of the last major updates to that service was splitting the REST API into microservices back end by Dynamo to allow for a more horizontally scalable service.