Click any tag below to further narrow down your results
Links
The article compares human “rockstar” developers—who produce clever but inscrutable code—with AI tools that can churn out massive, disjointed codebases. It shows how both create unmaintainable systems and recommends guiding AI to generate small, understandable snippets, slowing down to match architecture to problem complexity, and keeping craftsmanship in human hands.
- AI coding tools act like "rockstar" developers of old: producing huge volumes of code fast, but leaving behind unmaintainable messes once the task is "done"
- Unchecked AI output leads to tangled codebases so complex that only another AI can parse them, creating technical debt that's effectively unpayable
- The fix is treating AI as a guided tool rather than an autonomous contributor: small prompts, human-understandable code, and matching architecture complexity to the actual problem
- Sometimes writing a few lines by hand beats wrestling with AI-generated noise—craftsmanship can't be outsourced
The author quits a stable design-engineering role after growing frustrated with unchecked AI tools disrupting meetings, code reviews, and design processes. They trace their burnout to constant AI pressure, abandoned industry ideals, and a sense that shortcuts have overtaken craftsmanship.
- Quit a well-paying, remote, benefits-included design-engineering job despite strong performance metrics because unchecked AI adoption made the work untenable.
- Daily friction came from AI tools deployed without consent or review: auto note-takers in meetings, unverified chatbot answers in Slack, mass-merged AI-generated code, and bot-driven PR feedback replacing human collaboration.
- Frames the exhaustion using Freudenberger's definition of burnout as "political defeat" - grief over watching tech's early-2010s user-centered, civic-minded ideals get replaced by profit-chasing and political appeasement.
- Distinguishes this from ordinary overwork: the burnout stems from constantly deciding whether to push back against imposed AI shortcuts, not from hours or workload.
Judit Bekker reflects on how AI tools have made personal data visualization projects quick but soulless. She traces her own shift from passion-driven Tableau work to a broader AI and generalist role, arguing that while automation boosted efficiency, it drained the hobbyist joy of dataviz.
- AI tools like Claude turned dataviz projects that once took weeks of manual tinkering into seconds-long tasks, stripping out the personal satisfaction of the process
- The job market shifted from hiring specialized Data Visualization Experts/Dashboard Designers to demanding generalists who handle data modeling, stakeholder talks, analysis, reporting, and AI engineering
- She now spends only about 5% of her week in an actual visualization tool (Looker), reflecting how far her role moved from pure dataviz work
- Her core argument: AI didn't kill data visualization, but by making it too easy it killed the hobbyist joy and craftsmanship that made it meaningful