Activity
Mon
Wed
Fri
Sun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
What is this?
Less
More

Memberships

Chase AI Community

68.1k members β€’ Free

AI Developer Accelerator

11.3k members β€’ Free

77 contributions to AI Developer Accelerator
AI Developer Accelerator β€” Coaching Call - June 16th
AI Developer Accelerator β€” Coaching Call - June 16 VIEW RECORDING - 89 mins (No highlights) Meeting Purpose Share project updates and discuss strategies for AI development. Key Takeaways - Fable's absence is a setback, but developers are adapting with multi-model workflows (e.g., Claude for planning, Codex for coding) and focusing on deterministic scaffolding to maintain control. - New projects include an AI-native CRM for UK estate agents (Ryan), a positive-only "KindMark" platform for service workers (Ty), and an AI photo booth (Juan). - Patrick developed "AgentOps," a meta-scaffolding for Hermes using NATS as a "nervous system" to monitor and manage his home lab infrastructure. - A key strategy is using an "adversarial" system prompt to force the AI to challenge assumptions and clarify the core business problem, preventing it from amplifying broken processes. Topics Fable's Absence & Mitigation Strategies - Fable's shutdown is a significant setback, but developers are adapting with multi-model workflows. - Ryan: Uses Opus for iteration on a Fable-generated V1 plan. - Ty: Used Fable for initial problem-solving but found it unusable for security auditing, a critical step. - Paul: Combines Opus for projects with Codex for validating requirements documents. - Patrick: Prefers a collaborative model that challenges assumptions over one that simply executes instructions.
0
0
RecapFlow : June 16th Coaching call analysis
πŸ“ SUMMARY This week's call opened with the community offering condolences to Patrick Chouinard and Paul Miller, who both recently experienced family losses. Patrick shared how Claude helped him compress two months of estate administration into 48 hours during his bereavement. The technical discussion centered on coping strategies following the sudden unavailability of Anthropic's Fable model, with members sharing alternative workflows combining Claude Opus 4.8, Codex GPT-5.5, and the emerging Fusion architecture. A strong consensus emerged around the danger of automating broken business processes, alongside practical demonstrations of adversarial prompting and agent scaffolding strategies. πŸ’‘ KEY INSIGHTS Estate administration acceleration: Claude processed funeral home paperwork and proactively searched government websites for required forms and benefits, reducing administrative burden from months to hours while demonstrating unexpected emotional sensitivity by pacing tasks and flagging only time-sensitive items. Deterministic over autonomous: Keep systems as deterministic as possible, using AI decision-making only where necessary. The value in coming years lies in scaffolding and infrastructure rather than end-to-end autonomy. Model specialization: For terminal, infrastructure, and script work, GPT-5.5 (Codex) currently outperforms Claude Opus 4.8, while Opus remains superior for UI-backed application development. Adversarial prompting: Patrick's system prompt configures Claude as a challenging business analyst that asks "what problem are you actually trying to solve?" rather than accepting stated solutions at face value. Placed in Claude.md at the user level, it applies to every session including Claude Code. Process integrity warning: AI amplifies broken business processes rather than fixing them, making dysfunction bigger and more visible. Intention is a muscle that atrophies when over-relying on highly autonomous models. Intent queue workflow: Ty's method uses Claude's background commands to capture context-rich questions, storing them locally to surface as a primed queue at the next session, saving token spend on re-priming.
0
0
Go/Vue or next.js?
For those building AI-native apps, what are your thoughts on a Go + Vue stack? How does it compare to Next.js in practice? Are there situations where Go + Vue is clearly the better choice, or do you still prefer Next.js for most AI applications? I’d love to hear about real-world tradeoffs around performance, developer experience, deployment, and scaling.
1 like β€’ 3d
@Tom Welsh nailed the shape of it, so I'll just add the part that actually bites you in production once you're past the demo. For "AI-native" specifically, the stack debate matters less than how you handle streaming and long-running work. That's where Next.js and Go split in practice: - Next.js gives you the fastest path to a user-facing AI product. Token streaming, the Vercel AI SDK, auth, routing, SEO, all batteries-included in one TypeScript codebase. The catch nobody mentions upfront: serverless function timeouts. The moment you've got multi-minute agent runs, tool-calling loops, or background jobs, you're fighting the platform, reaching for queues, edge runtime workarounds, or a separate worker anyway. - That's exactly the seam where Go earns its keep. Long-lived connections, concurrent fan-out to model providers, retries and backpressure on a flaky upstream API. Go's concurrency model makes that boring instead of brittle, and the single-binary deploy is genuinely a quality-of-life upgrade when your control plane gets complex. So I land where you did: Next.js as the default for the product surface, Go services underneath once the orchestration gets real. The "thin Vue UI over a Go control plane" pattern is great when the backend is the product, but for most user-facing AI SaaS, Next.js front plus Go for the heavy orchestration gives you the best of both without making the frontend team learn two ecosystems. One honest tiebreaker that has nothing to do with performance: what can your team ship confidently today? A solo dev or a TS-heavy team will out-build a "better" architecture they're slower in. The stack you can move fast on usually beats the stack that benchmarks better. (And +1 that the AI SDK ecosystem still leans hard toward TS. That's a real, underrated reason the default tilts Next.js.)
AI Developer Accelerator β€” Coaching Call - June 16th
Plot twist: bringing a friend to watch you work is now a certified business strategy, "guarded surfaces" have nothing to do with skateboarding, and Anthropic's Fable model as been removedβ€”so if you haven't stress-tested your architecture with it yet, consider this your friendly eviction notice. πŸ“ž 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. Curious if Ty nailed the "explain it to a 10-year-old" test for ShipSafe's messaging? Wondering how Juan's first AI Booth deployments went with his observer friend catching all the customer reactions? Or whether Ryan managed to squeeze every last drop of Fable wisdom before the paywall hits? Come find outβ€”or bring your own experiments to share. πŸ”— ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 πŸ“… WHEN Tuesday June 16th at 6PM ET Looking forward to seeing you on the call!
6
0
AI Developer Accelerator β€” Coaching Call - June 9th
Impromptu Zoom Meeting - June 10 VIEW RECORDING - 89 mins (No highlights) Meeting Purpose Reviewing current AI projects and discussing Anthropic's new Fable model. Key Takeaways - ShipSafe: Ty presented a platform to control AI agents, solving critical issues of runaway costs, security, and authorization for non-reversible actions. - AI Booth: Juan's AI-powered photo booth is ready for its first event. The strategy is to personally manage the initial deployments to refine operations before hiring. - Digital Signage: Ryan's retail signage SaaS is scaling, with new remote management features like diagnostics and one-click updates to improve operational efficiency. - Fable Model: Anthropic's new Fable model is powerful for macro-level tasks but costs 2x Opus tokens. It's free to use until June 22, after which it becomes token-only. Topics Anthropic's New Fable Model - Anthropic released Fable, a new model from the Mythos family. - Key Characteristics: Cost: 2x token usage of Opus. Availability: Free to use until June 22, then token-only. Use Case: Excels at macro-level tasks (e.g., refactoring an entire app) over micro-level problems. - Strategy: Use Fable for large projects before the June 22 deadline. - Note: Security analysis tasks may be redirected to Opus 4.8.
0
0
1-10 of 77
Patrick Chouinard
5
249points to level up
@patrick-chouinard-8756
AI strategist & IT generalist building local LLM stacks, RAG chatbots & automation pipelines. Pragmatic, future-focused, and debate-ready.

Active 3h ago
Joined Jun 27, 2025
Montreal, Quebec, Canada
Powered by