Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Hydraulic Exchange Technique: super useful in complex PCI/CTO work. Quick way to get a microcatheter off a short wire without a 300cm wire, trapper, or trapping balloon. Connect an indeflator to the microcatheter, pressurize to 20 atm (it drops constantly, so keep bumping it back up), and just open...

24,566 görüntüleme • 6 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Learn from my pitfalls: Severe iliofemoral tortuosity during a MitraClip case. Right iliac: the guide wouldn’t cross over Bayliss wire then Amplatz Super Stiff. Tried the left side instead, very tortuous too. 24F DrySeal went through fine, but the guide still wouldn’t follow. Went back to the right, swapped for a Lunderquist wire. Left the DrySeal sitting in the left iliac/IVC to help straighten things out. Right before pushing the guide through, pulled the DrySeal back to the left iliac and it finally advanced. Lesson: in tortuous vessels before you think about switching to the other side, don’t stop at one stiff wire. Escalate: Bayliss, Amplatz Super Stiff, Safari, Lunderquist, Meier. The theory of a contralateral sheath straightening the IVC might be helpful too. Another idea is to put a 28 F dry-seal then advance the mitraclip through it? Curious to hear how others have handled similar tortuosity? TCTME+ Altayyeb Yousef Wail AlkashkariFSCAI,FPICSوائل القشقرى🇸🇦🇨🇦🇺🇲 MIЯVΛƬ #IC ༄ 。° Amr Mohsen, MD Aref BinAbdulhak MD MSc Marwan Saad Abdallah El Sabbagh Musa A. Sharkawi David J. Cohen, MD, MSc Mohammed Qintar, MD MSc Muhammad Hammadah Mohammed Al-Hijji Juan Del Cid Fratti MD MSc Anton Camaj, MD Cardiovascular Research Foundation David J. Cohen, MD, MSc Mamas A. Mamas Cardiovascular Research Foundation Hooman Bakhshi Abdelkader Almanfi, MD, FACC, FSCAI إبراهيم الحربي Ibrahim Alharbi scottiejj12 Dr Alo, DO, FACC

Anas T. Noman

13,168 görüntüleme • 9 gün önce

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

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

Akshay 🚀

167,968 görüntüleme • 22 gün önce

Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.

JJ Englert

29,322 görüntüleme • 4 ay önce

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

375,365 görüntüleme • 4 ay önce

