A coworker who was always bad at coding now uses Claude for everything—and it works
On one development team, a coworker had been consistently bad at the job for years—not junior, just genuinely weak. Code was messy, mistakes repeated, previously fixed things broke again, and tasks usually needed someone else to finish or fix. Now that coworker uses Claude for every step of the workflow: a ticket goes into Claude and code comes out, an error goes back into Claude for a fix, a review comment goes in and a new version comes out.
He is essentially just moving text between Jira, Claude, and GitHub. The result, though, is that the work is now genuinely good—not amazing, but solid. are cleaner, mistakes are fewer, and output is higher.
Reviewing the code often turns up nothing to complain about. The catch is that when asked about his own code, he often can't really explain it or say why it works the way it does.
Key points
- A long-underperforming coworker now uses Claude at every step of the workflow
- Pattern: ticket → Claude → code, error → Claude → fix, review comment → Claude → new version
- PR quality visibly improved, with fewer mistakes and more output
- He often can't explain why his own code works the way it does