The AI skill anxiety that only $20/month developers can afford to have

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3759118) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } brian austin Posted on Apr 28 The AI skill anxiety that only $20/month developers can afford to have #ai #discuss #programming #career The AI Skill Anxiety That Only $20/Month Developers Can Afford to Have There's a fascinating discussion happening right now on Dev.to. Developers are asking: Is AI making me worse at coding? The most-reacted article this week is 'I Used to Love Coding. Now I Just Prompt.' It's struck a nerve. Developers are worried about skill atrophy, loss of deep thinking, the slow erosion of the ability to hold complex problems in their heads. This is a real concern. I've felt it too. But here's the thing nobody in that conversation is saying: This is a luxury problem. Who gets to worry about AI skill atrophy? Developers who worry about whether AI is making them lazy are, by definition, developers who are using AI enough to form an opinion. That requires $20/month for ChatGPT Plus. Or $20/month for Claude Pro. Let's be concrete about what that means globally: Nigeria: $20/month = 3-4 days of average developer salary Philippines: $20/month = 2.5 days of typical freelance billing Indonesia: $20/month = Rp320,000 — a significant weekly grocery budget Kenya: $20/month = KSh2,600 — nearly a week of transportation costs India: $20/month = Rs1,600 — 10x what a local SaaS subscription costs For developers in these markets, the skill-atrophy debate is academic. They're not using AI enough to atrophy. They're rationing it. The rationing problem is worse than the atrophy problem Here's what rationing looks like in practice: // Developer who can afford $20/month AI: // "Let me ask Claude to review this function" // Gets review, iterates, learns the pattern, ships better code // Developer rationing expensive AI: // "Do I really need to use an API call for this?" // Decides it's not worth the mental accounting // Solves it manually, correctly, but slower // OR: asks a vague question to get maximum value per query // Gets a vague answer, doesn't learn the pattern Enter fullscreen mode Exit fullscreen mode The developer who rations is not free from AI's influence on their thinking. They're just getting the worst of both worlds: They're not building fluency with AI tools (which matter for employability now) They're spending cognitive budget on cost-consciousness instead of the actual problem They're not iterating — one shot per session, hoping for the best The research on AI-assisted coding found developers felt 20% faster but measured 19% slower. That gap exists partly because developers changed their behavior when AI was present. They started writing differently — more skeleton code, less thought about edge cases upfront. But that behavior change requires trust in the AI. Trust requires enough usage to form habits. And enough usage requires affordability. The experiment you can't run if you're rationing The developers writing thoughtful articles about AI's effect on their skills have had the chance to actually experiment. They've tried different prompting styles. They've had Claude do the whole thing and then done it themselves to compare. They've noticed patterns: "I reach for AI faster on Fridays." "I think less carefully…

This excerpt is published under fair use for community discussion. Read the full article at DEV Community.