Project ideas from Hacker News discussions.

My spicy take on vibe coding for PMs

📝 Discussion Summary (Click to expand)

1. PMs are stepping into the code‑writing role
The discussion is dominated by the idea that product managers (PMs) will use LLMs to “vibe‑code” prototypes or even production changes.

“PMs coding unlocks a whole new category of work, mainly addressing the long tail of cool ideas/small optimisations that ordinarily would not be addressed.” – raviisoccupied
“I think this is the main takeaway, but I'm curious how bad the PM must have been at communicating to begin with if this is necessary.” – sublinear

2. Quality, safety and accountability are at risk
Many commenters warn that letting non‑engineers ship code creates bugs, hard‑to‑debug production issues and a blurry ownership trail.

“If the person shipping code doesn’t understand it, can’t debug it, and won’t be around when it breaks in production, who’s responsible?” – nachocoll
“Vibe coding doesn’t help in ‘Understand the systems’ – it’s the opposite.” – nevertoolate

3. The value of engineering vs PM skill sets is contested
The thread debates whether engineers should become PMs, whether PMs should become engineers, and how AI changes that balance.

“Most seniors are hired for their code readability and real‑life experiences with real products and problems.” – otabdeveloper4
“The dedicated PM role will vanish and the classic BigCo PM will need to look a lot more like the startup one.” – dmckinno

4. Organizational incentives and culture shape the outcome
Comments highlight how metrics, on‑call expectations, unpaid overtime and a “move‑fast‑break‑things” culture influence whether vibe coding is embraced or rejected.

“Leadership claims they are aware of Goodhart’s Law, but their actions show otherwise.” – 650
“Unpaid overtime is common across the continent for salaried positions.” – closewith

These four themes capture the core of the discussion: the shift of PMs into coding, the risks to quality and accountability, the ongoing debate over the relative value of engineering and PM roles, and the cultural/incentive forces that determine how AI‑assisted coding is actually used.


🚀 Project Ideas

ProtoGen

Summary

  • Enables product managers to turn natural‑language feature ideas into interactive, code‑ready prototypes in minutes.
  • Cuts the “idea‑to‑demo” lag, improves stakeholder alignment, and reduces the risk of mis‑specification.

Details

Key Value
Target Audience PMs, designers, and early‑stage founders in tech companies
Core Feature AI‑driven UI mockup & skeleton code generator with live preview, version control, and export to GitHub
Tech Stack Next.js, TypeScript, OpenAI/Claude API, GitHub Actions, Docker
Difficulty Medium
Monetization Revenue‑ready: $29/month per user, enterprise tier with SSO and audit logs

Notes

  • HN commenters lament “you make a better product if you plan it out first” and “communicating a feature with a doc or mock can be really hard.” ProtoGen gives a quick visual and code baseline that satisfies both sides.
  • The tool can be used to create “proof‑of‑concept” repos that can be merged into the main branch after a short review, speeding up the feedback loop.

CodeAudit AI

Summary

  • Automatically reviews AI‑generated or human‑written code for quality, security, and compliance before it hits production.
  • Provides a risk score, actionable suggestions, and CI/CD gate integration to prevent buggy or insecure deployments.

Details

Key Value
Target Audience Engineering teams, DevOps, and PMs who ship AI‑generated code
Core Feature LLM‑powered static analysis, unit‑test generation, security scanning, and risk scoring
Tech Stack Python, FastAPI, OpenAI/Claude API, GitHub Actions, Snyk, OWASP ZAP
Difficulty High
Monetization Revenue‑ready: $99/month per repo, enterprise plan with on‑prem deployment

Notes

  • Addresses the frustration that “PMs landing prod diffs” often produce low‑quality code. CodeAudit AI enforces accountability and quality without stifling speed.
  • The risk score can be displayed in PR comments, making it visible to all stakeholders.

OnCall Scheduler & Compensation Tracker

Summary

  • Automates on‑call rotation, tracks hours, calculates fair compensation, and provides analytics to prevent unpaid overtime.
  • Integrates with Slack, Jira, and payroll systems to give visibility to managers and employees.

Details

Key Value
Target Audience Mid‑size to large tech companies, HR and engineering managers
Core Feature Rotational scheduling, real‑time alerts, overtime calculation, payroll integration
Tech Stack Node.js, PostgreSQL, Slack API, Jira API, Stripe for payouts
Difficulty Medium
Monetization Hobby (open source) with optional paid support and custom integrations

Notes

  • Responds to comments about “unpaid overtime” and “on‑call rotation” pain points. By automating compensation, it reduces friction and improves morale.
  • Analytics dashboards help leadership spot patterns and adjust policies proactively.

SpecGen

Summary

  • Reverse‑engineers existing codebases into detailed, human‑readable specifications and documentation using LLMs.
  • Helps PMs, new hires, and auditors understand system behavior, edge cases, and test coverage.

Details

Key Value
Target Audience PMs, technical writers, onboarding teams, compliance auditors
Core Feature Code‑to‑spec extraction, test‑case generation, API documentation, and change‑impact analysis
Tech Stack Python, LangChain, OpenAI/Claude API, GraphQL, Markdown generator
Difficulty Medium
Monetization Revenue‑ready: $49/month per repo, enterprise tier with custom model fine‑tuning

Notes

  • Tackles the frustration that “vibe coding” leaves “debris in the database” and “edge cases” unhandled. SpecGen surfaces hidden assumptions and provides a safety net.
  • The generated specs can be stored in a knowledge base, making future maintenance and onboarding faster and less error‑prone.

Read Later