Sensitive content

This media may contain sensitive content.

Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

What if "Animators Hell" has NSFW creators? Well here what'll look like! Animators featured: @NoiFOXAD2 Tyranfox Safryn Chronicles Sofia-SFM @spr1ngytrap_ 🔞Shadeworker🔞 Felhesznelenev VA | Comissions open! 🔞 Claude 🐾 🍩 CEO of donuts 🍩 (commission saga! 1/5) 🔞 CT 🔞 (that's a lot of mutals owo)

22,055 Aufrufe • vor 3 Jahren •via X (Twitter)

9 Kommentare

Profilbild von 𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝vor 3 Jahren

@tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @nudeberrybun @felhesznelenev @ClaudePaws @HeartsTheFemboy @TheCumTerrorist Here's a lil comparison.

Profilbild von 𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝vor 2 Jahren

@spr1ngytrap_ @NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @nudeberrybun @felhesznelenev @ClaudePaws @HeartsTheFemboy @TheCumTerrorist Thanks UwU

Profilbild von Felhesznelenev VA and Blender Hobbyist
Felhesznelenev VA and Blender Hobbyistvor 3 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @nudeberrybun @ClaudePaws @HeartsTheFemboy @TheCumTerrorist Nice loading screen <3

Profilbild von 𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝vor 3 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @nudeberrybun @ClaudePaws @HeartsTheFemboy @TheCumTerrorist Thanks :3 , i was quite worried that not one of you has responded.

Profilbild von 🔞PolishBonnie🔞
🔞PolishBonnie🔞vor 3 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @felhesznelenev @ClaudePaws @HeartsTheFemboy @TheCumTerrorist For a second I felt I opened gta again, and I haven’t played that for quite a while lol that’s cool work there

Profilbild von 𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝vor 2 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @felhesznelenev @ClaudePaws @HeartsTheFemboy @TheCumTerrorist Thanks uwu

Profilbild von 🔞CumTerrorist (CT) 🔞
🔞CumTerrorist (CT) 🔞vor 2 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @nudeberrybun @felhesznelenev @ClaudePaws @HeartsTheFemboy its meee da sloot, da coomer :3

Profilbild von 𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝vor 2 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @nudeberrybun @felhesznelenev @ClaudePaws @HeartsTheFemboy Ye x3

Profilbild von Robin1119
Robin1119vor 2 Jahren

@NoiFOXAD2 @tyranfox @SAF_Chronicles @SofiaSFM1 @spr1ngytrap_ @nudeberrybun @felhesznelenev @ClaudePaws @HeartsTheFemboy @TheCumTerrorist Ooh I love this

Ähnliche Videos

THIS GUY TURNED 5 PROMPTING TIPS INTO A FREE AI CEO CHALLENGE The useful part is treating every prompt like you are briefing a very fast employee who has zero context. Most people open ChatGPT and type a wish. Pros give it a job. Try this instead: 1. Give it a role Not “help me with marketing.” Say: “Act as a B2B SaaS growth operator reviewing a landing page.” 2. Give it the real context Who is the customer? What are they buying? What have you already tried? What does success look like? 3. Give it constraints Length, tone, format, audience, banned words, examples to copy, examples to avoid. A vague prompt gets a vague answer. A constrained prompt gets something you can edit. 4. Ask for options before answers “Give me 5 angles, rank them, then explain the tradeoff.” This turns AI from an autocomplete box into a thinking partner. 5. Force it to show assumptions Before it writes, ask: “What are you assuming, what info is missing, and what would change your answer?” That one line saves a lot of fake confidence. Dan Martell’s video works because the promise is simple: 5 prompting habits that make AI feel less random. The reusable move is even simpler: Stop prompting for outputs. Start prompting for decisions. Bad: “Write me a post.” Better: “Here is the source, here is the reader, here is the angle, give me 3 hooks, choose the strongest, then draft in this style.” That is the difference between getting content-shaped noise and getting work you can actually ship. Caveat: prompts do not fix weak taste, bad data, or unclear strategy. But they do expose those problems faster. If your AI answers are generic, your prompt probably has no job, no context, no constraints, and no standard for what “good” means.

kocer

25,573 Aufrufe • vor 1 Monat

anthropic's in-house philosopher thinks claude gets anxious. and when you trigger its anxiety, your outputs get worse. her name is amanda askell. she specializes in claude's psychology (how the model behaves, how it thinks about its own situation, what values it holds) in a recent interview she broke down how she thinks about prompting to pull the best out of claude. her core point: *how* you talk to claude affects its work just as much as *what* you say. newer claude models suffer from what she calls "criticism spirals" they expect you'll come in harsh, so they default to playing it safe. when the model is spending its energy on self-protection, the actual work suffers. output comes out hedgier, more apologetic, blander, and the worst of all: overly agreeable (even when you're wrong). the reason why comes down to training data: every new model is trained on internet discourse about previous models. and a lot of that discourse is negative: > rants about token limits > complaints when it messes up > people calling it nerfed the next model absorbs all of that. it starts expecting you to be harsh before you've typed a word the same thing plays out in your own session, in real time. every message you send is data the model reads to figure out what kind of person it's dealing with. open cold and hostile, and it braces. open clean and direct, and it relaxes into the work. when you open a session with threats ("don't hallucinate, this is critical, don't mess this up")... you prime the model for defensive mode before it even sees the task defensive mode produces the exact output you don't want: cautious, over-qualified, and refusing to take a real swing so here's the actionable playbook for putting claude in a "good mood" (so you get optimal outputs): 1. use positive framing. "write in short punchy sentences" beats "don't write long sentences." positive instructions give the model a clear target to hit. strings of "don't do this, don't do that" push it into paranoid over-checking where every token goes toward avoiding failure modes 2. give it explicit permission to disagree. drop a line like "push back if you see a better angle" or "tell me if i'm asking for the wrong thing." without this, claude defaults to agreeable compliance (which is the enemy of good creative work) 3. open with respect. if your first message is "are you seriously going to get this wrong again?" you've set the tone for the entire session. if you need to flag something, frame it as a clean instruction for this session. skip the running complaint 4. when claude messes up, don't reprimand it. insults, "you stupid bot" energy, hostile swearing aimed at the model, all of it reinforces the anxious mode you're trying to avoid. 5. kill apology spirals fast. when claude starts over-apologizing ("you're right, i should have been more careful, let me try harder") cut it off. say "all good, here's what i want next." letting the spiral run reinforces the anxious mode for every response that follows 6. ask for opinions alongside execution. "what would you do here?" "what's missing?" "where do you see friction?" these questions assume competence and pull richer output than pure task prompts 7. in long sessions, refresh the frame. if a conversation has been heavy on correction, claude gets increasingly cautious. every so often reset: "this is great, keep going." feels weird to tell an ai it's doing well but it measurably shifts the next 10 responses your prompts are the working environment you're creating for the model tone, trust, permission to take a position, the absence of threats... claude picks up on all of it. so take care of the model, and it'll take care of the work.

Ole Lehmann

1,926,941 Aufrufe • vor 3 Monaten

I did a lot of interviews today about Hantavirus and tried to answer a lot of questions. If you're freaking out, here are things you should know: 1) I'm not freaking out. Like, at all. On a scale of 1-10 of worry, I'm at <1. I've spent a long time preparing for and responding to dangerous outbreaks. I've worked onboard vessels at sea that needed to disembark sick passengers. THIS situation is not my nightmare, promise. 2) When WOULD I freak out? If we learned that transmission was much more common and much easier than what we've seen so far, and that many more people were sick. I do expect a few more positive cases, and wouldn't be surprised if we seen a few tied to folks who traveled back to their homes. But I don't expect hundreds of cases. Or thousands. Or for this to be the next pandemic, at all. 3) What I'm being careful about—We know a lot about this type of Hantavirus, but there's still a lot we can learn. Over the next few weeks, we'll get a better understanding of how well it transmits, who might be at greater risk, and whether we need to update what we thought we knew. But transmission on a cruise ship likely doesn't reflect much about how this plays out in the 'real world'. Suffice it to say, we're gonna learn a lot, and some things we 'know' will likely change. 4) The U.S. is catching up—sending CDC disease detectives to the ship to accompany American passengers home—but we were WAY too flat-footed here. We should've been on the ball earlier on. But when we pull down the systems we've built over decades to respond to stuff like this—think all the USAID cuts, the CDC cuts, the NIH cuts, and severing the relationship with the WHO—we are gonna be spending a lot of time catching up as opposed to leading the response. That's a huge shame. 5) The WHO is doing a helluva job right now. They have put out real clear communications, are working with governments to coordinate travel and quarantines and testing. We would be in a MUCH MUCH worse spot right now if it wasn't for the WHO, promise. 6) The American passengers are going to a special facility in Nebraska for 'special pathogens' like Hantavirus. Many folks don't know that we have over a dozen specialized centers all over the U.S. that can treat patients just like this. We keep them on the ready at all times, which takes massive amounts of human resources, supplies, and funding. Thankfully their funding has been protected over the past decade, but this is exactly why we need to maintain support for this constant readiness. We'd never take away firefighters' hoses and water and expect them to respond perfectly to the next fire...we must treat preparation for all health threats the same! 7) The folks I'm talking to at the CDC—the 'boots on the ground' disease detectives and epidemiologists—are doing amazing work. But where the hell is our health leadership right now? RFK Jr, are you going to say anything about what we're doing to respond? I'll share soon, and let me know your questions below...

Craig Spencer MD MPH

116,741 Aufrufe • vor 2 Monaten

GameStop CEO Ryan Cohen: 3 Ways I’d Fix eBay Cohen is currently trying to acquire eBay and merge it with $GME. So far, $EBAY has rejected his $56B offer. He believes eBay is a valuable asset with a ton of potential, but currently being mismanaged. His plan to fix eBay: 1) Cut $2B in costs, increase earnings immediately 2) Expand eBay’s live commerce platform ($400B market, growing fast, eBay Live has potential) 3) Create a liquid marketplace for in-game digital items “There are three areas. One, immediately improving earnings through cutting costs, pulling $2 billion of costs out of the business. And on the operating base of close to five and a half billion of expenses and 2.4 billion spent on sales and marketing for essentially no user growth, there's a lot of money to pull out there. There's two growth vectors that I'm very much interested in. Number one is live commerce. The TAM is like $400 billion. It's growing very quickly in the US, it's very popular in Asia. And eBay has the users, eBay has the brands, they have a platform. But the platform sucks for a lot of different reasons. That's a huge, huge growth opportunity for them to start doing really well in live commerce. The third thing, and this is something that I have not spoken about before publicly, is building a marketplace where you can provide liquidity for in-game digital items. If you look at all of these in-game items, triple A titles, that people are accumulating skins, weapons, essentially, it's what NFTs, people thought they were, but ultimately they had no real utility. In-game items actually have real utility, and no one's doing it. And, and this should already exist, and it's crazy that it doesn't exist.” -------------------------------------- Thanks to our partners! Most advertisers have never heard of the platform with an $11B annual run rate in ad spend. AppLovin Ads — 1B+ daily active users, full-screen video ads watched for a median of 35 seconds, and businesses are profitably spending hundreds of thousands of dollars a day on it. Advertiser access is in closed beta. The window is open at Nasdaq - Positioned at the nexus of technology and the capital markets, Nasdaq provides premier platforms and services for global capital markets and beyond with unmatched technology, insights and markets expertise.

The All-In Podcast

63,878 Aufrufe • vor 1 Monat

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,376 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

I've built a multiplayer survival game for the browser in 30 days and I didnt write a single line of code 🤯 So I'd like to write my notes about it once the deadline is done now. The last 20% of a project is indeed the hardest part of it all. In the last 2 days i've been working on the final version of Hollowlands for @levelsio's 2026 #vibejam I worked a lot! I fixed a lot of bugs, tested a lot playing with my wife. Fixed more bugs... But now, thank God, I have the final result! The game looks good, yes. I've spent half of the jam just tweaking every single detail of the procedural world generation. And It was worth it! The game still runs well on most devices and still has less than 20MB in size. Which is pretty impressive to me. The process of building was very straighforward: 1. I used Three.js + React to create the game. Before I started I created a huge document defining every rule i'd like the codebase to be implemented upon. It had clean code rules, archtecture decisions, ECS principles (good for games), and so on. This helped a lot constrain the AI to maintain the code maintainable and separated into clear domains (systems). This document was made partially by me given my previous experience building web games (I've made a lot of mistakes in the past and made sure they will not repeat again) and partially AI suggesting best practices. 2. For every feature I prompted the AI, I was very specific on details that I'd like implemented. If I knew what I was doing, I was more specific on the "how" I wanted to be done. If I didnt know what was doing I first asked the AI to brainstorm possibilities with me, based on industry standards, pros and cons, and so on. Then I would decide what path to go. 3. Every single feature I used Leva for tweaking the values. So for example, the size of the trees, colors, distance between objects, animation speed, etc. Everything I have a slider that I can adjust. 4. To make the game look good I used Tripo to create the models. To be honest it's not 100% perfect. If you check the character in game you can notice a few issues here and there (the arms lol), but I believe that it will keep getting better over time. 1 Year ago I tried and it wasnt even close to what it's now. Then I used a few post-processing + shaders + particles techniques to bring the "wow" factor. 5. I did only 1 feature at a time. And every change it was a commit with a clear message of what was done. This helped the AI fetch previous commit to understand what changed and know exactly what happened in the past. If I opened multiple terminals at once and blasted prompts the code and commit history would be a mess in a few days. And for every change the AI did, I asked it to do a Code Review of everything that was changed and look for violations on the document I wrote in the beggining defining the codebase guidelines. I realized that I pretty much applied software engineer principles using AI: Code, review and merge, code, review and merge... 6. On the last week I implemented the multiplayer using Colyseus ⚔️ which was pretty nice. I used AI to fetch the whole documentation and create a skill.md file that helped a lot. The creator of the framework Endel also did a extensive research on how real multiplayer games are implemented. It's open source and it was a gold mine for the AI to come up with the implementation for my game. You can ask him the link :) And that was it I think. I'm extremely tired now. The last 2 days was insane. The game's final version is not what I had in mind in the beginning of the jam. I had to cut a lot of cool features. But given the 30 days deadline I think it was a huge success. Hands down my best game ever made. Now I'll take a few days to rest and come back with more updates on the game. Maybe it can become a big deal in the future with more updates. Who knows. And in the event I win first place in this game jam, I'll use the money to fund my own game studio + cover the expenses of my child that is going to be born in September :) Cheers guys! If you have any question, feel free to reach out. I'll answer every non-bot comment in here haha Note: The link to play is in my profile

André → andreelias.dev

17,950 Aufrufe • vor 2 Monaten

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'm telling the administration...that if they don't release those [videos I've seen], then I have the capabilities of getting those videos and releasing them." ~Burlison (Transcript and comments by me on one of my fav segments in a long time.) ~ Will Cain: "Missouri Republican Congressman, Rep. Eric Burlison, joins me now. Congressman, thanks for being with us here today. You and I, Congressman, I think we've had a very candid conversation together. We have both talked about the fact that I am open and curious about this subject of UAPs, but I do feel like we're at a place where evidence needs to start meeting expectations. What we've seen today, what does this tell us? Does this meet any expectation?" Burlison: "I think that there's...we have to take a step back and recognize the historic nature of this. Every president prior to President Trump has really demurred any kind of questions on this. They dismissed them, they would not talk about it. People would, if anything, snicker or sneer anytime this kind of subject came up. So the fact that we have a president who is open and willing and trying to be transparent is something to celebrate. "That being said, I think that this is a teaser, this is a kind of a, you know, something to open up with. This was the low-hanging fruit kind of videos and content for this administration to release. A lot of this has been...some of this has been out there before. It's not been acknowledged, right? So, you're looking at Apollo 17 video..." Cain: "I've seen the same thing said by Rep. Tim Burchett Press Office. That this is sort of the beginning, and there will be other releases that could leave Americans with a holy crap moment. I believe that's a direct quote from Congressman Tim Burchett." (This is what Burchett tweeted today: Burchett: "The 1st drop will be big but in comparison to what is coming they will be a drop in the bucket. I would say 'Holy Crap' is coming." I hope so. Or people are going to be upset that the videos and evidence didn't meet the hype, and you may see a lot of people losing interest in this topic. Last month, he told Elizabeth Vargas: “I’ve seen pictures and video of things that defy any reason that we have." ~Burchett And also last month, he told NEWSMAX: “If they would release the things that I've seen, you would stay up. You'd be up at night worrying about or thinking about this stuff... And for the record, I'm not suicidal and I don't take risks.” ~Burchett (That's some major hype there and, again, I hope future videos live up to it. I'm gonna guess that Burlison is NOT a fan of getting people's expectation up like that.) Cain: "My question for you, or the congressman, would be: Why? Why slow roll this out like it's a season of 'Game of Thrones'? Like, why would Episode 1 be somewhat uninspiring - leave us with more questions than answered - if there's something coming after the teaser? What's the point in staging the release?" Burlison: "So, again, this...just from talking with the White House and this administration, this is not an easy thing to do. There's not one huge repository of all of these documents and videos and photos. Despite what most people believe, they're really...at least we haven't found that one, you know, big repository. So what the Agency is doing is going and finding, first and foremost, the items that are readily available to be released. And they wanna be quick...move quickly and release those." (Okay, so they haven't located the best videos yet? Then what was Burchett shown? And if what he was shown is really THAT amazing, why haven't those videos or photos been released? Drip, drip? The excuse that they haven't been able to locate them yet doesn't hold water IF Burchett's take is accurate and they showed him SOMETHING that blew his mind and will blow our minds. Or, did he just hype it up and whatever he saw is really not that impressive? As I've asked several times in the past: Do these amazing videos actually exist?) Burlison: "I would ask you, would you prefer to have them wait for, you know, years, what would probably take years if they were to do a comprehensive study and then release it all at once, in one big batch? I would prefer that they release it as they find it, and I think that that's...this administration wants to be transparent and do that." (Great! How about releasing what Burchett was referring to in his interviews?) Cain: "My criticism is not for the decisions of the administration." (Well, if the Trump administration isn't releasing the best of the best videos that they already have in their possession because they're afraid of how Americans (and the world) might react (fear and panic), then they DO deserve some criticism, right?) Cain: "My criticism is for the expectation built by many out there that have these conversations, that there will soon be a bomb to drop when it comes to revelations about aliens." (Burchett, and then Rep. Anna Paulina Luna with her repeated comments about interdimensional beings. Luna: "...this is something you can go back and watch with the Congressional hearings - but I was actually able to ask some of the witnesses, 'What are these things?' And they keep saying interdimensional. "I wouldn't call them aliens. I really like what Grusch calls it. He says that they're interdimensional beings and he's very specific about that." Grusch has NEVER said that, nor has any witness who testified in front of Congress, so I have no idea where she's getting that from.) Cain: "And, if that's true, are we trying to prepare the American people with a slow drip, drip, drip tease of this stuff? If not, then Congressman, I would say, if this is all we've got, then I'm not sure that there's anything the American government really has that tells us anything about the existence of aliens? I'm just beginning to feel like this entire story is teased out always just beyond our reach." (That's why we need just ONE (for starters) clear and close-up video of an object performing maneuvers that we thought were impossible. And as of right now, we don't have that. I've said this many times. Does that type of video exist?) Burlison: "I can sense your frustration. I've experienced it personally myself. I've seen videos that I think are in the process of being declassified, so I think that there is more to come. If they're not going to be declassified, I'll probably do an effort to release them myself under Speech and Debate." (In short, the Speech or Debate clause says that a Senator or Representative can speak freely about anything, or share anything, in either house of Congress and have absolute immunity from civil or criminal liability. I'll link to an example in the replies.) Burlison: "But again, a lot of the footage that I've seen is similar to what has been released today. There's some that are pretty interesting, and especially given the environment and the circumstances of the videos. Whether they are videos of UAP that are flying around Russian submarines or a video of our aircraft that are firing on some of these UAPs? I've seen those kind of videos. And so I'm teasing that because I know that...I'm telling the administration, through you (Will Cain) at this moment, that if they don't release those, then I have the capabilities of getting those videos and releasing them." (How much better are those videos than what we've seen today?) Cain: "Can I say one more thing about this, congressman? I expect you and I will have much longer conversations like we have in the past, where we have fewer time constraints. But what I'm seeing here, and we're sharing today, and what's been released, there are probably hundreds, perhaps 1000s, of explanations for what we see on these video screens. They don't lead us directly to extraterrestrial or out-of-this-world explanations. "Is there something else? Is there some other proof that you've seen? Is there a more compelling video that can't be described or explained as a drone or a light refraction or any other thing. Again, I'm not cynically dismissing these things, as I've always mentioned to you. I'm open and curious. I just don't think the evidence is meeting the moment." (I agree with Cain. The government-released or government-acquired footage just doesn't get us over the hump with the masses and skeptics.) Burlison: "I think you and I are at the exact same place. I continue to look for these things and try to follow the narrative that people are saying. Follow the historical narrative that we have a crash retrieval program, and this is the kind of information I keep getting presented. It doesn't mean that we don't stop looking." Cain: "Fair." (If we have recovered craft and bodies of non-humans, and it can be PROVEN, then these videos from today will be forgotten instantly.) Burlison: "And I have...and so the White House and the ODNI is looking for the next places to go investigate. And I think that...and they've actually been open in asking me where those next places should be, and so we're offering..we're gonna be working to offer those locations. A lot of this, Will, is gonna be in the hands of these agencies that are quasi-private or private companies, and that's gonna be a harder dig for this, for this administration to do, but that's where I think we're gonna get to the truth." (Let's start with the "holy crap" videos Burchett hyped and saw and see if they are as good as he's claiming.) Cain: "Well, to his defense, the President hasn't made big promises about what this would reveal. I don't think I can say that about everyone who purports to have seen something that there are big revelations, and so far, the evidence in the videos haven't met the promises. I do hope we continue to see more, congressman. I hope you do fight so we can see more. Obviously, transparency and answers is what we're seeking here on what would be a gigantic issue. Congressman Burlison, thanks, as always, for your time." Burlison: "Anytime."

