4 Comments
User's avatar
Twone_Offshore's avatar

Very nice. Much appreciated.

Uri Kogan's avatar

This is an excellent way to describe what I have been doing. Thanks for writing it up and for the resource list. I have felt there was a missing middle between vibe coding for non engineers to create one shot apps an vibe coding for engineers who can go very deep and have the habits well engrained. As a PM I know the habits / practices I need from observation of engineering teams, but they aren’t second nature.

Andrew Oppong Writes's avatar

Awesome set of resources here. This is indeed very helpful not just for a vibe coder but for every engineer. It is a good set of references to keep going back to frequently to stay knowledgeable.

Thanks for sharing!

Patricia Juarez @ AWS's avatar

Thanks a lot for sharing. Part of engineering is to analyze the different options before choosing frameworks and libraries. In the post I missed why Clerk with Supabase if Supabase includes authentication. I also got surprised about not seeing Google Analytics (I might be old, 15 years ago it was a no brainer to use it)

I would love too a similar post filling the PM side of releasing products with AI. Engineers who built products using Vibe engineering, don’t know about monetizing and delivering them with immediate success.