Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

(1/2) Trying to solve an unsolvable problem , which becomes progressively worse as more attempts are done trying to solve it and get better result .. Q.1 What is the problem here ? Q.2 How to solve it ? #cardiotwitter #medtwitter #PTMC #BMV Hany Ragy Nishith Chandra Ankur Phatarpekar...

20,414 Aufrufe • vor 2 Jahren •via X (Twitter)

10 Kommentare

Profilbild von Joy Sanyal,MD, DM,
Joy Sanyal,MD, DM,vor 2 Jahren

@Hragy @NishithChandra Stuck in the subvalve apparatus

Profilbild von Abad khan,MD/DM
Abad khan,MD/DMvor 2 Jahren

@Hragy @NishithChandra Yes , absolutely that was the complication which was occuring due to a PROBLEM .. but why will it not form a tug at the valvar level and form a typical dumbell ??

Profilbild von Rajesh VIJAYVERGIYA
Rajesh VIJAYVERGIYAvor 2 Jahren

@Hragy @NishithChandra How much was the MR post procedure. Balloon inflated at sub-valvular level!!

Profilbild von Abad khan,MD/DM
Abad khan,MD/DMvor 2 Jahren

@Hragy @NishithChandra Nothing sir , NO MR ..

Profilbild von Dr G Rajesh (Gopalan Nair Rajesh)
Dr G Rajesh (Gopalan Nair Rajesh)vor 2 Jahren

@Hragy @NishithChandra Was it ox balloon? Some focal bulge in proximal part before full inflation.

Profilbild von Abad khan,MD/DM
Abad khan,MD/DMvor 2 Jahren

@Hragy @NishithChandra Yes , it was ox balloon indeed sir .. and u r almost on spot .. i will post the video of the problem later and how was it solved ..

Profilbild von Ahmed Suliman, MBBS, FACP, FESC, FACC
Ahmed Suliman, MBBS, FACP, FESC, FACCvor 2 Jahren

@Hragy @NishithChandra - Make sure u r not subv - balloon appears malfunctioning - CA on the valve; is this redo and stenosis is subv -would exchange for smaller balloon

Profilbild von Abad khan,MD/DM
Abad khan,MD/DMvor 2 Jahren

@Hragy @NishithChandra I was subvalvular but it wasn't intentional, it was slipping there due to the PROBLEM it had .. I have tweeted in next video about the problem ..

Profilbild von SREEVATSA NADIG DM FSCAI FESC
SREEVATSA NADIG DM FSCAI FESCvor 2 Jahren

@Hragy @NishithChandra Stuck in SVP - avoid inflation there ; may cause acute MR

Profilbild von Abad khan,MD/DM
Abad khan,MD/DMvor 2 Jahren

@Hragy @NishithChandra Absolutely, The complication occurring is inflations keep on occuring at the subvalular level but that is not the problem , the problem is different .. See balloon

Ähnliche Videos

💡 Ready to witness the future of cardiovascular #innovation? Join Philippe Genereux as he unveils the highly anticipated results of the EARLY TAVR trial, debuting on Monday, October 28! Get an exclusive look at first-time presentations of key clinical trials and groundbreaking studies at #TCT2024! Don’t miss out—reserve your spot today: 📅 Explore the full schedule of late-breaking trials and cutting-edge science. Check it out here: #CardioX #CardioTwitter #CardioEd #CardioResearch Dan Burkhoff MD PhD David J. Cohen, MD, MSc George Dangas, MD, MACC, MSCAI Juan F. Granada Marty Leon Akiko Maehara Dr Roxana Mehran Sahil A. Parikh, MD Tricia Rawh TCT Conference jedicath աǟզǟʀ.ǟɦʍɛɖ إبراهيم الحربي Ibrahim Alharbi Abdelkader Almanfi, MD, FACC, FSCAI Hooman Bakhshi Alessandro Beneduce Nyal Borges Aaysha Cader BCaseMD Nishith Chandra Bailey Ann Richardson David L. Fischman Prof. Hector M. Garcia-Garcia Julia Grapsa Nadira Hamid Stefan Harb @AmandaLimaMD Evandro Martins F. MD Giorgio A. Medranda MD, FACC, FAHA, FSCAI Neisser M Srihari S. Naidu, MD sumonroy Michael Savage Muhammad Shuaib Abid Pooja Swamy, MD, FACC, FSCAI Ritu Thamman MD Anuradha Tunuguntla MD FACC FSCAI Poonam Velagapudi Edoardo Zancanaro MD Adriana C. Mares Niels R. Holm Abhishek Chaturvedi MD, FACC, FSCAI Krutarth Pandya Indah Sukmawati, MD Shariq Shamim MIЯVΛƬ #IC ༄ 。°
1:19

Sensitive content

💡 Ready to witness the future of cardiovascular #innovation? Join Philippe Genereux as he unveils the highly anticipated results of the EARLY TAVR trial, debuting on Monday, October 28! Get an exclusive look at first-time presentations of key clinical trials and groundbreaking studies at #TCT2024! Don’t miss out—reserve your spot today: 📅 Explore the full schedule of late-breaking trials and cutting-edge science. Check it out here: #CardioX #CardioTwitter #CardioEd #CardioResearch Dan Burkhoff MD PhD David J. Cohen, MD, MSc George Dangas, MD, MACC, MSCAI Juan F. Granada Marty Leon Akiko Maehara Dr Roxana Mehran Sahil A. Parikh, MD Tricia Rawh TCT Conference jedicath աǟզǟʀ.ǟɦʍɛɖ إبراهيم الحربي Ibrahim Alharbi Abdelkader Almanfi, MD, FACC, FSCAI Hooman Bakhshi Alessandro Beneduce Nyal Borges Aaysha Cader BCaseMD Nishith Chandra Bailey Ann Richardson David L. Fischman Prof. Hector M. Garcia-Garcia Julia Grapsa Nadira Hamid Stefan Harb @AmandaLimaMD Evandro Martins F. MD Giorgio A. Medranda MD, FACC, FAHA, FSCAI Neisser M Srihari S. Naidu, MD sumonroy Michael Savage Muhammad Shuaib Abid Pooja Swamy, MD, FACC, FSCAI Ritu Thamman MD Anuradha Tunuguntla MD FACC FSCAI Poonam Velagapudi Edoardo Zancanaro MD Adriana C. Mares Niels R. Holm Abhishek Chaturvedi MD, FACC, FSCAI Krutarth Pandya Indah Sukmawati, MD Shariq Shamim MIЯVΛƬ #IC ༄ 。°

Cardiovascular Research Foundation

16,807 Aufrufe • vor 1 Jahr

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

Yasmine Khosrowshahi

34,166 Aufrufe • vor 2 Monaten

