I've been a developer for a while. I can build almost anything I want. And for more than a year I had the same problem: I couldn't figure out what to actually build. Every time I sat down to pick a project, I'd hit the same wall. "What's a real problem?" I'd read indie hacker threads. Scroll Hacker News. Bookmark Ask HN posts and never come back to them. Start two projects I abandoned inside a week because I couldn't convince myself anyone actually wanted them. The advice everyone gives you: "hang out in communities and look for patterns" is good advice. It's also slow, demoralising, and mostly impossible to do consistently while you also have a job. So I did the thing developers do when we're stuck: I built a tool for it. Veksa scrapes Hacker News, Dev.to, and Stack Exchange every day. It looks for complaints, questions, and frustrations, the stuff people write when they're annoyed. On Sunday night, Claude reads everything from the past week and clusters it into the 10 most-complained-about problems. On Monday morning, a digest lands in my inbox. It's free and it will stay free. I'm not trying to build a course. I'm not selling a playbook. I built it because I needed it. If you're in the same place I was - technically capable, directionally lost - subscribe. The first email goes out this Monday.

Veksa

The internet's loudest dev frustrations, weekly.

The internet's loudest dev frustrations, weekly.