December 6, 2025
Code, meet woodchipper
Skin-Shedding Code (2024)
Delete it and start over? Zed’s devs do it — commenters split
TLDR: Zed’s devs regularly delete and rebuild code, even swapping their UI system with a huge rewrite. Comments split between confusion and caution: one warns rewrites can sink a funded startup, yet admits they’re now leaning into shredding—sparking the real question of when smashing and rebuilding is the smarter move.
Zed’s latest confession reads like a dare: their engineers regularly hit delete and rebuild whole chunks of the app, a practice they dub “shredding.” The community reaction? Split and spicy. One camp is stunned by the swagger—“delete five load‑bearing functions” turned into a running joke—while skeptics clutch the rulebook.
The title drama kicked it off, with akkartik puzzled: is it “skin‑shedding” or “shredding”? That confusion set the tone: is this brave spring‑cleaning or reckless demolition? Fans point to the jaw‑dropper stat—adding 42,150 lines while deleting 330,105—to argue it’s more snake‑skin renewal than chaos. Shredders say the team’s deep domain chops and Rust (a safety‑first programming language) make the sledgehammer feel surprisingly safe.
On the caution side, OisinMoran surfaced the startup taboo: once you raise money, “don’t rewrite the whole thing” or you’ll tank the company. Yet even they admit they’re drifting toward shredding, calling it “great” and hinting there are reasons it works—cue more debate about “scoped teardowns” versus all‑night arson.
The vibe: no code is sacred at Zed, and commenters are deciding whether that’s genius or madness. Meme energy: “controlled wildfires” vs “office arson,” with everyone asking the same thing—when do you wield a scalpel, and when do you grab the sledgehammer?
Key Points
- •“Shredding” is defined as large, scoped code rewrites that delete and rebuild components to improve design.
- •At Zed, shredding is part of the culture; no code is considered untouchable.
- •A multi-week shred rewrote Zed’s UI framework (GPUI), resulting in +42,150 additions and -330,105 deletions in a single pull request.
- •Shredding requires confidence and judgment to choose rewrites over small, incremental changes.
- •The author suggests careful scoping, domain expertise, and possibly Rust contribute to successful, stable rewrites that keep the codebase healthy.