The secret recordings: Texas Tech's senior official admits that they lied about me in the official documentation leading up to my medical school dismissal For months after I began writing about how wrong the medical and scientific communities had gotten the COVID-19 response, senior Texas Tech administrators had been engaged in a flurry of internal activity about my public speech. They did not debate my views. They only discussed what to do about the attention. My right to free speech is protected under the United States Constitution. Texas Tech is a taxpayer-funded agency that must guarantee its students First Amendment rights. Its Student Handbook promises to uphold them. Senior administrators, including deans of multiple schools, held several meetings about what I wrote online. They instructed administrators to compile surveillance dossiers -- screenshots, PDFs of my articles and tweets, negative emails and hearsay. They instructed faculty not to say good things about me. They assigned me a "professionalism coach," Cheryl Erwin, who posed as an impartial advisor but privately wrote that I engaged in "intellectual narcissism" and believed in "conspiracy theories." In one passage, she compared my case to the Trump indictment and his denial of the 2020 election results. She wrote that I was exercising my First Amendment rights to "make an idiot of himself." I questioned the wisdom of lockdowns and the effectiveness of masks. This warranted, it appears, my very own Stasi dossier. I was aware of none of this until I exercised my statutory right to inspect my educational records. After dozens of email exchanges, months of delay, and a federal complaint to the Department of Education, I was finally able to inspect them two months ago. Dr. Erwin had accused me of believing in conspiracy theories. I did not. But I should have. Shortly after the dean of the medical school demanded my signed Honor Code and asked "what rotation is he on," I began receiving evaluations from Texas Tech faculty that were false and misleading. This went on for months. Something on the order of fifty discrete complaints were made against me. Prior to that, the number had been zero. I filed seven detailed complaints according to the Student Handbook and under the guidance of several administrators. I alleged that my evaluators had fabricated evaluations. I demanded hearings to hold them accountable. On November 4, 2023, senior administrator Simon Williams signed a document removing me from campus on the pretext of being dangerous. A BOLO was issued telling students, faculty, and employees to call 911 if I was seen. Mass emails warned that I was dangerous. An incident that continues to be cited to this very day, more than two years later. On November 5, Dr. Williams invited me to a sandwich shop. He confessed that he knew I was not dangerous. He admitted that Texas Tech faculty and administrators felt threatened by my complaints -- and took it out on me. In other words, Dr. Williams confessed that he lied in Texas Tech's official documentation and that the campus removal was retaliation for constitutionally protected speech alleging wrongdoing by Texas Tech faculty. Here are just some of the things he told me: "This profession expects more of everyone. And if you choose to enter it, by definition you choose to live by those professional rules." "And you know, free speech is free speech. We've actually had a lot of talks. Our lawyers are doing works with us. Just yesterday when I was at the meeting, they were talking about free speech. I mean I'm 100%. I want you to be able to say whatever the frick you want. And I won't get -- I usually will not get in any way triggered by it. But when you're in a position that's such a trusted position in society -- then your standard has to be a little bit. And that's one of the places this is becoming a problem." [Timestamp: 00:34:48] "Can I say in my appeal letter that Dr. Williams seems to believe that I'm not [nervous laughter] homicidal?" "I... I have said that. I don't think you are. I don't think there's -- I've never sensed threat or danger or anything like that." [Timestamp: 00:34:48] "But it's important for me that I do this. In fact, that's why I moved back from Seattle a day early. Because I needed to be here today. I want you to know that because I never felt [inaudible] bad here. I've always enjoyed my interactions with you. I wish other people could see it that way, but apparently that's [inaudible]." [Timestamp: 00:34:48] Yet in his letter authorizing my removal just the day before, he wrote: "You have engaged in behavior that may constitute violation(s) ... specifically, but not limited to ... 'Physical harm or threat of harm to any person.'" Then an appeal hearing was held. A Schrodinger's Administrator of sorts, just as soon as Dr. Williams was observed to speak publicly, he immediately asserted that I was indeed dangerous and should be kept off campus, flip-flopping back from the position he communicated privately. The timeline: November 4: "Physical harm or threat of harm to any person" November 5: "I've never sensed threat or danger or anything like that" November 9: Kevin is dangerous actually To be clear. Under 18 U.S.C. § 242, it is a federal crime to willfully deprive a person of constitutional rights under color of law. A federal crime. And that is exactly what Dr. Williams did. Dr. Williams's decision to remove me was not impulsive. Nine months earlier, two days after my Newsweek article was published, he wrote in internal emails: "It is obviously protected speech but also quite concerning in the way he appears to speak for the medical community. We need to discuss an appropriate response." -- February 1, 2023 "I am not surprised that there was backlash. I think it will be best to hear what legal says we should do." -- February 2, 2023 The "appropriate response" took nine months to execute. It was relentless, and it came from all directions. This "appropriate response" was precisely the one I filed grievances to confront. And I was met with calls from the campus police. I am not the first one Texas Tech has done this to. How do I know? An administrator told me. At least one other student had false allegations leveled against him because the administration wanted them gone. And if they win, I won't be the last they do this to either. I only discovered these emails because I exercised my right under FERPA to inspect my educational records. Now Texas Tech's litigation counsel, Assistant Attorney General Scott Smith, has recently blocked all further access to my records -- in writing. If Texas Tech does not fulfill its FERPA obligations, it could lose all federal funding. Texas Tech, apparently, is getting very nervous. Smith also ordered me to stop contacting the Registrar and to route all requests through him. That's right. The attorney defending Texas Tech against my lawsuit is now trying to establish gatekeeping control over my education records. That's illegal. A federal complaint is pending with the Department of Education and other federal agencies. FIRE Greg Lukianoff -- crickets DOJ Civil Rights Division -- you have my complaint Attorney General Ken Paxton @OAGTexas -- your AAG is doing a terrible job; borderline sanctionable; I don't get it Greg Abbott -- this your university Texas Tech University -- Williams was not the top of the decision tree; I know that for a fact Newsweek -- help me publish my story @ACLUofTexas -- do you know about this? Department of Justice (DOJ) Harmeet K. Dhillon Pam Bondi -- theoretically, this is prosecutable under 18 U.S.C. § 242. I'm not a prosecutor, but it does theoretically fulfill the elements. Willful. Chancellor Brandon Creighton -- you are the chancellor. Do something. My case is a strange one. It gets stranger everyday. It will get stranger still. Of that I am sure. Here's something strange: the defending Assistant Attorney General and two colleagues are getting hammered on the docket by a pro se plaintiff. They seem utterly incapable of following court rules, making coherent arguments, or even properly citing their own exhibits or authorities. I suspect that they just don't know what to do with my case. In the next post, I will begin telling that story. You won't believe it. Texans, your government is setting your taxpayer money on fire to defend a university that set out not just to destroy a medical student's career, but his personal and professional reputation as well. Remember. They destroyed me because I was damn good at what I did. Now I'm an order of magnitude better. And I don't bluff. Horror and laughter. Those come next.

Kevin Bass

45,536 Aufrufe • vor 3 Monaten

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

Himanshu Kumar

85,668 Aufrufe • vor 2 Monaten

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

Himanshu Kumar

101,105 Aufrufe • vor 3 Monaten

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

36,552 Aufrufe • vor 9 Monaten

