Sensitive content

This media may contain sensitive content.

正在加载视频...

视频加载失败

Ashley and Andy doing lovey-dovey things, fuck it. Full uncensored version (NSFW) . Credits: nemlei . . . . #hentaivídeo #sex #thecoffinandyandleilei #hentai_ #nsfw #ashleygraves #andygraves #pussy #ass

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

🔊 JADE’s boyfriend (Rizzle Kicks’s Jordan Stephens) defends Harry Styles’s BRITs performance, pushing back at claims that Harry lacks authenticity with the genres he’s exploring: “This is proximity bias, I promise you. [People are] unable to detach themselves from the memory of a young Harry Styles. If Harry had mystery… he doesn't have that in the UK. I live through the same issue with people. He has lived a life that you don't know about. He didn't even do anything [in the public eye] for an entire year. He wasn't even around. You don't know what he did; you’ve got no idea where he was. If no one knew who Harry Styles was and that was the first performance [they saw], why are you questioning whether or not he went to a fucking club? Just listen to the song. Do you know why I loved Harry's performance? I loved Harry’s performance because – and I mean this – when I was away in Canada, I saw JADE perform twice… and I genuinely, in my heart of hearts, don't think there's a better all-round [pop] performer than JADE in the UK. And I'm not even trying to say this as some lovey-dovey bullshit, I swear to fuck I'm not. I mean this as objectively as possible. Not everyone's going to love pop. But Jade does full choreo, full live vocal, she does full stage design… The amount she puts into a live show, you have to – l have to – respect it. I have to go, ‘Whoa, that is incredible.’ When I look at men who are pop-adjacent, it is fucking barren. Just seeing a solo male artist on stage doing any kind of dance routine – while singing, with a dope set, with a choir, and he's doing these little moves… I want that. I need pop-adjacent artists to get it. For me, my journey with music or movement has developed throughout my life. And actually, oddly, my relationship to techno or club or that kind of rhythm – that energy has come out in me since becoming sober. Since I stopped drinking, I actually want to engage with that club culture more, because the music brings me a sense of escape. And I see that in Harry. My point is, I can understand why a person can be taken into a place of connection to that style of music without trying to *be* anything. Dancing isn't owned by anybody. If anyone wants to dance, they can dance.”

JADE tea room ☕️

411,476 次观看 • 6 个月前

Angela White reveals the wildest on-set disasters in adult film, including turning up to a FILTHY mansion for an ANAL SCENE after full 24-hour prep “There’s, sure, I mean, sure, there are some ridiculous scripts I’ve done, but nothing like too mortifying. I do, I, I see my scripts before I agree to a scene, so I’m able to like change things in a script if I’m like, like actually the main things that I’ve changed in scripts is, is anything that was like slut shaming. So sometimes I’ll do like a script that’s kind of… no, it’s more like competitive for the women, and I’m like, No, I don’t wanna do anything that’s like, where I’m, like, slut shaming another performer, even if it’s just a role, but I just didn’t wanna represent that in any of my scenes. I want it to all be like, sex positive and fun. so, but if it’s like silly, I don’t mind, like, I can laugh at myself. Like, I don’t mind playing a silly character. I don’t care if the plumber’s coming and I’m like, you know, I don’t care about, you know, making fun of myself.” “Oh, all the time. Oh, like some days you just like have a disaster day, like, like from the moment you arrive on set. So say like, sometimes with location scouting, you don’t have the opportunity actually go and look at the location, and so you’ve seen the photos online, and you rock up, and you’re like, ‘This is nothing like the photos. Filthy. Like, I’ve turned up to like the most beautiful mansion on Sunset Plaza, and the person who was renting the place had a party the night before, and there were beer bottles everywhere on the floor, there was dog piss on the floor, there was like, it was filthy. And this was a beautiful mansion, so turning up, it’s already like, ‘Wow, we’ve got, we’ve got to clean up.’ And also, it’s an anal scene, so you don’t wanna reschedule. Like, I’ve already For 24 hours for anal, so I Whatever’s happening, someone’s sticking a dick in my ass, you know? Like, this is Oh my God. I’m sorry. I’m not doing all that prep for nothing.” “So yeah, I mean, there’s just, you could, like, every disaster you can think of, like, you know, like you’re in the make, you’re already in the makeup chair, and then you get the call that, the talent needs to cancel for some reason, and then your second choice also is now unavailable, and then your third choice is, but they turn up hungover, and you’re like, ‘We can’t do this.’ Like, like, there’s Things that can go wrong, like on any day, at any time. Thankfully, that’s not the norm though. Most of the time, things are nice and smooth, but these things do happen.”

Dunmola♋

78,722 次观看 • 14 天前

Doggy is trending because Nollywood’s Baba Tee said he didn’t have sex with Ijoba Lande’s wife Dara, that it was just ‘small’ Truth or Dare Doggy. [Full Story One Piece] Last week, content creator Lande announced his marriage had ended, because Dara slept with up to 21 nollywood colleagues. And he had evidence. Adding that, some of them are powerful people. And if he mentioned their names, they’ll kll him. Although, he mentioned actor, Babatunde Tayo (Baba Tee). Lande also accused his manager, and Dara’s bestie, Mary Gold for being the facilitator and the pimp behind his wife’s decadence. In reaction, Baba Tee denied, asked for evidence and threatened a defamation lawsuit against Lande. Over the weekend, Mary Gold confessed. She said, she took Dara to Baba Tee’s house. But when they got there. Dara started seducing Baba Tee, then they played a game. Dara herself dared Baba Tee to do sex with her. Charging him to make the game ‘romantic’. Then, Mary Gold said she left them, went to cook. And later slept off, leaving Dara and Baba Tee alone in the living room. Which she regrets doing. She denied claims of pimping Dara to men. Arguing that, Dara herself seduces these men. But most of all, Baba Tee didn’t know Dara was a married woman, talk less of Ijoba Lande’s wife. Following this.. Baba Tee had no other choice than to admit and narrate his own part. He said, Mary lied. That everything happened in the kitchen. And Mary was with them, and they asked her to look away while it happened. That, Mary was even the one daring Dara to do dirty things like twerk, moan, and asking him to spank her hass. But the doggy was brief. And he’s now suspecting they set him up. Because he was shocked how Ijoba found out, when it only happened amidst three of them. And they all did it with clear eyes. After that, they left his place. Now Darasimi’s Version. She’s saying, she was drunk. Hmm.. Anyways. According to her, Mary asked her to follow her to Baba Tee’s place to invite him as an MC for an event. When they got there, Mary initiated the truth or dare. They did the games in the kitchen. Mary participated, she was the one who asked them to make the game “Romantic”, since they were all adults. (Contrary to Mary’s claim) Mary then dared Dara (Lande’s) wife to give Baba Tee doggy. Baba Tee said he won’t pay money again, that they should just do it. So he whipped out a condom, but she refused. Only offered to “sit” on his laps. Which she did.? When they pressed her. She further said. She and Baba Tee didn’t do anything. Because BT didn’t even get an erection. When they pressed her again, reminding her that Baba Tee said they did Doggy but it was brief. Guess what Dara said. “Maybe it happened and I didn’t know, because I was drunk on 10shots”. Now, experienced players are saying they are all lying. And Baba Tee is irresponsible for sleeping with someone’s wife, even though he claims he’s not aware she was married. Also, Lande should do a DNA test on his kids. The summary of it all is, three adults played dirty truth or dare and it got casted. Follow Trending Explained for daily explanations!
13:14

