Podcasts about SEV

Po siedmiu latach do kin wróciły Gwiezdne wojny, ale również po siedmiu latach zakończył się jeden z najgłośniejszych seriali superbohaterskich, czyli „The Boys”. W wirtualnym studio spotkali się z tej okazji Sev z Pory Imperatora oraz Jerry, aby podyskutować o piątym sezonie tej produkcji. Z jakimi oczekiwaniami podchodziliśmy do finałowej odsłony tego serialu? Czy twórcy mieli ciekawy pomysł na domknięcie poszczególnych wątków, czy może nazbyt skupili się na promocji spin-offów? Dlaczego uważamy, że hasła o flanderyzacji postaci to leniwa kalka recenzencka? Czy showrunnerzy „Chłopaków” przegięli z ilością odniesień do bieżącej polityki, czy może to życie dogoniło satyrę? I w końcu, jak oceniamy wielki finał (i zakończenia wątków poszczególnych postaci)? O tym wszystkim i paru innych kwestiach posłuchacie w dzisiejszym podcaście.

Po siedmiu latach od premiery ostatnich, kinowych Gwiezdnych wojen, czyli „Star Wars IX: Skywalker. Odrodzenie”, na duże ekrany trafili w maju bohaterowie wywodzący się z serialu! Din Djarin i Grogu otworzyli worek z serialami z uniwersum na Disney Plus i po dziś dzień cieszą się sporą popularnością, ale czy film z nimi to dobry pomysł? O tym dziś dyskutują Mando, Sev z Pory Imperatora oraz Jerry. Jakie mieliśmy oczekiwania względem tej produkcji? Jak wyglądała jej promocja? Czy Favreau i Filoni zaserwowali nam festiwal cameo, czy może coś więcej? Jak oceniamy poszczególne rozwiązania fabularne? Jak broni się strona audio-wizualna całości? O tym wszystkim i wielu innych kwestiach posłuchacie w dzisiejszym podcaście. A jako, że „Mandalorian i Grogu” to produkcja zdecydowanie dla młodszych odbiorców to na koniec odcinka zapraszamy na dyskusję z dzieciakami Jerry'ego, które opowiedzą jak wypada ten film z perspektywy zarówno fanów Grogu, jak i osób, które z serialem nie miały wiele do czynienia. Opinii Młodych posłuchacie od: 01:44:49

During the Clone Wars, Darth Sidious and Count Dooku assembled the Dark Acolytes — a network of Dark Jedi and fallen Force-users who served the Confederacy as assassins, spies, and commanders, yet were forever barred from true Sith status by the Rule of Two. In this episode of Star Lores, we explore the most feared dark side adepts of the CIS, from Asajj Ventress and Savage Opress to Sev'rance Tann, Quinlan Vos, and Sora Bulq, and how Darth Sidious used them to corrode galactic faith in the Jedi Order. Become a patron to get access to the bonus episodes or support the show through Paypal and bitcoin! You can also check out our merch on Redbubble. Don't forget to also connect with us on Facebook, Instagram, X.com and Discord! Find all of our links here: https://doras.to/starlores Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Brandon Lentino is a prominent creative executive in the social media and creator economy space, currently serving as the Chief Creative Officer (CCO) at Viral Nation, one of the world's leading social media marketing transformation agencies. His work focuses on bridging the gap between traditional brand marketing and the fast-moving "social-first" world of creators and influencers. Chief Creative Officer: Lentino oversees the creative direction for global brands, ensuring that their social presence isn't just "ads," but content that resonates with modern audiences (especially Gen Z and Gen Alpha). VN Studio: Following Viral Nation's acquisition of Eight Seven Media (a production agency Lentino co-owned), he helped spearhead the creation of "VN Studio." This internal hub focuses on high-speed content production, distribution, and monetization for athletes, celebrities, and brands. Strategy: He is a vocal advocate for "engineering UGC" (User Generated Content). His philosophy is that brand activations should be designed as "social engines" where the physical experience is built specifically to prompt sharing and digital engagement. Zillow & "Demure" Marketing: He led a viral 2025 campaign for Zillow featuring creator Jools Lebron, leveraging the "very demure, very mindful" trend to reach first-time homebuyers on social media. Super Bowl Coverage: In February 2026, he was a featured expert for ADWEEK's "Big Game Live Show," providing real-time analysis of Super Bowl ads, social sentiment, and creator-led marketing strategies. 7-Eleven "Summer of Sev": He oversaw the award-winning creative for 7-Eleven Canada, which used a digital-first approach to position the brand as a convenience leader for a younger, social-savvy demographic.Lentino often speaks about the "Hybrid of Tech and Humanity." He argues that while a strong tech stack (social listening, AI, and analytics) is necessary, it must be combined with human expertise to know when a brand should enter a cultural conversation without looking like an "outsider."

W dzisiejszym podcaście wskakujemy prosto do Alcatraz! I uwierzcie nam - rakiety z gazem bojowym są dopiero początkiem problemów. Porozmawiamy o filmie "The Rock",  widowiskowym miksie kina akcji lat 90., wojskowego thrillera i bezczelnie dobrej rozrywki spod znaku wczesnego Michaela Bay'a. Na ratunek światu pędzą James Bond na emeryturze (Sean Connery) i chemiczny supernerd, z nerwami na poziomie "nie mów do mnie teraz" (Nicolas Cage). Będzie o kinowej nostalgii, akcyjniakach przed erą CGI, legendarnych pościgach i równowadze między prawdziwym napięciem a campem. Pobiegamy w zwolnionym tempie, pod dowództwem Eda Harrisa i przy okazji rozwalimy żółte Ferrari. Testosteron, one-linery, strzelaniny i świetna chemia między postaciami. Ciekawe, czy Bogusia, Sev i Jerry wypadną równie bombastycznie jak ten seans? Konglo dba o Wasze zdrowie i samopoczucie. Zapewniamy niezbędną dawkę Nicolasa Cage'a! Enjoy!!!

Äntligen dags för det första avsnittet av podden och jag är så glad över att du är här! Se till att prenumerera på podden så att du inte missar nya avsnitt och ge mig gärna ditt bästa betyg för att få podden att sprida sig till fler ~ det skulle betyda så mycket för mig! Nu kör vi igång detta nya kapitel tillsammans

When a "rogue AI agent" triggered a Sev-1 emergency at Meta, the media immediately started spinning up Terminator scenarios. However, what actually caused the breach is far less Hollywood and reveals a far greater risk to your organization. The reality is a much more sobering masterclass in human behavioral failure. In this week's episode of Future-Focused, I‘m breaking down the recent incident and chain-of-events at Meta that led to highly sensitive data being exposed. In doing so, you'll see that AI didn't maliciously hack anything. Its “rogue” behavior was posting flawed advice at the direction of a human followed by a human blindly executing it without verification. I'll explain why this was essentially an inadvertent social engineering hack, how the "halo effect" of AI is causing professionals to bypass their critical thinking, and why the ultimate security patch right now isn't in the code, but in our accountability structures.  My goal is to help you make some strategic moves and mitigate the risks to your oganization by highlighting three opportunities to prepare your organization for what's ahead:​Spot-Checking the "Rules of the Road": We love to assume that because we gave our teams new tools, they naturally know the boundaries. I break down why simply turning on AI agents without an updated Acceptable Use Policy is a recipe for disaster. You cannot blindly trust that your workforce has the discernment to navigate these tools; you must establish a baseline for effective AI use—like the AI Effectiveness Rating (AER)—before a Sev 1 happens to you.  ​Defining the Accountability Matrix: We casually assume that when an AI makes a mistake, the technology is to blame. I share why "the AI told me to" is quickly becoming a catastrophic excuse in the workplace. You need to clarify immediately that whoever executes the AI's advice owns the outcome, ensuring you don't accidentally build a culture where responsibility is endlessly deflected.  ​Running an AI "Grand Rounds": We are avoiding talking about our internal vulnerabilities because we fear judgment. I explain why adopting the medical community's practice of "Grand Rounds" is the perfect way to openly stress-test your systems. You must bring this Meta story to your next team meeting and force an open, judgment-free conversation about how a similar failure could happen in your own workflows.  By the end, I hope you'll recognize that true leadership in the AI era isn't about bracing for a sci-fi apocalypse. It's about building the human guardrails that will prevent a mundane mistake from becoming a catastrophic emergency.⸻If this conversation helps you think more clearly about the future we're building, make sure to like, share, and subscribe. You can also support the show by buying me a coffee at https://buymeacoffee.com/christopherlindAnd if your organization is wrestling with how to lead responsibly in the AI era, balancing performance, technology, and people, that's the work I do every day through my consulting and coaching. Learn more at https://christopherlind.co⸻Chapters00:00 – Introduction & The Terminator Myth01:57 – Declassifying the Meta "Sev 1" Emergency05:22 – The "Social Engineering" Hack of AI Trust07:59 – Action 1: Spot-Checking Your Acceptable Use Policy11:45 – Measuring Capability with the AI Effectiveness Rating (AER)14:52 – Action 2: Building an AI Accountability Matrix23:42 – Action 3: Running an AI "Grand Rounds"30:46 – Conclusion & How to Work With Me#ArtificialIntelligence #Leadership #CyberSecurity #FutureOfWork #ChristopherLind #FutureFocused #BusinessStrategy #DecisionMaking #TechTrends

LISTEN TO ADS-FREE Audio of this episode at https://djamgamind.com

Hoy en 10 Minutos con Sammy: Anthropic captura el 73% del gasto en IA de nuevas empresas tras negarse a quitar barreras de seguridad al Pentágono. Micron casi triplica ingresos gracias a la memoria HBM que devoran los chips de IA. Perplexity lanza gratis su navegador Comet en iOS — y reconoce que recopila tus datos para publicidad. Un satélite del tamaño de una caja de zapatos busca vida en 50.000 millones de planetas con IA a bordo. Y un agente de IA de Meta provoca un incidente Sev 1 dejando datos de usuarios expuestos durante dos horas — mientras a la directora de seguridad otro agente le borró todo el inbox.Puedes seguirnos en YouTube en https://youtube.com/olivernabani y puedes unirte al Discord Mashain en https://olivernabani.com/discord

LISTEN TO ADS-FREE Audio of this episode at https://djamgamind.com/daily