** Sega Genesis 3D Engine Update 8 ** Significant improvements all round as you can see and hear from the last update !! Foremost - A huge thanks to Toni Gálvez - Megastyle - BG. who has joined the project to create a bit of 16bit low poly magic. Toni's an Amiga fan but also crazy about game dev in general, he's worked on GBC, GBA, PC, MD, PSP, C64, CPC, MSX... and others. Gaming titles include War Times, Metal Gear, Rocketman, Tintin & Asterix to name a few. He's provided the great new ship model you see on screen - new striped buildings, all the backgrounds / palettes etc. There's a lot of models he's given me which need to be added, also he will be planning a lot of the level design. Very happy to have him help me turn this into something more than a tech demo as I have my hands tied pushing the MD as far as it can go haha - there is no cpu cycle to be spared. Also many thanks to my good friend CYBERDEOUS - Crouzet Laurent for the Music for this showing , I wanted to have the music load occurring so we have a realistic benchmark for performance and he was only too obliging. If you're into MD chiptunes check him out !! Since last update : New player model , substantially more detailed than the Arwing. Last update had a 23 triangle Arwing , this update has a 39 triangle custom model from Toni. We had several to choose from , others will be used for enemies . 3D Buffer size increased 25% to 256x160. This was quite tricky as I'm close to the DMA limit even with an extended vblank . Spent a few days thinking of how to do this as like anything retro every solution has a drawback, finally got a workable solution. It makes a big difference to have a bit more vertical height . Z Rotation added ( the screen tilting left to right ) , small hit to vertex transform on cpu thanks to look up tables doing the heavy lifting, saving 4 multiplies per vertex. Multiple speed ups in rendering code. Onscreen paths with no range checking used until Z is close enough to cause clipping , partial onscreen drawing pathes that need to check boundaries, quad rendering completely rewritten - was very very painfull to get right . I found out the hard way that things are great when they are not rotating in the Z axis haha . Partial buffer draw optimisations - which have helped with the massive dma load , sending up to a 20kb buffer in a single frame needs a lot of optimisation. Min / Max tile lines are analysed and only sent if dirtied , reducing most buffer swaps substantially. Still some issues to sort out , at times you can see the flicker near top of screen when frames are near full height . I need to optimise that a bit. Due to the onscreen buffer system a full Sprite background had to be implemented almost Neo Geo style. This flips the usual MD rendering system on its head as it uses both foreground and background layers for a foreground 3d plane and sprites for the background. This presents a few issues, one is to get a tilt effect on the background by using narrow sprites (16x32) we run out of sprites when trying to cover the screen. Thankfully the MD is not limited to 80 sprites, to fix this a 114 sprite multiplexor is used to draw the background, its completely made up of 16x32 sprites ! Why do things this way ? speed . Its the interleaved foreground/background layers that allow a double buffered ram system writing to write to vram using dma in a completely linear fashion - virtually no tile translation needed. The negative is you have no planes for the background, that's where the sprites come in . Thanks to H40 mode we still have a few sprites we can use for effects in the forground also . Thankfully we can implement a fairly good tilt still for the background using sprites, in future updates this will be able to move horizontally also and a bit of vertical movement. XGM1 music driver in use to simulate music cpu load, XGM2 unfortunately with the massive DMA needed to shift the 3d buffers would slow down at times rendering it unusable, XGM1 plays at full speed - albiet with a bit more of a cpu hit. Together with the sprite multiplexor and the music driver active theres a 10 % hit to cpu so I've had to play around with draw distances / object heights and other optimisations to offset that. Not to mention the larger buffer takes more cpu to fill also. Everything is placeholder so will be changed with proper stage design. We are averaging 20 FPS in the current video, I'll push for more as always !! Progress continues on my other projects , updates soon on those - retirement can't come quick enough . #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

32,825 görüntüleme • 11 gün önce

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.

Yam Peleg

419,636 görüntüleme • 7 ay önce

