Gather 'round the campfire, and let me tell you a scary story, one that you might already know from the bones. But, when added to the flesh and sinew of raw detail, you might find yourself sweating, thinking of an all-too-familiar codebase... If you're old enough to recognize this, I have a few scarier things to tell you, later. The bug seemed simple enough: our dashboard on app.hackernoon.com was flashing a login form, then once the login state loaded, it was flashing an empty dashboard while the drafts loaded. Simple enough...just wait for everything to load. Right? Dead wrong. I entered through the main entrance, the component which rules over our dashboard, powering data fetching, etc. A "smart component", if you will. For each section of the dashboard, there's a component too, like for, you guessed it, the section that displays your drafts. Of course, this component, being one of the early abstractions in our codebase, has another concern: displaying the welcome screen or the draft dashboard, based on internal loading state. Home HomeDrafts Do you smell it yet? The kind of old cartoons, an old oldie... One component should have one concern. That concern can involve many different moving parts -- for example, our `Home` component handles data loading for a few collections in the database -- but never should the two concerns interfere with one another. Unless you're implementing a concurrent process with Node streams, in which case you should totally cross them. More than that, we have some concerns spread across multiple components! It's not quite this bad, but it does feel Hydra-like sometimes As you make changes in , you have to make changes in , which necessitates a change in the master file (this was before Next.js was widespread or even usable for our needs). This has led to a beast, lurking within our system, an insatiable beast called the "Cruft Creature" HomeDrafts Home Routes The Cruft Creature is fed by deadlines. The Cruft Creature eats developers in a rush. It devours your future, by giving you a temporary reprieve in the present. It kills time. It kills your future. Squidward needs to chill. Stressing me out. There a weapon that is said to be able to destroy the Cruft Creature...it's a powerful set of tools: refactoring, rewriting, and throwing away obsolete code, among other tools. However, these weapons are deadly! In the wrong hands, you can destroy yourself in the process...don't overdo it, in other words. is I've been beating back the Cruft Creature, in our own codebase. It has retreated into the dank depths for now. But they say it has siblings... Siblings that feed on other codebases, other systems... 😱 One of them...MAY EVEN BE YOURS! All gifs courtesy of Tenor.com.

Different

Universal Basic Income: "Threat or Menace?"

Top 10 Programming Languages for Web Devs to Learn During Quarantine

Latest writings on my blog

Too Long; Didn't Read

Make resilience your competitive advantage

Bugs, Cruft, and Other Spooky Code-stuffs

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

The New Year’s Resolutions Mega Thread

104 Stories To Learn About Go

105 Stories To Learn About Functional Programming

100+ Free Pluralsight Courses to learn Python, Java, and Spring Boot

10 Websites to Learn JavaScript for Beginners

The New Year’s Resolutions Mega Thread

104 Stories To Learn About Go

105 Stories To Learn About Functional Programming

100+ Free Pluralsight Courses to learn Python, Java, and Spring Boot

10 Websites to Learn JavaScript for Beginners

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps