Sensitive content

This media may contain sensitive content.

Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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! 4/5) 🔞 CT 🔞 (that's a lot of mutals owo)

22,087 görüntüleme • 3 yıl önce •via X (Twitter)

9 Yorum

𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝 profil fotoğrafı
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝3 yıl önce

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

𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝 profil fotoğrafı
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝3 yıl önce

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

Felhesznelenev VA and Blender Hobbyist profil fotoğrafı
Felhesznelenev VA and Blender Hobbyist3 yıl önce

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

𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝 profil fotoğrafı
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝3 yıl önce

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

🔞PolishBonnie🔞 profil fotoğrafı
🔞PolishBonnie🔞3 yıl önce

@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

𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝 profil fotoğrafı
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝3 yıl önce

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

🔞CumTerrorist (CT) 🔞 profil fotoğrafı
🔞CumTerrorist (CT) 🔞3 yıl önce

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

𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝 profil fotoğrafı
𝙵𝙽𝙰𝙵 𝙿𝚘𝚛𝚗 𝙰𝚛𝚝𝚒𝚜𝚝3 yıl önce

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

Robin1119 profil fotoğrafı
Robin11193 yıl önce

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

Benzer Videolar

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 görüntüleme • 1 ay önce

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,928,326 görüntüleme • 3 ay önce

Rory McIlroy has never minced his words when it comes to his views on LIV Golf. He was asked about it again yesterday, and in typical Rory fashion, after saying he was “too judgemental” with players that went, he then said “if you want to be the most competitive golfer you can be, this (PGA Tour) is the place to be. And if you don't want to play here, I think that says something about you.” Speaking after a 5 under par 67 to climb inside the top 10 of the Truist Championship, Rory spoke about his thoughts on the news that the Saudi Arabian PIF was pulling funding to the league: “Yeah, look, I think everyone sort of knows my views on LIV and where it stands in the game of golf. I don't think I need to rehash any of that. It's never been for me and, look, it doesn't mean that LIV is going to go away. They're going to go and try and find alternative investment, whatever that may look like. But when one of the wealthiest sovereign wealth funds in the world thinks that you're too expensive for them, that sort of says something (laughing).” He then was asked what a possible route back for players to the PGA Tour would look like: “It's a question if they do want to come back. Obviously we have seen the quotes over the last few days. And, you know, it seems like some of the guys, if -- again, it all depends on what happens to LIV. But if it is a scenario where they have the option to come back and play on the traditional tours, you know, I think Brian Rolapp has said anything that makes this Tour stronger, anything that makes the DP World Tour stronger, I think everyone should be open to that. That's just good business practice. “So, but again I think there's going to be a lot of sort of bridges to cross to get there, just because, you know, obviously the guys over there are under contract and if they are able to keep it going and get a schedule together next year, it seems like those guys are still going to play the majority of their golf on LIV, in whatever form it takes.” That was followed up with a question about whether he was surprised that LIV Golf players have been outspoken about not wanting to return to the PGA Tour: “Yeah, which is totally fine. Like, again, I think I've said at the start, I was probably too judgmental with the guys that went because I was seeing it from my point of view and maybe not seeing it from other points of view. But again, I'm not going to judge anyone for not wanting to play on the PGA Tour. “I don't know, you know, does that mean that they go play DP World Tour maybe; if that's a pathway, that would make the DP World Tour stronger, and I would be delighted with that, because that's my home Tour, at the end of the day. “But this is, if you want to be the most competitive golfer you can be, this (PGA Tour) is the place to be. And if you don't want to play here, I think that says something about you.” Rory is 4 shots behind Sungjae Im heading to the weekend at Quail Hollow. Rory McIlroy PGA TOUR Truist Championship

Flushing It

33,565 görüntüleme • 3 ay önce

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,811 görüntüleme • 3 ay önce

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,694 görüntüleme • 4 ay önce

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 görüntüleme • 3 ay önce

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 görüntüleme • 3 ay önce

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 görüntüleme • 10 ay önce

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 görüntüleme • 1 yıl önce

For Those That Don’t Understand Donald Trump’s VP Pick Being JD Vance, Here’s Why “He’s a brilliant pick” “Absolutely brilliant pick by Donald Trump to select JD Vance as his vice presidential candidate, his running mate, when he sworn into office on January 20, 2025. Now look, I know there's a lot of people who are hand ringing and don't understand the pick, but I'm here to tell you JD Vance checks a ton of boxes. More boxes than anybody else that was being looked at. And there's two things about JD Vance that nobody else brings to the table. JD Vance understands what it means to grow up in a severely depressed part of the country. He understands what modern American families deal with living paycheck to paycheck. He grew up in that environment, trying to figure out how to make your money last as long as your month does. He gets it. He made his money himself. He understands the impact of addiction on society because it ripped through his family. But the thing about JD Vance is this guy is wicked smart, and he's an incredible debater, and he knows his stuff. You put him on a stage with Kamala cackling Harris, and you watch what he does to her. He's gonna expose to the entire world how inept and unqualified Kamala Harris is, not only to be vice president, but to be president if Joe Biden were to be reelected because he ain't making it a full 4 year term. But the thing that you have to remember about JD Vance is 8 years ago, he was a never Trumper. And I know that sounds like a bad thing, and the media is gonna harp on that, but you wait until you hear JD Vance explain why he's not a never Trumper anymore and how he's gonna speak to that change that he had by watching Donald Trump keep his promises and perform exactly the way he said he was gonna perform. And as a matter of fact, do for this country what he promised to do. That's what changed JD Vance's mind. He's talked about it. He's been open about it. Donald Trump is an actions guy, and JD Vance responded to that. And I think most Americans just want to be able to believe that their candidate is gonna keep their promises. And when you put someone like JD Vance on a stage or in front of a microphone or in front of a camera, and he explains how Donald Trump changed his mind through his actions and his performance, that's gonna speak to a lot of the people that are still sitting on the fence trying to decide whether or not Donald Trump is the right candidate for them. This pick was the best pick that Donald Trump has made so far. Well done.”

Wall Street Apes

728,866 görüntüleme • 2 yıl önce

👽 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

64,181 görüntüleme • 15 gün önce

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 görüntüleme • 2 yıl önce

If you want to understand the Joe FlipperHead, Olivia Lamb, Karen Read and Aidan TurtleBoy Kearney chaos; FlipperHead (a guy named Nick from Philly) got confirmation Aidan recorded Karen Read. Then the recordings leaked. Basically, Olivia works for Aidan as a paralegal, now, but Olivia used to be close to Karen in the past (and Olivia and FlipperHead used to be close, as well, on a personal level). FlipperHead, for his part, is loyal to Olivia and Karen but FlipperHead doesn't like Aidan (much like other people close to Karen). Aidan, in turn, seems to be using Olivia to discredit Flipperhead (potentially without Olivia's permission). VIDEO TRANSCRIPT: [Opening remarks on social media and focus] Grant: [Lindsey Gaetani's] been talking about on social media, but let's get to that second. What I wanna start with—let me find the tab—I wanna start with the developments related to Aidan Kearney and Karen Read, okay? So we're gonna jump right into that, and what I have here is the actual discussion. Now, if you go on my X, you will be able to see the entire transcript. I'm gonna try to scroll with you as the video plays. It's a lot, okay? And then we're gonna do part two as well. So eventually, we're gonna hit part two of the transcript. I'm gonna pause, and we're gonna go to the second video. Now, this discussion—the reason why I wanna go over this—is I was listening to it, and I was like, "Wait a minute, I speak this language that they're all talking. I understand sort of the subtext of all of this, but they weren't really talking on the surface." It's a conversation between somebody named Chris, who Aidan Kearney calls a "koala," somebody named Joe Flipperhead—who's actually named Nick from Philadelphia, who was apparently close to a woman named Olivia Lamb, who is gonna come up in this as well. Now, Olivia Lamb did a lot of social media posts about the Karen Read and John O'Keefe trial on her profile on Twitter under Olivia. Now, then Olivia started—in a public announcement—saying that she started working for Aidan Kearney. And what you're gonna hear in this conversation is there's also a woman named—who else? There's a woman who's Australian that Aidan also knows named Lily. She introduces herself in the beginning, and then she's kind of the moderator-mediator. And then there's another woman that pops up in the middle named Erika Walsh. She only speaks two or three times. She's one of Turtle Boy's moderators. She interjects at two random times: one, when someone starts talking about Meredith; and two, when Aidan starts saying how bad the content of the conversation in question—that was allegedly recorded and sent to Karen Read, between Aidan and Karen—is for Karen. And then there's a third unknown voice that pops up at the end, who sounds like—it's a female, she's American. I don't know her voice, but it sounds like she's very close to Joe Flipperhead, this guy Nick. And she uses this phrase about Nick "leaving Olivia's ass" in a way that makes me think maybe this girl is close to Nick, and like, she got close to him after Olivia and Nick separated. Now you might say to yourself, "Oh dear God, why—first of all, Grant, why do you know all this?" These people post a lot; I don't know. Tracking this thing is something I've been doing for a while. So it's not like I went into it because I wanted to know who the hell Joe Flipperhead was, or Olivia Lamb was. They entered into a world that I knew a lot about because they were trying to cover this case. And so inevitably, I just had them on my radar, and when things pop up like this, I just connect the dots. [Background on Olivia Lamb] In terms of Olivia though—so she, I don't know. There was this weird situation, I think, at the end of trial one for Karen Read. So somewhere in—I don't know—late 2024, summer 2024 or so. Weird situation where Olivia kind of then, for a few months, wasn't around as much, or she was, but not as much. And then she came back around for Aidan and said she was working on his team or something. Now, Olivia—I don't think Olivia Lamb's necessarily a bad person. I think whoever she is, and whatever she's doing, is very intelligent. But if you kind of look into that family, her mom is named Christina Lamb, and her mom does boutique consulting for law firms. I think her mom might be a lawyer, but she doesn't really—I think the way that she does consulting is more like tactically how lawyers should think about how a case is presented in the public, et cetera, stuff like that. And you have to tie this into this Elizabeth Dombrowski person out of New York that runs this Good Counsel Legal Services that proclaimed that Jen Altman and whoever else were paralegals for Aidan. You see what I'm saying? And what I think Olivia's role is—I think she just does PR. She does some paralegal work clearly, but I think she's mostly like a PR specialist. But I think why there's so much obfuscation—and I'm giving you all this background, because the conversation you're about to hear makes no sense if you don't know all this background. The context there, I think, is that—I think Olivia is a person. Like, I think she is real. But I think the reason why there's so many smoke and mirrors is that she's a conduit for implausible deniability. In the world of public relations—especially this kind of public relations—is incredibly important. So I think she's like a conduit for more entrenched public relations interests, which—okay, fine. I don't see that as per se evil. I'm a critical theorist. So I study propaganda. So like, if you are doing anything that emerged from Edward Bernays's systemic weaponization of his uncle Sigmund Freud's study of the mass psychology of the mind—if you do any of that—you're inevitably gonna catch my attention. Not because I necessarily per se think it's evil, but because that's my wheelhouse. Like, I reconstruct public relations and then I figure out what's driving that. Okay. So she—Olivia—got on my radar because of that, not necessarily because she's evil. Same, because I never really saw it. Now maybe some of the witnesses in the trial would think differently, but that's not my role here. I am like—I'm an objective observer. And um, Olivia was never really cruel. Like she just does PR. So I wouldn't necessarily say like everything she did was like right. But if you look at her style, it's not polemical. It's not—it's mostly analytical. Okay. So that's not an aphoristic or manipulative or evil person really. That's a PR specialist. And this guy, Nick—very similar, Joe Flipperhead. Okay. If you look at his posts—like, I wouldn't exactly say he's a cruel human being, you know, like he memes and stuff. Okay. He's kind of like Dave Cullinane a little bit, but he's just like a human. And you can hear it in this conversation. Like Joe is the one who's really holding Aidan accountable. Joe Flipperhead—whose name is Nick—he's from Philly. And um, I noticed 'cause I watched the stream of them one time—I don't know—he seems all right. I don't have anything against him or Olivia. In fact, I think they did a damn good job, at least Joe. Because what you'll also see here is there's another subtext. What this conversation is about is an allegation that Aidan Kearney sent a recorded conversation to Karen Read—a conversation with her—and then someone—nobody knows who—sent the recording to Karen's lawyers, David Yannetti and Alan Jackson. Now, what's weird about this is that there's also—and I don't like, whatever, I guess it is what it is—but the host, one of the hosts, Chris, this Australian guy—he might be a New Zealander, I don't know. But anyway, he starts saying directly to Aidan, "Listen Aidan, you went to lunch with Meredith—this Turtle Boy's former girlfriend—but her name is Meredith O'Neill (Meredith O). She's a person; she has an existence outside of Aidan Kearney and whether—a lot of people, I think, rightfully so, will take issue with some of the things Meredith has posted. But that's for her soul to deal with. She has to reckon with it, reflect on it, whatever the fuck, okay? That's separate from; she exists outside of the fact that she used to date Aidan Kearney." And I just wanna make that as a blanket point that like Aidan Kearney does not own someone's soul because they had some connection to him at any point in time. These people are independent people who have their own lives. So Meredith O'Neill is her name. And Meredith—like, clearly something happened between Aidan and Meredith because over the past few weeks—like, first of all, there's some more subtext to this, which is Aidan's paralegal team before Olivia Lamb came on was Courtney Healy and this woman named Tina Murray. Tina Murray —I didn't even know THE NAME until two weeks ago—but I had seen her before because she had silver hair when she was in court one time. I had no idea who it was, but she was sitting next to Courtney Healy. Now, way back when Aidan Kearney was incarcerated in late 2023, early 2024—apparently these two women, Courtney Healy and Tina Murray, were very close to Aidan Kearney. Someone had his logins, allegedly. They were helping like post for him while he was in jail, et cetera. Now, there's time back to that as well. Jen Altman is a key figure in all of this. And the reason why is that Jen Altman was the reason that Aidan Kearney and Karen Read got hooked up initially through Natalie Wiweke-Bershneider or whatever her name is. Jen Altman was also among this weird group of people. It was Tina Murray, Courtney Healy, Jen Altman, I think, and maybe just them three, who had access to Aidan in jail on a paralegal list. And at one point, Tim Bradl, Aidan's lawyer, wrote down that Jen Altman was a lawyer. She got so mad that she messaged Bradl, and then those messages got leaked. So there's all this discontent brewing within Aidan Kearney's kind of like organization, if you wanna call it. I'd call it more like a—yeah, it's like a hierarchy. And like he's at the—it's like a politician almost, but he's not a politician. You have like a top person at the top, and then you have all these staffers, and you have to manage the staffers. That's what he's dealing with. And he's gotta keep everybody like in line because like at one person breaks—especially a key—all right, two things. One, there's a reason you compartmentalize information, and you're not gonna be able to get in these type of operations because nobody needs to know everything. If you did that, then everyone would be a weak link. The problem is though, in order to compartmentalize in a bureaucracy or a schema like this, you have to have some people who actually know what's going on. Those people are liabilities. They're weak links. If you have someone who is too close and they know how you compartmentalized information, they'll see the full picture. They're the weak link. That's Courtney Healy, Tina Murray, Jen Altman, Meredith, Lindsey a little bit. These people are the weak links for Aidan because they see the full picture, whether they are aligned with him, don't like him, etc. etc. It's just they're the biggest weaknesses for him because they see the full picture. That's why he tries to either control them—in my opinion—or destroy them. But Aidan's in a real tough spot here because you can't run that playbook on Karen Read. Clearly, these people are incredibly loyal to her. Flipperhead, Olivia, etc. They may have been helping Aidan, but they're incredibly loyal to Karen. Now, what I've always suspected is that the whole point of charging Aidan Kearney was—one, he did bad things to the witnesses in the retrial, Lindsey Gaetani. He did bad things allegedly. Okay, the grand jury indicted him. But I think Brian Tully and the MSP unit that investigated Aidan—they were more interested in two different goals. Okay, they had parallel objectives beyond just the criminal proceeding. One: get information about who the target of the federal probe was after August of 2023. And it was Tully's unit and Matthew Farwell related to the Sandra Birchmore murder coverup. Number two: I think Tully wanted—and Kate Peter and Marty Keach wanted—Aidan Kearney and Michael Morrissey wanted Aidan Kearney to flip on Karen Read. It was a pressure tactic. It was always just a pressure tactic. That's what I fully believe. Now, I'm not saying he didn't do bad things. I just believe in the mind of the DA—these people were using pressure tactics to get Aidan Kearney in a tactical position where he would flip. Why do I think this? Well, a few things. One: in the fall of 2023, between like August and November, Aidan Kearney didn't need an intermediary with Karen Read. Natalie was out of the picture, although I'm suspect, because there's this new text from Natalie from August saying that like she was still loyal to Karen Read—although ostensibly they had a falling out in June of 2023 because Natalie called Karen late at night and she was upset about it. I always thought that was BS. Now I know why it was BS because there's also a March 24 message about like Joe Warren and Natalie wanting to go to court. I just have this suspicion that Natalie was never really like against Karen. What Natalie was doing was using Turtle Boy as leverage with Karen's permission—using it's called a limited hangout. Limited information about Turtle Boy's culpability for witness intimidation to the MSP so that the MSP would trust Natalie—so that Natalie could relay information back to Karen about the ongoing investigation of Karen and Aidan for conspiracy under 2747 and witness intimidation under 26813B. Now they did try to eventually indict Karen on that in March of 2024 at No True Bill, but they can do it again. They got more evidence—the state in May of 2024 about Aidan saying in Facebook messages that one Karen told him not to go to Lindsey Gaetani's apartment on December 23rd, 2023, and then some other stuff—basically where Aidan was implying that someone told him to run Jen McCabe's license plates. Who would that be? Karen Read. He didn't say it but he implied it to Jenna Rocco and Amy D'Angelis and whoever else was in that internal chat that got leaked. So I really believe that the reason why Aidan Kearney was such a liability to Karen Read—and why she was saying it out loud—is that Karen Read always saw Aidan Kearney as vulnerable to flip. Why? Because Brian Tully did his homework—whatever his motives were—and he found a few things. And I think that him and Kate Peter profiled Aidan Kearney. That's why Kate Peter had some role in this—because they thought Kate Peter should really like Aidan in a lot of ways because he used to be colleagues. Two: I think the state police thought she saw his psyche—Aidan's psyche—and could help them profile him. Three: I think Kate Peter is very hard into the world, and Tully and those other people in the unit could say like, "Yeah, we're worried about Birchmore; we got to do damage control here. Nothing's really wrong with the O'Keefe death investigation," and just—they're going to find out about Birchmore—and Kate would go along with it. That's my opinion. But Tully gets this video of Aidan that he had sent to Lindsey—and it's out there on the internet. I don't want to play the content; it's sad. But this is why I think this is what was in the prosecutor's mind when they were going—and the MSP's mind—when they were going after Kearney. Yes, he did bad things—especially to people that knew the DA and Tully like McCabe, Jen McCabe, etc. But also Aidan was an Achilles heel for Karen. Think about MSP, right? And the way we're analyzing Aidan's weaknesses via weak links in the compartmentalization chain. Okay, flip it around and think about MSP thinking about Karen. What's a weak link in her compartmentalization chain? Aidan Kearney. Now, in that regard, Aidan Kearney—if he flips on Karen Read—guarantees a conviction for Karen Read for the state, even if they can't get her on John's death. It was a backup plan. Second to that, I think though—it's a dynamic situation—and that something must have fucking happened recently. Okay, and I've long thought—and we'll read Lindsey's post on this later because she was talking about it on Twitter overnight, and I was reading it this morning, and it made me think about this—I've long suspected that Kate Peter made a deal with Aidan Kearney in the past like 6-8 months. And the deal was involving the Norfolk DA and the people prosecuting Kearney, and the goal was to get Kearney to flip. And I also think Kate wants Kearney in the Netflix documentary that she's working on with Gretchen and Sandpaper—which, they don't really understand. Like, bro, you think you're getting my footage and me if you're going to enable Kate Peter and try to portray her as the Charlotte of the internet? What planet are you on? No. No, the answer is no. But anyway, I really believe that this deal was made because why else—and I think Karen found out about it—because why else would Karen—[we're going to—the conversation is going to clarify all this]—why else would Karen on Friday authorize Joe Flipperhead to release information that confirms that Aidan recorded Karen. Now, why Karen is not going to do this if she didn't hear the fucking recording? She's not a moron. She's a tactical genius. I'm telling you—I don't necessarily agree with all the things she's done. I personally think she's responsible for John's death, but like—she's a fucking tactical genius. And you have to understand in some sense—like she wouldn't do this unless it's real. Like someone sent her that recording, and I don't believe Aidan Kearney sent it to intermediaries because if Meredith is the closest person to him—or was—in the world, and he's going to lunch with her and will only play it for her allegedly—okay, there's no way in hell that he would just send it to people. I believe—whether through a fake account or otherwise—Aidan Kearney sent that to Karen's lawyers. That's just my opinion. I think there's strong reason for him to do it. It's a message. Okay. As a result, I think Karen Read doing this had to sense that this was the moment—like this was the moment where the decision was going to be made about whether or not he cooperated. And now is Aidan's kind of like signal flare that I'm thinking—from Karen Read's perspective—Aidan sending that recording to Jackson and Yannetti is a signal flare that if she doesn't act now, he's making the choice to flip on her. Okay, well, what did she just do? She in essence just put him in the worst position possible because he had to be able to—him and Kate Peter—had to sell the narrative in public that—and this is why I was on Lindsey's profile earlier. Let me see if I can bring that up—him and Kate Peter had to sell the narrative in public that Karen was worse than Aidan Kearney. All right, so let's take a look at Lindsey Gaetani's post here. Let's read this first and then let's look at the post from Kate Peter. So Kate Peter post last night: "Karen Read has killed a man before and to my knowledge, Aidan Kearney has yet to do anything like that. Take that as you will. Regardless, they're both giant DBAGs, but you can decide who is worse. My vote is Karen Read." That's Kate Peter—one of the closest people in the world right now to Brian Tully, Michael Morrissey, and the decision makers who were initially prosecuting Kearney—telling you in plain sight what's going on. So let's read Lindsey's post: "Yes, we already know a deal was made a long time ago. How cute of Kate trying to win over the turtle riders after she pretended she was still trying to put him in jail the past several months. Does anyone of the turtle riders know who Christine Gagne is? I have no idea who that is. Does anyone know who that is? That's the woman Kate Peter blamed for wiretapping charges with TB and the person she blamed when I asked her where her deleted Google Drive went with the state's evidence. Why would Kate blame this woman for deleting evidence when this woman's name was never mentioned during the grand jury or in a single email or police report? Interesting." Well, wait a minute. Wait a minute. Wait a minute. So we know Kate Peter was providing evidence to the grand jury. We know that from the recently released court documents and discovery in the Kearney criminal case. Why was—why is Kate Peter blaming someone? Who is Christine Gagne, who—why is Kate blaming her when Kate was the one who was—there's evidence that Kate was directly providing this material to Tully, who was taking it to the grand jury. And by the way, I want people to understand: my anger here is not because Aidan Kearney was prosecuted. I think he should be held accountable. My anger here is because the people prosecuting him had ulterior motives. Lindsey Gaetani didn't have an ulterior motive. She was victimized. She was an unwitting pawn in this proxy war between Karen and the DOJ—Karen and the DOJ and Aidan on one side, and the Norfolk DA and the MSP unit on the other. But instead of trying to prosecute Aidan, it was all tactical. And nobody was told—that's the worst part. And that's why I'm so upset about all of this, because it was a disgrace. It was a disgrace to the process. If you're going to hold someone accountable, do it. You don't use it as leverage to get someone else. And if you're going to do that, be open with the people who are victimized. Otherwise, you are going to build resentment. Why would you ever want to be in a situation where you have to handle a victim? Because if they were made aware of what was actually going on, they would be upset. That is a very prime example—on its face example—that something is very wrong. Not because Aidan Kearney is absolved of liability or because I think he did nothing wrong. Absolutely not. No. Other way around. But because that kind of behavior—given impunity basically, because there's a larger fish—it's an abuse of prosecutorial discretion, not because the prosecution exists. In my opinion, a grand jury indicted him; he should be prosecuted. That's what happens when indictments get handed up. But because the aim of the prosecution was not to seek justice—it was to get—it was to pressure Kearney to flip on Karen Read. [Transition to the conversation] Now, to bring this all back—because we got to go—I want to look at this conversation here. I want to actually listen to this chat a minute. I'm going to explicate; I'm going to try to tell you what happens. "Hi, Bunny Towel. Hi, Christina. No haircut. But guess if you want to send donations—today's a good day for that. We got to get Towel to the end of the month. Towel's not going to be able to move very much for the next few days. So I could use some food if you want to send me some gift cards. I just need some help. All right. I'm a little towel. I got a lot going on. And anyway, so I'll—I'm sitting in my chair. That's as much as I can do right now. I can talk; my brain works. I can sit in my chair. I'm not doing anything else, but I should eat at some point. Anyway, so we're going to listen to this conversation because you have to think of all that background when you're analyzing. Why right now? Okay, why would Karen Read tactically right now burn Aidan Kearney? Aidan Kearney supporters are very loyal, but a lot of Aidan Kearney's base are becoming alienated because either they care more about Karen Read than Aidan Kearney or because Aidan Kearney's been on this weird tear recently where he like been attacking middle-aged women who are most of his fans. All right. Most of his fans are middle-aged women. And he goes after people's looks like whatever. So there's already this alienation happening. I believe the only reason Karen Read does this right now is because what it did—and what it's doing to Aidan Kearney—is it's decimating his support. Okay. Well, why are you decimating his support? Why are you forcing people to pick sides? Why would you do that right now? Either [he] cooperated or he's about to. All right. Now Karen Read—if she was—here's my read of this—if Karen Read was just going to cooperate, she wouldn't have done this this way. Okay. I'm sorry. It would have been completely different. I don't believe that she would have done it this way. I believe she would have done it a completely different way. And the reason why I believe that—we're going to read the text from Karen before we start listening to this. By the way, you can see I have the video here for you. What happened? By the way, just to give you a little more context. So this X Spaces that we're going to listen to—I have the full 37-minute X Space. This X Space, okay—it was before the text messages from Karen to Joe Flipperhead got released. 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 say it.

