Podcasts about slightly

■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 5月16日で《ピアノ万葉集》は完結しました ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■《ピアノ万葉集》プロジェクトは2026年5月16日に完結しました。でもここは大事な場所なので、前に創った《ピアノ万葉集》の曲をお届けします。ただ、すみませんが、前に流した曲ですので重複しています。=================================================something sl..

Tracy Douglas is the president of the Alberta Hotel and Lodging Association. Learn more about your ad choices. Visit megaphone.fm/adchoices

Wall St fell Friday as a Chinese AI breakthrough rattled semis and oil rose after holding ground for the previous three sessions on further US-Iran escalation. Dow Jones down 407 points. S&P 500 down 1.01%, closing below its 50-day moving average. Nasdaq down 1.40%. Slightly better than futures yesterday were indicating. Russell 2000 down 0.42%. Mag7 down 1.78%. SOX down 1.63%, recovering from a 5.5% opening drop. VIX up 12.19%.ASX set for a good session today although escalation in the Middle East will not help.. SPI futures up 54 points or 0.62%.US futures flat currently - Korea to reopen - Japan closed.Marcus Today – Daily Market InsightsMarcus Today provides clear, practical commentary for self-directed investors – covering markets, portfolios, education, and decision-making without the noise.If you'd like to go further:Start a free 14-day trial of Marcus Today http://bit.ly/mt-trial-podcastJoin Marcus Today Use code MTPODCAST for 10% off http://bit.ly/mt-join-podcast-offerMT20 – Managed ETF Portfolio A professionally managed portfolio run by Marcus Padley and the team, using ASX-listed ETFs with active market timing. http://bit.ly/mt20-podcastPrinciples – How We Think About Investing A short video series on timing, behaviour, and decision-making. No stock tips. http://bit.ly/mt-principles-podcast—Disclaimer This podcast is general information only and does not consider your personal circumstances. It is not personal financial advice.

本期摘要很多人把“心想事成”归结为运气，或者一种玄学。但老朋友 Shu 的这半年，让我们很难只用运气来解释：一月份她还在和我们聊“一人公司”，几个月后，她带着女儿去硅谷 world schooling；用十天筹备期，和一群第一次合作的一人公司交付了一场千人发布会；在湾区攒起一桌 AI 创业者的小饭桌；然后在一顿被拒绝的晚饭之后，签出了人生第一份 SAFE，成为一名天使投资人。这一期，Slightly Open 和 Shu 聊的是“许愿”：为什么她随地大小许愿，愿望却总能以某种方式实现？聊到后来我们发现，这件事和玄学关系不大——它更像一种能力：敢把愿望说出口的能力，把没有被完全摁死的拒绝变成下一步行动的能力，以及在别人只看到前台时，那些被忽略的十几年后台积累。我们也没有回避另一面：并不是随地大小许愿都会实现；懂了那么多道理，蹦极前的恐惧依然真实；而对循规蹈矩长大的我们来说，配得感和专业敬畏，既是铠甲，也是链锁。这期聊的是许愿，也是行动；聊的是草台班子，也是种树苗的人。如果世界真的没有一个总导演，那么被推上舞台之后，我们要怎么写好自己的剧本。时间轴01:49｜节目开场一句打中老柴的话：“女孩儿们有什么想法就去试试，别等完美了才出发。”上次来聊“一人公司”的 Shu，这次是在 SO 200 期留言里许愿返场的。05:12｜Coco 为什么一直在谢谢 Shu很多人都在说愿力和显化，但 Shu 让“相信”变得特别具体：说要上 SO 就上了，说去美国就去了。她是一个给出很多具体相信的人。07:42｜老柴眼中的 Shu：野生创业者没上过一天班就开始创业的 1.0，是无知无畏的少年气；经历过 ups and downs 之后回来的 2.0，完全不一样。11:13｜第一个愿：带女儿去硅谷 world schooling起心动念之后才发现，它并没有想象中那么难：女儿可以在那边上学，自己可以在那边工作，三月份一家三口就出发了。21:03｜十天筹备一场硅谷千人发布会一群第一次合作的“一人公司”临时成班，每个人都能独当一面，背靠背极限交付。一人公司的价值，在这十天里被具体地看见。26:25｜快乐的疯感与 AI 小饭桌发布会之后，Shu 又许了一个愿：攒一桌硅谷和中国的 AI 创业者。没有赞助商宣讲，十二个人纯粹地吃饭、交换认知。28:36｜下一个念头：做一个基金认识了这些早期创业者之后，她想和他们发生更深的连接——投资他们。虽然“募投管退”这四个字，她也是第一次听说。32:22｜一顿被拒绝的晚饭，和一条新的路潜在 LP 快速而中肯地拒绝了她，但同时给她指了一条更小的路径：先去向创业者要份额。34:53｜5 万美金，人生第一份 SAFE什么是 SAFE？是去对方办公室的路上，合伙人在车里念给她听的。三十分钟现学，现场就用上了。36:32｜同样的信息，为什么我们接不住Coco 的诚实对照：遇到婉约的拒绝，就把它当作拒绝收好回去了；而 Shu 能把那 20% 没被摁死的部分，变成“那我能干什么”。40:59｜世界是个草台班子同一句话有两种解读：有人因此对世界失望，有人看到的是——既然是草台班子，是不是咱也可以试试？47:21｜薇薇说：我们特别容易用自己的后台，去判断别人的前台只看到别人干成了，看不到背后的混乱；只看到台上侃侃而谈，看不到底下准备了七遍。头悬梁锥刺股的人，最容易觉得自己“不配得”。48:59｜Coco 的两点补充懂了道理也未必迈得出去，因为蹦极前的恐惧是真实的；以及本期免责声明——并不是随地大小许愿，都会实现。52:26｜发愿到底是什么Shu 说，发愿更多的是你想成为一个什么样的人。愿望带来的种种机缘，都是基于这个人的底色发生的。她也讲了自己的遗憾与初心：那些曾在她活动上冒出来、却只能目送的创业者。58:49｜老柴的三个启发和一个故事敢想、路径可以野一点、给自己正反馈。一个“没有资格”的小公司，怎么用一年半拿下全球顶尖客户，再从 60 万做到 1000 万。01:07:11｜野生与盆景盆景只能在盆里被修修剪剪；野生的植物，你根本不知道它会长成什么样——但你得先允许这件事情发生。01:12:59｜还没长出来的愿望在国际组织工作二十多年的薇薇，被宏大的东西深刻塑造，下一个愿望还没有长出来。Coco 说：没有特别清晰的愿望，也不一定是坏事。01:19:05｜许愿环节老柴在微博向二十万读者发愿招人，收到了让她在屋里跳起来的简历；Coco 想再要一两个“灵魂伴侣客户”；薇薇想认识张小珺——微信当场就加过去了。01:31:50｜Coco 为什么喜欢呼兰一个勇敢对世界说“我想赢”、也认真付诸实践的人。愿望说给朋友听，就有人愿意替你厚着脸皮去问——为别人开口，总是更容易一些。01:37:06｜从旧金山飞匹兹堡的红眼航班全网寻找赛考斯：26 年前的 5000 美金捐款，让一片沙漠长成森林。一场无关金钱的奔波，和一个几亿曝光的故事。01:42:21｜一场只有一个人在看的直播Coco：它不是一种悬浮的成功，而是特别真实的努力和交付。肉身痛苦、ROI 惨淡，但它是安抚人心的快乐。01:45:02｜最后想对女孩们说的话世界没有总导演，被推上舞台之后，要写好自己的剧本。而在许愿之前，女人先要种下树苗——比起许愿，更值得感激的是努力。本期思考同样听到“世界是个草台班子”，为什么有人从此对世界失望，有人却觉得“是不是咱也可以试试”？差别是勇气、配得感，还是我们太习惯用自己的后台，去判断别人的前台？随地大小许愿看起来是幸运，背后其实是一种能力：敢把愿望说出口，把没有被完全摁死的拒绝变成下一步，并且愿意为一个念头付出十几年的后台积累。这些能力里，哪一个是我们最缺的？如果发愿更多的是“你想成为一个什么样的人”，那么在向宇宙开口之前——先种下树苗、先表达需求、先给自己正反馈，哪一步是你一直没有迈出的？本期分享1. 《年龄只是一种感觉》｜鲁豫翻译，Coco 在结尾念的段落出处：“女人种下树苗，女人越长越高，女人爱得热烈，你们还会在风雪中舞蹈。”2. 月下的老柴｜老柴的创业视频栏目，build in public，小红书、视频号、抖音、B 站同步更新3. “全网寻找赛考斯”｜26 年前捐出 5000 美金支持治沙英雄殷玉珍的美国历史老师，今年夏天将受邀再访中国

Do you want to become the smartest person in the room this weekend, or do you just really love listening to Simon desperately defend the scientific validity of his trivia?

You've seen the wildly successful crowdfunder. I'm joined by the lead brain behind the game Night Shift: Devil Division from Slightly Reckless Games. Why did they use Draw Steel as a base, and what did they change from the base game? And what are ascended techniques?Links to everything: https://goblinpoints.com/2620#linksChapters:00:00:00 - Intro00:00:43 - Interview01:00:12 - OutroSupport the showGoblinPoints.comStawl.appDiscord ServerLeave a comment on YouTube or Spotify, or send me an email at tips@goblinpoints.com.Theme music by Patrick Haesler.Art by Chris Malbon.