Jeff Collins, CEO of WanAware The last time the channel faced a shift this fundamental was the rise of the hypervisor. That transition reshaped everything, but it happened inside the four walls of the data center. What’s different about the current moment, argues WanAware CEO Jeff Collins, is that AI workloads, inference nodes, IoT, and SCADA infrastructure are being bolted onto customer environments without the kind of formal network redesign that virtualization demanded. The result is a growing visibility gap that most MSPs don’t realize they have. Collins points to a striking finding from a WanAware survey conducted in late 2025: when business leaders were asked about their visibility gap, they rated it extremely high. When IT was asked the same question, they rated it low. Both were technically right. IT was measuring visibility against the machines in their purview – Active Directory, database servers, web front ends. The business was measuring it against everything else: Kubernetes workloads, cloud functions, agentic AI processes, and infrastructure that might not exist tomorrow. That disconnect is why MSPs can show perfect MTTR and SLA performance while the customer is saying you’re failing. The conversation covers where traditional monitoring breaks down, why 30% false positive rates persist even after major platform investments, and how ephemeral workloads designed to disappear create alerts that will never resolve. Collins makes a compelling case that MSPs need to push visibility up the OSI stack, from layers one through three into the application and business logic layers where margin is significantly higher. He shares a practical framework for how to start, using vertical industry knowledge – particularly in sectors like Canadian oil and gas, where SCADA networks and AWS IoT Core infrastructure represent opportunities to grow a $1,000-a-month customer into a $30,000-a-month engagement. Read Full Transcript Robert Dutt: Hello and welcome to the ChannelBuzz.ca podcast, bringing news and information to the Canadian IT channel for the last 16 years. I’m Robert Dutt, editor of ChannelBuzz.ca and still your host for the show. Today we’re talking about a problem a lot of MSPs and channel partners are starting to feel, even if they don’t always have a name for it yet, and that’s visibility. As AI workloads, hybrid architectures and distributed endpoints become the norm, network traffic is changing faster than the tools that many partners rely on to understand what’s actually happening inside their customers’ environments. My guest today is Jeff Collins, CEO of WanAware. Jeff spends a lot of time with service providers and enterprise teams dealing with this shift, where accountability for performance, security and uptime is increasing, even as environments become harder to see and harder to diagnose when something goes wrong. WanAware operates in the network and infrastructure visibility space, but this conversation isn’t about the tools, the dashboards. It’s about how blind spots form in modern networks, why they’re easy to miss until there’s an outage, a security issue, or an SLA failure, and what partners need to understand as AI-driven infrastructure quietly reshapes traffic patterns and dependencies. In this discussion, we’re going to explore where traditional monitoring starts to fall apart, how partners can rethink what good visibility really means today, and why the ability to see what’s happening across distributed environments is quickly becoming both a risk issue and a business opportunity for MSPs. If you’re responsible for customer outcomes, but you don’t always feel confident you can see everything that matters, this conversation is for you. [MUSIC] Robert Dutt: Jeff, thanks for taking the time. I appreciate it. Jeff Collins: Thanks, Rob. Thanks for having me on. Robert Dutt: You’ve been advising partners, MSPs, VARs, these types of folks through a lot of change over time. Why does this moment with the rise of AI workloads and the continuing trend of hybrid networks feel like a real inflection point rather than sort of just the next evolution of the way things look? Jeff Collins: I think one of the biggest reasons why is because it’s so transformational to what MSPs and resellers and VARs and distributors have dealt with for, let’s say, the last 25 years. If we think about the last major inflection point that they dealt with was really kind of the realm of the hypervisor, this ecosystem where no longer did we have to have a server running an operating system, and that created kind of the whole ecosystem we deal with today. It created cloud, it created containers, all those things were built off this concept of a hypervisor. That was really the last major transformational thing that has happened. Now we fast forward to today and we’ve got this era of AI. We’ve got this era where we’re now taking agentic approaches, generative approaches, to things that our customers deal with every day. When I talk about our customers, those are the customers of the MSP, those are the customers of the reseller, the distributor. Not only are they dealing with that, they’re dealing with this massive evolution in the customer base, but they’re also having to do that same evolution in their own environments. If you’re an MSP and you’re focused on infrastructure, or you’re an MSP and you look more like an MSSP where you’re focused on security, now you’re starting to have to deal with, “Okay, I’ve got these tools, I’ve got these people, I’ve got these agents, I’ve got all these entities inside of my business that are doing something for my customer.” But now I have to think about how am I going to do that faster? How am I going to do that better? How am I going to do that more effectively? Because our customers are getting much more advanced. That’s really one of the biggest things that I see that we’re seeing a lot of, that “Where do I start?” from the channel partner community. When we think about the channel, we know all this stuff is going on, but it seems like such a Herculean lift that I think sometimes it’s hard to know where we make that first step. Robert Dutt: That makes sense. A lot of this, a lot of AI especially, and to a degree sort of the hybridization of the network, that complexity has come on without kind of a formal network redesign. Like you mentioned the transition to hypervisors and that necessitated rethinking how things were done because it was a physical change. Whereas a lot of, especially with AI, it’s kind of being bolted in, added on as you go. Why does that make the environment today harder to understand than maybe it was for past transitions when you’re sitting there watching it as an MSP or other partner? Jeff Collins: Well, I think one of the biggest reasons why this era is so much more difficult than the last transition is because we’re not bound by the four walls of our proverbial house. If we think about when we dealt with the last transition, every customer, their physical server sat inside of something they control. So we’ll refer to it as their house because that’s the easiest kind of comparison we can do. In today’s world, there’s certainly a lot that exists in our customers’ houses and in the houses that the MSP or the reseller or the channel partner or whomever it is are engaged in. But so much of that’s going outside of those walls. And when we think about AI, AI is certainly outside of those walls. I mean, we might be dealing with Anthropic, we might be dealing with ChatGPT or Gemini or the thousand other agentic or generative approaches that are out there. Those are all over the place. And now we’re asking these entities to take oftentimes a process-driven approach that they’ve had for 20, 25 years. And how do you change that process-driven approach when you don’t really know where those workloads, where those assets, where that data is going to reside either today or tomorrow, or even if that data that we’re looking at is even going to exist tomorrow. That’s this whole realm. I mean, we’ve been talking about ephemeral workloads for, you know, let’s call it 14 years, 15 years since really the rise of AWS. But now we’re starting to deal with these ephemeral workloads, not just in the realm of infrastructure, but also in data, in generative concepts, in agents. You know, historically, we had Bob Smith, who might have worked in the NOC. Well, tomorrow, Bob Smith is an agent. What does that look like? It’s AI. What did Bob Smith do yesterday? Did Bob Smith, the new agentic version of Bob Smith, did that person do the right thing, the wrong thing, the incorrect thing? How do we manage that? How do we deal with that? How do we process that? Those are all the things that are across the board, just happening at massive rapid scale. And so, you know, it’s a really difficult time right now to be an MSP or a channel partner, but it’s also an amazing time to be an MSP or channel partner. You know, our world, our capabilities are advancing so fast. You think about one of the simplest use cases that’s out there that all of us think is simple, that MSPs deal with every day, is a circuit outage. You know, a telecom circuit goes down and it’s connected to SD-WAN or it’s connected to a router or it’s connected to some type of device that’s out at the prem. And historically, every MSP on the planet’s dealt with it kind of in a similar way. We get an alert from a monitoring system that feeds a ticketing system. It pops up on a tier one agent’s dashboard. The tier one agent looks at it, they verify power, they verify if the router’s operational, and then they open a ticket with a carrier. And then they, and that’s the hurry up and wait type of world. Well, now in the era of AI, that changes that quite a bit, because every one of those things are very process driven. We don’t need people for that anymore. So now we can have a system take that process flow on, do that. Now, historically, we could use a system to do that. We could write automation and a lot of MSPs did that historically, but the problem with automation is automation is static. When we leverage AI, we can leverage enrichment that helps influence that agentic approach. And so now if there’s a nuance going on, let’s say an example is there’s a global power outage. So let’s say there’s a power outage in the entire Vancouver area. We know that. Well, historically, if we’re looking at that, we see all these customers that are down, we might through a tier one agent approach, a person-based approach that following a process, or even an automated approach, not really correlate that. Because if the MSP is in, let’s say, Montreal, they might not realize there’s a large scale power outage in Vancouver, which is thousands of kilometers away. And so when we think about that, that’s really where these things can change a lot from an agentic perspective. And then the MSP gets the joy of being able to repurpose that person to be much more valuable to their organization, that tier one person can become tier two, and that can really start changing that dynamic a lot. Robert Dutt: Most MSPs would have historically said we have good visibility across what our customers are doing. And probably I would say most believe they have good visibility today. Where does that confidence most often turn out to be misplaced or to start to break down as the model shifts? Jeff Collins: Yeah, so I would 100% agree that most MSPs, when workloads are static, have great visibility. The problem is that in today’s world, so many workloads are becoming dynamic. And we see that change happening consistently. You know, customers, you know, historically MSPs had problems monitoring services inside of a cloud provider. You have ephemeral workloads, you have workloads that aren’t necessarily a server, they’re much more like a service. So you have things that might be a Kubernetes instance, they might be a Kubernetes runtime instance, they might be a function. Those are all things that are crucial to the operation of a customer. They’ve taken those workloads that historically operated on a machine. And they’ve taken those workloads and now they’re in some type of small form factor instance that exists for a very short period of time. That’s been very difficult for MSPs to deal with across the board. But now we take that same concept and that same concept goes outside of the cloud providers. We now have that moving into inference nodes. We now have that moving into IoT and IIoT and OT, where we’re starting to deal with these ecosystems where these workloads are very ephemeral by nature. They might exist for a short period or components of those might exist for a short period, or the way that those are correlated and analyzed might exist. But if you think about inside of a customer from a business risk perspective, those actually carry the highest business risk. An individual Windows 2012 server has some level of business risk. If it’s running SAP, probably a higher level of business risk. But if it’s one Active Directory node and the customer has 100 machines in Active Directory, it doesn’t really matter in the scheme of the world. And so those are the realities of what happens as we kind of think through this stuff. And so for MSPs, this really drives that visibility gap. You know, we did a survey earlier this year, or actually late last year, sorry, in 2025. We did a survey across the board asking business leaders really what the visibility gap was and what they believed. And we asked business leaders and we also asked IT. It was really interesting to see kind of the dichotomy. When you ask the business what the visibility gap was, it was extremely high. When you ask technology what the visibility gap is, it was really low. Now they were both technically right. And here’s why. So IT was thinking about the visibility gap of the machines that they understand, the machines in their purview. So those might be, you know, an Active Directory server, a database server, maybe you have a web front end. Those are all there. And those are 100% being monitored to that IT team or to that MSP. The problem is, is the business itself is operating on a whole bunch of additional workloads that IT doesn’t necessarily have purview to. And so because of that, we start ending up with this difference of visibility. And that’s why oftentimes when you’ll go and you’ll talk to a customer or you’ll go and you’ll talk to the business itself. And the business is saying, why do we have this MSP who works for us? This MSP isn’t doing anything. And the MSP is coming back with these great reports that are showing MTTR is consistently dropping. You know, initial response time, triage time is consistently dropping. We’re blowing out every single metric that we provided you in an SLA or an SLO. And the business is coming back and saying, but you’re failing. And the MSP is saying, I don’t understand. We are not. And here’s all the metrics. And it’s because of this difference in resources that exist, that is what is happening. And so I think that’s one of the big areas that we always have to think through is, you know, as we’re looking at things and as MSPs look at things, they have to continue to be pushing upward inside of the business to understand all those areas that the business is driving that IT, who they’ve historically sold to, may not know about those resources, especially in a lot of these other spaces, AI, IoT, IIoT, OT, ephemeral workloads, cloud workloads, those types of things that are often outside of that scope. Robert Dutt: Yeah. I guess when you’re looking at sort of your visibility stopping basically at the edge of the organization, you’ve got all of this out there, pretty significant impacts on real world issues like latency, like security exposure, like the ability to meet those SLAs that you signed up for, those kinds of things. Jeff Collins: Yeah. Yeah. 100% agreed. And, you know, when you think about the core components that an MSP does, you know, MSPs generally deal with availability and they deal with performance. When you add in the MSSP, now we add in the security component. And some MSPs and MSSPs are more hybrid-based approaches. They may deal with all three. But as you kind of look at those, those core tenant areas have become much more difficult, especially in the last 10 years, certainly in the last year. I mean, the last year has been so disruptive for all that we do. And it’s because those pieces have become much less simple. You know, if I go back 25 years or even 20 years, customers by and large used MPLS networks, rather simple to monitor. You have guaranteed jitter, you have guaranteed latency, you have, you know, all these things that are very easily assumed by an MSP. So if latency exceeds 74 milliseconds between these two individual locations, that breaks the SLA that the provider provides and it’s an easy conversation. You need to go fix this. This is not okay. Well, in today’s world, most of our customers don’t have MPLS networks. Most of them have, you know, sometimes now it’s satellite. They might have Starlink for LEO. They might have 4G or 5G, depending on what portion of the world they’re in. They might have some type of broadband service, fiber broadband, or copper broadband, or some other type of realm. Well, those don’t necessarily have SLAs for that in any way, shape, or form. We may luck out and they have an availability SLA. Maybe it’s three nines or two nines, or maybe not even two nines, depending on what type of service that is. And then when we start moving inside of the network, outside of the service provider, outside of the circuit provider itself, we start moving into other arenas that look like this. You know, historically we had a Dell server, an HP server that had a mean time before failure. Well, that’s pretty easy to understand. If I have a server and it’s going to run for 25,000 hours, it’s easy to understand that life. But when now we’re starting to get services that have an expected failure, and that expected failure is generally measured in less than a year, because the assumption is that the software, the application, resolves that issue. If you’re an MSP and you’re not monitoring the application and you don’t understand the application, you’re now chasing outages that don’t matter. And that’s one of the other things that’s really hard. And we see this all the time. You know, I’ll talk to MSPs and they’re like, “Jeff,” and it goes back to that same conversation we had before of not knowing the business. “Jeff, we get, today we have 30% of our tickets that become false positives. What do we do about that? We’ve gone out and we’ve bought the newest monitoring platform. We’ve implemented AI. We’ve implemented all this automation. We spent $20 million doing that.” These are all real things that I have in conversations with MSPs. And at the end of the day, they still have 30% false positives that they’re working. And the reality is, is because it’s certainly an outage. There was 100% an outage that happened. But the reality is that outage was never going to get restored because the outage was designed. You know, that workload disappeared. A DevOps team or a DevSecOps team deployed a new environment and that workload is now gone. And there’s a brand new workload that you’re not monitoring right now. You know nothing about it. And those are the things that we all collectively have to continually evolve to. It’s that driving up the stack. You know, one of the things that I often see is, you know, we have this proverbial thing that we’ve all dealt with, the OSI model. You know, there’s seven layers to that OSI model. So often in MSPs, we focus on four of them. The problem is, and most MSPs only focus on the first three. They don’t even focus on the fourth one. The issue is, is there’s three more. And those three more are what get driven by the business. And so the more that we can focus on visibility within those three, understanding that, bringing that into our tools, that drives additional value. It also drives significantly larger margin. You know, if we think about margin contribution at monitoring a telecom circuit, that’s a pretty low margin at this point in time. There’s a lot of automation around that. Monitoring a server – that world used to be high-margin, but it’s compressing. Customers are increasingly doing more of this themselves. They’re doing automation directly into their CI/CD pipeline. So it becomes this knife fight. And there’s more and more MSPs that are out there that are also fighting for that same share of market. And so the key is, the more that MSPs can go up market, they can understand, you know, I hate to use this term digital transformation because it literally gets overused every day by every marketing team on the planet. But the reality is, is that if we go behind this marketing abomination of this term, and we actually look at what happens, there’s a ton of value that we can go after. And if we go after that value, and we go after what people are trying to do, we align with that, we can now take those same products, those same processes that we’ve historically had as MSPs, and we can really start evolving that. Moving upward, driving in significant value, taking our tool sets that we may have today, maybe those can evolve with us, maybe we have to make new changes in our tool sets. But the reality is we’re driving that margin upward. So we’re going from maybe our contribution margin to our business today is 30%, let’s say, we can start moving back up into 60, 70, 80% contribution margin from a managed services perspective, which is where we all want to be. We don’t want to be fighting knife fights for 30%. It’s just hard, it’s difficult. Our customer acquisition costs are still generally high. We have salespeople, we have marketing efforts, we have all those things that we’re burning through every day. And we need more and more market share, we need more and more assets that we’re monitoring. And as a result of that, we need better ways that can contribute higher margin and create stickier customers that we’re not in those knife fights with. Robert Dutt: The situation seems to be putting MSPs in a situation where they’re increasingly accountable for outcomes that they can’t fully see the contributing factors of. Before you move on, I just wanted to double click on that just a little bit and just ask, how does that change kind of the risk profile for an MSP when you’re accountable for those things that you don’t completely understand or have complete control over? Jeff Collins: Yeah, I would say a lot of that. And one of the things that MSPs have to think through is a lot of that starts at the sales cycle. If you don’t ask the right questions at the sales cycle stage, oftentimes you get pushed into that ecosystem. When you’re looking at the core functional plumbing behind what a customer is trying to do, and that’s the only thing you’re looking at, you often get siloed into that ecosystem. You’re looking at a server, you’re not looking at SAP. One server going down in SAP doesn’t necessarily mean SAP has a problem. But if that one server is the only HANA server in SAP, that’s catastrophic. You know, it’s this realm of contextual knowledge. Historically MSPs have that contextual knowledge, but it’s all the way at tier three and tier four. That contextual knowledge has to move to tier one. If MSPs want to get to the arena where that is no longer a problem, the contextual pieces have to move downward. You have to go from a hero-based MSP to a process-driven MSP. So many MSPs are built on heroes. It’s really hard to build a scalable business off heroes. You have to have heroes. Heroes are the people that when everything breaks and the world is on fire, they’re the ones who carry you through. And those heroes we want to have, we want to empower them, but they can’t be doing the stuff that should be done at tier one. So if we take that exact same question that you had, Rob, that question is, you know, how do we make, at the end of the day, how do we make MSPs more relevant to their clients and much more aligned with what the client’s trying to do? And that’s by taking the contextual knowledge of what the customer is trying to do, aligning that with the tactical approaches that the MSP is trying to do, and having a very crystal clear playbook of how this tactical component makes up this strategic initiative inside of the business. So we’ll take that, we’ll take that simple example. I shouldn’t say simple. SAP is far from simple. But the reality is, is that SAP is something that customers rely on. And when they rely on that, if SAP goes down the business goes down. And if you have an MSP that’s monitoring that, and at the same second of the same day, the MSP gets 36 tickets. We’ll just pick a random 36 number. 36 severity one tickets come in at that point in time. One of those severity one tickets is for SAP HANA. And the customer only has one instance of that. And that is taking down a large company. So that’s the first ticket. The next 35 tickets are for ephemeral workloads that the customer migrated off of, you got the alert, they migrated to a brand new ephemeral workload. And the 35 don’t matter. They’re false positives. But the one fully matters. In every single MSP on the planet, those 36 tickets are eligible for the same response interval. That’s a pretty tough average to be able to. Are you going to luck out and get the one? Or are you going to luck out, or not luck out, for lack of a better term, and work 35 false positives before you get to the one that matters? Now, most MSPs are going to tell me and they’re going to tell us that, well, we have more than one tier one path. That’s great. But the reality is you need to be responding to that one ticket right now. And you need to understand that that one ticket matters. And the only way you can do that is by starting at the beginning, starting with the sales cycle, understanding what customers are doing. If you’ve already gone down the path and the customer’s embedded, use your customer support teams. Understand what your customers are doing, start layering in that context, start enriching that data, knowing what that actually feeds, and understanding the dependencies and interdependencies inside of that. So if that server goes down, certainly you could by virtue say a database server going down is a SEV-1, but it may not be. If they have four database servers, they’re running in a high availability group, who cares? If one goes down, not the end of the world, go fix it tomorrow. That’s where context, that’s where understanding those dependencies is so crucial. And I mentioned at the beginning of this is how do you take that first step forward? We always take this first step forward and how I instruct MSPs is start doing things like this, take this step forward, break this down into simple programmatic approaches. And when we think about AI, it’s the exact same idea. We move steps forward, we have agentic, we have generative. Pick one, pick an area you want to focus on with your customers, understand the business outcome they’re trying to do. And if you have an inference engine, that’s going to be really crucially important here. So let’s understand that. Let’s monitor that. Let’s understand the intricacies related to how that customer is leveraging it, why it’s important. Are there latency constraints? Are there packet loss constraints? Those types of things. Let’s monitor to that and let’s understand how that happens. And if a customer has an application on the back end, you know, maybe they have New Relic or they have AppDynamics or they have some type of APM toolset, great. Let’s start bringing those into our monitoring. Let’s start bringing that intelligence in, understanding application flows, understanding dependencies, building that to be part of our story. And now we create so much more opportunity for us as an MSP driving that contribution margin northbound. Robert Dutt: So it sounds like we’re kind of defining good visibility in a modern environment and kind of setting up for looking forward as understanding what actually matters to the customer and understanding what kind of flows into it, what all results in that thing that’s important to the customer still being up, still being running, still being functional, and kind of work backwards from there as opposed to the more “this machine is working, this machine is not” kind of approach. Jeff Collins: Yep. Yeah. You want to go from tactical to transformational. That’s really the idea. Robert Dutt: And you shared kind of the idea of the first step to do towards that. I guess as you’re moving towards that first step, you know, is there any one question or kind of mindset that you find works for MSPs to have in mind or asking customers to surface those blind spots and really start to understand what that context is that they have to have? Jeff Collins: Yeah, that’s a really good question, Rob. And, you know, there’s some things that I do tell MSPs to start with before you ever ask that first question. One of them is kind of some of the simple, let’s call it research that you can do before you ever reach out to your customer. One of the easiest things you can do is start by what industry are they in. You know, in Canada, Canada has a lot of oil and gas, lots and lots of oil and gas companies exist in Canada. And so if you have an oil and gas company, we can start right off the bat with a lot of the things that oil and gas companies live and die with. And we’ll just pick on this one as an example. So oil and gas companies have SCADA networks. They have industrial IoT devices that are out there. They’re processing massive amounts of data. That data may be going into the cloud. It may be going into a data center. It may be going into some type of vault or something like that, depending on what they have. But each one of those are things that, as an MSP, you can start out before you ever ask your customer anything. You know that those are the things that exist in their environment. And you can quickly look and see, well, am I monitoring any of those? Well, no, I’m only monitoring Active Directory. Okay, Active Directory is probably important to the oil and gas company. But if it goes down, do they quit producing oil? The answer is probably no. And so if your answer is ever no, you know right off the bat that you’re not monitoring something that’s strategic to your customer. And so the first thing that you should always think about is, okay, if we have this industry, we should be monitoring the things that are strategic. Well, how do we do that? Well, we start with that one step forward. The first thing we talk to them about is just like when we went out and we sold that initial monitoring of Active Directory, they did it because they didn’t have time for it. There’s no oil and gas company on the planet that has time to be monitoring their SCADA networks. They just don’t. They may tell you that they do, but they don’t. So leverage your relationships, leverage your engagement with them and go after those pieces. Understand, you know, if they’re in AWS IoT Core, understand what that looks like. Understand who’s monitoring that. Understand how DevOps is working within that space. Maybe it’s DevSecOps inside of that environment. Understand that convergence of the teams and then start building a story around, you know, let’s take that on for you. Let’s start changing that. Let’s use the same paradigm that we’ve done, driving MTTR down, driving availability up, driving resolution times down, all those types of things. Let’s bring that into the era of SCADA networks, IoT, our core infrastructure. That’s where we start changing the value inside of our customer engagements. And that’s really where I see a huge opportunity for MSPs across Canada, where you can take that environment, you can take those opportunities you already have, and you can grow them from, you know, maybe you bill that customer $1,000 a month. You can grow it to billing them $20,000 or $30,000 a month, but it’s the most crucial $30,000 they spend. Because, you know, if that offshore environment or that, you know, oil sands environment or whatever it might be within the oil and gas space or in the energy sector, whatever it might be, those things are crucial to their business. And so the more that MSPs can kind of make that step forward, and then also start incorporating AI, every single one of those entities is incorporating AI. They’re incorporating it directly into their pipelines. They’re incorporating it directly into their data pipelines, not just the oil and gas pipelines, but each one of those, the more you can incorporate that, the more you can monitor, the more you can show value of everything that you do amazing as an MSP, that’s really where you start creating that intrinsic strategic value and you get out of that tactical approach. Robert Dutt: And the good news is for a lot of these folks in the MSP space, presumably they have some of these pieces already in place, just not necessarily connected up to the technical side, i.e. sales and marketing have been focused on a vertical. And even if they haven’t, because they have customers in this space, they’ve built some of that muscle memory, some of that knowledge of what really matters. Now it’s just a matter, hopefully, of connecting it into the services that they’re offering. Jeff Collins: Yep, totally agreed. Robert Dutt: All right. Well, it’s been a really interesting look at sort of where visibility is at. And I think a real interesting opportunity that you’ve surfaced in terms of how it can be turned into a value conversation. I appreciate your taking the time. Jeff Collins: Sounds great. Thanks so much for having me on, Rob. Robert Dutt: There you have it, my chat with Jeff Collins from WanAware. I’d like to thank Jeff for sharing his insights. The thing that stuck with me from this conversation is how much of what’s changed in the modern network hasn’t been designed in, it’s been bolted on. AI workloads, hybrid architectures, IoT, SCADA, all of it layered into environments without the kind of formal rethinking that happened when we moved to virtualization. And Jeff made a really compelling case that for MSPs, closing that visibility gap isn’t just a risk management play, it’s a revenue opportunity, and potentially a significant one, especially in verticals like energy and critical infrastructure where visibility is tied directly to uptime, safety, and compliance. We’ll be back on Monday with In Case You Missed It, your weekly news roundup. Thanks for listening. I’m Robert Dutt for ChannelBuzz.ca, and I’ll see you in the channel.

