Routine production
Boilerplate, syntax conversion, basic tests, familiar CRUD and first-draft documentation.
AI resilience
AI is changing what programmers are paid to do. Treat a career as a bundle of tasks, judgment, context and responsibility—not one indivisible job.
Two bad strategies
Boilerplate, syntax conversion, routine CRUD and basic documentation are getting cheaper. Verification, architecture, debugging, integration, security, domain knowledge and ownership are changing shape.
AI reality
AI capabilities evolve. Exposure labels are not permanent safety claims; they are a lens for today’s learning decisions.
Task model
Lower exposure never means AI-proof. It means context, accountability and consequences currently matter more.
Boilerplate, syntax conversion, basic tests, familiar CRUD and first-draft documentation.
Architecture options, debugging hypotheses, database models, test strategy, integration and security review.
Understanding the actual problem, stakeholder trade-offs, risk, domain expertise, production ownership and verification.
AI-native, not AI-dependent
Speed is useful. Without deliberate independent reasoning, that speed becomes borrowed capability.
Explain the problem and success criteria yourself.
Solve selected foundational exercises without AI.
Use AI to generate options and critique—not authority.
Verify correctness, complexity, edge cases and security.
Debug failures and own trade-offs.
Take responsibility for the consequences of the result.
Practice modes
Selected sessions for foundational reasoning, debugging and recall. The goal is not purity; it is measuring your own capability.
Take an AI solution, then find a bug, complexity issue, counterexample, security gap and simpler alternative.
Career-specific exposure
Open a target career to see which tasks are exposed and which capabilities deserve deliberate practice.
Next step
Then do one AI-free foundation exercise and one AI-assisted review. Evidence replaces panic.
Choose a career