The World Is Not Linear: A Field Guide to the Laws That Quietly Run Everything Most smart people don’t fail because they’re dumb. They fail because they apply clean logic to a messy world — and the world punishes that mistake with a smile. The messy truth is that modern life is shaped less by individual intent and more by systems: incentives, competition, scaling effects, path dependence, and statistical weirdness. These systems produce outcomes that feel unfair or mysterious until you learn the underlying “laws” — a set of lenses that let you predict how things actually behave. This is not about becoming cynical. It’s about becoming accurate. Once you internalize these lenses, you start noticing that most disagreements aren’t about values. They’re about which hidden force you think dominates: Do incentives matter more than morals? Do networks scale value more than craftsmanship? Do rare events matter more than averages? Do systems evolve, or can they be designed? This article is a guided map through those forces — told as one story. 1) The seduction of “doing the obvious thing” Imagine you’re in charge of improving something important: a company, a city, a hospital, a school, a product, maybe even your own life. You do what responsible people do: you define a goal. You pick a metric. And you tell everyone: we’re going to win on this number. This is where the first trap snaps shut. Goodhart’s Law: the metric stops being real When a measure becomes a target, it stops being a good measure. Before it became a target, the metric was an instrument: a thermometer. After it becomes a target, it becomes a game. Hospitals improve “wait times” by changing intake rules. Companies improve “engagement” by nudging addiction. Schools improve test scores by teaching to the test. Police departments improve crime stats by changing what counts as a crime. Not because anyone is evil. Because the system rewards it. The principal–agent problem: the doers don’t pay This is the deeper engine under Goodhart. The person deciding is not the person suffering the consequences. Executives chase quarterly optics; employees deal with the chaos. Politicians chase election cycles; citizens live with the long-term effects. Managers chase easy metrics; customers absorb the frustration. Once you see principal–agent problems, you start seeing why seemingly intelligent organizations keep doing self-destructive things: the incentives are miswired. The Cobra Effect: perverse incentives grow cobras Sometimes this miswiring gets darkly funny. Reward outcomes and people will manufacture the appearance of outcomes. In the original parable, a colonial government offered a bounty for dead cobras — and people began breeding cobras. This isn’t historical trivia; it’s a universal pattern: Reward bug counts → people file junk bugs. Reward convictions → plea bargains + overcharging. Reward content volume → SEO sludge. Reward “delivery” → rushed work + tech debt. The world is full of cobra farms. 2) Why fixing things often makes them worse Okay, so: choose better metrics, align incentives, done. Not quite. Because even well-intentioned fixes trigger the next law: second-order effects. Chesterton’s Fence: don’t remove constraints you don’t understand You walk into an old system and see “stupid rules.” You want to clean house. You want to simplify. But: why is that rule there? Don’t remove a fence until you know why it was built. A lot of institutional weirdness is scar tissue from past disasters. The rule might be dumb — but if you don’t understand it, you don’t know what disaster you’re re-inviting. This is why naive reformers are dangerous: they confuse “not understanding a thing” with “the thing being pointless.” Gall’s Law: complex systems must grow from simple working ones Even if the fence is removable, you still hit the next problem: A complex system that works is always evolved from a simple system that worked. This demolishes a common fantasy: that you can design complexity from scratch. Most large redesigns fail for one reason: They try to create a finished organism instead of growing a living embryo. If the system matters, you don’t “implement” the final form. You build something simpler that works. Then you iterate. Gall’s law is harsh, but kind: it explains why so many ambitious “transformations” flame out. 3) Efficiency doesn’t save you (and sometimes consumes you) Now suppose you do manage to improve a system. You make it cheaper, faster, more efficient. Surely this reduces resource usage? Often, no. Jevons Paradox: efficiency increases total consumption When you make something more efficient, you often make people use more of it. Make lighting cheaper → people illuminate more spaces. Make driving more fuel-efficient → people drive farther. Make computing cheaper → people compute vastly more. Efficiency doesn’t always shrink the pie. It can expand it. This is one of the most important and least emotionally intuitive truths about progress: efficiency changes behavior. 4) Some things don’t get more efficient — and get expensive forever Now meet the mirror image of Jevons: not everything can get dramatically more productive. Some work is bottlenecked by time, humans, and attention. Baumol’s Cost Disease: sectors that don’t scale inflate A string quartet takes as long to play Beethoven as it did 200 years ago. A therapist can’t 10× their clients without breaking the thing. A teacher can’t “scale” classroom attention the way software scales distribution. Meanwhile, other industries do scale — manufacturing, computing, logistics. So as society grows richer, productivity sectors get cheaper and cheaper… and human-time sectors get relatively more expensive. That’s why: healthcare education legal services childcare eldercare …feel like they eat the world. Baumol isn’t “a problem to solve” so much as a physics constraint: certain value comes from human presence. And presence doesn’t compress easily. 5) The invisible accelerant: networks At this point you might feel like everything is doom and friction. It’s not. Some forces make systems wildly better as they grow. The biggest one is networks. Metcalfe’s Law: value scales with connections A phone is useless alone. A fax machine is useless alone. A social app is useless without other humans. As users increase, connections increase faster than users do. That creates accelerating value. Reed’s Law: groups scale even faster than connections But it’s not just one-to-one links. Once people can form groups — communities, coalitions, companies, subcultures — the number of potential groupings explodes. That’s Reed’s law: group-forming networks can scale with frightening speed. This is why networked platforms can go from “niche” to “dominant” almost overnight: the product isn’t just features — it’s the social graph. 6) Progress has a heartbeat: learning curves Not all progress comes from networks. Some comes from repetition. Wright’s Law: cost falls with cumulative production This is the law behind why solar, batteries, and manufacturing tech get cheaper and cheaper: Every doubling of cumulative production yields a predictable cost reduction. The implications are enormous: the future is shaped by what we manufacture at scale volume is not just output; it’s learning building the thing teaches you to build the thing better Strategy through Wright’s law becomes: maximize learning rate. Not “be brilliant,” but “iterate relentlessly.” 7) Cooperation is rare — and competition forces ugliness Now we move from economics into game theory and moral physics. Even with good metrics, good redesign, good scaling… Sometimes the system makes people do bad things. Prisoner’s Dilemma: defecting is rational If you and I cooperate, we both win. But if I suspect you might defect, I should defect first. So we both defect. We both lose. This structure appears everywhere: labor vs management nations vs nations companies vs companies roommates siblings Twitter discourse It’s tragedy-by-incentives. Moloch: the god of coordination failure “Moloch” is the poetic version of the same idea: systems where competition forces everyone into worse behavior, even if nobody wants it. No one wants the attention economy. But creators compete for attention. Platforms compete for engagement. So everyone converges on outrage and addiction. Moloch doesn’t need villains. It only needs incentives. 8) The biggest mistake smart people make: believing in averages Now we arrive at the statistical heart of why forecasts fail. Most planning assumes the world behaves like a bell curve: most outcomes are near the average, extremes are rare. In many domains, that’s false. Fat tails: extremes happen way more than you think In fat-tailed worlds, the “average” is a comforting lie. Outliers dominate: venture returns blockbuster movies bestselling authors company outcomes war and peace pandemics market crashes In a fat-tailed world: one event can erase ten years of progress or create it overnight Black swans: surprise + impact + fake hindsight A black swan isn’t just an outlier. It’s an outlier we didn’t know how to model. The signature of black swans is: huge impact surprise beforehand “it was obvious” afterward We are story machines. We can rationalize anything after it happens. Survivorship bias: you’re studying the winners This is why business advice is mostly nonsense. We read biographies of billionaires and imitate their habits — forgetting the cemetery of equally hardworking, equally smart people who lost. Survivorship bias turns randomness into “wisdom.” A good thinker always asks: what am I not seeing because it died? 9) The final set of tools: tradeoffs, simplicity, and time After you’ve internalized incentives, scaling, networks, and tail risk, you earn the right to something important: Less ideology. More judgment. That’s what these last lenses provide. Pareto efficiency: every improvement has a cost At some point, you stop making “free” gains and enter a world of tradeoffs. If you want more of A, you give up B. This is what breaks utopian thinking: more safety can mean less liberty more speed can mean less quality more fairness can mean less efficiency more growth can mean more inequality Smart people aren’t the ones who avoid tradeoffs. They’re the ones who name the tradeoff out loud. Occam’s Razor: don’t add gears without proof Now that you’re thinking in systems, you could easily overcomplicate. Occam is your brake pedal: prefer the simplest explanation that predicts. It’s not “simplicity is truth.” It’s: don’t hallucinate complexity. Lindy: time is the best filter we have In fragile worlds, “new” is often a synonym for “untested.” The Lindy effect says: the longer something has survived, the longer it’s likely to survive. Ideas, books, institutions, even practices: time is a stress test. Lindy isn’t anti-innovation. It’s pro-robustness. Comparative advantage: specialization beats self-reliance Finally, comparative advantage gives you the social version of Occam. Even if you’re worse at everything than someone else… trade can still make both better off, because efficiency comes from relative differences. That lens dissolves a lot of macho self-sufficiency myths. So what does this worldview do? It does three things. First: it replaces naive optimism with durable optimism Not “everything will work out.” But: we can build systems that don’t collapse under their own incentives. Second: it changes what you fear Not competitors. Not critics. Not even failure. You start fearing: bad metrics misaligned incentives brittle complexity tail risks coordination failure Which are the real predators. Third: it gives you a usable strategy A decision-making style that looks like this: Start simple (Gall) Measure carefully (Goodhart) Align incentives (principal–agent) Expect adaptation (cobra effect) Respect old constraints (Chesterton) Model scaling honestly (Metcalfe/Reed/Wright) Don’t assume efficiency saves you (Jevons/Baumol) Prepare for tails (fat tails / black swans) Don’t trust winner stories (survivorship bias) Name tradeoffs and keep models simple (Pareto + Occam + Lindy) That list is more than theory. It’s a survival kit for reality. Closing: the meta-law If I had to compress this entire worldview into one sentence, it would be: Outcomes come from incentives and scaling under uncertainty—not from intentions and plans. Most people live inside stories. This toolkit makes you live inside systems. And once you do, you become harder to fool — including by yourself.

Carlos E. Perez

102,951 Aufrufe • vor 6 Monaten