Grant Smith Ellis

36,588 görüntüleme • 10 ay önce

My first two words on this particular Sunday morning were "Hallelujah!” followed by, “Amen!” I was not in church when I uttered them. I was at my kitchen table, watching the CEO of the most valuable company in the world say precisely what mikeroweWORKS has been espousing for the last sixteen years. In other words, this is what I look like before coffee, when I find myself in violent agreement with a multi-billionaire. If you haven’t already heard, a massive challenge is upon us. With regard to artificial intelligence and the energy we need to feed it, America will either change its current direction, or get left far, far behind. I know this because I run a modest foundation that has been arguing for decades that the portion of our workforce most often described as “the skilled trades,” will become the most essential component of our economy, our independence, and our collective future. Well, the future is here. Obviously, I didn’t know that the race to dominate artificial intelligence would be the thing that finally galvanized the folks at the grown-up table. When I founded mikeroweWORKS in 2008, I figured it would be a new commitment to rebuild our crumbling infrastructure that would necessitate a collective push to reinvigorate the trades. That need is still pressing, but I never imagined the most urgent cry for more welders and electricians would be ushered in by the need for more data centers. Back then, I didn’t even know what a data center was. But today, here we are. Data centers are headline news, because they are – as Jensen Huang says - AI factories. And if we want to remain competitive with China, we need to build thousands of them. Now. And presently, we simply don’t have the workforce to do it. I’ll be discussing all of this next Tuesday in Pittsburgh, at the Energy and Innovation Summit, which is turning out to be a pretty high-profile event. looks like I’ll be joining a panel of elected officials, including the President, and dozens of well-known CEO’s to discuss Pennsylvania’s role in the energy renascence. A lot of money is being invested in Pennsylvania, (a LOT), and my message to those writing the checks will be no different than it’s been since we launched mikeroweWORKS: "Set some of that money aside to make a more persuasive case for the work itself. The skilled trades need better PR, and they need it on a national level. The country needs to see thousands of examples - real world examples - of men and women who have prospered as a result of learning a skill that's in demand." I first made this point to President Obama in an open letter to The White House in 2009, shortly after he promised 3 million “shovel-ready” jobs in his Highway Infrastructure Act. I was rooting for the President back then, and offered to use Dirty Jobs and mikeroweWORKS as vehicles to help promote his initiative. I did so because I was skeptical that people would line up to take those jobs simply because they were "created." “Filling three million shovel-ready jobs,” I wrote, “will be a lot easier if people feel enthused about the prospect of picking up a shovel. Investment alone, won’t create that kind of enthusiasm.” The White House did not respond to my offer. Understandably, most presidents do not seek the advice of marginally famous cable television hosts best known for crawling through sewers. But it’s worth remembering that the unemployment rate back then was over 10%. Millions of people were newly unemployed, and I think the former President assumed that creating three million shovel-ready jobs would translate to three million people going back to work. But that’s not what happened. Because back then, even with record high unemployment, there were 2.3 million open jobs, most of which did not require a four-year degree. Nobody wanted to talk about that. Today, that number is more like 7.6 million. Nobody wants to talk about it now, either. This is why I'm going to Pittsburgh. Just as I was rooting for President Obama in 2009, I’m rooting for President Trump today. I hope he succeeds in reinvigorating our industrial base and reshoring our manufacturing capabilities, and I want to offer my support. But if he does succeed, we’re talking about millions new jobs in manufacturing alone. And currently, there are over 400,000 jobs in that sector that are currently open, begging the obvious question... If we can’t fill the openings we have, how will we fill the one’s we’re about to create? That’s the question I’ll pose in Pittsburgh. I’ll let you know if anyone has an answer. Mike PS. Not to put too fine a point on it, but this change is truly upon us, and I've had a front row seat. Over the last six months, mikeroweWORKS been flooded with inquiries to collaborate on various recruitment initiatives and multiple industries. I mean, flooded. Not a week goes by that I don't hear from an industry leader who has come to the realization that they’ve gone as far as they can go without more skilled labor. Panic, is not too strong a word. The Maritime Industrial Base for instance, is currently tasked with delivering three nuclear powered submarines to the Navy every year for the next decade, and looking to hire 140,000 tradespeople. 140,000!!! “Do you know where they are?” they asked me. “We’ve looked everywhere.” “Yes,” I said. “I know where they are. They’re in the 8th grade.” I’ve had similar calls with the automotive industry, who needs 80,000 technicians and collision repair workers. Every single home service company is hiring – from foundation repair to roofing. The energy industry is looking for hundreds of thousands of skilled workers, and so too is the construction industry. A few weeks ago, at something called The Aspen Ideas Festival, I heard Larry Fink, the CEO of Blackrock, say we’re short 500,000 electricians. A few months before that, at an Energy Conference in Newport, I heard Governor Rick Perry describe the race to build data centers and catch up to China with all things AI as nothing short of a “modern-day Manhattan Project.” I think he's right. Part of the problem is an aging demographic. For every five skilled workers who retire, two replace them. That’s why we need to engage with eighth graders today. Maybe even before that. We have to make a persuasive case for these jobs to the next generation, and just as importantly, to their parents. That won’t solve the immediate problem, but this is marathon, not a sprint, and these jobs need to be magnified and amplified at an early age. The more immediate problem is the labor force participation rate. As we speak, millions of able-bodied Americans - for all sorts of reasons - are not working and not looking for work. According to economist Nick Eberstadt, that number is close to 7 million able-bodied men. I’m not sure what to do about that, but it’s a colossal problem that needs to be addressed. On the positive side, our last round of work ethic scholarships generated unparalleled interest. This year, mikeroweWORKSwill award $5 million to help train the next generation of skilled workers. That's ten times the number of qualified applicants we got this time a year ago. The needle is moving, and I believe we can move it a lot further, with a little help from the companies most incentivized to see the trades reinvigorated. Should be a lively conversation in The Keystone State…

The Real Mike Rowe

987,568 görüntüleme • 1 yıl önce