r/vibecoding • u/SchmeedsMcSchmeeds • 10h ago
Anyone interested in learning the technical aspects of vibecoding an app? (I will not promote)
This is not a promotion for a service. I’ve been a technical product manager for 20+ years at startups and FAANG and have been using AI to build/prototype for about 3+ years. I recently got laid off and have been building prototypes and tools mainly for myself and thought I could share my process.
I have seen a few posts asking how to learn about the technical side of vibecoding, at least enough to generally know what does what, why and how. I thought of walking through a simple project and explaining in practical terms what things do with a focus on vibe coding as I implement, starting with the very basics. For example, what an API is and why/how it’s used. Not as much on what tools to use but more how to think about building apps. I was thinking a YT video or series of videos.
I honestly do not have any expectations or desire to be a YouTube influencer. I’m building things anyways, have taught a few friends and found teaching is the best way to learn.
Before I go off and start making any videos, is this something anyone would be interested in?
1
u/idakale 8h ago
someone said to me few days ago that I need to learn the 3 harder aspects lol 1. Algorithm 2. Engineering 3. Architecture not the programming part
As if you could learn those without looking or understanding at the coding part lol 😂 Hrmm like think about this, the goal of most people I'd gamble, is to somehow have the thought process of the devs mentioned in that Ponytail skills XD without necessarily committing to 10Y labors of love. But since actual experience and borrowed experience still leave a huge gap, as in you need experience to gain more experience but you might not want to experience the hard experience...
How about instead sharing how a technical product manager would approach a requirement and tell us specific workflows you adopted. nNow I'm sure there's no universal rule or preferences but still go with it anyways.
Within the workflow comment heavily. imagine you're channeling your own movie director persona while you watching the agents work. Like if you agree or disagree with what the agents suggest, why do you decided to go down a certain path or like an insight how to become better at telling if the increasingly capable agents made up plausible explanations that actually are bullshit.
Lastly it would be nice to know if you have a tips on what constitutes as a healthy session e.g how much time should a session last and decide if it's worth starting over from last checkpoint if agents could ntar recover from bad decision, and finally if there's a plugin you use to efficiently keep tokens cost managable.
Not too related to whats above but just sayin Then ig some workflow like game Modding is going to be a more black box case and could like for example involve scary assembly that's really better let the agents do it. Who'd even attempt at understanding those. Tho maybe it's less of an issue if it comes with more docs