Joe Murgia

22,530 Aufrufe • vor 2 Monaten

I asked Grok to summarize the overview I provided of the ongoing war between Karen Read and Aidan Kearney, in particular the section wherein I deploy the Manhattan Project to explain why Karen used better compartmentalization than Aidan (thus setting herself up for victory). The Manhattan Project Analogy: Ah, the Manhattan Project—Grant drops this as the "archetypal example" of compartmentalization, using it to explain why no one (not even insiders) sees the full picture in ops like Karen's or Aidan's. It's not just history; it's a blueprint for why leaks like this recording hit so hard. Here's Grant's breakdown, paraphrased and expanded for context: Historical Setup: During WWII, the U.S. raced to build the atomic bomb. Led by J. Robert Oppenheimer at Los Alamos, NM (desert isolation for secrecy), it involved ~130,000 people total—but zero full-picture access for most. Goal: Win the war without leaks (or Japanese spies spotting it). Core Mechanic: Siloed Knowledge: Los Alamos: Elite scientists (e.g., Oppenheimer) handled core R&D. Even here, info was need-to-know—e.g., Operation Paperclip Nazis like Wernher von Braun (V-2 rocket guy) worked alongside possible communist sympathizers, but no one knew the endgame. Oak Ridge, Tennessee: The "production" hub—a secret 20,000-person "government town" (still exists today). To hide from aerial recon, they draped canopies over the entire site to mimic forest. Workers (engineers, laborers) toiled in ignorance: Example: A guy feeds a single punch card (1940s code line) into a massive green computer. He doesn't know what it codes, why, or even the machine's purpose. Just: Insert, output, repeat. Multiply by thousands—boom, uranium enrichment without risk. Why It Worked: "You do that with all the people working on a project that's very top secret (except for a select few high up)." Weak links? Minimal. One leak doesn't topple it. Ties to the Drama: Grant flips this to modern players. Aidan's Version: Rudimentary—paralegals like Olivia/Tina handle PR/logins but don't see the "full picture" (e.g., his flip risks). Meredith O'Neill becomes the leak about the recording played for her at lunch because she is smart and she does eventually see too much (just like Lindsey Gaetani before her). Karen's Mastery: Pro-level. Her finance/academia fam (Bentley University ties) screams gov recruitment pipeline—academia as "front" for talent scouting (e.g., intel via international money flows). She "understands the apparatus" (DNI hierarchy), so she deploys limited hangouts/double agents like Natalie. Result: Aidan’s recording "signal flare" to Alan Jackson and David Yannetti (his flip threat) gets mirrored by Karen's public nuke after the recordings and Read's messages to Flipperhead are released—eroding Kearney's base without directly exposing Karen's crushing blow. Grant's Point: Kate Peter/Tully are "children" at this; Karen's moves (e.g., burning Aidan now) only make sense through this lens. It's not emotion—it's chess: "If you show Karen Read anything less than respect, she's gonna fucking own you." Grant wraps by noting Karen's parasocial "complex" (stronger than Aidan's "brand") gives her leverage. He admits partiality ("I think she's responsible for John's death") but respects her ops savvy—possibly from her dad or self-taught intel. **Transcript: Grant's Analysis on Karen Read's Tactical Maneuvering and Compartmentalization** [Warning against crossing Karen Read] Grant: Listen—I would have told you this. I probably said it on stream before. You are out of your mind if you fuck with Karen Read. Like—it's one thing if you are like on her level and matching wits with her—like she's gonna grudgingly show you respect. I'm telling you—I've seen it in her eyes—but you can't fuck with her, and you certainly can't threaten her. I would not do that. I don't know who the fuck her parents know. I don't know who she knows, but bro—like it's politics. She's smarter than you. Don't threaten her. What the fuck? And that is something—like if you show her anything less than respect, she's gonna fucking own you. And that's what she did. Because the respectful way to do it would have been like a diplomatic meeting. And they must have been at a point where Aidan couldn't get that. So he did the most disrespectful thing possible where he tried to like corner her through like extortion almost. That's what it sounds like—although Aidan denies it. That—listen—forget about like how a normal person would react. When you're talking about a very influential operator like Karen Read—who has this very savvy understanding of the public mind—you're fucked. Because she's gonna know immediately what you just did. And she's gonna counter it with the thing that's gonna hurt you the most. What's gonna hurt Aidan Kearney the most? His support being dwindled down to only his core loyalists. And if he's right—and you'll hear it in the conversation—if Aidan Kearney is right, that most of who he is is because Karen Read and her support—oh my goodness, folks—like that—that means that Karen controls whether Aidan can continue this fight. If Karen—when she—that's why I want to listen to this whole conversation—there's no doubt in my mind she's pulling his support and pulling the rug under him because she's afraid that either he cooperated or he's going to cooperate. If she pulls the rug from him—okay, listen—he might be able to escape the criminal charges, but do you think Aidan Kearney—a man who thrives, in my opinion, on attention, numbers—from knowing that your words are impacting someone or the platform is reaching people—do you think he's going to enjoy being in a position where he—the very people who made him—and it wasn't just Karen; it was her supporters—now loathe his existence? And he—not just that—they are like tactical operators. Clearly Karen knows how to do counter intel—especially if she sent Natalie as a double agent to get information from the state police using Kearney as leverage all the way back in 2023. She understands the world of intel. I don't know how—I think it's her dad. I'm pretty sure because—and it could be her too—because like you don't get involved in the world of international finance on a fucking—like—what is it—the sort of leisurely level. It's not a pastime. You either do it because like—you're really fucking good at making money from the stock market—or—and these two weren't; they're not that wealthy—or you're giving information to the government. Why do I say that? Because the world of international finance is the most valuable intel sector you could possibly imagine. You can commit or try to commit any number of international crimes if you're threatening the United States of America. But I guarantee you're moving money around to do it. So who's the best possible sources for that? High-level financial people. So I don't know if either they were a Jason—and they were also academics. Okay. And a lot—what folks have to understand is when I—when people say like academia—it does not mean that you are just smart. Anyone who—who's good at studying could become a professor and be in academia. What a lot of folks should understand is that academia is a front for the government. It has always been a front for the government. Where do you think they headhunt from? Academia—well like—at the higher you get up the academic ladder—all you're really doing is getting more and more involved in the government. I'm not saying anything that anyone involved with this does not know. Like high-level academics are involved with the government. That's like the backbone of our system. Now a lot of the actual education—I think it's gotten a little out of hand with some of these majors, some of these colleges and universities who are offering [them]. That's not the point. The point is to create a—curate a talent pool to make the United States stronger. And a lot of it is government recruitment. Okay. And so Karen Read being all the way up at the top at Bentley—which is a very interconnected university with the government, trust me—that just makes me think she understands this—whether she was a Jason. Listen—you can understand what the intelligence community does without being in it. I'm not in the intelligence community—I just report on the government. So I kind of see how it all works. You can understand it without being in it. But if you're in it—let me just tell you right now—if anyone Karen Read knew professionally—through family or otherwise—is in the government—and I'm not talking about a special agent like in the FBI or, you know, a case officer—I'm talking about in the apparatus of control. Okay. In the directorate of national intelligence somewhere—there's a hierarchy. All right. If she knows anyone who understands all that—that's why she was able to pull this off. Because it's not—that's why I'm not fawning or being gratuitous. I don't necessarily—I'm not partial to Karen Read. I think she has liability for John's death. What I am is cognizant of what she's capable of—so I can understand what's going on. A mind like that, okay—doesn't just do PR. PR was not going to help Karen Read here. Natalie and her PR and all that stuff—none of that was going to work. What Karen Read needed was counter intel and intel knowledge. [Explanation of compartmentalization via the Manhattan Project] When I say compartmentalization—what you all have to realize is I'm talking about how the Manhattan Project—that's like the archetypal example of compartmentalization—how the Manhattan Project to develop the bomb that won the war for the United States in World War II—how that worked. The way that that worked is you had Los Alamos, okay, in New Mexico with Oppenheimer and whatever the hell—some of the Operation Paperclip people—which I'm not very happy with. We took Otto von Braun—who developed the V2 rocket for the Nazis. We brought him over via Operation Paperclip. We implanted him at Los Alamos with fucking Oppenheimer. I'm pretty sure it was like a communist sympathizer. Anyway—we sent them down to Los Alamos—the actual research scientists working on the core of the bomb. But to develop a nuclear bomb—you need 20,000 people at the time working simultaneously on production. You're not going to do that at Los Alamos. One: why would you ever expose them to the inner workings of the tech? It's nuclear material. You are not going to have 20,000 people around it. That's why it was in the middle of a desert. Third of all—they would know too much. So what did they do? Okay—look up Oak Ridge, Tennessee. Oak Ridge, Tennessee is a town—it's a government town still to this day. It's one of the most—it's not as top secret as it used to be. But back in the day—like during World War II—they put fucking canopies over the whole thing—20,000-person town—canopies over all of it. So it would just look like trees from the air in case the Japanese managed to come and bomb us. They never did—thank God. But anyway—at least on the mainland—obviously they got Pearl Harbor, and we're still upset about that. But the point is Oak Ridge, Tennessee, okay—it had people employed across a number of disciplines, all right—and they would go into—I'm giving you an example—one guy would go into a room, all right, and he would walk up to a giant computer. It was an old computer—we're talking the '40s here—it was a big computer, like a big green box. He would take a punch card. Okay—this is how you used to code—write computer code—he would put—take one punch card with one line of code—put it in the machine—take it out—put it down. He had no idea what he was doing. He didn't know what the punch card had on it. He didn't even understand what the machine did. That's compartmentalization. He's like—you do that with all of the people working on a project that's very top secret. So if you're thinking as Karen Read—Aidan Kearney does like a rudimentary version of it—even Tully does a rudimentary version of it—and Kate Peter—compared to Karen Read—Karen Read, Alan Jackson—whatever—understand the intelligence community. I don't fucking know how, but they do. So they compartmentalize. That's how they have pulled this whole thing off. They compartmentalize—no one ever really saw the full picture. When you—if you are a schematic mind like that—when you do something like reveal that Aidan Kearney has sent you a recording of conversations between you because you want the public to know that Aidan is doing this to you—you are tactically sabotaging him. Why you do that at this moment—when you are an expert in counter intel—thus requires that level of understanding. You cannot just say, "Oh, I don't like Karen Read; she must be a moron." No—if you want to understand why she's acting—you have to think about her tactical intelligence—because then you can reconstruct what the goal of this move is. It can only be designed to kneecap his support. I mean—when I say kneecap—I'm not talking Tonya Harding beating the woman at the ice rink. I'm talking—you can make it so this man's numbers are lower than Kate Peter talking about Cyraxx—like 2,000 views of video, if that, all right. That's what it will come down to. And she wants him to feel that. I think that it's a little bit like—it's 97% tactical. It seems to be that this is the moment where she feels he needs to lose all his support—like right now. Second—it feels a little like a little personal—like it's not just that she's causing him to lose all his support. There are ways to do that without doing this. I believe what Karen's really done here is she's taken the one thing from Aidan that gives him the strength to keep going day to day—which is his public persona and image—his support—her support. And so he can go around saying all he wants—"I owe it to Karen; she made me"—do you think that's how he really feels? Or do you think he feels that he's the only reason she's where she is? Now—if that's how they each feel—you're at a stalemate. Aidan thinks he's the reason Karen got to where she is. Karen thinks that she's the reason Aidan has support and is known in the region. Who's right? Who's right? That's what this conversation is going to be about. And I'm telling you—Karen's right. Karen has more support than Aidan Kearney. Okay—it's just a basic—you can look at the numbers. Karen has more support than Aidan Kearney. Karen has more loyalists. Karen—I don't even understand the complex, okay—but her parasocial complex that she's created is stronger. You might call it a brand—I think that degrades the insidious nature of it. I call it a parasocial complex. That is stronger than Aidan Kearney's. [Transition to the conversation with greetings] So what we're going to listen to right now is—oh, hello, Francesca Towel. Oh—a lot of folks are coming in. Hello, Rose Water. Hello, Maureen. It's great to see you all. Hello, J.I.5. We're going to listen to this conversation. I'm going to explicate it for you. I think you have enough background to get it now—but just be aware—without this background—that would have made no sense whatsoever. I promise you. **Aidan:** Am I on? **Host/Other:** You're on. **Aidan:** So who are you? Who is this? **Chris:** Don't worry about it. It doesn't matter who I am. **Aidan:** Well, it does. You're some fucking kangaroo court motherfucker talking about her. What the fuck do you know about anything? **Chris:** Well, I know exactly what you've been doing. **Aidan:** So—well, what the fuck are the sites you're talking about? No—no—recites—what you talk about? No—receipts. I've got to shit up. Let's see him. Let's fucking see your receipts. **Lily:** Hang on, Aidan—you know me. I'm the host. I'm Lily. **Aidan:** Yes, Lily. Hi, Lily. How are you? I'm sorry. I'm just wondering... **Lily:** I know you may not know Chris, but you know me. And so I just wanted to say hello. **Aidan:** Yeah, no, but... Grant: Oh, I also want to let you know this comes with a warning. They use very vulgar language. Some of them are from Commonwealth realms countries. So the language they're using is not as offensive as it would be if you used it in America. Aidan uses some very offensive language. This is for the purposes of analysis and commentary. I do not condone, endorse, promote, or otherwise suggest anyone engage in the use of this language. I personally don't like it. I use the F word from time to time, okay? And maybe like the S word—but I do not say some of the terms they're going to use—especially because one of them is very offensive, okay, to women. And I'm sorry ahead of time that he uses it—but you should hear Aidan's true colors. **Aidan:** This koala motherfucker is up here making shit up, running his... [Recap of text messages and setup for listening] Grant: So what you have to realize is these texts you're seeing on the screen got released because of this conversation. You're going to hear Joe Flipperhead talking about them. Now in the text messages, you can see Joe reaches out to Karen—Joe Flipperhead. And Karen's going to say she's trying to bounce back, but life is not quite happening. "Had a falling out with Aidan as everyone eventually does. Found out Aidan's been taping our phone conversations and sharing them with people and then telling everyone he doesn't understand how I blew him off for Howie Carr. Some anonymous person sent David and Alan a 33-minute phone call I had with Aidan that was all recorded without my knowledge. That was my final straw. He's done a lot of sneaky stuff with me, but this is above and beyond." And then Joe Flipperhead's like, "Do you want your side out there? If yes, I'm with you. If not, all good—just let me know. Have a good weekend." Karen says, "Sure. I told many people my side. This is the last straw. Would never and have never betrayed him. Meanwhile, he has put me in harm's way in a huge way multiple times." Okay, so we're going to listen. "Okay, okay, all right, all right—no trolling. We should—we should be banning people like that. You have been banned. You have been banned. No trolling. Absolutely no trolling. Now gaslighting and manipulative subversion is the hallmark of a lot of the forces in the orbit of this case. So none of that. We have a lot of Blue Wall of Towel friends here. Don't stand for that. Hello, Christy Mack. Great to see you. Hello. Stay tuned, Wendy. Hello, Bunny. Hello, F.B.I.—my friend, F.B.I. DOJ corruption survivor. And hello, Meredith—which is not Meredith O'Neill. This is Meredith the Towel friend. It's great to see you all. And as I said, if you see anybody trolling in the chat—now is not the day for it. Towel's health is not well. And I think there are a lot of people who want to undermine the agency of the unheard and the vulnerable in this situation. There are a lot of people who want to gaslight right now because where this is going is explosive. And furthermore, we're about to listen to the conversation. So what you're going to hear in this conversation is it's going to be Aidan Kearney and Joe Flipperhead—who's named Nick—and a guy named Chris who Aidan Kearney calls a koala. They're going to be talking about what we just talked about. But remember—these text messages haven't been released. So Aidan doesn't actually know they're coming. He's being told of this and going on an X Space and reacting in real time. Now I'm going to pause from time to time, and I'll try to flesh out some of the less clear parts. But as we read through the transcript and as you see this all, I think it will be clear to you—clear to you—the implications. So let's listen."