An interview by VERY DARK AND CORRUPT Wall Street Journal aired today [1] WSJ's terrible "journalists" (and I use that term lightly) made many false statements about Sarepta's worthless, dangerous drug and Vinay Prasad's firing [1,2] I explain how the FDA sausage is made in excruciating detail Buckle up To get readers up to speed -> In June, corrupt pharma company Sarepta Therapeutics paid $40,000 to lobbying group Michael Best Strategies (MBS) to deal with a problem [3] -> MBS had recently hired Chris LaCivita, who had close connections with "MAGA" influencer Laura Loomer [4] -> With stock down 88%, Sarepta needed to sell their very bad, very dangerous drug or the company would go bankrupt [5] -> After several deaths from the drug this year, FDA official Vinay Prasad said "no way" and kicked the drug to the curb [2,6] -> Sarepta panicked and paid MBS (we believe) to deal with Prasad [3,4] -> If this story is right, LaCivita recruited Laura Loomer to take down Prasad [4,7] -> Loomer said she was defending Trump, but she was lying [7] -> She was defending taxpayer-funded payouts to a worthless, corrupt company [7] -> Laura Loomer so brave A history of bad drugs and regulatory failure -> This is one of the worst pharma scandals in American history and corrupt mainstream media isn't covering it -> Sarepta has a very long, troubled history [8] -> For more than a decade, every major Sarepta FDA drug approval has required INTENSE political intervention [8,9] -> Scientists at FDA have been repeatedly overruled [8,9] -> Many scientists have resigned, very publicly, over these POLITICAL decisions, some writing scathing public criticisms of these terrible decisions [10,11] -> The most recent resignation by Vinay Prasad is not something new; it follows in a long tradition [2,10] -> In fact, standards have dramatically deteriorated since the first controversies about the company's drugs in the 2010s [8,9] -> Prasad was trying to hold the line in the face of rapidly deteriorating standards at the agency [2,6] -> For that, pharma launched a coup--a literal coup of a drug regulator [4,6] -> This is unprecedented -> Banana republic sht, unbelievably corrupt 2016: first Sarepta drug approval and the "highly unusual" decision -> The first Sarepta drug approved by FDA was called Exondys 51 [8] -> This drug was for patients with mutations in dystrophin, a muscle protein [8] -> This is a debilitating and fatal disease affecting children [8] -> Exondys 51 increased dystrophin by 0.2% of normal levels [8,12] -> Unsurprisingly, there was no good evidence the drug worked [8,12] -> Why would it? It increases the protein from zero to 1/500th of normal levels -> One reviewer wrote: "I can find no precedent of an accelerated approval for a marketing application where the effect size on the surrogate endpoint is as small as 0.3%." [12] -> The study submitted by the company included no proper control group [12] -> The techniques used were so bad not even a first-year PhD student would do a study that way -> This the level of work you would expect from a mediocre undergraduate with no guidance -> It's almost like it was so bad on purpose -> (Narrator: it was on purpose) -> Nerd time: -> One reviewer wrote: "The Western blots submitted by the applicant for Study 201 were oversaturated, unreliable, and uninterpretable." [12] -> Another wrote: "Because CDER also determined that the conditions under which the original IHC analysis was performed were inadequate, including that the reader was not masked to sequence and time, the Center requested a re-reading of the stored images by three masked pathologists under different conditions. The IHC results from the reread were not nearly as favorable, as compared to the initial IHC results reported by Sarepta." [12] -> "The lack of concordance between the IHC and the Western Blot results is 'striking'" [12] -> "Study 201/202 had fundamental flaws, including baseline biopsies from external controls who could differ in unknown ways from study subjects, Week 180 biopsies from different muscles than baseline, and potential protein degradation in stored baseline samples." [12] -> And on and on. -> FDA commissioner Robert Califf wrote at the time: the submitted study was "characterized by major flaws in the clinical study design" and "Blinded experts assembled by the FDA fundamentally debunked this study, which has yet to be retracted and continues to be cited" [9,12] -> That's right, the FDA commissioner expressed dismay that the study that the company used to gain approval hadn't yet been retracted, it was so bad [9] -> Senior FDA official Janet Woodcock decided to approve before scientific review team had even voted [9,12] -> Woodcock be like: yeah i'm going to decide before you guys can because i know what you're going to say lol -> Despite external intense pressure, FDA scientists voted against Exondys 51's efficacy [9,12] -> They then voted against its accelerated approval [9,12] -> The review team filed an appeal with FDA commissioner after "passionate" disagreement with Woodcock [9,12] -> One reviewer called Woodcock's decision "unprecedented" [12] -> In a 126-page report, FDA commissioner Califf called Woodcock's decision "highly unusual" [9] -> The FDA board wrote: "[Woodcock's] involvement here appears to have upended the typical review and decision-making process. ... Care should be taken to avoid the appearance of interfering with the integrity of scientific reviews at the lower levels of a Center." [9] -> Again, the data were unbelievably bad, literally every technique in the study was inappropriately used [12] -> I would fire an undergraduate student who did science like this, immediately -> FDA's chief scientist accused Sarepta of "serious irresponsibility" for selectively publishing only some of the data [9] -> Even Woodcock, who approved the drug, called the research "seriously deficient" [12] -> Yes, even the person who approved the drug over the heads of FDA's scientists said the research was horrible [12] -> Still, FDA tried to bury their heads in the sand and beg that, basically, Sarepta pretty please do a better job next time -> FDA commissioner: "The utmost attention should be paid to optimizing the methodological rigor of [future] trial[s]" [9] -> FDA also demanded a clinical trial "to verify the benefit" of the drug [8] -> Welp, this was in 2016 [8] -> The trial results are supposed to be available in 2026, maybe [13] -> Or maybe later, depending on how much money needs to be made first -> As an article published in Nature three years later despaired of the decision: "The approval was conditional on the company agreeing to conduct a two-year post-approval trial to show Exondys 51’s efficacy. But by August 2019, the company had yet to begin such a trial and in the meantime had profited from sales of $300 million in 2018." [13] -> If it sounds like Sarepta used political pressure to get its drug approved and then tried to avoid actually publishing the study showing it didn't work, it sounds that way because that's exactly what happened [13] -> FDA commissioner after deferring to Woodcock: "I am confident this unique situation will not set a general precedent for drug approvals under the accelerated approval pathway, as the statute and regulations are clear each situation must be evaluated on its own merits based on the totality of data and information." [9] -> This statement was profoundly naive, and the historical record bears this out [8,14] -> Three FDA scientists resigned, including the lead reviewer of the drug, understanding the grave implications of the collapse of scientific standards and where they would lead [10,11] -> One was John K. Jenkins, M.D. Director, Office of New Drugs Center for Drug Evaluation and Research/FDA [10] -> In a presentation given just before his resignation, he wrote: -> "Path taken by Sarepta NOT a good model for other development programs" [10] -> Crucially: -> "Upholding statutory standards for approval in face of hopes and desires of patients, families, sponsors, and investors is a very difficult job" [10] -> "Personal attacks on FDA reviewers creates an atmosphere of distrust and isolation rather than collaboration" [10] This brings us to WHY Sarepta's drug was approved Facebook FDA -> So why did the drug get approved? -> Basically, Sarepta propagandized extremely desperate patients [9,15] -> They used miraculous snake oil promises and patients believed them -> Remember that this is life or death for patients, and they are extremely vulnerable -> Sarepta also professionally trained some patients to give testimonials to FDA and congress [15] -> The patients then went to congressmen who don't have time to understand the science [15] -> They gave emotional stories to congressmen [15] -> The result: -> Letter from 109 House members [15] -> Letter from 24 Senate members [15] -> And a media circus documented in the New York Times [16] -> Patients screaming at scientists during meetings [9] -> 2,792 emails written to FDA urging approval [12] -> One of them: "Dear Dr. califf: How is it that everyone in and around DMD understands this simple Idea and the science geniuses at FDA don't? You stupid fckers are costing each and every DMD kids days of their lives with your Moronic Dystrophin dance. Time to get a fcking clue" [12] -> Upon approval, a journalist for Reuters wrote: "owing to pressure from patient advocates, the U.S. Food and Drug Administration on Monday approved a treatment for Duchenne muscular dystrophy even though an outside panel of experts and the agency's own reviewers questioned the drug's efficacy" [17] -> A commentary in Nature Medicine was also published called "Railroading at the FDA" [9] -> Its author wrote: "In the words of one FDA committee member, Exondys lowers the agency's evidentiary standard for drug effectiveness 'to an unprecedented nadir.'" [9] -> A highly critical commentary was also published in Science, titled "Sarepta gets an approval - Unfortunately" [18] -> The article's author pharma veteran Derek Lowe wrote: "The company... called up Duchenne-affected boys and their families to plead with the FDA, and won over Janet Woodcock, and that appears to be enough. Is this going to be the new way to get a drug approved? Run a trial in a dozen people, generate unconvincing data, and then lobby Janet Woodcock? I share the worries that this might open the floodgates, because after all, Sarepta got their drug through." [18] -> One FDA reviewer ended in an equally grim note: ". Approval of this NDA would send the signal that political pressure and even intimidation – not science – guides FDA decisions, with extremely negative consequences. The public is well aware of this development program: the meager size of the study population, the marginal (at best) effect size, the Division’s dim view of the efficacy data, and the robust activism of some members of the DMD community. Many would be amazed at an approval action, because other DMD drugs, recently turned down for approval, appeared to provide stronger evidence of efficacy. ...The ramifications here are profound. The public will perceive that it was their unprecedented lobbying efforts that made the difference and earned eteplirsen its accelerated approval. For the future, this will have the effect of strongly encouraging public activism and intimidation as a substitute for data, which is one of the worst possible consequences for communities with rare diseases. This type of activism is not what was envisioned for patient-focused drug development." [12] -> A new era was born -> Activism had replaced data -> Facebook had fried people's brains -> And now Facebook-fried brains had fried FDA too -> FDA's credibility as a regulatory agency would now be hollowed out -> FDA's Facebook age had begun -> But the worst was yet to come Sarepta approvals: 2016 to present -> Three more drugs were approved from Sarepta on the same shoddy basis, proving Califf's promises that Exondys 51 was an isolated case empty [8,14] -> But things would take a turn for the worse with Sarepta's newest drug Elevidys in 2024 [19] -> At last a rigorous clinical trial looking at actual clinical outcomes was published [19,20] -> All would be put to rest -> At long last the issue could be resolved with HARD CLINICAL DATA -> There was only one problem -> The trial failed to show any benefit according to the primary outcome [19,20] -> The surrogate biomarker of micro-dystrophin meant absolutely nothing; it wasn't actually helping patients [19,20] -> What did FDA scientists do? They voted against approval. Of course [19] -> How could they not? The drug didn't actually work in the clinical trial [19] -> It's the only thing that made sense, since FDA is a scientific agency -> AND THEY WERE OVERRULED AGAIN BY PETER MARKS [19] -> YES THAT'S RIGHT, OVERRULED YET AGAIN -> PHARMA WINS AGAIN -> HAHAHAHAHAHA PHARMA ALWAYS WINS YOU FOOLS -> What happened is that Marks crossed his eyes somewhat, trying to make the words on the page blurry -> He prayed really hard, "my god please give me a sign, something, anything, I need this for my career" -> lzzosolsolzzolzozlslzolosllslozllzlzl -> Marks was trying really hard to see SOMETHING, come on come on, give me SOMETHIGN he said -> And he said: wait, look, there are these secondary, exploratory endpoints and a two of them look pretty good, I'LL APPROVE [19,20] -> AHAHAHHAHAHA YES PHAMRA WINS AGAIN -> And Marks said, "Thank you pharma go- I mean god, not pharma god, why did I just say that, FCK" -> The trial was explicitly designed for what Marks did NOT to happen [20] -> Once the primary endpoint was not met, the secondary endpoints couldn't even be statistically tested [20] -> And the trial explicitly said that they could not be interpreted the way Marks interpreted them [20] -> They were not adjusted for multiplicity and they were, like expression of dystrophin, simply bad endpoints [20] -> These two secondary endpoints were time to rise from lying on the floor and the 10-meter walk/run tests [20] -> Subjects who received the Elevidys performed, on average, about 0.5 seconds better than placebo recipients on these tasks [20] -> However several facts must be borne in mind when interpreting these: -> 1. At the time of testing, patients receiving the drug were receiving more corticosteroids than placebo patients, biasing the results [20] -> 2. Blinding might have been broken because those receiving the drug experienced lots of nausea and vomiting from the drug (~70%) [20] -> 3. These differences were tiny and may be attributable to chance, since the natural course of the disease varies widely [20] -> Marks knows this but who cares? Pharma I mean Facebook needed to be placated Elevidys: the drug -> To understand why this is so messed up, one must understand a few things -> On a Bayesian basis, one must assume that Elevidys is harmful until proven otherwise, for two reasons: -> 1. All drugs are potentially "toxic", but some toxins heal: by default you must assume it is a toxin that does not heal because this is what is actually usually the case; you need evidence that it actually heals -> 2. Elevidys IN PARTICULAR must be assumed to be harmful until proven otherwise because of the very nature of the drug -> Let's do a breakdown of the basic science of Elevidys that supports this (Bayesian) hypothesis: -> Gene therapy that permanently integrates into human genome [21] -> Meant to replace dystrophin, the protein that these patients cannot produce themselves [21] -> Preferentially targets muscle but gets expressed everywhere [21] -> Killed three people this year [6,21] -> Costs $3.2 million per injection [21] -> Truncated version of the protein it is supposed to replace [21] -> 3X shorter than the real protein [21] -> Has to be truncated because the technology cannot create the full protein [21] -> Because it's an abnormal protein, it's foreign, so immune system attacks it [21] -> Patients injected with drug are basically given an autoimmune disease [21] -> Patients have to be given anti-inflammatories to fight the disease that the drug causes [21] -> Causes terrible muscle inflammation [21] -> Inflames the heart, heart walls thicken because of the inflammation [21] -> Blows up the liver, causes acute liver injury and death [21] Drug should actually be assumed harmful, not beneficial -> Given all of the above, since the drug failed to meet its primary endpoint, it should actually be considered harmful by default, not beneficial [19,20] -> In other words, what we would actually expect if we added more patients and did an even larger study... -> Is that the drug would do worse than placebo, i.e., patients taking the drug would do worse than those taking placebo -> Why isn't this the default interpretation? -> They are reading the study with an intervention bias -> An intervention bias is natural, which is why "do no harm" is such a central tenet of medicine -> If I may put forward a thesis: most of Vinay Prasad's 500+-paper body of work has been dedicated to demonstrating the "do no harm" principle empirically [22] -> Rose-colored glasses study interpreters are simply not applying this principle properly and are thus failing scientifically in the most fundamental way -> Incomprehensible -> Back in 2016, scientists were adamant that the approval of Sarepta's first drug indicated the profound deterioration of scientific standards [8,9] -> But this latest approval is even worse: actual clinical data is now being overruled -> No standards at all are being enforced anymore; anything can now be approved based on any evidence whatsoever -> What Vinay was trying to do was simply to stop the unrelenting downslide -> And his firing punctuated that downslide for what it was The WSJ segment -> When Elevidys was approved, former FDA chief scientist and one of the original reviewers of Sarepta's first drug Luciana Borio said: -> "I don’t know what to say. Peter Marks makes a mockery of scientific reasoning and approval standards that have served patients well over decades. This type of action also promotes the growing mistrust in scientific institutions like the FDA." [23] -> To return to this video, these two WSJ reporters show an incredible level of ignorance and arrogance -> Finley says that the drug is "clearly" beneficial by misreading the secondary endpoints, just like Marks did -> An FDA memo from last year says about these endpoints: "Under these circumstances, they are misleading and cannot guide any stakeholders—including patients, family members and caregivers, and prescribers—in making informed decisions about the potential benefit of treatment with ELEVIDYS." [20] -> It really doesn't get any clearer than that -> But these two journalists are overruling the actual scientists, just like Marks did -> One of the most incredible comments during this interview was the complaint that "90% of clinical trials fail", as if that's bad thing [1] -> It's actually a good thing; most drugs suck; failing in clinical trial actually allows us to use only the drugs that don't suck -> These people don't understand the most fundamental purpose of the clinical trial -> They think clinical trials failing is a bad thing, as if it means that patients now won't get to use a useful drug -> No, it's a good thing, because it means that patients won't be exposed unnecessarily to a useless drug that might harm them -> The level of ignorance really is unbelievable -> What's worse is that these "journalists" defend their decision -> But what they did is exploit social media hysteria caused by Laura Loomer [1,7] -> Following up on her heels with editorials, using her as pharma attack dog [1,4] -> This is a huge blow to WSJ's credibility, and they know it -> Unbelievably shameful Where do we go from here? -> The Vinay Prasad firing creates a serious crisis of credibility at FDA [2,6] -> Up to this point, we could call these approvals a difference of opinion, but as we've seen, that's a huge stretch -> But any illusion of that is now shattered: the firing shows that drug regulation is explicitly political -> Janet Woodcock: approve, keep job -> Peter Marks: approve, keep job -> Vinay Prasad: block, transparently fired -> Make a decision that is anti-pharma and lose your job: that's the message -> Who can trust any decision at FDA anymore? -> RFK Jr. and Marty Makary both stand behind Vinay Prasad [24] -> Trump went along with lockdowns, he went along with mask mandates, he went along with all of the Covid pseudoscience that he now decries -> He should reverse course and not go along with this -> Trump has created a profound crisis of credibility at FDA and needs to fix it

