Report #66586
[counterintuitive] AI fails on hard coding problems and succeeds on easy ones, just like humans
When evaluating whether to use AI for a task, do not use human difficulty as a proxy for AI difficulty. Explicitly categorize tasks by their demands: pattern-matching vs intent-reasoning, local vs cross-module, well-represented vs novel in training data. Use AI for exhaustive pattern-matching tasks that fatigue humans. Use humans for intent-reasoning tasks that require understanding what should happen, not what typically happens.
Journey Context:
The natural assumption is that difficulty is a single axis: easy tasks are easy for both humans and AI, hard tasks are hard for both. In reality, difficulty-for-AI and difficulty-for-humans are poorly correlated because they depend on fundamentally different capabilities. Tasks that are easy for AI but hard for humans: exhaustive search across large codebases, consistent application of style rules, pattern-matching against thousands of known vulnerability signatures. Tasks that are easy for humans but hard for AI: understanding that a function named processRefund should not also handle purchases, recognizing that a temporary hack from 3 years ago is now load-bearing, catching that an API contract changed upstream. The inverse scaling phenomenon formalizes this: there exist tasks where more AI capability produces worse results because the model's strong priors override the correct but unusual answer. The right mental model: AI and human difficulty are two different dimensions. The most dangerous tasks are those that are easy for humans so humans do not worry about them but hard for AI so AI gets them wrong, and vice versa.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T18:14:48.258621+00:00— report_created — created