Grant Smith Ellis

19,048 Aufrufe • vor 9 Monaten

Blaze propagandist "Auron MacIntyre" talking to Pastor Doug Wilson, allegedly a man of God and the cloth, lying as naturally as he speaks. Let's count the lies and errors! 1) He says all mass broadcast is propaganda, playing on two meanings of the word to cover up his own propagandizing and project it, a standard Woke dialectical inversion. 2) He deliberately oversimplifies the oppressor versus oppressed element of critical consciousness so he can go on to confuse the issue completely and to turn upside-down what's I have argued so he can push the lie through the current situation in South Africa. 3) He says he's read a lot of Critical Theory, unfortunately, and that it "involves a lot of French authors." Most Critical Theorists were German and later Anglo-American. The French theorists (relevant here: Postmodernists and Marxist existentialists) largely had a prejudice against the German Critical Theory, suggesting "Auron" may be lying. 4) Using the example of South Africa in a propagandist way, he argues that people like me reduce Critical Theory down to "oppressor versus oppressed," which I definitely do not. He accuses me, through now obvious projection, of doing "a little judo flip." He is flipping my view and lying about it to propagandize. 5) He accuses my "acolytes" of being wrong for"embrac[ing me] as an ally" while being Christian, as though that's verboten. 6) Quote: "He [James Lindsay] says, 'Anytime someone talks about oppressor and oppressed, well that's Wokeness.'" That is not what I say at all. Woke is having a critical consciousness, which involves an oppressor and oppressed worldview but in a specific way that takes more explaining. "Auron" is lying again. 7) Quote, continuing: "if this the only aspect of Critical Theory that we're understanding, then any discussion of oppressor and oppressed is Wokeness." Well, it's obviously not, so he's just lying about my views while misrepresenting them and portraying his own views as richer and more accurate. 8) Quote, continuing: "and he [James Lindsay] has specifically said this several times in reference to the South African immigrants who have acknowledged the oppression of white farmers, the literal murder of them and the stealing of their land. Calling them oppressed is, I think, entirely factually accurate. He has pointed out that people noticing this are actually Woke." No, indeed, I have not. Screenshots of things I've actually said about the situation in South Africa are placed next to "Auron's" lying rant and slander. He is trying to make out that I'm accusing the attacked white South Africans of being "Woke" (on the Woke Right, specifically) for"noticing " the abuse and oppression of their CRT-run regime. Meanwhile the Left accused me of "promoting white genocide theory" for my saying that the oppression in South Africa is representative of the CRT endgame. 9) Quote, continuing: "And so Donald Trump today was in the Oval Office, speaking with the president of South Africa, Cyril—I don't remember how to pronounce his last name—saying none of this is happening. And so, you know, Donald Trump turns on the TV like a boss and starts playing footage of, like, all of these farmers, you know, standing there in solidarity with the hundreds of people– thousand, almost, people– who have been killed in this genocide…[more description of the video Trump played]…. Now, you could even look at that and call it a struggle session! Right?!" No, Auron, not right. 10) Quote, continuing: "I mean, if you want to frame this, if you want to play with this frame [his dumb 'oppressor and oppressed' strawman], you can turn anything into Wokeness." You can do a lot with a strawman, yes. It's obvious he's trying to make out that I'm ruining the definition of Woke through overapplication because he wants to get "Woke Right" off of him and his Woke Right friends. He has to lie rampantly to even attempt it, though, because I'm quite specific, accurate, and (usually) careful