Kevin Bass

80,314 Aufrufe • vor 11 Monaten

💥 LAP Alert 💥 "I did this sort of spy thing where I changed hotel rooms and I changed taxis. I was making sure I wasn’t followed." ~Knapp Is Lacatski Lying to Us About the Craft and Breaching the Hull? ~ "If not for that [2017 NYT] story about AATIP and the problems that [Lacatski] saw with it, he would never have mentioned [AAWSAP]...I don't think, ever." ~Knapp (So, in other words...thank you from the UFO community, to the NYT, for getting it wrong? 🙂) ~ Jeremy Kenyon Lockyer Corbell: "Should we listen to Dr. James Lacatski on UFOs, on the fact, or the idea, that our government has at least one, he's admitted, and we breached the hull? Should we listen to him, George?" George Knapp: "I know a lot of people have noticed that he's talked about his role in counterintelligence as part of the AAWSAP program. And because they equate counterintelligence with lies, false info., cover stories, misdirection. Aha! He's putting out a bunch of false info. a decade after he retired from government service." (I saw one person suggest that, and I thought it was a questionable take...) Grant Lavac: "Given that Dr. James Lacatski was the 'counterintelligence coordinator' for AAWSAP, how much confidence can we invest in the veracity of his public statements that 'at least one recovered craft of unknown origin, a flying machine with no wings, no engine, no fuel, and no fuel tanks' is in the possession of the US government and that they had 'breached the hull' of the UFO? In the context of the counterintelligence value of UAP/UFO, his comments in this most recent interview on WEAPONIZED (edited for brevity) only raise more questions for me." ~~~ Knapp: "A, it's not [Lacatski]. He's not out there beating the bushes. He's talked to us, but that's pretty much it. He's telling the full story as much as he can in a series of books. And I was co-author on two of those, not on this one. And, you know, I remember the first time I met him, it was in 2018." ~ (In April of 2019, Knapp shared that story, minus Lacatski's name, at UFO MegaCon. Knapp in 2019: "I thought today I would share with you, sort of the informational foundation that I’ve acquired. So, one year ago, I made this trip to Washington, D.C. at the invitation of Senator Harry Reid. It was St. Patrick’s Day, 2018 and I already knew a little bit about AATIP and AAWSAP and what they’ve been studying and where the money came from and how the program was created. I did this sort of spy thing where I changed hotel rooms and I changed taxis. I was making sure I wasn’t followed. And if there was ever actually, anybody following me, they must have thought I looked ridiculous because it was way over the top. "But I ended up having to meet with Senator Reid and some other people who were directly involved in these programs and they gave me a download. And I thought I knew a lot about these programs when I went there and realized that I only knew a little tiny bit. The purpose of this was to learn about these programs. We all know about AATIP, but in reality, there was something before that. "I sat down for a couple of hours with Senator Reid and other people whose names, they don’t want to be known. They brought me up to speed on how AATIP was created. How its predecessor was under way for a number of years. It coexisted for a long time. People in this room. People who investigate this topic may have suspected for a long time that there was some kind of a program that still existed. We’ve all heard that Project Bluebook was the end. 1969 it ended and the government was done with UFOs. They closed up shop. And the reason they closed it down is because there was no evidence that it involved national security. "And we all knew that was baloney because of the stories that we’ve seen that are really well documented. For example, UFOs over nuclear missile bases. UFO encounters with the military installations and atomic facilities. Things of that sort the have been well documented over the years. There are cases that involved national security. So at the end of Blue Book, of course, this memo said, alright, any cases involving national security will continue to be investigated in the regular way. Well, what the heck was the regular way? We didn’t know. Well now we do know. At least a little bit of it." (Project Blue Book was shut down in December of 1969, but a few months earlier, in October, we had the Bolender memo, which noted that "reports of UFOs which could affect national security should continue to be handled through the standard Air Force procedure designed for this purpose." What standard Air Force procedure? The regular way? Where did those cases go? We still don't know what Bolender was referring to in that memo.) ~ Knapp in 2019: "And one of the regular ways was this program called AATIP. So I went on this trip. [and] I learned this stuff about AATIP. I had known a lot about it before but I got this briefing about this alphabet soup of different programs, how they began and what they studied. December 2017, the New York Times breaks this story about AATIP. Now, I had known about it for a long time because I lived in Las Vegas. I knew Bob Bigelow. I knew Harry Reid. We’d talk about UFO stuff and what was going on. "So when I was told the New York Times was gonna break the story, I’m kind ticked off about it. Because hey, I’ve been sitting on this for a long time. Why don’t I get to break the story? And they had to, one after another, gently remind me, 'You know. You’re not the New York Times.' Which I had to admit! It was true. And if I had done the story, the Times had said that they weren’t going to do it if somebody else breaks it. So, if I had done it, it’d be another story from a UFO reporter. "The New York Times did it and they changed everything. Because they did it, wider organizations did it. Some of them took shots at the New York Times because The Times got the story and they didn’t. But that story was accurate, to a degree. But the story that it told was not the full story. AATIP, that we know about…the AATIP that studies nuts and bolts saucers…case of UFOs that have encounters with military units such as the USS Nimitz, that is studied by a group of people, Lue Elizondo was the head of it. "It’s not so much a program as it was a loose network of intelligence officials in different agencies, including the Air Force and the Navy, CIA, DIA, DARPA…there might be a couple of other agencies. But a case would come in from any one of their units [and] it would be shared with this group of people, analysis would be done, evidence would be looked at and then stashed in a draw and nobody ever sees it. It’s not passed up the chain of command. "In 2007, that changed. One of the guys (Lacatski. ~Joe 2025) I met with in this meeting in Washington is the one who changed it. He had been in the same position that Lue Elizondo had been in. And his name is just not out there. He grew frustrated with what was happening with the phenomenon and he suspected that UFOs flying around the sky, buzzing our military units every once in a while, is not the full story. Even if you could solve that part of the mystery it wouldn’t solve the bigger part of the picture. "So he grew interested in Skinwalker Ranch and he had read the (Knapp/Kelleher – 'Hunt For The Skinwalker') book. And after he read it, he called up Bob Bigelow and said…actually, he wrote him a letter and said, 'Hey, can I go to the ranch…go look around? I’m with the DIA.' Bigelow says, 'Come on out to Las Vegas and I’ll take you there.' And that’s what happened. He flew to Las Vegas. They flew on Bigelow’s jet. They went to the ranch. "This guy’s not there fifteen minutes and he has an experience. And I’m not gonna go into detail. I’m hoping that he’s going to maybe come forward at some point and describe his experience. But it was just for him. Of all the people in this room, in the encounter, he was the only one who could see it. He’s the only one who had an angle on this thing that appeared. And he’s pretending that he’s not seeing it but it’s right out of the corner of his eye. And he doesn’t say anything until he leaves the ranch. And he gets off and he asks Bigelow if he had seen it. And he had not. The other people who had been in the room had not seen it. "He flies back to Las Vegas, goes back to Washington, D.C. and looks up Harry Reid and tells him about it. Now Reid had some experience in these matters that I’ll get into in a little bit. But as a result of that conversation, Reid, who had an interest in UFOs and had maintained that interest over many years – and I can attest to that personally – called in a couple of his friends in the Senate – Daniel Inouye and Ted Stevens. They had a conversation in a secure room and they decided to provide some funding for a much broader study. Something that looked at…beyond flying saucers, that looked at other paranormal aspects…supernatural aspects that we would not normally associate with aliens or ETs. Assuming that that’s what this is, which I’m not sure anyone knows for sure. And that is how AAWSAP was born. The Advanced Aerospace Weapon System Applications Program." ~~~ Knapp Yesterday: "The only reason [Lacatski] came forward, he was ticked off about how AATIP had been described in major media reports, and no mention had been given to the actual, real program. That one that had a $22 million budget, lasted 27 months, and which put together the biggest UFO data warehouse in history, that had written all these papers that still have not been released." (In the most-recent interview (Part 1) with Weaponized, Lacatski let it fly with his issues related to the 2017 NYT article: "The initial reporting...by the New York Times story in 2017 was totally inaccurate. Contrary to what some people claim, the authors knew my name and position at AAWSAP, yet never attempted to contact me. Likewise, the The Washington Post. POLITICO (laughs) contacted me within hours after the articles were published in the free publications, asking for my opinion. They knew my name, they had my phone number. Why didn't they contact me [beforehand]?" ~Dr. James Lacatski on Weaponized ~ Knapp: "So, Jim was a counterintelligence guy for AAWSAP, but in this role. He wasn't putting out cover stories or lies, he didn't put out anything. The world didn't hear that AAWSAP existed until years later, at least by that name. There was one statement made to the press about that program. It was by Robert Bigelow, whose company, BAASS, got the contract. A week after he signed it, he came on with me on Coast to Coast AM and said, 'We got this program dealing with UFOs, we have an unnamed partner, and we're excited to get going.' That was it. "Jim Lacatski wasn't putting out PR releases about AAWSAP. There was nothing. That was the last thing anybody said until the New York Times did the AATIP story, and then Jim Lacatski felt the real story was being covered up. If not for that story about AATIP and the problems that he saw with it, he would never have mentioned this. I don't think ever." (Well, then, thank you to the NYT journalists and editors for pissing off Lacatski!) Knapp: "You'll recall, AAWSAP, at the time that things went downhill, that the funding was moved away, they were trying to make it into a SAP, a Special Access Program. And if it had happened, we probably would never have heard of it. If it had happened, Lue Elizondo would have been the counterintelligence guy for AAWSAP, that he had already talked to Lacatski. "But Lacatski is not proclaiming the greatness of the program. He's not out there beating the bushes on podcasts and newscasts, other than with us, and he never put out in counterintelligence. His role, counterintelligence, meant something different for AAWSAP. The thing that DIA had told him was, 'Look, you know, it's not a rogue program. I know it gets weird into some of the phenomena that was at Skinwalker Ranch and other places. We don't care. Here's what we care about: Don't let the secret out. We don't want to see this on the front page of the Washington Post. We want it kept secret.' (John Greenewald was one person questioning whether AAWSAP was actually a prosaic program and Lacatski just decided to go rogue with a foray into UFOs and the paranormal.) Greenewald Tweet: "Did the U.S. government really sanction this, and if so, is this really how it was run? Or was this a rogue operation by a select few on the inside playing with Uncle Sam's coffers?" (Greenewald was quote tweeting a Greenstreet hit-piece video on AAWSAP. In his interview on Weaponized aired over the past few weeks, Lacatski said that former Deputy Director of AARO, Tim Phillips, also used the "rogue" word when describing AAWSAP. Did DIA really not know what AAWSAP was about? Did Lacatski go rogue and turn a program that was supposed to look at prosaic, advanced technology into one that studied UFOs and the paranormal? Here's an exchange from the 2023 interview Knapp and Corbell did with Lacatski and Colm Kelleher.) Kelleher: "The critical part of AAWSAP that we tried to convey in 'Skinwalkers at the Pentagon,' was that there were two fundamental, parallel tracks that AAWSAP ran on. The first one was the examination of UFO performance. And, you know, the UFO performance part was getting all of the data from eyewitnesses, plus deploying sensors into the field, in order to gather data on the performance of UFOs. That was track number one. And track number two was: What effects do UFOs have on humans? That was a parallel track that, from the get go, AAWSAP decided, unambiguously, to run both tracks in parallel. We documented psychological effects, and then we also documented paranormal effects." Lacatski: "Anything can be said on the internet it seems, factual or not. Well, one thing that is not factual is, DIA knew what it was getting into in regard to both aspects that Colm just described to you. And let me end my statement right here. We had no choice but to pursue both aspects." (That was a poor way of him saying: The claim that DIA was unaware of AAWSAP looking into all aspects of UFOs, including the paranormal, is NOT true.) Lacatski: "I want to emphasize something I said on my first and only interview. It was a closed program. It operated very similar to a SAP. The director, the director of analysis, and my office chief...and, of course, division chief, knew about this program. No one else did. Now, I was also protected by the stovepipe nature of that. I did not have to address political-type questions. I was insulated, but they were, too. There was no one else. People in the surrounding cubicles didn't know. Nothing was purposely being hid. It was a closed, stovepipe system, and it needed to be. It needed to be operated that way." ~~~ Knapp: "And so, Jim Lacatski took it on himself, put it in his own hands. He and Colm Kelleher interviewed all these people who applied for the jobs, the 50 full-time positions that they staffed, in a matter of months. They did background checks, they required security clearances for all those people, and they were worried about leaks. They didn't want information to get out. "They also were concerned about espionage by foreign players, by foreign companies, things of that sort. And some of that really did happen. As Jim has shared with us, there were a couple of phones that were transmitters that were found inside Bigelow Aerospace, inside the Bigelow, uh, facilities, and it was very alarming because they weren't sure who was doing it. I think they think it was a foreign government. I'm not going to say which one, uh, they suspected the most." (Lacatski said that the phones in question were made in China.) Knapp: "But, and then they also found weird frequencies emanating from Skinwalker Ranch. That's not strange, and there's a lot of unusual stuff that happens there, but it was some sort of a an espionage program that they believed was was not only looking at the ranch, but also at BAASS. "That was his primary concern. He was worried that the story gets out, because secrecy was of paramount interest to the heads of DIA and he's worried about the information getting out to the public. Because once it happened, then the knives come out in the Pentagon and within the intelligence community, which is kind of what happened. A memo was sent from Harry Reid's office, let other people know that AAWSAP existed, and that's when things started getting problematic." Corbell: "The bugging thing. So, it's not just like Bigelow Aerospace was tapped with something, he said, specifically, AAWSAP, right? So they were looking at that new UFO program. And I don't know how public this is, but he did say it was - not just him, other people have all said - it was multiple nations, multiple, different devices from those phones. And he also said that they worked with FBI, they had FBI liaisons looking at the ranch property, and also at Bigelow Aerospace. "Because, remember, they were supposed to receive a transfer of materials. That's why they reverse, reverse engineered (laughs), you know, they built everything to be able to hold SCIF-capable and material-capable property at that classification level. So, look, I think if we pull it back, the whole idea is, James Lacatski made a statement at some point that he was, you know, head of, or part of, or running the counterintelligence for AAWSAP. But his point was to keep AAWSAP itself secret from foreign nations. So then he has to keep it secret from the U.S. He did it. He did a great job. They actually kept it secret. That doesn't mean he's going out and creating false information to the public like he's been accused of. "So, should we listen to Jim Lacatski? That was like, you know, the main question. Oh, one second. He also identified that there is currently a counter-programming, counterintelligence operation going on to the American public, but not against the American public, by AARO." (In other words, spread misinformation to the American public so they can advance their goal of misinforming and confusing our adversaries who are always listening. National security! IMO, that's only acceptable if we're talking specifics related to propulsion, technology and weapons that can be used to give us a leg up on said adversaries. But everything else should come out and be made public. We shouldn't be told a bunch of lies about information we paid for and that could, potentially, give us some clarity about our species and other lifeforms on this planet.) Corbell: That was so clear in our interview with him that he said that, you know, 'Look, they're acting this way. They are telling you lies about AAWSAP and what happened.' And that's why he said, 'My books, I'm a government employee. This was paid by taxpayers. I'm trying to give you information.' And that's what his books are. "So it's clear from these rounds of interviews that we just had with Dr. Lacatski that he supports a controlled UFO disclosure. He made that very clear. So should we listen to what he has to say? I mean, he was a big dog, right, George?" Knapp: "He was the head of the largest U.S. government-funded UFO investigation in history, that we know of. He worked with Colm Kelleher, who was the boots-on-the-ground guy in Las Vegas. He worked with Jay Stratton. Stratton's role in the development of AAWSAP has not been really fully explored, but he's got a book coming out at some point, once it gets through the DOPSR process. But then we'll get additional information to buttress what Lacatski has said."

Joe Murgia

56,558 Aufrufe • vor 7 Monaten

CRITICAL: Joe Rogan connects the dots between the AIDS and Covid scams (my term): "Maybe [AIDS was] the same as what happened during Covid, but maybe back then, there's no internet, and... they could just get away with it... [and it's Fauci who pushed] the vaccine during... [AIDS and] during the Covid crisis." Rogan (Joe Rogan), who's talking with stand-up comic Brian Redban here, goes on to highlight several key points: 1. The fact that Peter Duesberg, a genius German-American molecular biologist and professor of molecular and cell biology at the University of California, Berkeley, known for his early research into the genetic aspects of cancer, said that AIDS was not due to HIV, but rather namely heavy drug usage among the gay community. 2. AZT (zidovudine), a drug—supposedly—used to treat HIV infection by inhibiting the virus from replicating, was actually doing immense harm. 3. Tony Fauci was the face of both the AIDS and Covid scams (again, my term). Rogan even notes that Fauci pushed both the Covid injections and AZT as quote-unquote "safe and effective." 4. Reading an article in Spin Magazine written by Bob Guccione, Jr., Rogan even highlights the fact that AIDS journalist Cecilia Farber (Celia Farber) had "unearthed hard evidence of the cold-bloodedness of the AIDS establishment pushing a drug [AZT] that was worse than the disease and killed faster than the natural progression of AIDS left untreated." Regarding Covid, note that there are parallels between AZT and Remdesivir, the deadly drug physicians and nurses used to kill "Covid patients" in hospitals. (See tweets 4 and 5.) Critically, note that Rogan's conclusions in this clip almost perfectly parallel those of cancer and AIDS research titan Dr. David Rasnick, who has said that the "bogus" HIV pandemic established the "playbook" for the bogus Covid "pandemic." (See tweet 2.) Also note that a documentary film was made about the possibility AIDS was a scam, dubbed House of Numbers. In the film, Nobel Prize winner and inventor of the PCR technique Kary Mullis noted that there was no link (that he could find) between HIV and AIDS. (See tweet 3.) ----------------Partial transcription of clip--------------- "Suge Knight was on— I think he was on Jimmy Kimmel show, talking about how you just inject somebody with AIDS. You can inject them with AIDS. What was my question? Oh, Peter Duesberg, Spin Magazine. "So he wrote this article about it, and then he— I believe he wrote a book about it. But he's fucked. Like, his career completely stalled out after that. He couldn't get funding for things and, you know, widely dismissed by all— most all other scientists. And back then, I used to think it doesn't make sense that this one guy has figured things out and that nobody else does. But now I'm like, maybe it's the same as what happened during COVID but maybe back then, there's no Internet, and maybe back then they could just get away with it. "Maybe back then they got used to getting away with it, which is why they tried it again in 2020. That's why they did the exact same thing to all those, like, legitimate professors, legitimate doctors. They shamed them and banned them. They didn't want anybody deviating. And that's, I think, what they might have done to this guy. "That's crazy to think that the the whole AIDS crisis might have really been about people destroying their immune system through hardcore drug use. That was his contention. People were saying, it's very homophobic. It's like, okay, let's. Let's not. Let's say a bunch of nice things about gay people. Let's. We love them. We appreciate. You know, I have no problem with gay. Let's say it. Like, if you're. If we're talking about this. If you were a doctor back then, gay people are amazing. However, all these gay people are doing drugs. All these gay people that are getting AIDS, like, something like 90% of them were hardcore drug users. This was his contention. "And you would say, 'Well, that's what opens them to the type of behavior that you get AIDS with.' Like, oh, okay, right. But Sam Kinison had a bit about that. Do you remember his bit? He was like, they say, 'Sam, AIDS is a communicable disease. Straight people get it too.' He goes, 'Name one. Name one fucking guy. Name one. It's not our fucking dance.' He didn't write the article, but he's definitely in the article. Right, there was an article about him... No, he didn't write the article. Did I say he wrote it? "Bob Guccione, Spin Magazine. Isn't he the guy that owns Penthouse? I think so. Right? Bob Guccione, Jr. Founder of Spin. "Okay, listen to this. So this is what he wrote, what Bob Guccione Jr. wrote. Scroll up a little higher. At the end of 1989, two years after we started the highly controversial AIDS column, in Spin, we published an article by Cecilia Farber called the Sins of Omission about the truly bad and corrupt science surrounding promoting AZT as a treatment for the syndrome of diseases. Celia was the editor and frequent writer of the column, and unearthed hard evidence of the coldbloodedness of the AIDS establishment, pushing a drug that was worse than the disease and killed faster than the natural progression of AIDS left untreated. "AZT had been an abandoned cancer drug, discarded because of its fatal toxicity, resurrected in the cynical belief that AIDS patients were going to die anyway. So trying it out was sort of like playing with the house's money, because the drug didn't require the usual massive expensive research and trial processes. Having gone through that years earlier, it was insanely profitable for its maker, Burroughs Wellcome. "It was a tragically perfect storm of windfall profits, something to pacify AIDS activists and the media, and a convenient boom to the patient holders for HIV testing. Patent. Excuse me, patent owners, patent holders for HIV testing. Celia, who should get the Congressional Medal of Honor for her brave and relentless reporting here and throughout the 10 years we ran the column, exposed the worthlessness of the drug, the shady studies and deals to suppress the negative findings and its awful and final consequences. "This piece very literally changed the media's view of AIDS and sharpened their discerning and skeptical eye. And soon after, AZT was once again shelved, hopefully this time forever. Many times over the years since, people have come up to me and said that reading this article saved their lives, that they either stopped taking the drug and their health improved vastly, or they never took it because of what we reported. Nothing ever made me prouder. Bob Guccione, Jr. Founder of Spin October 3, 2015. So this is all— This article is all about Peter Duesberg's perspective on this. And, it's very complicated. And it's certainly not for me, a guy like me, to figure out, if he's telling the truth or if he's correct. But what they said about AZT and chemotherapy and pushing AZT through and how they made a bunch of money, that's all true. "Not only that, but they were giving AZT to people that showed no symptoms like Arthur Ashe. Arthur Ash tested positive. They gave him AZT. There's a bunch of people died from taking AZT that probably didn't have to die. That's scary shit, man. If it's the same guy that pushed the vaccine during the AIDS crisis, during the COVID crisis, it's kind of fucked that he got to do it twice. "And if he didn't do it twice, nobody probably would be aware that it was the same guy. Because, even if you know about AZT, nobody was going Anthony Fauci. Nobody was saying that guy's name. You know, you weren't saying when you would talk about the AIDS crisis even. They even made a movie about it, right? Dallas Buyers Club. That's the movie. That's what it's about. The bad guy in Dallas Buyers Club is Anthony Fauci. "That's the guy keeping them from getting other medications and pushing AZT. They do the same thing. We— We played a video the other day where Fauci's talking about AZT. The reason why they use it is because it's both safe and effective. He used the exact same terminology. Fucking wild."

Sense Receptor

18,528 Aufrufe • vor 8 Monaten