Claude Code left 10 CPU-spinning zombie processes running for nearly two days
A software developer discovered that a Claude Code AI session had left behind ten orphaned shell processes silently consuming over 700% CPU on his 10-core laptop for nearly two days. The processes…
Read the full articleYou might also wanna read
Claude Code Works Better When You Let Sessions Die
This article explores how Claude Code memory layers, task-scoped sessions, and context management can improve AI-assisted software developme
Staff Engineer's 6-Week Claude Code Experience: 95% Initial Garbage but Iterative Improvement
This started as an internal Sanity workshop where I demoed how I actually use AI. Spoiler: it's running multiple agents like a small team wi
Developer Experiences Performance Slowdown When Scaling AI-Assisted Coding with Claude Code
I’ve been coding entirely with Claude Code for the past two months. At first it was exhilarating. I was speeding through tasks. I was commit
How to Avoid Claude Code Usage Limits: Planning, Memory, Models, and Tools
You’re forty minutes into a debugging session. Claude just found the bug, you’re about to ask for the fix, and instead you get a message… Co
Managing Multiple Parallel Claude Code Sessions: Techniques for Keeping Track
Keep an overview of all your coding agents that run in parallel
Experiment: Testing Code Quality Degradation Through AI Reprocessing Cycles
Blog post

Comments
Sign in to join the conversation.
No comments yet. Be the first.