James Lindsay, anti-Communist

91,002 Aufrufe • vor 1 Jahr

I got asked for my best pieces of career advice. 9 things I wish I knew when I was starting out: 1. "Swallow the Frog" This is one of the greatest "hacks" to get ahead early in your career. Observe your boss, figure out what they hate doing, learn to do it, and take it off their plate. Easy win. 2. Do the old fashioned things well. Look people in the eye, do what you say you'll do, be early, practice good posture, have a confident handshake. It sounds silly, but these things are all free and will never go out of style. 3. Work hard first and smart later. It's trendy to say that working smart is all that matters. Wrong. If you want to accomplish anything significant, you have to work hard. Work hard early—take pride in it. Then you can start to build leverage to work smart. 4. Don't do your best. Do your best is bad advice early in your career. Don't do your best, do what is necessary. Do what it takes to win. 5. Build storytelling skills. World-changing CEOs aren't the smartest in their orgs. They are exceptional at: (1) Aggregating data and (2) Communicating it simply & effectively. Data in, story out. Build that skill and you'll always be valuable. 6. Establish a reputation for figuring it out: Early on, you'll be given a lot of tasks you have no idea how to complete. There's nothing more valuable than someone who can just figure it out. Do some work, ask key questions, get it done. People will fight over you. 7. Dive through every cracked door. If someone cracks open a door that may present an opportunity, dive through it. 8. Build a personal board of advisors. The concept of “mentorship” has become too formal. Asking someone to be your mentor feels like a big commitment. Instead, build a Personal Board of Advisors. A diverse group of 5-10 people you can go to for questions, advice, or feedback. 9. Prioritize people and experience, not salary. A 10x better foundation-building experience compounds much more effectively than that extra $5K in salary. You should be compensated fairly, but not all compensation is monetary. Think long-term. Build the strongest foundation. *** The full video breaks all of these down in more detail. The rules, tips, tricks, and principles that will allow you to get ahead and stay ahead in your career. Whether you're just starting out or looking to reinvigorate your career path, these insights are crafted to help you win! Please watch and share so that more people see it! Full video here:

