We have created an AI bot for helping golfers with their game, since I'm not a golfer myself I wanted to check if anybody wanted to fire off 10 messages to the bot and give some light feedback?

Use prompt files to help you learn as you build. The fastest way to learn something is to have a real need for it. If you need to solve a problem, you will solve it no matter what. But without clients to build for, learning becomes a drag. 1. First, find a problem to solve. Check your own life. A friend's or family member's works too. Once you have that, use Claude to write the code. Before you start, do this. Create instructions for how you want the code to look and what your preferred languages are. 2. Ask Claude to write simple, readable code that a noob would understand. Ask it to create side folders with the code and test data so you can run it yourself. My favourite way to learn is to break the code and rebuild it. It teaches you how things work from the ground up. 3. On language, if you don't tell Claude what you prefer it will pick whatever it likes. Split code into two parts. Backend and frontend. Pick your languages. JavaScript for backend, React for frontend. Tell Claude to default to those. That way you will keep learning one language and get used to it. The same rule applies to tools. Pick a database you enjoy and set it as your default. Supabase works well. Do this while solving real problems. You will learn faster than watching tutorials with no goal. So that is it. If you want to learn, make it easy by learning while you build.

There is a big divide between two types of people. Person A sifts through data. They find the answers and test it themselves. They keep going until they solve their own problems. Person B asks questions and hoards information. They never take action. They buy courses hoping it will fix their situation. I was Person B when I bought a $2k course in 2025. Before joining, I thought there was some magical key behind the paywall. When I got in, I found that everything they shared was already on YouTube. Yes, it was spread out. So you had to connect the dots. But you could do it. If you were crafty enough. But I turned into Person A when I started my cold email journey a few months ago. I found three YouTube channels with solid info. I built a structure. I got the tools they mentioned and set up an infrastructure. I avoided the mistakes most noobs make. The only reason it worked was because I studied hard. I tested what they said and threw out what did not work. If you do this over and over, you will have no problems learning anything. But if you need permission before testing things or cannot solve problems on your own, you will fall behind.

Hey all, I made my first skill in Claude Chat and I'm ready to start learning Claude Code. Which way are you using it - in VS Code, with Claude added, or in Claude Code on the desktop? (I'm omitting the terminal option, since I'm not a coder.) And more importantly - why? What is the difference? FWIW, I'm not a coder. I learned MatLab for my PhD, but don't code regularly.

If you've ever asked yourself that question, this is for you. In the past 6 months we've gone from Make, n8n, Cursor, Codex, OpenClaw, Antigravity to Claude. That's not one tool, or even two. It's 7 tools in 6 months. Also think about how many new features Claude dropped in March alone. Or OpenClaw? So how can you keep up as a beginner when everyone is dropping new features at breakneck speed? Keep it simple and learn the basics. Understanding how HTTP works will transfer to Python when you need the requests package. What about removing duplicates? If you can remove duplicates in Make, doing it with a JS script won't be much harder. And if I were to give advice to my younger self, I would tell him to start with n8n or Make. It's visual and each node is like a container. Having AI help you with the nodes speeds up the learning. Once my younger self felt confident, I would tell him to start using Claude to code. With one condition: read over the code. Try to understand it. At times, copy it by hand to build a deeper understanding. That way, over time, he would get good at the craft. And before you ask where to go or what to watch, keep it simple. Watch any video. It does not matter. I've watched bad tutorials and still walked away with something. The idea is to immerse yourself in it. If you have zero knowledge, any knowledge will help you