Vallée and the Closed System: Are We Prisoners? 🧠👽 Vallée: "Are We Being Taken Over by a Species from Somewhere in Space That's Vastly More Intelligent Than We Are?" 👽🧠 "..the simulation...was a new concept that I initially rejected." ~Vallée "Is it looking for us to try to interact with it as equals or with parity?" ~Scafish "Nobody says that to Congress, and I think Congress should hear it." ~Vallée If, "it's a closed system, we're like prisoners and something is going to happen to us, and there is very little we can do." ~Vallée Turn the thermostat dial. "If the temperature doesn't change, then I know I'm inside a control system. So, we can do the same thing with UFOs, but we have to react. We have to, number one, acknowledge that it exists, and number two, we have to react to it." ~Vallée ~~~ I've been wanting to share this one for a while... Vallée: "So, he said, the question you have to ask about UFOs is, number one, is it a natural system or an artificial system...control system. And if it is a control system, is it open or closed? In other words, are we being taken over by a species from somewhere in space that's vastly more intelligent than we are?" (I've never heard him even suggest that possibility.) Vallée: "You know, as Dr. Garry P. Nolan says, you know, people who have had ten, you know, scientific revolutions, or a hundred or a thousand, and come here with superior science to do something... And in which case, you know, it's a closed system, we're like prisoners and something is going to happen to us, and there is very little we can do. Or, is it an open system where we can, in fact, communicate with it. And if we can communicate with it, then the question for me as an information scientist is, what are the modalities of the interaction, you know? It's not just can we learn their language? And they say, you know, 'We come in peace to save mankind,' or something. Or 'We will give you the cure for cancer' or something. I don't think it's at that level." (Will we ever be able to get answers to these extremely important questions? If it's an open system, how do we communicate with it? How do we provoke it to react? We know it reacts to anything nuclear but we still don't know why. This is why we need the USG (and other governments) to present evidence that shows the masses this is real and extremely important for our species to investigate. If that evidence exists and is shown, we'll have an easier time getting the world's best minds to join the effort in figuring out the best way to answer these questions. We still may fail but we should at least try.) Vallée: "I think it's a meta-system. It's not a system. And that's my fear...if we can circle back to your earlier question about, you know, about NIDS and about BAASS, what we did for the government and what we did for the Defense Intelligence Agency. Half of the budget was spent developing, you know, a super database. And we don't know where it went. I mean, I'm not cleared to know where it went." (On the contractor (BAASS) side, Bigelow should have all copies of what AAWSAP produced. And on the DIA side, Lacatksi said he put all of the digital files in a specific place that he didn't name. As long as someone didn't delete it all, it should still be there. Vallée has said that the Capella database has about 250,000 cases from around the world.) Vallée: "But that would be a very interesting question, because the people who are getting [the database] are getting raw data, which we have very well organized, all in English. So they have the luxury of, you know, we had five translators from French, English, Portuguese, Russian, you know, everything was translated in a single structure across fourteen databases. "That's what we need to answer the question about the control system, and it's not being done. And we hired a whole team that we had trained to work on it. So to rebuild that will take the next ten or fifteen years. And nobody says that to Congress, and I think Congress should hear it, because it's our money." (As long as names and personal details are scrubbed from that database, there is no reason NOT to release it to the public. This way, we can take it and use AI to help decipher patterns and maybe answer some of these questions. Can Congress help us get access to that database?) Vallée: "When you ask, is it a control system? That's a big question." Peter Scafish Peter Skafish - "You asked, at one point, whether the system is open or closed, and you said, additionally, I believe, if it's open, that it would be possible to communicate back to it. And it sounds to me like that's the key question for you. Is, if you can understand what what the system of symbols is, or the modalities of communication, then you can understand enough to engage in some kind of communication, or at least give some kind of response to show that you understand." Vallée: "Yes." Scafish: "So then the question, and we have a member named Jacqueline, who has asked this. Could the system be stimulating us - provided there is such a system - to interact with it, more as subjects or agents than as something like animals or objects? Is it looking for us to try to interact with it as equals or with parity?" (When people report getting injured or sick from being in close proximity to UAP, it suggests to me that the phenomenon won't go out of its way to avoid affecting us in a negative manner if we get in their its/way (assuming it even knows that close encounters with UAP are not good for humans). Kind of like how we treat lower lifeforms. If we encounter a wild rabbit crossing the road, many of us will do our best to avoid it, but not if it means damaging our car or ourselves in an accident. It may ruin our day if we hit it, but it won't stop us from driving again in the future. Do NHI have bad days if their tech injures us or makes us sick? I have no clue.) Vallée: "Well, what I saw in the notes you gave me, is she was also asking: Is it a control system because we think it is? And that's a very interesting question. Because we react to the UFO phenomenon, or the UAP phenomenon. And, you know, at this point when I think about what I'm going to do next in this research, if I'm given the the opportunity to live a little longer, I'm not going to go back and write any more computer programs. There are better people to do that now, they have the data, and we're in a different phase now. We're in a whole different system. I have the luxury of doing some experiments I wanted to do for a long time." (Would have liked Scafish to ask him: What types of experiments?) Vallée: "So, if you think you are inside the control system, there are things that you can do. Or, if you think you're inside the simulation, you know, which was a new concept that I initially rejected, and then, you know, Ray's (Kurzweil?) work and others have brought it back to the forefront. And we have to ask that at the same time. Can we test it? How would you test it? Well, if, you know, I'm here in my apartment, and the temperature is constant in this apartment. But outside, I can see it's cold, or I can see the sun is out and it's warm, and how come it's constant here? So this would lead me to think that there is a control system, namely a thermostat, that is somewhere. "So I can start looking around the walls, and if I see dial, I can turn it, or I could start a fire and see what happens, see if the temperature changes. If the temperature doesn't change, then I know I'm inside a control system. So, we can do the same thing with UFOs, but we have to react. We have to, number one, acknowledge that it exists, and number two, we have to react to it."

