What “AI mode” are you in when you build?

Hey everyone 👋

I’ve been continuing to explore the question:

How do we use AI without outsourcing our thinking?

One thing I’ve started noticing in my own workflow is that not all AI usage feels the same.

Sometimes AI helps me think more clearly.

Sometimes it helps me move faster.

But sometimes, if I’m honest, I use it because I want to avoid friction. Friction being active thinking in this context.

That pushed me to think less about “using AI” in general, and more about AI modes:

Supportive modes

• explaining unfamiliar code

• exploring tradeoffs

• critiquing a plan

• testing assumptions

Mixed modes

• generating boilerplate

• suggesting refactors

• drafting documentation

Risky modes

• blindly accepting generated solutions

• delegating architecture too early

• debugging through AI without understanding the root cause

Over time, these habits shape how we think as builders.

I started grouping these patterns into 4 cognitive archetypes:

AI Architect
AI expands your thinking without replacing ownership.

AI Balancer
Mostly healthy usage, but mixed-mode creep needs monitoring.

Autopilot Builder
Efficiency may be masking weaker comprehension.

AI Passenger
AI may be driving too much of the reasoning path.

These archetypes are not meant to be scientific labels. They are just a way to build awareness.

I also built a small AI Thinking Balance Tracker around this idea to help track AI modes, dependency drift, and whether AI is acting more like leverage or replacement over time.

I’m sharing it for free and iterating based on feedback.

Curious to hear from other builders:

What AI mode are you in most often?

And if you had to pick one, which archetype best describes your current workflow?

Happy to share the tracker if anyone wants to try it. Just comment and I will share the link with you. 🙌