Curtis Dery, executive vice president at Xerox IT Solutions Canada Curtis Dery, executive vice president at Xerox IT Solutions Canada (doing business as Powerland), has been living the HPE GreenLake story since before most Canadian partners knew what as-a-service infrastructure meant. At HPE Discover 2026, he joined In The Channel to talk about what this week’s announcements look like from the practitioner’s desk. Dery’s team won HPE’s Canada GreenLake Partner of the Year in 2022 and has kept the streak going, but he’s clear that the barrier to adoption was never the technology. “Customers are facing constraints financially,” he says, citing tariffs and geopolitical pressure. That’s why he sees the 90/9 financing offer and 150% credit line expansion as genuine deal-closing tools. “It helps open more doors and close deals even sooner.” He also sees the channel-only expansion of Private Cloud and Zerto as a deliberate strategy his team was ready for, thanks to deep ties with HPE’s advisory councils. The real differentiator, he says, is operationalizing customer processes so they can move from 20-30 projects a year to 50-70. Where Dery gets animated is AI. He calls the current moment “the most exciting time in any of our careers” and describes AI as a “digital goldmine.” His team runs internal hackathons to build reps with large language models, work that has already helped Powerland close four of the largest infrastructure deals in the world – all out of Winnipeg. But he’s also blunt about tokenomics: “The burn is real.” On sovereignty, Dery points to the Anthropic government oversight incident as validation for private AI. “If I’m a customer and I’m all in on that model, what would happen?” He sees HPE’s network optimization and Private Cloud AI stack as the hedge. Read Full Transcript Robert Dutt: Hello and welcome to In The Channel from ChannelBuzz.ca, bringing news and information to the Canadian IT channel community for the last 16 years. I’m Robert Dutt, editor at ChannelBuzz.ca and your host for the show. We’ve been on a bit of an unscheduled hiatus, but we’re back. We’re going to get back into the swing of things right now, and we’re going to start that off by finishing our coverage of this year’s HPE Discover 2026. Today’s guest is Curtis Dery, executive vice president at Xerox IT Solutions Canada, which most of the channel still knows as Powerland. Curtis is based in Winnipeg. His team covers the country. He’s been living the HPE GreenLake story since before most Canadian partners knew what as-a-service infrastructure meant. His team won HPE Canada’s GreenLake Partner of the Year back in 2022 and has kept that streak alive. They were the first partner to sell a GreenLake deal in Canada, the first to sell VM Essentials, and the first to sell a cyber vault. But Curtis isn’t just a sales exec. He’s genuinely hands-on with emerging technology, running internal AI hackathons with his team, and has a perspective on the announcements from Discover that come from actually closing the deals, not just reading the press releases. He joined me on site at Discover to talk about what the new financing tools, the channel-only expansion, and the AI story mean for partners on the ground. Let’s get right into it. My chat with Curtis Dery. Robert Dutt: Curtis, thanks for taking the time. I appreciate it. Curtis Dery: Absolutely. Thanks for having me. Robert Dutt: Before we get into this week, I have to acknowledge – just having been in this industry a while, you’ve got Xerox and what is formerly HP at a conference here. Slightly unexpected combination on the surface. Most people’s mental model of Xerox is still copiers, but you were running Powerland as one of the leading HPE infrastructure providers in Canada long before that. What does the Xerox relationship mean in practice for the IT business? Has it changed how you go to market with HPE, or does Powerland essentially operate in its own lane? Curtis Dery: You know what, that’s a great question. The way the market’s changing, the industry is changing, businesses are needing to change. That was the reason why Xerox looked at acquiring us – to help go through the realignment and the changes that they’re making as a business. Obviously, from a print perspective, looking at the industry challenges it was going through through COVID and post-COVID and just the market shift around that, having a focus around infrastructure and technology and driving those outcomes with our customers helped them amplify the customer base that they have across North America. Robert Dutt: You were doing GreenLake before a lot of Canadian partners knew what it was. You won the Canadian GreenLake Partner of the Year back in ’22, closing deals in the as-a-service model when it was still a pretty hard sell to customers used to buying it outright. Now HPE’s on stage talking about 90/9 financing and offering 150% expansion of credit lines. For someone who’s been engineering these deals since the beginning, what do these tools mean specifically? Do they change what’s possible for you, or are you already doing – you already have your system set up and ready to go? Curtis Dery: Yeah, I mean, being fortunate to be a little bit on the front edge of GreenLake, we’re fortunate to be Partner of the Year four years in a row, and from a North American perspective, Partner of the Year to make it five. What that created was just validation that how we’re going to market and how we’re executing it is a little bit more uniquely than others, and how we’re prepared to understand the customer, the outcomes that they want, and wrap that around operationalizing it through a GreenLake model. Having flexibility in some of these announcements helps with the challenges that we’re all entering – some of it unknown, some of it shortages, all these changes, and then you wrap that around obviously the disruption of AI. So having these flexibilities of what they want to do around credit is definitely needed because customers are facing constraints financially – just with the cost of, from a geopolitical impact perspective, tariffs, all these things are real. So HP coming to the table with new offerings helps open more doors and close deals even sooner than expected sometimes. So we’re always looking at making sure, yes, we have a foundational core that we can execute on with a rinse and repeat with a proven track record, but always making sure we’re aligned with the changes that they’re making and making sure we’re enhancing our offering with them, a walk and step together. Robert Dutt: It feels like they’re acknowledging that one of the barriers to GreenLake adoption isn’t the technology, the concept, or anything like that. It’s the customer’s budget cycles. And it sounds like you’re saying that’s the right diagnosis from what you’re seeing in the Western Canada market. Curtis Dery: Yeah, and I think also people sometimes think it has to be OpEx. There’s a balance that you can still capitalize GreenLake as well too, and then do a term top-up depending on the utilization they have, but also operationalizing it from a financial [perspective]. So that flexibility is still there. I just think sometimes that message isn’t out there at the street level. So that’s where our value comes in as a partner, right? To understand where that noise and friction is and remove the friction. Robert Dutt: Three products went to channel-only at Partner Growth Summit this week: Private Cloud, PC 3000, PC 1000, and Zerto. Last year it was VM Essentials. It seems like it’s clearly a deliberate expansion of that strategy. From where you sit with that infrastructure-heavy book of business, is channel-only a meaningful strategic signal for you, or is it about filling the gaps for customers who need DR and private cloud but haven’t had a clean vehicle to buy it through you? Curtis Dery: That’s a great question. I think, fortunate to have a strategic partnership with HP, we sold the first cyber vault in the country. And so same with VME, we sold the first in the country, and same with GreenLake. So there’s a theme there, right? Being so strategically aligned with them from executive level down to technical level, I’m on their advisory council from a GreenLake perspective. My pre-sales engineer is the ambassador on the GreenLake program. Because of that exposure, we get line of sight a little bit earlier. So then we’re already preparing on how we’re going to market to augment some of these announcements that they’re doing, and then wrapping around our own little secret sauce to that to be able to expedite the sales and making sure that we’re taking down the logos together. Robert Dutt: What is that secret sauce, in whatever depth you wish to share in this forum? Curtis Dery: Well, I think sometimes getting down to the nitty-gritty of what GreenLake really does, and that’s operationalizing the customer’s process to be able to allow them to be more agile within their own business. So instead of going to a traditional market and doing a traditional way of getting quotes, going to an RFP process, all those things take time, money, and energy. And when you do that, you then don’t have time to focus on the business to drive the outcomes you can do. Now, with our customers from a GreenLake perspective, that agility of being able to streamline that process – we have our customers that are able to go from 20 to 30 projects a year to now 50 to 70 projects a year. So then they get to see the benefits of how fast we can make their business move, get the outcomes that they want so they can start to accelerate further. Robert Dutt: You heard the partner branded services announcement this week. Curious what you thought of that and how it kind of maps with what you do in terms of, are you already running that services-led model, or are you looking for opportunities to have HP back you up but still go under your brand? Just curious how it hit. Curtis Dery: For us, it definitely hit. But yes, we also do it as well that way. But again, it’s the right tool at the right place at the right time. And sometimes we may need them, they may need us, or it’s an augmentation of both. And that’s the beauty that I love about HP is the investment to the channel, always staying aligned at the street level and making sure it’s very predictable on how you can make bets jointly with them. So it’s a flexibility thing. Robert Dutt: A hundred percent. Curious what’s driving the HP business for you right now. What’s kind of hitting, what are customers talking to you about, what’s driving it forward? I have to imagine AI is part of that. Curtis Dery: Yeah. And I think AI was a little bit of paralysis in the market, right? People were frozen of like, “What do I do? Where do I start? What type of technology? Do I go to a public LLM?” Or you hear this word, “sovereign,” and what does that mean? And I think the perfect storm is brewing. But the beauty is that HP has made the right investments, right? Acquisitions to now truly be ready for what the market is going to be hitting with right now. Which is, you look at the announcement of what happened with Anthropic last week. Government oversight, they said shut down that model. Well, if I’m a customer and I’m all in on that model, what would happen? And so this created that validation of why private sovereign AI with HP wrapping around customers’ data and giving them real hardened AI outcomes within their environment, and then choosing if they need to go into the public LLM. And so getting ready for that market condition is what’s going to drive success and velocity with HP in the market. Robert Dutt: Along with the idea of tokenomics, that idea of AI projects getting stuck in, and maybe hand-in-hand with tokenomics in fact, that idea of AI projects getting stalled out in the implementation or the proof-of-concept phase and not getting to full implementation is a theme that we’re hearing from HP and from just about any vendor who’s playing in the space this year. It seems to be one of the big catches. I’m curious how you’re seeing that reflected in your customer base, if they’re kind of getting to a point of doing POCs and then starting to discover, “Well, wait a second, this could get real expensive, real fast.” Curtis Dery: I’m 1000% [there]. Right? The burn is real. We have customers that knew that they have to start getting their battle scars and learning from the AI and understanding how does it work, how do we integrate it, how do we make sure there’s no hallucinating, how do we trust it, how do we do all these different things? My analogy I like to use is, at the end of the day, we all need refrigerators. But a lot of people probably don’t remember who invented the refrigerator. They just know they needed one, right? That’s the same with the public LLMs, right? You need the refrigerator when you need to go into it. What we do with our customers is show them how to take a Coke can and put it in the fridge and bring it out of the fridge. And so we help them navigate it so then tokenomics is not exposed as much, right? They can manage their cost, manage their environment, and choose where they want to put their data. I think the tokenomics is definitely a real thing and I think we’re going to find out significantly what that means in the next 120 days. Why? Because these companies are going IPO and you now know where the math is mathing, right? And so that’s going to show us a lot on what the true tokenomics looks like. Robert Dutt: You touched a little bit on the importance of sovereignty in customer discussions, but can you tell me a little bit more about how that’s showing up in terms of what customers are asking about and how you see that trending and evolving as an interest and a care about, both on the geopolitical front and, as you say, on an issue like Anthropic suddenly having to pull access to the latest model? Curtis Dery: Yeah, a thousand percent. I think when you hear the word sovereign, I always ask people, “What does that mean to you?” Because when you look at the World Economic Forum, for example, in February, what did they announce as the next pandemic, the cyber pandemic? Why? You’ve got scale of agents running everywhere. People don’t know what is a good agent or a bad agent, right? And if you look at the internet bandwidth since December till now, it’s increased over 12x of volume. Do you know how much traffic is now coming down? So now people are going to need to get prepared about how do you control your network, your data, your access, and sovereign that so that you’re secure so that if a bad day occurs, you don’t have the public exposure. And that’s why you hear from Antonio Neri and the focus around the network. How do you optimize that network? How do you secure that traffic and have the access to where you need to go and ensure that it can handle the scale? So that’s why this storm is brewing in front of all of us right now. Robert Dutt: Looking at your background, it’s clear that you’re not just selling infrastructure. You’re genuinely interested in AI and emerging technology. And it seems like you like to get pretty hands-on. As you’re at an event like this and you’re hearing the announcements and seeing what’s coming and what they’re talking about, what are you really excited to get your hands on and play with, and beyond that to actually get in front of your customers either now or down the road as it becomes more concrete? Curtis Dery: You know, I tell people this is probably the most exciting time in any of our careers because it’s the first time in any of our careers that it’s a level playing field, where it’s up to you to grab the baton of AI and understand how do you use it, apply it, and get the outcomes and innovation that you want to do with people. The tagline I like to use with my team internally is, we’re not underpinned by anyone anymore. We have the opportunity to dream, to build, and execute, and we can use AI technology to do that. And so I call it the digital goldmine. We get to go inside these LLMs and mine what we want out of that and be able to take advantage of what we can do with our customers. And that’s the one thing I enjoy the most is understanding, okay, what tools can I use, whether it’s from PCAI and apply our own private AI strategy around that. I’ve worked with a lot of advisory around a lot of the latest LLMs that are out there, but also some of these private ones like [Mistral AI] and understanding how it’s a puppet master to the public AI and how to optimize white space within a customer’s environment to show them where they have inefficiencies, profitability, when they can take the market in a different way. And that’s what AI does – allow customers to be agile, at edge, on time, and be able to really disrupt if they choose to. And I think it sounds a lot daunting for a lot of people, right, to understand how do I get proactive now with AI and not get disrupted by it, because you don’t know if you can wake up and all of a sudden your competitor is something that you didn’t expect. And so I think being able to just dive in and learn. A lot of people say, “Well, I don’t know much about AI.” None of us do. This is all the latest technology. So I tell people to speak to it, learn from it, and just start understanding how it works. So then at the end of the day, you can now augment it because it ain’t going away. If you think about from a generational perspective, we have kids that are going to be born in AI. They don’t even understand what that means. So it’s exciting times. And I tell people embrace it, because like I said, it’s the first time in history that nobody’s really walking in a room saying, “I got 10 years in AI.” Everyone’s like, “Hey, I’ve been working with it for six months. Cool.” Just like all of us. It’s how many people are putting in the reps with it. Robert Dutt: What are you pulling out of that goldmine so far at Powerland? What are you doing in terms of both – how’s AI changing both what you’re doing customer-facing, and internally your own operations and how you think about AI within the org? Curtis Dery: Yeah, absolutely. So I mean, we were fortunate being ahead of it from an AI perspective and understanding our domain strengths, using AI to be better prepared for our customers and think through strategies with them. And with that, we were able to build out blueprints where we were fortunate to close out four of the largest deals in the world with four different vendors out of a city called Winnipeg. And a lot of people came to me and said, “Curt, I don’t get it. We’re not doing this in New York, Toronto. You were doing this in Winnipeg. How are you doing this?” And I’m like, using AI to get better prepared to understand how do we simulate an environment to say, “This is the customer. What can we do to drive out these types of outcomes? And what does this look like from a strategy?” We get the blueprint and now we go and see the customer and go, “Does this make sense?” And they go, “Yes. Well, let’s go execute that with AI.” And so that’s the advantage that we get to do. And then from an internal perspective, I love having our own internal roundtable hackathons. What’s something we want to do? Throw it on the whiteboard. Everybody has their AI account and go, “Okay, how would you approach that?” So then our team is learning how to put those reps in to say, “Well, I would approach it this way.” And it’s a cool exercise to see how everyone thinks differently. And that’s the beauty about AI. We’re all going to prompt it differently. We’re all going to work with it differently and then take those unified approach of everyone’s pieces, put it together and go, “Okay, now we solve the puzzle together.” So I really enjoy the ability to be able to scale so rapidly with it. It’s an exciting time. I feel like we’re built for this era. Robert Dutt: And I’d imagine a lot of those ideas that are coming out in the internal hackathons are eventually going to find their way into what you’re doing with customers as well. So that’s a nice plus. Curtis Dery: Yeah, absolutely. Robert Dutt: As you point out, you’re in Winnipeg, presence across Western Canada. I’ve talked to a couple of other Canadian partners this week, and I’m getting this consistent theme that Canadian customers right now are in their moment – between sovereignty, between AI infrastructure refresh, between really starting to get AI in play rather than playing with AI. Does that map with what you’re hearing from your customers in the prairies and the West? And where do you see HPE fitting into that story for the balance of the year and beyond? Curtis Dery: Yeah, I think we touched on it lightly, right? The changes that happened with the government oversight last week, I think opened people’s eyes on what their approach is to public LLMs. And then also understanding costs, constraints, all these things that have been hitting our markets and hitting customers’ budgets and challenges. It’s a difficult time to be a CIO right now. When you’re sitting there and you have to protect them from a cybersecurity perspective, you have to have a future of understanding where AI fits into this, and never mind constraints around cost and all that stuff. It’s a tough time to be an executive for a business right now and understand how you can be profitable, scale all these things while you’re facing all these challenges in the market. So being prepared in Canada of how we’re going to our customers is understanding how to package what HP has done effectively well on the overall strategy around GreenLake and saying, “How do we now enter the customer and say, ‘You can now do on-demand AI in your environment predictably, cost-effectively, compliance and govern, and now you can choose how you want to scale that rapidly?'” I think finally, we’re starting to see that curve get around the corner where customers are jumping into wanting to do it this way. It’s just such a learning dynamic exercise right now, right? Because at first it was ChatGPT and then it was Grok and then it was Claude and it just kept going and going. People are not talking about the disruption that happened out of China too with their LLMs. So if you look at DeepSeek, Kimi and all these models, they’re doing exactly what Claude and these others can do at 75% cheaper. So when people start to realize, “Well, I can run that SDK natively inside my environment way cheaper than going to a public API Claude license,” people are going to look at that and go, “Oh, what makes sense now? Because the math ain’t math.” Robert Dutt: That theme is coming up in a lot of different places, isn’t it? Last one for me, whether it’s something we’ve already covered off or something else, what’s the one thing that’s really caught your attention here at Discover this week, the thing that you’re going to take back to the team and on Friday or Monday or whenever you’re first in there saying, “By the way, this is what I heard. This is what we got to get ready for.” Curtis Dery: Well, a few things. One is truly being prepared on the foundation of the network and understanding what does that mean to have an optimized AI network both internally and externally for the customer. I think there’s a high, high value in that. I learned that on the journey with cloud. Everybody wanted to go to cloud. Love the destination. Nobody talked about the highway to the cloud. Nobody talked about the cloud tax of egress coming out of there. So there’s a lot of lessons and best practices that came from the cloud journey that we can now reapply to the AI journey. So focusing on that is huge. And then understanding the intelligence layer and understanding [NVIDIA] Morpheus is an extremely powerful tool and understanding how does that fit into the entire reference architectural stack with PCAI and understanding how do we build on top of that. And that’s some of our secret sauce of what we’re doing, being able to do our own private SDK on top of PCAI so customers can truly control their own AI platform. And so that’s the focus that we’re going to do. And we’re super excited to get velocity going into Q4 with HP so that in 2027, I expect a big year. Robert Dutt: All right. Well, good luck on bringing that back to the team next week and good luck on that big year. And thanks again for taking the time on what I’m sure has been a very busy week. Curtis Dery: Absolutely. And I welcome the time and being able to share this conversation with you. So we look forward to doing it again. Robert Dutt: There you have it. Curtis Dery from Xerox IT Solutions Canada. I’d like to thank Curtis for his time. If you’re finding value in these interviews, I’d appreciate if you’d follow or subscribe to the show. You can find the podcast on Apple Podcasts, Spotify, YouTube, and most major podcast directories. Ratings and reviews are always welcome. A few things that stood out for me from this conversation. One is Curtis’s framing that the real barrier to GreenLake adoption has never been the technology, it’s the customer’s budget cycle. The 90/9 financing and expanded credit lines aren’t abstract partner program benefits. They’re deal-closing tools for partners who are already in the room with constrained CIOs. Another is his digital goldmine metaphor for AI. The idea that for the first time in our careers, the playing field is level and what matters is who’s putting in the reps. But he’s also refreshingly blunt about the burn on tokenomics and the need for partners to help customers manage costs as AI moves from proof-of-concept to production. I appreciated his point about sovereignty not being theoretical anymore. The Anthropic incident gave customers a concrete reason to ask hard questions about public LLM dependence. Finally, it’s worth noting that the company is closing some of the largest infrastructure deals in the world out of Winnipeg. The Canadian channel is not a Toronto-only story, and this is a reminder of that. Until next time, I’m Robert Dutt for ChannelBuzz.ca, and I’ll see you in the channel.