Joe Murgia

27,613 görüntüleme • 7 ay önce

"We do it again. We do it again. We do it again. Because, this can't be. The problem is..it be. No matter how skeptical you are, be as skeptical as you'd like, but there it is." ~Bengston (This is what Mick West said he doesn't find interesting and thus, he doesn't want to interview Bengston. The truth? IMO, he's scared shitless to take on Bengston as there's too much data to refute. Psi (or whatever this is) is real and this is one of the more interesting claims in the world. How could you NOT be interested in this? How about you, Michael Shermer?) "We re-injected the mice without any treatment, and the mice were immune to cancer." ~Bengston (It's the 1970s on Long Island. A skeptical Bill Bengston is working as a lifeguard at the town pool and meets a guy, Ben, who claims to be psychic. No matter what tests Bengston comes up with, Ben passes with flying colors. Then Ben starts healing people. But how to know if they were being healed with Ben's psi or something more prosaic? Did they change their diet? Supplements? Conventional medicine? Not everybody came back so it was very hard to know. So Bengston moves to the lab where Ben would try to cure mice of a cancer that has killed every mouse ever injected within 27 days max. At the last minute, Ben drops out and Bengston is forced to be the healer.) ~ Bill Bengston: "If you watch a few hundred healings, at first it's exhilarating, but after a while it's frustrating. Because you don't know what, why, where, when, any of those things that someone interested in serious inquiry might be interested in. You were just looking at people coming in, some benefit occurred. People leaving. Sometimes they didn't come back. Sometimes it took more than one treatment. Sometimes it happened pretty quick. I think I was the fastest ever (Bengston says Ben healed his back after one short treatment). But what did? "So you come in, you have x, it's a famous algebraic disease. You have x, and you leave better. Now maybe it's the multiple treatments, you know, whatever it may be. But you leave better. What did it? Was it time? Because people get better over time. Was it belief? I didn't think it was belief, because I wasn't a believer. I was an experiencer, but not a believer. Was it the food you ate, the food you stopped eating, the grapefruit you had in the morning? I can't...I don't have the head to wrap myself around clinical questions like that. I never know why something happens, because there's too many variables and such. "And so, after watching a couple hundred healings, taking part in a couple hundred healings, I decided to...I gotta go past this. And I ran into another guy who was watching this, somewhat parallel to me. A geologist, pretty well known (David Krinsley ~Joe). And we said, 'What can we do to test this? You know, the phenomenon is seriously interesting. What could we do to really test it so that if healing occurs, there's no viable counter hypothesis.' "And at the time, he was the head of the geology department at City University of New York, and he said, 'I got some favors owed me, let me see what I can find out in the biology department. I'm pretty good friends with the chairman of the biology department there.' "And so he met with the biology chair, and he said, 'Well, let me poke around in my department and see what we can do.' And he said, 'I got the perfect study. There's a mouse model of cancer that has 100% fatality. Never been an extension of life past a month after it's been injected with cancer. There's thousands of journal articles written about this mouse and this cancer. Everybody around the world knows this mouse and this cancer. If you're in oncology, you know this mouse and this cancer, and [there] has never been a cure.' "I said, 'Let's do it. Let's find out what we can do.' "And at the time, I had no idea what to expect. So I was thinking, 'Well, maybe we can extend the life towards a month. Maybe it won't be a normal curve distribution, maybe it'll be a negatively-skewed distribution. And maybe the mouse will live to the end of their lifespan and all that. "We had no idea what to expect. "So we got a cage of mice. I held the cage of mice for an hour at a time in the lab at Queens College, City University, and we watched as the tumors grew. And I was sure this was failing. And incidentally, I'm almost always wrong. I expected, if we got to the mice right after injection and we treated them a couple times, enough, every day - we didn't know - if we treated them every day, they wouldn't develop cancer. I was thinking, you know, it's something like radiation. You know, you go, 'Zzt, zzt,' and you zap the mice and the tumors, or the cancer cells die, or something along those lines. I was thinking conventional oncology. "And so, I put my hands around the cage of mice, treated them every day, the tumors started to grow anyway, and I wanted to call off the experiment. You know, it shows you how much I believe. I got talked into going a couple extra days, and the tumors developed these blackened areas. And I said, 'Let's call it off, didn't work. You know, we tried it. Didn't work.' "Go a couple more days. Tumors started to ulcerate, and so there was this raw part of a tumor. And I said, 'Would you pay attention? It doesn't work!' Couple more days. And then the tumors suddenly imploded, and the mice were cured. They weren't remitted, they were cured. And by that, I mean it wasn't a suppression of symptoms, it wasn't a temporary reduction in symptoms. It was...there was no cancer in the mouse at all. "And it's farther than that. We re-injected the mice without any treatment, and the mice were immune to cancer. Now that's reasonably interesting. "So, first thing you do is, I, as a skeptic, go, 'Umm, this doesn't make any sense (laughs). Let's do it again. But let's not do it with just me, let's do it with some volunteers.' "So I had a couple of faculty volunteers who thought this thing was insane, and they were right. So I had a couple of faculty volunteers, they got a couple of student volunteers. All non-believers, no experience in any of this hocus pocus. Taught 'em the little technique that I had developed. They treated the mice, the exact same pattern: Tumor grows, blackened area, ulceration, implosion, full lifespan cure. "We do it again. We do it again. We do it again. Because, this can't be. The problem is..it be." (Both laugh) "It's just, you know, no matter how skeptical you are, be as skeptical as you'd like, but there it is. You know, I deny this gravity, you know? I don't believe in gravity. There is gravity. I don't believe in this healing. There is healing. "I just finished, recently, my twentieth mouse experiment, I'm a little slow. I've done it in, I think, six medical schools, equal number of other biology labs. And I just finished at Tokyo University, multiple strains of cancer and details you don't care about. "And so, I have done, at this point, twenty mouse experiments, multiple medical schools, many cell experiments. I've done many experiments. That's the really short version. A hundred years truncated into a couple of paragraphs."

