When ChatGPT Becomes a Coworker's Entire Brain
Artificial intelligence tools like ChatGPT have transformed the modern workplace in genuinely exciting ways. They help professionals brainstorm faster, draft communications more efficiently, and navigate complex problems with a useful second perspective. But there's a fine line between using AI as a tool and surrendering your own judgment to it entirely — and a growing number of workers are watching their colleagues cross that line in real time.
A recent update posted to the popular workplace advice column Ask a Manager captures this tension with striking clarity. A software developer described leaving a role partly because a coworker had become so dependent on ChatGPT that he would visibly type every question into the chatbot during live Zoom calls — even questions directed at him personally. At one point, this coworker proposed rewriting the company's entire codebase in a different programming language using ChatGPT alone, apparently unaware of how catastrophically impractical that suggestion was. The coworker, by the letter-writer's account, did not know how to write code at all.
This isn't just an amusing anecdote. It's a window into a workplace dynamic that's becoming increasingly common — and one that carries real professional and organizational consequences.
What Is AI Overreliance and Why Is It a Problem?
AI overreliance occurs when a worker substitutes AI-generated output for their own reasoning, judgment, and expertise rather than using AI to supplement those skills. The distinction matters enormously. A competent developer who uses ChatGPT to quickly look up a syntax pattern or generate boilerplate code is using the tool intelligently. A developer who cannot answer a technical question without first asking ChatGPT — and who accepts its answer uncritically — has stopped developing professionally.
The risks of this pattern extend far beyond individual performance. When team members can no longer think critically without AI assistance, several problems emerge:
- Accountability gaps: When something goes wrong, no one fully understands why, because no one fully understood the solution that was implemented in the first place. AI-generated code or decisions are difficult to audit when the person who submitted them doesn't comprehend them.
- Bad suggestions go unchallenged: As the developer in the Ask a Manager story observed, her coworker genuinely believed that rewriting an entire codebase via ChatGPT was a viable proposal. Without domain knowledge to filter AI output, dangerous ideas can enter serious conversations.
- Skill erosion over time: The original letter-writer noted that her coworker "seemed to stop thinking for himself as time wore on." This is not incidental — it reflects how habitual AI dependency can actually degrade the cognitive muscles that professional work requires.
- Team morale and respect: Colleagues who maintain their expertise often find it demoralizing to work alongside people who outsource every thought to a chatbot, particularly when those colleagues are treated as equally authoritative.
The Rise of "Vibe Coding" and What It Signals
The letter-writer's update also introduced a term worth understanding: "vibe coding." This phrase, which has gained traction in tech circles, refers to the practice of using AI to generate functional-looking code without fully understanding what the code does or why it works. You describe what you want, the AI produces something, it seems to run correctly, and you ship it. The "vibe" is right even if the technical foundation is shaky.
Notably, the developer who left the toxic AI environment found herself at a new job where, in her words, "the vibe coding here is a bit off the charts too." Even after escaping one problematic culture, she encountered the same phenomenon elsewhere. This suggests that vibe coding and uncritical AI usage are not isolated incidents tied to specific bad actors — they represent a broader cultural shift happening across industries.
For organizations, this is a governance and quality problem. For individual workers, it is a career risk. Code, analyses, reports, and strategies generated by AI without human expertise behind them are brittle. They work until they don't, and when they fail, no one on the team has the knowledge to fix them.
How to Protect Your Career in an AI-Saturated Workplace
The developer at the center of this story made a decision that many skilled professionals in similar situations may want to consider. She kept her technical skills sharp through projects outside her day job, continued to advocate for thoughtful AI use, and ultimately prioritized roles where her experience and judgment were genuinely valued — even if those roles weren't perfect in every other respect.
There are practical steps anyone can take to navigate a workplace where AI overreliance has become normalized:
- Continue building skills independently. Side projects, open-source contributions, personal learning goals — these keep your expertise real and current regardless of what's happening at the office. They also make you more competitive if you need to move on.
- Document your contributions clearly. When your expertise catches an error, prevents a bad decision, or produces a result AI alone could not have achieved, make that visible. In performance reviews and project retrospectives, your judgment should be identifiable as yours.
- Raise concerns through the right channels. If a coworker is proposing genuinely risky AI-driven decisions — like rewriting a production codebase without understanding the language — that is a legitimate technical concern worth raising with a manager or tech lead, framed around risk rather than personal frustration.
- Evaluate company culture before accepting roles. As the letter-writer reflected, the ChatGPT coworker probably should have been a signal earlier. During interviews, asking how a team uses AI tools and what standards exist around code review or output verification can reveal a lot about whether critical thinking is still valued.
The Bigger Picture: AI as a Tool, Not a Replacement
None of this is an argument against using AI at work. ChatGPT, GitHub Copilot, and similar tools genuinely improve productivity when used by people who understand what they're doing. The problem is not the technology — it is the abdication of professional judgment that some workers and organizations are allowing to occur in the technology's wake.
The developer's story ends on a cautiously optimistic note. Her new job comes with an AI usage mandate she finds uncomfortable, and the vibe coding culture gives her pause. But she feels respected. Her questions are answered thoughtfully. Her expertise is treated as valuable. For now, that matters.
That distinction — between a workplace that uses AI thoughtfully and one that uses it as a substitute for thinking — may become one of the most important factors professionals weigh when evaluating where they want to work. Companies that figure out how to harness AI without hollowing out human expertise will almost certainly outperform those that don't. And workers who keep their skills sharp through the current wave of AI enthusiasm will be the ones best positioned to lead when that reckoning arrives.