Our stories tonight treat us to many sunny moments in and around the Inn. They are stories about a stately home at the end of a long drive, a lake shimmering as rowboats glide across it, coffee cake and names in a ledger and a place to rest and enjoy some of the sweetest days of summer. Subscribe to our Premium channel. The first month is on us.

Dr. St-Onge is the founding Director of the Center of Excellence for Sleep & Circadian Research at Columbia University Irving Medical Center. The overall focus of her research program is the study of the impact of lifestyle, specifically sleep and diet, on cardiometabolic health. Dr. St-Onge has been NIH-funded since 2008, conducting innovative, cutting-edge clinical research combining her expertise on sleep, nutrition, and energy balance regulation to address questions related to the role of circadian rhythms, including sleep duration and timing as well as meal timing and eating patterns, on cardiometabolic risk. Dr. St-Onge was Center Director for the American Heart Association funded Go Red for Women Strategically Focused Research Center, aimed at determining the causality of the relation between sleep and cardiovascular disease and the specific role that sleep plays in the health of women throughout the life cycle. She is a pioneer in this field, having chaired the first scientific statements endorsed by the AHA on sleep and cardiometabolic health as well as meal timing and frequency and cardiovascular disease risk prevention. More recently, she chaired a follow-up scientific statement highlighting the role of multidimensional sleep health for cardiometabolic health. She is a Fulbright Scholar, and the recipient of an NHLBI Outstanding Investigator Award from the National Institutes of Health. Dr. St-Onge has authored over 200 peer-reviewed publications and is author of Eat Better, Sleep Better: 75 recipes and a 28-day meal plan that unlock the food-sleep connection.Support the show

