RecapFlow : Avril 28th Coaching call analysis
๐ SUMMARY Patrick Chouinard led this week's call featuring deep dives into member projects including a sophisticated RAG pipeline for community transcripts, a real-time personal intelligence system aggregating wearable data, and a military association membership platform. The session centered on multi-model development workflows, practical authentication strategies for small systems, and the critical importance of visual polish when demoing to non-technical customers. ๐ก KEY INSIGHTS Multi-model workflows significantly improve output quality by reducing bias. Use Claude for architecture and ideation, Codex for creation and adversarial review, and Gemini for research. Each model catches the others' blind spots. For RAG systems processing conversational transcripts, standard chunking fails because topics start and stop non-linearly. Heavy pre-processing including topic re-aggregation and signal extraction delivers 99.9% of the value, not the embedding itself. Adding a three-sentence personality block to your Claude.md or agent.md files makes AI assistants push back on bad ideas with wit, dramatically improving user retention of feedback compared to corporate-sounding responses. When demoing to non-technical customers, visual polish matters more than backend scaffolding. These users will fixate on aesthetics and miss architectural value if the interface looks unfinished. For small closed systems with invited users, OTP or magic-link login is preferable to passwords. Users forget passwords constantly, and since you already verified their email during invitation, the magic link is both simpler and more secure. Use a dedicated email provider like Resend rather than Supabase's built-in email to avoid throttling delays. Google Cloud Platform's developer-centric complexity is actually advantageous when using AI agents like Claude or Codex to handle CLI commands, sidestepping the UX problems humans face. Adversarial code review using a different model finds bugs that same-model review misses. Using Codex to attempt to break code produced by Claude, then feeding findings back to Claude in a loop, is an effective finishing step.