Sensitive content

Doggy is trending because Nollywood’s Baba Tee said he didn’t have sex with Ijoba Lande’s wife Dara, that it was just ‘small’ Truth or Dare Doggy. [Full Story One Piece] Last week, content creator Lande announced his marriage had ended, because Dara slept with up to 21 nollywood colleagues. And he had evidence. Adding that, some of them are powerful people. And if he mentioned their names, they’ll kll him. Although, he mentioned actor, Babatunde Tayo (Baba Tee). Lande also accused his manager, and Dara’s bestie, Mary Gold for being the facilitator and the pimp behind his wife’s decadence. In reaction, Baba Tee denied, asked for evidence and threatened a defamation lawsuit against Lande. Over the weekend, Mary Gold confessed. She said, she took Dara to Baba Tee’s house. But when they got there. Dara started seducing Baba Tee, then they played a game. Dara herself dared Baba Tee to do sex with her. Charging him to make the game ‘romantic’. Then, Mary Gold said she left them, went to cook. And later slept off, leaving Dara and Baba Tee alone in the living room. Which she regrets doing. She denied claims of pimping Dara to men. Arguing that, Dara herself seduces these men. But most of all, Baba Tee didn’t know Dara was a married woman, talk less of Ijoba Lande’s wife. Following this.. Baba Tee had no other choice than to admit and narrate his own part. He said, Mary lied. That everything happened in the kitchen. And Mary was with them, and they asked her to look away while it happened. That, Mary was even the one daring Dara to do dirty things like twerk, moan, and asking him to spank her hass. But the doggy was brief. And he’s now suspecting they set him up. Because he was shocked how Ijoba found out, when it only happened amidst three of them. And they all did it with clear eyes. After that, they left his place. Now Darasimi’s Version. She’s saying, she was drunk. Hmm.. Anyways. According to her, Mary asked her to follow her to Baba Tee’s place to invite him as an MC for an event. When they got there, Mary initiated the truth or dare. They did the games in the kitchen. Mary participated, she was the one who asked them to make the game “Romantic”, since they were all adults. (Contrary to Mary’s claim) Mary then dared Dara (Lande’s) wife to give Baba Tee doggy. Baba Tee said he won’t pay money again, that they should just do it. So he whipped out a condom, but she refused. Only offered to “sit” on his laps. Which she did.? When they pressed her. She further said. She and Baba Tee didn’t do anything. Because BT didn’t even get an erection. When they pressed her again, reminding her that Baba Tee said they did Doggy but it was brief. Guess what Dara said. “Maybe it happened and I didn’t know, because I was drunk on 10shots”. Now, experienced players are saying they are all lying. And Baba Tee is irresponsible for sleeping with someone’s wife, even though he claims he’s not aware she was married. Also, Lande should do a DNA test on his kids. The summary of it all is, three adults played dirty truth or dare and it got casted. Follow Trending Explained for daily explanations!

Trending Explained

88,789 次观看 • 1 年前

Thank you to everyone who has helped me raise awareness. Over 5 years later the IOPC Independent Office for Police Conduct (IOPC) are still covering up though. One of the IOPC officers is former GMP and only GMP were allowed to take part. Instead of investigating GMP they even surveillanced me in an attempt to discredit me. Now they are relying on PAID 'experts' to reinforce their lies. This is despite Prime Minister Andy Burnham admitting I shouldn't have been treated the way I was, nor should I have been arrested/detained (others said the same). As of 2025, I am aware of 4 men who lost their lives following contact with GMP officers. THEN, I find out Greater Manchester Police are keeping their former colleague at the IOPC busy as shes also on the Salford death case (allegedly). Sky News really pushed the 2023/4 Vera Baird Review scam. It was a scam because why am I STILL hearing stuff like this? Liz Lane would you mind me releasing the interview from outside Andy Burnham former officer where I said the un-sugarcoated version of my case that didn't air that all media know about? For some reason I don't want to upset you as you saw my footage in full😓. I also told Burnham/IOPC so you shouldn't get in to trouble if you do you can just blame me cos IDGAF. Why is a former GMP officer on 2 seperate GMP Salford cases with the IOPC? I am triggered and when I'm triggered only Rich can calm me down #undiagnosed #PTSD. Now do you see why you ain't fucking coming for Richard Leslie Winter? South Yorkshire Police Greater Manchester Police. Abtisam Mohamed can you please fasttrack contact with Dr Marie Tidball MP please? Like, Greater Manchester Police WHAT THE FUCK WAS THAT like WHAT THE FUCK WAS THAT at #pendleton I CAN'T FUCKING UNSEE IT... you do realise that I KNOW, know you dickheads - you are all fucking lucky I've kept my big fat gob shut ie I could do a 2021 in 2026 or Feb 2027 doesn't really matter when you have undisclosed #receipts does it 🙄#idiots (not at home or with me) I am happy in general believe it or not - these dickheads just piss me off though. Like really piss me off. 🩷🙂SO, any way gona get dolled up cos me and Rich are off for Sunday Dinner not decided which pub yet... HAPPY SUNDAY EVERYONE else what ever you are doing.🩷🙂 (ps I promise I am not in their words 'psychotic'- I can be though if they want 😁😜) May or may not go quiet as neglected the gym stuff wana get feminine ripped💪🏽 #plans #thankyou 🩷 you all

(was) Seeking Justice (now) Raising Awareness

32,121 次观看 • 10 天前