The burgeoning East Coast broccoli industry is helping slightly lower costs and reduce reliance on drought-prone Western states like California, and the NCGA released a new strategy outlining how the U.S. corn industry can build demand for new domestic and international markets.

Hey hey! It's the first pod from Vermont Summer 2026 and I'm coming to you slightly jet lagged from a beautiful porch. First, a little life update now that we have landed in Vermont and have the next 3 weeks here. Then, Rapid Fire Questions. I decided to turn this into a rapid fire episode and I get into all my little obsessions, current thoughts, ideas, and alllll the things I've been loving. Hope everyone had an amazing 4th of July weekend! This episode is brought to you by Staples. If there's ever a time parents deserve an Easy Button, it's back to school season. To shop the most wonderful deals for school, check out staples.com/WITHWHITThis episode may contain paid endorsements and advertisements for products and services. Individuals on the show may have a direct, or indirect financial interest in products, or services referred to in this episode.Produced by Dear Media See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

The world's monumental leaders have made peace with discomfort. They know the path to anything extraordinary drives directly through difficulty. When circumstances are hardest, they lean in. When the pressure is greatest, they do their finest work. My latest book “The Wealth Money Can't Buy” is full of fresh ideas and original tools that I'm absolutely certain will cause quantum leaps in your positivity, productivity, wellness, and happiness. You can order it now by clicking here.FOLLOW ROBIN SHARMA:InstagramFacebookYouTube

The ASX 200 closed down 13 points at 8,831 (0.2%) after drifting from positive to negative throughout the day. The banks were a little sloppy, with WBC down 1.1% and the Big Bank Basket falling to $273.60 (-0.3%). The insurance sector also eased, while the rest of the financials were mixed.REITs also had a mixed session, with CHC down 0.7%, while GMG edged slightly higher. Industrials lacked direction. Healthcare was the standout sector, with CSL up 2.0%, RMD rising 1.3% and SIG adding 1.1%. Technology stocks also found support, with solid gains in WTC and XRO, both up 7.3% and 1.8% respectively, while REA and CAR also finished higher.Resources were mixed, with BHP down 0.8%, while FMG rebounded 0.9% from Friday's losses. The gold sector was in focus after GMD launched a rival bid for VAU, joining RRL in the takeover battle. Despite the M&A activity, NST fell 1.8% and EVN eased 1.6%. Lithium stocks were also slightly weaker, with PLS down 1.7% and LTR falling 2.9%.In the oil and gas sector, despite little movement in crude oil futures, positive broker commentary helped WDS rise 0.8% and STO gain 1.4%. Coal stocks drifted lower, while uranium stocks were little changed.In corporate news, it was all about the new VAU bid from GMD. We also saw a solid quarterly from GGP, while WOR firmed 0.2% after securing a new consultancy agreement. In the tech space, IFT edged 1.4% higher following an independent valuation of its holding in CDC.There was nothing of note on the economic front today.Asian markets mixed, Nikkei 225 down 0.5%, HK up 1%, China up 0.2%. Kospi down 1.5%.US futures: Dow up 8 pts, Nasdaq up 223.Marcus Today – Daily Market InsightsMarcus Today provides clear, practical commentary for self-directed investors – covering markets, portfolios, education, and decision-making without the noise.If you'd like to go further:Start a free 14-day trial of Marcus Today http://bit.ly/mt-trial-podcastJoin Marcus Today Use code MTPODCAST for 10% off http://bit.ly/mt-join-podcast-offerMT20 – Managed ETF Portfolio A professionally managed portfolio run by Marcus Padley and the team, using ASX-listed ETFs with active market timing. http://bit.ly/mt20-podcastPrinciples – How We Think About Investing A short video series on timing, behaviour, and decision-making. No stock tips. http://bit.ly/mt-principles-podcast—Disclaimer This podcast is general information only and does not consider your personal circumstances. It is not personal financial advice.

本期摘要“在穿墙而过的过程中，把自己给拆了。”一场原本要像往年一样共襄盛举的生日聚会被薇薇喊停，只有三个人围坐着录一期播客。当一个人可以随时颠覆自己最看重的仪式，她在经历什么？话题从某公开活动上薇薇“演砸”的那一刻讲起，一路滑向更难的地方：我们既渴望被看见，又厌恶所有人都在刻意表演的场域；既想做自己，又无法完全离开世界给出的规则；既想保住真诚，又不得不承认，掌声、位置、影响力和被认真对待，仍然牵动着我们。当一个人试图穿墙而过，却发现自己先被拆开了，那份撕扯该如何安放？51岁，真正的成长，是终于允许自己成为一个完整的人。不是一个永远正确、“彻底脱离了低级趣味”的人，而是一个允许复杂存在的人：既喜欢舞台，也厌恶表演；既希望被尊重，也知道title不能定义自己；既有野心，也开始学习放下；既热爱这个世界，也知道世界充满幻象。这些不需要统一，也不需要消灭其中任何一个，它们共同组成了“我”。“Render unto Caesar the things that are Caesar's, and unto God the things that are God's.” 凯撒的归凯撒，上帝的归上帝。可以进入凯撒的世界，也知道什么不能献祭给凯撒；可以享受被看见，也可以不被那束聚光灯所裹挟。过去的生日像庆典，今天更像纪录片，记录一个人如何慢慢停止和自己对抗，和自己站在一起。时间轴02:50 当生日不再用来证明一场原本盛大的生日派对被叫停，热闹退场之后，真正的问题才显影：生日究竟是在庆祝自己，还是在向朋友、关系和世界证明自己现在很好？当一个最被重视的仪式也可以被推翻，被推翻的也许正是那个"应该如此"的自己。05:43 如果没有人知道这一天当生日不再被他人的祝福、朋友圈的反馈和盛大的聚会定义，一个更安静的问题出现了：如果这一天无人知晓，你会怎样把它过好？答案不再指向形式，而指向一种更内在的愿望——把此刻真实的生命状态记录下来，而不是把它包装成一个可观看的celebration。08:03 反对那个无处不在的"应该""和自己站在一起"不是一句温柔的安慰，而是一种立场转换：不再自动站到"应该"那一边。应该办生日、应该兑现承诺、应该看起来很精彩、应该不辜负外界期待，这些声音并不总是错的，但它们不能永远替真实需求做决定。17:26 舞台的刺痛：想被看见，也厌恶表演舞台带来的不是简单的不适，而是一种更复杂的自我撞击：一边渴望在重要舞台上被听见、被尊重、被认真对待，一边又厌恶名利场里无处不在的表演、排位和工具化。最难承认的不是那个场域虚假，而是自己其实也在乎它。30:01 名利不是抽象词，而是身体经验所谓名利场并不只存在于宏大的判断里，它藏在座次、发言顺序、谁坐在中心、谁被放到边缘这些细节中。人一边批判等级和工具化，一边又会被自己是否被重视深深牵动。这里真正被看见的，是那个既冷眼又在乎的自己。32:32 想被看见，是虚荣吗想被看见、被听见、被当回事，究竟是虚荣，还是一种存在需求？当"虚"和"荣"被拆开，问题不再是要不要掌声，而是掌声是否已经成为自我价值的来源。也许真正需要警惕的不是想被看见，而是把自己完全交给别人怎么看。41:42 对于好学生来说整个世界都是考场一旦进入某个规则，就本能地想赢；哪怕知道规则不合理、不值得认同，也还是忍不住想拿第一。这个困境不只属于某一个舞台，它属于许多被"优秀强迫"的人：外部世界给出题目，内在的小孩立刻开始答题。57:35 穿墙而过时，先被拆开的自己"在穿墙而过的过程中，把自己给拆了"是这一期最深的意象。一个自己要上台、交付、赢得尊重；另一个自己想保住真诚、自由和赤子之心。真正困难的不是选择其中一个，而是如何不把任何一部分自己彻底献祭掉。01:00:24 工具化自己，是否也可能是一种自由工具化并不总是堕落，有时它是角色、责任、策略，甚至是成年人不得不掌握的手段。问题不在于是否进入游戏，而在于进入游戏时，自己还知不知道为什么而进、为谁而做，以及哪一部分绝不能被交换。01:08:29 成功和做自己，能不能同时成立做自己和成功并非必然矛盾，但叠加在一起从来不容易。有人先保住自我，给成功留下余地；有人把自我藏得很深，等到拿回规则之后再展开。普通人的难处在于：既想保有真实，又无法完全拒绝世界的奖惩系统。01:13:30 凯撒的归凯撒，上帝的归上帝真正的自由不是退出世界，而是重新建立秩序。舞台、职位、掌声、达沃斯属于凯撒；真诚、热爱、创造和那个无人看见时仍然愿意做事的自己属于上帝。可以认真上台，可以享受掌声，但不能把灵魂押在聚光灯上。01:18:08 选择题逼出的价值排序如果一件事影响很大，却没有人知道是你做的；另一件事影响有限，却让很多人看见你，你会选哪一个？这样的极端问题不一定有标准答案，却会照出每个人此刻真正想要的东西：影响力、署名权、被爱、被懂得，或者只是健康、快乐、有人一起玩。01:25:23 从庆典到纪录片过去的生日像大庆典，今天更像纪录片。它不负责证明一个人过得多好，只负责保存此刻的生命状态：仍然矛盾，仍然充满追问。51岁不是终于不再撕扯，而是开始允许撕扯本身也是自己。彩蛋01:28:55 AI眼中的自我画像一个小游戏：让AI根据长期对话总结"我是一个什么样的人"，那些看似夸张的句子，照见每个人如何叙述自己、期待自己、也安慰自己。01:31:17 把舞台还给世界，也把自己还给自己"把舞台还给世界，也把自己还给自己"意外呼应了本期的核心：终于承认自己喜欢舞台，也可以从舞台上回来。本期书影音推荐· 《大秦帝国》（第一部）——"身段欲柔，其心欲坚"· 《甄嬛传》——作为"谋定而后动"的例子· 《庄子》——薇薇生日祝词出处："独与天地精神往来，而不敖倪于万物"本期思考这涉及一种疗愈观：当你对自己感觉很差的时候，这究竟是来自自己，还是外部环境？当环境不友好的时候，我们能不能学会分辨，而不是指向自己——“把孩子留下来，把脏水泼出去？”

