Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Holy shit… someone just made DSA finally click. Not static notes Not boring pseudocode Not guessing what happens in memory Real data structures — animating step-by-step — visually. It’s called Data Structure Visualizations and it lets you watch algorithms run in real time. Here’s why this is different: Instead...

14,425 Aufrufe • vor 3 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Holy shit… someone just made machine learning click. Not static diagrams. Not math-heavy PDFs. Not black-box training. Real algorithms — training step-by-step — visually. It’s called Machine Learning Visualized and it lets you watch models learn in real time. Here’s why this is different: Instead of dumping theory first, it shows optimization happening live: • gradients moving • weights updating • decision boundaries shifting • loss decreasing • models converging You literally see learning happen. Everything is built from first principles: • Gradient Descent • Logistic Regression • Perceptron • PCA • K-Means • Neural Networks • Backpropagation No magic. Just math → code → visualization. Each chapter is a Jupyter notebook that derives the math then implements it then animates training. So you can watch: • neural nets shape decision surfaces • PCA rotate feature space • K-means clusters form live • gradient descent find minima • sigmoid reshape boundaries • backprop update weights step-by-step This solves a huge problem: Most ML resources teach: math → code → ??? → trained model This shows: math → code → learning process → result Which means you finally understand: • why gradients matter • how weights evolve • what loss landscapes look like • how convergence actually happens • why deep nets learn non-linear functions Even better: You can open any notebook modify parameters and watch behavior change instantly. Learning ML becomes interactive. Not passive. Not abstract. Not confusing. Just… visible. Perfect for: • beginners learning ML • devs moving into AI • interview prep • teaching concepts • understanding backprop • visual learners • building intuition This is the kind of resource that makes neural networks finally “click”. Link: We’re moving from: reading about ML → watching ML learn That’s a big shift. Because once you can see training, you stop memorizing… and start understanding. AI education just got visual.

Suryansh Tiwari

132,399 Aufrufe • vor 3 Monaten

Stanford professor just gave away the entire foundation of how AI Agents & automation actually works. 1-hour lecture. Tool calling. Multi-step workflows. Planning. Reflection. SAVE this to watch this before you open Netflix tonight. More valuable than 6 months of copying Make and n8n tutorials, for building Ai Agents Most people learn by copying tutorials blindly. Stanford teaches you WHY agents work the way they do. Follow Himanshu Kumar for more high-signal content that actually moves your skills forward instead of just entertaining you for 30 seconds. ↓ Why your automations keep breaking. You copied a Make tutorial. Built the exact workflow. Worked for a week. Then the API changed. The trigger failed. An edge case broke everything. You had no idea how to fix it. Because you never understood why it worked. You were copying keystrokes. The people shipping real automation were understanding architecture. ↓ What Stanford actually teaches. Tool calling: how an agent decides which tool to use by scoring each option against the current task state, not just matching keywords. ReAct loop: the agent reasons, acts, observes, then reasons again. Break this cycle and your workflow fails silently. Planning vs execution: why agents that plan all steps upfront break on dynamic inputs, and why iterative planners survive production. Memory architecture: short-term context for the current task, long-term vector memory for patterns. Most automations fail because they confuse the two. Reflection: how agents catch their own errors by evaluating outputs against original intent before moving to the next step. Tool composition: why chaining 10 tools blindly creates cascading failures, and how to structure dependencies so one broken node doesn't kill the whole workflow. This is the foundation behind every automation that actually works. Not prompting tricks. Not "10 best AI tools" reels. Actual architecture. Follow Himanshu Kumar for more high-signal content that actually moves your skills forward. ↓ Your weekend plan. Tonight: watch the Stanford lecture. 1 hour. Saturday to Sunday: build 3 projects applying what you learned. Next 2 weekends: 6 more projects. 9 projects. 2 weeks. APIs, webhooks, LLM integration, real workflows. No theory. Just build. ↓ Stanford Agentic AI lecture: free on YouTube. Watch it this weekend or buy another $500 "AI automation course" in 2027 that teaches less than this one free lecture. Bookmark. Watch tonight. Follow Himanshu Kumar for more high-signal content that actually moves your skills forward.

Himanshu Kumar

28,120 Aufrufe • vor 2 Monaten

Dear Friend, I wrote this book for you. For the past year, I have labored to create a product that will help you learn and master SQL. I have been there. I have felt the frustration of trying to learn SQL and not knowing where to begin. I have lived through the struggle of setting up a platform to run SQL queries. Most platforms require sign-ups and logins that create a headache for learners. I also know the challenge of finding proper SQL exercises that mirror the real-world experience of a data analyst. Yes, I have been in your shoes. That’s why I created SQL Essentials for Data Analysis: A 50-Day Hands-on Challenge Book (Go From Beginner to Pro). Yes, to give you a clear, practical path from beginner to confident SQL user. ✅Why SQL Still Matters You may be wondering if SQL still matters in 2025. The answer: it has never mattered more. SQL is the lingua franca of data. Data still lives in databases, and the only language it truly understands is SQL. Think about it, even in Python, SQL is there. You’ve probably heard about the powerful pandas library. Guess what? It also has some SQL. And don’t get me started on BigQuery, Tableau, Power BI, and Databricks; the answer is the same: they all rely on SQL. SQL is the big shadow that hovers over everything data. This is why learning SQL is a must for data analysts, engineers, scientists, and anyone working with data. SQL connects everything: exploration, extraction, transformation, modeling, validation, and reporting. ✅Why I Wrote This Book Dear friend, I wanted to create a resource that gives you everything you need to learn SQL for data analysis. Quite often, resources are scattered across different places. You might learn theory in one place, search for datasets in another, and hunt for questions somewhere else. More often than not, the only place you can tackle SQL challenges is online. But online platforms usually focus on syntax and don’t reflect the messiness of real-world data. I wrote this book to give you the best of both worlds: theory and practice. I don’t want you to be worrying about where to find resources. I want you to focus only on learning SQL. If you are new to SQL or need a refresher on the fundamentals, Part 1 of the book has you covered. If you are looking for practice, Part 2 is 49 days of hands-on SQL challenges designed to mirror real-world tasks. Each day in the book is designed to feel like a mini project, rather than isolated exercises. Take Day 15: Standardize Climbers Data, for example: On this day, you’re not just writing a single query; you’re working with a dataset from start to finish. By combining these tasks, you experience a full data preprocessing workflow, just like a real project. You get to practice loading, transforming, cleaning, and validating data, all in one challenge. This approach makes every day a hands-on project, not just an isolated query. You’re learning how SQL is used in real-world scenarios, not just memorizing syntax. By the end of each day, you’ve solved a problem that feels meaningful and practical: yes, something that mirrors data analysts’ and engineers’ work in real life. In this book I use SQLite. I chose SQLite because it’s simple, lightweight, and runs on any system without complicated setups or cloud accounts. You don’t need to worry about complex configurations. SQLite allows you to focus entirely on learning SQL concepts, queries, and logic without distractions. You will just have to import it. I also structured the book for use in Jupyter or Google Colab notebooks. These are playgrounds for data analysts, engineers, and scientists. These environments are interactive and flexible. They let you run queries, visualize results, and experiment in real time. Using notebooks ensures that you can practice SQL while documenting your work and learning at your own pace, all in one place. No need for sign-ups. ✅Why 50 Days? I chose 50 days intentionally. Learning SQL isn’t a sprint; it’s a habit. You can’t truly master a language by cramming a few queries in one sitting. 50 days creates a commitment. You attach yourself to a goal, a tangible outcome. Every day is a small win, a step forward, and by the end of the journey, you’ve transformed your understanding of SQL. By spreading the learning over 50 days, you build momentum, consistency, and confidence. Think of it like training for a marathon. You don’t run 26 miles on the first day. You run a little each day, gradually building strength, endurance, and skill. By the end of the 50 days, you’ll have tackled a wide range of SQL tasks: from simple filtering to window functions, date operations, joins, and performance tuning. You’ll have not just learned SQL but truly internalized it. The goal isn’t to overwhelm you. It’s to give you a structured, achievable path that fits into your daily routine, so learning SQL becomes natural, steady, and rewarding. Even if you don’t finish within 50 days, the 50-day structure gives you a rhythm, a habit, and a sense of accomplishment. The kind of outcome that sticks long after the book is finished. In summary, I wrote the book to address these pain points: 🔶Not knowing where to start: The book gives you a clear roadmap that guides you day by day. 🔶Too much theory, not enough practice: Reading about SQL is not the same as doing SQL. This book includes hands-on challenges that mirror real-world scenarios, so you’re not just memorizing commands; you’re learning to think like a data analyst. 🔶Complex setup: Many learners get stuck setting up databases or configuring environments. You will not worry about complex setups; everything runs in SQLite3 inside Jupyter Notebook, so you start immediately. 🔶Disconnected learning: The challenges mirror real-world analytics problems. Every day here is like a mini project, giving you the experience of exploring, cleaning, transforming, and analyzing data ✅What I ask of You I wrote this book for you because I want you to succeed, but books alone don’t create mastery; your effort does. I have provided the tools. All I ask is that you show up every day. Even if it’s just 20–30 minutes, take the challenge seriously. Tackle the problems, experiment with your queries, make mistakes, and fix them. That’s how real learning happens. I also ask that you trust the process. The book is designed to guide you from beginner to confident SQL user, step by step. Some days will feel "easy" and others "hard." Stay the course, and by the end, you’ll see how all the pieces fit together. Finally, I ask that you bring curiosity and persistence. SQL is a language of logic and structure, but it’s also a language of insight. The more you explore, the more patterns you’ll discover, and the more confident you’ll become in solving real-world problems. Don’t be scared to experiment. If you commit to this, I promise you’ll finish 50 days with more than just knowledge. You’ll have the skills, confidence, and habit of thinking like a data analyst. To make starting even easier, as a subscriber to this newsletter, I’m giving you an exclusive 35% launch discount. You can grab your copy today and start the 50-day journey at a reduced price. Grab SQL Essentials for Data Analysis here: I can’t wait to hear about your progress, the insights you uncover, and the confidence you gain along the way. If you have any questions, feel free to reach out to me or post them in the comments section. Let’s start this journey together: one challenge, one query, one day at a time. Warmly, Benjamin PS. Please repost.

Benjamin Bennett Alexander

16,646 Aufrufe • vor 8 Monaten