There really are conspiracies. Democrats weaponized the CIA and FBI to spy on and entrap Trump advisors to delegitimize the 2016 election by falsely accusing the president of being a secret agent for Russia. “Former” military and Intelligence Community (IC) officials created a censorship-by-NGO scheme, designed specifically to circumvent the First Amendment, that censored, and still censors, millions of people in the US and Europe for disfavored, legal speech. And senior FBI officials, retired IC leaders, and IC intermediaries ran a sophisticated information operation to persuade journalists, social media executives, and millions of voters that Russians had obtained and manipulated the contents of Hunter Biden’s laptop. But not everything is a conspiracy. There is no evidence that NASA faked the moon landing, and abundant evidence that it happened. There is no evidence that the condensation trails (contrails) left by jets in the sky contain chemicals intentionally sprayed by the government to control the population or weather, and abundant evidence to the contrary. And there is no evidence that low levels of radiation from nuclear power plants, electromagnetic fields, or cell phone towers cause measurable harm. It’s true that suspicious things have happened and are happening. The FBI didn’t let Joe Kent, the director of the Counterterrorism Center (CTC), investigate Charlie Kirk’s death, and Israel has influenced US foreign policy. Jeffrey Epstein hid cameras in Kleenex boxes, sent himself an email suggesting a scheme to blackmail Bill Gates, and worked for the arms dealer at the heart of the Iran-Contra scandal. President Trump confirmed that the US government knows more about Unidentified Anomalous Phenomena (UAPs) than it has revealed, and high-level current and former IC officials say they exhibit characteristics that US technologies lack and may indicate non-human intelligence (NHI). The CIA experimented with mind control, its director visited Jack Ruby in prison shortly before he became psychotic, and high-level scientists and officials are dying and disappearing. But those facts do not prove many of the theories currently circulating. The FBI was right to deny Kent and the CTC new powers to go on a fishing expedition, since doing so would be precisely the abuse of IC power the US Constitution protects us against. Trump has wanted to attack Iran for decades and is solely responsible for the US military action. The email Epstein sent himself was in the voice of a Gates advisor trying to get more compensation, and there is no good evidence of a domestic or foreign intelligence agency working with him to run a sex blackmail operation. There is still no hard proof of NHI or recovered craft. And there is no good evidence of any connection between, or pattern of, high-level scientists dying. And many of those theories undermine the search for truth. Kent’s claim that Israel may have been involved in Kirk’s murder could support the defense of Kirk’s shooter, Tyler Robinson, against whom the evidence is overwhelming. Falsely claiming that Israel controls Trump undermines public trust in democracy, just as did the false conspiracy theory that Russia controlled him. Smearing and scapegoating everyone who associated with Epstein as complicit in his crimes has undermined our justice system and legitimized mob rule. False claims about UAP have been used for decades to maintain government secrecy. And irresponsible claims about the government murdering its scientists worsen delusions about mind control, directed energy weapons, and gangstalking. And so the question now is: how do we distinguish between real conspiracies and unproven theories? What can we learn from proven conspiracies and disproven ones? And how should we think about conspiracies and conspiracy theories moving forward? The Liberty Forum of Silicon Valley recently invited me to give a talk on the subject, and I addressed Russiagate, censorship, Hunter Biden’s laptop, Epstein, the JFK assassination, MK-Ultra, and UAPs. An edited version of that talk follows. Please subscribe now to support Public's award-winning journalism, read the full article, and watch the full video!

Michael Shellenberger

32,573 次观看 • 4 个月前

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,793 次观看 • 5 个月前

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 次观看 • 4 个月前