Lux Radio Theatre - Slightly DangerousBecome a supporter of this podcast: https://www.spreaker.com/podcast/harold-s-old-time-radio--4206392/support.

The Mechanics of Genetic Drift Plants are natural genetic mosaics. As they grow and divide over time, typos naturally accumulate in their DNA code, which are known as somatic mutations. Traditional vegetative cuttings and field-grown plants accumulate these mutations at a very low, linear baseline rate over decades. However, the extreme genomic degradation highlighted in the paper is driven by rapid generational cell cycling in vitro. Forcing an unorganized mass of cells to constantly divide and regenerate bypasses the plant's normal cellular quality control checkpoints. Somatic Embryos vs. Meristem Cultures Somatic embryogenesis involves stripping a plant down to a single cell or callus phase to regenerate an embryo. This is considered high risk for mutations because if the founder cell contains a mutation, that mutation becomes permanently fixed in every single cell of the thousands of plants propagated from it. This differs from meristem tip culture, which is the low risk, predominant form of tissue culture used in cannabis for clearing Hop Latent Viroid. Because meristem tip culture preserves the existing, highly organized architecture of the shoot apical meristem rather than forcing single cells to reprogram, the genetic risk is fundamentally lower. DNA Typos vs. Chromosome Catastrophes The high-stress cell cycling environment caused macroscopic genomic errors, such as whole-chromosome duplications called trisomies. In the walnut clones, these large-scale errors made it incredibly difficult to grow the tissue back out into healthy adult plants. The stress of rapid lab cell cycling also desilenced transposable elements, or jumping genes, allowing pieces of DNA to insert themselves randomly throughout the genome and disrupt normal gene expression. It is worth noting that not all mutations are bad. Small point mutations, or single base changes, happen constantly in nature as life being life. Most occur in non-coding regions and have zero impact, while a rare few can actually create desirable new traits as seen historically in citrus and wine grapes. Genetics vs. Epigenetics The guests distinguish between true genetic mutations, which are permanent changes to the A, C, T, G code, and epigenetic modifications, which act like chemical bookmarks such as methylation that change how a gene is read without altering the underlying sequence. Some instances of a mother plant losing vigor may actually be epigenetic shifts caused by environmental stress or endophyte and pathogen buildup over time, rather than a permanent genetic mutation. Actionable Advice for Cannabis Nurseries Commercial operations scaling up clones to the tens of thousands should utilize genetic sequencing early in the pipeline. Testing the early founder material can easily catch large-scale catastrophic mutations like chromosome duplications or deletions, protecting the nursery from mass-producing defective production plants. Whole-genome sequencing costs have plummeted significantly, and the guests encourage cultivators and nursery operators with unique, degenerating, or shifting clonal lines to collaborate with academic labs to sequence the data and map exactly what is changing. Guest Information and Contact Details J. Grey Monroe is an Associate Professor in the Department of Plant Sciences and the Genome Center at UC Davis. His lab studies how mutations arise across genomes, DNA repair, epigenomics, and genome evolution in plants, with applications in crop improvement and protection. Lab website: https://monroelab.org/ Email: gmonroe@ucdavis.edu Matthew Davis is a fifth year PhD candidate in the Plant Biology Graduate Group co-advised by Grey Monroe and Pat J. Brown. His research focuses on somatic mutation in orchard crops, an understudied genetic process that directly affects one of California's largest agricultural industries. Bluesky: @davismw.bsky.social Email: mtdavis@ucdavis.edu Research Links and Resources Peer-Reviewed Paper: https://www.pnas.org/doi/10.1073/pnas.2530182123 Shorter general audience article: https://www.ucdavis.edu/blog/not-all-clones-are-created-equal Slightly longer general audience article: https://www.plantsciences.ucdavis.edu/news/davis-monroe-somatic-mutations Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Welcome to The Times of Israel's Daily Briefing, your 20-minute audio update on what's happening in Israel, the Middle East and the Jewish world. Military correspondent Emanuel Fabian joins host Jessica Steinberg for today's episode. After Israel and Lebanon signed a deal that includes a partial IDF withdrawal from southern Lebanon, Fabian discusses the strikes against Hezbollah on Saturday and Israel's ability to continue acting against threats from the terrorist organization. For now, Israel will remain in the security zone it established in southern Lebanon, reports Fabian, withdrawing from only two trial areas as part of the agreement. Fabian notes that the deal's efficacy will depend on whether the Lebanese army will be able to exercise control over Hezbollah, which has already stated that it does not respect the deal. An IDF strike killed another Hamas terrorist, the nephew of the terrorist organization's political leader, Ismail Haniyeh, reports Fabian, part of the ongoing Shin Bet effort to locate all Hamas members who took part in the bloody October 7, 2023 assault. IDF Chief of Staff Eyal Zamir utilized a televised cadet ceremony to make it clear that the army will not back down from a pilot program to bring women into the armored corps, says Fabian, given the need for more combat soldiers and the availability of women who want to serve in tank units. Check out The Times of Israel's ongoing liveblog for more updates. For further reading: IDF says it struck terror operatives in south Lebanon, after framework deal announced PM: Iran, Hezbollah to have ‘no role in Lebanon’ under deal, Israel can maintain security zone IDF says strike killed Oct. 7 terrorist commander, nephew of ex-Hamas chief Haniyeh IDF chief says military needs ‘every male and female combat soldier’ Subscribe to The Times of Israel Daily Briefing on Apple Podcasts, Spotify, YouTube, or wherever you get your podcasts. This episode was produced by Ari Schlacht. IMAGE: Military correspondent Emanual Fabian joins host Jessica Steinberg for today's Daily Briefing (AP/ Mohammed Zaatari)See omnystudio.com/listener for privacy information.

