Custom ESLint ratcheting: how Notion modernizes code without slowing down development

Blogs

As any codebase grows, so does the proliferation of old code and outdated patterns. This often results in a massive technical burden that requires large cleanup sprints, increasing the risk of regressions and ultimately slowing engineers down.

Visit Site

Blogs Notion So

BlogsA guide to the software development processNotion So BlogsBeyond AI experimentation: How to get real business valueNotion So BlogsA complete guide to Agile epics (with examples)Notion So BlogsMastering the art of the Content CalendarNotion So BlogsWhat exactly is the project management triangle?Notion So BlogsA pre-mortem template to help your team identify problems before they happenNotion So BlogsSocket for ClickUp Is Now AvailableSocket Blogsnpm Registry Code SigningSocket BlogsAI + a16z Podcast: Vibe Coding, Security Risks, and the Path to ProgressSocket NewsMeasuring CI/CD Adoption Rates Is a ProblemThenewstack NewsHow Community Prevailed at Python's Virtual Core Development SprintThenewstack NewsHow the Tech World Honored JuneteenthThenewstack NewsWERF Automates Kubernetes-based GitOps from the Command LineThenewstack NewsThe Hardware and Software Used in SpaceThenewstack BlogsNode.js Native Binary Compilation Using vercel/pkgPulumi BlogsOrg-only Template Gallery and Setting Default Repositories: Streamline Your DevelopmentPulumi BlogsIntroducing Read-Only Mode for Pulumi NeoPulumi BlogsThe Agentic Infrastructure EraPulumi BlogsWhat Exactly Is Cloud Engineering?Pulumi BlogsBenefits of Policy as CodePulumi