The 4-Question Filter That Killed My GitHub Star Habit
I star a lot of repos. Trending page, a newsletter link, whatever shows up mid-search for something unrelated. Almost all of it looks genuinely good. That was never the problem. The problem is "genuinely good" and "belongs in my stack" are two different questions, and starring something answers neither. One afternoon I stopped starring and started writing verdicts instead. Sixteen repos, one…
This article discusses a personal system for evaluating GitHub repositories, titled "The 4-Question Filter That Killed My GitHub Star Habit." The author, after reducing the habit of starring repositories, developed a filter based on four questions to determine whether a repository should be installed or not.
The first question is if the repository is a reference or dependency. The author found that many starred repositories were curated lists or guides, which do not have a runtime footprint and should be bookmarked instead of installed. This simple filter saves time by eliminating reference-versus-dependency confusion.
The second question asks if the repository already covers a role the user has in their current stack. This includes tools like ego-lite and holaOS, which are redundant and don't add any new capabilities. The author emphasizes asking if a current tool in the stack can already perform the function of the new repository, and if so, there's no need to install the new tool.
The third question focuses on whether the repository fits the user's actual hardware and scale. The author uses an example of a 45MB model built for phones/IoT, which would require a different hardware setup than the one they have. They stress the importance of knowing one's actual hardware limitations before evaluating a repository.
The fourth and final question asks if the repository solves a problem the user currently has. The author uses examples of tools like ToolJet, unsloth, and OpenCut, which don't solve any existing problems in their setup. This question helps the user focus on repositories that address current needs rather than hypothetical ones.
After applying this four-question filter, the author found that only one repository, a collection of technical interview preparation resources, met all the criteria and was the only one installed. The author emphasizes the importance of not installing repositories out of excitement or FOMO, but rather by purposefully applying the filter to make informed decisions about what to add to their stack.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