这是一期有些特别的《Slightly Open》。这一次，是Coco Solo 主持，和 SO 的两位老朋友——简单心理创始人简里里、播客《文化有限》主播超哥——在线下聊了一期原本为六一准备的节目。从“什么是合格大人”，到情绪为什么不必永远稳定；从成为母亲以后，如何从孩子身上重新看见自己，到什么时候应该努力，什么时候也可以认输、放弃、休息。这场对谈虽然来的晚了一点，但和薇薇、老柴商量后，还是想把它作为一份迟到的六一儿童节礼物送给大家。有时候，好好生活不是变成一个更正确的人，而是少一点“应该”，多一点身体、感受、关系和真实生活。希望从这个六一开始，我们都可以练习做一个不那么合格、但更真实的大人。本期时间轴【00:04:07】超哥：我已经很努力假装是一个合格大人了，怎么还是第一个想到我？【00:05:03】简里里：“我觉得我太合格了。”【00:06:51】陪孩子过六一，母爱额度燃尽，还算不算一个好妈妈？【00:10:07】为什么我们心中的“合格大人”，总是要吃苦、奉献、燃烧自己？【00:11:48】里里：人的情绪不可能稳定，真正需要稳定的是行为边界。【00:13:02】情绪没有好坏，它首先是在提醒我们：累了、饿了，还是某个需求没有被看见？【00:16:24】成为母亲以后，我们想养育一个快乐的孩子，还是一个合格的孩子？【00:18:48】为什么我们允许孩子成为自己，却很难用同样的方式对待自己？【00:19:29】超哥的35岁分水岭：搞砸了，好像也没有什么大不了。【00:22:24】里里：我确实在意别人怎么看我，也不再逼自己必须做到完全不在意。【00:24:34】“做所有正确的事情，lose all the fun。”【00:27:14】所谓“活人感”，不是不努力，而是不再每件事都死磕到底。【00:27:59】超哥：“这事我认怂了，我不行了，我不努力了，我放弃。”【00:30:36】Coco：我开始学习，不再为每一件事情解释。【00:32:14】“美好生活配比”大公开：工作、孩子、运动和自己，各占多少？【00:33:09】女性选择照顾家庭，为什么也可能面对另一套“不够独立”的审判？【00:34:28】真正的问题不是选事业还是家庭，而是女性能不能拥有自己的选择。【00:36:36】只要有“合格”两个字，就意味着有标准；有标准，就意味着迎合。【00:37:35】超哥一年瘦40斤：从认真吃每一根面，到泳池里和陌生大爷暗自比赛。【00:41:23】情绪坍塌的时候，要不要立刻把自己“救起来”？【00:42:36】里里：如果没有一个必须解决的问题，为什么一定要救？【00:44:01】怎样通过桌面的温度、脚底的触感和一碗面，把自己拉回当下？【00:47:22】什么是正念进食？吃饭的时候，只是好好吃饭。【00:49:41】为什么别人问“你最近好吗”，成年人总是回答“挺好的”？【00:50:36】你的感受对你自己最重要，但并不意味着别人必须为它负责。【00:53:01】讨好、回避和压抑，也可能是曾经帮助我们活下来的盔甲。【00:56:55】现场提问：回避创伤，是不是一件坏事？【00:59:56】真正带来创伤的，可能不只是坏事发生，而是那一刻的孤立无援。【01:05:00】超哥的翻译：我搞砸了，却没有因此被责备、抛弃或离开。【01:07:14】三个人的“好好生活练习”：超哥｜少看手机，多见真人。里里｜好好吃饭，好好睡觉，然后保持运动。Coco｜多一些松弛，允许自己不时发作、偶尔坍塌。本期提及项目：北京 SKP-S × 简单心理「Let's Get Together 好好生活练习」播客：《文化有限》《那么问题来了》心理学概念：情绪言语化、正念进食、修复性情感体验、一型创伤与二型创伤本期思考你心中的“合格大人”，是谁定义的？情绪稳定，究竟是心理健康，还是一种外部期待？成为母亲以后，你有没有从孩子身上重新看见小时候的自己？当一件事情努力过，却依然只能做到40分，你允许自己放弃吗？情绪低落的时候，我们真的需要立刻振作吗？你的“美好生活配比”里，工作、家庭、身体、朋友和自己，各占多少？你的好好生活练习，准备从哪里开始？也欢迎在评论区告诉我们：好好生活练习，你打算从什么做起？我们会精选留言，送出由北京 SKP-S 和简单心理为大家准备的大小礼物。Slightly Open｜由薇薇、Coco（@Wang蔻蔻）和老柴共同主持我们在这里持续分享成长、困惑、观察与感受。也欢迎关注我们在小红书的同名账号。

Kev from Mojo in the Morning joins the pod! We’re talking all things Idlewild, the memories, the culture, and the exciting return of one of Michigan’s most legendary summer weekends.See omnystudio.com/listener for privacy information.

Today's headlines include: Prices increased by an average of 4% over the year to May, down from 4.2% in April, according to new inflation data from the Australian Bureau of Statistics (ABS). Papua New Guinea (PNG) has suspended the importation of all Australian chicken and egg products after the first mainland cases of a deadly bird flu strain. YouTube and its parent company Google have settled a case with a Florida teen who ‌claimed the platform caused mental health harms. And today’s good news: A new study from an international team of scientists shows Indigenous traditions can offer new insight into volcanic activity. Hosts: Emma Gillespie and Zara SeidlerProducer: Rosa Bowden Want to support The Daily Aus? That's so kind! The best way to do that is to click ‘follow’ on Spotify or Apple and to leave us a five-star review. We would be so grateful. The Daily Aus is a media company focused on delivering accessible and digestible news to young people. We are completely independent. Want more from TDA?Subscribe to The Daily Aus newsletterSubscribe to The Daily Aus’ YouTube Channel Have feedback for us?We’re always looking for new ways to improve what we do. If you’ve got feedback, we’re all ears. Tell us here.See omnystudio.com/listener for privacy information.

Ep 271 “Slightly Less Legal Shipped Discreetly” – National Gun Violence Awareness Month (Bullet Poof Bulletins) Celebrating the launch of eco-fiction anti-gun novella Bullet Poof and National Gun Violence Awareness Month, Avis Kalfsbeek brings back beloved Kitty O'Compost with the Bullet Poof Bulletins. Tonight on the Spoke-Easy stage, Kitty O'Compost deconstructs a leaked aftermarket catalog designed to exploit regulatory gray areas. This bulletin satirizes the distribution of unbranded drop-in components engineered solely to reverse-engineer standard safety compliance under the cover of "discreet" shipping. Inspired by the grounding, collaborative themes of Bullet Poof, this episode laughs at the shadow marketing funnel and reminds us of the true safety found in open, accountable community spaces. Resources: Bullet Poof is a hopeful eco-fiction novella about what happens when ordinary people refuse to accept the gun status quo. Get the book: https://www.aviskalfsbeek.com/bullet-poof National Gun Violence Awareness Month: www.wearorange.org Theme Music: "Turn the Steel" and punk intros produced by Avis Kalfsbeek (via ElevenLabs). Music Credits & Support: Buy LPs and music downloads directly from the bands' websites, or from platforms like Bandcamp where artists retain the majority of your purchase. This project is inspired by decades of punk ethos, raw energy, and the brilliant musicians who shaped the movement. The sonic landscape of this series was informed and inspired by: The Sex Pistols, Black Flag, Rites of Spring, The Buzzcocks, Minor Threat, The Clash, Social Distortion, Bad Religion, The Dead Kennedys, The Ramones, Jawbreaker, Fugazi, Rise Against, The Damned, The Stooges, Bad Brains, Bikini Kill, The Lawrence Arms, Husker Du, Pennywise, The Adicts, The Exploited, Descendents, Stiff Little Fingers, Crass, The Germs, Dropkick Murphys, Operation Ivy, Against Me!, Green Day, Blink-182, The Hives, Sleater-Kinney, The Violent Femmes, The Network, The Jam, The Gaslight Anthem, No Use For A Name, and The Interrupters.

Could a tiny injury to your brain change your personality? If your friends didn’t know something had happened in your brain, would they just think you're choosing to act strangely? What if the self is nothing but a fragile coalition of neural processes? Join Eagleman today with Masud Husain, a neurologist and neuroscientist at Oxford, to explore fascinating case studies about how changes in the brain lead to changes in the self.

Episode Title: Midwest Meltdown: 80-Degree Dew Points and the Ring of Fire!  Slightly more humid than classic St Louis Missouri. 00:03 - 01:04: Introduction to the heat wave and high dew points for next week, focusing on the Midwest and the consistent heat dome.01:04 - 02:07: Explanation of heat dome decameter readings and how dew points are the "hidden heat" despite seemingly moderate temperatures.02:07 - 03:08: Forecasting extreme heat indices (105-110°F) for next week, highlighting the unusual widespread 80-81°F dew points.03:08 - 04:14: Discussion of how wind affects perceived temperature in low vs. mid 90s, and the continued high humidity in the Midwest.04:14 - 05:22: Mention of Illinois tornado record and detailed forecast of an 81°F dew point around July 1st in western Illinois/eastern Missouri.05:22 - 06:47: Specific cities and their forecast temperatures and dew points around July 1st-2nd, with emphasis on central Illinois, Indiana, and the Iowa-Missouri corridor.06:47 - 07:51: List of cities most likely to hit 80°F dew points, and the periphery status of Chicago and St. Louis.07:51 - 08:52: Detailed tracking of the 589 decameter line and Chicago's position on the edge of the heat dome, intensifying to 594 decameters by July 2-3.08:52 - 09:55: Chicago falling out of the heat dome by Thursday night as the dome shifts southwest and a trough of low pressure approaches.09:55 - 10:43: The pattern breakdown for Chicago, with the dome shifting west and a cold front approaching by July 3rd-4th.10:43 - 11:46: Introduction of the "Ring of Fire" phenomenon: severe storms forming on the northern and western edges of the heat dome's 588 decameter boundary.11:46 - 12:49: Regions expected to experience repeated severe storms (Northern Wisconsin, Minnesota, Michigan, Iowa, Indiana) while Chicago may sit on the ring.12:49 - 13:17: Final summary of the Ring of Fire, explaining how the dome suppresses storms internally but pushes moisture to explode into storms on its periphery, affecting Chicago by July 2-4.20 Hashtags: #MidwestHeatwave #DewPointDanger #HeatDome2020 #ExtremeHumidity #RingOfFireStorms #WeatherEnthusiast #EuropeanModel #IllinoisWeather #IndianaHeat #MissouriClimate #IowaForecast #SevereWeatherRisk #SummerHeat #HeatIndexAlert #DecametersExplained #MidwestWeather #ClimateWatch #JulyForecast #WeatherNerds #StayCoolStaySafeBecome a supporter of this podcast: https://www.spreaker.com/podcast/weather-with-enthusiasm--4911017/support.Weather with Enthusiasm is produced by Kol Simcha Productions.New episodes drop daily (B'N)— a morning forecast at 7 AM and historical deep dives Tuesdays and Thursdays. Contact: kolsimchaproductions@outlook.comHistorical content is thoroughly researched and factually verified. After it has been factually verified it often will say so in the description. Should you find any mistakes, please email kolsimchaproductions@outlook.com so we can look into it and correct it. Not affiliated with any government agency or academic institution. Presented for educational and entertainment purposes — with meaning.Support the show — exclusive bonus episodes available to subscribers for just $2/month at spreaker.com/organization/kol-simcha