BUONASERA REGAZZ!Abbiamo appena finito con questa prima stagione di "A Knight of the Sev... Nine Kingdoms" che veniamo travolti già dal primo teaser trailer della terza stagione di "House of the Dragon".In questa live conclusiva, che farà anche da apripista alle accesissime discussioni su HotD, tireremo le somme su AKOTSK e il suo adattamento su schermo e commenteremo insieme a un ospite speciale le immagini del nuovo teaser trailer.Per chi non la conoscesse, Chiara Giovannini è "la vostra crazy fangirl di quartiere" e ha anche incontrato il cast di entrambe le serie tv di cui parleremo in live!Avrete l'occasione quindi di chiederle in chat in diretta delle sue esperienze sul red carpet ;)Potete trovarci su tutti gli altri social con i link qua sotto:Facebook: https://www.facebook.com/tronodispadepod/Twitter: https://twitter.com/tronodispadepodInstagram: https://www.instagram.com/tronodispadepod/Spotify: https://open.spotify.com/show/4mdslx4Nd8vunpc7nP3B45Google Podcast: https://www.google.com/podcasts?feed=aHR0cHM6Ly9hbmNob3uZm0vcy81MDk3ZTk4OC9wb2RjYXN0L3Jzcw==Patreon: https://www.patreon.com/ilpodcastdelghiaccioedelfuocoKo-fi: https://ko-fi.com/ilpodcastdelghiaccioedelfuocoLinkt.ree: https://linktr.ee/ilpodcastdelghiaccioedelfuocoPotete trovare la nostra ospite qua sotto: - https://www.instagram.com/chiarigiovannini/- https://www.tiktok.com/@chiarigiovannini?_r=1&_t=ZN-94MLAgIy28U

Episode #414 of BGMania: A Video Game Music Podcast. Today on the show, Bryan and returning special guest Kyle step into the Care Center to have an in-depth discussion and review analysis on the recently released Resident Evil Requiem. The latest game in this crazy successful series from Capcom, Requiem explores the story of newcomer Grace Ashcroft and the returning Leon Kennedy as they become entangled in a new investigation connected to mysterious deaths among survivors of the Raccoon City incident years prior. During the episode, the guys break down the game in full and offer up their thoughts and opinions on the setting, narrative, characters, soundtrack, and so much more. At the end, they attempt to rank the game up against the previous entries as best as possible, while also providing an official review score. Join us for a spooky and tense fun time, and in the words of longtime non-listener and Discord veteran Sev.. you too can play this game! Email the show at bgmaniapodcast@gmail.com with requests for upcoming episodes, questions, feedback, comments, concerns, or any other thoughts you'd like to share! Special thanks to our Executive Producers: Jexak, Xancu, Jeff, & Mike. EPISODE PLAYLIST AND CREDITS Foreboding from Resident Evil Requiem [Nao Sato, 2026] Night Haze from Resident Evil Requiem [Masahiro Ohki, 2026] Recurring Nightmare from Resident Evil Requiem [Nao Sato, 2026] Deadly Encounter from Resident Evil Requiem [Nao Sato & Masahiro Ohki, 2026] Burst Their Heads from Resident Evil Requiem [Masahiro Ohki, 2026] Baptism by Blood from Resident Evil Requiem [Nao Sato, 2026] Tangled Web from Resident Evil Requiem [Snakes of Russia, 2026] Indomitable from Resident Evil Requiem [Nao Sato & Masahiro Ohki, 2026] Over Capacity from Resident Evil Requiem [Masahiro Ohki, 2026] Memories from Resident Evil Requiem [Masami Ueda, 2026] Night Terrors from Resident Evil Requiem [Shigeyuki Kameda, 2026] Contact from Resident Evil Requiem [Snakes of Russia, 2026] Ambition from Resident Evil Requiem [Nao Sato, 2026] Through the Darkness from Resident Evil Requiem [Nao Sato feat. Colin & Caroline, 2026] LINKS Patreon: https://patreon.com/bgmania Website: https://bgmania.podbean.com/ Discord: https://discord.gg/cC73Heu Facebook: BGManiaPodcast X: BGManiaPodcast Instagram: BGManiaPodcast TikTok: BGManiaPodcast YouTube: BGManiaPodcast Twitch: BGManiaPodcast PODCAST NETWORK Very Good Music: A VGM Podcast Listening Religiously

Station: 101.1 FM WBRU 360 & the WBRU360 AppOn this show, we are joined by Vladimir Jean a.k.a Jean who talks about Afroverse a brand rooted in community and expression. He tells us all about how his staple poetry night started and where he wants to take things. Then you know Sev had to get all up in his love business so we gave us his love report.Plus, don't miss The Love Report with this week's topic: Vlad's takes on privacy and the fear of love It's The Mid-Day Spark Up. Your weekly midday check-in where culture, conversation, and community collide. Hosted by Cristina Sev and co-hosted by DJ Franchise, this show brings real talk, good energy, and unfiltered perspectives.Week #188, from popular news, to world news, local headlines, love, new england creatives & entrepreneurs, new music & then someWhether you're listening in the car, at work, at home, or anywhere across the country, this is your reminder to pause, spark your mind, and stay grounded.Tune in every Tuesday Live 12 PM to 1 PM from Providence, RI on 101.1 FM WBRU360Stream on The Website: https://www.wbru.com/ Download The WBRU app on an iPhone: https://apps.apple.com/us/app/wbru/id1274238066 Download The WBRU app on an Android: https://play.google.com/store/apps/details?id=com.wbru&pcampaignid=web_shareFollow Cristina on Instagram: https://www.instagram.com/cristinasev_?igsh=enFkemc2MXAxOWx2 Follow Cristina on Tik Tok: https://www.tiktok.com/@cristinasev_?_r=1&_t=ZP-931QjkCHb7X Follow DJ Franchise on Instagram: https://www.instagram.com/djfranchise1?igsh=anptNXh6bTE3am9k Follow DJ Franchise on TikTok: https://www.tiktok.com/@djfranchise1?_r=1&_t=ZP-931Qmux6s3DFollow Vlad on Instagram:https://www.instagram.com/vladimirjean/Follow Afroverse on Instagram: https://www.instagram.com/afroversepvd/ or vist: afroversepvd.comContact For Inquiries: afroverse@icloud.com

Never Give Up! In this inspiring episode, Terri sits down with TEDx speaker, author, and resilience mentor Sev Joy Dumaisnil for a powerful conversation about resilience, reinvention, and finding purpose after life's hardest seasons.Sev is beautiful inside and out.Her journey began in an orphanage in communist Poland. But instead of allowing her past to define her, Sev chose a different path - one rooted in courage, personal growth, and service.Today she is a TEDx speaker, mentor, and author helping women (and men) rediscover their voice, step into leadership, and create a life of meaning and joy.In this episode we talk about:• How Sev transformed her darkest moments into purpose• The mindset shift that helped her rise from adversity• Why your past does not define your future• Finding your voice and stepping into your next chapter• How small steps can lead to profound transformationIf you are navigating a difficult season, reinventing yourself in midlife, or searching for deeper purpose, this conversation will remind you that your story is not the end - it may be the beginning of your greatest impact.✨ Sev's message is simple but powerful:You are not defined by your past. You are shaped by the meaning you choose to give it.CONNECT WITH SEV:LinkedInFacebookFree Gift – R.E.N.E.W. Roadmap + Guided MeditationPrivate Mentoring Inquiry Link WebsiteSev's Book:  Never Give Up and Live the Life of Your DreamsTed Talk : Finding Joy in the Darkest MomentsCONNECT WITH TERRI:Terri's WebsiteTerri's Book - Step ForwardFacebookKeep Stepping Forward!

Sev Ohanian is an Armenian American immigrant who became one of the most talked about producers in the industry. From home-made humorous films about Armenians to making Oscar history with 16 Academy Award Nominations, including Best Picture. He also won major awards like Sundance Institute Producer of the Year Award and Golden Globe for Best Cinematic and Box Office Achievement for Sinners. From indie beginnings to producing record breaking films, Sev's journey is all about creativity, resilience, passion & great partnerships.

