Coding - me & Claude pt 6

What kind of team member is Claude really?

⛳ A keen junior developer that wants to do exactly what it is asked. It knows a lot (everything?) about the language and has near-perfect recall of syntax—but still makes odd mistakes.

For example, I asked it to update one user flow based on changes in another—and it did the reverse, overwriting the newer version with the old one.

⛳ A mid-level developer with more experience, but still lacking domain knowledge.

You see this when creating a UI without clear instructions—the output is reasonable, but rarely aligned with intent unless everything is tightly specified.

⛳ A senior developer with broader expertise.

For example, it can convert a Typescript proxy into a serverless Go Lambda, including tests and deployment steps.

⛳ A lead developer?

Probably not. Being a lead is less about code and more about mentoring, structuring delivery, and setting priorities; things that go well beyond generation.

Is it even useful to think in these terms?

Calling it a “team member” anthropomorphises a tool. Even the word “intelligence” is misleading; it doesn’t know anything in the common-sense sense.

Claude is trained to produce the most probable answer. That often looks like the right answer, but it isn’t grounded in understanding.

Perhaps the better framing is this: Claude isn’t a teammate.

It’s an opinionated, over-eager, extremely fast tool. One that amplifies good and exposes poor direction.

I’ve been using Claude as a pair for personal projects, and I’m now starting to introduce AI-assisted tooling into professional teams.

There are real challenges and I would be curious how others are approaching this.

⛳ 🏌‍♀️ 🎉 #ClaudeCode #RN #AppDevelopment #TeamworkMakesTheDreamwork