🔗 Is your team still hand-chiseling code?

If you go on Hacker News or to conferences and meetups, it’s easy to leave with the impression that everyone is using Claude Code or Cursor as a crucial part of their development process.

But if your team isn’t using AI yet (or using it as much as you would like), you’re probably worried that they, and your team, will fall behind. And you aren’t the only one.

In conversations with founders and engineering leaders lately, I’ve noticed that there’s a widening gap, and it’s only quietly talked about: many engineers are eagerly adopting AI, but lots are also rejecting it, either quietly or openly. They’re less than thrilled about the prospect of cleaning up AI slop or worry that it will take away their favorite part of their job.

And this is becoming a big frustration on both sides. Engineers who aren't using AI feel pressured into doing something they don’t want to do, and leaders panic as they watch other teams and competitors that are using AI speed ahead.

Here at Geocodio, Claude Code has become a key part of our workflow, and it’s exponentially sped up our development. Yet it’s also changed how our engineers spend their time: less coding, more architecture, more QA. That’s a big shift towards other parts of the engineering process, and it's understandable that some people would struggle with such a big shift.

But that’s a relatively recent development. Claude Code was released on February 24, 2025: less than a year ago.

I’d say that I myself was still pretty skeptical of the practical applications of AI myself until last summer, and even somewhat opposed to it given that my own book was included in the LibGen dataset used as training data by Meta and OpenAI. If you’d told me a year ago that I’d be writing this blog post, I would have laughed you off. But the benefits are undeniable, and I know we wouldn’t be as productive as we are without it. We can build full prototypes of features in a day's worth of work that would previously have taken months. We're tackling far more ambitious projects than we would have attempted before.

But I’ll shut up about that now, because if your team isn’t using AI, that probably only makes you feel worse, and that’s the opposite of my intent here.