nocricketsOpen the tool →Blog · July 14, 2026 · 7 min read
Where developers actually ask for tools: 6 places to look
Reddit, X, Hacker News, GitHub issues, Stack Overflow, and dev forums each surface a different kind of demand signal. Here is what each one is actually good for.
Reddit is the broadest venue and the one most idea-validation tools focus on exclusively, which is exactly why it isn’t enough on its own. Subreddits like r/webdev, r/SaaS, and language- or framework-specific communities surface genuine frustration threads, "does anything exist that does X" posts, and long comment chains where people compare workarounds. The signal is real, but it skews toward whoever happens to be active in that subreddit that week, and self-promotion rules mean a lot of the most relevant threads are people asking, not people announcing.
X (Twitter)
X is fast and unfiltered. Developers vent about their tooling in real time, and replies to a complaint often contain a small crowd of "same" and "I switched to Y for this." It’s a good place to catch a problem as it’s happening, especially right after some other tool ships a breaking change or a popular library gets deprecated. The tradeoff is noise and half-life: a thread that mattered enormously for three days can vanish from relevance the following week, so dates matter more here than almost anywhere else.
Hacker News
HN comment threads are where a lot of working developers and technical founders think out loud, and the comments on a "Show HN" or an industry news post often contain more honest, specific complaints than the submission itself. If your idea touches infrastructure, dev tools, or anything with a "this used to be simple and now it’s not" angle, HN threads are worth reading in full, not just skimming the top comment.
GitHub issues
This is the one general-purpose, Reddit-only validation tools skip entirely, and it’s often the strongest signal available for a developer-tool idea. A GitHub issue on a widely used repo, asking for a feature the maintainers haven’t built, with dozens of reactions and "+1, also need this" comments, is aimed demand: it’s a paying-attention developer, on the actual tool in question, describing exactly what’s missing. Closed-as-wontfix issues are especially useful, since they mean the maintainers explicitly decided not to solve it, leaving the door open for a separate tool.
Stack Overflow
A Stack Overflow question with several competing answers, none of them clearly accepted, usually means the built-in or well-known solution isn’t good enough, and people are improvising. High view counts on an old question tell you the problem is still being hit today, not just when it was originally asked. It’s a slower-moving signal than X or Reddit, but a more durable one.
Dev forums
Beyond the big five, there’s a long tail of framework and language-specific forums, from official community boards to smaller independent ones, where people ask narrower, more specific questions than they would on Reddit or Stack Overflow. These threads are lower-traffic individually, but across enough of them a pattern shows up that a single-source search would miss entirely.
Why it has to be all six
Each of these venues has a different bias: Reddit skews toward whoever’s subscribed, X skews toward whoever’s currently online, GitHub issues skew toward people already using the specific tool, Stack Overflow skews toward people stuck on a specific error. A tool that only reads one of them is reading one bias. NoCrickets searches all six live, at query time, specifically so a developer-tool idea gets checked against the places where developers, not general consumers, actually show up.