Real problems people complain about online, pulled every morning and scored out of 100. Build, validate, or skip. How scoring works
Developers need simple, accessible online IDEs for quick coding, prototyping, and collaboration without heavy desktop setup. Despite existing tools, there's still demand for specialized or niche-focused online editors.
YC Graveyard17y agoToolDev
Developers need better tools than PhoneGap to create cross-platform mobile apps with native performance and easier development workflows.
YC Graveyard18y agoToolDev
Solo developers and small teams struggle with server deployment, monitoring, and maintenance tasks that require specialized DevOps knowledge. They need automated solutions that just work.
YC Graveyard14y agoToolDev
Designers create mockups in Figma/Sketch but developers still spend days manually converting them to code. This conversion bottleneck slows down web development workflows.
YC Graveyard14y agoToolDev
Mobile app developers need easy-to-integrate customer support chat systems that work seamlessly within their iOS and Android applications.
YC Graveyard14y agoToolDev
Indie game developers need simple, affordable ways to host multiplayer game servers without dealing with complex infrastructure setup.
YC Graveyard14y agoToolDev
App testing is time-consuming and expensive, but manual testing misses bugs. Developers need automated mobile testing that's accessible to small teams.
YC Graveyard14y agoToolDev
Software engineers experience significant stress and time burden from on-call shifts, seeking automation beyond just code review.
X6mo agoToolDev
Diagram languages and tools like Mermaid are error-prone, produce low-quality visuals, and fail to match professional tools like OmniGraffle.
X6mo agoToolDev
Spending 12+ hours fixing minor issues in projects, frequently reverting changes, scrapping work, and feeling guilty for wasting time without substantial output.
X7mo agoToolDev
Codex, Amp, Cursor, and others are starting to standardize around AGENTS.md (https://agents.md/) — a unified Markdown file that coding agents can use to understand a codebase. By contrast, CLAUDE.md feels too specific to Claude Code. It doesn’t work as well when collaborating with other developers who aren’t using Claude Code.
GitHub1y agoToolDev
PRs often depend on other PRs that need to be merged first, requiring manual waiting and rebasing of branches each time.
X7mo agoToolDev
After an API returned success but failed to apply a DNS change correctly, leading to 18 hours of downtime, now manually verifying every deployment before downtime periods like Shabbos because monitoring doesn't catch the issue.
X6mo agoToolDev
Still manually reviewing and annotating code even with Anthropic and other AI code review tools available, feeling like a loser for not having full automation.
X6mo agoToolDev
Developers encounter confusing dashboards and convoluted steps to un-provision old devices and provision new ones for app installation and testing in Apple's ecosystem.
X7mo agoToolDev
Indie app developers spend excessive time preparing and submitting apps to the App Store, dealing with compliance and review processes, needing a guaranteed service to handle it all.
X6mo agoOtherDev
Follow these steps: 1. Find the Right Communities Collect 10 subreddits where your target audience is active. Focus on communities where people discuss problems related to your product or service. 2. Understand Their Problems Read posts and comments to identify: Frequently asked questions Common frustrations Challenges your audience faces This helps you understand what people really need. 3. Send a Personalized Welcome Message Use r/DMdad to send a ready-made welcome message, but personalize it automatically. This will help you: Avoid being flagged as spam Increase reply rates Start a natural conversation 4. Help First Once someone replies, focus on helping them before selling. At this stage: Answer their questions Give useful advice Solve part of their problem for free The goal is to build trust at the MOFU (Middle of Funnel) stage. 5. Present an Irresistible Offer After providing value, introduce your solution.
Reddit6mo agoToolDev
Developers and businesses need data or functionality from websites that don't offer public APIs, forcing them to build fragile custom scrapers or integrations that break with site updates. This manual work takes weeks, requires constant maintenance, and delays projects. Teams either accept this overhead or abandon valuable data sources entirely.
Product Hunt6mo agoToolDev
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
Reddit6mo agoToolDev
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.
Reddit6mo agoToolDev