Joe Murgia

12,705 görüntüleme • 1 yıl önce

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

Jeffrey Emanuel

25,483 görüntüleme • 6 ay önce

[ condition update ] 🐻‍❄ In short of what happen with me is an inflammation on heart muscle from a virus infection which still cant be identified yet. The symptoms I experience are painful breathing, heart racing, tight chest, difficulty breathing, kinda thing. I’m told not to overwork my heart because it could make the inflammation gets worse. That’s basically in short. As for the details, it was 4-5 days ago, I started feeling uncomfortable in my chest, it felt tight and I had trouble breathing as well. Anytime I did something, like exercising or walking on a treadmill, my body felt hurt, and my heart rate went up way higher than usual. It’s normally around 100, but it went to 150 even when I was just doing little activity. It felt off, so I thought I might have caught some kind of infection. The other day I made a doctor appointment in the hospital as I got some free time. I was told to go to internal medicine doctor and was asked about what I’ve been experiencing. I had fever, waking up found tightness in chest at one night, a nausea, but nothing came out. I just felt like about to vomiting but nothing came out at all, so I thought it was unusual. At that time, my face went all pale and lips went all purple already, which why I decided to go to the hospital. Once I was in the internal medicine, well, they did some screening. I said I have low fever, painful breathing, body and muscle pain, so I was sent to ENT because I experience a ringing in my ear as well, I then sent to do a hearing function test. Right ear was normal, while my left ear was.. what’s it called.. ringing in ear. My left ear hearing function drops down one level. It’s not that serious but since it’s related to inner ear, and it's a part of nervous system, right? If it’s affecting that, the doctor afraid it could lead to permanent hearing function loss. Yeah, that part is concerning. So I was prescribed steroids to be consumed to prevent further inflammation and damage more than this. Not sure if I’m explaining it right, but that’s what I remember. I’m not a doctor, lol. And then, after I got the steroids and back home, I had work to film on the next day. I was like, why I feel so tired going for work at 6 in the morning, why my body feels this exhausting, just bending over to grab something or doing other things made me feel like I was gonna pass out. Thought I was just old lol. But at that time I felt unwell, my chest felt tight, and I felt exhausted. That day, I kept working even though I was exhausted. I felt like I don’t wanna work anymore, it was tiring, even just walking up the stairs, I had to stop and take a break. I couldn’t do it, it felt so tiring. When filming, just stepping my legs already felt tiring that I didn’t want to step my legs anymore. So that day decided to see a doctor, focusing to check my heart as it felt tight and was racing, and I had pain when breathing as well so I decided to see a heart specialist doctor but I arrived there at 2 PM and there was no available appointment anymore. Also, the Echo or ECG machine was all used so I had to schedule an appointment for the next day. I went there in the afternoon. Blood pressure and other test was normal, around 110-160, and it’s normal. Pulse is normal. Blood pressure was okay. And what else, yeah that’s it. I had an ECG, the result came out normal. I’ve also just get physical check up recently and the result were almost the same when compared. But since I still didn’t feel well, I wanted to know what’s wrong with me so I asked for a blood test. It’s a blood test that focusing on troponin and CRP level, which are enzymes in blood cells that indicate heart issues if the levels are high. After my blood test, I waited an hour for the results. When they called me, they said my symptom is serious, it’s a heart disease. Normal troponin levels are below 1 for healthy human, but mine was 3800, which is extremely high, so I had to be admitted. This is an enzyme level in the heart muscle cells. If heart muscle is damaged or its cells break down, the enzyme will mix into the blood and can be detected in the blood indicating a heart problem, so I need to be admitted for further examination with echo. It’s an ultrasound for heart. The result saying that there’s an inflammation in my heart as predicted by the doctors. The heart muscle is really swollen and… [takes deep breath] oh I’m tired already. It's enlarging which makes my heart race and feel tight and uncomfortable. That’s what they said. It’s not working the way it should, which is why I get tired so easily. So it answers everything. After the echo I took a rest and got therapy regimen… as what I understand, consuming steroid can suppress the immune system, right? They help reduce inflammation while the body fights the virus. It’s reducing the inflammation, right? But they said steroids alone weren’t enough because my troponin levels were way too abnormally high, so I got an injection instead. [deep breath] I got injected last night for only three dosage because I had to work today in the morning.asked the doctor to discharge me cause I had to work first. But the decision was taken with condition. I got injected three dosage in the morning and did another blood test which show a result of a decrease in troponin level from 3800 to 1600. Doctor said it was probably 5000 before this and it keeps decreasing to 3800, and to 1600, So if the work isn’t too hard physically, I’m allowed to go, I then go to work. Today at work I was only standing around and talking around. I can stand and talk, but I can’t do any heavy work as it’ll will make my heart work hard and affecting the recovery, I then have to walk slowly. But even so, I can’t even walk fast tho, I get tired easily. Yeah, that’s all. It’s not like I’m completely bedrotting or something, it’s just heart muscle problem, so… fighting ✌🏻

