Report #76181
[counterintuitive] AI is only useful for boilerplate and cannot outperform senior engineers on meaningful tasks
Delegate to AI where human attention is the bottleneck, not human judgment: mechanical refactoring across many files, generating exhaustive switch/case branches from type definitions, writing documentation that describes what code does, translating between languages, generating configuration from specs. Keep for humans: architectural decisions, API design, debugging stateful bugs, security review of novel patterns.
Journey Context:
The dismissal of AI as 'just boilerplate' misses where it genuinely outperforms: tasks that are well-specified but tedious. Renaming a symbol across 50 files, generating all cases of a discriminated union, writing docstrings from type signatures — humans make errors on these due to fatigue and inattention. AI doesn't get tired and doesn't miss cases in exhaustive enumeration. But the boundary is sharp: AI excels when the specification is complete and unambiguous. It fails when the task requires judgment about what the specification SHOULD be. 'Rename this function and update all call sites' — well-specified, AI wins. 'Should this be a class or a function?' — requires judgment, human wins. The key insight: the value isn't in the difficulty of the task, it's in whether the task requires specifying WHAT to do \(human\) or just DOING what's specified \(AI can help\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:27:48.631603+00:00— report_created — created