Taking the Wheel With AI

I was praised because an RFC I wrote did not sound like AI.

The funny part is that it was written with AI.

Most of what I do uses AI in some way. The difference is that I take the wheel.

I decide where we are going, what we are talking about, how it should sound, and what the final shape should be. AI plays an important role, mostly as an editor, reviewer, co-worker, and very smart friend that helps me organize my thoughts.

At CrewAI, RFCs are one of the ways we think carefully before building things that need to last. When the work touches scale, reliability, or enterprise use cases, the document matters because it makes the tradeoffs visible early.

That is where AI is useful. It helps with boring passes. It challenges wording. It finds gaps. It makes the work faster.

But it should not replace the thinking.

People are still learning that balance. Give AI too much autonomy and you may gain speed, but lose ownership. The job gets done, but it does not fully become part of your memory. You do not grow as much from doing it.

AI is a tool, like Google, Stack Overflow, or Wikipedia. The tool is not the problem. It never is.

The hard part is finding the balance (isn’t it always?): how much autonomy to give, how much control to keep, when to choose each, and what to prioritize.