Hi all, I was wondering… Nate has lots of great stuff for helping with automations, workflows, improving job tasks, etc… That said, one of the bigger things I am working on is an app for engineers. It’s fairly complex and I’ve never designed an app before. I have figured out how to acquire the needed information that powers it, but I need to learn more about things like general security, authorization, general development principles (so I don’t blindly trust Claude), and then how to get broader compliance like SOC-2 and others since this would be used by large companies at higher levels. Where’s the best place to start with this? I Like this channel for everyday applications and uses, but this is a bit more specific and Nate often mentions he doesn’t build apps. Any guidance? Channels, documents, books, etc… I’ll take anything!

Hey everyone, I've built a platform called ConnectYourBot that helps businesses and influencers manage all their customer conversations in one place, WhatsApp, Instagram, Messenger, and website chat and automate replies with AI, so they never miss a lead or an order. It also handles WhatsApp bulk marketing for reaching customers at scale. It's almost ready to launch, but I don't have a marketing budget right now, so I have to go the organic route. Would love suggestions from people who've done this before, where would you go first to find early users? Any communities, cold outreach, or content approach that actually worked for you?

Right now I'm using Codex, but I feel like I'm hitting the limits very quickly. Which one do you think offers better value for money: Claude or Codex?

Fable is not really for planning — did you know that, or am I wrong? From what I understand, Opus is stronger for planning and architecture, Sonnet is better for executing clear tasks, and Fable is better for long, difficult, or ambiguous execution where the model needs to investigate, test, review, and close the loop. So Fable can plan during execution, but it is not mainly “the planning model.” The confusion is thinking that Fable is the planning model and Sonnet is the execution model. That is not quite right. The practical rule is: Opus is best for planning. Sonnet is best for executing well-defined tasks. Fable is better for difficult, long, or ambiguous work because it tends to investigate, test, review, and close the loop more carefully. Use Opus when you need to design the architecture, write a spec, define phases, or think through the strategy before touching the code. Use Sonnet when the plan is already clear and the task is to implement, edit files, run tests, and fix clear issues. Use Fable when the project is still unclear, has hidden bugs, requires investigation, involves multiple steps, or needs more autonomous execution. There is also an important difference in Claude Code: Using `/model opus` means using Opus for everything: planning, execution, and review. Using `/model opusplan` means using Opus for planning and Sonnet for execution. So, simply telling Opus “I want to plan” does not automatically activate `opusplan`. To use that hybrid flow, you need to explicitly select `/model opusplan`. Final summary: Opus thinks through the plan. Sonnet executes the plan. Fable handles the work when it is difficult, long, or ambiguous. `opusplan` combines Opus for planning with Sonnet for execution. https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-fable-5

I ingested all my YouTube videos into an LLM wiki and turned them into a connected second brain that my AI OS can actually reason over. In this one I show you how to build the same thing in about five minutes using Claude Code and Obsidian, based on Andrej Karpathy's LLM knowledge base idea. You drop in sources, the AI reads them, splits them into cross-linked wiki pages, and keeps the whole thing organized with routing rules so it can find anything fast. By the end you'll know how to set up the vault, write the schema, ingest a PDF and a URL, and decide when to keep your wiki flat versus structured.