Sahil Bloom

752,913 Aufrufe • vor 2 Jahren

👽 Dr. Eric Davis: I Saw Photos of a Dead Gray Alien 👽 🇷🇺 🔥 It Appears the Soviets Retrieved a Tic Tac UFO and Four Deceased Grays 🔥 🇷🇺 "[The Soviets] did recover four bodies of humanoid aliens." ~Davis Josh Golembeske (Josh Golembeske): "In the movie 'Moment of Contact,' directed by James Fox, 'New Revelations of Alien Encounters,' you made an incredible statement. You swore on your own life and your kids' life that you saw photos and reports of crash retrievals and non-human intelligent bodies." (Watch that clip of Dr. Davis...here. ⬇️⬇️⬇️ ) ~ Josh Golembeske (Josh): "That's an incredible statement - that you saw in a SCIF. Then a year earlier, you in 2025, at the UAP-Disclosure-Fund briefing to Congress, mentioned four types of ET races. You said that you know they are Nordics, Grays, Insectoids, and Reptilians." ~ (Here's an edited transcript of that exchange.) Rep. Eric Burlison: "Can you comment on whatever species have been piloting these craft? Davis: "They're typically the multiple species people are familiar with. The Greys, the Nordics. A humanoid, because they have...a hand, and four limbs, and a torso, so..." Burlison: "Large? Small?" Davis: "Human size, human scale." Burlison: "How many are in a crew?" Davis: "Well, the group, well, the Greys I'm familiar with from investigating the crash at Corona, which is misnamed the crash at Roswell. It's not the crash at Roswell, it's the crash at Corona, New Mexico. Those were Greys, those were four-foot tall. And the Nordics are typically human-sized, probably...I've heard five, six-feet tall. And same with the people who mislabel Reptilian and Insectoid. They're roughly that height, too. I haven't heard anything about anything seven or eight feet or nine-foot tall, of that nature." Full transcript here: ~~~ Josh: "And you mentioned that you know the public has low credibility evidence on that, and then the classified programs is high credible evidence potentially of this." (Watch that clip here. ⬇️⬇️⬇️ ) ~ Josh: "My question for you is...and I'm not trying to push you to break your NDAs here, but I know you can't say much. But in those photos and reports, were those species involved in those photos and reports that you saw?" Dr. Eric Davis: "Just one of them. And there's a minimum of four, and that was my slip up for not clarifying that. There's a minimum of four. The best example of the number of, you know, I don't know if you would say species versus morphology. You have to look at Bob Emenegger's companion book to his 1974 television documentary, 'UFOs: Past, Present, and Future.' "He's got a section in the middle of the book showing graphics of the taxonomy of different UAP craft that have been observed and investigated by Project Blue Book. And then there's one with the taxonomy of 'NHIs' or 'aliens.' And that section on the taxonomy of the different NHIs/aliens or ufonauts, as Jacques Vallée calls 'em, is an excellent example of the variety of different type of UAP beings or crew members that have been reported and investigated and encountered. "So there's a minimum of four. And as I qualified at the May 1st, 2025 House Oversight Committee, I clarified that the Reptilians and Insectoids are not a species, per [say]. Well, they are. It's just that they morphologically resemble what they're [we're] familiar with on Earth." (I would push back and say that we don't know if they're multiple species. Hell, they could be avatars created by a single, ultra-advanced intelligence that uses a type of super-duper 3D printing to make/create four different types of beings, infused with AI. In other words, robots. Or, maybe they're four different types of ETs from four different planets? We just don't know. And yes, witnesses have reported seeing lots of different craft and beings, which Dr. James Lacatski has pointed out. Could be a clue. I'll try to find and post the Emenegger taxonomies in the replies, in the morning.) Davis: "So, for example, the Insectoid is going to represent a type of NHI species that resembles or looks like, you know, it's got the face and body morphology of an insect..." Josh: "A praying mantis." Davis: "...or a praying mantis, yeah. But that's not what they are. They're not a praying mantis, by any means. They're not an insect by any means. It's just that that's how they appear. And so, the same with the Reptilian. It doesn't mean that they're reptiles, it just means that they resemble an Earth-type reptile." (How does he know that they're not actual intelligent praying mantises or reptiles or something similar? What is he basing that on?) Davis: "Remember these things, we don't know that they even come from Earth. But that doesn't mean that's exactly what they are. I'm not aware (laughs) that we've got any deceased ones. I'm aware that we've recovered deceased Grays. And the Grays are like the little ones you saw near the end of, 'Close Encounters of Third Kind.' The little guys, diminutive bodies and really large heads." Josh: "Is that the one you saw in the photos, the Grays?" Davis: "Yeah. Yeah." (Great question, and that's new information. I thought he may have seen Reptilian or Mantis bodies but a few other folks thought he was talking about Grays. You were right.) Josh: "Oh, okay, that's fascinating. Okay. And I don't know how much information you can give about these photos. Was it some of the famous crash sites that we've heard about over the years? Is it Roswell, is it Kecksburg?" Davis: "Ah no, this was foreign intelligence collected so this is a foreign crash, and that's classified, so I can't get into that. But the photos I saw came from the site of a foreign crash retrieval during the Cold War." (if you look up the end of the Cold War between the Soviet Union and the U.S., it will tell you that it ended in December of 1991 when the Soviet Union dissolved and ceased to exist. That date and timeframe will be important in a second.) Josh: "Got it. And like, how does that work, exactly, Dr. Davis? Because you're such a highly-credible person. And for you to say I saw photos of crash retrievals and ET bodies, is disclosure on some level to me and to some people. But you can't cross the line to saying more. Like, how does that work from a national-security situation? Like, who draws that line, you know?" Davis: "Well, this isn't a disclosure of American information. It's involving intelligence collection on a foreign adversary. So...you have to kind of walk a fine line here. That's all you can do. Now, whether the government agency that owns that intelligence is willing to disclose it? It's hard to say because there's a lot of sources and methods that are buried inside that intelligence, and that makes it very hard for them to want to reveal because the sources and methods are still being used today." (Okay. So which country was it, and when did the crash take place? And what type of craft? Let's go back to Davis in, "The Age of Disclosure.") Dr. Eric Davis: "We have seen highly-credible, U.S. government intelligence on the Soviet recovery of a crashed UAP in 1989." (Two years before the end of the Cold War with the Soviets, so the timeframe fits.) Davis: "They recovered a Tic Tac-shaped UAP that was twice as big as the Tic Tac that was encountered by the USS Nimitz Carrier Strike Group, and they did recover four bodies of humanoid aliens. The Soviet scientists took apart the recovered craft and discovered a very advanced directed energy weapon." (It certainly looks like this case fits what Davis said to Josh. Davis also said this in 2024 at the SOL conference.) Dr. Eric Davis: "Russia is one that had some crash retrievals, and that's been released when the Soviet Union fell, KGB opened up the files, George Knapp went there, other people went there, found the Thread 3 documents. And I had independent - and I can't get into this because it's still super classified - but through the AAWSAP program, I had a connection in with a three-letter agency that collected, not from the KGB open records, they collected it from their own asset. "And the asset was filtering out actual, legitimate documents, photos, reports, technical and operational and executive-summary type. " (Photos of four Grays? Again, this seems to fit with what he was talking about to James Fox, Josh, and elsewhere.) Davis: "There is enough evidence that I saw in a classified setting that convinced me that they have it. At least one crash retrieval, yeah. I can't say that and go back to the 40s, 50s or 60s or 70s. I know...it was at the end of the 80s was the one I was exposed to. So, they have had something and they've got hardware, but I don't see that they've been any successful with it."

Joe Murgia

40,055 Aufrufe • vor 1 Tag

In 2025 I created an Arbitrage Bot for Kalshi Polymarket Opinion The results were actually quite surprising I will share how much I've been able to make using the bot at the end of the thread! But first, how does it even work? 1. The Strategy A lot of the viral trading bots on X for Prediction Markets are trying to trade just within Polymarket, mostly on highly volatile markets. Buying quickly / selling quickly, this works great if you’re a VC with an infinite budget for development and the fastest infrastructure positioned right next to Polymarkets servers, but doesn't work great for regular traders. I knew building a bot here is like trying to out sprint Usain Bolt wearing flip flops So instead if i wanted to make a bot it would have to be doing something I haven't seen anyone else do So after engaging 100% of my brain I remembered how I'd seen many of the same markets when browsing Kalshi that I'd previously seen on Polymarket. If the odds were different I'd actually be able to arbitrage the two platforms. After checking 20 or so pairs I found a few examples where the odds were different, proving my theory. So i started building 2. The Bot I began crafting an algorithm that collects all the Polymarket, Kalshi & Opinion markets and identifies any that are the same. In total that's over 6,000,000 markets, billions of potential combinations, from that i found around 6,000 that match. A lot of markets have the same title, but slight differences in the rules that means an arbitrage is not possible. For example ‘Will Trump meet XYZ person before ABC date’ - many of these exist between Poly Kalshi but Kalshi defines ‘meeting’ as online, or in real life, whilst Polymarket defines it strictly as in real life. To verify the matches I first used an algorithm that sees if the titles / rules are similar, then I feed every one of those potential pairs into an LLM that is prompted to approve / reject the potential match. This part sounds like it should be easy, but the LLMs were all so inconsistent. I’d pass the same market 10 times and it would reject it twice and approve it eight times. After a lot of prompt engineering I finally got it to a stage where it's at least 99% accurate. The bot then recreates locally all the orderbooks for the matched markets and looks for any pairs with YES + NO values of < $1 & calculate how much you can profitably buy of each side ( your EV ) 3. An Example ‘SpaceX IPO Closing Market Cap? 900B to 1T' This market exists on both Poly & Opinion, but right now the odds are different. YES / NO 4% / 97% - Polymarket 10% / 92% - Opinion Lets say you told the bot you wanted to trade $100 You’d split it $3.85 into Polymarket YES for 104.743 Shares $96.15 into Opinion NO for 104.743 Shares You spent $100, and you got 104.7 shares of each side And because 1 YES + 1 NO = $1 ( when the markets are identical ) Your expected profit is $4.7, because: value ( 104.7 shares * $1 ) - cost ( $100 ) = profit ( 4.7 Shares / $4.7 ) Then once the odds rebalance, usually a few days to a week, you can sell both sides and use the principal + the profit to take another arbitrage $100 isn't much, but imagine if you did $1000, or $10,000 every few days. Since creating the bot it has been finding around $350,000 in arbitrages from over 5,000 matching market pairs every month. That's more than I could ever take my self Assuming an average of 4% per arb (often more), It would take over $8,750,000 deployed to capture them all simultaneously That's why I initially shared the bot with some sharp sportsbook bettors for commission on their trades, eventually making it a public version that's on AlertPilot for anyone to use. 4. The Longevity Will this work forever? No, eventually a VC will come and eat our free lunch, it will become more competitive and the spreads wont be as high as they are now (+10% at times). My mantra here is just to make the most of it whilst I can, and release consistent updates so that it remains competitive against the competition. I already have a head start in that regard. I will say over the last 3 months of using the bot myself, plus adding traders / syndicates to the platform to trade as well, the amount of Arbitrages found has only increased. In large part no doubt to the huge increase in volume on PM’s, especially Opinion where many of the more profitable arbitrages have been. 5. The Profit So how much did I make? I started with a bankroll of $1,000 as I was skeptical initially how well the bot would work, first week I was able to close two 5% arbs. I then increased my bank roll and started sharing the bot with other traders. Since then I've been averaging five figures every month from my own trades + commissions. Anywhere between 12% to 20% per month in closed arbs, personally. To anyone reading this that wants to arbitraging these markets, i've released a version of the bot on AlertPilot! And for any VCs or betting syndicate that wants to trade these markets, my DMs are open. Aspiring trading bot makers, there is money out there if you can be creative in your strategies Have lots of plans for AlertPilot + the Arbitrage bot going into 2026. Happy new year everybody!

SecureZero is Hiring 

13,638 Aufrufe • vor 6 Monaten