User
Write something
Weekly Coaching Call is happening in 4 hours
Pinned
AI Developer Accelerator โ€” Coaching Call - May 5th
Patrick's about to drop an open-source Community Brain preprocessing pipeline and test whether Claude Design can handle our chaos, while Juan prepares to demo an AI photo booth that actually delivers photos via QR code. If you missed the multi-model workflow magicโ€”where Claude architects, Codex builds, and Gemini researchesโ€”you missed three AIs arguing about your code so you don't have to. ๐Ÿ“ž HOW THE CALLS WORK The calls can run 2+ hours. We want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the structure: ๐Ÿ‘‰ Reply to this post with your questions before the call ๐Ÿ‘‰ If you submit a question and you're on the call, you go first ๐Ÿ‘‰ We work through questions in the order they came in ๐Ÿ‘‰ Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. Patrick will have updates on Claude Design and his Cohere meeting about multimodal embeddings, Juan is bringing the AI photo booth demo with QR code delivery, and Tom might have that Resend OTP implementation ready to show. If you were waiting to see the Community Brain pipeline go open source or Ty's Propria system hit GitHub, this could be your week. ๐Ÿ”— ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 ๐Ÿ“… WHEN Tuesday May 5th at 6PM ET Looking forward to seeing you on the call!
3
0
Pinned
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.
1
0
Pinned
๐Ÿš€ Welcome to AI Developer Accelerator (Start Here)
๐Ÿ‘‹ Hey there! Ready to supercharge your dev skills with AI? You're in the right place. Watch the intro video below for a walkthrough of our community and a peek at our AI-enhanced future. ๐Ÿ›  CLASSROOMS: - Full Stack Development with AI: Where code meets cognition. Sharpen your skills and build AI-- powered apps. - CrewAI: Your squad for all things AI. Share ideas, collaborate on projects, and celebrate successes together. - Code Bugs & Project Issues: Debug like a pro. Get help on tricky bugs and offer your wisdom to others. - Monetize Your AI Dev Skills: From AI code to income: Collaborate, innovate, and monetize your dev skills! - YouTube Tutorial Requests: Please let me know what you want to learn more about when it comes to Fullstack Developement and AI. ๐Ÿ“œ RULES: - Promotions are a no-no. Let's keep the focus on learning and growing. - We appreciate quality contributions. Enhance your posts with visuals and use ChatGPT for refining your content. - No talking about politics or religion. Go to X if you want to talk about that. - See something off? Help us maintain the community spirit by reporting any issues to me. ๐Ÿฅ‡ FIRST STEP: Introduce yourself with a post about your AI journey and what you're working on in the General Discussion group. **Bonus points for sharing a screenshot of your current app!** ๐ŸŽฏ ACTIONS: Be proactive, engage in discussions, and collaborate on group projects. ๐Ÿ‘ฉโ€๐Ÿ’ป๐Ÿ‘จโ€๐Ÿ’ป Let's code, innovate, and thrive together!
AI Developer Accelerator โ€” Coaching Call - April 28th
Last week Brandon burned through $120 in Claude credits in 30 minutes while proving the "SaaSpocalypse" is realโ€”rebuilding a $20 SaaS in under an hour and making everyone panic about their lack of moats. If you missed the chaos, you missed the survival guide for what happens when AI makes code trivial to replicate. ๐Ÿ“ž HOW THE CALLS WORK The calls can run 2+ hours. We want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the structure: ๐Ÿ‘‰ Reply to this post with your questions before the call ๐Ÿ‘‰ If you submit a question and you're on the call, you go first ๐Ÿ‘‰ We work through questions in the order they came in ๐Ÿ‘‰ Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. We've got some delicious follow-ups brewing: Ty is running his ShipSafe security scanner against Morgan's catio site (cybersecurity meets cat patios), Patrick is polishing that elegant multi-model pipeline for open source release, and Tiran is stripping his landing page down to a single address input. Perfect time to jump back in if you want to see how the experiments land. ๐Ÿ”— ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 ๐Ÿ“… WHEN Tuesday April 28th at 6PM ET Looking forward to seeing you on the call!
Botsd, Bots and more bots
To the @admins. Appologies, but I have just reported about 10 bots in need of a band and delete posts ( bearing in mind none of them have made any posts) All 10 7 day leader board entries are bots, 9 out of the 10, 30 day leader board entries are bots. @Brandon Hancock Wen you get a minute can you turn on some of the following 1. Tighten Membership Approval - Disable Instant Membership Approval: Change your settings to manual approval. This allows you to inspect profiles before they join. Go to Settings > Plugins > Instant membership approval: OFF. - Enable Membership Questions: Require new members to answer questions about their bio, location, or intent. If they fail to answer or provide spammy answers, ban them immediately. - Check for "High Risk" Flags: Look for the "high risk" spam warning in new membership requests, a feature Skool introduced to identify suspicious accounts early. 2. Restrict Activity & Content - Raise Required Levels for Posting: Stop bots from spamming the community feed to earn points. Restrict posting to Level 2 or 3. This forces them to earn points through organic engagement rather than spam. - Set Chat Restrictions: Limit direct messages to a higher level (e.g., Level 3 or 4) to protect members from spam DMs, which is a common tactic for bots. - Use the New AutoMod: Utilize Skool's spam detection system to auto-flag suspicious content and quarantine spam accounts without needing manual review. 3. Active Moderation and Cleanup - Ban and Delete Activity: If a bot gets through and posts, use the Ban and Delete Last 7 Days of Activity feature. This removes them and all their spam posts instantly. - Report Profiles: Report spammers to Skoolโ€™s moderation team so they can be removed from the platform entirely, preventing them from jumping to other communities. - Enforce Community Rules: Clearly state in your community guidelines that point farming or unsolicited DMs will lead to an immediate ban.
1-30 of 1,816
AI Developer Accelerator
skool.com/ai-developer-accelerator
Master AI & software development to build apps and unlock new income streams. Transform ideas into profits. ๐Ÿ’กโž•๐Ÿค–โž•๐Ÿ‘จโ€๐Ÿ’ป๐ŸŸฐ๐Ÿ’ฐ
Leaderboard (30-day)
Powered by