In r/ProductManagement, PMs describe the AI boom pulling them into vibe coding prototypes and repo-driven workflows, while engineer-turned PMs struggle to stop coding and fully transition into facilitation.
I am an engineer-turned PM who is unable to let go of programming responsibilities because I feel it would be easier and faster and more to my liking if I just developed it myself.
I need help and insight from people who have had similar experiences on how to properly facilitate this transition.
I feel like I am in a completely different role now.
now my days are spent almost entirely vibe coding prototypes and working directly with AI tools to build things out.
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.
but here's the thing... instead of AI meaning less work, it means we need to deliver more.
Over the past 12 months I moved almost all my PM work into GitHub repos and Markdown files.
The unlock was maintaining a structured **context folder** per product: codebase, interviews, analytics, docs - all in one place, connected to live sources.
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