The most epic 13 minute AI rant I've heard in 2026 PS: My parent's heard this when I was playing it in the car and thought Jason ✨👾SaaStr.Ai✨ Lemkin went OFF like Stephen A Smith does on first take PPS: Full transcript below [17:00] Harry Stebbings: I I just wanted to ask Jason, if the people that we want are fundamentally different, the developers that we used to hire, we don't because AI writes the code for us. The marketers we don't want, the sales people we don't want—who who do we want genuinely? Like what is the attractive profile? Because your Anthropic’s and your OpenAIs are hiring, so so what are the people that we want in the companies of the future? [17:18] Jason Lemkin: Look, I know it sounds trite, but but the answer is simple. It's just the expression each year changes. We want folks that are genuinely AI fluent. It's pretty simple. Now you know, maybe last year we called them prompt engineers, right? That used to be a job. I don't know if you remember that actually used to be the hottest job on planet earth. Now no one needs a prompt engineer because it's pretty easy to prompt all these tools. That job died. Okay. Um and now we need go-to-market engineers. Um I think that job's going to die. We need—everyone needs so many forward deployed engineers. Like you can't hire enough forward deployed engineers. But uh you know um but Palantir just announced in whatever their their big their big event—they've gotten their deployment times down over 90% with forward deployed engineers. So that may become—so the this wave of disruption for the titles and the specificity, it's also exhaustingly accelerating. But it's really simple. You meet anyone for any role—sales, marketing, engineering, product, QA—they're they're either they're either they can't keep all of the ways they use AI to accelerate their job from spewing out of their mouth, or they're staring at you. It's there's nowhere in the middle. Like, and the person that comes in and says—it's it's it sounds Captain Obvious—but like, you know, you just had the whatever from Lovable, the the marketing head that was super popular on the show, right? She's just spewing AI-native insights into Lovable, right? It's not that complicated. You hire her, Elena, or whatever it is. You just hire her. It doesn't matter whether she's still in college or a junior or a senior or a middler, a left or right. And honestly, if you interview people, I would say of all even of the best startups I've invested in, maybe 30% of the management team meets this standard at best. 30%. Maybe less. And of the interviews I do in general, it's single-digit percents. It's just and in in that sense, it's the same as ever. Like you either lower the bar in hiring or you hire someone that's actually great. And someone that's actually great is so far ahead of you in how to apply to to employ the efficiencies of AI in their role, your jaw falls on the table. The difference is we used to need warm bodies. That's what's changing. We used to need warm bodies to answer the call, to do QA, to do code review, to to get the blue pixel to go from the upper left to the lower right. You laugh, but you need you literally needed to brute force this with humans. With AI, every day that goes by, the AI—you do not need brute force human beings on your team. And that's another reason they're shrinking. Why are all these new companies so efficient? They're just not brute forcing things with humans. They're just not. They're choosing not to. And so these team—all the brute forcers out there—everyone talks about how bloated teams got in 2021. I don't agree with that. I think they got as big as they needed to be when growth was high and you needed humans to do everything. All you look at these teams that that doubled—well if growth continued at 60% like the rate in early 2021 for 5 years or can help me do the math and every single thing a software company did required a human. You were understaffed by your 2021 headcount. You'd be sitting here in 2026. You every office in SoMa would be triple packed and you there wouldn't be enough humans to staff your company. It's just the world changed. [20:33] Harry Stebbings: Jason, you live on the bleeding edge. I think me and Rory see that and I think the world sees that when they hear you every week in terms of how you run SaaS. For all of the CEOs and execs who listen to the show, what would you advise them in terms of determining whether someone is AI fluent when they meet them for jobs, for talent? [20:51] Jason Lemkin: Here's I realized I was just asked this. I just did a review with a super fast startup growing just crossing 100 million and I was asked this question. And one of my favorite executives, I thought his answer was pretty dated and because he gave me an answer that was about 6 months old. The answer 6 months old is: "I look for folks in my team, I look for you know at what tools they play with." Okay, that was a great answer in like summer of 2025. Okay, I tried Lovable last week. Okay, the answer in 2026 is: "What commercial AI tool have you brought into your organization this month?" That's the test. Anyone that is on the bleeding edge that you would want to hire—now there are so many great products in the market. Okay, there is no excuse in any role to have not brought one tool a month into your organization. Okay, there—now there's going to be better and better tools and better and better products as the year goes on. What's the one you did? And you will see folks with their deer in the headlights to this question. What what sales tool? What marketing tool? What product tool? What engineering tool? What did you bring in? Why did you pick it? How does it working? Because if you're at remotely at the cutting edge, you're all over this. You're looking for the next agentic tools that will radically improve how you do business. This is—you think everyone thinks SaaS is at the bleeding edge, right? You know, you know, all we do is we're just looking for the tools and trying them. Okay? Okay, we're one year ahead of everybody else because we did the simplest thing in the world. Like we tried the tools early and we trained them. We trained them for a month. Okay, I'll give you—want hear a horrible example from this week? Super hot AI company valued at 6 billion. Okay, I'm not going to name it. Um, this week yesterday told us we had to quadruple what we spent on their product. Okay, their agent told us, right? And why did this happen? Okay. Well, at this $6 billion company, no one had trained the agent on its pricing properly. No one had tested it. They said, "Well, well, we've been in beta." And we said, "Well, when did the beta launch? A year ago." Okay, these are people asleep at at the wheel. You want somebody who the instant this comes up, they exactly know what the issue is. And "Hey, when I was at Lovable Replit, we trained the agent. This is how we did it. I brought in this tool. I brought in this tool that that Rory invested in last week. It solved all these issues." That's what you want to hear. And if they haven't brought in a tool in the last 30 days, at least deeply evaluated it. I don't really care whether they bought it, but gone so far down the funnel they can tell you—pick whatever tool: Fixie, Regie, GC, AIGC—I don't care how you went through it, you looked at it, you can tell me the eight ways it would improve the productivity of your business and three you didn't. Just don't hire that person because they're going to run your company to the ground. This is the job today. The job today is not to screw around on ChatGPT and to be a prompt engineer. The job today is to bring the best AI and agentic products into your organization and leverage all the hard work that the engineers have done building those products. That's your job. You don't have to screw around. You don't have to be a prompt engineer anymore. You have to be an agent deployment expert. A—this is the new job we're making up today. An Agentic Deployment Expert. That's your job from C-level to junior. Agentic Deployment Expert. Don't hire anybody else. You're going to regret it. They're going to stare at the camera. He's good. Stare at the camera. He's honorable. We could probably just I could slip away, get a coffee, and come back. No. And I I sound exasperated, Rory. And I—but the reason I am is I can just see I can see my best companies doing it. And I can see some companies I've invested in not doing it. And I want to cry. I just want to cry when they have no ADs on their team. I just—like you're flushing your years of your life down the toilet by not approaching your how you're building this company this way. [24:33] Rory: Yes. And at the risk of being positive, it's worth pointing out two things he didn't say. Well, something implicit why he said—Jason didn't do the only hire, you know, he didn't commit the um employment law, I think it's a civil penalty of saying only employ people below X who get the new new thing because he implicitly said anyone can do it provided you're willing to learn. And I think that's the big aha that's one of the positive statements to make here right? Look and I think it applies—I'm always wary of being "Hey, coming across, hey this this is the things that you all have to do." I think it applies to everyone including investors right? I mean I will say I have found that unless you're willing to invest the time learning these tools you actually shouldn't be investing in them. One of my partners Andy had this expression: "You know, if you decide you want to stop learning new things you probably should retire within 6 to 12 months and never write another check again." Maybe that's down to 3 to 6 months at this stage, right? And I think, you know, it's— [25:27] Harry Stebbings: Yeah, I actually I actually had a meeting with mine and Jason's biggest investor the other day and I—pretend he's not here—I said I think he's the most equipped investor for this generation of investing because I don't think anyone quite sits at the bleeding edge like he does on the investor side. [25:42] Harry Stebbings: Why in terms of using the equip stuff? Yeah. Yeah. In terms of using the stuff, understanding understanding bottlenecks, constraints. For sure. [25:51] Jason Lemkin: But can I just add one point? We can just cuz it's so important if it helps people. Okay, we are—and thank you Harry. We're going through these phases. Okay, and when AI started to blow up for real for us, uh call it early 2024, right? Maybe late '23, I wasn't equipped. It was too technical. I wasn't going to go in and figure out—I wasn't smart enough to figure out how to deal with a massively hallucinating LLM API and turn that and turn that into something magical. Kudos to investors and others that that got it in early '23, '22. I mean I remember I—I guess it was maybe SaaStr Annual '23. I was with David Sacks and I did a Q&A and I said, "How you thinking about AI at Craft?" He's like, "Well we're all in. We want 80% of '23 of investments to be AI." I'm like, "Great but like show me the show me the great ones in market." He's like, "They're all prototypes. We're all they're all they're all proof of concepts but we're all in anyway." That's where you kind of had to be in '23 if you weren't investing at like the LLM level. Okay, I wasn't smart enough. Then we went through this weird-ass prompt engineer era where like you you could torture these products to do something good, right? But you had to torture them. You had to like craft these crazy things that made no sense. Now we are in the era where mere ordinarily smart generalists can make these tools do magical things. And literally I go to these meetings and people be like, "I don't know how to like this is so scary. I don't know how to do this." And we show them our backends. Do you know how to do a workflow generator? Do you know how to do a a decision tree? Like we've been building these since software in the '90s. Okay, if you—I can show you all of our agents. The how they work is novel. They do have to be trained. You can't be lazy and have these agents work. But honestly, the the UI, the UX, the way we interact with them, it's just software. And so my point is: Pick yourself off the ground. This is your time now. If you felt lost in AI era, if you felt like you're behind, you don't understand what all these people are saying on X and Twitter and their Claude and and their and talking about all the 4.6 point Nano point and it's over—like you just it's not your world. This is your time. This is your time for the generalist that knows how to use software tools really really well. And I—this is my last point but it's so important. If ever in your recent life—and this is why you could be all you need to be is young at heart to Rory's point—if in the last three to five years you have successfully deployed a piece of enterprise software of any sort you yourself, not some agency you hired, but if you have deployed it, you can deploy any agentic tool. Any. And you can become the hero in your company and you can become the hero in your functional area. But I watch folks—I'm literally helping a company now that they're adding hundreds of sales folks this year with a new pre-IPO COO—he's not hasn't brought in a single tool, totally scared of it. Okay, it's not that hard. Did you use SalesLoft? Did you use Outreach? Did you use HubSpot? Do you know these tools? If you can deploy these tools, you can deploy a world-changing AI agent. And so this is the time for people like the folks that that were shut out of the AI revolution right now. The generalist folks that are not that know how to deploy software that don't even know how to build software. Like vibe coding for me was folks who knew how to build software, but you didn't have to be an engineer. Now, you just need to know how to deploy software to win with AI agents. That's all you need to know. So many people have these skills and they're petrified of AI. "How did you do that? How did you deploy an AI BDR?" Well, we bought a piece of software, we figured out how it worked for a day, we set it up in an afternoon, and then and then we did spend 30 months training it, which you didn't do with this old software because in the old days, we just had to manually upload all the data, right? And there was no training. The the only non-intuitive part is training these things. And it's it's it's just work. So that's why when I see folks on the management team not doing this, there's no excuse. You do not need to be technical to win with AI agents in Q2 of '26. You do not need to be even 1% technical. Not at all. So it's your time. Or you're going to get laid off. Or you're going to get laid off because you're not going to matter.

Arjun Mahadevan (Mr. LLC 🇺🇸)

37,934 次观看 • 6 个月前