How do you scale a coaching business to over 140 clients while still working a full-time trade? Richard Detering joins Sev on the show to reveal the backend of Richard's Muscle Lab. This episode is a must-watch for creators and business owners looking to understand the difference between "The Journeyman" and "The Educator" content strategies.Richard shares his experience getting burned by a $30,000 marketing agency and why organic trust will always beat paid ads in the long run. We discuss the power of collaboration, hiring the right team, and why being unapologetically yourself is the ultimate competitive advantage in a crowded market. Learn how to use keywords, hooks, and authenticity to dominate your niche and build a brand that resonates.Enjoyed this deep dive? Like, comment, and subscribe to The Sevo Show for more inspiring conversations. Let us know your biggest takeaway in the comments and share this video with someone who needs a dose of FIFO optimisation.Follow Richard:Instagram: https://www.instagram.com/ric_hyy/Website: https://richardsmusclelab.com/Follow me:https://www.instagram.com/sevspics/https://www.instagram.com/thesevoshow/Hire the Studio and Production Team:https://brighttsar.com/Sponsors:https://www.whereu.com.au/

Sev began as a rap artist and now has evolved into one of the most recognized actors in the independent film community. Sev relates memorizing lines for movies to memorizing the rhymes that made him an exceptional lyricist. Shad talks to him about his journey so far in the industry and what his fans can expect from him in the future! Tap in at www.eblockradio.com and EVERYWHERE you stream your favorite podcasts.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Provozovatel přenosové soustavy ČEPS doporučuje, aby se dočasně zachoval provoz poloviny bloků uhelné elektrárny Chvaletice. Přestože energetická skupina Sev.en oznámila, že se jí zdroj už nevyplatí provozovat. „V oblasti Chvaletic jsou zatím bohužel problémy s řízením napětí toku jalového výkonu,“ vysvětluje v Pro a proti Michal Macenauer z poradenské společnosti EGU. Jan Krčál z think-tanku Fakta o klimatu souhlasí: „Toto jsme neposuzovali a jsem rád, že to ČEPS vysvětlil.“Všechny díly podcastu Pro a proti můžete pohodlně poslouchat v mobilní aplikaci mujRozhlas pro Android a iOS nebo na webu mujRozhlas.cz.

Je potřeba zachovat v provozu polovinu uhelné elektrárny Chvaletice. Hnědouhelné zdroje v Počeradech a na Kladně může jejich majitel, firma Sev.en Pavla Tykače, příští rok klidně zavřít, zní stanovisko státního správce energetické soustavy ČEPS. Reagoval tím na nedávné oznámení firmy, že se jí provoz starých uhelných elektráren nevyplácí a chystá se je vypnout. Bude mít Česko dost elektřiny i v zimě? Jana Klímová se ptala Svatopluka Vnoučka, místopředsedy představenstva ČEPS.

Je potřeba zachovat v provozu polovinu uhelné elektrárny Chvaletice. Hnědouhelné zdroje v Počeradech a na Kladně může jejich majitel, firma Sev.en Pavla Tykače, příští rok klidně zavřít, zní stanovisko státního správce energetické soustavy ČEPS. Reagoval tím na nedávné oznámení firmy, že se jí provoz starých uhelných elektráren nevyplácí a chystá se je vypnout. Bude mít Česko dost elektřiny i v zimě? Jana Klímová se ptala Svatopluka Vnoučka, místopředsedy představenstva ČEPS.Všechny díly podcastu Dvacet minut Radiožurnálu můžete pohodlně poslouchat v mobilní aplikaci mujRozhlas pro Android a iOS nebo na webu mujRozhlas.cz.

S Ondrášem Přibylou o výsledcích nového modelování elektrické soustavy bez Chvaletic a Počerad od Fakt o klimatu, zbavování závilosti na fosilních zdrojích, světové elektrotechnické revoluci, roli petrostátů i třetím nejteplejším roce v historii měření. Moderuje Štěpán Sedláček.Minulá vláda stanovila odklon od spalování uhlí na rok 2033. Ale potvrzují se odhady řady analytiků, kteří tvrdili, že k tomu může dojí významně dřív mimo jiné pod tlakem rostoucí ceny emisních povolenek a rychlého rozvoje obnovitelných zdrojů. Při aktuální ceně povolenky, která přesahuje 90 €/MWh, je levnější vyrábět energii v plynových elektrárnách. České uhelné zdroje tak přijdou na řadu, jen když jaderné elektrárny a OZE nepokryjí spotřebu a po většinu roku by bylo levnější elektřinu do Česka dovážet než ji získávat ze spalování hnědého uhlí. CNa sklonku loňského roku oznámila firma Sev.en Pavla Tykače plán ukončit hnědouhelných elektráren Chvaletice, Počerady a teplárny Kladno, jejichž provoz se přestává vyplácet. Nová analýza organizace Fakta o klimatu ukazuje, že vypnutí uvedených elektráren by nemělo v Česku ohrozit dodávky elektřiny a na její ceně se podepsat jen minimálně. To vyplynulo na základě modelování české a evropské energetické soustavy. Podle zakladatele a vedoucího Fakt o klimatu Ondřáše Přibyly tak ekonomicky nedává smysl chod Tykačových elektráren dotovat. Jak rychle Česko může odpojit dalších uhelné zdroje a čím je nahradí? A jak zásadní roli mají v kontextu všech českých emisí skleníkových plynů? A jak se jeví postupující vývoj ohřívání planety a snahy ho zastavit s ohledem na dění ve světě? Nejen o tom mluví nad novou knihou Atlas dekarbonizace Česka (Fakta o klimatu, 2025) Ondráš Přibyla v dalším čtení s Respektem.K poslechu doporučujeme také: Úplně bez uhlí to ještě Česko pár let nezvládne. Ale ne kvůli výrobě elektřinyDiskutovaná analýza: Konec uhlí v ČeskuJe soustava připravena na uzavření zdrojů skupiny Sev.en a co zbývá vyřešit pro bezpečný útlum uhelné energetiky?Odkaz na Atlas v pdf a související online kurz: Atlas dekarbonizace ČeskaDoporučený zdroj s dalšími informacemi k tématu od Ondráše Přibyly: The Electrotech Revolution | Ember

Welcome to the latest episode of Harmonious World, where I interview musicians about how their music helps make the world more harmonious.Pianist Øystein Sevåg and I discussed his new album, Lacrimosa, which I reviewed a few weeks ago.Thanks to Øystein for allowing me to use clips from Lacrimosa alongside our conversation.Get in touch to let me know what you think!Thank you for listening to Harmonious World. Please rate, review and share: click on the link and subscribe to support the show.Don't forget the Quincy Jones quote that sums up why I do this: "Imagine what a harmonious world it would be if every single person, both young and old, shared a little of what he is good at doing."Support the showRead reviews of albums and gigs and find out more about me at hilaryseabrook.co.ukFollow me on instagram.com/hilseabrookFollow me on facebook.com/HilarySeabrookFreelanceWriterFollow me on twitter.com/hilaryrwriter

This one's a true Sesh, we're hanging with Sev from Clean Torch and letting the convo bounce between the “why” and the “how.” Sev Isayan breaks down what it really looks like to build a physical product from scratch, five years of R&D, dialing heat-up time, battery life, materials, and the pain of trying to prototype without getting financially suplexed.Then we go full Sev mode, martial arts since he was a kid, Navy chapter, rolling and getting humbled, plus the plot twist, he also runs a spot in Glendale called Asahi Grill where the whole vibe is “real ingredients only,” grass fed, butter, beef tallow, no seed oils.And yeah, we still nerd out on the device, windproof, elevation-proof, 510 thread head, what battery you actually need, plus the new sleeve and Sev's dream collab, Clean Torch x Supreme.What we get into:The long game, Sev's “I'm not dropping it until it's perfect” mindset (heat-up speed, max temp behavior, battery life, materials)  The reality of manufacturing, prototypes, cost barriers, and why time is the hidden price tag  Patents, timing, luck, and the one connection that changes the whole trajectory  Sev's personal ritual, morning routine, bongs, filtration, and chasing “as clean as possible”  Flavor talk and why Sev leans indica/hybrid (and why sativa doesn't hit for him)  Asahi Grill, why he opened it, and the ingredient standards most places won't touchClean Torch specifics, what it does (ignite + vaporize), windproof, elevation-proof, and why the battery mattersSev's “hidden hobby” confession, Supreme obsession and the dream collab  Get yourself a Clean TorchSave on Dr Dabber with Code: Cannabisschool10Save on Storz & Bickel with Code : CannabisschoolSave on Santa Cruz Shredder with Code: CSP10Save on Bomb Erigs with Code: CSPScore 100 on your test