Made $530,000 with Ai Bot that started with $313. Didn't know how to code. Now this bots run 24/7 printing money while sleeping. I've made the exact step-by-step guide to build this Claude Code Polymarket trading bot. Prompts. Code. Risk settings. Paper trading checklist. Everything from zero to running bot. It's free. For 24 hours. After that I'm charging $499 for it. To grab it right now: 1. Comment "Claude Bot" 2. Like and Retweet this post 3. Follow me Himanshu Kumar ( I can't send DMs to non-followers ) I'm DMing everyone who Complete the 3 steps. I spent hundreds of thousands hiring developers because he was too scared to learn. Then learned Claude Code. Built algorithmic trading systems. $313 → $530,000. You have the same tools available right now. And you're using them to ask ChatGPT for Instagram captions. This attached video is a goldmine. Full live walkthrough. Claude Code building actual Polymarket trading bots. From zero. Every line of code. Every decision explained. Now let me break down why everything you're doing in trading is wrong and exactly how to fix it. Save this post. You'll hate yourself if you lose it. ↓ Let's start with why you keep losing money. You already know the answer. You just won't admit it. You overtrade. Every. Single. Day. You see a candle move. You feel something. You enter. No plan. No edge. No reason. Just feelings. Then it goes against you. You feel something else. Panic. Anger. Denial. You move your stop loss. Or you didn't set one at all. "It'll come back." It doesn't come back. So you take another trade. A revenge trade. Bigger size this time. Because you need to "make it back." That one fails too. Now you're emotional. Now you're tilted. Now you're using leverage you have no business touching. 40x. 50x. 100x. On a trade you entered because a candle looked "bullish" and some guy on Twitter said "send it." You get liquidated. Close the laptop. Punch something. Tell yourself you'll be "more disciplined" tomorrow. Tomorrow comes. Same cycle. Same result. Same liquidation. You've been doing this for months. Maybe years. And you still think the problem is your strategy. The problem isn't your strategy. The problem is you. Save this post right now. What I'm about to show you is the only way to remove yourself from the equation. Follow Himanshu Kumar so you don't miss any of this. ↓ Here's what's actually killing your account. It's not the market. The market doesn't care about you. It's not your indicators. RSI works fine. MACD works fine. They all "work." It's not your timeframe. It's not your broker. It's not the "manipulation." It's four things: 1. Emotions. You hold losers because hope feels better than loss. You cut winners because fear feels stronger than greed. You size up when angry. You skip trades when scared. Your emotional state determines your position size. That's insane. And you know it's insane. But you keep doing it. 2. Overtrading. You take 15 trades a day. Maybe 5 of them had actual setups. The other 10 were boredom. Boredom trades are the most expensive hobby in human history. 3. Leverage. You use 20x-50x on trades where you're not even sure about the direction. That's not trading. That's a casino with a nicer interface. 4. Fees. You're smashing market orders. Paying spread. Paying commission. On 15 trades a day. Your broker makes more money from your account than you do. Think about that. Your broker is profitable on your account. You're not. You're the product. Not the trader. These four things are why 90% of traders lose. Not bad luck. Not the market. You. Save this post and follow Himanshu Kumar because the solution is coming next. ↓ The solution is painfully obvious. Remove yourself from the equation. Not partially. Not "I'll be more disciplined." Not "I'll journal my trades." Not "I'll meditate before trading." Completely remove yourself. Build a bot. Let the bot trade. You go live your life. The bot doesn't feel emotions. The bot doesn't overtrade. The bot doesn't use reckless leverage. The bot doesn't smash market orders and bleed fees. The bot follows the rules. Every single time. Without exception. Without "just this once." Without "I have a feeling about this one." Rules in. Execution out. No human in the middle to mess everything up. That's algorithmic trading. And before your ego jumps in with "but I'm different, I have discipline" — No you don't. Your account balance proves you don't. If you had discipline, your account would be green. It's not. So you don't. Accept it. Automate it. Move on. This is the hardest truth in trading. Your discipline will always fail. A bot's won't. Save this post. Follow Himanshu Kumar for the exact bot setup that removes your emotions permanently. ↓ "But I don't know how to code." Neither did he. The guy in this video didn't know how to code for most of his life. Got held back in 7th grade. People counted him out early. Spent years building apps and SaaS businesses without writing a single line of code. Hired developers on Upwork instead. Spent hundreds of thousands of dollars paying other people to build what he could have built himself. Because he was scared to learn. That fear cost him years. And hundreds of thousands of dollars. Sound familiar? You're doing the same thing right now. Not with developers. But with your time. You're spending thousands of hours trading manually because you're scared to learn the thing that would make trading automatic. The fear of learning to code is costing you more than any bad trade ever did. Because every month you trade manually is a month of emotional decisions, overleveraged entries, and unnecessary losses that a bot would never make. And here's the thing that should really frustrate you: AI does the hard parts now. You don't need a computer science degree. You don't need to work at a hedge fund. You don't need to be "good at math." Claude Code writes the code for you. You just need to think clearly about trading ideas. That's it. If you can describe a strategy in English, Claude can build it in Python. "I don't know how to code" stopped being a valid excuse in 2024. It's 2026. You're 2 years late on that excuse. Find a new one. Or stop making excuses entirely. Save this post. Follow Himanshu Kumar because I'm showing you how people with zero coding experience are building profitable bots. ↓ The process that actually makes money. Three letters. R. B. I. Research. Backtest. Implement. That's it. That's the entire process. Every single day. Research: Find an idea. A pattern. A market inefficiency. Don't trade it yet. Don't even think about trading it yet. Just research it. Backtest: Test the idea against historical data. Does it work? Not "does it look good on one chart." Does it work across thousands of trades? Across different market conditions? Across in-sample AND out-of-sample data? If no, kill it. Find another idea. If yes, move to step 3. Implement: Build the bot. Deploy it. Paper trade first. Then live with small size. Scale only on evidence. Research. Backtest. Implement. Every day. No exceptions. You know what your current process is? Feel. Enter. Pray. F. E. P. Feel bullish. Enter a trade. Pray it works. That's not a process. That's gambling with a TradingView subscription. RBI is the only process that works. Save this post. Tattoo it on your forearm. Follow Himanshu Kumar for daily RBI breakdowns. ↓ What Claude Code actually does that your manual process can't. You can maybe test 3-5 strategy ideas per week. Manually adjusting parameters. Manually checking results. Manually writing code (badly). Claude Code tests 50-100 ideas per week. With parallel agents running simultaneously. Multiple strategies being built, tested, and validated at the same time. While you sleep. The guy in this video spends 4-8 hours a day building systems with Claude Code. Not trading. Building. Research. Backtest. Implement. Then iterate. Improve. Optimize. Every day the systems get better. Every day the edge compounds. Every day the bots get smarter. While you? You spend 4-8 hours a day staring at charts making the same mistakes you made last month. Same indicators. Same patterns. Same entries. Same losses. He's iterating forward. You're running in circles. Same 8 hours per day. Completely different outcomes. Because he's building systems. And you're feeding a casino. Stop feeding the casino. Start building the machine. Save this post and follow Himanshu Kumar for the Claude Code workflow that iterates strategies while you sleep. ↓ Jim Simons. That's the benchmark. You probably don't know who Jim Simons is. And that tells me everything about how seriously you take trading. Jim Simons. Mathematician. Founded Renaissance Technologies. Built a net worth of $31 billion. 100% from algorithmic trading. Not one single manual trade. Not one "gut feeling" entry. Not one RSI divergence. Not one "smart money concept." Algorithms. Bots. Systems. Data. $31 billion. His fund averaged 66% annual returns for over 30 years. While you're excited about making $200 on a trade that you'll give back tomorrow. The best trader in human history never placed a manual trade in his life. And you think your edge is staring at a 5-minute chart with bloodshot eyes at 2 AM? Your edge is building the system. Not being inside it. Jim Simons is the benchmark. Everything else is noise. Save this post. Follow Himanshu Kumar because I'm building toward the same goal and showing every step publicly. ↓ What you need to understand about patience. This is not get-rich-overnight. The guy in this video says it directly: "This channel is not for people looking to get rich overnight. It's not plug and play. There are no shortcuts. If you're impatient, this probably isn't for you." And that's exactly why most people will fail at this. Because you want results now. Today. This trade. You don't want to spend a week building a bot. You don't want to paper trade for 2 weeks. You don't want to test 50 ideas to find 1 that works. You want to copy someone's bot, run it live with your rent money, and be rich by Friday. That's why you'll be broke by Friday. The guy making $2.3M spent months iterating. Testing. Failing. Rebuilding. Testing again. He was patient when you would have quit. He was calm when you would have panicked. He was consistent when you would have given up. Patience isn't just a virtue in trading. It's the only virtue. Without it, everything else fails. Impatience is the most expensive personality trait in trading. Save this post. Follow Himanshu Kumar and learn to build systems with the patience that actually pays. ↓ The live streams where the real learning happens. The YouTube video is the trailer. The live streams are the movie. Real-time bot building. Real-time questions answered. Real code shown. Real mistakes made and fixed. Not polished highlight reels where everything works perfectly. Actual development. Where things break. Where strategies fail. Where code doesn't compile. Where the fix takes 2 hours. Because that's what real development looks like. And seeing the messy parts is more valuable than any polished tutorial. Because when your bot breaks at 3 AM, you need to know how to fix it. Not just how to celebrate when it works. The streams mix beginner and advanced. Start with how to automate trading. How to use AI for code generation. Then dive into the daily work. Claude Code. Parallel agents. Constant iteration. Live debugging. 4-8 hours of real algorithmic trading development. Live. Uncut. No filter. Most "trading education" shows you the wins. This shows you the work. Save this post. Follow Himanshu Kumar for the stream schedules and breakdowns. ↓ The belief that changes everything. Code is the greatest equalizer. Not money. Not connections. Not a degree. Not where you grew up. Not what school you went to. Code. Once you can build systems, you can build anything. For the rest of your life. A trading bot today. A SaaS product tomorrow. An automation business next month. A completely different life next year. The skill isn't "algorithmic trading." The skill is building systems. And that skill transfers to everything. The guy who can build a trading bot can also build a lead gen tool. Can also build a content pipeline. Can also build a SaaS product. Can also build literally anything that runs on logic and code. One skill. Infinite applications. And AI makes learning it 100x easier than it was 5 years ago. You don't need to be smart. You don't need talent. You need Claude Code and the willingness to sit down and build something instead of consuming content about building something. Building is the skill. Everything else is entertainment disguised as education. Save this post. Follow Himanshu Kumar because I'm showing you how to build, not just how to watch. ↓ If any of this applies to you, pay attention. If you've lost money from overtrading. If you've been liquidated. If you know trading is the vehicle but manual execution keeps crashing you. If you've tried "being more disciplined" and it never lasted more than a week. If you keep saying "next month I'll start automating." If you've spent more money on courses than you've made from trading. There is a better way. It's not a magic indicator. It's not a signal group. It's not a $997 mentorship from a guy who makes money teaching, not trading. It's building your own system. A system that trades without emotion. A system that follows rules without exception. A system that runs while you sleep. A system that compounds while you live your life. That's the answer. It's always been the answer. You've just been too scared to accept that the solution requires building something instead of buying something. ↓ What the next 30 days look like if you actually commit. Week 1: Watch the video. Learn Claude Code basics. Build your first simple strategy. Run your first backtest. Week 2: Iterate. Let Claude improve the strategy. Run Monte Carlo validation. Paper trade. Week 3: Go live with $50-100. Tiny positions. Watch every trade. Compare to paper results. Week 4: Scale based on evidence. Not based on excitement. Not based on one good day. Based on data. 30 days from now you either have a running bot that trades without your emotions destroying every position. Or you're exactly where you are right now. Reading another post. Making another promise. Breaking it by Tuesday. Same 30 days either way. Different actions. Different results. Different life. ↓ Full video tutorial attached. Live bot building with Claude Code. From zero to running Polymarket trading bot. Every line of code. Every decision explained. The video is free. Claude Code is available now. The market is open 24/7. The only thing standing between you and a profitable trading bot is the same thing that's been standing there for months. You. Get out of your own way. Follow Himanshu Kumar for daily AI trading bot breakdowns, live build sessions, and the full RBI process. Save this post. Watch the video. Build the bot. Or keep trading manually and keep losing. The choice has never been easier. And you've never been more stubborn about making the wrong one.

Himanshu Kumar

37,300 Aufrufe • vor 3 Monaten

This explains it all. Hillary Clinton has greatly been behind the destruction of America Hillary Clinton wrote her entire college thesis on a book that explains how to turn any country into a communist dictatorship Wait until you hear this “You want to know how we got here? I'll tell you. It's people like Hillary Clinton who've been introducing Socialist Marxist ideology to the American public for decades, and they've been pushing their agenda to turn this country into a commie nation. And if you don't believe me, tell me if any of Saul Alinsky's Rules for Radicals sound familiar based on how you're living your life right now and what this country's become. It's the exact playbook on how to convert any nation into a communist dictatorship. — It was written down step-by-step. So here's how it works. It's eight steps to take any civilization and convert it to socialist Marxist ideology that's reinforced by communism, which, by the way, Hillary Clinton wrote her entire college thesis on this particular book. — The first move is to control healthcare. You control healthcare, you control people's bodies, you control their choices, and you create dependency - The second move dovetails right off the first. They jack up poverty so people can't breathe. Keep wages low, make prices high through inflation, tax f*cking everything, and then suddenly people are desperate. That's exactly what they want because when you're desperate, you beg for anyone who promises some form of relief - Then the third step is to bury a generation in debt. $20 trillion, $30 trillion. Who's keeping score again? Nobody. That's where we're at. The math is absolutely f*cking brutal on purpose and the goal is to crash the system, and then they offer the solution. - Step four in Alinsky's plot is to take guns off the table, disarm the people, and centralize enforcement. Makes everything easier when no one can push back - The fifth step is to weaponize welfare. Food, housing, income, dependency on the state. Call it compassion if you want. I call it a leash. - Then the sixth step is to own the classrooms. Control the curriculum, control the future voters, control the narrative. Kids are taught to parrot slogans and not to ask questions, which is perfect, right? At least if you want to institute socialism and a Marxist ideology and a communist dictatorship in your own f*cking country, - Then step seven is to erase God, or at least replace faith with dependency. Because faith causes people to ask questions. Dependency forces people to submit - Then finally, the eighth step. They keep the population fighting each other. Class versus class, race versus race, left versus right. While the people are busy clawing over crumbs, they rob us blind and they take over. Look, every single one of these moves is being played out in real time right now. It's not a coincidence. Not even close. It's a pattern, and if you see the pattern, good. You're awake. Don't just watch it happen. Push back. Talk about it. Share it. Wake people up. Because the worst part of this is that they knew that a society of young, strong, level-headed, logical thinking men would never have allowed any of this to take place, and that's why they came after us first.“

Wall Street Apes

440,432 Aufrufe • vor 9 Monaten

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

192,483 Aufrufe • vor 3 Monaten

At the BNB Chain hackathon, CZ 🔶 BNB made several very important points about AI trading (Everything in parentheses is my own view and judgment.) He first said that AI will be involved in trading everywhere. Trading itself is already a huge market: there are 300 million users on Binance alone, and if you add the decentralized ecosystems, that number is not small either. In such a mass-market environment, many different trading strategies can work, with countless different coins, different projects, and different ways to play. But there is a big problem here: building commercial AI trading platforms for retail users is actually very hard. If a trading strategy works very well for one person, once a billion people start using the same strategy, that strategy “might still work, or might stop working.” Take copy trading / follow trading as an example: if you buy first and everyone follows you, the first buyer will perform very well, but the last person to follow may not end up with good results. So, with the exact same strategy and the exact same copy logic, the outcomes can be completely different for different people. (On top of that, every strategy also has its own capital capacity limits.) Teams that can really build strong AI are, with high probability, going to trade with their own money. In today’s world, money itself is already somewhat like a “commodity”; many people have a lot of capital, and it’s actually not that hard to raise funds. If you truly have an algorithm that can make a lot of money, it’s not hard to get money and run your own book. There is really only one situation where you would sell this algorithm to mass-market users: for example, if you charge a $10 monthly subscription and can sell it to one million users, then your $10 million monthly subscription revenue is higher than the profit you could make by trading the strategy yourself. (Here this touches one of our earlier theses: as training AI models becomes relatively easier and the supply of models increases, model companies have more incentive to open-source. By analogy, as the production process of trading strategies is increasingly simplified by AI and the supply of strategies explodes, traders will have stronger incentives to monetize by expanding their influence in other words, by “open-sourcing” their strategies.) Of course, CZ did not say that this model can never work. Another path is to build an AI trading platform that lets users tune different AI algorithms, or very easily assemble their own structures and strategies, so that what each person ends up running is different and better tailored to themselves. Some people will make money, some people will lose money, but the platform still has value because it’s very hard for most people to build an AI trading algorithm from scratch. So there are a lot of trade-offs here; it’s not as simple as saying “once AI shows up, everything automatically gets better.” (This is exactly what we presented at the hackathon: you describe your own strategy in natural language, and the AI automatically generates a workflow. The parameters in that workflow, the models used, the logical structure, the APIs it calls, and even the algorithms it invokes are all customizable. The reasons we think workflows are a good way to do this include: controllable execution paths, Lego-like modular nodes, and better visualization that makes it easier for users to build and adjust their workflows.) Finally, his conclusion was very clear: it’s not that AI will definitely make trading better, and it’s not that AI will definitely make things worse. Rather, no matter what, in the future a huge number of people will use AI to trade. This will be a very large field, and whoever can build the best algorithms will make a lot of money.

Tykoo

25,535 Aufrufe • vor 7 Monaten

This 6-minute video reveals how Elon Musk learns complex topics: Elon Musk: “You don’t need college for learning.” “Everything is available basically for free. You can learn anything you want for free. It is not a question of learning.” Musk starts with a blunt point: College may still have value, but not for the reason most people think. He says the real signal of college is not intelligence. It is proof that someone can work through structure: “Can somebody work hard at something, including a bunch of sort of annoying homework assignments, and still do their homework assignments, and kind of soldier through and get it done?” That, in his view, is one of the main things a degree demonstrates: Discipline. Compliance. Follow-through. Not necessarily exceptional ability. Musk pushes the idea even further: “Colleges are basically for fun and to prove you can do your chores. But they’re not for learning.” Whether or not you agree with him fully, the underlying point is hard to ignore: We live in a time when knowledge is no longer locked inside institutions. The internet has dismantled the old gatekeeping model. Today, if someone wants to learn design, engineering, writing, sales, coding, marketing, or history, they can access world-class information without ever stepping into a lecture hall. The bottleneck is no longer access to information. It is desire. Focus. Curiosity. Consistency. Musk then draws a distinction that matters: “If you’re trying to do something exceptional, there must be evidence of exceptional ability.” That line changes the whole conversation. Because in real life, people do not reward credentials alone. They reward proof. Not what you enrolled in. What you built. Not what you intended to do. What you finished. Not what you say you know. What you can demonstrate. This is why portfolios outperform claims. Why execution beats prestige. Why visible work creates leverage. Musk even says, somewhat provocatively: “I don’t consider going to college evidence of exceptional ability.” And then he points to the kinds of examples people love to cite: “Gates is a pretty smart guy, he dropped out. John was pretty smart, he dropped out. Larry Ellison, smart guy, he dropped out.” His broader message is not that everyone should leave school. It is that conventional paths are not the only paths to intelligence, capability, or impact. Then Musk moves into something even more useful: His view of how people actually learn. “Education should be as close to a video game as possible. Like a good video game. You do not need to tell your kid to play video games. They will play video games on autopilot all day.” That comparison is simple, but powerful. Why do people obsess over games? Because games are interactive. They are immersive. They provide immediate feedback. They make progress visible. They create challenge without making the challenge feel meaningless. Musk’s point is that learning should work the same way. “If you can make it interactive and engaging, then you can make education far more compelling and far easier to do.” This is where traditional education often breaks down. Students are expected to move in lockstep. Same pace. Same timeline. Same structure. Same sequence. Musk rejects that model completely: “People are not objects on an assembly line.” That may be one of the clearest criticisms in the entire transcript. Because standard education often optimizes for administration, not human variation. It is easier to manage people in batches. But easier to manage does not mean better to learn. Some people move faster in math. Some are stronger in language. Some are highly visual. Some need to touch the thing, build the thing, test the thing. And yet most systems still treat learning like synchronized marching. Musk argues for something more individualized: “Allow people to progress at the fastest pace that they can or are interested in in each subject.” That idea matters beyond school. Adults learn this way too. No one becomes exceptional by waiting for permission to move at average speed. The most effective learners usually follow interest with intensity. They go deeper where curiosity pulls them. They accelerate where energy is highest. They build momentum through engagement, not force. Musk also shares one of the most practical ideas in the transcript: “Teach problem solving, or teach to the problem, not to the tools.” Then he gives an example. If you wanted to teach someone how engines work, the traditional system might start with separate lessons on screwdrivers, wrenches, and tools. Musk thinks that is backwards. A better method is: “Here’s the engine. Now let’s take it apart.” Then the tools become relevant in context. Now the student understands *why* the screwdriver matters. Now the wrench has meaning. Now the lesson is connected to reality. This is a much bigger principle than education. People learn faster when relevance is obvious. Abstract instruction is forgettable. Applied learning sticks. When people can see the problem first, they care about the tool. That is true in business too. You do not start with theory for theory’s sake. You start with the problem that needs solving. Then you learn exactly what is required to solve it. Finally, Musk says something that quietly explains why so much education fails: “A lot of things people learn, probably there’s no point in learning them because they never use them in the future.” That may sound harsh, but most people know the feeling. They do not resist learning because they are lazy. They resist learning because it feels disconnected. They are told to memorize before they understand relevance. They are told to sit still before they become curious. They are told to absorb information before they have any reason to care. Musk’s view, underneath the provocation, is actually simple: People learn best when learning is alive. When it is tied to action. When it respects differences in pace and aptitude. When it feels engaging instead of ceremonial. When it produces visible competence, not just paper credentials. The internet made learning abundant. What matters now is whether someone can turn information into evidence. That is the real separator. Lessons I'm taking away from this clip: 1. In today’s world, access to knowledge is cheap. Proof of skill is expensive. We have crossed a point where information alone is no longer impressive because everyone has access to it. You can watch the best interviews, read the best essays, take the best online lessons, and still remain average if you never turn any of it into real work. So the advantage now is not “I know this.” The advantage is “I built this, tested this, shipped this, and can show the result.” From my perspective, this is especially true in business and personal branding. The market rewards visible competence far more than silent knowledge. 2. People learn faster when the learning feels useful, alive, and connected to a real problem. This is why so many people struggle with conventional education but thrive when they start building something for themselves. Urgency creates focus. Relevance creates retention. Once the lesson is attached to a real outcome, the brain pays attention differently. That’s why I think one of the best ways to learn anything is to start a project that forces you to use the skill in public or in real life. Learning becomes sharper when there is something at stake. It stops being passive consumption and becomes active problem-solving. 3. The smartest people are often not the ones collecting credentials. They are the ones following curiosity with discipline. Exceptional people usually do not just learn what is assigned to them. They go where their interest is strongest and then they pursue it seriously. That combination matters: curiosity without discipline goes nowhere, and discipline without curiosity becomes lifeless. The sweet spot is when someone becomes obsessed enough to keep going deeper than required. To me, that is where the real edge comes from. Not from following the default path better than everyone else, but from developing uncommon depth in something that genuinely pulls you.

Yasmine Khosrowshahi

34,166 Aufrufe • vor 2 Monaten

Moneytaur study blueprint 🗺️ The process I used to go from not knowing what an order block is to pulling cash from the crypto markets in under 6 months using 🎯 Master concepts. Proof of performance, past 120 days👇 Start date: 09/03/2025 Requirements: - A PC/laptop - Wifi - A basic understanding of trading. ( What candlesticks are, how to actually place trades , etc ) - A free mind - Time or the ability to free up time. Starting: - Structure and routine - Stick to that routine + Pre mortem plan. - Notion / Obsidian setup. The first thing you need to create is a clear routine moulded around how you intend to approach this very large and complex task. This will not be linear and you will naturally adapt it as you progress but especially in the beginning some resemblance of structure each day is vital. This is an individual process but it is important to understand from the beginning that this will require a majority of your free time assuming you work a full time Job or study as a student. For me in the beginning this looked like: - Wake up at 6:30. - Shower - Study/work for 1h 45m before leaving for work. - 09:00 -> 17:00 work - 17:30 Exercise / Train - Eat - 19:00 resume study/work - 22:30 Start to wind down and get ready to sleep. It changed several times over the months and especially now I am full time but this is irrelevant, the only thing that matters is sticking with what you choose. Whatever your own routine may look like, it is important to understand it will inevitably require sacrifice. --- The next thing once you have established a draft framework of your routine is ensuring you will actually stick to that routine. Something I implemented which I found particularly beneficial was the concept of a Pre-Mortem plan. This involves creating several scenarios of a future in which you have failed and working backwards from each of these to find where it went wrong. Here is a video which explains it fully: When I did this I came up with 3 scenarios as well as prevention and cure for each. In the 6 months that followed each scenario presented at some point but I was able to catch them early due to having done this. The last thing is to not over complicate this, don't hyper focus on systems and loose momentum optimizing each detail. Just ensure you do the fucking work. I was a little guilty of the above at times, trying to craft the perfect routine. In reality the person who just gets up, drinks too much coffee and works his ass off out performs the workflow perfectionist who visualizes and repeats affirmations, any day of the week. --- Next you need somewhere to store your notes, journal your trades and build your knowledge. For me this was Obsidian but I have also used Notion before and it is an equally viable option. Whichever one of these you choose be warned you will inevitably want to bang your head against a wall trying to use them for the first few days, but they will both click pretty quick and are 100% better options the word document or paper alternative. Here is my full obsidian setup tutorial: Here is a link to MisterPA 's notion Journal: Here is how I create "Meta-Notes" using obsidian: The process: - How I did it. - How I would do it if doing it again. Now I did things the "hard way" and manually worked my way back through each of MT's tweets starting in 2021, reading every one and logging those that I felt where relevant. You can see in my first post: the very first system I used to do this. I quickly adapted though after about a week and focused less on just logging each relevant tweet but trying to find and focusing on those which contained the most information. There where a lot of charts I looked at then skipped over because especially at the start of his timeline they contained little useful information and my time was better spent finding those where there was something to decode. Now this does not mean skip out on "work" just use your time efficiently. -- If however if I was to start from the beginning again with the goal of levelling up technical understanding as quickly as possible I would take a different approach. To start with I would familiarise myself with all relevant SMC concepts, I have linked the best free recourses for this below 👇 CryptoChase beginner friendly index: Barncore's "The Moneytaur Way" series: Gian Luca's Trading bootcamp playlist: Following this I would then work through all of Taur's subscription posts working backwards, recreating his charts and taking notes on his logic. The subscription feed has the highest value density and least noise. Video example of my notes from his subscription posts 👇: --- Okay so now once you have a basic understanding of concepts and can re-recreate them on charts of your own it is time to put this in to practice. The next step is vigorous backtesting, you can use the trading view tool but I think trade Zella offers a more use friendly option if you pay for the subscription. Especially as it allows you to change timeframes without skipping ahead to candle close time of the timeframe you change too ( like Trading view does ) *my only note would be that their LTF/Micro TF data feed with be different to brokerage charts you will use on Trading view, to start with though you should not be going low enough that this is an issue. When you backtest in this context, treat it like real trading. That means journal and logging like you would if real cash was on the line. Take time, do not rush and focus on quality. Stick to BTC, ETH, Major FX pairs or indices as these assets are less reliant on confluence, backtesting a shitcoin is near useless as whether levels work or not will be highly dependent on Majors PA. Go on HTF, scroll back a couple years and try not too look at chart while doing so and then begin. Start with HTF analysis and work down to 2H or wherever you feel comfortable, chart it fully and then identify setups. Make rough notes / plans and then press play, execute the setups as they hit, log and journal trade management as well as observations and key notes. It is very important to not cheat when you do this, do not skip back and adjust your stoploss because it hit by 0.1%, do not skip back and adjust plan because you missed a block and your TP got frontrun. Instead these are the things you journal, embrace these mistakes because they are the cheapest mistakes you are going to make. Grind this, do it for hours, put some music on and enjoy. To start with focus on HTF's, as you get better and start netting $ on paper you can drop the timeframes and increase the difficulty. HTF = Normal, MTF = Medium, LTF = Hard. Even if you do not intend to day trade, learning how to read the lower TF's that force you to think faster, harder and prepare you for lower win rates / loss streaks can greatly improve your ability on higher TF's. While you are doing this as you start to have concepts click you now want to build up your real trading experience, take a sum of money that you care about but will be okay loosing and dedicate this to live trading. Start taking real trades and expect net losses in the beginning. This is where you will make you 2nd cheapest mistakes. This is also where you can begin to learn about your psychology. You may encounter some elements already in backtesting but the real market is where true colours really start to show. Mental issues are inevitable and part of the game, get used to them and start working to identify and fix them. Reading and applying books like Trading in the Zone and Mental Game of Trading are important and will help a lot but there is no easy fix, for some stuff you I believe you just have to get used to it and it goes away with experience. Losses suck at the beginning but after you loose 100 times you starting getting pretty numb to it, same goes for the winners. To accelerate the learning process, build connections and get advice there is also always the option of private groups, while I never personally chose this route and committed to learning everything through my own endeavours there is no denying that having nearly all the information you need structured and compiled in one place is valuable and can save time. Beyond this having access to real time thoughts and opinions of profitable traders can accelerate performance, however it carries the risk of being a double edged sword if not used properly, if relying on it like a crutch and using it as a substitute for real work you will not succeed. With that said if you take it for what it is, a learning opportunity then I believe it can be very beneficial. I am not a member of, nor affiliated with any paid group. There are now many options available within the community, all run by different people with different styles, tailored to different needs. If I was to make a recommendation though, as a non-member, it would be Albert & Co's 618'ers simply due to the diversity in styles of the traders running it and results I have seen from members I know personally. It is important that as you start to trade with real capital you reduce noise in your social feeds or eliminate it all together. You do not need 5 different opinions, you also do not need 2 people telling you the same thing in their own way so you feel re-assured. What you do need is to develop your independent thinking as a trader and be comfortable making different decisions to others, even traders ahead of yourself if it fits with your system or understanding of market. Taur here is perhaps an exception as this is who you are learning from but down the line a real test of your own ability and independence will be being able to stick with your own plan even when it differs from his. Don't get me wrong, counter trading him is retarded but you must learn to adapt his gift to your own style. This will make sense at some point. The next stage is taking your understanding of specific concepts to higher level as you simultaneously snowball experience. Look back through your journal and review where you lost money and made money, do not over extrapolate from a small sample but start to take notes and observe if trends in performance emerge. This is the beginning of the transition to self reliance, you now understand the strategy but must learn for yourself when and where it works. Here you can also learn more nuanced secondary concepts such as VSA, orderflow etc and add these to your game where appropriate. Do NOT get lost in the sauce though and remember mastery of basics is key. IMO a big focus should be understanding correlation thoroughly but especially on HTF's this is the most important thing and what triggers the majority of large swings where most of your cash will be made and losses recovered. Some people will disagree with me here but IMO you should also not be *focusing* on Odd TF's. These are secondary at best and most people overweight their significance leading to avoidable losses while wondering why price did not care about their 327minute Breaker Block which they think is the key to the market. Study Taurs feed and take note of how he mostly uses: 3M, 1M, 3W, 2W, 1W, 5D, 4D, 3D, 2D, 1D, 12H, 8H, 6H, 4H, 2H, 1H, 30m, 15m + micro time frames. The only thing left is time and repetition, you must show up each day and really do this, for months. Maybe you start to see result's, you catch your first key swing and where able to trade where others froze. Congratulations. Learn from these winners and repeat the actions. Find what assets work best for you, find your style, refine and grow. --- The last thing I will include is a short list of tools or links that can be helpful. - Trading view tutorial: - Dictionary: - Market news Calendar: --- Thank you too all those who have read this, I hope this has been helpful for the beginners who want to start but are just not sure how. 🫶 Don't just bookmark this and move on, start 🙃

Ace

44,749 Aufrufe • vor 8 Monaten

The most interesting part for me is where Andrej Karpathy describes why LLMs aren't able to learn like humans. As you would expect, he comes up with a wonderfully evocative phrase to describe RL: “sucking supervision bits through a straw.” A single end reward gets broadcast across every token in a successful trajectory, upweighting even wrong or irrelevant turns that lead to the right answer. > “Humans don't use reinforcement learning, as I've said before. I think they do something different. Reinforcement learning is a lot worse than the average person thinks. Reinforcement learning is terrible. It just so happens that everything that we had before is much worse.” So what do humans do instead? > “The book I’m reading is a set of prompts for me to do synthetic data generation. It's by manipulating that information that you actually gain that knowledge. We have no equivalent of that with LLMs; they don't really do that.” > “I'd love to see during pretraining some kind of a stage where the model thinks through the material and tries to reconcile it with what it already knows. There's no equivalent of any of this. This is all research.” Why can’t we just add this training to LLMs today? > “There are very subtle, hard to understand reasons why it's not trivial. If I just give synthetic generation of the model thinking about a book, you look at it and you're like, 'This looks great. Why can't I train on it?' You could try, but the model will actually get much worse if you continue trying.” > “Say we have a chapter of a book and I ask an LLM to think about it. It will give you something that looks very reasonable. But if I ask it 10 times, you'll notice that all of them are the same.” > “You're not getting the richness and the diversity and the entropy from these models as you would get from humans. How do you get synthetic data generation to work despite the collapse and while maintaining the entropy? It is a research problem.” How do humans get around model collapse? > “These analogies are surprisingly good. Humans collapse during the course of their lives. Children haven't overfit yet. They will say stuff that will shock you. Because they're not yet collapsed. But we [adults] are collapsed. We end up revisiting the same thoughts, we end up saying more and more of the same stuff, the learning rates go down, the collapse continues to get worse, and then everything deteriorates.” In fact, there’s an interesting paper arguing that dreaming evolved to assist generalization, and resist overfitting to daily learning - look up The Overfitted Brain by Erik Hoel. I asked Karpathy: Isn’t it interesting that humans learn best at a part of their lives (childhood) whose actual details they completely forget, adults still learn really well but have terrible memory about the particulars of the things they read or watch, and LLMs can memorize arbitrary details about text that no human could but are currently pretty bad at generalization? > “[Fallible human memory] is a feature, not a bug, because it forces you to only learn the generalizable components. LLMs are distracted by all the memory that they have of the pre-trained documents. That's why when I talk about the cognitive core, I actually want to remove the memory. I'd love to have them have less memory so that they have to look things up and they only maintain the algorithms for thought, and the idea of an experiment, and all this cognitive glue for acting.”

Dwarkesh Patel

1,051,061 Aufrufe • vor 9 Monaten

Real estate has a simple problem that people don’t always say out loud: it’s not designed for partial participation. You either have enough money to buy in properly, or you don’t. There’s usually no “in-between.” And once you do invest, your money is tied up for a long time. Selling isn’t instant and flexibility is limited. So even though real estate is seen as a solid way to build wealth, a lot of people are effectively locked out... not by lack of interest but by how the system is structured. That’s the gap APARTCHAIN is focused on. APARTCHAIN is a platform that turns real estate into something you can invest in fractionally. Instead of buying an entire property, the ownership is divided into digital shares (tokens), and investors can buy a portion that fits their budget. So rather than needing large capital, you’re able to take smaller positions in actual properties. Here’s how it works in practice: • APARTCHAIN acquires real estate • The property is split into multiple ownership shares • Investors buy those shares on-chain • Rental income from the property is distributed to shareholders • When the property is eventually sold, any profit is also shared So your return comes from two places: ongoing rental income and potential appreciation when the property is sold. Now, fractional real estate isn’t a brand-new idea. What makes APARTCHAIN different is how it’s positioned. It operates within Kazakhstan’s regulatory framework, with oversight connected to the country’s national financial authority. That’s a key detail because a lot of tokenization platforms operate without clear local regulation. Here, the structure is built to align with an existing legal system, not bypass it. On the technical side, it runs on a blockchain network designed for low fees and fast transactions. That means buying, holding or transferring your share doesn’t come with the heavy costs or delays typically associated with traditional property processes. There’s also no strict lock-in at the protocol level... you’re not forced to hold your position for a fixed period. But in reality, your ability to exit depends on the secondary market, which is still developing. So liquidity exists, but it’s not fully mature yet. It’s also worth being clear about the risks. Property values can go up or down. Rental income isn’t guaranteed and because this system relies on smart contracts, there’s a technical layer that traditional real estate doesn’t have. On top of that, the platform itself is still growing. Property inventory is limited for now and the resale market for shares is still building. That said, it’s not just an idea on paper... APARTCHAIN has already completed at least one full investment cycle... acquiring a property, generating returns, and exiting. That matters because it shows the model can actually function beyond theory. So at the core, this isn’t really about “changing real estate” in some dramatic way. It’s about removing the all-or-nothing barrier that’s always surrounded it. And that leaves a simple question: if you could start building exposure to real estate without needing to go all in from day one, would more people actually step in earlier or would they still wait until it feels “big enough” to matter? Superteam Kazakhstan || APARTCHAIN

Jessica♡🛡

105,393 Aufrufe • vor 2 Monaten

🙌Meet Artifig: A Figma Plugin to Generate Figma Plugins Do you use Figma and ever feel like this: - Your mind is bursting with plugin ideas, but you can't bring them to life because you don't know how to code? - You want to focus on design, but repetitive tasks keep slowing you down? - You dream of creating custom tools for your team, but lack the time or resources? I’ve been there too. That’s why I created Artifig. ✨ What is Artifig? Artifig is an AI-powered Figma plugin that empowers anyone to build their own Figma plugins using just natural language. No coding needed—simply describe what you want, and watch as your idea transforms into a fully functional, real-time plugin. 🚀 Redefining Figma Plugin Development The core philosophy of Artifig is simple: Designers often have countless ideas and creative visions, but many of them remain unrealized due to a lack of technical skills. We believe designers shouldn’t be limited by their inability to code. You should focus on creating, not be held back by technical barriers or repetitive tasks. Artifig takes you directly from "description" to "implementation." 🛠️ How Does It Work? 1. Describe Your Needs: Tell Artifig what you want, like “Create a skew transformation tool for objects, supporting horizontal and vertical skew with real-time preview functionality.” 2. Generate and Run the Plugin: Artifig instantly generates the plugin and runs it right within Figma. For example, the generated plugin can apply skew transformations to objects, precisely controlled via matrix transformations, with an intuitive user experience. 3. Optimize and Iteration: Need adjustments? Simply describe them, and Artifig will Iterating the plugin step by step. 4. Share Your Creations: Publish your plugins to the Artifig community, or remix plugins shared by others to build on their ideas. No learning curve. No complex steps. It’s as simple as that. 🌟 Key Features - Zero Barrier to Entry: No coding experience needed—any Figma user can create plugins effortlessly. - Multilingual Support: Works in multiple languages, including English, Chinese, French, Japanese, and German. - What-You-See-Is-What-You-Get: Generated plugins run in real-time, so you can quickly validate and refine your ideas. - Open and Flexible: The generated plugin code is 100% yours—modify it, distribute it, even use it commercially. - Global Community: Share your plugins, explore others’ creations, and publish your plugins to the Figma community. 🎯 Why is Artifig a Game-Changer? 1. No More Repetitive Work Let AI handle the tedious, time-consuming tasks: batch renaming layers, auto-aligning elements, or applying styles in bulk. All you need to do is say, “Import a PDF and arrange each image on the canvas with 20px spacing.” 2. Quickly Bring Ideas to Life From color contrast checks to data imports and custom components, all your “what if we could” ideas can now become plugins. Just one natural language description, and Artifig makes it happen. 3. Custom Tools for Your Team Build tailored tools for your team, creating unique solutions to streamline your workflow. 4. Not Just a Tool, But a Learning Experience Artifig explains the logic behind the code it generates, helping you understand Figma APIs and JavaScript. Today, you’re a designer; tomorrow, you could also be a design engineer. 🧑‍🚀👩🏻‍💻🥷🏻 Who is Artifig For? - Beginners: No development experience needed—just describe your ideas and let Artifig do the rest. - Experts: Save time and focus on high-value tasks while Artifig handles the repetitive work. - Learners: Use Artifig as a bridge to deepen your understanding of development. - Teams: Build custom tools to enhance collaboration and efficiency. 🎉 Ready to Get Started? I believe designers’ time and focus should be spent on creating, not on wrestling with complex tools. Artifig is the first step toward realizing this vision. Try Artifig now and experience an unprecedented flow of creativity!

yancymin

21,222 Aufrufe • vor 1 Jahr

I found God on 300mg of DMT at DreamMind. . . At the core of a human being is a divine spark of light. Some call it their spirit or their soul. That divine spark of light drives our physical human bodies. Our physical bodies operate on the 3rd dimensional plane, but our souls operate on a higher plane. Breathe work, meditation, sound, etc. allow humans to disconnect from their physical bodies and operate on this “soul level” of reality. You know that feeling when you’re thinking of someone and they call you? That is your soul operating on a higher plane. You know the feeling when you’re day dreaming and visualize a different time in a different place? Or that feeling when you’re in a dream and you just know it’s real? It’s because it is real, in a different time and place, on a higher plane of reality where 3rd dimensional rules don’t apply. Psychedelics like DMT (ayahuasca), Psilocybin (mushrooms), mescaline (peyote), etc give us the ability to interact with these higher realms. You could say they “thin the veil” between levels of reality. Native people have been using meditation, breath, sound, and psychedelics for tens of thousands of years. Modern businessmen like Steve Jobs have credited meditation and psychedelics as one of the most impactful experiences of their lives. Why? Because it allows them to connect, or “tune in” with the spirit realm/higher dimension/whatever you want to call it. Think of it like a video game…once you tap in to this higher consciousness level, you gain access to knowledge, understanding, etc. It’s a level up so to speak. BUT… It’s not that easy. If you have negative things you have buried deep, they will be exposed if you want to ascend. You will be forced to be the most honest with yourself that you have ever been. Some aren’t ready for that in this modern society we live in. But others are ready. You will be forced to face the feeling of dying. For some it takes traumatic life experiences to understand that feeling. For others it could take eating mushrooms with your buddies in the backyard. Sounds scary, but there are some positives to experiencing the feeling of death. You realize that death of your physical body is just a transition of your soul from the 3rd dimensional plane of existence to a higher realm. Once you realize that your soul never dies, you lose that “fear of death” so to speak. Going into this 300mg extended state DMTx journey, I already knew what death felt like, and made peace with that before going in. I’ve learned there is knowledge found on the edge of death that only comes to those who have felt it. I’ve learned that speaking an intention can help unlock things you want to figure out as well. My intention going in was to bring back knowledge to help humanity “wake up” so to speak. Now that you have a baseline understanding, let me tell you what happened. This is how I would describe it. “I felt the weight of humanity resting on my heart, like it is my job to carry the torch for all of mankind. And that feeling was one of pure love, gratitude, and understanding of the gravity of what that meant. But I realized that feeling isn’t just in me, that feeling is inside all of us, waiting to be unlocked. That pure fire of all knowing belief that no matter what evil and darkness throws at us, NOTHING can extinguish the flame, it’s NOT possible. That understanding, if felt by all, could free a people from the chains of slavery they don’t even know exist. That flame is the divine spark of existence that is humanity. That divine spark is GOD.” You see…it took me traveling to the edge of death to understand that good ALWAYS defeats evil. The flame of life cannot be extinguished. It’s impossible. They call that faith. Your divine soul never dies. Once you realize it, you have a duty to tell others. All it takes is one person. One thought. One step. And the world is changed forever. That’s how easy love conquers fear. That’s how fast good defeats evil. Imagine an army of humans they are truly awake. Truly aware to the scam that we call this modern society. They would move mountains and part seas. They would see that we are just ONE STEP away. One step away from transcending the fear. One step from overcoming the negativity. One step from freedom. You have that power inside you, waiting to be unlocked. You are God expressing himself in human form. You have an eternal flame burning inside you. A divine spark that CANNOT be extinguished. The power to overcome any and all. That power is the divine spark of existence. That power is GOD. You are a super natural being… Wake up and start acting like it.

Nathan Hughes

58,877 Aufrufe • vor 5 Monaten

Most $TAO holders staking right now are trusting the wrong validators. Not because they are careless. Because nobody explained what the numbers on the Validators page actually mean. There is a tool inside Taostats that shows you exactly which validators are genuinely working and which ones are collecting your emissions without contributing anything to the network. It is free. It is live. And almost nobody is using it correctly. Here is exactly how to read it. Step 1: Understand what Dominance actually measures. Dominance is not popularity. It is not a ranking of which validator is best. It describes a validator's Stake Weight as a percentage of all validator stake weights combined across the network. Stake Weight is calculated as: root stake multiplied by 0.18, plus all alpha staked across subnets converted into TAO. Root stake is deliberately discounted at 18 percent of its face value. Alpha stake carries the full weight. This means a validator with deep subnet-level staking is structurally more powerful than one sitting purely on root, even if their raw TAO numbers look similar on the surface. When you see a validator with rising Dominance over time, it is not just getting more popular. It is getting more alpha stake directed toward it across active subnets. That is a meaningful signal about where serious capital is moving inside the network. Step 2: Check the Take percentage before you delegate anything. Take is the percentage of emissions the validator keeps for itself. Everything above that number flows to you as a nominator. A validator with a 18 percent Take keeps 18 percent of the emissions their position generates and distributes the remainder to stakeholders. A validator with a 50 percent Take is keeping half of what your stake earns. Most people never look at this number before delegating. It is the first number you should check. A high Take is not automatically a red flag if the validator is genuinely performing well and contributing to the network. But a high Take combined with low VTrust in their subnet performance page is the exact combination that should make you move your stake immediately. Step 3: Open the Validator Performance page and find the VTrust score. This is the number most holders never see. VTrust measures how closely a validator's weight assignments align with the honest stake-weighted majority across the network inside each subnet they operate in. Validators are responsible for evaluating miner output and assigning scores. Those scores go into Yuma Consensus and determine which miners earn emissions. A validator doing genuine evaluation work will have weights that align closely with the honest consensus. High VTrust. Consistent emissions. Reliable nominator returns. A validator that is weight copying, meaning they are simply copying the Yuma consensus scores back onto themselves rather than doing real evaluation, will show a flagged return on Taostats. Their nom/24hr/1k TAO score appears in red. This is Taostats telling you directly: this validator is extracting value from the network without contributing to it. When you stake to a weight copying validator, you are funding a free rider. Step 4: Watch the 24hr Nominator Change column. This number moves fast and it tells you something before any other signal does. A validator losing nominators over consecutive days is a validator that informed stakers are quietly leaving. A validator gaining nominators rapidly while their VTrust is healthy is a validator attracting attention for the right reasons. The 24hr column is the on-chain version of sentiment before sentiment becomes a narrative on social media. Step 5: Check Active subnets alongside Total Weight. Active tells you the number of subnets where the validator has a parent or child hotkey running. A validator with high Total Weight but low Active subnets is concentrated. They are running a specific strategy in specific markets. A validator with broad Active coverage across many subnets is building a wider surface area for emissions and is more exposed to the overall network performance rather than any single subnet cycle. Neither is inherently better. But knowing which type of validator you are delegating to tells you what you are actually betting on when you stake. Step 6: Check the Weight Change column over time. Total Weight is a snapshot. Weight Change is momentum. A validator with stable or growing Total Weight over consecutive days is attracting net new stake consistently. A validator with declining Weight Change is losing stake faster than it is gaining it. Most people look at the current number. The people positioning correctly are watching which direction the number is moving and how fast. The difference between a good validator and a dangerous one is not obvious from the outside. It is not the name. It is not the size. It is the VTrust score, the Take percentage, the nominator trend, and whether Taostats is showing their return in red or not. Every one of those signals is sitting on the Validators page right now. Free. Live. Updated every block. The investors who read the data layer before the narrative layer will not need to explain their staking decisions later. Open Taostats tonight. You will want to find this post when you do.

2xnmore

11,771 Aufrufe • vor 29 Tagen

Just in $AMD Anush "Speed is the moat"|ROCm🎙️ In the race to define the future of AI, what's the one advantage that truly lasts? It's not proprietary tech, argues Anush Elangovan Elangovan, VP of AI Software at AMD , but the sustainable speed of innovation. He explains why AMD is rejecting the "walled garden" model for its open source ROCm stack, betting that an open community flywheel is the key to victory. Listen to understand how this open strategy is designed to out-innovate closed systems by empowering developers to solve everything from frontier-model challenges to the mundane, everyday problems that define the "last mile" of AI. AMD ROCm Software: Part 1 Transcript [00:00:00] Andrew Zigler: Joining me is Anush Elangovan, VP of AI software at AMD. And when people talk about AI compute, the conversation often stops at hardware specs, but it's more than just physical chips that win the game. It's also the software ecosystems supporting them. [00:00:18] Andrew Zigler: The prevailing strategy in the industry has been to build something like a walled garden. You know, something closed, proprietary locks, developers in. But AMD is betting on an entirely different play, open source acceleration, and with rock, their open source AI software stack. AMD is building not just hardware parity, but an innovation flywheel that's powered by the community with interoperability and the freedom to scale without all of that pesky lockin. [00:00:48] Andrew Zigler: And in this world, speed is your moat and how fast you can innovate while your platform remains open, flexible, and standardize across all of its applications. That's what we're gonna explore [00:01:00] today. So Anush, I'm really excited to have you here. Welcome to Dev Interrupted. [00:01:04] Anush Elangovan: Thanks for having me. Uh, super excited to chat about it. [00:01:07] Andrew Zigler: Amazing. Well, let's go ahead and dive right in with kind of what I laid it out with in the beginning, the idea of the moat and it being about speed. I wanna unpack that a bit because that came from you when you and I first spoke. And I, and I want to know, you know, how do you define speed inside of AMD beyond just things like hardware, benchmarks. [00:01:27] Anush Elangovan: Yeah, that's a very good question. So when we typically talk about speed, everyone's like, Hey, hardware benchmark specs, right? Like, uh, memory bandwidth or, or flops. And that is one important part of it, uh, AMD does very well. With that, we do have, a, a very good history of executing on that axis. [00:01:47] Anush Elangovan: But when I say speed is the moat, it is about, uh, how we prepare, how we build the muscle to run the race for a long time and run it fast. And it is [00:02:00] not about a single point in time that you've, you've beat some you know, benchmark and, and you declare victory. It's about building the ability to consistently develop and deliver. [00:02:13] Anush Elangovan: Both hardware and software innovation at scale and do it fast, right? Like, you know, we we're increasingly getting to a point where models come out and they're, uh, you know, a year or two ago it was like, Hey, they work on AMD on day zero, which is great, but now they are performing on AMD the day it releases, right? [00:02:32] Anush Elangovan: So, what does it take to Prefetch where the industry is going? Be prepared to intercept. At that point is what you know, I, I refer to as you know, the, the speed factor in, in creating this mode, right? And the mode is just shed all things that hold you back and run as fast as you can. [00:02:53] Anush Elangovan: Uh, because the pace of innovation that is, uh, being seen in, in AI [00:03:00] industries is just. Amazing. Right? And it's like, it's transformational at at how you generate electricity. It's transformational as at how you build data centers. It's transformational at how you deploy compute, networking. It's transformational at what kind of use cases you, you know, uh, use AI for. [00:03:17] Anush Elangovan: Uh, and for that, you need to be prepared to, see what comes tomorrow and be prepared to run the race tomorrow. [00:03:23] Andrew Zigler: Yeah, it's a really great perspective because it highlights that it's not just like a checkpoint that you run through. I like how you called out, like it's not just hitting that benchmark or being the best in class at that moment, in that snapshot, it's about having a. The throughput and about having that dedication to the idea and continuing to deliver on it. [00:03:43] Andrew Zigler: It's not just crossing the threshold, but it's also being the engine. And that's what, that's what protects a business. That is the moat, because the moat is that innovation layer, the faster and more, uh, future forward. That you can work and think, [00:04:00] you know, the better. Uh, we, we talk a lot about like future forward work styles. [00:04:04] Andrew Zigler: Like what are the things I could be doing right now today that are gonna be like, way more useful tomorrow? Let, let's abandon those, workflows that are older and that kind of like, that translates into. An advantage when you work that way. You know, what kind of things have you learned working with, uh, like across all spectrums of people who would use ROCm, right? [00:04:23] Andrew Zigler: You have like the developers, but then you also have the enterprises and you have this large span of adoptees, right? So what is the, what does that look like that you learn? [00:04:32] Anush Elangovan: Yeah, so, so the way I look at it is there are gonna be pockets of different, uh, you know, cadences, right? Like, so people who are deploying in enterprises, for example, right? The validation and how long it takes for them to deploy an LLM that's secure. It's, with guardrails, et cetera, maybe longer. [00:04:52] Anush Elangovan: but you still have to go through the process and you have to be prepared to like, walk that walk to deploy an enterprises. That doesn't mean it's [00:05:00] not fast, that's as fast as you can do for that industry, right? And if you are deploying AI in healthcare, right, it's, it's got its own, uh, cycle. [00:05:07] Anush Elangovan: but in each one of these, you want to see how, like, go down to the essence of what is it that you actually have to do. And, you know, I, I, I like how you framed it. It's like it's, you shed your prior assumptions of how things are done, right. And, and you kind of build up from a, uh, first principles, uh, approach to say, this is how I could use AI to unlock, whatever I'm doing. [00:05:33] Anush Elangovan: And, and, some of it, you know, it's good to really step back and look at. Just question every part of it, right? Like right now you're getting chat GPT and, Gemini competing for like, math, olympiads and, and, uh, college, uh, reasoning, uh, tests. Right? And, and those are like that, that is amazing and increasingly like complex tasks that they're trying to do. [00:05:58] Anush Elangovan: But there may also be like. [00:06:00] More mundane things that AI could, could get applied to. Right? And, and so when we think about shedding old ways, you wanna shed it not just in like the tip of the spear. It's like, you know, I'm gonna see what's the frontier model. It's also, it could be something as simple as. [00:06:18] Anush Elangovan: How do you choose a, a movie, uh, you know, like a recommendation system, right? Or, or, uh, an automated, uh, flight, uh, rebooking system. So the moment, you know, your flight is late, uh, right now it's a notification, right? It's like, oh, you got a text message saying your flight's late. And I got that like three times this week. [00:06:38] Anush Elangovan: But anyway, uh, and, and, and, and, I was just like, okay, so if I were to rethink this. All this MCPs that we have that should be hooked up into an MCP that says, your flight's delayed. Here are your options. If you want, you know, these are the paid options. Yeah. Here are the free options. This will get you back into your you know, Toronto airport [00:07:00] tonight. [00:07:00] Anush Elangovan: Or if you stay, here's a hotel plus this, plus this, plus. It's just like, go ahead is all I should say. Versus now I'm like, okay, can someone, you know, can I call a travel agent? Can I do this? Can I go online and log into And you know, so we gotta fundamentally rethink even those like small, nuances of, things that we do that can be automated out and AI is really, really good at doing something like this, right? Maybe I just explained an AI startup idea right now. Somebody should just start that. [00:07:29] Andrew Zigler: I think you did. Yeah, you definitely did. Someone, one of our listeners is definitely going to lift that off of you. I, I, I, you know, I hate being on the receiving end of those. You feel a little helpless and then you have to like, follow the whole flow. So I know what you mean. Like I, I like how you called out that the build and this like. [00:07:45] Andrew Zigler: Where speed is your moat and the innovation layer is protecting you, is what makes you better than your competitors. How you scale that and you bring that to market. So by understanding the problems that you're solving, uh, throwing away those older assumptions, but also [00:08:00] recognizing that like. We're building every single day, new things and new ways of using stuff that we're still figuring out the implications of. [00:08:08] Andrew Zigler: And so when you have a lot of velocity and you're introducing a lot of new ideas, and maybe you have that workflow now that automatically rebook your flight off of your late flight text message, and uh, I know I would certainly use it, but you know, what kind of philosophies guide the way that y'all think about building this ecosystem to manage that stability while letting folks. [00:08:29] Andrew Zigler: Play with the speed and the assumptions and the airplane re bookings. [00:08:34] Anush Elangovan: so, so I think, you know, we need to peel one layer down, right? and the philosophy is, Hey, we, we just discovered electricity, right? And you know what we're gonna do? We are gonna make motors, uh, or dynamos, right? Like engines. Uh, sure. We don't know if it's gonna be a Ferrari that you're gonna make, or it's a a a a dump truck. [00:08:57] Anush Elangovan: That's good for doing this. But let's [00:09:00] let, which is also required, right? You need a dump truck. You need a garbage truck. And, [00:09:04] Andrew Zigler: Yeah. You need the [00:09:04] Anush Elangovan: course you need, uh, a Ferrari for a midlife crisis, right? So, [00:09:09] Andrew Zigler: precisely. [00:09:10] Anush Elangovan: But, but my, uh, point is what do we build next? And, uh, and this is what I meant by like, okay, let's, let's take those baby steps to build the. [00:09:20] Anush Elangovan: Infrastructure that's required that we know we'll have to use, right? So, so if I just discovered electricity, okay, great. Now one, how do I save this electricity and how do I use it? So there's battery technology, so you need to do something like that, right? Like so. But then you also want to make it into an actionable thing. [00:09:37] Anush Elangovan: You want to make it for like automobiles, or you wanna use it for, you know, powering, uh, entire cities. So it is that transformational. So, uh, AI is that transformational. So, if you distill down, it'll, it'll come down to how do we think about, what we can do with this this fundamental technology that, We may not be aware of what it [00:10:00] is gonna unlock next, but at least you know the next step is clear, right? It's like a dense fog, you know, it's gonna be like, it, it's the right path. You see the light, but it's kind of like out there and, and the steps you're taking are concrete and you're like, okay, this is good. [00:10:16] Anush Elangovan: I, this is better than where I was or where we were. So we are moving forward. So you can build with the. Intuition from what you see in the short term and a tactical view, but towards what you think the future is gonna be. [00:10:28] Andrew Zigler: Right. You almost like we're all in this like fog of war, right? And like you said, you're reaching out and you're trying to step through it. You could think of it too, as like you're in the dark and your hands are up in front of you and you know that. You're, you're not gonna run your face into a wall because your hands are out in front of you, but you're not gonna maybe do much better than that. [00:10:45] Andrew Zigler: So that's kind of like, I think the eco, the, the industry, the world that we find ourselves in, uh, and we all have to, then this becomes the power of an ecosystem, of a group of people working together to create that layer of, [00:11:00] uh, of establishing the [00:11:01] Anush Elangovan: exactly. And I, I, I just, instead of, you know, saying fog of war I describe it as like, you're in this. Beautiful valley with like a morning, uh, fog that's in. You can smell the flowers. You, you hear the birds. You are like, okay, it's, we are in like, uh, utopian paradise and yes, I just need to like, continue the walk, right? [00:11:24] Anush Elangovan: and then move forward with that, conviction that you're in the right spot. [00:11:27] Andrew Zigler: Yeah. So let's talk about that ecosystem world. This nice, I love how you describe it, this grassy side of a hill in the morning that's covered in some mist and maybe we can't see 30 feet in one direction, but it sure is a beautiful hill and it smells nice. And so we're all here. And why is, in that world, why is. [00:11:44] Andrew Zigler: You know, open source, their strategic advantage that y'all are going for in the AI hardware market. And, and then how does like ROCm turn that into wins for people within that ecosystem? [00:11:56] Anush Elangovan: you know, the, the way we look at it is this, is kind of like how I view [00:12:00] AI and the ecosystem, right? But, but it is for everyone to enjoy. Uh, and so we do want to make sure that. You know, it is, uh, beneficial for everyone. [00:12:09] Anush Elangovan: The ecosystem can come in and, and innovate. It's an open innovation engine. and uh, it is very different from, you know, having a walled garden with, Hey, only I know how to do this and I'm gonna do it and throw it over the fence and you can use it or keep walking, right? So we'd like to be good citizens that way, but also. [00:12:30] Anush Elangovan: Uh, it is self-fulfilling in a way, right? Like it, the, the pace at which we innovate with open source is unmatched. Like, you know, our serving engines are like VLLM and, and sg l. Those things, uh, those frameworks are like super, super aggressive in terms of how fast they come out with features and how fast they can you know, get performant models out. [00:12:52] Anush Elangovan: And that compared with what, uh, you'd get from, you know, the likes of like T-R-T-L-L-M or something is always lagging, right? Because you [00:13:00] just can't keep up with you know, 200 commits a week just on one particular model to get that model really performant [00:13:06] Andrew Zigler: And, and, and in that world where, you know, everyone can enjoy the winds of this, what kind of customer stories or innovation stories have really stood out to you and excite you about building and creating this place for developers? [00:13:19] Anush Elangovan: Yeah. So I think the parts that are super exciting for me are when when we get to see a customer that is first skeptical. Then they start a little like, okay, fine, we'll give you a chance. Uh, we do a simple, uh, POC and then they're like, huh, this seems to work. Yeah, we told you it works. [00:13:42] Anush Elangovan: You don't have to change one line of code. Really? Yes, no need to change one line of code. Okay, let's try a production workload. So then they try it. Oh, you're more performant than the competition. Yes. We're more performant than, than the competition. So how much does it cost? And we're like, oh, it's your TCO is better with, uh, [00:14:00] AMD. [00:14:00] Anush Elangovan: So again, they're like, wow, okay, good. So now how do we deploy at scale? And then we go deploy it at scale. And when they give a thumbs up on that and they say, this is good, right? That's when you know, you, you see it go full circle from like, oh, we, we've never heard about AMD to like actually deploy to tens of thousands of GPUs In the order of a few months, right? It, it, it really is fascinating to see and very exciting and invigorating to [00:14:28] Andrew Zigler: Yeah. At like a great exposure to a lot of interesting problems. And, and then people using the infrastructure, the, the technology available to solve those problems. Really specific problems by the way, that's often why they're bringing their data and AI to it, uh, is because it is really specific and important for them. [00:14:45] Andrew Zigler: And there's a, a lot I think that other engineering orgs can learn and even emulate from AMD's success and, and having this open source ecosystem and it causing this acceleration within. You [00:15:00] know, uh, customers and enterprises that use and adopt the tools and, and, and that creates an advantage. And that goes back to why we're talking and like the real thesis of our conversation today. [00:15:10] Andrew Zigler: So how do you think engineering leaders that are listening to this and obviously tapping into this great success AMD has from an open source flywheel, how do you think other, other folks building in the same space can foster that open, first, that open source oriented culture in order to, you know, accelerate their innovation goals? [00:15:29] Anush Elangovan: Yeah, that's a very good question. So the startup that um, was acquired by AMD we, we built, I mean, we started off doing iot stuff and you know, smart ring and all that, right? But in the, the end of like, uh, and not the end, the last six years of the company was building ML compilers. [00:15:47] Anush Elangovan: And ml, ML compilers are like super, uh, complicated, sophisticated, advanced algorithms, dah, dah, dah. but it was all open source, right? So our VCs were like, wait, what do you mean your core [00:16:00] IP is open source? And um, the speed is the moat applied even then, right? It was just like, yes, if you have an idea that. [00:16:08] Anush Elangovan: Because someone saw this idea that you are, they're gonna be able to catch up, then you probably have the wrong idea anyway. But if they are, you know, you execute and they're gonna catch up, that you should assume they're gonna catch up. Right? So you gotta move forward. So keeping it open source is super important. [00:16:25] Anush Elangovan: But also to your question on like, you know, the learnings from an AMD standpoint, right? If there are, hard problems, I'd say dig in and work through it, right? Like there's no way but through it, right? That should be the simple mentality. And more, uh, frequently than not. you'll see that you'll just make it through in a, in, in good form. [00:16:52] Anush Elangovan: But if you doubt it and you're like, oh, I don't know if I should commit, if I'm, I, you know, what should just commit to do the right thing [00:17:00] every step, right? Every step, and just keep taking one step in front of the other. And in no time you'll see that you'll be running. Right. And, and yes, the first few steps will be like, yeah, everyone's complaining about your software quality. [00:17:15] Anush Elangovan: Everyone's complaining about this and that, and it doesn't work. And, and a few steps in, you know, you get, you get the hang of all the complaints that are coming in. You get the feedback loop. You're like, okay, what, what are you prioritizing again? One step in front of the other, right? You just keep knocking that out and then you get to a point where you're, it just becomes second nature, right? To do the, to do the right thing. And, and then yes, if someone gives you two options, you'll be like, fine. This is, uh, you know, there's always the resource trade off. There's always a human capital trade off, but what's the right thing to do? of course, I, I'm pragmatic about what we choose, but, but if the right thing for your long-term success is dig in, go first, principles, make it [00:18:00] happen. [00:18:00] Anush Elangovan: Well. Then just go for that. There's, there is no shortcut to [00:18:04] Andrew Zigler: acknowledging, you know, how it aligns with your mission, your core company goals, and what you're looking to achieve. And, and I, I love how you rightfully called out that in the open source world and you know, you have your technology that you've built, what you think is your moat upon, right? [00:18:22] Andrew Zigler: It's your code and, and to open source that, or to just make it where anyone could peer in is, you know. Scary in one regard, but two, it just kind of feels like you're handing away your throne room in some kind of sense, a very direct feeling sense. But the ultimately, you were really right to call out, and this is something I think about all the time, that the real power there is still the speed This the speed. [00:18:42] Andrew Zigler: That was the moat at the beginning of our conversation. It's the speed in combination with your. Very specific domain understanding of what you're building and what you're creating, and your new role as the steward of that world and how people plug into it, which [00:19:00] has frankly, a lot more influence and power than lording over a closed. [00:19:04] Andrew Zigler: You know, repository or an ecosystem, and like you said, like throwing things over the wall. Sure. There, there might be people always on the other side of that wall, but you're not gonna have a great connection with them. You're not gonna be able to really clearly understand them. I, I like your metaphor of the side of the field of the mountain a lot more. [00:19:23] Andrew Zigler: But, but in the, in this world, you know, where. That speed is, is the power and, and open source is just one way that you can harness that speed to get really far ahead and to innovate. , There's other parts of this equation that you can be experimenting with too, and I'd love to pick your brain about them as a software leader and, and, and one of them is about looking forward and kind of understanding that future that we're all building towards and beyond today's models and hardware. [00:19:48] Andrew Zigler: You know, what do you see as the next major bottleneck or opportunity in the AI compute space? As, as you know, enterprises and folks start to get a little more mature about what's available to [00:20:00] them. [00:20:00] Anush Elangovan: Yeah, I think, the bottleneck and opportunity is, uh, what I'd call, call walking the last mile of ai. Right. Uh, and like I I, I gave you an example, uh, previously, but, but it's similar to that. It's like there are cases where Humans have so many, uh, things to do in your day. You know, like the, if we sit down and actually had a customer focus like, okay, these customers lives, I'm gonna save four hours of this customer's life. And if you actually sit down and look at all of that, it'll be. Easily automatable, easily you know, uh, applicable, uh, for ai, right? [00:20:39] Anush Elangovan: Like, but then making it happen is gonna take a little bit, right? It's like maybe it's, uh, paying your utility bill, right? Or something like that, right? Or, or, your healthcare explanation of benefits. Uh, like, I'm sure you get an explanation of benefits, and I'm like, I, I don't even know what that thing is. [00:20:55] Anush Elangovan: It's just like EOB and like. [00:20:57] Andrew Zigler: it's a big, a big old PDF. Yeah, [00:21:00] exactly. [00:21:01] Anush Elangovan: Like, like, I'm like great straight to the, uh, shredder, right? And but that could be, you know, automated with the ai, right? It, it, it'd be like, Hey, the summary of this thing is you went and visited this day. Everything is okay. Everything is paid for, so don't worry, it's not a bill. [00:21:17] Anush Elangovan: That again, the same, uh, thing, but the sense of what that information overload is could be. Digested by ai, uh, accumulated over time and retrieved when you need it. Like, I don't, I actually don't even need to know this EOB right now, unless of course, whenever I need to know it, that maybe, you know, like for some benefits I need to figure out what do, what did I do over the past year and how do I apply it? Source:

Mike

14,195 Aufrufe • vor 7 Monaten

I made this product launch video over the weekend with just prompts It's all vibe coded There's something you should know, though: Like everyone else, a few days ago my timeline started getting full of videos like this when Remotion launched their Claude skill, so I decided to give it a go I was captivated by all the examples, so I started like everyone was saying: "just write a prompt" I typed the prompt, and it created an extremely bland, untasteful, stock-looking video 10 prompts in and it was not getting better. It was very, very bland. But at least it was something, so I kept going at it I ended up spending my entire weekend on this, 2-3 days of work. Only to realize my original reference videos that inspired me to get started were all fake Everyone was outright lying about their results. They all claimed "I made this with just one prompt", but it was just bait, they didn't really use Remotion or code at all, it was just a normal, human-made motion video Then you expand the X post and read the replies and they're all like "haha joke" in the comments, but their main post already got 1.5 million views and bamboozled everyone who didn't read further And this is a problem: when a viral trend happens, these posts flood your timeline, and you only realize that they're all noise and bait (and that they haven't even used the tools they claim) when you click through the post and read its comments. But 90% of people (like me, initially) just see the post on their timeline while scrolling, and assume it's all real. You don't go in to check every single post you see: you just like it, or save it for later, and carry on with your day, thinking what you saw was the real thing, and that it's all outstanding results, and that motion designers are really done And it's so anxiety inducing, because everyone is hyping their results, but most of it is just not true. I have stopped reading X lately because going in makes me so anxious, everyone is claiming extraordinary outlier results just for the views and clicks, and you feel like you're lagging behind and you're not good enough because you don't get those results So for this video I decided to actually take the tech out for a spin, and see what results I could really get out of it I used Remotion and Claude Code 4.5, but contrary to what everyone was claiming, this video was not "just a prompt". It was fully vibe coded, but it required much more than a prompt. It was multiple days worth of work Here's what I learned: - Making vibe coded videos with Remotion is ~10-20x slower than building app code. I've been wasting my Claude limits on this video - Everything takes a lot of manual work and reprompting. You often need to go frame by frame correcting tiny things - It makes very silly mistakes - Even Opus 4.5 has very very limited knowledge of spatial / visual things. It doesn't understand well z-indexes, layers, compositions, proportions, temporal coherence, etc. Claude Code feels extremely dumb when creating code for Remotion videos, which surprised me a lot, beacuse I had been mind blown by how incredibly well it worked with my Ruby on Rails SaaS codebases - You need to have some design knowledge to adjust things manually, you need to ask for exactly what you want, in the technical jargon it expects. You can't just say "make this more beautiful" or "animate this better" because it just creates slop - Right now vibe coded videos are promising, but I think I could have done this video faster just by doing it manually in After Effects. It really took that much work - If you have a creative idea for something you want to animate, it takes multiple hours of back and forth prompting to create just one or two seconds worth of **good** animation - Tip: PARAMETERIZE everything! It tends to hardcode magic numbers everywhere in the code, so if you change something earlier in the video timeline, everything else breaks. You want to essentially be creating "key frames" with code by telling it to parameterize every frame where something important happens, and calculate the rest of the keyframes based off that. This comes in handy when you need, for example, to adjust keyframes to match the music So in summary: vibe coded videos are promising, but right now it only works for very stock-looking videos unless you put in a ton of effort Maybe actually useful for 1-2 second web animations though, I'll try that next It will obviously get better, this feels like the quality of code generation in 2023-2024, you need to hold its hand and correct it at every step along the way. But even if video code generation was better, you would still need someone with motion design knowledge to at least set the creative direction, lay out the overall script and composition, etc. It's not completely hands-off unless you want slop And a word on caution: especially here on X, there's 90% hype and 10% reality, nothing is what it seems. Do not believe what you see online, people are constantly baiting and then just laughing it off in the comments

Javi

311,442 Aufrufe • vor 5 Monaten

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,105 Aufrufe • vor 3 Monaten

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 Aufrufe • vor 2 Monaten

The 40,000% ROI "Bug": How Claude Code Cracked the TradingView Holy Grail most people think the elite traders at the top of the mountain have some secret indicator or a hidden math formula that gives them a forty thousand percent return. they assume the game is rigged against the small player and that you need a multi million dollar budget just to get a seat at the table. the truth is that the holy grail of trading is actually hidden in plain sight inside a community tab that most people scroll past every single day i spent years losing money to liquidations and over trading because i thought i had to manually predict where the price was going next. i even spent hundreds of thousands of dollars on developers to build apps for me because i was convinced that i would never be able to code the systems myself. it turns out that once you stop trying to be a genius and start using the tools that are already available you can crack the code to unlimited trading strategies the secret is not in a single indicator but in the process of research back test and implement. if you go to the community section of trading view you will find an endless stream of source code for indicators that people have built over decades. most traders just slap these on a chart and hope for the best but if you are a data dog like me you know that a chart is just a pretty picture that lies to you i believe that code is the great equalizer because it allows us to take these public ideas and turn them into fully automated systems that trade for us while we sleep. i decided to learn to code live on youtube to show everyone that you can iterate your way to success without being a math wizard or a stanford graduate. now i have fully automated systems that manage my capital instead of getting liquidated by emotional decisions in the middle of the night the biggest trap in the trading world is something called repainting and it is the reason why so many strategy back tests look like they are printing money when they are actually just a scam. repainting happens when an indicator looks at future data to tell you what happened in the past which makes every buy and sell signal look like a perfect entry at the top and bottom. if you trust a back test on a basic chart without understanding the logic underneath you are just building a house on a foundation of sand this is why i transitioned all of my serious work into python because python does not lie to you. in python you can control the data flow tick by tick and bar by bar to ensure that no future data is leaking into your strategy. i built a back test architect which is a specialized sub agent that knows exactly how to take a simple idea and test it against twenty five different data sources all at once when you run a strategy across btc eth apple google and tesla you start to see the real truth about whether a strategy has an edge or if it was just a lucky fluke on one chart. i saw one strategy this week that showed a one million percent return which sounds like a total lie but the data does not have an ego. even if a number looks insane you have to investigate it and incubate it with tiny size to see if it holds up in the live market you must treat your trading like a business where you are the manager and the code is your team of tireless employees. i have sub agents running for me right now that act as masters of specific tasks like converting pine script into python or optimizing exit logic. if you are not using these specialized ai assistants in your workflow you are essentially trying to build a skyscraper with a hand saw while everyone else is using heavy machinery most people get stuck in the beginner phase because they think they need to write every single line of code from scratch. the reality is that the best developers are just really good at importing the hard work of others and connecting it like lego blocks. i use a library called ccxt that allows my bots to communicate with every major exchange in the world with just a few lines of script which saves me months of development time the reason i show everything live is because the industry is filled with gatekeepers who want to keep the secrets of automation to themselves. they want you to stay as a manual trader who pays high fees and provides liquidity for their algorithms. once you learn to automate you are no longer a victim of the market but a participant in the architecture of the financial system if you are sitting there right now feeling defeated because you just got smoked on a trade or you missed a massive pump you have to realize that those emotions are your greatest enemy. a computer does not feel fomo and it does not get tilted after a loss; it just waits for the next signal that fits the parameters you defined. my mission is to help you get to a place where you can walk away from the screen and let the machines do the heavy lifting learning to code is actually much easier than learning a second language because the syntax is logical and the feedback is immediate. i spent ten years in tech scared to touch a keyboard for anything other than emails because i thought i was not smart enough for engineering. once i realized that code is just logic i was able to build my first profitable bot within a few months and i have never looked back the transition from a manual trader to an algorithmic expert is about building a robust framework for testing your ideas as fast as possible. you want to be able to find an indicator on trading view convert it to python and run it against years of historical data in less than five minutes. if you can do that you have a higher chance of success than ninety nine percent of the people who are just drawing lines on a screen one of the most powerful strategies i found recently combines the squeeze momentum indicator with smart money concepts. when you test these individually they might show a decent return but when you combine them and add a filter like the adx you can find setups that have a massive expectancy. the key is to look for strategies that show positive returns across multiple different asset classes and time frames simultaneously even if a strategy looks like it is printing a forty thousand percent return you must always remain skeptical and look for the catch. i always incubate my new ideas with tiny capital for at least a few weeks to see how they handle real world slippage and fees. a back test is a map of the past but the live market is a wilderness that changes every single day this is why i believe in the rbi method which stands for research back test and implement. you spend your mornings looking for new ideas your afternoons stress testing them with ai and your evenings deploying the winners to the market. it is a systematic approach to wealth that removes the need for luck or guessing what a celebrity is going to tweet next the most successful traders in history like jim simons did not sit around looking at rsi levels on a fifteen minute chart. they built systems that identified mathematical edges and then scaled those systems until they were managing billions of dollars. you do not need thirty one billion dollars to change your life but you do need the discipline to stop trading like a human and start thinking like a system i give away so much for free on youtube because i want to build a community of data dogs who are all chasing the same goal of financial freedom through automation. when we work together and share our findings we can collectively identify edges that nobody else is looking at. the world is moving towards an ai dominated economy and if you are not learning to control the machines you are going to be controlled by them the road to automation is not a straight line and you will run into bugs that make you want to throw your computer out the window. but every time you fix an error and every time you optimize a script you are getting one step closer to a life where you own your time. code really is the great equalizer and it is waiting for you to pick it up and start building your own future if you can fly then run and if you can run then walk but whatever you do you must keep moving forward in this journey. trading can be heartless but the logic of code is always fair and consistent. stop being the liquidity for someone else's bot and start building the walls that will protect your capital forever

Moon Dev

245,471 Aufrufe • vor 5 Monaten

Seth Godin gave a masterclass on how to build an audience that throws money at you: 1. Being original and creative is overrated when it comes to building a business. Copy a model that already works. Find someone who has a structure that succeeds and use it instead of trying to invent something from scratch. 2. Stop making average crap. There is no shortage of pizza places, cookies, or skincare products. There is a shortage of things worth talking about. A line around the block exists because the pizza was good enough to put on TikTok, not because of TikTok. 3. The false proxy of followers is a trap. Someone can get 40 million views on TikTok and sell $200 worth of product. If you need 40 million views every time you want to make 200 bucks, you are in real trouble. 4. Marketing is creating the conditions for an idea to spread. It does not spread because you push it hard. It spreads because the people you serve benefit from telling their friends about it. 5. Remarkable does not mean neat. It means worth making a remark about. Google did not run ads for years. Facebook did not run ads for years. The iPhone did not take off because of great advertising. People talked about them. 6. Step one is to invent a thing worth making, with a story worth telling, and a contribution worth talking about. Most people buy a Birkin bag not because they need a purse but because they are buying a story about status and affiliation. 7. Step two is to design and build it in a way that a few people will particularly benefit from and deeply care about. A $220 jigsaw that feels incredible in your hand will outsell a cheap one to the right woodworker, even at ten times the price. 8. Being popular is different than being great. Being popular is different than being profitable. Find the smallest group of people with a problem they are desperate enough to pay you to solve. 9. Start with the smallest viable market. An agency built only for pediatric orthodontists will have a line out the door after four happy clients, because that specific audience does not want an innovator. They want the best at one specific thing. 10. Good decisions and good outcomes are not the same thing. Buying a lottery ticket and winning was still a stupid decision. Making something for a specific group, even if it sometimes fails, is the right decision regardless of the individual outcome. 11. Practical empathy means showing up and finding out who responds to what you are saying, even if you are not the person you are trying to serve. You do not have to be a cancer survivor to build something for cancer survivors. You just have to show up and listen. 12. Step three is to tell a story that matches the built in narrative and dreams of that tiny group of people. Context changes everything. A world class violinist playing in a subway gets ignored by the same people who would pay $200 to see him on stage. 13. You cannot make people change their worldview easily. It is far easier to tell people they were right all along than to convince them they were wrong. Meet people where their beliefs already are. 14. Authenticity is overrated. Authenticity is for your friends and family. Consistency is for professionals. Nobody wants their hotel doorman to be authentically having a bad day. They want the promise kept every single time. 15. The last time you were fully authentic was in diapers. Every choice since then has been shaped by how the world responds. That is not fake. That is called being part of civilization. 16. Step four is to spread the word, but not by you spreading it. Your customers spread it. The question is not how do I get the word out. The question is what are the conditions that make my customers want to tell their friends. 17. Status and affiliation drive almost every purchase decision once basic needs are met. When Tom's Shoes put a visible logo on a pair of espadrilles, it gave the buyer a story to tell, and her friends a reason to ask about it, creating tension that drove the next sale. 18. The same idea applied to coffee failed completely. Nobody sees the label on your coffee bag the way they see your shoes. If the system is not built to spark a conversation, the idea will not spread no matter how good the cause is. 19. Step five is the one everyone skips. Show up regularly, consistently, and generously for years to earn permission and enrollment. Most people quit too late, not too soon. Most people should never have started a project that size in the first place. 20. The biggest businesses in the world started in the smallest markets. Airbnb did not begin by trying to take over the travel industry. Find a small problem, make a promise, keep it, and do it again. Follow Yasmine Khosrowshahi if you want to see more content on marketing & branding.

Yasmine Khosrowshahi

84,424 Aufrufe • vor 23 Tagen