Alright, here's the epic towel rant from tonight; And so that's what kind of tipped me off in real time. I was like: wait a minute. Is Judge Doolin ruling from the bench right now? And then I was like: wait a minute. He's ruling from the bench and ordering them to appoint a new prosecutor and potentially the Attorney General. Oh my word. How—what is this? I—this wasn't on my bingo card. Even now I'm just like: Oh my God, I can't believe he did that. Judge Doolin—in a good way. I'm just like: Oh my God, there is hope. And then to follow it up with: "Oh yeah, I'm thinking about a hearing on the contempt." Oh my God—you're telegraphing. You're going to have a contempt hearing after the Attorney General is potentially on the case. The other witnesses, however, are left in this position where they have this kind of not really well-funded—like kind of spastic prosecution, like the special prosecutors on the Kearney cases. Then you got the December 23rd, 2023 criminal charges against Aidan that were charged in Dedham District Court, 23rd or 26th or so. And that was for illegally—allegedly—recording Lindsey Gaetani and then submitting an edited version of the recording into court for some reason. I don't know why Aidan did that, especially apparently when there's an original version of the recording pursuant to some of the statements in court. And then also for intimidating Lindsey—for allegedly going over there on December 23rd, 2023—against Karen Read's advice and against his lawyers' advice, apparently, according to a leaked group chat message from Facebook in 2024—in May of 2024—going over to Lindsey's apartment. And then according to the affidavit from the search warrant for Karen Read's cell phone—allegedly telling Lindsey that she shouldn't cooperate with the grand jury. She should—she could remove information from her phone or something—that Aidan would get her a lawyer, but only if she agreed to meet with a lawyer only with him present, because she had, quote, "broken his trust." It just like—wild stuff. And that new grand jury, by the way, was apparently—it did go forward. And then in time it came out that it—that was about Karen and Aidan and witness intimidation and conspiracy, because Aidan Kearney—between October and November—really August and November of 2023—it started telling Lindsey Gaetani about his communications with Karen Read that included—in writing—Exhibit O to Karen Read search warrant affidavit, which says that Karen Read told Aidan Kearney that in November of 2023—November 28, 2023, to be specific—that Karen Read told Aidan Kearney that Karen Read and her team at ex parte conversations with former U.S. Attorney Josh Levy—which was right in the window of time that Jessica Leslie, the grand juror leaker, was leaking information. Leslie started leaking in August of 2022—which is the same month that Alan Jackson joined Karen Read's legal team. And Josh Levy—who was one of the U.S. Attorneys in charge of that grand jury—Leslie was leaking about four different cases: probably the Birchmore case, definitely the Read and O'Keefe case, definitely the CDL case. One more case. We can't really—the group of us journalists involved in this—can't really figure out. So right in the middle of that—November of 2023—Josh Levy is leaking ex parte grand jury information to Karen Read, which she's putting—she's telling Aidan Kearney about; he's putting it in writing. He just was trying to just show off for Lindsey, but you don't like—come on—like what is it? First day in the IC, bro? I'm not in the IC. I'm not part of the government. I'm a towel. But anyway—so Aidan's bragging to Lindsey, and I don't think that was a very good idea. I mean, she's brilliant and stuff, but like—why would you ever say that to her? Don't say that stuff. But anyway—like, why would you say—even if it's your significant other—unless they are read-in on the intel that you are sharing—why would you ever, ever, ever share that with someone? It exposes them to an incredible liability—which, if you love them, don't do it. It also exposes your own credibility to an incredible risk of liability. You will never be trusted by the intelligence community again. Pillow talk and honeypots are how they trap operatives. If you chase sex, they will compromise you. How can you not understand that? So if you get compromised by someone who's not an agent—just someone who's your partner and you're just telling them stuff about protected federal investigations—what do you think your reputation is going to be like among the intelligence community when you're doing that and they haven't even honeypotted you? You just voluntarily started putting this shit in writing. They're going to look at you like you are out of your mind. So anyway—Karen Read apparently is telling Aidan Kearney that she's having ex parte conversations with Josh Levy. Now, the grand jury that Leslie was leaking from was impaneled in May of 2022 when Rachael Rollins used to be U.S. Attorney in Boston. Now think about this. In 2020, Rachael Rollins and Aidan Kearney—Rachael Rollins, a hyper-liberal known for her soft-on-crime stance. We'll also hear Rollins hated Michael Morrissey. Anyway, Rollins worked with Turtle Boy to send a Republican operative named Rayla Campbell to Joe Kennedy Jr.'s events in the Senate race against Ed Markey so that Ed Markey could win the Senate seat. Now, interestingly enough, Rachael Rollins then got appointed to the position of U.S. Attorney right after that. And you might say: well, Grant, that's a stretch. No, no—because then within a few months, Rachael Rollins—part of the reason she gets thrown out of office by the DOJ OIG—is because she attends an event in Andover with—guess who?—Dr. Jill Biden, the wife of the then-president who appointed her. Now, what does that mean? Well, if you really think about the geopolitical implications of the 2020 Senate race between Ed Markey in Massachusetts and Joe Kennedy Jr.—well, one of the things you're going to realize is that—think about 2020. The leadership around Biden did not know that the chaos of 2024 was going to happen with Kamala and Biden not really being up to it. You're thinking ahead to 2024. Why? Who's your biggest target if you are a sitting Democrat and you're worried about a primary challenge four years from now? Well, what if JFK's—what is it—nephew or whatever it is—is in the House of Representatives? And what if JFK started his career in the House of Representatives? And what if that new young Kennedy with red hair and sort of a photogenic face? What if he is running for JFK's old Senate seat? What if he's on the same exact trajectory as JFK? Oh, we can't have that. We—as the Biden White House—cannot have Joe Kennedy Jr. beating Ed Markey for Senate. And how it got to the point that somebody talked to Rachael Rollins and she came up with the brilliant idea to reach out to Turtle Boy so that Turtle Boy would talk to Rayla Campbell to send her to Joe Kennedy Jr.'s events to help Markey—I don't know. But that's why I think Rachael Rollins became U.S. Attorney—someone who, in my opinion, was uniquely unqualified and fundamentally unethically un-predisposed to being able to run that office. Who then in turn immediately tried to interfere in the 2022 Suffolk DA primary between Kevin Hayden and Ricardo O'Rourke—because Rollins wanted to see her progressive vision continue through O'Rourke—so she worked with Daniel Medwed—the same professor who was involved with advocating the media on behalf of Karen Read's team. She worked with Daniel Medwed to get a story leaked about how a non-existent federal probe into Kevin Hayden—to increase Ricardo O'Rourke's chances in the Suffolk DA primary. Sound familiar? Oh, hell yeah. So anyway—between November of 2022 and May of 2023—you got this weird situation where Rollins knows she's getting forced out; Levy's going to take over the office. The people who take Rollins out are Josh Levy, Bill Abley, and still head of the criminal division—Dustin Chao, I think—still head of the public integrity unit, and then executive officer who is also the press secretary or the communications director of the office. Those four people—without being named; they're named by title—were the people who cooperated with the DOJ to take Rollins out—DOJ-OIG to take Rollins out. Now, why is that interesting? Well, one—because it shows that people in that office knew that Rachael Rollins had a proclivity for weaponizing leaks about non-existent federal probes to interfere in particular district attorney races and matters. Second—Rachael Rollins and Michael Morrissey had a bifurcated history of ten years. One: Rachael Rollins had this list of 25 crimes she wouldn't prosecute, and other DAs critiqued her—not just Michael Morrissey but others. Rollins—I'm pretty sure—was the one who first called Morrissey a "meatball," in fact, because of his criticism of Rollins over that issue. Rachael Rollins—I think—has a proclivity, in my opinion, to hold a bit of a grudge. When she became U.S. Attorney and she realized she was on the way out—well, maybe the Sandra Birchmore probe started back in May of 2022 because former chief of the Canton police—Ken Berkowitz—went to the FBI and told them that the FBI covered up—the MSP unit detailed to the Norfolk DA covered up Sandra Birchmore's murder—potentially because Yuri Bukhenik and John Fanning used to work in Stoughton with Matt Farwell and Robert Devine and Billy Farwell—I think they all worked there. And furthermore—that Brian Tully, the unit commander, was partners with John Fanning for 20 years. All right, and in that regard—it is very interesting, I think—that Chief Berkowitz—who may have been very offended that his unit... So Sandra Birchmore was murdered on February 1st, 2021, at 9:23 p.m. in her apartment in Canton. Okay—on February 4th, Monday in the morning—the Canton police do a wellness check after they get a call from her—Sandra's—colleagues at the school where she worked as an administrative assistant. Now the Canton police respond—on Monday, February 4th—by Wednesday, February 6th. The Canton police have collected the following evidence in order. And if you don't believe me, you can read pages—I think 97 through 101—of the Canton Police Department audit report released in April of 2025. Point by point. Number one: the Canton police confirm—via a witness who was the maintenance worker at Sandra's apartment building—that Matt Farwell was the man on camera outside Sandra's apartment in the elevator at 9:23 p.m. on February 1st—which is exactly when Sandra died. Two: that the man was Matt Farwell, and he was the same man who helped Sandra move into her apartment. Three: that when the Canton PD went to Sandra's school, they got information that Farwell was telling people that Sandra was pregnant with his child—that he had abused her since she was a child—and that he was going to quote "take care of the problem himself" if Sandra decided to carry the baby to term. All right. All of that information—by February 6th of 2021—was passed over to the MSP. John Fanning and this whole unit—I think—really then facilitate a report sometime over the next six to 12 months that exonerates Farwell and says Sandra dies from self-harm. Well, I think that's why Ken Berkowitz blew the whistle before he died of cancer—and that's why there was a grand jury impaneled in May of 2022—and it was really about the cover-up of Sandra Birchmore's murder. Well—one—it was about Sandra Birchmore's murder. Why does that make everything so interesting? Because I think that the investigation wasn't just about who killed Sandra and why—but how was it ruled a—the result of self-harm—instead of the very obvious murder that it was. Well—that starts—2022, I think—May of 2022—the grand jury. Jessica Leslie was on the grand jury—leaker—who's going to be sentenced on October 4th of 2025. I think Jessica Leslie—ladies and gentlemen—in August of 2022 somehow leaked to Karen Read—Alan Jackson—that the Norfolk DA was dirty because they covered up—and that MSP unit—because they covered up Sandra Birchmore's murder. All right—so therefore, Alan Jackson—that's the skeleton in the closet. It wasn't what the people in the house were doing. I'm still a little suspect of who they know—but I don't think that's the big deal. I don't think Jen McCabe's social life is the big deal. Nobody cares—nobody fucking cares. Sorry for cussing. The big issue is that Jen was friends with Tully. Tully's unit knew literally where the bodies were buried. And they—I think—they brought on the PI—Marty Kraft—and Kate Peter—to insulate their exposure from the coming publicity that they knew was going to be brought upon them by Alan Jackson. And so they were worried. And who would you bring in if you had covered up a murder? If you were a MSP unit—you'd bring in someone like Kate Peter. Because you can read her in on that. She's hardened. She doesn't give a fuck. She lost two of her kids—and I don't think she even fucking cared. So who the fuck's the perfect person be like: "Bruh, if that shit gets national attention, we're fucked. So you better control that fucking narrative and handle all these like different people that get too close to this—or we're going to be exposed for Birchmore." But let me bring it back to the point here—which is in 2022, the feds clearly were starting to poke around. And come 2023—I think Brian Tully's unit was desperate. Who was going to find out because of the coverage of the Read case? Could they make sure that Kate Peter got close enough to Netflix and Gretchen Voss so that they couldn't find out what was actually going on? And could the Birchmore cover-up be kept up—even in light of the national spotlight? When you think about the fact that some people may not have been loyal to the Justice for John O'Keefe movement—but were instead primarily loyal to Brian Tully's unit. And when you think about the fact that maybe Tully's unit didn't run the best investigation of Karen Read—maybe there were some flaws. But if you think about the fact that they did get her—but if you think about it in the context of: Karen knew from the jump that the MSP were dirty over Birchmore—then you understand: Karen—that's why it was going to become an incident. Everyone knew—everyone around Tully, his friends, all of them—the unit—they knew they covered up Birchmore's murder. And they knew Karen had it in her hands if she could just figure out the PR. And that's exactly what she did—to put enough pressure on them. They took her to trial anyway—and it destroyed the fucking Norfolk DA—destroyed Brian Tully's unit. It cost them dearly—and she's a tactical fucking genius. I think Brian Tully thought he was slicker than he was by using the prosecution of Aidan Kearney—not to get a genuinely—in my opinion—bad guy who was deserving of the indictment handed up by a grand jury of his peers. But because Tully wanted to know what the real target of the federal probe is. If you don't know what a backhand is, folks—a backhand is where you investigate one thing on the surface because you're dealing with a very high-level operation like the state police—who are a paramilitary intelligence-gathering operation. So you trick them. You make them think they're under investigation for John's death and the investigation of that death. But really—you're investigating them for the cover-up of Sandra Birchmore's murder. And that's exactly what I think happened to this unit. That's what I think Brian Tully was trying to figure out—from August of 2023 until about December. I think they eventually put it together—and by August of 2024, Matthew Farwell got indicted. Now—it's a question of all this as a result of today. I want to be very clear: this is what was called for. There needed to be an independent voice with power and who takes no nonsense—who came into this and said: Nope—it's out of your hands. And that's what Judge Doolin did today. Someone just needed to not either be involved with Karen Read, Aidan Kearney, or the Norfolk DA—or Kate Peter or Marty Kraft—and prosecute this. Now, all those other witnesses—I have no idea what the hell is going to happen there. But at least for Lindsey—Judge Doolin was like: enough of this nonsense. And that's why today was such a big deal in light of that historical context—because just tracing that very insidious pattern of events over the past 18 months—you can see this became a proxy war. It was Michael Morrissey on one side with his marching soldiers: Brian Tully, Kate Peter, Marty Kraft. And then it was Karen Read and the DOJ on the other side. Okay. And their soldiers were like the Free Karen Read movement and Turtle Boy and Natalie and all these other people. This was an intelligence community proxy war. And that's why I've been trying to tell people for so long: Lindsey Gaetani was not involved. She was an unwitting pawn. These two factions both took advantage of her—including Brian Tully—who was more interested in preserving his unit's reputation than actually defending the interest of the vulnerable. In my opinion, I think Brian Tully is a terrible person. Does that mean that he's a bad person for trying to hold Karen Read accountable for John O'Keefe's death? No, of course not. He's a bad person because in what fucking world do you—as a fucking state police officer—who you—you are entrusted—not just to get the bad guys—but to protect the most fucking vulnerable? One: how do you justify what happened with Sandra Birchmore? Two: how the fuck do you get it in your fucking mind that you're going to take a 15-year unredacted extraction of a fucking vulnerable victim's cell phone and release it to a fucking defendant known for promulgating exactly that material? What fucking headspace? What satanic fucking chamber do you and Kate Peter have to be drinking blood from fucking cups in to think that that's fucking okay? Fuck you. How do you even get in the headspace where doing something like that to a fucking victim becomes acceptable. The rot in that unit—whether enabled by Morrissey or whether he didn't know about it—I don't fucking know. But the point is: the rot in that unit was so deep that they lost their fucking souls. They didn't think of victims as victims. They re-victimized victims because it was a political fucking war—and these people are so hardened, I guess, that they don't understand what it means to be vulnerable. And these were police officers—detectives—people entrusted to uphold and protect the dignity of the most vulnerable—and they fucking used victims to advance some political agenda—to deal with the fact that they covered up a fucking murder. I'm done being gentle about this. Fuck these people. And I'm not saying that it was wrong for them to investigate Karen Read. I am pleased someone tried to prosecute her. I'm pissed at them because they were thinking about it from the perspective of their own liability for an unrelated case—and they fucked everything up—and introducing Kate Peter to this shit. Oh my God. It's a disgrace. It's a disgrace to the people who were hurt. It's a disgrace to the vulnerable. I frankly do not understand how Jen McCabe, Brian Tully, and Kate Peter go to bed each night. I don't get it. I don't know. Maybe there's something that shuts off the GABA-1 receptor or something and just makes you go to bed. I don't know. Never heard of such a thing. But I'm just saying: I don't know how you do it. How do you do it? But anyway—Judge Doolin—without giving a... extemporaneous, uh, bloviating cuss-based rant like I just did—instead, in my opinion, is like: fuck all of you! You're not being involved in this prosecution anymore. Someone's gonna protect this fucking woman—Lindsey Gaetani. I'm making you appoint someone! I love that man. Good for Judge Doolin. But still—we never should have gone to this point. This is incredible. With the... the... the MSP. The fact that they had a unit operating like this for so long. This is worse than what John Connolly and Whitey Bulger did. This is institutional rot that is so pervasive that it requires fundamental reform of the MSP. They're not incapable of—um, uh—solving crimes. I'm sure most of the MSP are wonderful. Anyway—my point is: I don't think the state police officers that I generally run into—or troopers—are bad people. I think most of them are wonderful. They've never been really mean to me. They do good work. They're out there protecting our roads. They stop people from speeding. They—what else do they do? They go after commercial truck violations. They investigate homicides—like, on the whole. And this is why I think we have to be careful about how we talk about this. I am not saying that the entire MSP is just rotten. I'm saying that when you have factions or sections within the institution that understand its machinations and are able to thus manipulate the bureaucratic structure and avoid accountability—you lose the confidence of everyone. And how do you think some of those good troopers feel when they have to go out there? Yes—people like me are going to smile at them and bless them and whatever—because I know they're not part of the problem. But most people look at them and they think that they're fucking hated. They don't deserve that. They literally put their lives on the line for us every day. And if we're going to give them the respect they deserve—if we're going to make the profession have the respect that it deserves—then this kind of institutional rot can't be looked at as just an embarrassment. And it can't be looked at as something that—oh, we just wish didn't happen. Maybe some guys are going to go away. No—you point at it. You scream it from the rooftops and you say: if this happens even once—then we have so failed as an institution; we must fundamentally reform from the ground up. And this wasn't just once. It was Birchmore. It was the phone extraction. It was the SA report leak over and over and over and over again. They knew the law. They were an old boys' club. They abused it. They had cover—and it was systemically enabled. And that's why I think—to save the profession of policing in Massachusetts—there needs to be a full-on unbridled discussion about how this happened—how the personalities involved were able to do what they did. And we can't be so tribalistic that because someone we support as to their views on one case, right? We cannot be so tribalistic that we just block out everything bad that they do. Or this rot will continue. And it is pernicious. It is insidious. It is invidious. It undermines the faith that citizens completely removed from this situation have in our system of government. It undermines victims' confidence in the ability to seek redress in the face of serious fucking harm—because they think the system doesn't actually care about them. It's just using them to get someone bigger. We cannot allow this to perpetuate. And the only way to fix it is to hold up situations like what happened to Birchmore—Sandra Birchmore—and what happened to Lindsey Gaetani—hold them up in the national spotlight—and say: we—the MSP—have failed you. Brian Tully failed these people. John Fanning failed these people. Nick Guarino failed these people. Yuri Bukhenik failed these people. We need to say that. We need to highlight it. We need to say: this happened even once. Therefore, we are not good enough. Not only are we not good enough—the very fact that either of these things were able to happen—the Birchmore cover-up, the phone extraction leak—is such a pervasive, systemic degradation of the faith that victims and the public have in the justice system—that our only option is to talk about this—congressional hearings. We need the State House to have congressional hearings. We need these people to answer for what they did. And we need to make sure it never happens again. And the only way you do that is by finding out what aspects of the bureaucratic structure allowed this to happen. And it's not going to be comfortable. I don't think it's going to be comfortable for anyone to talk about the fallout of any of this—but that's exactly what happened at the CCC on a smaller scale. And if this country matters—if this form of government matters—if this republic matters—then we will fix this. We will fix it together. We will address the hard questions. We will address the uncomfortable questions. We will shed our prejudices and polemical biases at the door. We will engage in no fear, no favoritism—and we will look only for the truth and nothing but it. And if you are incapable of doing that—you're contributing—either consciously or subconsciously—to the problem. It's our only option. And you can't just say: because they prosecuted Karen Read, we can't talk about anything bad that they did. That's tribalism. That's polemical. That's what drove us to this point.