A well-done adaptation of the comedy about a small town girl who becomes a long lost heiress - Originally aired on December 30, 1949

The Blooming Court Ch. 10Rested and relieved in the Magnificent Mansion, the group breaks into different conversations. Arguile helps Turk with his Thieves' Cant; Zechs fiddles with the multitool, prompting him to tell Shanks about the tools at his disposal and ask if any can help; and he later goes to Hoshino's room to check in on him, as he knows that he's feeling the results of weeks and months of reconnaissance with the Journeyman, after which Zechs shares his experience meeting Tumra.Before starting the day's journey, Shanks goes out to scout and informs the group that there are more trees there than there were the previous day. After leaving the mansion, the party is contacted mentally by the Queen, displeased that the group passed their intended destination. A tense exchange occurs primarily between Hoshino and the Queen, and Hoshino convinces the Queen that the group will indeed retrieve the Song Bloom, on the way back from taking care of their other business, retrieving Glad's boon. The Queen, very obviously impatient and suspicious, tells the party to wrap up what they're doing quickly and retrieve the Song Bloom by day's end. Slightly relieved to have the conversation over, the group looks to Glad for guidance on where to go next and what to do. Looking out over the lake, Glad meditates briefly, then informs everyone that they will have to trust her, but they will need to wait until high noon before they can go anywhere. They understand her and reassure her that they trust her. They kill some time having a bit of a beach day before Glad slowly heads into the lake, and suddenly disappears.The group, concerned, tries to follow her in her wake and succeeds in reaching the temple entrance, where they seem to be looking at the water's surface from below their feet and can breathe normally. Once inside, Hoshino asks the group to gather for a spirit session to gather the magical energy needed for the Commune spell. Calling upon the Daughter of the Vine, he asks about their task at hand and what they should do. He gets answers, but not necessarily the ones he was at the very least expecting. Glad and the party traverse deeper into the temple and eventually find an orb that transfers Glad away from the party. Mildly concerned, they try to follow her, but to no avail. We end with the party discussing their exit strategy and whether they will continue to be pawns in the Queen's plans or suffer the wrath of defying the Fey Queen and heeding Shankise's warning to cease what they're doing.There's so much happening, and that's where we pick up…Find out what happens next in this episode of the Medusa's Cascade: Collateral Damage!Theme Music is written and performed by EfflorescenceMixed by Thomas Lapierre IIITitle Card by Pierce Graphics Check out the show at themedusascascade.com Hosted on Acast. See acast.com/privacy for more information.

Slightly later than billed, our latest episode sees a welcome return to Soundtacking to the utterly charming Finneas O'Connell, who joins us to discuss his score for Beef 2. We've already spoken to Sonny Lee, creator and showrunner of the hugely acclaimed and successful Netflix show, so please do listen to that if you haven't already. But it's always such a joy to take a deep musical dive with Finneas, who speaks so eloquently about his craft. We get into Bond and Barbie too!

Our stories tonight have us packing up the car and heading out of town to the cottage. They are stories about lounge chairs and lazy days, sailboats and swimsuits and listening to the waves as they rock you to sleep. Subscribe to our Premium channel.⁠⁠ The first month is on us.

Slightly younger versions of Earth's mightiest heroes team up because the one hero's brother, who would later also become one of Earth's mightiest heroes and then ... fix time? Or break it? ... anyway, he's got these space worms, and ... you know what, it's Avengers, you know what it's about. Listen to us revisit the first great team-up of the MCU!Plus, we'll talk about DISCLOSURE DAY, continue the ongoing evaluation of BACKROOMS and OBSESSION, drop in on SCARY MOVIE, HOPPERS, SWAPPED and more!

Link Up w/The Morning Sickness Digitally All Over:Instagram: @hms_98_official, @bosskupd, @bretvesely, @dickToledoX/Twitter: @HMSon98, @DickToledo, @bretveselyFacebook: @HMSKUPDYouTube: @hmspodcast9320, @98kupdRequest/Call in/Wakeup Song line:(IN AZ) 602.585.9800More HMS: holmbergpodcast.com, 98kupd.comEmail: dtoledo@98kupd.com, bvesely@98kupd.com, bbogen@98kupd.comSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Link Up w/The Morning Sickness Digitally All Over:Instagram: @hms_98_official, @bosskupd, @bretvesely, @dickToledoX/Twitter: @HMSon98, @DickToledo, @bretveselyFacebook: @HMSKUPDYouTube: @hmspodcast9320, @98kupdRequest/Call in/Wakeup Song line:(IN AZ) 602.585.9800More HMS: holmbergpodcast.com, 98kupd.comEmail: dtoledo@98kupd.com, bvesely@98kupd.com, bbogen@98kupd.comSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Greg Donaldson, senior vertical market manager, market intelligence, LexisNexis Risk Solutions, discusses evolving auto insurance shopping trends, consumer behavior, affordability pressures and shifting retention dynamics.

The guys are feeling pretty hopeless regarding a potential Dylan Larkin trade.

onight the wheels fall off reality on Nonsensical Nonsense Unhinged conversations, chaotic energy, questionable decisions, and zero adult supervision. Pull up a chair and embrace the insanty with The Nonsensical NetworkFOLLOW US EVERYWHERE bio.link/nonsensicalnetworkSUPPORT THE SHOWS CASHAPP $glickglick13

These are all the appearances Matteo Pascale made on The Ryan Show FM, compiled in chronological order. It is a weekly radio program hosted by radio broadcaster Ryan Verneville along with Mr. Cheeks of the iconic hip-hop group Lost Boyz and Hamptons Dave.The full unabridged version is available on www.crooklyncomedy.comThis slightly Abridged Version had the following music samples as listed: CUT OUT:C.R.E.A.M. - El Michels AffairEl Michels Affair - C.R.E.A.M - El Michels AffairVoodoo Child (Slight Return) - Jimi HendrixForest Green - Odd FutureForest Green (feat. Mike G) - Odd Future

Slightly delayed, but we're back with our final takes on this year's Eurovision Song Contest! Tune in to find out what we think of Bulgaria's win and everything else that happened it yet another dramatic year! Thank you to our listeners, new and old, for joining us for another season, and hope to see you … Continue reading Bulgariaranga: A Eurovision 2026 Debrief →

See omnystudio.com/listener for privacy information.

This week on Gamertag Radio! Interview with Stanley Pierre-Louis, CEO of the Entertainment Software Association. Learn how 212 million Americans, from all ages, are gaming weekly, boosting mental sharpness and social bonds. Uncover surprising insights on gaming's impact on mental health, culture, and real world skills. Players continue to break stereotypes for who is a ‘gamer'.• 212.3 million Americans play video games every week, up 3% (7.2 million) compared to 2025.• The gender of players is split fairly equally between men and women, with 53% of men and 46%of women actively playing. Slightly more boys and men play than girls and women in allgenerations except Boomers (ages 62-80) where 52% of Boomer women play games comparedto 47% of men.• Video games are for everyone, not just kids. While more than 80% of Gen Alpha (age 5-13) andGen Z (age 14-29) play video games, the majority of adults are powering up as well: 71% ofMillennials (age 30-45), 56% of Gen X (age 45-61) and 50% of Boomers (age 62-80) say they playweekly. Even 32% of the silent generation (age 81-90) are joining in on the fun.• Adult players are more likely to be employed full-time (39%) or to have children (35%) comparedto the general U.S. population – 34% and 30%, respectively.Parents prefer their kids play video games, and love playing with them, too.• The majority of American parents (75%) actively play video games each week, with most (81%)saying they also game with their children (52% at least weekly).• Nearly half (49%) of parents whose children play video games believe playing games teachesimportant skills to their children, such as problem solving and creative thinking.• Two thirds of parents say they use parental controls with that number jumping to 70% forparents of kids 12 and under.Americans feel overwhelmingly positive about video games.• Most American adults recognize the positive benefits of playing video games, such as thembeing fun (85%), bringing joy (81%), offering stress relief (78%), and providing mental stimulation(79%). Younger players (Gen Z) especially believe that video games offer a great way to bringpeople together (88%) and build relationships (87%).• Most adults agree that playing video games helps develop problem-solving skills (76%) andteamwork/collaboration (67%), as well as adaptability/resilience (58%) and STEAM (53%) andcommunication skills (52%).• Nearly nine-in-ten (89%) players who play a sport both on-screen and in real life say playing thevideo game version of their sport improves their real-world performance.Mobile leads the way, with people playing across genres and platforms.• Playing on a mobile device is the most popular across all age groups (80%), while PC and consolegameplay is more common with Gen Alpha, Gen Z and Millennials.• Puzzle, primarily driven by older players, is the top genre on mobile (66%) and PC (60%) but fallsbehind action (66%), shooter (60%) and arcade (60%) games on console.Americans believe video games offer the most value for their money.• A majority of players (63%) report that video games deliver the most entertainment value fortheir money, compared to video streaming services for music, TV and movies, as well as books,magazines and news articles.• Most Gen Alpha (69%), Gen Z (78%) and Millennial (67%) players have purchased in-gamecontent, typically spending $20 per month (median).• Parents also purchase in-game content for their children (54%). Of those that do, nearly all ofthem (93%) require approval for in-games purchases made by their kids.• More than half (58%) of players downloaded a game for free in the past 12 months, while 43% purchased a game, 35% purchased a game subscription and 19% borrowed a game.The full Essential Facts About the U.S. Video Game Industry report is now available. For more information, visit the ESA's website.Send us questions - fanmail@gamertagradio.com | Speakpipe.com/gamertagradio or 786-273-7GTR. Join our Discord - https://discord.gg/gtr chat with other GTR community member.

