Few days ago I started to practice and code an aios type project with the help of claude code. I have learnt a lot and hope to reach level 3 to unlock Nate's tutorial for it to get more knowledge of what I'm lacking right now. Good luck on your projects guys!😄

Recently, I moved from building N8N workflows manually to using Claude Code to build the workflows. Here are five lessons I've learned from building in N8N workflows with Claude Code. Lesson 1. Be Specific. Be specific with your goal and your desired outcome. A good way to make sure Claude knows specifically what you want to achieve is to write up a technical document or project report containing some brief detailed information about what your building, who you're building it for, the problem you're trying to solve, along with other project specifications you think might be important. The document you feed Claude doesn't have to be long, nor does it have to contain all the information about the architecture of the workflow, the different nodes you would use, or any other technical information that a builder would normally need to know. Treat Claude like a developer. Just give Claude a brief report telling it what you want and any specific details you have that you can provide and let Claude do the thinking and designing. Lesson 2. Don't just jump in to building the workflow with. Put Claude in planning mode and make sure Claude asks you specific questions about what you are trying to achieve. I've noticed that sometimes Claude will think of things that I didn't think of. Get Claude to ask you questions about your project so it knows more about what it needs to do to create the most satisfactory outcome. Lesson 3. If your project is a complex project that requires multiple workflows, ask Claude to spin up some agents that can work in parallel and build multiple workflows at once. The workflows won't be production-ready immediately. They will need to be tested, and you'll have to test each of them one by one. Having Claude's spin-up agents that work in parallel will save you time. Just make sure that Claude has a solid understanding of your project before asking Claude to spin up multiple agents to build each of the workflows. Lesson 4. Create backups and periodically save your progress. Use GitHub and JSON files to save your progress and back up your workflows and projects. By creating a GitHub repository, you can download your projects and the workflows from GitHub to your laptop when you're not using your desktop. Once you're done working on your project on your laptop, you can ask Claude to push the changes to GitHub and then download the changes from GitHub to your desktop and proceed from there. GitHub is a free cloud service you can use to save your project.

Most people are using AI completely wrong. They’re treating it like a chatbot instead of a system. The biggest shift happening right now is not “AI content creation.” It’s AI replacing workflows. The people who will win over the next 3–5 years are the ones who understand how to connect: - LLMs - automations - APIs - databases - business processes into systems that actually produce outcomes. A lot of businesses still operate with: - manual lead qualification - repetitive admin work - disconnected software - slow response times - poor customer follow-up AI automation changes all of that. We’re moving from:“AI helps humans work” to: “Humans supervise AI systems that work.” That’s a massive difference. The interesting part is that most of these automations don’t even require advanced coding anymore. With tools like: - n8n - Claude Code - Make - OpenAI APIs - vector databases - browser automation small teams can now build systems that used to require entire departments. A single operator with the right AI stack can: - automate inbound lead handling - generate personalized outreach - summarize meetings - qualify prospects - create content pipelines - build internal AI assistants - automate reporting - optimize business operations This is why AI automation is becoming such a valuable skill set. Not because AI replaces humans. But because people who know how to orchestrate AI systems become exponentially more productive. The real opportunity isn’t just “using ChatGPT.” It’s understanding how to build repeatable systems around AI. That’s the difference between casual AI users and AI operators. Curious where everyone thinks this space is headed over the next few years.

I spent 100 hours testing Claude Code vs ChatGPT Codex and what I found genuinely surprised me. Same prompts, same builds, both tools side by side, and one of them hit way harder than I expected. If you're picking between coding agents right now, then this video is the breakdown you actually need before you commit.