In r/ProductManagement and r/webdev, PMs are moving from writing detailed Jira requirements to building prototypes with AI and using repo-aware tools (Claude Code/Copilot) for context, while engineers push back on low-quality "vibe coded" contributions.
I’ve started using Claude Code to analyze repositories within my company recently.
it’s helps us in my Product team to be able to better prioritize tickets.
I used to spend so much time refining exact requirements for Jira tickets. now my days are spent almost entirely vibe coding prototypes and working directly with AI tools to build things out.
I'm a FE lead, and a new PM in the org wants to start pushing "vibe coded" slop to the my codebase.
I for one work in a product that is 15 years old and has gone through so many changes that the documentation is horrible. So I point my GitHub copilot with Opus 1 million context model at the repo and asked it to create architectur, design and other documentation for me
This finding is one of many signals tracked across Indiehacking. The live feed updates every few hours with new expert voices, debates, and emerging ideas.
← Back to Indiehacking