Grant Smith Ellis

41,546 次观看 • 1 年前

🚨❓🛸 Breaking: What the Heck is Going On? 👽❓🚨 Senior White House Officials: We cannot find any copies of the DIA's AAWSAP records. Robert Bigelow: "We have copies of everything [from AAWSAP]." (Please spread this far and wide and tag the appropriate people. Aaron Lukas Stephen Miller Donald J. Trump BigelowPodcast Bigelow Institute for Consciousness Studies (BICS). Let's get these folks together.) ~ Ainsley Earhardt: "....is releasing new documents that might provide proof of extraterrestrial life, including decades-old, never-before-seen UFO footage." Brian Brian Kilmeade: "Really? We should have led with this." Lawrence Jones: "Right. Peter Doocy joins us live from the White House with this exclusive. Hey, Peter." (Doocy has been kicking ass with his reporting on UAP.) Peter Doocy: "Good morning. I was summoned to an office in the West Wing yesterday for a private briefing about these files that you're about to see on your screen for the first time ever. "Let's show the first clip. It was taken by a Navy aerial photographer. His name was Delbert Newhouse. It was taken along a Utah highway. If you look closely, it looks like a drone swarm, but there were no known drones in the sky when this video was taken in 1952. "I am told they took the first and only copy of this film. They found it in the National Archives. It has been digitized into 4K to be released right here for the first time today." (I watched it today. Film footage from 1952 that's turned into 4K isn't much clearer. But...the Newhouse film clip was first released in 1956, and it was stabilized and posted on YouTube in recent years and that's much better than what was released today. I'm no expert on everything historical in ufology but I'll share something on that 1952 sighting in another post that's MUCH better than what was put out today by our government.) Doocy: "The second clip we have taken by a law enforcement officer's iPhone along a busy Colorado highway three years ago. The officer's narration and some nearby buildings have been redacted. I heard the unredacted version, though, and he is describing multiple orbs hovering over a sensitive military installation for 15 minutes at a time. This one was three years ago. "And then we have a third clip taken by a drone over the Middle East last year. It shows six objects flying in formation, destination unknown. The Pentagon looks at this, they say they do not know what they are looking at on the screen. "And then there's this. There is a newly declassified copy of an expense report, a line-by-line expense report, going through the $22 million dollars that the DIA spent to investigate repeated, years-long claims over something called Skinwalker Ranch. Claims of extra...things in the sky, UFOs, UAPs." (This was AAWSAP and it wasn't focused just on Skinwalker Ranch. Not even close. Read, "Skinwalkers at the Pentagon" by Drs. James Lacatski and Colm Kelleher, and award-winning, investigative journalist, George Knapp, for an inside look at that program. And the three follow-up books, with the last two authored by Lacatski himself). Doocy: "Harry Reid, before he passed away - this was in 2008 - got $22 million dollars to investigate this. Officials now are telling me, senior White House officials are telling me, they cannot find any copy of the records. They've got all the proof that this government contractor was spending $22 million dollars to do this investigation, but when folks high up at the White House who can just pick up the phone and say, 'I need a copy of those records,' make the call, they are being told that if these records were created, they are either lost or something happened to them. "Somebody has them; they are not available to White House officials right now. Which kind of seems like one of these UFO movies where it gets to the Oval Office and the president has to be told that there are certain things that are too classified even for the president." (Those senior White House officials should contact the guy who briefed Trump in the Oval Office in February on UFOs: Robert Bigelow. Bigelow's company, BAASS (Bigelow Aerospace Advanced Space Studies), was the contractor for that program.) Here's Bigelow on Episode 2 of The Bigelow Podcast: Bigelow: "BAASS, our organization, we have the 38 papers. We have copies of everything [from AAWSAP]." George Knapp: "The DIRDs." Bigelow: "We have everything. We have all the other papers going up to about approximately 100. So, DIA has those someplace." Knapp: "But they deny it. They say, 'We don't have 'em.'" Bigelow: "Well, I don't know. They could be buried in a frigging trailer or the back of a car somewhere in the trunk and put into a cellar. I don't know where it is, but we have ours, we have copies of everything. (Problem solved. I'm sure those senior White House officials will be on a plane to Las Vegas once they see my tweet. 🙄) Bigelow: "I don't think it's our business to go around the government and divulge ours without sanction of proof, without approval. I mean, without approval. I feel uncomfortable about that. I don't mind the 38 papers (which have been public for years). I think beyond that, I'm uncomfortable by not having some kind of official, ass-covering approval, you know?" (I disagree. The American taxpayers paid for that. Release it all. They then go on the discuss how personal details of people involved would need to be scrubbed if those papers were to ever be made public. No problem with that. But Mr. Bigelow has had a decade and a half to do that. Either way, that should NOT stop Mr. Bigelow from calling his contact at the White House (or vice verse), doubling down, and saying, "I have ALL of the AAWSAP data. Come to Vegas and I'll let you see it all.") Doocy: "But, we should stress, again, officials do not know what the objects are in these videos that are gonna go wide online after this report." Kilmeade: "Now they don't know, Peter, but do you know? Doocy: "[long pause] Can't say." [All laugh. I like the comedy.] Jones: "Well played." Kilmeade: I would check a burn bag in the FBI building. Jones: "Right, exactly." Earhardt: "He used to know, he wiped the record. They just look like white dots to me. I mean, How do we know that's not a drone?" Kilmeade: "Well, it's the 50s." Earhardt: "I know, but they're just like, white dots." (Exactly. Interesting, but it will NOT move the needle with the masses. We have no idea what those white dots represent and they're not making any incredible maneuvers. But it's still coverage of UFOs on a national news show that has a lot of viewers who aren't into UFOs, like us. So, not a bad thing.) Doocy: "Well, the one clip is from a guy in 1952, and so you look at a lot of this stuff now. It's like, oh well, maybe that's a lens flare, maybe it's a hobbyist, maybe it's a weather balloon. But in 1952, there was not a lot of stuff up in the sky. And so, when you look at a video like this, yes, it is old, but it kind of creates a decades-long storyline. We know that these are things that have been a curiosity of humans on Earth for generations, and this is why. And this is a really clear clip that puts into focus - clearer focus, 4K - what some of these guys were...said that they were seeing." (Excellent summary and context by Doocy.) Earhardt: "Were you able to look through the expense report? What are some of the expenses? How'd they spend $22 million dollars?" Kilmeade: "Wow." Earhardt: "And there are no records?" Jones: "Nothing to show for it." Doocy: "I've got it. It's 59 pages long, and some of the stuff is still blocked out. But you know it's got dates. A lot of the stuff is 2008 and 2009. $2.8 million dollars, $3.6 million dollars, $2.1 million dollars. It's a well-respected government contractor (Bigelow's company, BAASS) that was doing this." (I have ChatGPT trying to find this 59-page document and so far it has struck out. We know they had 50 full time investigators over a 27-month period and they all had to be paid. Plus, they had to retrofit buildings in case they received classified UAP-related materials, allegedly from Lockheed, or elsewhere. And, in 2021, I was told the DIRDs cost $15,000 a piece or $570,000 for all 38 studies.) Doocy: "And again, it was Harry Reid out in Nevada who had an interest in UFOs because there are a lot of sightings out there. Harry Reid is the one who got the $22 million dollars of government money appropriated for this." (Kilmeade scoffs. He should know that it was the late Senators Reid (D), Inouye (D) and Stevens (R) who helped fund AAWSAP to the tune of $22 million. This shouldn't be a partisan issue.) Doocy: "Somebody went and investigated, and the files...they just can't find them. Maybe they will turn up at some point, but it is noteworthy that, given all of the interest and all the money that was spent, that somebody from the West Wing of the White House calls and they can't produce the files." Earhardt: "It disappeared." Kilmeade: "Should check [Reid's] estate. Check Harry Reid's closet." Earhardt: "Or someone's bank account (laughs)." (Or make a phone call to Mr. Bigelow. Long-distance calls are free nowadays. To insinuate that Reid pocketed any of that money is ridiculous, and partisan. Also...apparently, Bigelow spent $1 million of his own money to keep the program going towards the end.) Jones: "They think we're all stupid. The only person that knows is the dead senator, right? I mean, come on. Thanks, Peter." Earhardt: "Very interesting. All right, thank you Peter." Kilmeade: "There's an excellent chance they're gonna be friendly." (Based on what?) Earhardt: "Oh, the aliens?" Kilmeade; "And just tell us what they know. Why are they able to move so quick?"

Joe Murgia

51,957 次观看 • 4 天前