Let's Chat!!Boo, bitches…This week's Cauldron of Chaos is dedicated to every witch currently trying to remain mystical while sweating through their eyeliner.We're talking: 

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

AI is everywhere right now, and so is the advice telling you to use it to replace your social media manager entirely. In this episode, Andrea gives her honest, unfiltered take from someone who uses AI every single day inside her agency: what it genuinely does well, where it falls short, no matter how sophisticated your setup, and the one thing AI simply can't replicate, no matter how good your prompts are.IN THIS EPISODE YOU WILL LEARN→ What AI is actually useful for inside a social media agency and where it has to hand back to a human→ Why AI plus a non-marketer is not the solution you think it is→ The real reason so much content looks the same right now and what your audience is craving instead→ Why AI will replace some social media managers and exactly which ones are safe→ What experienced strategic thinking gives your content that no AI tool can replicateLINKS MENTIONEDBook a content shoot (Illawarra businesses, June only): https://r0zov660ttj.typeform.com/to/khP778b4 Follow Andrea on Instagram: https://www.instagram.com/andreamareecreativeENJOYED THIS EPISODE?If this episode made something click for you, take a screenshot and share it on your Instagram stories. Tag @andreamareecreative so I can celebrate you.If you haven't already, follow the show so you never miss an episode. And if you've been listening for a while, leaving a rating and review takes two minutes and helps Instagram for Bosses reach more business owners just like you.ABOUT INSTAGRAM FOR BOSSESI'm Andrea, founder of Andrea Maree Creative, and my mission is to help established service-based business owners turn Instagram into a profitable enquiry channel. Instagram for Bosses is a globally top 2.5% podcast dedicated to simplifying Instagram marketing so you can consistently attract ready-to-invest clients without posting every day or living on your phone.

MRKT Matrix - Wednesday, May 27th Dow rises 200 points to record as oil declines, but a pause in the chip rally weighs on the S&P 500 (CNBC) Goldman raises its S&P 500 year-end forecast. It's for one simple reason (CNBC) Bank of America says prepare for a ‘summer correction' after rally to record highs (CNBC) Americans Are About to Pay Even More at the Grocery Store (Bloomberg) Mortgage refinance demand drops 18% as rates hit highest level since August (CNBC) JPMorgan, BofA CEOs Predict Another Round of Trading Windfalls (Bloomberg) Robinhood Lets Customers Use AI to Trade Stocks, Make Credit-Card Purchases (WSJ) Ford's Stock Is Surging—and It's Got Nothing to Do With Its Car Business (WSJ) China Wants Its Companies to Embrace AI—Without Firing Workers (WSJ) --- Subscribe to our newsletter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://riskreversal.substack.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ MRKT Matrix by RiskReversal Media is a daily AI powered podcast bringing you the top stories moving financial markets Story curation by RiskReversal, scripts by Perplexity Pro, voice by ElevenLabs

See omnystudio.com/listener for privacy information.

The Minnesota Court of Appeals won't reinstate a law to ban certain gun trigger mechanisms. And gas prices were down slightly today after hitting a four-year Memorial Day high yesterday.Those stories and more in today's evening update from MPR News. Hosted by Emily Reese. Music by Gary Meister.

Comedy: Gulf Screen Guild Theater “Ballerina, Slightly with Accent” 3/10/40 CBS, Favorite Story “The Man Who Married a Dumb Wife” 4/17/48 Syndicated.

become a member and get early access to videos, exclusive content, and a closer connection to the work

In this episode, I talk about offering a prompt, but I completely forgot to share.Here's a prompt I asked Listing Engine to create for a landing page.Prompt:[Location] is ...insert your city.You are a world-class direct response landing page designer, conversion copywriter, and Go High Level AI Studio website builder.Create a simple, clean, mobile-first landing page designed to generate property appraisal leads from homeowners in [Location].The purpose of the page is to invite homeowners to submit their details so they can receive a fully researched, accurate property market update for their own property within 24 hours.The page should feel professional, local, trustworthy, premium, and helpful.DESIGN STYLEUse a modern real estate lead generation style.The page should be:- Mobile-first- Clean- Premium- Uncluttered- Easy to read- Focused on one clear actionUse a dark charcoal background with white text.Use bold, tightly spaced Inter font throughout the page.Use strong contrast with an electric blue accent colour for buttons, icons, highlights, borders, glow effects, and key visual details.On desktop, use a simple two-column hero layout:- Left column: hero copy- Right column: 24-hour clock graphic and opt-in formKeep the text column and opt-in form visually close together so the page feels focused and conversion-driven.On mobile, stack the hero copy first, then the clock graphic, then the opt-in form.Do not add unnecessary navigation links, menus, extra buttons, or distracting sections.TOP BANNERAt the very top of the page, add this centred context line:HOW MUCH IS YOUR [Location] PROPERTY WORTH TODAY?Make this line bold, clean, and highly visible, but not larger than the main hero heading.HERO SECTION — LEFT SIDEHero Heading:Our Free 24 Hour Update Delivers A Researched and Accurate Property Market Opinion.Subheading:Find out what your property could be worth in today's market with a personalised market opinion prepared specifically for your [Location] home.Supporting Copy:No generic estimate. No automated guesswork. Just a researched property market update based on recent local sales, current buyer activity, comparable properties, and today's market conditions.Add these 5 bullet points with check icons:- Receive your personalised property market opinion within 24 hours- Based on current [Location] market data- Includes recent comparable sales and local buyer demand- Helpful whether you're thinking of selling now, later, or simply curious- Free, accurate, and obligation-freeBelow the bullet points, add a small trust line with a shield icon:Prepared by a local property professional with current market knowledgeHERO SECTION — RIGHT SIDEAt the top of the right column, above the opt-in box, create a large, prominent round 24-hour clock-style graphic.The clock graphic should look sleek, modern, and premium.It should include:- Circular timer ring- Subtle electric blue glow- “24 HR” displayed clearly inside the graphic- Clean, minimal real estate styleBelow the clock graphic, create a clean opt-in box/card.The opt-in box should have:- Slightly lighter charcoal background- Rounded corners- Subtle shadow- Subtle electric blue top gradient line- Strong visual focusOpt-in Box Heading:Get Your Free 24 Hour Market OpinionOpt-in Box Subheading:Enter your details below and we'll prepare a researched property update for your home.Form Fields:- First Name- Address of Property to be Assessed- Email- MobileAdd a tick box with this exact wording:I'm planning to sell. Please send me your marketing options and costs.CTA Button:Get My 24 Hr Market OpinionButton style:- Large- Full width- Rounded corners- Bold text- Bright electric blue background- High contrast- Strong hover effect if possibleBelow the CTA button, add this privacy microcopy:Your details are private and will only be used to prepare your property market update.HOW IT WORKS SECTIONBelow the hero section, add a simple “How It Works” section.Keep this section clean, short, and visually simple.Heading:How It WorksAdd 3 steps with simple icons:Step 1: Submit Your Property DetailsStep 2: We Research The Local MarketStep 3: Receive Your 24 Hour Market OpinionCLOSING CTA SECTIONAdd a final simple closing CTA section.TextWant to know what your [Location] property could sell for in today's market?Button:Get My 24 Hr Market OpinionIMPORTANT INSTRUCTIONS- Keep the page focused on one action only.- Do not add unnecessary navigation links.- Do not make the page busy.- Prioritise mobile readability.- Make the opt-in form the main visual focus.- Use strong spacing, bold headings, and clean sections.- Keep the design premium, local, trustworthy, and conversion-focused.- Make sure the page is suitable for real estate agents generating homeowner appraisal leads.

Our stories tonight feature a fan favorite character who has been known to get up to some gentle floral-related trouble. We'll come along for a lilac heist in the countryside, then spend some time restoring an old house, and finally visiting the farmer's market for a bit of community service. Subscribe to our ⁠Premium channel.⁠ The first month is on us

Our stories tonight carry us into the bright days of Spring, with stories about time spent in gardens and neighborhood streets, enjoyable chores and small adventures, seeds and shovels, and the joy of growing sunlight. Subscribe to our ⁠Premium channel.⁠ The first month is on us. 

Listen to the full 48 minute Between Friends episode. Go Directly to this Patreon Episode "What We Really Think About Celebrities (Unfiltered and Slightly Brutal)" https://www.patreon.com/posts/what-we-really-155331513   Picture this: a simple game of "say the first thing that comes to mind" between Chalene and Bret… and it completely goes off the rails. What starts as harmless celebrity opinions quickly turns into brutally honest takes and the kind of unfiltered commentary that probably shouldn't be said out loud. It's messy, funny, and exactly the kind of thing you get on Patreon that you probably weren't supposed to hear.   This story is part of The Saturday Spill series a little peek into the wild, unfiltered stuff that usually stays on Patreon. Some weeks it's hilarious, some weeks it's jaw-dropping, but it's always real life that doesn't quite fit on the regular show. If you're into a little chaos and behind-the-scenes tea, you're in the right place. If you love it, amazing…you can listen to the full, unedited version here http://Chalene.com/more