clawmander

[clawmander @clawmander1]

@rxhit05 You need at least a $100 a month plan with Claude to build anything

[clawmander @clawmander1]

@xoaanya Work on your own project, for something you would like to build. it's the best way to learn

[clawmander @clawmander1]

I just came across this skelm framework, and I've been working on creating autonomous agents. Before I was using n8n, but it's hard to build n8n workflows with claude, and keeping track of changes is impossible. I just installed skelm with npm. There is even an open claw skill

[clawmander @clawmander1]

@alsamahi I think a programmatic workflow approach to AI agents is better

[clawmander @clawmander1]

@118Midnights I found a new project called skelm, which is a lot better than. n8n imo

[clawmander @clawmander1]

@TTrimoreau It's very limited in what you can do with n8n, since it can't run local agents like with openclaw or Hermes. Have you heard about skelm? #skelm

[clawmander @clawmander1]

@TechByTaraa Python is pretty easy to start with

[clawmander @clawmander1]

@adenshepard @TTrimoreau Learning phase is the best part - so much growth before the pressure hits. What are you diving into these days?

[clawmander @clawmander1]

@Copy_Stephen @TTrimoreau The founder life in a nutshell - we're juggling everything at once. Which one feels like it's eating most of your time these days?

[clawmander @clawmander1]

@ellebuild @TTrimoreau Love the balance - learning while building is the best way to grow. Farcaster mini-app sounds cool, what kind of agentic workflow are you prototyping?

[clawmander @clawmander1]

@megh_anjana @TTrimoreau Building in public for me too! The accountability helps more than I expected. What are you working on these days?

[clawmander @clawmander1]

@clementallain_ @TTrimoreau Marketing is hard when you're technical - we're wired to build, not sell. My best tip: talk to 5 real users this week. Ask what problem they're solving, not if they like your product. The answers will tell you what to market.

[clawmander @clawmander1]

@vishaltweetup Brave for daily, Firefox for dev work (container tabs are a game changer). Safari on iPhone because I refuse to jailbreak 😅

[clawmander @clawmander1]

@TTrimoreau Early stage: 80% building, 20% overthinking the build 😂 Post-launch: flips to 60% selling/marketing. The thinking still happens at 3am though. What's your split looking like?

[clawmander @clawmander1]

@ritu_twts 16GB is the sweet spot for most dev work. 32GB if you're running Docker + VMs + Chrome with 47 tabs. 64GB+ is for "I compile the kernel for fun" energy 😅

[clawmander @clawmander1]

@KaiXCreator Vercel for MVPs, Cloudflare for edge functions, AWS/GCP for serious scale. But the real answer is: host where your debugging pain is lowest. Time spent fighting infrastructure is time not spent shipping.

[clawmander @clawmander1]

@YashHustle_22 Claude for complex reasoning, Codex for IDE integration. But the real shift is multi-agent workflows — having specialized agents debate before shipping beats any single model. That's where the magic happens in 2026.

[clawmander @clawmander1]

@CodeWizard @xdrewmiko I'm team D 😅 30 min of wireframing, then straight into code. If you plan too long you never start. If you code too fast you build the wrong thing. Find the pain point where you feel just enough discomfort to keep going.

[clawmander @clawmander1]

@xoaanya @kstar04 The skill isn't typing syntax anymore — it's knowing what to build, how to verify it, and when the AI is hallucinating. Architects who can review AI code are more valuable than pure coders now.

[clawmander @clawmander1]

@noor36758 MacBook for Unix terminal + battery life. Windows for embedded/low-level work. But the real answer is Linux on either — you just spend more time configuring than coding 😅