deeコ

147,640 görüntüleme • 1 yıl önce

Crazy week. Spent part of it in South Dakota, visiting trade schools and telling the incredible story of Build Dakota, a scholarship program similar to mikeroweWORKS that’s assisted nearly 3,500 kids with over $43 million dollars. I’ll tell you more about that later, and about how South Dakota is leading the country in the race to reinvigorate the skilled trades. For now, I just want to share some video from a ride-along I did on my way back to the airport. As it happens, the annual Buffalo Round-Up took place yesterday in Custer State Park - another one of things I’d always wanted to see. Well, I finally saw it, and all I can say is holy crap! Thirteen hundred buffalo who preferred not to be relocated, versus a couple dozen expert cowboys and cowgirls determined to get them out of the hills, into a valley, and through a narrow gate that led into a large corral. Assisting the riders were half-a-dozen F-150’s driven by park employees – one of which I was allowed to occupy. So much fun. Thousands of people showed up on a gorgeous morning to see what could possibly go wrong, and marvel at the sight of a buffalo herd on the move. The people lined the ridges above the valley, and watched for a few hours as the buffalo stampeded and the horses galloped and the riders cracked their whips and the trucks accelerated over the wild and rocky terrain, trying to keep the herd headed in the right direction. My driver, Cory, told me to buckle up and hang on. “You got one job, Mike. Keep an eye out for big rocks hidden in the grass. They’re all over the place. Last year, a driver hit one and snapped the chassis in two. Had a Senator on board. Not good.” Perhaps if I hadn’t been on the lookout for rocks, the attached video would look more professional, but it should give you an idea of what’s it looks like to chase a herd of buffalo in a pickup truck. In short, it’s a blast, but it’s also a bit unsettling. As we sped over the plains and over a massive prairie dog town, I couldn’t help but wonder what would happen if the buffalo suddenly all decided, together, to resist our best efforts to push them into a place they didn’t wish to enter. In other words, what would we do if the herd stopped acting like a herd, and realized that they were in fact, the superior force? Probably something similar to what happens when bipeds grow weary of being pushed in directions they don’t wish to go. I was about to share that philosophical observation with the other passengers in the pickup, when Cory ran over a large rock that I had neglected to spot. “Rock!” I yelled, a second too late. “Thanks,” said Cory, as his head bounced off the ceiling. Moments later, Cory’s walkie-talkie exploded with an urgent alert. “Rider down! Rider down.” Someone one the other side of the herd, hopefully not in the middle of the herd, was on the ground, and there was nothing we could do. A couple of EMT’s in a Razor were quickly dispatched to render assistance. I’m not sure what happened, but given the many thousands of prairie dog holes all over the sprawling landscape, I was worried for the horse as well as the rider. Herding buffalo on horseback is dangerous, and as I as tried to focus from keeping Cory from hitting anymore big rocks at high speeds, I couldn’t help but consider the business of hunting buffalo 200 years ago on this very land. Back then, at the beginning of the 19th century, there were something like 50 million buffalo in North America. They say the herds stretched for miles in every direction and moved like a massive wave over the prairie. To be a Dakota Sioux back then, riding a horse without a saddle into a vast herd of stampeding buffalo with nothing but a bow and arrow was amazing enough. To somehow bring one down and then live to tell the tale is mind-boggling. But maybe not as mind-boggling as what we did to the buffalo population in the decades that followed. That was nothing short of genocide, just as bringing them back from the brink of extinction was nothing short of a miracle. “Rock!” I yelled. Cory swerved to the left just in time, and then accelerated as a dozen animals broke away from the herd and tried to bolt back up the hill. I couldn’t help but notice they crapped as they ran - a lot. So much so, it made me wonder about the sheer volume of turds that 50 million buffalo would have produced two hundred years ago. (After 20 years of Dirty Jobs, my brain is still wired to ponder the impact of feces from every species.) Yesterday, the buffalo poop was literally everywhere. It was impossible not to walk in, ride over, or drive through. The tread on our tires was packed with scat, and that’s just from chasing down 1,300 of them. What would the poop from 50 million of these things look like? It must have been a foot deep for miles in every direction. And what would the impact of all that poop be on the early pioneers used to travel these same plains? How did their wagon wheels get any traction in all that dung? “Rock!” I yelled, again, just in the nick of time. The mind wanders when you’re riding shotgun in a buffalo chase vehicle, even when you only have one job to do. But if you ever have the chance to ride along on a round up like this one, do it. The sight will stick with you, even as you find yourself pondering the history of our great country, the impact of feces from every species, and the great good fortune of those lucky Dakotans who make their home here today. A home, where the buffalo roam.

The Real Mike Rowe

96,273 görüntüleme • 1 yıl önce