2026 is the year that we are asking everyone to get comfortable with using LLMs in their daily workflows. I want to talk about why that matters, what it looks like at Sentry, and how we're thinking about adoption.
If you haven't been paying attention LLMs have gotten to the point where they're actually quite powerful for a lot of tasks. They're by no means a cheap solution to many problems, but in a lot of situations we're optimizing for getting more done vs doing things the cheapest way possible. Think of this as Venture vs Private Equity: we're on the Venture side of the world, and we invest in growth. While my experience is primarily in using LLMs for engineering tasks, the same principles apply to other domains. I will focus on that for the sake of this conversation, but the message rings true for every department and every role.
You may know this already, but my role at Sentry is not contributing code; I do it because I enjoy it and it's really a core reason I'm even in this industry. It's the reason I