The content distinguishes between two approaches to using AI: as a tool versus as a crutch. The key differentiator is the type of question asked - 'what should I do?' versus 'what should I consider?'. When asking 'what should I do?', users hand control to AI, accept outputs without understanding, and fail to build mental models of their own systems. This creates dependency where the AI owns the context and understanding while the user only has the output. In contrast, asking 'what should I consider?' maintains user control by having AI provide trade-offs, constraints, and failure modes while the user makes final decisions. This approach builds understanding that enables troubleshooting when issues arise. The creator argues that engineers who can explain their architecture are more durable than those who outsource decision-making to AI. The core thesis is that AI should expand decision surfaces rather than own them, keeping humans in control of critical thinking and system understanding.
Asking 'what should I do?' hands control to AI while 'what should I consider?' keeps you in control
High confidence
When you ask AI what to do, you stop building mental models of your own system
High confidence
Asking 'what should I consider?' loads AI context with trade-offs, constraints, and failure modes while you decide
High confidence
Engineers who can explain their architecture are more durable than those who outsource it to AI
High confidence
AI should expand your decision surface, not own it
High confidence
No vendors were mentioned.
The creator's overall position toward the main topic discussed.