TLDR: It was Claude :-)When I set out to compare ChatGPT, Claude, Gemini, Grok, and ChatPRD for writing Product Requirement Documents, I figured they'd all be roughly equivalent. Maybe some subtle variations in tone or structure, but nothing earth-shattering. They're all built on similar transformer architectures, trained on massive datasets, and marketed as capable of handling complex business writing.What I discovered over 45 minutes of hands-on testing revealed not just which tools are better for PRD creation, but why they're better, and more importantly, how you should actually be using AI to accelerate your product work without sacrificing quality or strategic thinking.If you're an early or mid-career PM in Silicon Valley, this matters to you. Because here's the uncomfortable truth: your peers are already using AI to write PRDs, analyze features, and generate documentation. The question isn't whether to use these tools. The question is whether you're using the right ones most effectively.So let me walk you through exactly what I did, what I learned, and what you should do differently.The Setup: A Real-World Test CaseHere's how I structured the experiment. As I said at the beginning of my recording, “We are back in the Fireside PM podcast and I did that review of the ChatGPT browser and people seemed to like it and then I asked, uh, in a poll, I think it was a LinkedIn poll maybe, what should my next PM product review be? And, people asked for ChatPRD.”So I had my marching orders from the audience. But I wanted to make this more comprehensive than just testing ChatPRD in isolation. I opened up five tabs: ChatGPT, Claude, Gemini, Grok, and ChatPRD.For the test case, I chose something realistic and relevant: an AI-powered tutor for high school students. Think KhanAmigo or similar edtech platforms. This gave me a concrete product scenario that's complex enough to stress-test these tools but straightforward enough that I could iterate quickly.But here's the critical part that too many PMs get wrong when they start using AI for product work: I didn't just throw a single sentence at these tools and expect magic.The “Back of the Napkin” Approach: Why You Still Need to Think“I presume everybody agrees that you should have some formulated thinking before you dump it into the chatbot for your PRD,” I noted early in my experiment. “I suppose in the future maybe you could just do, like, a one-sentence prompt and come out with the perfect PRD because it would just know everything about you and your company in the context, but for now we're gonna do this more, a little old-school AI approach where we're gonna do some original human thinking.”This is crucial. I see so many PMs, especially those newer to the field, treat AI like a magic oracle. They type in “Write me a PRD for a social feature” and then wonder why the output is generic, unfocused, and useless.Your job as a PM isn't to become obsolete. It's to become more effective. And that means doing the strategic thinking work that AI cannot do for you.So I started in Google Docs with what I call a “back of the napkin” PRD structure. Here's what I included:Why: The strategic rationale. In this case: “Want to complement our existing edtech business with a personalized AI tutor, uh, want to maintain position industry, and grow through innovation. on mission for learners.”Target User: Who are we building for? “High school students interested in improving their grades and fundamentals. Fundamental knowledge topics. Specifically science and math. Students who are not in the top ten percent, nor in the bottom ten percent.”This is key—I got specific. Not just “students,” but students in the middle 80%. Not just “any subject,” but science and math. This specificity is what separates useful AI output from garbage.Problem to Solve: What's broken? “Students want better grades. Students are impatient. Students currently use AI just for finding the answers and less to, uh, understand concepts and practice using them.”Key Elements: The feature set and approach.Success Metrics: How we'd measure success.Now, was this a perfectly polished PRD outline? Hell no. As you can see from my transcript, I was literally thinking out loud, making typos, restructuring on the fly. But that's exactly the point. I put in maybe 10-15 minutes of human strategic thinking. That's all it took to create a foundation that would dramatically improve what came out of the AI tools.Round One: Generating the Full PRDWith my back-of-the-napkin outline ready, I copied it into each tool with a simple prompt asking them to expand it into a more complete PRD.ChatGPT: The Reliable GeneralistChatGPT gave me something that was... fine. Competent. Professional. But also deeply uninspiring.The document it produced checked all the boxes. It had the sections you'd expect. The writing was clear. But when I read it, I couldn't shake the feeling that I was reading something that could have been written for literally any product in any company. It felt like “an average of everything out there,” as I noted in my evaluation.Here's what ChatGPT did well: It understood the basic structure of a PRD. It generated appropriate sections. The grammar and formatting were clean. If you needed to hand something in by EOD and had literally no time for refinement, ChatGPT would save you from complete embarrassment.But here's what it lacked: Depth. Nuance. Strategic thinking that felt connected to real product decisions. When it described the target user, it used phrases that could apply to any edtech product. When it outlined success metrics, they were the obvious ones (engagement, retention, test scores) without any interesting thinking about leading indicators or proxy metrics.The problem with generic output isn't that it's wrong, it's that it's invisible. When you're trying to get buy-in from leadership or alignment from engineering, you need your PRD to feel specific, considered, and connected to your company's actual strategy. ChatGPT's output felt like it was written by someone who'd read a lot of PRDs but never actually shipped a product.One specific example: When I asked for success metrics, ChatGPT gave me “Student engagement rate, Time spent on platform, Test score improvement.” These aren't wrong, but they're lazy. They don't show any thinking about what specifically matters for an AI tutor versus any other educational product. Compare that to Claude's output, which got more specific about things like “concept mastery rate” and “question-to-understanding ratio.”Actionable Insight: Use ChatGPT when you need fast, serviceable documentation that doesn't need to be exceptional. Think: internal updates, status reports, routine communications. Don't rely on it for strategic documents where differentiation matters. If you do use ChatGPT for important documents, treat its output as a starting point that needs significant human refinement to add strategic depth and company-specific context.Gemini: Better Than ExpectedGoogle's Gemini actually impressed me more than I anticipated. The structure was solid, and it had a nice balance of detail without being overwhelming.What Gemini got right: The writing had a nice flow to it. The document felt organized and logical. It did a better job than ChatGPT at providing specific examples and thinking through edge cases. For instance, when describing the target user, it went beyond demographics to consider behavioral characteristics and motivations.Gemini also showed some interesting strategic thinking. It considered competitive positioning more thoughtfully than ChatGPT and proposed some differentiation angles that weren't in my original outline. Good AI tools should add insight, not just regurgitate your input with better formatting.But here's where it fell short: the visual elements. When I asked for mockups, Gemini produced images that looked more like stock photos than actual product designs. They weren't terrible, but they weren't compelling either. They had that AI-generated sheen that makes it obvious they came from an image model rather than a designer's brain.For a PRD that you're going to use internally with a team that already understands the context, Gemini's output would work well. The text quality is strong enough, and if you're in the Google ecosystem (Docs, Sheets, Meet, etc.), the integration is seamless. You can paste Gemini's output directly into Google Docs and continue iterating there.But if you need to create something compelling enough to win over skeptics or secure budget, Gemini falls just short. It's good, but not great. It's the solid B+ student: reliably competent but rarely exceptional.Actionable Insight: Gemini is a strong choice if you're working in the Google ecosystem and need good integration with Docs, Sheets, and other Google Workspace tools. The quality is sufficient for most internal documentation needs. It's particularly good if you're working with cross-functional partners who are already in Google Workspace. You can share and collaborate on AI-generated drafts without friction. But don't expect visual mockups that will wow anyone, and plan to add your own strategic polish for high-stakes documents.Grok: Not Ready for Prime TimeLet's just say my expectations were low, and Grok still managed to underdeliver. The PRD felt thin, generic, and lacked the depth you need for real product work.“I don't have high expectations for grok, unfortunately,” I said before testing it. Spoiler alert: my low expectations were validated.Actionable Insight: Skip Grok for product documentation work right now. Maybe it'll improve, but as of my testing, it's simply not competitive with the other options. It felt like 1-2 years behind the others.ChatPRD: The Specialized ToolNow this was interesting. ChatPRD is purpose-built for PRDs, using foundational models underneath but with specific tuning and structure for product documentation.The result? The structure was logical, the depth was appropriate, and it included elements that showed understanding of what actually matters in a PRD. As I reflected: “Cause this one feels like, A human wrote this PRD.”The interface guides you through the process more deliberately than just dumping text into a general chat interface. It asks clarifying questions. It structures the output more thoughtfully.Actionable Insight: If you're a technical lead without a dedicated PM, or you're a PM who wants a more structured approach to using AI for PRDs, ChatPRD is worth the specialized focus. It's particularly good when you need something that feels authentic enough to share with stakeholders without heavy editing.Claude: The Clear WinnerBut the standout performer, and I'm ranking these, was Claude.“I think we know that for now, I'm gonna say Claude did the best job,” I concluded after all the testing. Claude produced the most comprehensive, thoughtful, and strategically sound PRD. But what really set it apart were the concept mocks.When I asked each tool to generate visual mockups of the product, Claude produced HTML prototypes that, while not fully functional, looked genuinely compelling. They had thoughtful UI design, clear information architecture, and felt like something that could actually guide development.“They were, like, closer to, like, what a Lovable would produce or something like that,” I noted, referring to the quality of low-fidelity prototypes that good designers create.The text quality was also superior: more nuanced, better structured, and with more strategic depth. It felt like Claude understood not just what a PRD should contain, but why it should contain those elements.Actionable Insight: For any PRD that matters, meaning anything you'll share with leadership, use to get buy-in, or guide actual product development, you might as well start with Claude. The quality difference is significant enough that it's worth using Claude even if you primarily use another tool for other tasks.Final Rankings: The Definitive HierarchyAfter testing all five tools on multiple dimensions: initial PRD generation, visual mockups, and even crafting a pitch paragraph for a skeptical VP of Engineering, here's my final ranking:* Claude - Best overall quality, most compelling mockups, strongest strategic thinking* ChatPRD - Best for structured PRD creation, feels most “human”* Gemini - Solid all-around performance, good Google integration* ChatGPT - Reliable but generic, lacks differentiation* Grok - Not competitive for this use case“I'd probably say Claude, then chat PRD, then Gemini, then chat GPT, and then Grock,” I concluded.The Deeper Lesson: Garbage In, Garbage Out (Still Applies)But here's what matters more than which tool wins: the realization that hit me partway through this experiment.“I think it really does come down to, like, you know, the quality of the prompt,” I observed. “So if our prompt were a little more detailed, all that were more thought-through, then I'm sure the output would have been better. But as you can see we didn't really put in brain trust prompting here. Just a little bit of, kind of hand-wavy prompting, but a little better than just one or two sentences.”And we still got pretty good results.This is the meta-insight that should change how you approach AI tools in your product work: The quality of your input determines the quality of your output, but the baseline quality of the tool determines the ceiling of what's possible.No amount of great prompting will make Grok produce Claude-level output. But even mediocre prompting with Claude will beat great prompting with lesser tools.So the dual strategy is:* Use the best tool available (currently Claude for PRDs)* Invest in improving your prompting skills ideally with as much original and insightful human, company aware, and context aware thinking as possible.Real-World Workflows: How to Actually Use This in Your Day-to-Day PM WorkTheory is great. Here's how to incorporate these insights into your actual product management workflows.The Weekly Sprint Planning WorkflowEvery PM I know spends hours each week preparing for sprint planning. You need to refine user stories, clarify acceptance criteria, anticipate engineering questions, and align with design and data science. AI can compress this work significantly.Here's an example workflow:Monday morning (30 minutes):* Review upcoming priorities and open your rough notes/outline in Google Docs* Open Claude and paste your outline with this prompt:“I'm preparing for sprint planning. Based on these priorities [paste notes], generate detailed user stories with acceptance criteria. Format each as: User story, Business context, Technical considerations, Acceptance criteria, Dependencies, Open questions.”Monday afternoon (20 minutes):* Review Claude's output critically* Identify gaps, unclear requirements, or missing context* Follow up with targeted prompts:“The user story about authentication is too vague. Break it down into separate stories for: social login, email/password, session management, and password reset. For each, specify security requirements and edge cases.”Tuesday morning (15 minutes):* Generate mockups for any UI-heavy stories:“Create an HTML mockup for the login flow showing: landing page, social login options, email/password form, error states, and success redirect.”* Even if the HTML doesn't work perfectly, it gives your designers a starting pointBefore sprint planning (10 minutes):* Ask Claude to anticipate engineering questions:“Review these user stories as if you're a senior engineer. What questions would you ask? What concerns would you raise about technical feasibility, dependencies, or edge cases?”* This preparation makes you look thoughtful and helps the meeting run smoothlyTotal time investment: ~75 minutes. Typical time saved: 3-4 hours compared to doing this manually.The Stakeholder Alignment WorkflowGetting alignment from multiple stakeholders (product leadership, engineering, design, data science, legal, marketing) is one of the hardest parts of PM work. AI can help you think through different stakeholder perspectives and craft compelling communications for each.Here's how:Step 1: Map your stakeholders (10 minutes)Create a quick table in a doc:Stakeholder | Primary Concern | Decision Criteria | Likely Objections VP Product | Strategic fit, ROI | Company OKRs, market opportunity | Resource allocation vs other priorities VP Eng | Technical risk, capacity | Engineering capacity, tech debt | Complexity, unclear requirements Design Lead | User experience | User research, design principles | Timeline doesn't allow proper design process Legal | Compliance, risk | Regulatory requirements | Data privacy, user consent flowsStep 2: Generate stakeholder-specific communications (20 minutes)For each key stakeholder, ask Claude:“I need to pitch this product idea to [Stakeholder]. Based on this PRD, create a 1-page brief addressing their primary concern of [concern from your table]. Open with the specific value for them, address their likely objection of [objection], and close with a clear ask. Tone should be [professional/technical/strategic] based on their role.”Then you'll have customized one-pagers for your pre-meetings with each stakeholder, dramatically increasing your alignment rate.Step 3: Synthesize feedback (15 minutes)After gathering stakeholder input, ask Claude to help you synthesize:“I got the following feedback from stakeholders: [paste feedback]. Identify: (1) Common themes, (2) Conflicting requirements, (3) Legitimate concerns vs organizational politics, (4) Recommended compromises that might satisfy multiple parties.”This pattern-matching across stakeholder feedback is something AI does really well and saves you hours of mental processing.The Quarterly Planning WorkflowQuarterly or annual planning is where product strategy gets real. You need to synthesize market trends, customer feedback, technical capabilities, and business objectives into a coherent roadmap. AI can accelerate this dramatically.Six weeks before planning:* Start collecting input (customer interviews, market research, competitive analysis, engineering feedback)* Don't wait until the last minuteFour weeks before planning:Dump everything into Claude with this structure:“I'm creating our Q2 roadmap. Context:* Business objectives: [paste from leadership]* Customer feedback themes: [paste synthesis]* Technical capabilities/constraints: [paste from engineering]* Competitive landscape: [paste analysis]* Current product gaps: [paste from your analysis]Generate 5 strategic themes that could anchor our Q2 roadmap. For each theme:* Strategic rationale (how it connects to business objectives)* Key initiatives (2-3 major features/projects)* Success metrics* Resource requirements (rough estimate)* Risks and mitigations* Customer segments addressed”This gives you a strategic framework to react to rather than starting from a blank page.Three weeks before planning:Iterate on the most promising themes:“Deep dive on Theme 3. Generate:* Detailed initiative breakdown* Dependencies on platform/infrastructure* Phasing options (MVP vs full build)* Go-to-market considerations* Data requirements* Open questions requiring research”Two weeks before planning:Pressure-test your thinking:“Play devil's advocate on this roadmap. What are the strongest arguments against each initiative? What am I likely missing? What failure modes should I plan for?”This adversarial prompting forces you to strengthen weak points before your leadership reviews it.One week before planning:Generate your presentation:“Create an executive presentation for this roadmap. Structure: (1) Market context and strategic imperative, (2) Q2 themes and initiatives, (3) Expected outcomes and metrics, (4) Resource requirements, (5) Key risks and mitigations, (6) Success criteria for decision. Make it compelling but data-driven. Tone: confident but not overselling.”Then add your company-specific context, visual brand, and personal voice.The Customer Research WorkflowAI can't replace talking to customers, but it can help you prepare better questions, analyze feedback more systematically, and identify patterns faster.Before customer interviews:“I'm interviewing customers about [topic]. Generate:* 10 open-ended questions that avoid leading the witness* 5 follow-up questions for each main question* Common cognitive biases I should watch for* A framework for categorizing responses”This prep work helps you conduct better interviews.After interviews:“I conducted 15 customer interviews. Here are the key quotes: [paste anonymized quotes]. Identify:* Recurring themes and patterns* Surprising insights that contradict our assumptions* Segments with different needs* Implied needs customers didn't articulate directly* Recommended next steps for validation”AI is excellent at pattern-matching across qualitative data at scale.The Crisis Management WorkflowSomething broke. The site is down. Data was lost. A feature shipped with a critical bug. You need to move fast.Immediate response (5 minutes):“Critical incident. Details: [brief description]. Generate:* Incident classification (Sev 1-4)* Immediate stakeholders to notify* Draft customer communication (honest, apologetic, specific about what happened and what we're doing)* Draft internal communication for leadership* Key questions to ask engineering during investigation”Having these drafted in 5 minutes lets you focus on coordination and decision-making rather than wordsmithing.Post-incident (30 minutes):“Write a post-mortem based on this incident timeline: [paste timeline]. Include:* What happened (technical details)* Root cause analysis* Impact quantification (users affected, revenue impact, time to resolution)* What went well in our response* What could have been better* Specific action items with owners and deadlines* Process changes to prevent recurrence Tone: Blameless, focused on learning and improvement.”This gives you a strong first draft to refine with your team.Common Pitfalls: What Not to Do with AI in Product ManagementNow let's talk about the mistakes I see PMs making with AI tools. Pitfall #1: Treating AI Output as FinalThe biggest mistake is copy-pasting AI output directly into your PRD, roadmap presentation, or stakeholder email without critical review.The result? Documents that are grammatically perfect but strategically shallow. Presentations that sound impressive but don't hold up under questioning. Emails that are professionally worded but miss the subtext of organizational politics.The fix: Always ask yourself:* Does this reflect my actual strategic thinking, or generic best practices?* Would my CEO/engineering lead/biggest customer find this compelling and specific?* Are there company-specific details, customer insights, or technical constraints that only I know?* Does this sound like me, or like a robot?Add those elements. That's where your value as a PM comes through.Pitfall #2: Using AI as a Crutch Instead of a ToolSome PMs use AI because they don't want to think deeply about the product. They're looking for AI to do the hard work of strategy, prioritization, and trade-off analysis.This never works. AI can help you think more systematically, but it can't replace thinking.If you find yourself using AI to avoid wrestling with hard questions (”Should we build X or Y?” “What's our actual competitive advantage?” “Why would customers switch from the incumbent?”), you're using it wrong.The fix: Use AI to explore options, not to make decisions. Generate three alternatives, pressure-test each one, then use your judgment to decide. The AI can help you think through implications, but you're still the one choosing.Pitfall #3: Not IteratingGetting mediocre AI output and just accepting it is a waste of the technology's potential.The PMs who get exceptional results from AI are the ones who iterate. They generate an initial response, identify what's weak or missing, and ask follow-up questions. They might go through 5-10 iterations on a key section of a PRD.Each iteration is quick (30 seconds to type a follow-up prompt, 30 seconds to read the response), but the cumulative effect is dramatically better output.The fix: Budget time for iteration. Don't try to generate a complete, polished PRD in one prompt. Instead, generate a rough draft, then spend 30 minutes iterating on specific sections that matter most.Pitfall #4: Ignoring the Political and Human ContextAI tools have no understanding of organizational politics, interpersonal relationships, or the specific humans you're working with.They don't know that your VP of Engineering is burned out and skeptical of any new initiatives. They don't know that your CEO has a personal obsession with a specific competitor. They don't know that your lead designer is sensitive about not being included early enough in the process.If you use AI-generated communications without layering in this human context, you'll create perfectly worded documents that land badly because they miss the subtext.The fix: After generating AI content, explicitly ask yourself: “What human context am I missing? What relationships do I need to consider? What political dynamics are in play?” Then modify the AI output accordingly.Pitfall #5: Over-Relying on a Single ToolDifferent AI tools have different strengths. Claude is great for strategic depth, ChatPRD is great for structure, Gemini integrates well with Google Workspace.If you only ever use one tool, you're missing opportunities to leverage different strengths for different tasks.The fix: Keep 2-3 tools in your toolkit. Use Claude for important PRDs and strategic documents. Use Gemini for quick internal documentation that needs to integrate with Google Docs. Use ChatPRD when you want more guided structure. Match the tool to the task.Pitfall #6: Not Fact-Checking AI OutputAI tools hallucinate. They make up statistics, misrepresent competitors, and confidently state things that aren't true. If you include those hallucinations in a PRD that goes to leadership, you look incompetent.The fix: Fact-check everything, especially:* Statistics and market data* Competitive feature claims* Technical capabilities and limitations* Regulatory and compliance requirementsIf the AI cites a number or makes a factual claim, verify it independently before including it in your document.The Meta-Skill: Prompt Engineering for PMsLet's zoom out and talk about the underlying skill that makes all of this work: prompt engineering.This is a real skill. The difference between a mediocre prompt and a great prompt can be 10x difference in output quality. And unlike coding or design, where there's a steep learning curve, prompt engineering is something you can get good at quickly.Principle 1: Provide Context Before InstructionsBad prompt:“Write a PRD for an AI tutor”Good prompt:“I'm a PM at an edtech company with 2M users, primarily high school students. We're exploring an AI tutor feature to complement our existing video content library and practice problems. Our main competitors are Khan Academy and Course Hero. Our differentiation is personalized learning paths based on student performance data.Write a PRD for an AI tutor feature targeting students in the middle 80% academically who struggle with science and math.”The second prompt gives Claude the context it needs to generate something specific and strategic rather than generic.Principle 2: Specify Format and ConstraintsBad prompt:“Generate success metrics”Good prompt:“Generate 5-7 success metrics for this feature. Include a mix of:* Leading indicators (early signals of success)* Lagging indicators (definitive success measures)* User behavior metrics* Business impact metricsFor each metric, specify: name, definition, target value, measurement method, and why it matters.”The structure you provide shapes the structure you get back.Principle 3: Ask for Multiple OptionsBad prompt:“What should our Q2 priorities be?”Good prompt:“Generate 3 different strategic approaches for Q2:* Option A: Focus on user acquisition* Option B: Focus on engagement and retention* Option C: Focus on monetizationFor each option, detail: key initiatives, expected outcomes, resource requirements, risks, and recommendation for or against.”Asking for multiple options forces the AI (and forces you) to think through trade-offs systematically.Principle 4: Specify Audience and ToneBad prompt:“Summarize this PRD”Good prompt:“Create a 1-paragraph summary of this PRD for our skeptical VP of Engineering. Tone: Technical, concise, addresses engineering concerns upfront. Focus on: technical architecture, resource requirements, risks, and expected engineering effort. Avoid marketing language.”The audience and tone specification ensures the output will actually work for your intended use.Principle 5: Use Iterative RefinementDon't try to get perfect output in one prompt. Instead:First prompt: Generate rough draft Second prompt: “This is too generic. Add specific examples from [our company context].” Third prompt: “The technical section is weak. Expand with architecture details and dependencies.” Fourth prompt: “Good. Now make it 30% more concise while keeping the key details.”Each iteration improves the output incrementally.Let me break down the prompting approach that worked in this experiment, because this is immediately actionable for your work tomorrow.Strategy 1: The Structured Outline ApproachDon't go from zero to full PRD in one prompt. Instead:* Start with strategic thinking - Spend 10-15 minutes outlining why you're building this, who it's for, and what problem it solves* Get specific - Don't say “users,” say “high school students in the middle 80% of academic performance”* Include constraints - Budget, timeline, technical limitations, competitive landscape* Dump your outline into the AI - Now ask it to expand into a full PRD* Iterate section by section - Don't try to perfect everything at onceThis is exactly what I did in my experiment, and even with my somewhat sloppy outline, the results were dramatically better than they would have been with a single-sentence prompt.Strategy 2: The Comparative Analysis PatternOne technique I used that worked particularly well: asking each tool to do the same specific task and comparing results.For example, I asked all five tools: “Please compose a one paragraph exact summary I can share over DM with a highly influential VP of engineering who is generally a skeptic but super smart.”This forced each tool to synthesize the entire PRD into a compelling pitch while accounting for a specific, challenging audience. The variation in quality was revealing—and it gave me multiple options to choose from or blend together.Actionable tip: When you need something critical (a pitch, an executive summary, a key decision framework), generate it with 2-3 different AI tools and take the best elements from each. This “ensemble approach” often produces better results than any single tool.Strategy 3: The Iterative Refinement LoopDon't treat the AI output as final. Use it as a first draft that you then refine through conversation with the AI.After getting the initial PRD, I could have asked follow-up questions like:* “What's missing from this PRD?”* “How would you strengthen the success metrics section?”* “Generate 3 alternative approaches to the core feature set”Each iteration improves the output and, more importantly, forces me to think more deeply about the product.What This Means for Your CareerIf you're an early or mid-career PM reading this, you might be thinking: “Great, so AI can write PRDs now. Am I becoming obsolete?”Absolutely not. But your role is evolving, and understanding that evolution is critical.The PMs who will thrive in the AI era are those who:* Excel at strategic thinking - AI can generate options, but you need to know which options align with company strategy, customer needs, and technical feasibility* Master the art of prompting - This is a genuine skill that separates mediocre AI users from exceptional ones* Know when to use AI and when not to - Some aspects of product work benefit enormously from AI. Others (user interviews, stakeholder negotiation, cross-functional relationship building) require human judgment and empathy* Can evaluate AI output critically - You need to spot the hallucinations, the generic fluff, and the strategic misalignments that AI inevitably producesThink of AI tools as incredibly capable interns. They can produce impressive work quickly, but they need direction, oversight, and strategic guidance. Your job is to provide that guidance while leveraging their speed and breadth.The Real-World Application: What to Do Monday MorningLet's get tactical. Here's exactly how to apply these insights to your actual product work:For Your Next PRD:* Block 30 minutes for strategic thinking - Write your back-of-the-napkin outline in Google Docs or your tool of choice* Open Claude (or ChatPRD if you want more structure)* Copy your outline with this prompt:“I'm a product manager at [company] working on [product area]. I need to create a comprehensive PRD based on this outline. Please expand this into a complete PRD with the following sections: [list your preferred sections]. Make it detailed enough for engineering to start breaking down into user stories, but concise enough for leadership to read in 15 minutes. [Paste your outline]”* Review the output critically - Look for generic statements, missing details, or strategic misalignments* Iterate on specific sections:“The success metrics section is too vague. Please provide 3-5 specific, measurable KPIs with target values and explanation of why these metrics matter.”* Generate supporting materials:“Create a visual mockup of the core user flow showing the key interaction points.”* Synthesize the best elements - Don't just copy-paste the AI output. Use it as raw material that you shape into your final documentFor Stakeholder Communication:When you need to pitch something to leadership or engineering:* Generate 3 versions of your pitch using different tools (Claude, ChatPRD, and one other)* Compare them for:* Clarity and conciseness* Strategic framing* Compelling value proposition* Addressing likely objections* Blend the best elements into your final version* Add your personal voice - This is crucial. AI output often lacks personality and specific company context. Add that yourself.For Feature Prioritization:AI tools can help you think through trade-offs more systematically:“I'm deciding between three features for our next release: [Feature A], [Feature B], and [Feature C]. For each feature, analyze: (1) Estimated engineering effort, (2) Expected user impact, (3) Strategic alignment with making our platform the go-to solution for [your market], (4) Risk factors. Then recommend a prioritization with rationale.”This doesn't replace your judgment, but it forces you to think through each dimension systematically and often surfaces considerations you hadn't thought of.The Uncomfortable Truth About AI and Product ManagementLet me be direct about something that makes many PMs uncomfortable: AI will make some PM skills less valuable while making others more valuable.Less valuable:* Writing boilerplate documentation* Creating standard frameworks and templates* Generating routine status updates* Synthesizing information from existing sourcesMore valuable:* Strategic product vision and roadmapping* Deep customer empathy and insight generation* Cross-functional leadership and influence* Critical evaluation of options and trade-offs* Creative problem-solving for novel situationsIf your PM role primarily involves the first category of tasks, you should be concerned. But if you're focused on the second category while leveraging AI for the first, you're going to be exponentially more effective than your peers who resist these tools.The PMs I see succeeding aren't those who can write the best PRD manually. They're those who can write the best PRD with AI assistance in one-tenth the time, then use the saved time to talk to more customers, think more deeply about strategy, and build stronger cross-functional relationships.Advanced Techniques: Beyond Basic PRD GenerationOnce you've mastered the basics, here are some advanced applications I've found valuable:Competitive Analysis at Scale“Research our top 5 competitors in [market]. For each one, analyze: their core value proposition, key features, pricing strategy, target customer, and likely product roadmap based on recent releases and job postings. Create a comparison matrix showing where we have advantages and gaps.”Then use web search tools in Claude or Perplexity to fact-check and expand the analysis.Scenario Planning“We're considering three strategic directions for our product: [Direction A], [Direction B], [Direction C]. For each direction, map out: likely customer adoption curve, required technical investments, competitive positioning in 12 months, and potential pivots if the hypothesis proves wrong. Then identify the highest-risk assumptions we should test first for each direction.”This kind of structured scenario thinking is exactly what AI excels at—generating multiple well-reasoned perspectives quickly.User Story GenerationAfter your PRD is solid:“Based on this PRD, generate a complete set of user stories following the format ‘As a [user type], I want to [action] so that [benefit].' Include acceptance criteria for each story. Organize them into epics by functional area.”This can save your engineering team hours of grooming meetings.The Tools Will Keep Evolving. Your Process Shouldn'tHere's something important to remember: by the time you read this, the specific rankings might have shifted. Maybe ChatGPT-5 has leapfrogged Claude. Maybe a new specialized tool has emerged.But the core principles won't change:* Do strategic thinking before touching AI* Use the best tool available for your specific task* Iterate and refine rather than accepting first outputs* Blend AI capabilities with human judgment* Focus your time on the uniquely human aspects of product managementThe specific tools matter less than your process for using them effectively.A Final Experiment: The Skeptical VP TestI want to share one more insight from my testing that I think is particularly relevant for early and mid-career PMs.Toward the end of my experiment, I gave each tool this prompt: “Please compose a one paragraph exact summary I can share over DM with a highly influential VP of engineering who is generally a skeptic but super smart.”This is such a realistic scenario. How many times have you needed to pitch an idea to a skeptical technical leader via Slack or email? Someone who's brilliant, who's seen a thousand product ideas fail, and who can spot b******t from a mile away?The quality variation in the responses was fascinating. ChatGPT gave me something that felt generic and safe. Gemini was better but still a bit too enthusiastic. Grok was... well, Grok.But Claude and ChatPRD both produced messages that felt authentic, technically credible, and appropriately confident without being overselling. They acknowledged the engineering challenges while framing the opportunity compellingly.The lesson: When the stakes are high and the audience is sophisticated, the quality of your AI tool matters even more. That skeptical VP can tell the difference between a carefully crafted message and AI-generated fluff. So can your CEO. So can your biggest customers.Use the best tools available, but more importantly, always add your own strategic thinking and authentic voice on top.Questions to Consider: A Framework for Your Own ExperimentsAs I wrapped up my Loom, I posed some questions to the audience that I'll pose to you:“Let me know in the comments, if you do your PRDs using AI differently, do you start with back of the envelope? Do you say, oh no, I just start with one sentence, and then I let the chatbot refine it with me? Or do you go way more detailed and then use the chatbot to kind of pressure test it?”These aren't rhetorical questions. Your answer reveals your approach to AI-augmented product work, and different approaches work for different people and contexts.For early-career PMs: I'd recommend starting with more detailed outlines. The discipline of thinking through your product strategy before touching AI will make you a stronger PM. You can always compress that process later as you get more experienced.For mid-career PMs: Experiment with different approaches for different types of documents. Maybe you do detailed outlines for major feature PRDs but use more iterative AI-assisted refinement for smaller features or updates. Find what optimizes your personal productivity while maintaining quality.For senior PMs and product leaders: Consider how AI changes what you should expect from your PM team. Should you be reviewing more AI-generated first drafts and spending more time on strategic guidance? Should you be training your team on effective AI usage? These are leadership questions worth grappling with.The Path Forward: Continuous ExperimentationMy experiment with these five AI tools took 45 minutes. But I'm not done experimenting.The field of AI-assisted product management is evolving rapidly. New tools launch monthly. Existing tools get smarter weekly. Prompting techniques that work today might be obsolete in three months.Your job, if you want to stay at the forefront of product management, is to continuously experiment. Try new tools. Share what works with your peers. Build a personal knowledge base of effective prompts and workflows. And be generous with what you learn. The PM community gets stronger when we share insights rather than hoarding them.That's why I created this Loom and why I'm writing this post. Not because I have all the answers, but because I'm figuring it out in real-time and want to share the journey.A Personal Note on Coaching and ConsultingIf this kind of practical advice resonates with you, I'm happy to work with you directly.Through my pm coaching practice, I offer 1:1 executive, career, and product coaching for PMs and product leaders. We can dig into your specific challenges: whether that's leveling up your AI workflows, navigating a career transition, or developing your strategic product thinking.I also work with companies (usually startups or incubation teams) on product strategy, helping teams figure out PMF for new explorations and improving their product management function.The format is flexible. Some clients want ongoing coaching, others prefer project-based consulting, and some just want a strategic sounding board for a specific decision. Whatever works for you.Reach out through tomleungcoaching.com if you're interested in working together.OK. Enough pontificating. Let's ship greatness. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit firesidepm.substack.com

#Podcast #IA #ChatGPT #Coatlicue En este episodio platicamos de todo: desde las fundas más raras para celular hasta los 3 años de ChatGPT y los dilemas de su privacidad. Además, comentamos la polémica de si todos deberían hacer servicio militar y presentamos a Coatlicue, la nueva supercomputadora mexicana que dará muchísimo de qué hablar.También te contamos sobre Comet en Android, el nuevo satélite mexicano, la salida de SEV de México, y qué se consumió en YouTube en 2025.

Jak si Motoristé poradí s výhradami prezidenta Pavla vůči ministerské nominaci Filipa Turka? Mohlo by se plánované uzavření uhelných elektráren skupiny Sev.en odrazit i na cenách energií? A podařilo se vědcům vůbec poprvé zachytit signály vesmírné temné hmoty?

Jak si Motoristé poradí s výhradami prezidenta Pavla vůči ministerské nominaci Filipa Turka? Mohlo by se plánované uzavření uhelných elektráren skupiny Sev.en odrazit i na cenách energií? A podařilo se vědcům vůbec poprvé zachytit signály vesmírné temné hmoty?Všechny díly podcastu Hlavní zprávy - rozhovory a komentáře můžete pohodlně poslouchat v mobilní aplikaci mujRozhlas pro Android a iOS nebo na webu mujRozhlas.cz.

Dr. Sev MacLaughlin, the CEO of DeLorean AI, has developed an AI platform to identify at-risk patients, including those with renal disease, cardiovascular disease, and mental health conditions. Serving smaller and mid-sized provider clinics, this approach supports the shift to value-based care by predicting adverse events, recommending preventive measures, and reducing hospitalizations and healthcare costs. By analyzing entire populations instead of samples, the platform avoids biases and overlooked subgroups inherent in traditional analytical methods. Sev explains, "So I think there's an opportunity to not only give better care at the point of care, but also aid in the discovery or assist in the diagnosis of unknown diseases that people may have in the chronic format. That may be identifying chronic kidney disease patients five years earlier, so they can have a different treatment modality and directionality in their lives, or hypertension or cardiovascular disease."  "We're very strong in renal. So both chronic kidney disease and end-stage renal failure, or patients on dialysis. And then the two comorbidities that most that are huge influences for that are cardiovascular disease, cardiovascular system, and diabetes. In addition to that, we do CD and pulmonary. And then we were asked by one of our largest clients, United Healthcare, to look at mental health. And I have to say another surprise to me is how important mental health is to the other disease states, so that mental health needs to be taken care of to ensure that those individuals are medically adherent, they're going to their appointments, they're taking their medications, they're taking their health seriously. And that is something that I learned was most important and needed to be treated in parallel with the primary care diagnosis." #DeLoreanAI #PreventativeCare #RenalCare #MedAI #Diagnostics #PopulationHealth #RiskStratification DeLoreanai.com Download the transcript here

Dr. Sev MacLaughlin, the CEO of DeLorean AI, has developed an AI platform to identify at-risk patients, including those with renal disease, cardiovascular disease, and mental health conditions. Serving smaller and mid-sized provider clinics, this approach supports the shift to value-based care by predicting adverse events, recommending preventive measures, and reducing hospitalizations and healthcare costs. By analyzing entire populations instead of samples, the platform avoids biases and overlooked subgroups inherent in traditional analytical methods. Sev explains, "So I think there's an opportunity to not only give better care at the point of care, but also aid in the discovery or assist in the diagnosis of unknown diseases that people may have in the chronic format. That may be identifying chronic kidney disease patients five years earlier, so they can have a different treatment modality and directionality in their lives, or hypertension or cardiovascular disease."  "We're very strong in renal. So both chronic kidney disease and end-stage renal failure, or patients on dialysis. And then the two comorbidities that most that are huge influences for that are cardiovascular disease, cardiovascular system, and diabetes. In addition to that, we do CD and pulmonary. And then we were asked by one of our largest clients, United Healthcare, to look at mental health. And I have to say another surprise to me is how important mental health is to the other disease states, so that mental health needs to be taken care of to ensure that those individuals are medically adherent, they're going to their appointments, they're taking their medications, they're taking their health seriously. And that is something that I learned was most important and needed to be treated in parallel with the primary care diagnosis." #DeLoreanAI #PreventativeCare #RenalCare #MedAI #Diagnostics #PopulationHealth #RiskStratification DeLoreanai.com Listen to the podcast here

On this episode, Sev sits down with Marcelo Avila, a car dealership entrepreneur and immigrant success story who reveals the hard truths about buying and selling used cars. Discover why most people buy what they want instead of what they need, how to avoid the biggest car-buying mistakes, and why choosing the right partner in life and business makes all the difference. Marcelo opens up about his journey from Ecuador to Australia, building a multi-location dealership, and his practical framework for sustainable success. If you're considering a car purchase or just love deep dives into entrepreneurship, business culture, and family, this episode delivers.Enjoyed this deep dive? Like, comment, and subscribe to The Sevo Show for more inspiring conversations. Let us know your biggest takeaway in the comments and share this video with someone who needs a dose of used car ownership or family man entrepreneurship. 00:00:00 - Biggest used-car mistake: wants vs needs 00:00:24 - New-dad intro and guest Marcelo Aila 00:01:15 - Entrepreneurship is failing forward 00:02:01 - Why migrate to Perth: origin story 00:02:59 - Showroom crash and ownership lessons 00:04:56 - Car-loan regret and money mindset 00:06:24 - Family hardship, England to Australia arc 00:07:51 - Picking the right life partner matters 00:11:00 - COVID boom, market cool-off, subleasing 00:12:30 - Building an internal marketing team 00:14:22 - Agencies vs in-house: incentives and speed 00:16:24 - Set 30-day success metrics that count 00:18:10 - Test small budgets, learn from data 00:19:16 - SOPs so knowledge doesn't walk away 00:20:49 - Culture: people stay by choice 00:21:49 - Franchises, buying land, scaling yards 00:22:55 - Sponsor message: ads done properly 00:23:42 - Qualifying buyers: use case and budget 00:24:54 - Chinese brands, EVs, hybrids complexity 00:26:27 - Consignment explained with real example 00:28:10 - Price bands for first car, risk trade-offs 00:29:08 - BYD servicing, parts and range realities 00:31:05 - Toyota/Mazda/Subaru: reliability and resale 00:33:06 - Autonomy timelines and safety features 00:35:44 - Adapting to policy shifts and markets 00:40:10 - Raising kids while building a business 00:43:15 - Document everything; avoid assumptions 00:50:08 - How to contact Marcelo and businessesFollow Marcelo's Business:Instagram: https://www.instagram.com/3mt.auto/Website: https://www.3mtauto.com.au/Follow me:https://www.instagram.com/sevspics/https://www.instagram.com/thesevoshow/Hire My Studios and Production Team:https://brighttsar.com/Sponsors:https://www.whereu.com.au/

Sev Tok is a Speaker, Author, Spiritual Counselor, Experiencer Advocate and a life-long Experiencer. Originally from Istanbul, Turkey, she emigrated to the US as a a little girl, not knowing English as she started first grade, and earned a Bachelor of Science degree in Biology from Loyola University. Sev's ET contact started at age 10, which she kept secret until 2017 when Greys burned red X-marks into her back. This ET contact prompted her to “come out” in 2018 as a Speaker at AlienCon and through her book, You Have The Right To Talk To Aliens, endorsed by renowned UFOlogist, Kathleen Marden. Sev is featured in the Canadian TV docuseries, Encounter: UFO - Physical Contact, has been interviewed around the world, speaks at conferences, and is honored to be the Master of Ceremonies at MUFON's International Symposium in Denver in July 2022. As a MUFON Field Investigator, the Assistant State Director for North Carolina, and as a member of MUFON's Experiencer Resource Team (ERT), Sev helps Experiencers around the world. She also offers personal and private guidance to Experiencers through Tell Me Your ET Story on her website, planetsev.com, her monthly newsletter, and her YouTube channel Alien Spirit TV. For the past 12 years, Sev has been conducting Soul Sessions, with clients around the world. The Sessions offer inter-dimensional guidance to manifest one's purpose and activate multidimensional DNA in order to design a fulfilling, successful, and dynamic life. A planet and star system is named after her in the STAR WARS Galactic System! You can find the Sev Tok Star System and Planet in Wookieepedia. Sev lives on the Inner Banks of North Carolina.

In this episode, we discuss recordings of “Fantasia: Works For Trumpet & Organ” (Chandos) by Matilda Lloyd & Richard Gowers, “Martinů String Quartets 2-3-5-7” (Supraphon) by the Pavel Haas Quartet, “Kevin Puts: Concerto for Orchestra, Silent Night Elegy & Virelai” (Delos)by the Saint Louis Symphony Orchestra / Stéphane Denève, “Window” (Royal Potato Records) by Kirk Knuffke, “Martha's Dance” (April Records & Music Co.) by Rolf Thofte, and “Oblivity” (Origin) by Shawn Purcell.   The Adult Music Podcast is featured in: Feedspot's 100 Best Jazz Podcasts   Episode 229 Deezer Playlist   Fair use disclaimer: Music sample clips are for commentary and educational purposes. We recommend that listeners listen to the complete recordings, all of which are available on streaming services in the links provided. We also suggest that if you enjoy the music, you consider purchasing the CDs or high-quality downloads to support the artists.   “Fantasia: Works For Trumpet & Organ” (Chandos) Matilda Lloyd, Richard Gowers https://open.spotify.com/album/75Cs0LBcBklIvksm1SY1Hs https://music.apple.com/us/album/fantasia-works-for-trumpet-organ/1828559617 https://music.amazon.com/albums/B0FJCGJZYF   “Martinů String Quartets 2-3-5-7” (Supraphon) Pavel Haas Quartet https://open.spotify.com/album/5LhBAJvYfW3akK0G35B8wh https://music.apple.com/us/album/martinů-string-quartets-nos-2-3-5-7/1832782214 https://music.amazon.com/albums/B0FM474BZ7   “Kevin Puts: Concerto for Orchestra, Silent Night Elegy & Virelai” (Delos) Saint Louis Symphony Orchestra / Stéphane Denève https://open.spotify.com/album/3s5T4R7QJKHjgfNHmVy6Vz https://music.apple.com/us/album/kevin-puts-concerto-for-orchestra-silent-night-elegy/1826975431 No Amazon Music   “Window” (Royal Potato Records) Kirk Knuffke https://open.spotify.com/album/1LySanfHzroc4tGbTk3Vub https://music.apple.com/us/album/window/1825438476 https://music.amazon.com/albums/B0FH34CV3P   “Martha's Dance” (April Records & Music Co.) Rolf Thofte https://open.spotify.com/album/0BPTo5uHCsy0C9E13uwfvx https://music.apple.com/us/album/marthas-dance/1818579136 https://music.amazon.com/albums/B0FBX5NF6R   “Oblivity” (Origin)  Shawn Purcell https://open.spotify.com/album/4BdcYHpppD4zNskoxnuP2Z https://music.apple.com/us/album/oblivity/1831093754 https://music.amazon.com/albums/B0FL4V5HPB   As mentioned in the episode, check out these other recordings:   “Turn It Up! Live at the Sidedoor!” (Cellar Music)  Mike Ledonne's Groover Quartet https://link.deezer.com/s/31as1BOtXouuUWp4gd3H7 https://open.spotify.com/album/2XaWFbDK4CnBGChEBJROUz https://music.apple.com/us/album/turn-it-up-live-at-the-sidedoor/1812724629 https://music.amazon.com/albums/B0F7MN5XRH   “Lacrimosa” (Siddartha Records) Øystein Sevåg https://link.deezer.com/s/31as12IxaLUTLtqgmznxd https://open.spotify.com/album/6uwtuJAbxfU1pmWpwpsgtE https://music.apple.com/us/album/lacrimosa/1833099090 https://music.amazon.com/albums/B0FMD1QBVF   “Mischief in the Musitorium” (Need to Know Music) Funkwrench Blues https://link.deezer.com/s/31as0wlHVYv05BnPG26Zc https://open.spotify.com/album/4G5ncKCkFsgyq35jdyOnuM https://music.apple.com/us/album/mischief-in-the-musitorium-album-master-feat-frank-swart/1822729695 https://music.amazon.com/albums/B0FFB6JQJ7

OBS. Denna podcast kom till betalande prenumeranter den 9 september. Om du vill ha våra podcasts utan reklam och direkt när de publiceras, teckna en betald prenumeration på https://podcast.detfriasverige.seVår svenska strävan är på riktigt. Den är en ödeskamp om vårt folks framtid och överlevnad. Därför är det av yttersta vikt att den bygger på sanning, och att vi inte tillåter lögnare och bedragare att dra vår sak i smutsen. I den här podcasten gör vi upp med influerare och alternativmedier som medvetet sprider lögner och desinformation, vare sig det är av dumhet, ondska eller girighet. Vi tar upp flera aktuella exempel, och förklarar varför de är så skadliga.Men framförallt: Vi berättar om hur du kan skydda dig från att bli lurad av dessa oseriösa aktörer. Hur du får en större förståelse för vår samtids stora lögn, och hur du kan slå dig fri.Vi talar också om nationalisten Jörgen Kromann som nyligen gick bort, och minns tillbaka på när vi båda arbetat med honom.Dessutom: Allt om vårt nya projekt, dess framtidsplaner och vision. Häng med!Become a supporter of this podcast: https://www.spreaker.com/podcast/det-fria-sverige--4339034/support.

In this episode, I divide colesevelam and Welchol into syllables, tell you which syllables to emphasize, and share my sources. The written pronunciations are below and in the show notes on https://www.thepharmacistsvoice.com.   Note: we don't cover pharmacology in this series. Just pronunciations. The FULL show notes are available at https://www.thepharmacistsvoice.com/podcast.    colesevelam = KOE-le-SEV-e-lam  Emphasize KOE and SEV. SEV gets the most emphasis. Source for the written pronunciation = USP Dictionary Online (subscription-based resource) or medlineplus.gov (free resource)  Source for the spoken pronunciation = Product video on Welchol's website (accessed 9-15-25)   Welchol = wel-kaal  Source for the written pronunciation = Google search using a Chrome Browser (9-15-25)  Source for the spoken pronunciation = Product video on Welchol's website (accessed 9-15-25). See also Merriam-Webster's Online Dictionary https://www.merriam-webster.com/medical/Welchol (accessed 9-15-25) or Tony PharmD's YouTube Channel (accessed 9-15-25)   Thank for listening to the 63nd episode in my drug pronunciation series!   If you'd like to recommend a drug name for this series, please reach out through the contact form on my website, thepharmacistsvoice.com.   If you know someone who would like to learn how to say colesevelam and Welchol, please share this episode with them. Subscribe for all future episodes. This podcast is on all major podcast players and YouTube. Popular links are below. ⬇️   Apple Podcasts   https://apple.co/42yqXOG  Spotify  https://spoti.fi/3qAk3uY  Amazon/Audible  https://adbl.co/43tM45P YouTube https://bit.ly/43Rnrjt   ⭐️ Sign up for The Pharmacist's Voice ® monthly email newsletter! https://bit.ly/3AHJIaF   Host Background: Kim Newlove has been an Ohio pharmacist since 2001 (BS Pharm, Chem Minor). Her experience includes hospital, retail, compounding, and behavioral health. She is also an author, voice actor (medical narrator and audiobook narrator), podcast host, and consultant (audio production and podcasting).    Other episodes in this series The Pharmacist's Voice Podcast Episode 346, Pronunciation Series Episode 62 (valacyclovir) The Pharmacist's Voice Podcast Episode 343, Pronunciation Series Episode 61 (ubrogepant) The Pharmacist's Voice Podcast Episode 341, Pronunciation Series Episode 60 (topiramate) The Pharmacist's Voice Podcast Episode 339, Pronunciation Series Episode 59 (Suboxone) The Pharmacist's Voice Podcast Episode 337, Pronunciation Series Episode 58 (rosuvastatin)  The Pharmacist's Voice Podcast Episode 335, Pronunciation Series Episode 57 (QVAR) The Pharmacist's Voice Podcast Episode 333, Pronunciation Series Episode 56 (pantoprazole)  The Pharmacist's Voice Podcast Episode 330, Pronunciation Series Episode 55 (oxcarbazepine) The Pharmacist's Voice Podcast Episode 328, Pronunciation Series Episode 54 (nalmefene) The Pharmacist's Voice Podcast Episode 326, Pronunciation Series Episode 53 (Myrbetriq) The Pharmacist's Voice Podcast Episode 324, Pronunciation Series Episode 52 (liraglutide)  The Pharmacist's Voice Podcast Episode 322, Pronunciation Series Episode 51 (ketamine) The Pharmacist's Voice Podcast Episode 320, Pronunciation Series Episode 50 (Jantoven) The Pharmacist's Voice Podcast Episode 318, Pronunciation Series Episode 49 (ipratropium) The Pharmacist's Voice Podcast Episode 316, Pronunciation Series Episode 48 (hyoscyamine) The Pharmacist's Voice Podcast Episode 313, Pronunciation Series Episode 47 (guaifenesin) The Pharmacist's Voice Podcast Episode 311, Pronunciation Series Episode 46 (fluticasone) The Pharmacist's Voice Podcast Episode 309, Pronunciation Series Episode 45 (empagliflozin) The Pharmacist's Voice Podcast Episode 307, Pronunciation Series Episode 44 (dapagliflozin) The Pharmacist's Voice Podcast Episode 304, Pronunciation Series Episode 43 (cetirizine)  The Pharmacist's Voice Podcast Episode 302, Pronunciation Series Episode 42 (buspirone)  The Pharmacist's Voice Podcast Episode 301, Pronunciation Series Episode 41 (azithromycin) The Pharmacist's Voice Podcast Episode 298, Pronunciation Series Episode 40 (umeclidinium) The Pharmacist's Voice Podcast Episode 296, Pronunciation Series Episode 39 (Januvia)  The Pharmacist's Voice Podcast Episode 294, Pronunciation Series Episode 38 (Yasmin) The Pharmacist's Voice Podcast Episode 292, Pronunciation Series Episode 37 (Xanax, alprazolam) The Pharmacist's Voice Podcast Episode 290, Pronunciation Series Episode 36 (quetiapine)  The Pharmacist's Voice Podcast Episode 287, pronunciation series ep 35 (bupropion) The Pharmacist's Voice Podcast Episode 285, pronunciation series ep 34 (fentanyl) The Pharmacist's Voice Podcast Ep 281, Pronunciation Series Ep 33 levothyroxine (Synthroid) The Pharmacist's Voice ® Podcast Ep 278, Pronunciation Series Ep 32 ondansetron (Zofran) The Pharmacist's Voice ® Podcast Episode 276, pronunciation series episode 31 (tocilizumab-aazg) The Pharmacist's Voice ® Podcast Episode 274, pronunciation series episode 30 (citalopram and escitalopram) The Pharmacist's Voice ® Podcast Episode 272, pronunciation series episode 29 (losartan) The Pharmacist's Voice Podcast Episode 269, pronunciation series episode 28 (tirzepatide) The Pharmacist's Voice Podcast Episode 267, pronunciation series episode 27 (atorvastatin)  The Pharmacist's Voice Podcast Episode 265, pronunciation series episode 26 (omeprazole) The Pharmacist's Voice Podcast Episode 263, pronunciation series episode 25 (PDE-5 inhibitors) The Pharmacist's Voice Podcast Episode 259, pronunciation series episode 24 (ketorolac) The Pharmacist's Voice ® Podcast episode 254, pronunciation series episode 23 (Paxlovid) The Pharmacist's Voice ® Podcast episode 250, pronunciation series episode 22 (metformin/Glucophage) The Pharmacist's Voice Podcast ® episode 245, pronunciation series episode 21 (naltrexone/Vivitrol) The Pharmacist's Voice ® Podcast episode 240, pronunciation series episode 20 (levalbuterol) The Pharmacist's Voice ® Podcast episode 236, pronunciation series episode 19 (phentermine)  The Pharmacist's Voice ® Podcast episode 228, pronunciation series episode 18 (ezetimibe) The Pharmacist's Voice ® Podcast episode 219, pronunciation series episode 17 (semaglutide) The Pharmacist's Voice ® Podcast episode 215, pronunciation series episode 16 (mifepristone and misoprostol) The Pharmacist's Voice ® Podcast episode 211, pronunciation series episode 15 (Humira®) The Pharmacist's Voice ® Podcast episode 202, pronunciation series episode 14 (SMZ-TMP) The Pharmacist's Voice ® Podcast episode 198, pronunciation series episode 13 (carisoprodol) The Pharmacist's Voice ® Podcast episode 194, pronunciation series episode 12 (tianeptine) The Pharmacist's Voice ® Podcast episode 188, pronunciation series episode 11 (insulin icodec)  The Pharmacist's Voice ® Podcast episode 184, pronunciation series episode 10 (phenytoin and isotretinoin) The Pharmacist's Voice ® Podcast episode 180, pronunciation series episode 9 Apretude® (cabotegravir) The Pharmacist's Voice ® Podcast episode 177, pronunciation series episode 8 (metoprolol)  The Pharmacist's Voice ® Podcast episode 164, pronunciation series episode 7 (levetiracetam) The Pharmacist's Voice ® Podcast episode 159, pronunciation series episode 6 (talimogene laherparepvec or T-VEC)  The Pharmacist's Voice ® Podcast episode 155, pronunciation series episode 5 Trulicity® (dulaglutide)  The Pharmacist's Voice ® Podcast episode 148, pronunciation series episode 4 Besponsa® (inotuzumab ozogamicin) The Pharmacist's Voice ® Podcast episode 142, pronunciation series episode 3 Zolmitriptan and Zokinvy The Pharmacist's Voice ® Podcast episode 138, pronunciation series episode 2 Molnupiravir and Taltz The Pharmacist's Voice ® Podcast episode 134, pronunciation series episode 1 Eszopiclone and Qulipta   Kim's websites and social media links: ✅ Guest Application Form (The Pharmacist's Voice Podcast) https://bit.ly/41iGogX ✅ Monthly email newsletter sign-up link https://bit.ly/3AHJIaF  ✅ LinkedIn Newsletter link https://bit.ly/40VmV5B ✅ Business website https://www.thepharmacistsvoice.com ✅ Get my FREE eBook and audiobook about podcasting ✅ The Pharmacist's Voice ® Podcast https://www.thepharmacistsvoice.com/podcast ✅ Drug pronunciation course https://www.kimnewlove.com  ✅ Podcasting course https://www.kimnewlove.com/podcasting  ✅ LinkedIn https://www.linkedin.com/in/kimnewlove ✅ Facebook https://www.facebook.com/kim.newlove.96 ✅ Twitter https://twitter.com/KimNewloveVO ✅ Instagram https://www.instagram.com/kimnewlovevo/ ✅ YouTube https://www.youtube.com/channel/UCA3UyhNBi9CCqIMP8t1wRZQ ✅ ACX (Audiobook Narrator Profile) https://www.acx.com/narrator?p=A10FSORRTANJ4Z ✅ Start a podcast with the same coach who helped me get started (Dave Jackson from The School of Podcasting)! **Affiliate Link - NEW 9-8-23**      Thank you for listening to episode 348 of The Pharmacist's Voice ® Podcast.  If you know someone who would like this episode, please share it with them!  

We have another outdoor special for you this week, recorded near Chamonix in Servos. Kenton chats to Sev Garo, an artist and sculptor who is inspired by glaciers. Sev explains how he aims to capture the energy of glaciers through his art and how he hopes his work helps to start conversations about climate change and glacial melt. Sev tells Kenton how he initially came up with the idea to design unique pieces of jewellery from the surface detail of glaciers and the process he follows to create this wearable art. Take a look at Sev's work on his website: www.garogosi.com

In this episode of Wrestling Soup, Anthony and Joe delve deep into the latest WWE Raw episode, dissecting key storylines, character developments, and potential future directions. They discuss the ongoing issues with the WWE streaming service, recent talent cuts including Karrion Kross and Scarlett, and the company's handling of talent missteps. The chaos of the main event, the Swerve of Seth Rollins' injury, and the potential future of Karrion Kross are also covered. Additionally, opinions on Bayley's character transformation, Bray Wyatt's legacy, and the creative state of WWE are extensively discussed. Tune in for an in-depth analysis and some laughter along the way.00:15 Wrestler Reactions and Speculations00:35 Braun Strowman's WWE Departure03:08 WWE's Creative Stagnation03:23 Raw Recap and Highlights04:00 Dominick and Cross-Promotional Wrestling04:28 AEW and WWE Content Overload08:51 Rusev's Character and WWE's Creative Funk14:01 Naomi's Absence and Fan Expectations21:48 Mercedes Moné's Controversial Comments39:00 Bret Hart's SummerSlam Snub40:48 Crowd Seating Dilemma41:52 Triple H's Petty Decisions?44:10 Bret Hart's Influence and Critique45:36 Wrestling Match Interferences46:32 Konnan's Commentary Career51:32 "The Vision" Tag Team01:01:12 Bayley's Character Evolution01:15:15 Sammy and Sev's Match Recap01:16:06 Scarlet's WWE Farewell01:16:44 Kross's WWE Journey and Speculations01:18:26 WWE's Storyline Strategies01:20:13 Damien Priest and R-Truth's Storyline01:23:01 Kross's Future in Wrestling01:26:15 WWE's Creative Challenges01:48:55 Bray Wyatt's Creative Struggles01:54:18 Wrapping Up and AnnouncementsBecome a supporter of this podcast: https://www.spreaker.com/podcast/wrestling-soup--1425249/support.

In this episode of Wrestling Soup, Mish dives into a variety of hot topics within the wrestling world. Joey is on vacation in Las Vegas, enjoying his time at the Whitney Houston slot machine. The show covers the fallout from Hulk Hogan's passing, and emotional homages to Hogan on both Friday Night SmackDown and Monday Night Raw. Mish also addresses the intense controversies surrounding Hogan's legacy, including the responses from various commentators and the extreme reactions on social media. The episode transitions into a recap of Monday Night Raw, including match highlights and promos from stars like Jay Uso, Bronson Reed, Paul Heyman, AJ Styles, and the Kabuki Warriors. It ends with a preview of the upcoming Summer Slam event and other content viewers can expect on the Wrestling Soup network. Join Mish for an in-depth review and commentary on the latest wrestling drama and storylines.00:00 Introduction and Joey's Vacation01:58 Reactions to Hulk Hogan's Death06:57 Criticism of Hulk Hogan's Legacy28:57 Jay Uso's Promo and Paul Heyman's Response34:21 Mixed Match and AJ Styles' Performance37:52 Seamus vs. Grayson Waller41:25 Sev and Seamus: Rising Stars in the Ring42:25 Naomi's Heel Turn: Embracing the Dark Side44:16 Lyra's Painful Promo and Becky Stompers49:42 Paul Heyman and Bronson Reed: A New Leader Emerges51:01 Sammy Zane vs. Cross: A Battle of Truths55:52 Bailey's Struggles and Future Prospects58:02 Eight-Woman Tag Match: A Night of Surprises01:04:03 Judgment Day Clubhouse: Pep Talks and Steam Decks01:10:49 Gunther and CM Punk: The Addiction of Wrestling01:13:32 Main Event: Bronson Reed vs. Jay Uso01:20:28 Show Wrap-Up and Upcoming EventsBecome a supporter of this podcast: https://www.spreaker.com/podcast/wrestling-soup--1425249/support.

Delta Squad on our way! In this episode, we cover the Delta Squad box in full: RC-1138 Boss, RC-1140 Fixer, Sev, and Scorch.We cover these heroes in lore before breaking down their unit and stance cards, exploring how they fit into STAR WARS: Shatterpoint, and the impact they bring to the battlefield.Hello There! is a podcast about the tabletop game ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Star Wars Shatterpoint⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ and the Star Wars Universe.___________________________________Click the link below to help us out! The more people that click on the link below and follow our pages - the higher the potential of AMG to providing us with more giveaway items in the future.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://bit.ly/SWP-HelloThere⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ___________________________________Hello There! is supported by our wonderful patrons on Patreon. If you would like to help the show, and join our discord community, go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠patreon.com/hellotherecast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ and pledge your support. Hello There! Patrons directly support the show and its growth by helping pay our monthly and annual fees, while contributing to future projects and endeavors.___________________________________Twitch I ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠HelloThereCast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter I ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@HelloThereCast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram I ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@HelloThereCast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook I ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠HelloThereCast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠YouTube I  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠HelloThereCast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Apple Podcasts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ l⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ l⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Google Podcasts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ __________________________________Hello There! is hosted by ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Jesse Eakin⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

This week, Tiffany welcomes Dr. Severine Bryan to discuss a topic that doesn't get enough spotlight: rebuilding your finances after a late-life divorce. Whether you're in your 40s, 50s, or beyond, Dr. Sev's candid insights and practical advice are here to help you start fresh.Check out the full show notes: https://moneytalkwitht.com/podcast-show-notes/late-life-divorce/What is a Late Life Divorce?Dr. Sev defines it as any divorce after age 45—a time when most are thinking about retirement, not starting over. She shares her personal journey and the challenges of pivoting financially later in life.Key TakeawaysEmbrace the Journey: Allow yourself to grieve, but don't get stuck. Healing opens the door to rebuilding.Top 3 Financial Tips:Face your debt head-on—don't ignore it, seek help if needed.Invest in yourself—consider therapy, learning new skills, or finding support.Learn from setbacks—every hardship brings a valuable lesson.Never Handled the Money?Tap into local resources like libraries, nonprofits, and workshops. There's no shame in asking for help—everyone has had financial hiccups.Connect with Dr. SevLinkedIn: Dr. Severine Bryan, Accredited Financial CounselorWebsite: sevtalksmoney.comCatch up on previous episodes at moneytalkwitht.com and follow Tiffany on social @MoneyTalkWithT, everywhere!

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

Listen—if you've ever said, “I wanna build my brand, but I don't have the money,” this episode is your wake-up call and your wallet's new best friend. I'm joined by the brilliant Dr. Severine Bryan—aka Dr. Sev—an accredited financial counselor, Fortune 500 vet, and my fellow Nasdaq Milestone Circle sister.We're breaking down brand budgeting myths, how to grow your brand with just $5 (yes, really), and the real reason your mindset might be the biggest thing blocking your money moves. Whether you're bootstrapping or building with a budget, this conversation will help you make smarter, sustainable choices for your brand's financial future.You'll learn: 

What happens when you combine the brilliant mind of Ryan Coogler and a bunch of blood-thirsty vampires? You get SINNERS, one of the most original and entertaining films of the year. A theatrical feat at the box office, it's grossed over 285 million dollars since its April 16th release. It was my absolute pleasure to talk to producer Sev Ohanian about how this monster movie gem came to fruition. Sev is a homie and we go way back to our baby producer days, so it is really special for me to reconnect with him after so many years. Our meet cute story is also one for the books! Sev is Armenian-American screenwriter, producer, and founder of Proximity Media alongside Ryan and Zinzi Coogler. He co-wrote and produced (alongside his wife and producing partner Natalie Qasabian who was on the podcast back in 2019!), SEARCHING, released by Sony Screen Gems in 2018. The film grossed $75 million worldwide and sparked the sequel, MISSING. Ohanian also co-wrote and produced RUN for Lionsgate, which became Hulu's most-watched film upon its premiere. During our time together, we talked about his first foray into filmmaking - an $800 micro-budget film shot on his dad's home video camera, how his working relationship with Coogler came to be, and the trials and tribulations of shooting on location in the swamps of Louisiana. xx cg

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

This week on Sapphic Survival Guide, Cheyenne and Gina go into the archives!We will be taking a hiatus from recording new episodes, but we will be re-releasing some of your favorite old episodes in the meantime. Thank you, always, for being a listener!Submit your own questions by messaging us on Instagram or emailing us at sapphicsurvivalguide@gmail.com. You can also leave us a voicemail at 724-209-8877 (US. Only - You can also send a voice note via email. Unless stated otherwise, you are giving us permission to play your voicemail on the podcast.)CreditsProduced by Gina Finio and CheyenneEdited by Gina FinioCover Art by Sev & CheyenneMusic by PartnerSound Effects by Audio VampireFollow us on Instagram, Facebook, Twitter, and TikTok and subscribe to our Patreon for extras!Follow Cheyenne on Instagram, Facebook, Twitter, and TikTokFollow Gina on Instagram, TikTok, and her website

This week we discussed Update 43.4, the two new 64-bit servers, and our week in gaming. Game News Update 43.4 Release Notes Two new servers announced: Grond and Sting A note from Sev on recent down time Latest episode of We Have a Cave Troll Store Sales The Patron’s Coffer of the Sands is available […]