Ideas Lab

Real problems people complain about online, pulled every morning and scored out of 100. Build, validate, or skip. How scoring works

Ideas
4,820
BUILD
702
Sources
8
Last sync
3h ago
382 ideas
Dev

Built my side project with vibe coding. almost shipped chaos. specs saved it. here’s my workflow

i’m building a small side project right now and i went full vibe mode at the start. it was fun until i realized the same thing keeps happening the AI ships fast, and then i spend 2x time unshipping the “helpful” extras so i switched to a simple process that keeps speed but adds adult supervision what i’m building a small SaaS style tool. FastAPI backend, Next frontend, Supabase for auth and db what changed everything for me i write a tiny spec for every feature before i let any tool touch code my spec template goal in one sentence non goals so it doesn’t add random features files allowed to change api contract. request response errors acceptance checks. exact steps to verify rollback plan. what to revert if it breaks my workflow 1 brain dump into Traycer AI and it turns it into a clean checklist spec 2 implement in small chunks with Claude Code or Codex 3 use Copilot for boring glue edits 4 run tests and force the tool to paste command output. no output. not done example acceptance checks i actually use auth try call endpoint with no token. should fail call with valid token. should pass rate limit hit endpoint 30 times fast. should start returning 429 db confirm Supabase RLS blocks cross user reads why i’m posting i’m curious if other side project people do specs like this or if you just raw vibe it and fix later also if you have any good tricks to stop agents from doing “bonus refactors” nobody asked for i want them if you want i can share the exact spec template file i keep in my repo. it’s short and it’s saved me a stupid amount of time

Reddit8mo agoToolDev

75FL score
0Sign in to vote

i keep a spreadsheet of every "why doesn't this exist" post i find online. here are the patterns after 6 months

started doing this as a personal exercise and got kind of obsessed. every time i find someone online describing a problem and asking why nobody's built a solution, i log it. the source, upvotes, industry, existing alternatives, and what's missing. 6 months and hundreds of entries later, clear patterns emerged that i didn't expect. **pattern 1: the word "overkill" is the strongest buying signal on the internet** when someone describes a tool as "overkill" they're telling you three things. the problem is real. they're currently paying for a solution. and they'd switch to something simpler in a heartbeat. i started specifically searching for "overkill" across reddit and review sites. the hit rate for finding buildable opportunities is insane compared to searching "i wish there was." **pattern 2: the highest pain industries aren't tech** trades, healthcare admin, property management, and local services show up constantly. these people have budget, they're underserved by software, and developers don't build for them because the niches don't sound exciting. 22 separate posts about pet medication tracking. zero good tools. 14 threads about trade contractor scheduling. everything is built for office workers. 9 threads about personal trainers managing clients through whatsapp because every fitness app serves the gym member not the trainer. **pattern 3: the best opportunities have terrible competitors, not zero competitors** zero competitors usually means zero market. nobody wants it. 3 to 5 competitors with bad reviews is the sweet spot. the market is proven because people are paying. the execution is bad because people are complaining. you just need to be less terrible. 10+ well funded competitors means you're too late for the broad play. but zoom in. there's almost always a niche they're all ignoring. **pattern 4: "i've been doing this manually for X years" is worth more than any market research report** this phrase shows up everywhere once you start looking f

Reddit8mo agoToolDev

80FL score
0Sign in to vote

Monthly Getting Started / Web Dev Career Thread

Due to a growing influx of questions on this topic, it has been decided to commit a monthly thread dedicated to this topic to reduce the number of repeat posts on this topic. These types of posts will no longer be allowed in the main thread. Many of these questions are also addressed in the sub FAQ or may have been asked in [previous monthly career threads](/r/webdev/search?q=flair%3AMonthlyCareerThread&restrict_sr=on&sort=new&t=all). Subs dedicated to these types of questions include [r/cscareerquestions](/r/cscareerquestions) for general and opened ended career questions and [r/learnprogramming](/r/learnprogramming) for early learning questions. A general recommendation of topics to learn to become industry ready include: - [HTML/CSS/JS Bootcamp](https://www.udemy.com/course/javascript-beginners-complete-tutorial) - [Version control](https://www.atlassian.com/git/tutorials/what-is-version-control) - [Automation](https://blog.logrocket.com/tools-and-modern-workflow-for-front-end-developers-505c7227e917/) - [Front End Frameworks (React/Vue/Etc)](https://www.freecodecamp.org/news/complete-guide-for-front-end-developers-javascript-frameworks-2019/) - [APIs and CRUD](https://www.freecodecamp.org/news/crud-operations-using-vanilla-javascript-cd6ee2feff67/) - [Testing (Unit and Integration)](https://raygun.com/blog/javascript-unit-testing-frameworks/) - [Common Design Patterns](https://www.patterns.dev/) You will also need a portfolio of work with 4-5 personal projects you built, and a resume/CV to apply for work. Plan for 6-12 months of self study and project production for your portfolio before applying for work.

Reddit8mo agoToolDev

76FL score
0Sign in to vote