Phillip Carter Email & Phone Number

Redmond, Wa, Us

San Francisco, Ca, Us

I'm currently the lead for all AI-related efforts at Honeycomb. I designed, prototyped, and helped implement the industry's first natural language querying system for Observability data. I also lead and drove Honeycomb's cost management tool - Refinery - towards a differentiated experience that is now a "pillar" of our enterprise sales process. Prior to this, I defined and drove Honeycomb's OpenTelemetry efforts (something I still do today, but in a more shared capacity). I've ran the gamut from implementing solutions and leading product discovery to driving sales calls and speaking at conferences.

San Francisco, Ca, Us

I'm did lots of PM stuff for all things Developer Experience at Honeycomb. Honeycomb's OpenTelemetry strategy, entire Open Source presence, public API, and developer tool integrations.

Redmond, Washington, Us

I continued to own the F# language and tools and the .NET-based "project system" in Visual Studio, making mostly incremental improvements to both based on customer feedback. I personally implemented several brand-new features for the F# tooling in Visual Studio: tens of code fixes, a new form of IntelliSense, and dozens of bug fixes.I built and maintained a tool (try-convert) to convert .NET Framework projects to .NET 5 projects, which has since become a central component to our strategy for helping customers port their codebases to modern .NET.I also led the effort to build out a compelling experience for C# and .NET in Visual Studio Code, being careful to ensure that a good experience could be delivered for users without re-creating Visual Studio and thus potentially alienating developers in either toolset.I was also the primary driver in our efforts to make .NET better in education, specifically by building a bundler for education that enables students to install .NET, Visual Studio Code, and the right set of extensions to be successful. I also led a vision to make C# more accessible by removing the need for a project file, allowing beginners to "just run a C# file" anywhere.

Redmond, Washington, Us

I continued to own the F# language and tools, driving numerous updates to Visual Studio tooling, new language features, and new versions of the language. I helped cement F# as a fundamentally cross-platform and open source language, where Linux and macOS are first-class citizens when using the language. I spoke at several conferences about F#, interviewed customers, and developed a plan to dramatically improve the performance of F# tooling in Visual Studio for large codebases.I also began to own the "project system" in Visual Studio for .NET Core developers. At the time, it was an exciting new component with a lot of upside, but also a lot of performance problems. I worked with the Visual Studio team and my own team to make targeted architectural changes to significantly improve solution load times for large codebases, drop memory usage a lot, and make the product more responsive. We achieved an over 50% reduction in solution load times for a test solution over the course of this time, and I learned that performance and reliability are some of the biggest factors in keeping customers delighted.Lastly, I helped contribute to a far-reaching strategy around programming languages and AI, of which F# would play a part. I worked with several other researchers to come up with a vision and short-term and long-term plans that we could execute on immediately. Some of these have born into actual research work done in the F# language, particularly around tensor shape checking and differentiable programming.

Redmond, Washington, Us

I worked on .NET Core and leading up to its initial release, writing many foundational pieces of documentation and working with the technical documentation team towards an information architecture that could stand the test of time.I transitioned into owning the F# tooling for Visual Studio, which I helped fundamentally transform into a more sustainable and pluggable architecture that has since allowed for dozens of new productivity features to be written. I also fostered a small community of open source developers to contribute features and other improvements.At the same time as owning the F# tools, I helped re-architect .NET setup for Visual Studio 2017. One of the pillars of Visual Studio 2017 was a reimplemented setup engine that dramatically increased reliability, decreased setup time, and reduced the overall size of Visual Studio for developers. I helped bring the size of the .NET tooling payload from tens of GB to 2-7GB (depending on what tools you wanted to enable). The end result was that the large majority of Visual Studio users saw an order of magnitude improvement in setup, installation, and updates across several metrics.I also spent some time on a v-team doing growth-hacking efforts to see how we can better attach users of Visual Studio to Azure services. This involved tutorials, surveys, customer interviews, collaboration across organizations, and documentation updates.

Corvallis, Or, Us

I wrote a Clojure web service which translated oceanography data and metadata into target languages from JPL's PO.DAAC service.

Corvallis, Or, Us

I developed web apps and services on the .NET stack, developed documentation, performed web application security analysis, and led certain project management efforts in a minor role.I also mentored other student developers in building robust, test-driven solutions for the particular domain they were working in.

Bachelor Of Science (Bs), Computer Science

Computer Science