Demand board · computed November 2
What r/programming keeps asking for
Recurring demands mined from the community's top posts this week, with the threads as receipts. Not invented: if it's listed, people are actually asking.
Better tools and patterns for low-level performance optimization
People repeatedly share micro‑optimization techniques and IPC/CPU/graphics speedups, signaling demand for reusable tools, libraries, and diagnostics to find and fix hotpaths (SIMD, division, memory latency, lookup tables
Stronger vulnerability disclosure, auditing, and automated detection
Multiple posts about kernel TCP flaws, curl bugs, undisclosed patches, WebRTC issues and exploit chains show people want better disclosure processes, auditing tooling, and automated detection of critical security bugs
Faster, modern build systems and developer tooling to speed iteration
Posts about cutting CI time, the problems with Makefiles, and simple code checks (whitespace) reflect demand for faster CI, easier-to-use build systems, and lightweight developer tooling
Simpler, cheaper, and more secure email infrastructure
Questions about why sending email is expensive plus a post about email encryption indicate people want easier, lower‑cost, and more secure email tooling and services
Tools and practices to verify database correctness and performance
Jepsen results, articles on indexing, DB regressions and high‑throughput lookup work point to demand for better testing, benchmarking, and formal/concurrency verification for databases and storage systems
Get the board when it changes
Thinking of engaging here? Check r/programming's self-promotion rules first, and the wider method in the Reddit playbook. Thread Otter runs this same mining continuously on YOUR buyers' communities, with replies drafted when someone asks for what you build: start free.