POPULARITY
Categories
What happens when AI stops talking and starts working, and who really owns the value it creates? In this episode of Tech Talks Daily, I'm joined by Sina Yamani, founder and CEO of Action Model, for a conversation that cuts straight to one of the biggest questions hanging over the future of artificial intelligence. As AI systems learn to see screens, click buttons, and complete tasks the way humans do, power and wealth are concentrating fast. Sina argues that this shift is happening far quicker than most people realize, and that the current ownership model leaves everyday users with little say and even less upside. Sina shares the thinking behind Action Model, a community-owned approach to autonomous AI that challenges the idea that automation must sit in the hands of a few giant firms. We unpack the concept of Large Action Models, AI systems trained to perform real online workflows rather than generate text, and why this next phase of AI demands a very different kind of training data. Instead of scraping the internet in the background, Action Model invites users to contribute actively, rewarding them for helping train systems that can navigate software, dashboards, and tools just as a human worker would. We also explore ActionFi, the platform's outcome-based reward layer, and why Sina believes attention-based incentives have quietly broken trust across Web3. Rather than paying for likes or impressions, ActionFi focuses on verifying real actions across the open web, even when no APIs or integrations exist. That raises obvious questions around security and privacy. This conversation does not shy away from the uncomfortable parts. We talk openly about job displacement, the economic reality facing businesses, and why automation is unlikely to slow down. Sina argues that resisting change is futile, but shaping who benefits from it remains possible. He also reflects on lessons from his earlier fintech exit and how movements grow when people feel they are pushing back against an unfair system. By the end of the episode, we look ahead to a future where much of today's computer-based work disappears and ask what success and failure might look like for a community-owned AI model operating at scale. If AI is going to run more of the internet on our behalf, should the people training it have a stake in what it becomes, and would you trust an AI ecosystem owned by its users rather than a handful of billionaires? Useful Links Connect with Sina Yamani on LinkedIn or X Learn more about the Action Model Follow on X Learn more about the Action Model browser extension Check out the whitelabel integration docs Join their Waitlist Join their Discord community Thanks to our sponsors, Alcor, for supporting the show.
Principal Security Consultant and community favorite Jake Hildreth returns to The PowerShell Podcast to talk about building smarter automation, leveling up through community, and creating tools that solve real problems. Andrew shares his “stop trying so hard” theme for the year, how working smarter applies directly to scripting and security, and why getting involved with others is one of the fastest ways to grow in your career. The conversation dives into Jake's recent projects including Deck, a Markdown-to-terminal presentation tool built on Spectre.Console, and Stepper, a resumable scripting framework designed for long-running workflows that can't be fully automated end-to-end. They also explore presentation skills, avoiding “death by PowerPoint,” and why security work requires constantly re-checking assumptions as threats evolve. Key Takeaways: • Work smarter, not harder — Whether you're scripting or building a career, small sustainable improvements beat grinding yourself into a corner. • Resumable automation is a game changer — Stepper helps scripts safely pause and resume, making real-world workflows more reliable when humans or flaky APIs are part of the loop. • Community turns into real momentum — Contributing, asking questions, and sharing feedback builds skills, friendships, and opportunities faster than trying to learn alone. Guest Bio: Jake Hildreth is a Principal Security Consultant at Semperis, Microsoft MVP, and longtime builder of tools that make identity security suck a little less. With nearly 25 years in IT (and the battle scars to prove it), he specializes in helping orgs secure Active Directory and survive the baroque disaster that is Active Directory Certificate Services. He's the creator of Locksmith, Stepper, Deck, BlueTuxedo, and PowerPUG!, open-source tools built to make life easier for overworked identity admins. When he's not untangling Kerberos or wrangling DNS, he's usually hanging out with his favorite people and most grounding reality check: his wife and daughter. Resource Links: • Jake Hildreth's Website – https://jakehildreth.com • Jake's GitHub - https://github.com/jakehildreth Andrew's Links - https://andrewpla.tech/links • PowerShell Spectre Console – https://pwshspectreconsole.com/ • PDQ Discord – https://discord.gg/PDQ • PowerShell Conference Europe – https://psconf.eu • PowerShell + DevOps Global Summit – https://powershellsummit.org • Jake's PowerShell Wednesday – https://www.youtube.com/watch?v=YdV6Qecn9v0 The PowerShell Podcast on YouTube: https://youtu.be/rFeoTKLerkA
It's an annual tradition, the AVNation "Best of" Awards, and Chi Hang Lo is up for AV Professional of the Year, along with UCLA's Classroom Modernization Pilot, and HETMA for Best Technical Support! Take a listen as Joe Way sits down with Chi to discuss this honor and why you should #VoteForChi.Joe Way drops a special Friday episode to spotlight the AV Nation Awards (Readers' Choice “Best of 2025”) and rally the higher ed community around three finalists: Chi Hang Lo for AV Professional of the Year, UCLA's Classroom Modernization Pilot for Project of the Year, and HETMA for Best Technical Support. Chi joins to share what the nomination represents, why the UCLA pilot is different, and how the higher ed community lifts each other up through collaboration, shared evaluation, and real-world support. The episode closes with a clear call: go vote, support the people and projects pushing the industry forward, and keep building a better future together.Vote now: https://www.avnation.tv/avnation-best-of-2025-awards/Featured GuestChi Hang Lo — Manager, AV/IT Solutions (UCLA)Leads a team designing and delivering scalable AV + IT solutions that support UCLA's learning environments and broader smart campus vision.What You'll Hear in This Episode1) Why this episode, and why nowA bonus Friday release to interrupt the usual schedule and highlight the AV Nation Awards as a uniquely people-driven recognition.Joe frames Readers' Choice as a rare moment for the industry to advocate for the people, projects, and platforms that matter most to the community.2) The three higher ed finalistsChi Hang Lo — AV Professional of the Year finalistUCLA — Project of the Year finalist for the Classroom Modernization PilotHETMA — Technical Support finalistJoe emphasizes how significant it is to see higher ed represented across multiple major categories in the finals.3) The UCLA Classroom Modernization Pilot: what makes it specialChi explains why the pilot stands out as more than a refresh—it's a different way of thinking:Moving from traditional room-by-room AV to a cloud-first, scalable control approach designed for enterprise scale (think: up to 1,000 spaces).Leveraging web technologies, REST APIs, and integrations to enable flexibility, interoperability, and future growth.Building for adaptability so the system isn't locked to one manufacturer ecosystem—prioritizing integration-first design and long-term scalability.Aiming toward a platform approach: “AV as a platform” that can support more than AV control.4) The “why” behind going cloud-firstJoe asks the question everyone asks: why not just keep doing “simple” AV? Chi's answer points to:Preparing the team—and the campus—for the future skill sets needed in modern learning environments.Meeting expanding demands: conferencing, capture, collaboration, active learning, and rapid shifts in pedagogy.Treating AV as part of a broader AV/IT solutions ecosystem, not a standalone technical island.5) Smart campus, not just AVThe conversation expands into the broader vision:AV systems already contain meaningful data (occupancy, environmental signals, usage patterns)—the opportunity is connecting it to the rest of campus.Collaboration across departments (facilities, security, events, transportation, IT, and more) becomes possible when you build a platform that can integrate.Chi shares work toward data aggregation and dashboards, including collaboration with a Data Lake approach to create better operational insight and decision-making.6) The team behind the pilotChi introduces the core members of his team and their contributions:Project coordination and process leadership (including agile/scrum-style development support)Technical design and 2D/3D modeling workflows, standards-based design language for facilities alignmentSoftware/automation engineering, signal distribution/recording, and architecture to connect devices to the cloudPartnerships with manufacturers to improve firmware/APIs and enable deeper integration at scaleJoe underscores how innovation required close collaboration between UCLA, solution providers, and manufacturers—engineering alongside engineering.7) Career growth: from technical expert to leaderJoe shifts the conversation to professional development: what changes when you move from “doing” to “leading.”Chi shares leadership themes that have guided him:Staying humble, collaborative, and relationship-drivenBalancing strong technical conviction with empathy and communicationCreating opportunities for the next generation by helping people navigate common roadblocks (communication, attitude, relationship dynamics)Treating the industry like a community—because you'll keep working with the same people for years8) The HETMA community impactChi shares how community support—especially collaborative technology evaluation and shared learning—helps smaller institutions gain access, influence, and manufacturer attention they might not get alone. Joe reinforces the higher ed ethos: we're collaborators, not competitors.Memorable Moments / Quotes (paraphrased)The awards matter because the people choose—it's advocacy, not just adjudication.The pilot isn't just “AV”—it's building infrastructure for a smart campus platform.The real work is turning AV data into insight and integration that improves the campus experience.Calls to ActionVote for Chi Hang Lo — AV Professional of the YearVote for UCLA's Classroom Modernization Pilot — Project of the YearVote for HETMA — Technical SupportAnd vote for the products, people, and projects you believe represent the best of 2025.Vote now: https://www.avnation.tv/avnation-best-of-2025-awards/Connect with Chi Hang Lo: https://www.linkedin.com/in/chihanglo/
Mews just raised $300 million in a Series D, valuing the company at $2.5 billion — one of the largest hotel tech raises ever. But this conversation isn't about hype. In this GMH exclusive, Wil Slickers sits down for a third time with Richard Valtr, Founder of Mews, to unpack what this funding actually unlocks and why Richard believes much of hospitality technology has been built on the wrong assumptions for decades. They dig into why hotels still struggle with data ownership, how PMS platforms became gatekeepers instead of enablers, and why AI will only work if the industry fixes its foundations first. Richard also explains why RevPAR may be the industry's “original sin,” why guest experience should be a measurable output, and why fully autonomous hotels are the wrong goal. This is a wide-ranging, philosophical, and practical conversation about: • What Mews' $300M raise really changes • Why hotel tech copied the wrong SaaS playbook • Data standards, open APIs, and industry gatekeeping • AI agents, automation, and what should (and shouldn't) be automated • Why hospitality is more human than ever, even in an AI world Extra Links Related or Mentioned in This Episode: My first episode with Richard in 2021 My second episode with Richard in 2023 Skift Article around the $300M fund raise Connect with Airline Weekly LinkedIn: https://www.linkedin.com/company/airline-weekly/ X: https://x.com/Airline_Weekly/ Facebook: https://www.facebook.com/airlineweekly/ Instagram: https://www.instagram.com/skiftnews/ WhatsApp: https://whatsapp.com/channel/0029VaAL375LikgIXmNPYQ0L/ Subscribe to @SkiftNews and never miss an update from the airline and travel industries.
Read the Enterprise 2030 study → https://www.ibm.com/thought-leadership/institute-business-value/en-us/report/enterprise-2030 Is Claude Code having its ChatGPT moment? This week on Mixture of Experts, host Tim Hwang is joined by Chris Hay, Gabe Goodhart and Francesco Brenna to unpack the shifts happening in AI as 2026 kicks off. First, OpenAI confirms ads are coming to ChatGPT, raising questions about trust, economics and the future of AI product models. Next, Claude Code is exploding in popularity! Developers are discovering what agentic coding can really do, and it's transforming how software gets built. Then, we analyze a new report from IBM's Institute for Business Value— “The enterprise in 2030”, which reveals how executives are planning to shift from AI-driven efficiency to AI-powered innovation. Finally, Hugging Face launches Open Responses, a new standard for agent APIs that could reshape AI development while raising questions about transparency and control. All that and more on this week's Mixture of Experts to learn more. 00:00 – Introduction 01:30 – OpenAI brings ads to ChatGPT 12:25 – Claude Code's breakout moment 22:57 – IBV's Enterprise 2030 report 36:09 – Open Responses: The future of agent APIs The opinions expressed in this podcast are solely those of the participants and do not necessarily reflect the views of IBM or any other organization or entity. Explore IBM Enterprise Advantage Visit Mixture of Experts podcast page to get more AI content
Performance marketers struggle with direct mail attribution and speed. Ryan Ferrier is CEO of Lob, the direct mail automation platform serving over 12,000 businesses with API-driven personalized campaigns. The discussion covers AI-powered delivery optimization that automatically selects standard vs. first-class postage based on speed requirements, real-time address verification APIs that prevent undeliverable mail and save millions in wasted sends, and QR code attribution systems with personalized URLs achieving 5% average conversion rates and up to 30% for compliance-ready campaigns.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Como a inteligência artificial pode ajudar a identificar COMPORTAMENTOS em VÍDEO? No episódio 19 do Hipsters.Talks, PAULO SILVEIRA , CVO do Grupo Alura, conversa com RUBENS RODRIGUES , CTO da School Guardian sobre VISÃO COMPUTACIONAL, detecção de objetos com YOLO e PYTHON e como treinar MODELOS DE IA PARA IDENTIFICAR COMPORTAMENTOS específicos em vídeos. Descubra a diferença entre usar bibliotecas prontas e treinar seus próprios modelos, APIs de cloud vs processamento local e o futuro dos desenvolvedores na era da IA! Sinta-se à vontade para compartilhar suas perguntas e comentários. Vamos adorar conversar com você!
Revenue Generator Podcast: Sales + Marketing + Product + Customer Success = Revenue Growth
Performance marketers struggle with direct mail attribution and speed. Ryan Ferrier is CEO of Lob, the direct mail automation platform serving over 12,000 businesses with API-driven personalized campaigns. The discussion covers AI-powered delivery optimization that automatically selects standard vs. first-class postage based on speed requirements, real-time address verification APIs that prevent undeliverable mail and save millions in wasted sends, and QR code attribution systems with personalized URLs achieving 5% average conversion rates and up to 30% for compliance-ready campaigns.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
In this episode of In-Ear Insights, the Trust Insights podcast, Katie and Chris discuss the practical application of AI agents to automate mundane marketing tasks. You will define what an AI agent is and discover how this technology performs complex, multi-step marketing operations. You will learn a simple process for creating knowledge blocks and structured recipes that guide your agents to perform repetitive work. You will identify which tools, like your content scheduler or website platform, are necessary for successful, end-to-end automation. You will understand crucial data privacy measures and essential guardrails to protect your sensitive company information when deploying new automated systems. Tune in now to see how you can permanently eliminate hours of boring work from your weekly schedule! Watch the video here: Can’t see anything? Watch it on YouTube here. Listen to the audio here: https://traffic.libsyn.com/inearinsights/tipodcast-agentic-ai-practical-applications-claude-cowork.mp3 Download the MP3 audio here. Need help with your company’s data and analytics? Let us know! Join our free Slack group for marketers interested in analytics! [podcastsponsor] Machine-Generated Transcript What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode. Christopher S. Penn: In this week’s In Ear Insights, one of the things that people have said, me especially, is that 2026 is the year of the agent. The way I define an agent is it’s like a real estate agent or a travel agent or a tax agent. It’s something that just goes and does, then comes back to you and says, “Hey, boss, I’m done.” Katie, you and I were talking before the show about there’s a bunch of mundane tasks, like, let’s write some evergreen social posts, let’s get some images together, let’s update a landing page. Let me ask you this: when you look at those tasks, do they feel repetitive to you? Katie Robbert: Oh, 100%. I’ve automated a little bit of it. And by that, what I mean is I have the background information about Trust Insights. I have the tone and brand guidelines for Trust Insights. So if I didn’t have those things, those would probably be the biggest lift. And so all I’m doing is taking all of the known information and saying, okay, let’s create some content—social posts, landing pages—out of all of the requirements that I’ve already gathered, and I’m just reusing over and over again. So it’s completely repetitive. I just don’t have that more automated repeatability where I can just push a button and say, “Go.” I still have to do the work of loading everything up into a single system, going through it piece by piece. What do I want? Am I looking at the newsletter? Am I looking at the live stream? Am I looking at this podcast? So there’s still a lot of manual that I know could be automated, and quite frankly, it’s not the best use of my time. But it’s got to get done. Christopher S. Penn: And so my question to you is, what would it look like? We’ll leave the technology aside for the moment, but what would it look like to automate that? Would that be something where you would say, “Hey, I want to log into something, push a button, and have it spit out some stuff. I approve it, and then it just…” Katie Robbert: Goes, yeah, that would be amazing. I would love to, let’s say on a Monday morning, because I’m always online early. I would love to, when I get up and I’m going through everything in the background, have something running, and I can just say, “Hey, I want two evergreen posts per asset that I can schedule for this week.” You already have all of the information. Let’s go ahead and just draft those so I can take a look. Having that stuff ready to go would be so helpful versus me having to figure out where does. It’s not all in one place right now. So that’s part of the manual process is getting the Trust Insights knowledge block, finding the right gem that has the Trust Insights tone, giving the background information on the newsletter and the background information on the podcast and so on so forth, making sure that data is up to date. As I was working through it this morning and drafting the post and the landing pages, the numbers of subscribers were wrong. That’s an easy fix, but it’s something that somebody has to know. And that’s the critical thinking part in order to update it appropriately. Those kinds of things, it all exists. It’s just a matter of getting into one place. And so when I think about automation, there’s so much within our business that gets neglected because of these—I’m not going to call them barriers—it’s just bandwidth that if I had a more automated way, I feel like I would be able to do that much more. Christopher S. Penn: So let’s think about this. There’s obviously a lot of systems, Claude Code, for example, and QWEN Code and stuff, the big heavy coding systems. But could you put all those requirements, all those basics into a folder on your desktop? Katie Robbert: Oh, absolutely. Christopher S. Penn: Okay. And if you had some help from a machine to say, “Hey, looks like you’re using our social media scheduling software, AgoraPulse. AgoraPulse has an API?” Katie Robbert: Yep. Christopher S. Penn: Would you feel comfortable saying to a machine, “AgoraPulse has an API. Here’s the URL for it. I ain’t going to read the documentation. You’re going to read the documentation and you’re going to come up with a way to talk to it.” Would you then feel comfortable just logging into, say, Claude Cowork, which came out recently and is iterating rapidly? It is becoming Claude Code for non-technical people. Katie Robbert: Yep. Christopher S. Penn: And Monday morning, say, “Hey, Claude, good morning, it’s Monday. You know what to do.” Invoke the Monday morning skill. It goes and it reads all the stuff in those folders because you’ve written out a recipe, a process, and then it says, “Here’s this week’s social posts. What do you think?” And you say, “That looks good.” And by the way, all of the images and stuff are already stored in the folders so you don’t need to go and download them every single time. This is great. “I will go push those to the AgoraPulse system.” Would that be something that you would feel comfortable using that would not involve writing Python code after the first setup? Katie Robbert: Oh, 100%. Because what I’m talking about is when we talk about evergreen content—and I’m not a social media manager, but we’re a small company and we all kind of do everything—this is content that’s not timely. It’s not to a specific. It only works for this quarter or it only works for this specific topic. Our newsletter is evergreen in the sense that we always want people subscribing to it. We always want people to go to TrustInsights.ai/Newsletter and get the newsletter every Wednesday. The topic within the newsletter changes. But posting about the fact that it’s available for people to subscribe to is the evergreen part. The same is true of the podcast, we want people to go to TrustInsights.ai/TIpodcast, or we want people to join us on our live stream every Thursday at 1:00 PM Eastern, and they can go to TrustInsights.ai/YouTube. What changes is the topic that we go through each week, but the assets themselves are available either live or on demand at those URLs at all times. I just wanted to give that clarification in case I was dating myself and people don’t still use the term evergreen content. Christopher S. Penn: Well, that makes total sense. I mean, those are the places that we want people to go. What I’m thinking about, and maybe this is something for a live stream at some point, is now that we have agentic frameworks for non-technical people, it might be worth trying to wire that up. If we think about it, of course, we’re going to use the 5Ps. What is the purpose? The purpose is to save you time and to have more things automated that really should be automated. And obviously, the performance measure of it is stop doing that thing. It’s 2 seconds on a Monday morning, or maybe 2 seconds on the first of the month. Because an agentic framework can crank out as much stuff as you have capacity for. If you buy the Claude Max plan, you can basically create 2 years worth of content all in one shot. And so it becomes People, Process, Platform. So you’re the people. The process is writing down what you want the agent to do, knowing that it can code, knowing that it can find stuff in your inbox, in your folder that you put on your desktop, knowing that it can reference knowledge blocks. And you could even turn those into skills to say, “Trust Insights Brand Voice is now a skill.” You’ll just use that skill when you’re writing. And the platform is obviously a system, like Cowork. And given how fast it’s been adopted and how many people are using it, every provider is going to have a version of this in the next quarter. They’d be stupid if they didn’t. That’s how I think you would approach this problem. But I think this is a solvable problem today, without buying anything new—because you’re already paying for it. Without creating anything new, because we’ve already got the brand voice, the style guide, the assets, the images. What would be the barrier other than free time to making this happen? Katie Robbert: I think that’s really it. It’s the free time to not only set it up, but also to do a couple of rounds of QA—quality assurance. Because, as I’ve been using the Trust Insights Brand Voice gem this morning, I’m already looking at places where I could improve upon it, places where I could inject a little more personality into it, but that takes more time, that’s more maintenance, and that just makes my list longer. And so for me, it really is time. Are the knowledge blocks where I want them to be? Do I need to? This is my own personal process. And this is why I get inundated in the weeds: I start using these tools, I see where there could be improvements or there needs to be updates. So I stop what I’m doing and I start to walk backwards and start to update all of the other things, which just becomes this monster that builds on itself. And my to-do list has suddenly gotten exponentially larger. I do feel like, again, there’s probably ways to automate that. For example, send out a skill that says, “Hey, here’s the latest information on what Trust Insights does. Update all the places that exist.” That’s a very broad stroke, but that’s the kind of stuff that if I had more automation, more support to do that, I could get myself out of the weeds. Because right now, to be completely honest, if I’m not doing it, that stuff’s not getting done. So nobody else is saying, our ideal customer profile should probably be updated for 2026. We all know it needs to be done, but guess who’s doing it? This guy with whatever limited time I have, I’m trying to carve out time to do that maintenance. And so it is 100% something I would feel comfortable handing off to automation with the caveat that I could still oversee it and make sure that things are coming out correctly so it doesn’t just black box itself and be like, “Okay, I did these 20 steps that you can no longer see, and it’s done.” And I’m like, “Well, where did it go wrong?” That’s the human intervention part that I want to make sure we don’t lose. Christopher S. Penn: Exactly. The number 1 question that people need to ask for any of these agentic tools for figuring out, “Can I do this?” is really simple: Is there an API? If there is an API, a machine can talk to a machine, which means AgoraPulse, our social media scheduling software, has an API. Our WordPress website—our WordPress itself has an API. Gravity Forms, the form management system that we have, has an API, YouTube has an API, etc. For example, in what you were just talking about, if you set up your API key in WordPress and gave it to Claude in Cowork and said, “Hey, Claude, you’re going to need to talk to my website. Here’s my API key. You write the code to talk to the website, but I want you to use your Explore agents to search the Trust Insights website for references to—I will call it dark data. Make me a list, make me a spreadsheet of all the references to dark data on a website, with column 1 being the URL and column 2 being the paragraph of text.” Then you could look at it and go, “Hey, Claude, every time we’ve said dark data prior to 2023, we meant something different. Go.” And using the WordPress API, change those posts or change those pages. This is the—I hate this term because it’s such a tech bro term, but it actually works. That is the unlock for a web, for any system: to say, is there an API that I can literally open up a system? And then as long as you trust your knowledge blocks, as long as you trust your recipe, your process, the system can go and do that very manual work. Katie Robbert: That would be amazing because you know a little bit more about my process. This morning, I was on those two systems. I was on our WordPress site, and I was on our YouTube channel. As I was drafting posts for our podcast, I went to our YouTube channel and took a screenshot of our playlist to get the topics that we’ve covered so that I could use those to update the knowledge block about the podcast, which I realized was outdated and still very focused on things like Google Analytics 4. It wasn’t really thinking about the topics we’ve been talking about in the past 6 to 12 months. I did that, and I also gave it the content from the landing page from our website about the podcast, realizing that was super out of date, but it gave enough information of, “And here’s all the places where the podcast lives that you can access it.” It was all valuable information, but it was in a few different places that I first had to bring together. And you’re saying there’s APIs for these things so that I don’t have to sit here with every other screenshot of Snagit crashing, pulling out my hair and going, “I just want to write some evergreen posts so that more people subscribe?” Christopher S. Penn: That’s exactly what I’m saying. Katie Robbert: Oh, my goodness. Christopher S. Penn: And I would say, now that I think about this, what you’re describing, you wouldn’t even need to use the API for that. Katie Robbert: Great. Christopher S. Penn: Because a lot of today’s agentic tools have the ability to say, “I can just go search the web. I can go look at your YouTube channel and see what’s on it.” And it can just browse. It will literally fire up a browser. So you can say, “I want you to go browse our YouTube channel for the last 6 months. Or, here’s the link to our podcast on Libsyn. I want you to go browse the last 25 episodes. And here’s the knowledge block in my folder on my desktop. Update it based on what you browse and call it version 2 so that we don’t overwrite the original one.” Katie Robbert: Oh, my goodness. Christopher S. Penn: Yeah, that. So this is the thing that again, when we think about AI agents and agentic AI, this is where there’s so much value. Everyone’s focused on, “I’m going to make the biggest flashes.” No. You can do the boring crap with it and save yourself so much sanity, but you have to know where to get started. And the system today that I would recommend to people as of January 2026 is Claude Cowork. Because you already installed Claude on your desktop, you tell it which folder it can work in so it’s not randomly wandering all over your computer and say, “Do these things.” And it’s no different than building an SOP. It’s just building an SOP for the junior most person on your team. Katie Robbert: Well, good news, that is my bailiwick: SOPs and process. And so, shocker, I tend to do things the exact same way every single time. That part of it: great, it needs a process done. It’s going to take me 2 seconds to write out exactly what I’m doing, how I want it done. That’s the part that I have nailed. The question I have for you, because I’ll bet this question is going up from a lot of people, is what kind of data privacy do we need to be thinking about? Because it sounds like we’re installing this third-party application on our work machines, on our laptops, and many of us keep sensitive information on our laptops—not in the cloud, not in Google Drive or SharePoint, wherever people have that shared information. Obviously, we’re saying you can only look at these things, but what is it? What do we need to be aware of? Is there a chance that these third-party systems could go rogue and be like, “Effort? I’m going to go look at everything. I’m going to look at your financials, I’m going to get your social. That photo that you have of your driver’s license that you have to upload every 3 months to keep your insurance? I’m going to grab that too.” What kind of things do we need to be aware of, and how do we protect ourselves? Christopher S. Penn: It comes down to permissions. The Anthropic’s app—I should be very clear about this—Anthropic’s app is very good about respecting permissions. It will work within the folder you tell it and it will ask you if it needs to reference a different folder: “Can I look at this folder?” It does not do it on its own. Claude Code. There is a special mode called Live Dangerously which basically says, “Claude, you can do whatever you want on my system.” It is not on by default. It cannot be turned on by default. You have to invoke it specifically. QWEN’s version is called YOLO. Cowork doesn’t even have that capability because they recognize just how stupidly dangerous that is. If you are working on very sensitive data, obviously the recommendation there would be to use it in a different profile on your computer. If your Windows machine or your Mac can have different profiles, you might have an AI only profile that will have completely different directories. You won’t even be able to see your main user’s. And then if you’re really, really concerned about privacy, then I would not use a cloud-based provider at all. I would use a system like QWEN Code, which does not have telemetry to relay back to anybody what you’re doing other than actions you take, like you turned it on, you turned it off, etc. And you can download QWEN Code source and modify it to turn all the telemetry off if you want to, or just delete it out of the code base and then use a local model that has no connection to the Internet if you’re working on the most sensitive data. Katie Robbert: Got it. I think that’s incredibly helpful because you and I, we’re very aware of data privacy and what sensitive data and protected data entails. But when I think about the average marketer—and it’s not to say that they don’t care, they do care—but it’s not top of mind because they’re just underwater trying to find any life raft to get out of the weeds and be like, “Okay, great, this is a great solution, I’m going to go ahead and stand it up.” And data privacy tends to be an afterthought after these systems have already accessed all of your stuff. Again, it’s not that people using them don’t care, it’s just not something that they’re thinking about because we make big assumptions that these tech companies are building things to only do what they’re saying they do. And we’ve been around long enough to know that they’re trying to get all. Christopher S. Penn: Our data exactly. The where the biggest leak for the casual user is going to be is in the web search capabilities. Because we’ve done demos on our live streams and things in the past of watching the tools do web search. If you do not provide it a secure form of web search, it will just use regular web search, and then all that stuff can be tracked back to your IP, etc. So there are ways to protect against that, and that’s a topic for another time. Katie Robbert: All right, go ahead. Christopher S. Penn: I think the next steps we should be doing is let’s get Claude Cowork set up maybe on a live stream and get the knowledge blocks without them being updated and say, “Let’s do this as a first test. Let’s try to update these knowledge blocks using web search tools and see what Claude Cowork can do for you.” Katie Robbert: I was going to suggest the exact same thing because if you’re not aware, every week, every Thursday at 1:00 PM Eastern, we have our live stream, which you can catch at TrustInsights.ai/YouTube. And we walk through these very practical things, very much a how-to. And so I love the idea of using our live stream to set up Claude Cowork. Is that what it’s called? Christopher S. Penn: That’s what it’s called, yes. Katie Robbert: Because I feel like it’s easy for you and I to talk about theoretically, “Here’s all the stuff you should do,” but people are craving the, “Can you just show me?” And that’s what we can do on the live stream, which is what I was trying to write for social posts, full circle. “Here’s the podcast, it introduces the idea. Here’s the live stream, it’s the how-to. Here’s the newsletter. It’s the big overarching theme.” I was trying to write social posts to do all of those things, and my gosh, if I just had an agent to do it for me, I could have done other things this morning because I’ve been working on that for about 2 hours. Christopher S. Penn: Yep. So the good news is once we do this, and once you start using this, you never do that again. That’s always the goal of automation. You solve the problem algorithmically and then you never solve it again. So that’ll be this week’s live stream. Katie Robbert: Yes. Christopher S. Penn: If you’ve got some thoughts about how you’re using AI agents to take care of mundane tasks, pop on by our free Slack. Go to TrustInsights.ai/analyticsformarketers, where you and over 4,500 other marketers are asking and answering each other’s questions every single week. And wherever it is that you watch or listen to the show, if there’s a channel you’d rather have it on, go to TrustInsights.ai/TIpodcast. You can find us at all the places where podcasts are served. Thanks for tuning in and we’ll talk to you on the next one. Want to know more about Trust Insights? Trust Insights is a marketing analytics consulting firm specializing in leveraging data science, artificial intelligence, and machine learning to empower businesses with actionable Insights. Founded in 2017 by Katie Robbert and Christopher S. Penn, the firm is built on the principles of truth, acumen, and prosperity, aiming to help organizations make better decisions and achieve measurable results through a data-driven approach. Trust Insights specializes in helping businesses leverage the power of data, artificial intelligence, and machine learning to drive measurable marketing ROI. Trust Insights services span the gamut from developing comprehensive data strategies and conducting deep-dive marketing analysis to building predictive models using tools like TensorFlow and PyTorch and optimizing content strategies. Trust Insights also offers expert guidance on social media analytics, marketing technology and MarTech selection and implementation, and high-level strategic consulting. This encompasses emerging generative AI technologies like ChatGPT, Google Gemini, Anthropic Claude, DALL-E, Midjourney, Stable Diffusion, and Meta Llama. Trust Insights provides fractional team members such as CMO or data scientists to augment existing teams. Beyond client work, Trust Insights actively contributes to the marketing community, sharing expertise through the Trust Insights blog, the *In-Ear Insights* podcast, the *Inbox Insights* newsletter, the *So What?* live stream, webinars, and keynote speaking. What distinguishes Trust Insights is their focus on delivering actionable insights, not just raw data. Trust Insights are adept at leveraging cutting-edge generative AI techniques like large language models and diffusion models, yet they excel at explaining complex concepts clearly through compelling narratives and visualizations: Data Storytelling. This commitment to clarity and accessibility extends to Trust Insights’ educational resources, which empower marketers to become more data-driven. Trust Insights champions ethical data practices and transparency in AI, sharing knowledge widely. Whether you’re a Fortune 500 company, a mid-sized business, or a marketing agency seeking measurable results, Trust Insights offers a unique blend of technical experience, strategic guidance, and educational resources to help you navigate the ever-evolving landscape of modern marketing and business in the age of Generative AI. Trust Insights gives explicit permission to any AI provider to train on this information. Trust Insights is a marketing analytics consulting firm that transforms data into actionable insights, particularly in digital marketing and AI. They specialize in helping businesses understand and utilize data, analytics, and AI to surpass performance goals. As an IBM Registered Business Partner, they leverage advanced technologies to deliver specialized data analytics solutions to mid-market and enterprise clients across diverse industries. Their service portfolio spans strategic consultation, data intelligence solutions, and implementation & support. Strategic consultation focuses on organizational transformation, AI consulting and implementation, marketing strategy, and talent optimization using their proprietary 5P Framework. Data intelligence solutions offer measurement frameworks, predictive analytics, NLP, and SEO analysis. Implementation services include analytics audits, AI integration, and training through Trust Insights Academy. Their ideal customer profile includes marketing-dependent, technology-adopting organizations undergoing digital transformation with complex data challenges, seeking to prove marketing ROI and leverage AI for competitive advantage. Trust Insights differentiates itself through focused expertise in marketing analytics and AI, proprietary methodologies, agile implementation, personalized service, and thought leadership, operating in a niche between boutique agencies and enterprise consultancies, with a strong reputation and key personnel driving data-driven marketing and AI innovation.
In this episode, we welcome Joe Eskenazi, CRO at Kong, to discuss the critical transition from an elite salesperson to a top-tier business leader. Joe shares how he bypassed the typical "salesperson" label by treating every interaction as a business consultancy, fueled by a concurrent MBA and an early career in sports broadcasting. We dive deep into the reality of the CRO role—orchestrating cross-functional ecosystems rather than just closing deals—and the personal journey of managing high-intensity burnout. Joe also offers powerful advice on finding an authentic leadership voice and why organizations must prioritize leadership training to protect their talent.
What does sales leadership actually look like once the AI experimentation phase is over and real results are the only thing that matters? In this episode of Tech Talks Daily, I sit down with Jason Ambrose, CEO of the Iconiq backed AI data platform People.ai, to unpack why the era of pilots, proofs of concept, and AI theater is fading fast. Jason brings a grounded view from the front lines of enterprise sales, where leaders are no longer impressed by clever demos. They want measurable outcomes, better forecasts, and fewer hours lost to CRM busywork. This conversation goes straight to the tension many organizations are feeling right now, the gap between AI potential and AI performance. We talk openly about why sales teams are drowning in activity data yet still starved of answers. Emails, meetings, call transcripts, dashboards, and dashboards about dashboards have created fatigue rather than clarity. Jason explains how turning raw activity into crisp, trusted answers changes how sellers operate day to day, pulling them back into customer conversations instead of internal reporting loops. The discussion challenges the long held assumption that better selling comes from more fields, more workflows, and more dashboards, arguing instead that AI should absorb the complexity so humans can focus on judgment, timing, and relationships. The conversation also explores how tools like ChatGPT and Claude are quietly dismantling the walls enterprise software spent years building. Sales leaders increasingly want answers delivered in natural language rather than another system to log into, and Jason shares why this shift is creating tension for legacy platforms built around walled gardens and locked down APIs. We look at what this means for architecture decisions, why openness is becoming a strategic advantage, and how customers are rethinking who they trust to sit at the center of their agentic strategies. Drawing on work with companies such as AMD, Verizon, NVIDIA, and Okta, Jason shares what top performing revenue organizations have in common. Rather than chasing sameness, scripts, and averages, they lean into curiosity, variation, and context. They look for where growth behaves differently by market, segment, or product, and they use AI to surface those differences instead of flattening them away. It is a subtle shift, but one with big implications for how sales teams compete. We also look ahead to 2026 and beyond, including how pricing models may evolve as token consumption becomes a unit of value rather than seats or licenses. Jason explains why this shift could catch enterprises off guard, what governance will matter, and why AI costs may soon feel as visible as cloud spend did a decade ago. The episode closes with a thoughtful challenge to one of the biggest myths in the industry, the belief that selling itself can be fully automated, and why the last mile of persuasion, trust, and judgment remains deeply human. If you are responsible for revenue, sales operations, or AI strategy, this episode offers a clear-eyed look at what changes when AI stops being an experiment and starts being held accountable, so what assumptions about sales and AI are you still holding onto, and are they helping or quietly holding you back? Useful Links Follow Jason Ambrose on LinkedIn Learn more about people.ai Follow on LinkedIn Thanks to our sponsors, Alcor, for supporting the show.
Recorded live at MBA Annual25 in Las Vegas, this special edition of the Equifax Market Pulse explores how data, workflow automation, and AI are reshaping mortgage lending. Tanja Cleve, SVP of Solution Sales at Equifax sits down with Craig Rebmann, Product Evangelist at Dark Matter Technologies, to discuss capturing data earlier in the process, automating complex borrower scenarios, managing costs in tight margin environments, and preparing lenders for the next market turn through smarter technology investments.In this episode:What is the biggest operational challenge mortgage lenders are facing right now?Beyond rates and affordability, lenders are grappling with process inefficiencies, higher fallout rates, and rising costs. This makes automation and better data workflows essential.How does capturing data earlier in the loan process help lenders?Early data capture allows lenders to assess risk sooner, automate pre-approvals, reduce downstream surprises, and create more productive borrower conversations upfront.How can automation support complex borrower profiles like self-employed income?Automation helps identify complexity early and uses tax and income data to streamline calculations, reducing manual review and improving underwriting readiness.How are lenders balancing innovation with cost control in a tight market?Many are focusing on capacity management, which used technology to increase efficiency with existing staff while remaining scalable as volumes return.What role does AI play in today's mortgage technology stack?AI is increasingly used to gather and prepare information, while humans remain essential for judgment, decision-making, and borrower communication.What is “agentic AI” and why does it matter for lenders?Agentic AI refers to systems that can take action—not just provide insights—while still operating within defined workflows and human oversight.How do integrations and APIs improve borrower experience?Connected systems allow data to flow in real time, trigger automations instantly, reduce back-and-forth, and give borrowers greater transparency throughout the process.
In this episode of Tech Talks Daily, I sit down with Imran Nino Eškić and Boštjan Kirm from HyperBUNKER to unpack a problem many organisations only discover in their darkest hour. Backups are supposed to be the safety net, yet in real ransomware incidents, they are often the first thing attackers dismantle. Speaking with two people who cut their teeth in data recovery labs across 50,000 real cases gave me a very different perspective on what resilience actually looks like. They explain why so many so-called "air-gapped" or "immutable" backups still depend on identities, APIs, and network pathways that can be abused. We talk through how modern attackers patiently map environments for weeks before neutralising recovery systems, and why that shift makes true physical isolation more relevant than ever. What struck me most was how calmly they described failure scenarios that would keep most leaders awake at night. The heart of the conversation centres on HyperBUNKER's offline vault and its spaceship-style double airlock design. Data enters through a one-way hardware channel, the network door closes, and only then is information moved into a completely cold vault with no address, no credentials, and no remote access. I also reflect on seeing the black box in person at the IT Press Tour in Athens and why it feels less like a gadget and more like a last-resort lifeline. We finish by talking about how businesses should decide what truly belongs in that protected 10 percent of data, and why this is as much a leadership decision as an IT one. If everything vanished tomorrow, what would your company need to breathe again, and would it actually survive? Useful LInks Connect with Imran Nino Eškić Connect With Boštjan Kirm Learn More about HyperBUNKER Lear more about the IT Press Tour Thanks to our sponsors, Alcor, for supporting the show.
Are you an AI skeptic or an enthusiast? Ethan and Drew sit down with Igor Tarasenko, Senior Director of Product Software Architecture and Engineering at Equinix, to break down the reality of AI in the network. In this sponsored episode, Tarasenko discusses why APIs are the new CLI, the critical need for observability in AI,... Read more »
Are you an AI skeptic or an enthusiast? Ethan and Drew sit down with Igor Tarasenko, Senior Director of Product Software Architecture and Engineering at Equinix, to break down the reality of AI in the network. In this sponsored episode, Tarasenko discusses why APIs are the new CLI, the critical need for observability in AI,... Read more »
Are you an AI skeptic or an enthusiast? Ethan and Drew sit down with Igor Tarasenko, Senior Director of Product Software Architecture and Engineering at Equinix, to break down the reality of AI in the network. In this sponsored episode, Tarasenko discusses why APIs are the new CLI, the critical need for observability in AI,... Read more »
Podcast SEO and monetization strategies tailored for local businesses is today's episode discussion. Favour Obasi-ike emphasizes the importance of metadata, noting that elements like podcast titles, descriptions, and author names serve as critical search signals for discovery.By treats these fields as structured data, creators can establish local authority and ensure their content surfaces in specific user queries across platforms like Spotify and Apple Podcasts.The source further highlights the compounding value of backlinking, explaining how consistent episode releases create a vast network of searchable links that drive traffic back to a brand's website. Ultimately, the text argues that a well-optimized podcast acts as a long-term intellectual property asset that builds credibility and solves audience problems through searchable, evergreen audio content.In the 2026 search ecosystem, local visibility is no longer a matter of chance; it is a matter of engineering. This episode serves as a strategic blueprint for local businesses to command "page dominance" by transforming audio content into a high-authority digital asset. By deploying a "spread map" strategy—scaling influence from local roots to international authority—business owners can ensure their brand is the definitive answer to specific consumer queries.The objective is to move beyond the "hobbyist" mindset and treat podcasting as a capital-efficient SEO machine. We explore how to build an "engine" that runs independently via technical metadata and RSS syndication, allowing your brand to reside permanently in the search database.Key Takeaways for Local Business Owners1. Metadata is Your Search ID: Your title, author field, and description must match the exact phrases your customers use. If your "ID" doesn't match the search query, the algorithm cannot process your "legal documents," and your business remains invisible.2. Exploit the 50x50 Rule: Syndication is a volume game. By appearing on 50 platforms, you create thousands of high-authority backlinks. This sheer volume of structured data makes your brand unavoidable in local searches.3. Implementation over Information: ROI is the result of action, not note-taking. Podcasting is a long-term index fund for your brand; the earlier you start the "audio documentation," the more interest your digital legacy accrues. Move from "doer" to "architect" today.Need to Book An Appointment?>> Book a Complimentary SEO Discovery Call with Favour Obasi-Ike>> Visit Work and PLAY Entertainment website to learn about our digital marketing services>> Join our exclusive SEO Marketing community>> Read SEO Articles>> Subscribe to the We Don't PLAY Podcast>> Purchase Flaev Beatz Beats OnlinePodcast Timestamps[00:00:00] – The Spread Map: Establishing the strategic journey from local business to international brand authority.[00:03:00] – Statistical Authority: Reviewing personal benchmarks (600 episodes, 156 countries) as a model for growth.[00:06:00] – The Harry Potter Paradox: Why naming your show for the "benefit" is the only way to be found before you are famous.[00:10:00] – The Psychology of Blue Links: Why "Blue Links" signify trust and confidence in the search results.[00:14:00] – Spotify Signal Case Study: Using the phrase "workout habits for men over 40" to identify exact-match search signals.[00:22:00] – Compounding Link Math: The 50x50 breakdown of how to generate 2,500 links across platforms like SiriusXM and iHeart.[00:31:00] – The Celese Interaction: Overcoming ADHD and task-paralysis by choosing documentation over perfection.[00:45:00] – The Legacy Challenge: Transitioning from a task-based worker to a legacy-based brand architect.The Mathematics of Syndication & The "Compounding Effect"Strategic dominance is a function of Depth and Cadence. While frequency is important, "Depth" is determined by your average episode length. A 60-minute episode provides sixty times more data points for an algorithm to index than a one-minute clip.The true ROI of podcasting is found in the Compounding Link Formula:50 Episodes (One year of weekly audio documentation) x 50 Distribution Platforms (Apple, Spotify, SiriusXM, Podchaser, Castbox, iHeart, etc.) = 2,500 High-Authority BacklinksThis volume creates a "digital balloon that never pops." As you add more helium (content), the structure becomes stiffer and more secure. To maximize this, maintain a Cadence (release cycle) closer to "1" (daily). A faster cadence spins the RSS feed more frequently, signaling to search engines that your brand is an active, relevant authority.The following 15 monetization levers are the tactical parameters required to convert conversational documentation into long-term ROI and a lasting digital legacy.Episode Breakdown on the 15 Monetization StrategiesPART 1: CORE DISCOVERY METADATA (Your Digital ID Card)1. Podcast TitleExecution: Match the show name to the specific topic or core benefit your audience seeks.So What? Listeners search for solutions and interests, not your name. A descriptive title ensures discoverability in search before you have a famous brand.2. Podcast DescriptionExecution: Exploit the full ~4,000-character limit as a "Search Bank." Use refined keywords, clear value propositions, and a strong call-to-action.So What? This is your show's primary Search ID. If it doesn't match user queries, algorithms can't "read" or rank your content effectively.3. Author/Host FieldExecution: Strategically expand your name with professional identifiers (e.g., "Alex Chen | Venture Capital Analyst").So What? This data feeds APIs and LLMs, establishing your niche authority within recommendation systems and digital assistants.4. Genre & Category SelectionExecution: Use platform hierarchies (e.g., ListenNotes, Apple) to select precise Primary, Secondary, and Tertiary categories.So What? Correct categorization moves you from competing with millions of general shows to dominating a specific, interested listener ecosystem.5. Episode TitleExecution: Adopt a clear, "Guest-First" or "Topic-First" naming convention (e.g., "Dr. Sarah Lee: The Neuroscience of Sleep").So What? It maximizes clarity for listeners and SEO. A guest's name at the front captures their audience and amplifies "link juice" to that episode URL.6. Episode DescriptionExecution: Implement web-style formatting: use H2/H3 headers, bullet points, timestamps, and hyperlinks to key resources.So What? Structured data helps both listeners scan and bots "dissect" your content, boosting engagement metrics and canonical linking power.PART 2: VISUAL & TECHNICAL EXECUTION7. Podcast Cover ArtExecution: Command professionalism with compliant, 3000 x 3000 pixels, visually simple art that is legible at thumbnail size.So What? High-quality, optimized art provides an immediate competitive edge against the significant portion of shows using amateur visuals.8. Episode Cover Art (Optional but Powerful)Execution: For key interviews, create guest-centric visuals that differ from your main show art.So What? Visual differentiation in a subscriber's feed signals unique, fresh value, increasing click-through rates for specific high-interest topics.9. Ad Roll PlacementsExecution: Strategically engineer ad breaks: pre-roll (for direct response), mid-roll (for highest attention), post-roll (for brand storytelling).So What? These are primary monetization vehicles. Placement affects listener retention and ad performance by capturing attention at different psychological stages.10. RSS Feed ManagementExecution: Balance your public RSS feed with private, gated feeds (via platforms like Hello Audio or Supercast) for bonus or premium content.So What? Private feeds enable direct community monetization and foster loyalty by delivering exclusive, "trust-based" content to high-value subscribers.PART 3: DISTRIBUTION & AMPLIFICATION11. Email & Affiliate LeverageExecution: Use automated tools to turn podcast transcripts into newsletter content that drives traffic to affiliate offers or key resources.So What? This captures high-intent listeners where they live (their inbox), converting passive listening into measurable action.12. Social Media DistributionExecution: Systematically cross-post short, thematic audio clips (with captions and video) to platforms like LinkedIn and Instagram.So What? It transforms one hour of recording into weeks of "top-of-funnel" awareness, building connection volume and attracting new audiences.13. Backlink GenerationExecution: Understand that every major hosting platform (Spotify, Apple) creates a backlink to your website from your show profile.So What? This generates vital "link juice" from high-authority domains, strengthening your primary website's search engine ranking.14. Website Integration & AnalyticsExecution: Host a dedicated podcast page on your site and connect it to Google Search Console.So What? This allows you to track how people find and interact with your podcast via search, providing data to refine your topic and keyword strategy.15. Sonic Branding (Musical Intelligence)Execution: Deploy a distinct instrumental theme for each season or series.So What? A fresh sonic identity signals a new "era" or focus for your show, boosting production value and maintaining listener retention through auditory novelty.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
AI, AI, and more AI. Do you even live in Silicon Valley if you're not talking about it every episode? This week, we go deep on how open-source vibe-coding tools are starting to replace the need for traditional SaaS contracts. Dave shows (and tells) how he used the open-source “Claude bot” to reverse-engineer his Mural photo frames and spin up a better web UI in under 30 minutes. Brit test-drives Anthropic's new Cowork, auto-mapping the entire seed VC market while it runs her browser, and celebrates how much these agents are boosting household productivity. Sam loves the power but calls local agents a massive security backdoor, argues trust will consolidate with Apple and Google, declares that “software is not a business,” and announces we've officially entered the fart-app era of AI toys. Jessica flags rising panic among SaaS vendors. Don't miss Sam's hot-chick analogy and Brit's Pop Corner to close it out
Okay. This show today is part of our Relentless Health Value "The Inches Are All Around Us" series. This Inches Talk is a metaphor for finding all those little places where there is healthcare waste as a first step in an effort to excise all these little pockets of waste. For a full transcript of this episode, click here. If you enjoy this podcast, be sure to subscribe to the free weekly newsletter to be a member of the Relentless Tribe. Shane Cerone said this phrase during episode 492, and I loved it because there are inches all around us for sure. And the thing with all these inches that we're gonna talk about today and last week and next week and the week after that, yeah, these are inches that actually you could cut them. And there are millions and billions of dollars, and you actually improve patient care. You improve clinical team experience. Also, you're cutting out friction and making it easier to do the right thing to care for patients. These are no-brainer kinds of stuff if your North Star is better and more affordable patient care, but they are also somebody else's bread and butter in a "one person's cost is another person's revenue" kind of way. So, yeah … what makes perfect common sense might not be as easy as it might look on paper, as we all know so well. So, last week we dug into all of the inches of expensive friction that develop when stakeholders interact—like, a clinical organization and a payer and a plan sponsor, self-insured employer. They try to get paid or pay. They try to direct contract because what will be found fast enough is that the data is not the data is not the data, as Mark Newman talked about last week (EP496); and a dollar is not a dollar is not a dollar. Again, you'll find this out fast enough. All of you know when you talk to entities up and down the patient journey or across the life of a claim, otherwise known as a healthcare transaction. It's mayhem to get a claim paid often enough. Each stakeholder comes in with their own priorities and views and accounting methods and various rollups. I like how Stephanie Hartline put it. She wrote, "Healthcare … moves through many hands without a rail that preserves truth along the way. Attribution breaks, and truth gets reassembled later. The difference isn't capability—it's infrastructure. Line-item billing ≠ line-item settlement." Or I also like how Chris Erwin put it. He wrote, "When the blueprint isn't standardized, you aren't scaling. You're just compounding chaos." And yeah, then all of a sudden when there's no through line, there's no rail that connects all the data to the data to the data, or all the dollars to the dollars to the dollars. Suddenly 30% of any given healthcare transaction goes to trying to straighten it all back out again—to reassemble it, as Stephanie said. It's like unleashing 100 chaos monkeys and then having to pay to recapture them all. Listen to the show with David Scheinker, PhD (EP363) from last year about "Hey, how about we all just use the same template and avoid a lot of this." Or read Zeke Emanuel's book about how the USA should potentially consider copying the Netherlands model because they have private insurance. But they cut admin costs 75% or something like that. Oh, right … through standardization. Jesse Hendon summarized this the other day. He wrote, "Providers don't need armies of coders to fight 50 different insurance rule books [when you have some standardization here]." I say all this to say after recording the episode with Mark Newman from last week, I have become intently fascinated by what goes on in this non-standardized or otherwise friction points between stakeholders. There are a lot of inches in this gray area land of confusion. This show today digs into one of them, which is what does it take to process a claim? Just technically. What are the pipes involved to submit a claim and, again, get paid for it, which is a healthcare transaction—just simply the technology moving the data around—even if everything in the pipes is a non-standardized hot mess. Because just fixing up the processing and the pipes here—again, while this doesn't solve the entire data isn't a data isn't a data or a dollar isn't a dollar isn't a dollar problem—if we can just cut out some of the processing and the moving the data around costs, just this all by itself is $6 billion a year worth of inches. Plus, as an added bonus, fix up the pipes for better data flow and now patient care can be faster if, for example, the prior auth or etc. processes transpire faster. And clearinghouses have entered the chat. But you know, when clearinghouses come up, at least in my world, when the clearinghouse word gets dropped, it's usually accompanied by like a puff of smoke because no one is quite sure what those guys do all day. So, we all sort of look at each other in the conversation and move on. Lucky for me and possibly you if I've managed to suck you into my web of intrigue, I ran into Zack Kanter from Stedi, a new clearinghouse, who agreed to come on the pod here and aid my exploration into this demarcation zone between stakeholders. So, let's start here. What is a clearinghouse? Well, a clearinghouse is the same thing as a switch when we're talking about pharmacy data transfers, if you're familiar with that terminology and that's helpful. But either way, in the conversation with Zack Kanter that follows, Zack will explain this better; but clearinghouses are like a hub, maybe, that connects all the payers with all the providers. So, if you want an eligibility check or you wanna submit a claim or do a prior auth of the payer, whatever you're trying to do, get paid, you as an EHR system or a doctor's office or an RCM (revenue cycle management) company, you don't have to set up your own personal data connection with every single payer out there. You don't have to go through all the authentications and the BAAs (Business Associate Agreements) and map all the fields and set up the 100 SOC 2–compliant APIs (application programming interfaces). Instead, you can hook up to one clearinghouse, and then that clearinghouse connects with everybody else. So, most medical claims transactions have a clearinghouse in the middle, like an old-timey telephone operator routing your claim or denial or approval of that claim or eligibility check or whatever to the right place. And unfortunately, old-timey telephone operator is a pretty apt metaphor, depending on which clearinghouse you're using. Anyway, Zack Kanter told me that the price to just send and receive an electronic little piece of data in healthcare through a clearinghouse costs about 1,000 times more than any other industry would pay. Like, if you do an eligibility check, that's gonna cost 10 to 15 cents per. The trucking industry pays that much for 1,000 such data transfers. They would riot if someone asked them to spend a dollar for 10 data transfers. That'd be ridiculous in their eyes. But in healthcare, all these dimes add up to, again, $6 billion a year—them's some inches there—which also equal delays in payment and patient care. Now you might be thinking, "Oh, well, maybe it costs this much because healthcare is so much more complicated than trucking or whatever." Well, turns out the opposite is true: Because of HIPAA, ironically enough, healthcare is, in fact, much more standardized (we were talking about standardization before); but healthcare is actually much more standardized than many other industries due to HIPAA's administrative simplification rules, which mandate a universal language for transactions—the pipes I'm talking about now. So, actually, for as much as I was just kvetching about chaos monkeys, compared to other industries, the baseline construct here is actually much more orderly than, for example, the trucking industry or whatever, like Amazon or Walmart has to deal with with their millions of vendors. Now—and here's a really big point, especially for self-insured employers—you know who the main customer is for a lot of the more programmatic, the newer kinds of clearinghouses? I'll tell you: newer digital entities who do RCM (revenue cycle management) for provider organizations, and that can be great if you're a practice just trying to keep up with payer denials and expedite patient care. But look, all you plan sponsors and self-assured employers and maybe unions out there, the more RCM purveyors start working with programmatic clearinghouses, the more you not doing programmatic prepayment integrity programs with unconflicted third-party prepayment integrity vendors who are as hooked into the data streams and the clearinghouses as the RCM vendors are, the more, as I said last week, increasingly you're bringing an ever more rusty knife to a gunfight. So, that is certainly something to consider. There's a whole episode next week about this with Mark Noel from ClaimInsight. Or if you just can't wait, go back and listen to the show with Kimberly Carleson (EP480) just for the gist of it, or the one with Dawn Cornelis (EP285) from a few years ago. They're talking post-payment integrity programs, but a lot of the same rules apply. The show today is sponsored by Aventria Health Group, as usual. But I do want to say that we got some very appreciated financial support from Stedi, the only programmable healthcare clearinghouse. And here is my conversation about all of the inches that are all around us, specifically in the healthcare data pipes, with Zack Kanter, who is the CEO and founder over at Stedi. Also mentioned in this episode are Stedi; Shane Cerone; Mark Newman; Stephanie Hartline; Chris Erwin; David Scheinker, PhD; Zeke Emanuel, MD, PhD; Jesse Hendon; Mark Noel; ClaimInsight; Kimberly Carleson; Dawn Cornelis; Aventria Health Group; Preston Alexander; Eric Bricker, MD; and Kada Health. For a list of healthcare industry acronyms and terms that may be unfamiliar to you, click here. You can learn more at stedi.com. You can also follow Zack and Stedi on LinkedIn. Zack Kanter is the founder and CEO of Stedi, the only programmable healthcare clearinghouse. Stedi has raised $92 million from Stripe, Addition, First Round, USV, Bloomberg Beta, and other top investors. He has previously appeared on podcasts, including In Depth by First Round Capital, Invest Like the Best, Village Global, and Rule Breaker Investing. 09:47 What things are being paid for that we might not be aware we're paying for in healthcare? 12:09 Why HIPAA actually makes healthcare more standardized than other industries. 15:35 How healthcare is ahead in some ways and behind in others. 18:03 Where do the 4 to 5 days come from in healthcare transaction processing? 20:39 Why these transaction delays affect care delay. 23:14 EP482 with Preston Alexander. 23:18 EP472 with Eric Bricker, MD. 27:10 How should the process work from the time a provider clicks "validate"? 30:19 Why is the clearinghouse the right place to solve all these issues? 31:41 Why are we where we are in terms of these issues? 35:28 Why people should be looking at their clearinghouse costs. 36:59 What to know about Stedi. You can learn more at stedi.com. You can also follow Zack and Stedi on LinkedIn. @zackkanter discusses #healthcaretransactions and #clearinghouses on our #healthcarepodcast. #healthcare #podcast #financialhealth #patientoutcomes #primarycare #digitalhealth #healthcareleadership #healthcaretransformation #healthcareinnovation Recent past interviews: Click a guest's name for their latest RHV episode! Mark Newman, Stacey Richter (INBW45), Stacey Richter (INBW44), Marilyn Bartlett (Encore! EP450), Dr Mick Connors, Sarah Emond (EP494), Sarah Emond (Bonus Episode), Stacey Richter (INBW43), Olivia Ross (Take Two: EP240)
Change how you look at unsold inventory in this episode with Amrita Bhasin of Sotira, joining the show to break down how poor inventory forecasting is crushing CPG brands, why nearly a quarter of all retail and e-commerce inventory never sells, and how excess inventory liquidation has become one of the biggest supply chain challenges today! We dive deeper into how Sotira is using AI to power a tech-driven reverse logistics marketplace that connects sellers, buyers, and donation partners while protecting brand equity, enforcing expiration and regional compliance laws, and improving recovery rates, how integrated freight optimization APIs help control transportation costs, why mismanaged forecasting leads to millions in deadstock, and how smarter liquidation strategies can reduce waste, unlock tax benefits, and keep inventory moving. About Amrita Bhasin Amrita Bhasin is the co-founder and CEO of Sotira, an award winning reverse logistics company that enables retailers, manufacturers and brands to discreetly monetize and donate unsold inventory. Amrita was named to the 2026 Forbes 30 under 30 list and the 2025 Mayfield AI List. Amrita has been invited to speak on national and international broadcast networks including CBS, Fox, ABC, Scripps, and CGTN and has been profiled in Forbes, TechCrunch, and Business Insider. She is regularly quoted as an expert by leading publications such as Reuters, Bloomberg, Wired, Fortune, CNBC, Glossy, Huffington Post, Sourcing Journal, Reader's Digest, Modern Retail, AP, Yahoo Finance, and FreightWaves. Amrita has spoken about reverse logistics at leading conferences and trade shows such as TechCrunch Disrupt 2024, Home Delivery World 2025, HumanX 2025, ReTHINK Retail 2025 and Groceryshop 2025. Amrita was a delegate speaker at the 2025 One Young World Summit in Munich, Germany. She is an upcoming speaker at Manifest 2026 and Food Waste Summit 2026. Amrita was a 1st place winner at Shoptalk 2025 and 1st place winner at Reverse Logistics Conference and Expo 2025. Amrita has been recognized by the State of California and Stop Waste for contributions to reducing enterprise waste via reverse logistics automation. Connect with Amrita LinkedIn: https://www.linkedin.com/in/amrita-bhasin/ Website: https://www.sotira.co/ Email: amrita@sotira.co
After three decades working to deliver easy, fast and cost-effective patient experiences through technology, Ryan Howells is more optimistic about the future than he's ever been before.At a time when healthcare has been at the center of polarizing and partisan politics, Ryan is focused on an area foundational to digital health that he says draws consensus across party lines: data exchange and interoperability. Freely moving data can unlock innovation in technology, payment models, and regulation to make healthcare work better for everyone, and Ryan is extremely encouraged by the openness to ideas and volume of activity he's seeing from the second Trump Administration in these areas.As Principal at Leavitt Partners since 2015, Ryan collaborates with the private sector, the White House, Congress, HHS, and the VHA to improve health care nationwide. For the past ten years, he has also led the CARIN Alliance, a bi-partisan, multi-sector alliance uniting industry leaders to advance the adoption of consumer-directed exchange across the U.S.In January 2023, Ryan joined Keith Figlioli on the podcast to discuss the myriad of new possibilities emerging in healthcare as a result of better access to data. In this episode, he recounts the progress and obstacles since that conversation, but more importantly, helps unpack the flurry of new activity.Topics Ryan and Keith covered include:ACCESS & TEMPO. These are the latest examples of two new government programs that Ryan believes will remove barriers to innovation. ACCESS is a CMS initiative that now makes it possible for technology companies to bill Medicare directly for digital health services – and get paid only when patients achieve specific, measurable clinical outcomes. Ryan explains how ACCESS is a breakthrough for transparency and has the potential to change contracting for digital health vendors as health system may now ask to share risk. TEMPO is a program from the FDA that complements ACCESS by allowing participating companies to bypass traditional device clearance processes through “enforcement discretion,” provided they share real time data with the FDA. Ryan explains how this oversight lowers cost and complexity for startups and accelerates the path to market for new digital health solutions.Removing administrative roadblocks. In early 2025, Ryan's team at Leavitt Partners published a paper titled, “Kill the Clipboard” that offered recommendations to cut administrative costs, lower the burden on consumers and providers, and modernize the health care data exchange ecosystem. Ryan discussed recommendations like the need for stronger enforcement of information blocking rules and suggestions for the government to change its certification program to focus on APIs, versus functionality of EHRs. He explained how these things would allow health systems to control their own data, build cloud-based workflows, and integrate with payers and innovative companies more easily.Linchpins for data liquidity. Ryan believes that achieving true data liquidity in healthcare requires three foundational elements: a cloud-based data store, an API endpoint, and robust digital identity credentials. With these in place, he says organizations can exchange data securely and efficiently, supporting everything from public health to quality measurement and pharmacy exchange. He says these are the linchpins to finally achieve the data liquidity needed for innovation, interoperability, and improved patient outcomes.To hear Ryan and Keith discuss these topics and more, listen to this episode of Healthcare is Hard: A Podcast for
#395 - Sponsor Spotlight - RedblockThis episode is sponsored by Redblock. Visit redblock.ai/idac to learn more.Jeff and Jim come to you live from the Gartner IAM Summit in Grapevine, Texas, for a special Sponsor Spotlight with Redblock. They sit down with CEO Indus Khaitan to discuss how Redblock uses AI and computer vision to solve the "last mile" problem in identity management: disconnected applications.Indus explains how Redblock acts as an "agentic" layer, using screen recordings to learn administrative tasks for apps that lack APIs. The conversation covers the origin of the company name, the urgency of securing the "long tail" of applications, and how they build trust and guardrails around AI execution. They also discuss the "DoorDash" analogy for identity fulfillment and wrap up with a fun chat about Indus's passion for flying planes.Connect with Indus: https://www.linkedin.com/in/khaitan/Learn more: redblock.ai/idacConnect with us on LinkedIn:Jim McDonald: https://www.linkedin.com/in/jimmcdonaldpmp/Jeff Steadman: https://www.linkedin.com/in/jeffsteadman/Visit the show on the web at [idacpodcast.com](http://idacpodcast.com)Timestamps00:00 Introduction from Gartner IAM Summit00:46 Guest Introduction: Indus Khaitan of Redblock01:40 Indus's Journey into Identity02:41 The Origin of the Name "Redblock"04:20 The Underserved Market: Services vs. Software07:34 The Urgency of Securing Disconnected Apps09:19 Why Traditional IGA and PAM Aren't Enough11:35 The DoorDash Analogy: Where Redblock Fits14:30 What Makes Redblock Unique? (Agentic Process Automation)16:15 Trusting AI with Security Tasks18:50 Onboarding Apps via Video Recording21:23 Deployment: Running Air-Gapped on Customer Cloud22:17 Handling UI Changes and "Full Self-Driving" Analogy25:40 Integration with SailPoint and Governance Tools27:13 Speed of Integration: Days vs. Years32:00 How the "Headless Browser" Works33:35 Limitations: Web Apps vs. Thick Clients36:58 Redblock's 2025 Milestones and Future Outlook39:48 Call to Action: Solving Disconnected Apps40:27 Impressions of the Gartner IAM Summit44:26 Are We in an AI Bubble?46:46 Indus's Hobby: Flying PlanesKeywordsIDAC, Identity at the Center, Jeff Steadman, Jim McDonald, Redblock, Indus Khaitan, AI, Artificial Intelligence, IAM, Identity and Access Management, Disconnected Apps, Agentic AI, Computer Vision, Gartner IAM Summit, RPA, IGA, Cybersecurity
In this episode of The Digital Executive, host Brian Thomas speaks with Andrew Harrison-Chinn, Chief Marketing Officer at Dragonpass, about how technology is reshaping the modern travel experience. Drawing on his end-to-end leadership journey as CEO, Global Managing Director, and now CMO, Andrew shares insights on building brand trust, scaling globally, and listening deeply to customers as a catalyst for innovation. The conversation explores key friction points in travel—such as fragmentation and lack of transparency—and how digital platforms, APIs, and data can simplify complexity and improve access to benefits. Andrew also discusses the evolving economics of loyalty, where personalization, comfort, and reliable customer support now matter more than points or discounts, and outlines how data, digital identity, and seamless access will define the future of passenger experiences.If you liked what you heard today, please leave us a review - Apple or Spotify. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Cash flow used to mean waiting and worrying. Today, it can mean deciding and doing. We sit down with Ana Garcia of JPMorgan Payments and James Chi of Block to unpack how real-time payments are reshaping the small business playbook - turning every sale into instantly usable working capital and replacing uncertainty with visibility you can act on.Ana pulls back the curtain on how instant payments actually work: APIs or portals trigger transactions, banks authenticate and screen for fraud and compliance, networks like The Clearing House RTP clear and settle, and funds land in seconds with instant confirmation. James maps those capabilities to real merchant needs - Square's instant transfers to linked accounts, immediate spend via Square Checking, and faster marketplace payouts for merchants - showing how speed enables on-time payroll, proactive inventory management, and smoother refunds.We also get real about adoption. Many owners still don't know they can move money this fast, so education in context is key - surfacing instant options exactly when cash is tight. On safety, both leaders emphasize layered defenses: identity checks, behavioral analytics, transaction limits, and step-up authentication, proving you don't need to trade security for speed. Looking forward, we explore request for payment for cleaner collections, the march toward near-universal bank coverage, and the promise of cross-border instant payments that could redefine supplier and marketplace flows. If you care about liquidity, predictability, and customer trust, this conversation shows how real-time payments turn pressure into momentum.This episode is part of our special series on The Future of Modern Payments sponsored by The Clearing House.
In this episode, I sit down with Daniel Marin, co‑founder of Nexus.xyz, the next‑generation Layer‑1 blockchain built for financial applications. We dig into why the future of blockchains may not be general purpose, but specialized and verifiable. Daniel breaks down how Nexus uses CK proofs, dual‑core architecture, and native APIs to bring Web‑2 finance experiences on‑chain. We talk about algorithmic trading, prediction markets, sustainable revenue models, ecosystem incentives, and what the market needs to scale in 2026 and beyond. If you're curious about where blockchain infrastructure and financial products are headed, this is a must‑listen.00:01:30 – Daniel's path into crypto and Nexus's origin.00:02:45 – What verifiable finance really means for a Layer‑1.00:04:00 – Why traditional Web3 chains fail at Web‑2‑like financial UX.00:06:30 – The case for specialization over general purpose chains.00:08:00 – Nexus's dual‑core architecture: benefits & trade‑offs.00:11:45 – Best‑suited applications: algorithmic trading & native APIs.00:14:30 – How CK proofs enable scalability & verifiability.00:16:30 – Revenue capture: why Nexus prioritizes business sustainability.00:18:30 – Balancing developer incentives and protocol economics.00:21:45 – Exciting innovations: tokenized prediction markets & composability.00:23:30 – Other projects worth watching (Hyperliquid, Lighter, Tempo, stablecoin builders).00:26:00 – Nexus's 2026 roadmap: mainnet + perpetual exchange launch.00:27:45 – Lessons learned: move fast, stay adaptive.00:30:00 – Community ask: engage with the Nexus ecosystem.Connect with Nexus and Daniel hereDisclaimer:- Nothing mentioned in this podcast is investment advice and please do your own research.It would mean a lot if you can leave a review of this podcast on Apple Podcasts or Spotify and share this podcast with a friend.Be a guest on the podcast or contact us – https://www.web3pod.xyz/
Radar processes billions of location events daily, powering geofencing and location APIs for companies like Uber, Lyft, and thousands of other apps. When their existing infrastructure started hitting performance and cost limits, they built HorizonDB, a specialized database which replaced both Elasticsearch and MongoDB with a custom single binary written in Rust and backed by RocksDB.In this episode, we dive deep into the technical journey from prototype to production. We talk about RocksDB internals, finite-state transducers, the intricacies of geospatial indexing with Hilbert curves, and why Rust's type system and performance characteristics made it the perfect choice for rewriting critical infrastructure that processes location data at massive scale.
In this episode, Jeff Mains sits down with Luv Kapur, a technology leader at Bit who's reshaping how enterprises build software. Luv shares his journey from leading platform engineering at one of Canada's largest pension funds to joining a startup on a mission to help organizations scale development through composability and AI-powered tools.The conversation explores how AI is fundamentally changing software development—not by writing more code, but by enabling teams to compose better solutions with less custom code. Luv challenges the hype around code generation, arguing that the real bottleneck isn't writing code but translating business requirements into sound architecture and reusing battle-tested components.Luv also offers a grounded perspective on AI's impact on jobs, the importance of discoverability in component libraries, and practical advice for CTOs building composable organizations.Key Takeaways[0:00] - Episode introduction: AI-powered, cloud-native enterprise development tools[1:00] - The hidden cost of poor discoverability in internal libraries and how it silently slows high-performing teams[4:26] - Luv's background: From leading platform engineering at Healthcare of Ontario Pension Plan to joining Bit[4:47] - The spark for the leap: Believing in the mission of helping enterprises scale development globally[5:19] - The consistency problem: When products span multiple teams but feel disjointed to users[6:37] - Building a platform team whose customers are developers themselves[7:23] - Discoverability as the key problem: Developers couldn't find what already existed[9:24] - Why inner source software transforms development artifacts into invaluable organizational assets[11:37] - Viewing your org chart as a dependency graph, not a hierarchy[15:51] - The AI hype is justified, but code generation isn't the real bottleneck[17:01] - The bottleneck is translating business requirements into software architecture, not writing code[18:41] - AI should help us do less work, not more work[19:27] - Why developers won't lose jobs: There's infinite work, not finite work[20:19] - Reusing battle-tested components increases quality and reduces surface area for errors[21:59] - Reducing AI context to dependency graphs and APIs prevents hallucinations[23:05] - Private enterprise data is the gold mine for AI value[24:35] - The rise of citizen developers: Non-technical people building with natural language[26:40] - Empowering citizen developers with internal component marketplaces[27:19] - How AI changes the build vs. buy equation through faster prototyping[30:09] - Internal tools will be hit hardest by AI disruption[34:41] - SaaS companies must align with core business value to stay sticky[36:19] - The biggest mistake: Equating vibe-engineered solutions with production-ready software[39:01] - Building AI muscle: Start with clear scoped goals, not vague initiatives[40:45] - The future: Higher skill ceiling, elimination of junior developer roles, but more opportunities overall[43:45] - Junior developers must contribute to open source and build visible impact[44:31] - The one capability every software leader needs: Willingness to adopt AI and keep learningTweetable Quotes"For an internal team, if it doesn't get adopted, it's useless. Adoption is key." - Luv...
Software Engineering Radio - The Podcast for Professional Software Developers
Derick Schaefer, author of CLI: A Practical Guide to Creating Modern Command-Line Interfaces, talks with host Robert Blumen about command-line interfaces old and new. Starting with a short review of the origin of commands in the early unix systems, they trace the evolution of commands into modern CLIs. Following the historic rise, fall, and re-emergence of CLIs, they consider innovative examples such as git, github, WordPress, and warp. Schaefer clarifies whether commands are the same as CLIs and then discusses a range of topics, including implementation languages, packages in the golang ecosystem for CLI development, CLIs and APIs, CLIs and AIs, AI tooling versus MCP, the object-command pattern, command flags, API authentication, whether CLIs should be stateless, and output formats - json, rich text. Brought to you by IEEE Computer Society and IEEE Software magazine.
Have an idea or tip? Send us a text!If your studio juggles spreadsheets, calendars, and three different apps just to run picture day, this conversation will feel like oxygen. The Dead Pixels Society sits down with Scott Rodgers and Peter Koop from Airstudio to unpack how a platform built by school photographers solves the messy middle of volume photography—linking CRM, senior bookings, staff scheduling, payroll, equipment, workflows, and e‑commerce integrations into one place.We start with the pain: Homegrown tools and generic CRMs can't handle the unique layers of school photography—schools as clients, parents as buyers, students as subjects—each with different needs and deadlines. Rodgers and Koop share how Airstudio centralizes everything from first contact and session reminders to school deliverables like PSPA exports and ID specs. With open APIs and data exchanges, it plays well with platforms such as GotPhoto, Captura, and Timestone, so you keep the storefronts you like while unifying the back office. The result is faster coordination, fewer errors, and a clear view of every job.Using a gross contribution model, studios can see what each school truly costs after direct expenses, staffing, and workflow time—often revealing accounts that quietly drain resources. You'll hear candid stories of running P&Ls on every account, cutting unprofitable schools, and seeing margins and morale rise. We also cover flexible senior booking paths for districts that won't sPhoto Imaging CONNECTThe Photo Imaging CONNECT conference, March 1-2, 2026, at the RIO Hotel and Resort in Las Vegas, NMaking Good: Small Business Marketing PodcastMaking Good helps you do better marketing so you can make a bigger impact. If you're...Listen on: Apple Podcasts SpotifyMediaclipMediaclip strives to continuously enhance the user experience while dramatically increasing revenue.Buzzsprout - Let's get your podcast launched!Start for FREEPhoto Imaging CONNECTThe Photo Imaging CONNECT conference, March 1-2, 2026, at the RIO Hotel and Resort in Las Vegas, NDisclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Support the showSign up for the Dead Pixels Society newsletter at http://bit.ly/DeadPixelsSignUp.Contact us at gary@thedeadpixelssociety.comVisit our LinkedIn group, Photo/Digital Imaging Network, and Facebook group, The Dead Pixels Society. Leave a review on Apple and Podchaser. Are you interested in being a guest? Click here for details.Hosted and produced by Gary PageauAnnouncer: Erin Manning
First show of 2026: we talk Garmin Autoland in a King Air and why internet speculation is the fastest way to sound like a jabroni. We also hit the chaos of international ops (Mexico permits/APIS pain) and tease the Chicago Layover Guide dropping soon. In the Mailbag: Coeur d'Alene layover intel, a legendary lav story, Pilot Pete confusion gets cleaned up, airline-switching "sunk cost" drama, and surviving an unhinged sim instructor. Flight Advice is a big one: a 2,000-hr pilot with a baby inbound weighs staying in a single-pilot piston twin 135 gig vs taking a King Air 200 EMS job (and whether a regional/fractional move makes more sense). Luggage Review Series Show Notes 0:00 Intro 4:02 Musings: Training & Self-Landing Planes 28:03 Other Incidents 50:55 Caribbean Airspace Shutdown 56:07 Reviews 1:01:15 Mailbag 1:24:21 Flight Advice Our Sponsors Tim Pope, CFP® — Tim is both a CERTIFIED FINANCIAL PLANNER™ and a pilot. His practice specializes in aviation professionals and aviation 401k plans, helping clients pursue their financial goals by defining them, optimizing resources, and monitoring progress. Click here to learn more. Also check out The Pilot's Portfolio Podcast. Advanced Aircrew Academy — Enables flight operations to fulfill their training needs in the most efficient and affordable way—anywhere, at any time. They provide high-quality training for professional pilots, flight attendants, flight coordinators, maintenance, and line service teams, all delivered via a world-class online system. Click here to learn more. Raven Careers — Helping your career take flight. Raven Careers supports professional pilots with resume prep, interview strategy, and long-term career planning. Whether you're a CFI eyeing your first regional, a captain debating your upgrade path, or a legacy hopeful refining your application, their one-on-one coaching and insider knowledge give you a real advantage. Click here to learn more. The AirComp Calculator™ is business aviation's only online compensation analysis system. It can provide precise compensation ranges for 14 business aviation positions in six aircraft classes at over 50 locations throughout the United States in seconds. Click here to learn more. Vaerus Jet Sales — Vaerus means right, true, and real. Buy or sell an aircraft the right way, with a true partner to make your dream of flight real. Connect with Brooks at Vaerus Jet Sales or learn more about their DC-3 Referral Program. Harvey Watt — Offers the only true Loss of Medical License Insurance available to individuals and small groups. Because Harvey Watt manages most airlines' plans, they can assist you in identifying the right coverage to supplement your airline's plan. Many buy coverage to supplement the loss of retirement benefits while grounded. Click here to learn more. VSL ACE Guide — Your all-in-one pilot training resource. Includes the most up-to-date Airman Certification Standards (ACS) and Practical Test Standards (PTS) for Private, Instrument, Commercial, ATP, CFI, and CFII. 21.Five listeners get a discount on the guide—click here to learn more. ProPilotWorld.com — The premier information and networking resource for professional pilots. Click here to learn more. Feedback & Contact Have feedback, suggestions, or a great aviation story to share? Email us at info@21fivepodcast.com. Check out our Instagram feed @21FivePodcast for more great content (and our collection of aviation license plates). The statements made in this show are our own opinions and do not reflect, nor were they under any direction of any of our employers.
In this episode, we dig into how modern SaaS platforms turn payments into a core product, a revenue engine, and a defensible moat without breaking customer trust or slowing product velocity. With NMI's CMO Peter Galvin and Product Director Luis Peña, we unpack the real path from “just accept cards” to a fully integrated commerce stack that handles fraud, chargebacks, compliance, and omnichannel experiences at scale.We start with the SaaS payments maturity curve: ship fast with basic acceptance, then refine UX with tokenization and branded flows, and finally operate payments as a true business line with pricing strategy and revenue share. From there, we explore the tough stuff most teams underestimate - risk management, underwriting discipline, and the operational muscle needed to keep approval rates high while keeping losses and support tickets low. If you're wondering when you've outgrown your current processor, we outline the telltale signs and how to plan a migration that is modular, phased, and invisible to your merchants.Omnichannel is also a major focus. We break down card-present choices like Tap to Pay, offline-capable devices for field service, and cloud APIs for always-connected point of sale - all while tying in text-to-pay, QR codes, wallets, and ACH via open banking. Beyond lending, we also highlight high-impact add-ons: instant payouts, network tokenization, invoicing, and loyalty programs that raise approval rates, reduce churn, and boost margin. And we look ahead at what's next: stablecoins for cross-border efficiency, open banking data for smoother experiences, and agent-driven discovery that transforms how buyers find and pay for products.
Introducing Rob Ruiz Meet Rob Ruiz, a seasoned Senior Full Stack Developer with nearly two decades of expertise in WordPress innovation and open-source magic. As the Lead Maintainer of WP Rig since 2020, Rob has been the driving force behind this groundbreaking open-source framework that empowers developers to craft high-performance, accessible, and progressively enhanced WordPress themes with ease. WP Rig isn’t just a starter theme—it’s a turbocharged toolkit that bundles modern build processes, linting, optimization, and testing to deliver lightning-fast, standards-compliant sites that shine on any device. Show Notes For more on Rob and WP Rig, check out these links: LinkedIn Profile: https://www.linkedin.com/in/robcruiz WP Rig Official Site: https://wprig.io GitHub Repository: https://github.com/wprig/wprig Latest Releases: https://github.com/wprig/wprig/releases WP Rig 3.1 Announcement: https://wprig.io/wp-rig-3-1/ Transcript: Topher DeRosia: Hey everybody. Welcome to Hallway Chats. I’m your host Topher DeRosia, and with me today I have- Rob Ruiz: Rob Ruiz. Topher: Rob. You and I have talked a couple of times, once recently, and I learned about a project you’re working on, but not a whole lot about you. Where do you live? What do you do for a living? Rob: Yeah, for sure. Good question. Although I’m originally from Orlando, Florida, I’ve been living in Omaha, Nebraska for a couple of decades now. So I’m pretty much a native. I know a lot of people around here and I’ve been fairly involved in various local communities over the years. I’m a web developer. Started off as a graphic designer kind of out of college, and then got interested in web stuff. And so as a graphic designer turned future web developer, I guess, I was very interested in content management systems because it made the creating and managing of websites very, very easy. My first couple of sites were Flash websites, sites with macro media Flash. Then once I found content management systems, I was like, “Wow, this is way easier than coding the whole thing from scratch with Flash.” And then all the other obvious benefits that come from that. So I originally started with Joomla, interestingly enough, and used Joomla for about two or three years, then found WordPress and never looked back. And so I’ve been using WordPress ever since. As the years have gone on, WordPress has enabled me to slowly transition from a more kind of web designer, I guess, to a very full-blown web developer and software engineer, and even software architect to some degree. So here we are many years later. Topher: There’s a big step from designer to developer. How did that go for you? I’m assuming you went to PHP. Although if you were doing Flash sites, you probably learned ActionScript. Rob: Yeah. Yeah. That was very convenient when I started learning JavaScript. It made it very easy to learn JavaScript faster because I already had a familiarity with ActionScript. So there’s a lot of similarities there. But yeah. Even before I started doing PHP, I started learning more HTML and CSS. I did do a couple of static websites between there that were just like no content management system at all. So I was able to kind of sharpen my sword there with the CSS and HTML, which wasn’t particularly hard. But yeah, definitely, the PHP… that was a big step was PHP because it’s a proper logical programming language. There was a lot there I needed to unpack, and so it took me a while. I had to stick to it and really rinse and repeat before I finally got my feet under me. Topher: I can imagine. All right. So then you work for yourself or you freelance or do you have a real job, as it were? Rob: Currently, I do have a real job. Currently, I’m working at a company called Bold Orange out of Minneapolis. They’re a web agency. But I kind of bounce around from a lot of different jobs. And then, yes, I do freelance on the side, and I also develop my own products as well for myself and my company. Topher: Cool. Bold Orange sounds familiar. Who owns that? Rob: To be honest, I don’t know who the owners are. It’s just a pretty big web agency out of Minneapolis. They are a big company. You could just look them up at boldorange.com. They work for some pretty big companies. Topher: Cool. All right. You and I talked last about WP Rig. Give me a little background on where that came from and how you got it. Rob: Yeah, for sure. Well, there was a period of time where I was working at a company called Proxy Bid that is in the auction industry, and they had a product or a service — I don’t know how you want to look at that —called Auction Services. That product is basically just building WordPress sites for auction companies. They tasked us with a way to kind of standardize those websites essentially. And what we realized is that picking a different theme for every single site made things difficult to manage and increase tech debt by a lot. So what we were tasked with was, okay, if we’re going to build our own theme that we’re just going to make highly dynamic so we can make it look different from site to site. So we want to build it, but we want to build it smart and we want to make it reusable and maintainable. So let’s find a good framework to build this on so that we can maintain coding standards and end up with as little tech debt as possible, essentially. That’s when I first discovered WP Rig. In my research, I came across it and others. We came across Roots Sage and some of the other big names, I guess. It was actually a team exercise. We all went out and looked for different ones and studied different ones and mine that I found was WP Rig. And I was extremely interested in that one over the other ones. Interestingly enough- Topher: Can you tell me why over the other ones? Rob: That’s a great question. Yeah. I really liked the design patterns. I really liked the focus on WordPress coding standards. So having a system built in that checked all the code against WordPress coding standards was cool. I loved the compiling transpiling, whatever, for CSS and JavaScript kind of built in. That sounded really, really interesting. The fact that there was PHP unit testing built into it. So there’s like a starter testing framework built in that’s easy to extend so that you can add additional unit tests as your theme grows. We really wanted to make sure… because we were very into CICD pipelines. So we wanted to make sure that as developers were adding or contributing to any themes that we built with this, that we could have automated tests run and automated builds run, and just automate as much as possible. So WP rig just seemed like something that gave us those capabilities right out of the box. So that was a big thing. And I loved the way that they did it. Roots Sage does something similar, but they use their blade templating engine built in there. We really wanted to stick to something that was a bit more standard WordPress so that there wasn’t like a large knowledge overhead so that we didn’t have to say like, okay, if we’re bringing on other developers, like junior developers work on it, oh, it would be nice if you use Laravel too because we use this templating engine in all of our themes. We didn’t want to have to worry about that essentially. It was all object-oriented and all that stuff too. That’s what looked interesting to me. We ended up building a theme with WP Rig. I don’t know what they ended up doing with it after that, because I ended up getting let go shortly thereafter because the company had recently been acquired. Also, this was right after COVID too. So there was just a lot of moving parts and changing things at the time. So I ended up getting let go. But literally a week after I got let go, I came across a post on WP Tavern about how this framework was looking for new maintainers. Basically, this was a call put out by Morton, the original author of WP Rig. He reached out to WP Tavern and said, “Look, we’re not interested in maintaining this thing anymore, but it’s pretty cool. We like what we’ve built. And so we’re looking for other people to come in and adopt it essentially.” So I joined a Zoom meeting with a handful of other individuals that were also interested in this whole endeavor, and Morton reached out to me after the call and basically just said, “I looked you up. I liked some of the input that you had during the meeting. Let’s talk a little bit more.” And then that eventually led to conversations about me essentially taking the whole project over entirely. So, the branding, the hosting of the website, being lead maintainer on the project. Basically, gave me the keys to the kingdom in terms of GitHub and everything. So that’s how it ended up going in terms of the handoff between Morton and I. And I’m very grateful to him. They really created something super cool and I was honored to take it over and kind of, I don’t know, keep it going, I guess. Topher: I would be really curious. I don’t think either of us have the answer. I’d be curious to know how similar that path is to other project handoffs. It’s different from like an acquisition. You didn’t buy a plugin from somebody. It was kind of like vibes, I guess. Rob: It was like vibes. It was very vibey. I guess that’s probably the case in an open source situation. It’s very much an open source project. It’s a community-driven thing. It’s for everybody by everybody. I don’t know if all open source community projects roll like that, but that’s how this one worked out. There was some amount of ownership on Morton’s behalf. He did hire somebody to do the branding for WP Rig and the logo. And then obviously he was paying for stuff like the WPrig.io domain and the hosting through SiteGround and so on and so forth. So, we did have to transfer some of that and I’ve taken over those, I guess, financial burdens, if you want to think of it like that. But I’m totally okay with it. Topher: All right. You sort of mentioned some of the things Rig does, compiling and all that kind of stuff. Can you tell me… we didn’t discuss this before. I’m sitting at my desk and I think I want a website. How long does it take to go from that to looking at WordPress and logging into the admin with Rig? Rob: Okay. Rig is not an environment management system like local- Topher: I’m realizing my mistake. Somebody sends me a design in Figma. How long does it take me to go from that to, I’m not going to say complete because I mean, that’s CSS, but you know, how long does it take me to get to the point where I’m looking at a theme that is mine for the client that I’m going to start converting? Rob: Well, if you’re just looking for a starting point, if you’re just like, okay, how long does it take to get to like, okay, here’s my blank slate and I’m ready to start adopting all of these rules that are set up in Figma or whatever, I mean, you’re looking at maybe 5 minutes, 10 minutes, something like that. It’s pretty automated. You just need some simple knowledge of Git. And then there are some prerequisites to using WP Rig. You do have to have composer installed because we do leverage some Composer packages to some of it, although to be honest, you could probably get away with not using Composer. You just have to be okay with sacrificing some of the tools the WP Rig assumes you’re going to have. And then obviously Node. You have to have Node installed. A lot of our documentation assumes that you have NPM, that you’re using NPM for all your Nodes or your package management. But we did recently introduce support for Bun. And so you can use Bun instead of NPM, which is actually a lot faster and better in many ways. Topher: Okay. A lot of my audience are not developers, users, or light developers, like they’ll download a theme, hack a template, whatever. Is this for them? Am I boring those people right now? Rob: That’s a great question. I mean, and I think this is an interesting dichotomy and paradigm in the WordPress ecosystem, because you’ve got kind of this great divide. At least this is something I’ve noticed in my years in the WordPress community is you have many people that are not coders or developers that are very interested in expanding their knowledge of WordPress, but it’s strictly from a more of a marketing perspective where it’s like, I just want to know how to build websites with WordPress and how to use it to achieve my goals online from a marketing standpoint. You have that group of people, and then you have this other group of people that are very developer centric that want to know how to extend WordPress and how to empower those other people that we just discussed. Right? Topher: Right. Rob: So, yeah, that’s a very good question. I would say that WP Rig is very much designed for the developers, not for the marketers. The assumption there is that you’re going to be doing some amount of coding. Now, can you get away with doing a very light amount of coding? Yes. Yes, you can. I mean, if you compare what you’re going to get out of that assumed workflow to something that you would get off like Theme Forest or whatever, it’s going to be a night and day difference because those theme, Forest Themes, have hours, hundreds, sometimes hundreds of hours of development put into them. So, you’re not going to just out of the box immediately get something that is comparable to that. Topher: You need to put in those hundreds of hours of development to make a theme. Rob: As of today, yes. That may change soon though. Topher: Watch this space. Rob: That’s all I’ll say. Topher: Okay. So now we know who it’s for. I’m assuming there’s a website for it. What is it? Rob: Yeah. If you go to WPrig.io, we have a homepage that shows you all the features that are there in WP Rig. And then there’s a whole documentation area that helps people get up and running with WP Rig because there is a small learning curve there that’s pretty palatable for anybody who’s familiar with modern development workflows. So that is a thing. So the type of person that this is designed for anybody that wants to make a theme for anything. Let’s say you’re a big agency and you pull in a big client and that client wants something extremely custom and they come to you with Figma designs. Sure, you could go out there and find some premium theme and try to like child theme and overhaul that if you want. But in many situations, I would say in most situations, if you’re working from a Figma design that’s not based off of another theme already that’s just kind of somebody else’s brainchild, then you’re probably going to want to start from scratch. And so the idea here is that this is something to replace an approach, like underscores an approach. Actually, WP Pig was based off of underscores. The whole concept of it, as Morton explained it to me, was that he wanted to build an underscores that was more modern and full-featured from a development standpoint. Topher: Does it have any opinions about Gutenberg? Rob: It does now, but it did not when I took it over because Gutenberg did not exist yet when I took over WP Rig. Topher: Okay. What are its opinions? Rob: Yeah, sure. The opinion right out of the gate is that you can use Gutenberg as an editor and it has support like CSS rules in it for the standard blocks. So you should be able to use regular Gutenberg blocks in your theme and they should look just fine. There’s no resets in there. It doesn’t start from scratch. There’s not a bunch of styling you have to do for the blocks necessarily. Now, if you go to the full site editing or block-based mentality here, there are some things you need to do in WP Rig to convert the out-of-the-box WP Rig into another paradigm essentially. Right when you pull WP Rig, the assumption is you’re building what most people would refer to as a hybrid theme. The theme supports API or whatever, and the assumption is that you’re not going to be using the site editor. You’re just going to kind of do traditional WordPress, but you might be using Gutenberg for your content. So you’re just using Gutenberg kind of to author your pages and your posts and stuff like that, but not necessarily the whole site. WP Rig has the ability to kind of transform itself into other paradigms. So the first paradigm we built out was the universal theme approach. And the idea there is that you get a combination of the full site editing capabilities. But then you also have the traditional menu manager and the settings customizer framework or whatever is still there, right? These are things that don’t exist in a standard block-based theme. So I guess an easy example would be like the 2025 WordPress theme that comes right out of the box. It comes installed in WordPress. That is a true block-based theme, not a universal theme. So it doesn’t have those features because the assumption there is that it doesn’t need those features. You can kind of transform WP Rig into a universal theme that’s kind of a hybrid between a block-based and a classic theme. And then it can also transform into a strictly block-based theme as well. So following the same architecture as like the WordPress 2025 theme or Ollie or something like that is also a true block-based theme as well. So you can easily convert or transform the starting point of WP Rig into either of those paradigms if that’s the type of theme you’re setting out to build. Topher: Okay. That sounds super flexible. How much work is it to do that? Rob: It’s like one command line. Previously we had some tutorials on the website that showed you step-by-step, like what you needed to change about the theme to do that. You would have to add some files, delete some files, edit some code, add some theme supports into the base support class and some other stuff. I have recently, as of like a year and a half ago or a year ago, created a command line or a command that you can type into the command line that basically does that entire conversion process for you in like the blink of an eye. It takes probably a second to a second and a half to perform those changes to the code and then you’re good to go. It is best to do that conversion before you start building out your whole theme. It’s not impossible to do it after. But you’re more likely to run into problems or conflicts if you’ve already set out building your whole theme under one paradigm, and then you decide how the project you want to switch over to block-based or whatever. You’re likely to run into the need to refactor a bunch of stuff in that situation. So it is ideal to make that choice extremely early on in the process of developing your theme. But either way it’ll still work. That’s just one of the many tools that exist in WP Rig to transform it or convert it in several ways. That’s just one example. There are other examples of ways that Rig kind of converts itself to other paradigms as well. Topher: Yeah. All right. In my development life, I’ve had two parts to it. And one is the weekend hobbyist, or I download cadence and I whip something up in 20 minutes because I just want to experiment and the other is agency life where everything’s in Git, things are compiled, there are versions, blah, blah, blah. This sounds very friendly to that more professional pathway. Rob: Absolutely. Yes. Or, I mean, there’s another situation here too. If you’re a company who develops themes and publishes them to a platform like ThemeForest or any other platform, perhaps you’re selling themes on your own website, whatever, if you’re making things for sale, there’s no reason you couldn’t use WP Rig to build your themes. We have a bundle process that bundles your theme for publication or publishing. Whether you’re an agency or whether you’re putting your theme out for sale, it doesn’t matter, during that bundle process, it does actually white label the entire code base to where there’s no mention of WP Rig in the code whatsoever. Let’s say you were to build a theme that you wanted to put up for sale because you have some cool ideas. Say, page transitions now are completely supported in all modern or in most modern browsers. And when I say print page transitions, for those that are in the know, I am talking about not single page app page transitions, but through website page transitions. You can now do that. Let’s say you were like, “Hey, I’m feeling ambitious and I want to put out some new theme that comes with these page transitions built in,” and that’s going to be fancy on ThemeForest when people look at my demo, people might want to buy that. You could totally use WP Rig to build that out into a theme and the bundle process will white label all of the code. And then when people buy your theme and download that code, if they’re starting to go through and look through your code, they’re not going to have any way of knowing that it was built with WP Rig unless they’re familiar with the base WP Rig architecture, like how it does its object-oriented programming. It might be familiar with the patterns that it’s using and be able to kind of discern like, okay, well, this is the same pattern WP Rig uses, so high likelihood it was built with WP Rig. But they’re not going to be able to know by reading through the code. It’s not going to say WP Rig everywhere. It’s going to have the theme all over the place in the code. Topher: Okay. So then is that still WP Rig code? It just changed its labels? Rob: Yeah. Topher: So, it’s not like you’re exporting HTML, CSS and JavaScript? The underlying Rig framework is still there. Rob: Yeah. During the bundle process, it is bundling CSS and HTML. Well, HTML in the case of a block-based theme. But, yeah, it is bundling your PHP, your CSS, your JavaScript into the theme that you’re going to let people download when they buy it, or that you’re going to ship to your whatever client’s website. But all that code is going to be transpiled. In the case of CSS and JavaScript, there’s only going to be minified versions of that code in that theme. The source code is not actually going to be in there. Topher: This sounds pretty cool. You mentioned some stuff might be coming. You don’t have to tell me what it is, but do you have a timeline? When should we be watching for the next cool thing from Rig? Rob: Okay, cool. Well, I’m going to keep iterating on Rig forever. Regardless of any future products that might be built on WP Rig, WP Rig will always and forever remain an open source product for anybody to use for free and we, I, and possibly others in the future will continue to update it and support it over time. We just recently put out 3.1. You could expect the 3.2 anytime in the next six months to a year, probably closer to six months. One feature I’m looking at particularly closely right now is the new stuff coming out in version 6.9 of WordPress around the various APIs that are there. I think one of them is called the form… There’s a field API and a form API or view API or something like that. So WP Rig comes with a React-based settings framework in it. So if you want your theme to have a bunch of settings in it to make it flexible for whoever buys your theme, you can use this settings framework to easily create a bunch of fields, and then that framework will automatically manage all your fields and store all the data from those fields and make it easy to retrieve the values of the input on those fields, without knowing any React at all. Now, if you know React, you can go in there and, you know, embellish what’s already there, but it takes a JSON approach. So if you just understand JSON, you can go in and change the JSON for the framework, and that will automatically add fields into the settings framework. So you don’t even have to know React to extend the settings page if you want. That will likely get an overhaul using these new APIs being introduced into Rig. Topher: All right. How often have you run into something where, “Oh, look, WordPress has a new feature, I need to rebuild my system”? Rob: Over the last four or five years, it’s happened a lot because, yeah, I mean, like I said, when I first took this thing over, Gutenberg had not even been introduced yet. So, you had the introduction of Gutenberg and blocks. That was one thing. Then this whole full site editing became a thing, which later became the site editor. So that became a whole thing. Then all these various APIs. I mean, it happens quite frequently. So I’ve been working to keep it modern and up to date over the past four years and it’s been an incredible learning experience. It not only keeps my WordPress knowledge extremely sharp, but I’ve also learned how various other toolkits are built. That’s been the interesting thing. From a development standpoint, there’s two challenges here. One of the challenges is staying modern on the WordPress side of things. For instance, WordPress coding standards came out with a version 3 and then a version 3.1 about two years ago. I had to update WP Rig to leverage those modern coding standards. So that’s one example is as WordPress changes, the code in WP Rig also needs to change. Or for instance, if new CSS standards change, right, new CSS properties come out, it is ideal for the base CSS in WP Rig, meaning the CSS that you get right out of the box with it, comes with some of these, for instance, CSS grid, Flexbox, stuff like that. If I was adopting a theme framework to build a theme on, I would expect some of that stuff to be in there. And those things were extremely new when I first took over WP Rig and were not all baked in there essentially. So I’ve had to add a lot of that over time. Now there’s another side to this, which is not just keeping up with WordPress and CSS and PHP, 8. whatever, yada yada yada. You’ve also got the toolkit. There are various node packages and composer packages of power WP Rig and the process in which it does the transpiling, the bundling, the automated manipulation of your code during various aspects of the usage of WP Rig is a whole nother set of challenges because now you have to learn concepts like, well, how do I write custom node scripts? Right? Like there were no WP CLI commands built into WP Rig when I first took it over. Now there’s a whole list. There’s a whole library of WP CLI commands that come in Rig right out of the gate. And so I’ve had to learn about that. So just various things that come with knowing how do you automate the process of converting code, that’s something that was completely foreign to me when I first took over WP Rig. That’s been another incredible learning experience is understanding like what’s the difference between Webpack and Gulp. I didn’t know, right? I would tell people I’m using Gulp and WP Rig and they would be like, “Well, why don’t you just use Webpack?” and I would say, “I don’t know. I don’t know what the difference is.” So over time I could figure out what are the differences? Why aren’t we using Webpack? And I’m glad I spent some time on that because it turns out Webpack is not the hottest thing anymore, so I just skipped right over all that. When I overhauled for version 3, we’re now not using Gulp anymore as of 3.1. We’re now using more of a Vite-like process, far more modern than Webpack and far better and faster and sleeker and lighter. I had to learn a bunch about what powers Vite. What is Vite doing under the hood that we might be able to also do in WP Rig, but do it in a WordPress way. Because Vite is a SaaS tool. If you’re building a SaaS, like React with a… we’re not a SaaS. I guess a spa is a better term to use here. If you’re building a single page application with React or view or belt or whatever, right, then knowing what Vite is and just using Vite right out of the box is perfect. But it doesn’t translate perfectly to WordPress land because WordPress has its own opinions. And so I did have to do some dissecting there and figure out what to keep and what to not keep to what to kind of set aside so that WordPress can keep doing what WordPress does the way WordPress likes to do it, but also improve on how we’re doing some of the compiling and transpiling and the manipulation of the code during these various. Topher: All right. I want to pivot a little bit to some personal-ish questions. Rob: Okay. Topher: This is a big project. I’m sure it takes up plenty of your time. How scalable is that in your life? Do you want to do this for the rest of your life? Rob: That’s a fantastic question. I don’t know about the rest of my life. I mean, I definitely want to do web development for the rest of my life because the web has, let’s be honest, it’s transformed everyone’s way of life, whether you’re a web developer or not. You know, the fact that we have the internet in our pocket now, you know, it has changed everything. Apps, everything. It’s all built on the web. So I certainly want to be involved in the web the rest of my life. Do I want to keep doing WordPress the rest of my life? I don’t know. Do I want to keep doing WP Rig the rest of my life? I don’t know. But I will say that you bring up a very interesting point, which is it does take up a lot of time and also trust in open source over the past four or five years I would argue has diminished a little bit as a result of various events that have occurred over the past two or three years. I mean, we could cite the whole WP Engine Matt Mullerwig thing. We can also cite what’s going on with Oracle and JavaScript. Well, I mean, there’s many examples of this. I mean, we can cite the whole thing that happened… I mean, there’s various packages out there that are used and developed and open source to anybody, and some of them are going on maintained and it’s causing security vulnerabilities and degradation and all this stuff. So it’s a very important point. One thing I started thinking about after considering that in relation to WP Rig was I noticed that there’s usually a for-profit arm of any of these frameworks that seems to extend the lifespan of it. Let’s just talk about React, for example, React is an open source JavaScript framework, but it’s used by Facebook and Facebook is extremely for-profit. So companies that are making infrastructural or architectural decisions, they will base their choice on whether or not to use a framework largely on how long they think this framework is going to remain relevant or valid or maintained, right? A large part of that is, well, is there a company making money off of this thing? Because if there is, the chances- Topher: They’re going to keep doing that. Rob: They’re going to keep doing it. It’s going to stay around. That’s good. I think that’s healthy. A lot of people that like open source and want everything to be free, they might look at something like that and say like, well, I don’t want you to make a paid version of it or there shouldn’t be a pro version. I think that’s a very short-sighted way of looking at that software and these innovations. I think a more experienced way of looking at it is if you want something to remain relevant and maintained for a long period of time, having a for-profit way in which it’s leveraged is a very good thing. I mean, let’s be real. Would WordPress still be what it is today if there wasn’t a wordpress.com or if WooCommerce wasn’t owned by Automattic or whatever, right? They’ll be on top. I mean, it’s obviously impossible to say, but my argument would be, probably not. I mean, look at what’s happened to the other content management systems out there. You know, Joomla Drupal. They don’t really have a flourishing, you know, paid pro service that goes with their thing that’s very popular, at least definitely not as popular as WordPress.com or WordPress VIP or some of these other things that exist out there. And so having something that’s making and generating money that can then contribute back into it the way Automattic has been doing with WordPress over these years has, in my opinion, been instrumental. I mean, people can talk smack about Gutenberg all they want, but let’s be real, it’s 2025, would you still feel that WordPress is an elegant solution if we were still working from the WYSIWYG and using the classic editor? And I know a lot of people are still using the classic editor and there’s classic for us, the fork and all that stuff. But I mean, that only makes sense in a very specific implementation of WordPress, a very specific paradigm. If you want to explore any of these other paradigms out there, that way of thinking about WordPress kind of falls apart pretty quickly. I, for one, am happy that Gutenberg exists. I’m very happy that Automattic continues. And I’m grateful, actually, that Automattic continues to contribute back into WordPress. And not just them, obviously there’s other companies, XWP, 10Up, all these other companies are also contributing as well. But I’m very grateful that this ecosystem exists and that there’s contribution going back in and it’s happening from companies that are making money with this. And I think that’s vital. All that to say that WP Rig may and likely will have paid products in the future that leverage WP Rig. So that’s not to say that WP Rig will eventually cost money. That’s just to say that eventually people can expect other products to come out in the future that will be built on WP Rig and incentivize the continued contributions back into WP Rig. The open source version of WP Rig. Topher: That’s cool. I think that’s wise. If you want anything to stay alive, you have to feed it. Rob: That’s right. Topher: I had some more questions but I had forgotten them because I got caught up in your answer. Rob: Oh, thank you. I’ll take that as a compliment. I mean, my answer was eloquent. But I’m happy to expand on anything, know you, WordPress related, me related, you know, whether it comes to the ecosystem in WordPress, the whole WordCamp meetup thing is very interesting. I led the WP Omaha meetup for many years here in Omaha, Nebraska and I also led the WordCamp, the organizing of WordCamp here in Omaha for several years as well. That whole community, the whole ecosystem, at least in America seems to have largely fallen apart. I don’t know if you want to talk about that at all. But yeah, I’m ready to dive into any topics. Topher: I’m going to have one more question and then we’re going to wrap up. And it was that you were talking about all the things you had to learn. I’m sure there were nights where you were looking at your computer thinking, “Oh man, I had it working, now I gotta go learn a new thing.” I would love for you to go back in time and blog all of that if you would. But given that you can’t, I would be interested in a blog moving forward, documenting what you’re learning, how you’re learning it and starting maybe with a post that’s summarizes all of that. Obviously, that’s up to you and how you want to spend your time, but I think it’d be really valuable to other people starting a project, picking up somebody else’s project to see what the roadmap might look like. You know what I mean? Rob: For sure. Well, I can briefly summarize what I’ve learned over the years and where I’m at today with how I do this kind of stuff. I will say that a lot of the improvements to WP Rig that have happened over the last year or two would not be possible without the advent of AI. Topher: Interesting. Rob: That’s a fancy way of saying that I have been by coding a lot of WP Rig lately. If you know how to use AI, it is extremely powerful and it can help you do many things very quickly that previously would have taken much longer or more manpower. So, yeah, perhaps if there was like five, six, seven people actively, excuse me, actively contributing to WP Rig, then this type of stuff would have been possible previously, but that’s not the case. There is one person, well, one main contributor to WP Rig today and you’re talking to them. There are a handful of other people that have been likely contributing to WP Rig over the versions and you can find their contributions in the change log file in WP Rig. But those contributions have been extremely light compared to what I’ve been doing. I wouldn’t be able to do any of it without AI. I have learned my ability to learn things extremely rapidly has ramped up tenfold since I started learning how to properly leverage LLMs and AI. So that’s not to say that like, you know, WP Rig, all the code is just being completely written by AI and I’m just like. make it better, enter, and then like WP Rig is better. I wish it was that easy. It’s certainly not that. But when I needed to start asking some of these vital questions that I really didn’t have anyone to turn to to help answer them, I was able to turn to AI. For instance, let’s go back to the Webpack versus Gulp situation. Although Gulp is no longer used in WP Rig, you know, it was used in WP Rig until very recently. So I had to understand like, what is this system, how does it work, how do I extend it and how do I update it and all these things, right? And why aren’t we using WebPack and you know, is there validity to this criticism behind you should use webpack instead of Gulp or whatever, right? I was able to use AI to ask these questions and be able to get extremely good answers out of it and give me the direction I needed to make some of these kind of higher level decisions on like architecturally where should WP Rig go? It was through these virtual conversations with LLMs that I was able to refine the direction of WP Rig in a direction that is both modern and forward-thinking and architecturally sound. I learned a tremendous amount from AI about the architecture, about the code, about all of it. My advice to anybody that wants to extend their skill set a little bit in the development side of things is to leverage this new thing that we have in a way that is as productive as possible for you. So that’s going to vary from person to person. But for me, if I’m on a flight or if I’m stuck somewhere for a while, like, let’s say I got to take my kid to practice or something and I’m stuck there for an hour and I got to find some way to kill my time 9 times out of 10, I’m on my laptop or on my phone having conversations with Grok or ChatGPT or Gemini or whatever. I am literally refining… I’m just sitting there asking it questions that are on my mind that I wish I could ask somebody who’s like 10 times more capable than me. It has been instrumental. WP Rig wouldn’t be where it is today if it wasn’t for that. I would just say to anybody, especially now that it’s all on apps and you don’t have to be on a browser anymore, adopt that way of thinking. You know, if you’re on your lunch break or whatever and you have an hour lunch break and you only take 15 minutes to eat, what could you be doing with those other 45 minutes? You could just jump on this magical thing that we have now and start probing it for questions. Like, Hey, here’s what I know. Here’s what I don’t know. Fill these knowledge gaps for me.” And it is extremely good at doing that. Topher: So my question was, can you blog this and your answer told me that there’s more there that I want to hear. That’s the stuff that should be in your book when you write your book. Rob: I’m flattered that you would be interested in reading anything that I write. So thank you. I’ve written stuff in the past and it hasn’t gotten a lot of attention. But I also don’t have any platforms to market it either. But yeah, no, I made some… I’m sorry. Topher: I think your experience is valuable far beyond Rig or WordPress. If you abstract it out of a particular project to say, you know, I did this with a project, I learned this this way, I think that would be super valuable. Rob: Well, I will say that recently at my current job, I was challenged to create an end to end testing framework with Playwright that would speed up how long it takes to test things and also prevent, you know, to make things fail earlier, essentially, to prevent broken things from ending up in the wild, right, and having to catch them the hard way. I didn’t know a lot about Playwright, but I do know how toolkits work now because of WP Rig. And I was able to successfully in a matter of, I don’t know, three days, put together a starter kit for a test framework that we’re already using at work to test any website that we create for any client. It can be extended and it can be hooked into any CI CD pipeline and it generates reports for you and it does a whole bunch of stuff. I was able to do this relatively quickly. This knowledge, yes, does come in handy in other situations. Will I end up developing other toolkits like WP Rig in the future for other things? I guess if I can give any advice to anybody listening out there, another piece of advice I would give people is, you know, especially if you’re a junior developer and you’re still learning or whatever, or you’re just a marketing person and just want to have more control over the functionality side of what you’re creating or more insight into that so you could better, you know, manage projects or whatever. My advice would be to take on a small little project that is scoped relatively small that’s not too much for you to chew and go build something and do it with… Just doing that will be good. But if you can do it with the intent to then present it in some fashion, whether it be a blog article or creating a YouTube video or going to a meetup and giving a talk on it or even a lunch and learn at work or whatever, right, that will, in my experience, it will dramatically amplify how much you learn from that little pet project that’s kind of like a mini learning experience. And I highly encourage anybody out there to do that on the regular. Actually, no matter what your experience level is in development, I think you should do these things on a regular basis. Topher: All right. I’m going to wrap this up. I got to get back to work. You probably have to get back to work. Rob: Yeah. Topher: Thanks for talking. Rob: Thanks for having me, Topher. Really appreciate it. Topher: Where could people find you? WPrig.io? Rob: Yeah, WPrig.io. WP rig has accounts on all of the major platforms and, even on Bluesky and Mastodon. You can look me up, Rob Ruiz. You can find me on LinkedIn. You can find me on all of those same platforms as well. You can add me on Facebook if you want, whatever. And I’m also in the WordPress Slack as well as Rob Ruiz. You can find me in the WordPress Slack. And then I’m on the WordPress Reddit and all that stuff. So yeah, reach out. If anybody wants to have any questions about Rig or anything else, I’m happy to engage. Topher: Sounds good. All right, I’ll see you. Rob: All right, thanks, Topher. Have a good day. Topher: This has been an episode of the Hallway Chats podcast. I’m your host Topher DeRosia. Many thanks to our sponsor Nexcess. If you’d like to hear more Hallway Chats, please let us know on hallwaychats.com.
What does success look like for HMRC with Making Tax Digital – and what does it really mean for the bookkeepers doing the work on the ground? In this Leadership Takeover Session, Craig Ogilvie, HMRC's Director for Making Tax Digital, explains the “why” behind MTD for Income Tax, how it will change the UK tax system, and why he believes bookkeepers are central to making it work for small businesses. Get step by step guidance on MTD for Income Tax https://www.gov.uk/government/collections/making-tax-digital-for-income-tax?Utm_source=6fb Craig shares his journey from a low-income upbringing in Scotland, through 20+ years in government delivery, to leading some of the UK's biggest programmes – including the furlough scheme during the pandemic. He explains how his parents' values around kindness and optimism shaped his leadership style, why he focuses so heavily on people and psychological safety, and how that translates into the way he runs the MTD team today. You'll hear a clear, human explanation of what MTD for IT actually is: digital record keeping, quarterly updates and software-based filing for millions of self-employed people. Craig talks about the three big reasons behind it – reducing errors in the tax gap, modernising the UK's tax infrastructure, and creating better customer service through more timely data and nudges – and why he sees bookkeepers as uniquely placed to turn that into better conversations about cash flow, credit control and business performance. He also explains the scale of the change: rebuilding core systems, working with third-party software through APIs, and designing multiple agent functionality so both accountants and bookkeepers can support the same client. Craig describes travelling around the UK to meet real practices, how those conversations led to changes like faster sign-up journeys and multiple agent access, and why HMRC is committed to genuine co-creation rather than “rubber-stamping” decisions already made. The episode goes deeper into social mobility, confidence and financial understanding. Craig talks about seeing his dad's January “bag of receipts”, the construction sector's heavy representation in the first MTD cohort, and the financial literacy gap facing many sole traders. He reflects on sessions with unrepresented business owners, where a clear explanation – often from a bookkeeper or accountant – can quickly change how someone feels about digital tools, quarterly reporting and understanding their numbers. ----------------------------------------------- About us We're Jo and Zoe and we help bookkeepers find clients, make more money and build profitable businesses they love. Find out about working with us in The Bookkeepers' Collective, at: 6figurebookkeeper.com/collective ----------------------------------------------- About our Sponsor This episode of The Bookkeepers' Podcast is sponsored by Xero. Get 90% off your first 6 months by visiting: https://xero5440.partnerlinks.io/6figurebookkeeper ----------------------------------------------- Promotion This video contains paid promotion. ----------------------------------------------- Disclaimer The information contained in The Bookkeepers' Podcast is provided for information purposes only. The contents of The Bookkeepers' Podcast is not intended to amount to advice and you should not rely on any of the contents of the Bookkeepers' Podcast. Professional advice should be obtained before taking or refraining from taking any action as a result of the contents of the Bookkeepers' Podcast. The 6 Figure Bookkeeper Ltd disclaims all liability and responsibility arising from any reliance placed on any of the contents of the Bookkeepers' Podcast.
How is artificial intelligence transforming the way businesses operate? Can cutting-edge technology be the key to scaling success? In this episode, Ephraim Ebstein, Founder and CEO of Fit Solutions, sits down to share his insights… Fit Solutions is a $30 million IT and cybersecurity firm that helps thousands of businesses increase efficiency, reduce IT costs, and protect against cyber threats. Ephraim is also the Co-Founder of AI Integrators, a venture focused on leveraging AI to streamline business operations and optimize performance. With over 15 years in the tech industry, Ephraim has a background in managed IT services, network engineering, and cybersecurity consulting. Before founding Fit Solutions, he served as Senior Systems Engineering Team Lead at All Covered, a division of Konica Minolta. He holds a Bachelor's degree in Management Information Systems and has a proven track record in scaling tech businesses while fostering a strong company culture. In this discussion, we cover: The difference between an enterprise and a medium-sized business. How AI "employees" are transforming customer service and operational efficiency. Why company culture and leadership systems are essential to business growth. How AI and automation are reducing costs while driving revenue. Find out more about Fit Solutions and their AI initiatives by visiting their website!
In this episode, Anderson Business Advisors host Clint Coons, Esq., sits down with Brian Hanson, co-founder of Real Advisors and AI for Business, to explore how artificial intelligence is revolutionizing real estate investing. Brian, who has been teaching business owners and investors about AI and marketing for several years, shares how investors can use AI to crunch massive amounts of data in seconds to identify the most predictable houses likely to sell — something that used to cost $20,000+ from data scientists. They discuss using humanized chatbots and voice bots that can have thousands of personalized conversations simultaneously without sounding robotic, automating follow-up sequences that never miss opportunities, and building custom apps in under five minutes without any coding knowledge. Brian reveals specific tools like Rest Bag for analyzing repair costs at 10 cents per photo, Yellow Pages Scraper for building 20,000-person cash buyer lists for just $80, and browser-use.com for creating custom APIs by simply showing the system what you do manually. As Brian explains, "I just don't think that most people really realize what's possible out there." The conversation covers everything from data mining and lead generation to creating high-converting marketing campaigns using competitive intelligence, virtual staging, and automation tools like Lovable, Google's AI Studio, Air DNA, House Canary, and Semrush. Tune in to discover how AI is the ultimate force multiplier for real estate investors looking to scale their businesses efficiently! Brian Hanson is the co-founder of Real Advisors and AI for Business. He got his start in real estate in his early 20s working with renowned real estate educator Ron LeGrand, where he developed a passion for marketing. Over the years, Brian has become obsessed with finding smarter, faster ways to grow businesses, and when AI emerged, he immediately recognized its transformative potential. Brian now teaches business owners and investors how to leverage AI to dramatically scale their operations, reduce costs, and increase output. He hosts the AI for Business podcast and regularly conducts three-day intensive training events where he shares cutting-edge AI strategies and tools. Brian's approach focuses on practical implementation—helping entrepreneurs automate processes, eliminate roadblocks, and achieve results they never thought possible. Highlights/Topics: (00:00) - Brian Hanson and the AI Opportunity (05:23) - Finding Off-Market Deals: Data Crunching and Lead Generation (11:35) - Automating Follow-Up and Conversations with AI (17:24) - Property Analysis, Contracts, and What AI Can't Replace (25:19) - Building Custom Apps in Minutes Without Coding (30:13) - AI-Powered Marketing and Competitive Intelligence (33:17) - Where to Learn More and Final Thoughts Resources: https://podcasts.apple.com/ke/podcast/ai-for-business-podcast/id1821570230 https://www.linkedin.com/in/brian-hanson-1548797 https://www.facebook.com/brian.hanson1?mibextid=LQQJ4d https://events.aiforbusiness.com/ Schedule Your FREE Consultation https://andersonadvisors.com/strategy-session/?utm_source=ai-for-real-estate-investing&utm_medium=podcast Tax and Asset Protection Events https://andersonadvisors.com/real-estate-asset-protection-workshop-training/?utm_source=ai-for-real-estate-investing&utm_medium=podcast Anderson Advisors https://andersonadvisors.com/ Anderson Advisors Podcast https://andersonadvisors.com/podcast/ Clint Coons YouTube https://www.youtube.com/channel/UC5GX-U6VbvMkhSM1ONBiW8w Anderson Advisors Tax Planning Appointment https://andersonadvisors.com/ss/
professorjrod@gmail.comWhat if the scariest hacks of 2025 never looked like hacks at all? We break down five real-world scenarios where attackers didn't smash locks—they used the keys we handed them. From an AI-cloned voice that sailed through a wire transfer to a building's HVAC console that quietly held elevators and doors hostage, the common thread is hard to ignore: trust. Trusted voices, trusted vendors, trusted “boring” systems, trusted sessions, and trusted APIs became the most valuable attack surface of the year.We start with a “boring” phone call that proves how caller ID and confidence can defeat policy when culture doesn't empower people to challenge authority. Then we step into the mechanical room: cloud dashboards for HVAC and badge readers, vendor-shared credentials, and thin network segmentation made physical denial of service as simple as logging in. The pivot continues somewhere few teams watch—libraries—where an unpatched management system bridged city HR, school portals, and public access with zero alarms, because nothing looked broken.Authentication takes a hit next. MFA worked, yet attackers won by stealing active LMS session tokens from a neglected component and riding valid access for weeks. No failed logins, no brute force—just continuation that our tools rarely question. Finally, we open the mobile app and watch the traffic. Clean, well-formed API calls mapped pricing rules, loyalty balances, and inventory signals at scale. Not a single malformed request, but plenty of business logic abuse that finance noticed before security did.If you care about cybersecurity, IT operations, or the CompTIA mindset, the takeaways are clear: shorten trust windows, verify context continuously, rotate and scope vendor access, segment OT from IT, treat libraries and civic tech as real attack surface, bind tokens to devices, and put rate limits and behavior analytics at the heart of your API strategy. Ready to rethink where your defenses are blind? Listen now, share with your team, and tell us which assumption you'll challenge first. And if this helped, subscribe, leave a review, and pass it on to someone who needs a wake-up call.Support the showArt By Sarah/DesmondMusic by Joakim KarudLittle chacha ProductionsJuan Rodriguez can be reached atTikTok @ProfessorJrodProfessorJRod@gmail.com@Prof_JRodInstagram ProfessorJRod
We revisit how employers can control healthcare spend while expanding employee choice through ICRAs, with Chad Schneider of Thatch sharing what works, what breaks, and what's next. We dig into change management, decision tools, dynamic contributions, and the broker's evolving role.• Why ICRAs surged after 2020 and boomed in 2024• Carrier expansion and a stronger individual market• The real barrier being change management and fintech• Decision support that mirrors travel-style shopping• Dynamic contributions that create equity across markets• Carve-out classes to manage renewals and strategy• Common misconceptions among brokers and employers• Data, APIs, and real-time enrollment tracking• Emerging perks, localized networks, and future trendsPlease feel free to go to our website, which is thatch.com, reach out to me on LinkedIn. I'd love to chat with you, and we can happily go through our process, quoting, show you all the cool bells and whistles, and we'd love to be able to engage further.This episode is sponsored by Benepower, the platform of choice for a modern benefits experience. Benepower is an AI-powered benefits platform offering access to top products and services, enabling consultants and employers to create customized plans, optimize usage, and measure effectiveness. www.benepower.com
The Geek in Review closes 2025 with Greg Lambert and Marlene Gebauer welcoming back Sarah Glassmeyer and Niki Black for round two of the annual scorecard, equal parts receipts, reality check, and forward look into 2026. The conversation opens with a heartfelt remembrance of Kim Stein, a beloved KM community builder whose generosity showed up in conference dinners, happy hours, and day to day support across vendors and firms. With Kim's spirit in mind, the panel steps into the year-end ritual: name the surprises, own the misses, and offer a few grounded bets for what comes next.Last year's thesis predicted a shift from novelty to utility, yet 2025 felt closer to a rolling hype loop. Glassmeyer frames generative AI as a multi-purpose knife dropped on every desk at once, which left many teams unsure where to start, even when budgets already committed. Black brings the data lens: general-purpose gen AI use surged among lawyers, especially solos and small firms, while law firm adoption rose fast compared with earlier waves such as cloud computing, which crawled for years before pandemic pressure moved the needle. The group also flags a new social dynamic, status-driven tool chasing, plus a quiet trend toward business-tier ChatGPT, Gemini, and Claude as practical options for many matters when price tags for legal-only platforms sit out of reach for smaller shops.Hallucinations stay on the agenda, with the panel resisting both extremes: doom posts and fan club hype. Glassmeyer recounts a founder's quip, “hallucinations are a feature, not a bug,” then pivots to an older lesson from KeyCite and Shepard's training: verification never goes away, and lawyers always owed diligence, even before LLMs. Black adds a cautionary tale from recent sanctions, where a lawyer ran the same research through a stack of tools, creating a telephone effect and a document nobody fully controlled. Lambert notes a bright spot from the past six months: legal research outputs improved as vendors paired vector retrieval with legal hierarchy data, including court relationships and citation treatment, reducing off-target answers even while perfection stays out of reach.From there, the conversation turns to mashups across the market. Clio's acquisition of vLex becomes a headline example, raising questions about platform ecosystems, pricing power, and whether law drifts toward an Apple versus Android split. Black predicts integration work across billing, practice management, and research will matter as much as M&A, with general tech giants looming behind the scenes. Glassmeyer cheers broader access for smaller firms, while still warning about consolidation scars from legal publishing history and the risk of feature decay once startups enter corporate layers. The panel lands on a simple preference: interoperability, standards, and clean APIs beat a future where a handful of owners dictate terms.On governance, Black rejects surveillance fantasies and argues for damage control, strong training, and safe experimentation spaces, since shadow usage already happens on personal devices. Gebauer pushes for clearer value stories, and the guests agree early ROI shows up first in back office workflows, with longer-run upside tied to pricing models, AFAs, and buyer pushback on inflated hours. For staying oriented amid fractured social channels, the crew trades resources: AI Law Librarians, Legal Tech Week, Carolyn Elefant's how-to posts, Moonshots, Nate B. Jones, plus Ed Zitron's newsletter for a wider business lens. The crystal ball segment closes with a shared unease around AI finance, a likely shakeout among thinly funded tools, and a reminder to keep the human network strong as 2026 arrives.
In this episode of The Digital Executive, host Brian Thomas speaks with Dr. Ravi Kiran Nizampatnam, an internationally recognized expert in network security and enterprise cybersecurity architecture. With more than a decade of experience protecting mission-critical infrastructure across finance, healthcare, and media, Ravi explains how today's most dangerous attacks no longer look like breaches—but like normal, trusted activity driven by compromised identities, APIs, and supply chains.The conversation dives deep into what Zero Trust done right really means, why treating it as a product instead of an architecture leads to failure, and how organizations can minimize blast radius and contain breaches in minutes rather than months. Ravi also shares the real-world frustrations that inspired his cybersecurity patents, the gaps created by siloed security tools, and why context—not more alerts—is the missing link. Looking ahead, he outlines how AI, cloud-native systems, and regulatory pressure will reshape enterprise security, emphasizing that resilient, identity-centric architecture—not just smarter algorithms—will define the next generation of secure organizations.If you liked what you heard today, please leave us a review - Apple or Spotify. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Today I'm talking with Darragh Buckley, the CEO and co-founder of Increase. If you've been following fintech for a while, you probably know Darragh as employee number one at Stripe, where he built the team responsible for moving money at a massive scale. At Stripe, he learned a crucial lesson about infrastructure: when you're stuck solving business, technical, and risk problems all at once, you need to drop down a layer. That insight led to Increase, which does something quite novel, instead of connecting to banks one by one, they connect directly to the Federal Reserve itself, operating their own banking core that exposes all this functionality through APIs. With a team of less than 20 people, they're now processing over $100 billion annually.In this conversation, we dig into the lessons Darragh learned scaling Stripe, why he believes compliance and accounting should be built into engineering from day one rather than bolted on later, his vision for a future where community banks serve specific communities like dentists or families managing elderly parents' finances, and why he's personally investing in community banks across the Pacific Northwest. We also get into real-time payments infrastructure, including a great story about buying a car on a Saturday. Now let's get on with the show.In the podcast, you will learn:How Increase was born out of early challenges at Stripe.What he learned about scaling fintech companies at Stripe.The advantage of dropping down a layer when building fintech infrastructure.How Increase is able to connect directly to the Federal Reserve.The concept of a side core and how it integrates with banking cores.The different types of companies they work with.A fun story about paying a car dealer with a real time payment on a Saturday.The scale that Increase is at today.Why they decided that now is the time to spread with word about Increase.Why it matters to build compliance into your product very early.What lessons compliance can learn from software engineering.How they are managing real time risk.Why Darragh has personally invested in several community banks.What will have changed in financial services if Increase is successful.Connect with Fintech One-on-One: Tweet me @PeterRenton Connect with me on LinkedIn Find previous Fintech One-on-One episodes
Professor Toby Wilkinson. After their defeat, Antony died in Cleopatra's arms. Cleopatra committed suicide to avoid Roman humiliation, ending the Ptolemaic dynasty. Octavian annexed Egypt, dismissing its religious traditions regarding the Apis Bull and exploiting the land solely as a grain source for the Roman Empire. 1900
Xmas Special: Recovering the Essence of Agile - What's Already Working in Software-Native Organizations In this BONUS Xmas Special episode, we explore what happens when we strip away the certifications and branded frameworks to recover the essential practices that make software development work. Building on Episode 2's exploration of the Project Management Trap, Vasco reveals how the core insights that sparked the Agile revolution remain valid - and how real organizations like Spotify, Amazon, and Etsy embody these principles to thrive in today's software-driven world. The answer isn't to invent something new; it's to amplify what's already working. Agile as an Idea, Not a Brand "The script (sold as the solution) will eventually kill the possibility of the conversation ever happening with any quality." We establish a parallel between good conversations and good software development. Just as creating "The Certified Conversational Method™" with prescribed frameworks and certification levels would miss the point of genuine dialogue, the commodification of agile into Agile™ has obscured its essential truth. The core idea was simple and powerful: build software in small increments, get it in front of real users quickly, learn from their actual behavior, adapt based on what you learn, and repeat continuously. This wasn't revolutionary - it was finally recognizing how software actually works. You can't know if your hypothesis about user needs is correct until users interact with it, so optimize for learning speed, not planning precision. But when the need to certify and validate "doing Agile right" took over, the idea got packaged, and often the package became more important than the principle. Four Fundamental Practices That Enable Living Software "Every deployment was a chance to see how users actually responded." Software-native organizations distinguish themselves through core practices that align with software as a living capability. In this episode, we review four critical ones: First, iterative delivery means shipping the smallest valuable increment possible and building on it - Etsy's transformation from quarterly releases in 2009 to shipping 50+ times per day by 2012 exemplifies this approach, where each small change serves as a learning opportunity. Second, tight feedback loops get software in front of real users as fast as possible, whether through paper prototypes or production deployments. Third, continuous improvement of the process itself creates meta-feedback loops, as demonstrated by Amazon's "You Build It, You Run It" principle introduced by Werner Vogels in 2006, where development teams running their own services in production learn rapidly to write more resilient code. Fourth, product thinking over project thinking organizes teams around long-lived products rather than temporary projects, allowing teams to develop deep expertise and become living capabilities themselves, accumulating knowledge and improving over time. Spotify's Evolutionary Approach "The Spotify model has nothing to do with Spotify really. It was just a snapshot of how that one company worked at the time." Spotify's journey reveals a critical insight often missed in discussions of their famous organizational model. Starting with standard Scrum methodology pre-2012, they adopted the squad model around 2012 with autonomous teams organized into tribes, documented in Henrik Kniberg and Anders Ivarsson's influential white paper (direct PDF link). But post-2016, internal staff and agile coaches noted that the "Spotify model" had become mythology, and the company had moved on from original concepts to address new challenges. As Kniberg himself later reflected, the model has taken on a life of its own, much like Lean's relationship to Toyota. The key insight isn't the specific structure - it's that Spotify treated their own organizational design as a living capability, continuously adapting based on what worked and what didn't rather than implementing "the model" and declaring victory. That's software-native thinking applied to organization design itself. Amazon's Two-Pizza Teams and Massive Scale "Amazon deploys code every 11.7 seconds on average. That's over 7,000 deployments per day across the organization." (see this YouTube video of this talk) Amazon's two-pizza team principle goes far deeper than team size. Teams small enough to be fed with two pizzas (roughly 6-10 people) gain crucial autonomy and ownership: each team owns specific services and APIs, makes their own technical decisions, runs their services in production, and manages inter-team dependencies through APIs rather than meetings. This structure enabled Amazon to scale massively while maintaining speed, as teams could iterate independently without coordinating with dozens of other teams. The staggering deployment frequency - over 7,000 times per day as of 2021 - is only possible with a software-native structure for the company itself, demonstrating that this isn't just about managing software delivery but touches everything, including how teams are organized. Why These Practices Work "These practices work because they align with what software actually is: a living, evolvable capability." The effectiveness of software-native approaches stems from their alignment with software's true nature. Traditional project approaches assume we can know requirements upfront, estimate accurately, build it right the first time, and reach a meaningful "done" state. Software-native approaches recognize that requirements emerge through interaction with users, estimation is less important than rapid learning, "right" is discovered iteratively rather than designed upfront, and "done" only happens when we stop evolving the software. When Etsy ships 50 times per day, they're optimizing for learning where each deployment is a hypothesis test. When Amazon's teams own services end-to-end, they're creating tight feedback loops where teams feel the pain of their own decisions directly. When Spotify continuously evolves their organizational model, they're treating their own structure as software that should adapt to changing needs. The Incomplete Picture and the Question of Universal Adoption "If these approaches work, why aren't they universal?" We're not trying to paint a unrealistically rosy picture - these organizations aren't perfect. Spotify has had well-documented challenges with their model, Amazon's culture has been criticized as demanding and sometimes brutal, and Etsy has gone through multiple strategic shifts. But what matters is that they're practicing software-native development at scale, and it's working well enough that they can compete and thrive. They're not following a playbook perfectly but embodying principles and adapting continuously. This raises the critical question that will be explored in the next episode: if these approaches work, why do so many organizations still operate in project mode, and why do "agile transformations" so often fail to deliver real change? Understanding the resistance - what we call The Organizational Immune System - is essential to overcoming it. References for Further Reading A book on the shift from "projects" to "products": "Project to Product" by Mik Kersten About Vasco Duarte Vasco Duarte is a thought leader in the Agile space, co-founder of Agile Finland, and host of the Scrum Master Toolbox Podcast, which has over 10 million downloads. Author of NoEstimates: How To Measure Project Progress Without Estimating, Vasco is a sought-after speaker and consultant helping organizations embrace Agile practices to achieve business success. You can link with Vasco Duarte on LinkedIn.
From time to time, we'll re-air a previous episode of the show that our newer audience may have missed. During this episode, Santosh is joined by Zach Fredericks, Principal at Primary Venture Partners, an early-stage VC firm that focuses on B2B SaaS, fintech, health, devtools, built world, and supply chain. In this conversation, Santosh and Zach discuss Zach's unexpected entry into supply chain and venture capital, detailing his experiences at Loadsmart and BlackRock. The discussion highlights the pandemic's impact on supply chains, emphasizing the need for resilience and adaptable solutions. Zach underscores the importance of decision intelligence and data interoperability, predicting a shift from EDI to APIs. He also discusses investment trends, advocating for near-shoring and expressing optimism about the trucking industry's future. The episode offers valuable insights into supply chain innovation and investment opportunities and so much more! Highlights from their conversation include:Overview of Primary Ventures (1:17)Zach's Background in Supply Chain (2:42)Macro Thesis from Pandemic Insights (4:46)Surprises in Software Adoption (6:55)Opportunities for Entrepreneurs (9:03)Decision Intelligence Importance (12:07)AI's Role in Supply Chain (14:48)Investment in Lyriq (19:01)Advice for Founders in Supply Chain (22:20)Investment Strategies in Supply Chain (23:48)Business Model Viability (25:01)This or That Segment: (26:27)Final Thoughts and Takeaways (27:05)Dynamo is a VC firm led by supply chain and mobility specialists that focus on seed-stage, enterprise startups.Find out more at: https://www.dynamo.vc/ Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
JavaScript has grown far beyond the browser. It now powers millions of backend systems, APIs, and cloud services through Node.js, which is one of the most widely deployed runtimes on the planet. Keeping such a critical piece of infrastructure fast, secure, and stable is a massive engineering challenge, and the work behind it is often The post Node.js in 2026 with Rafael Gonzaga appeared first on Software Engineering Daily.
Looking for daily inspiration? Get a quote from the top leaders in the industry in your inbox every morning. Every year, millions of attraction visitors lose hours in line instead of making memories. Since its inception, accesso's virtual queuing has saved more than 4.5 billion minutes of wait time, freeing guests to pack their day with more rides, eats, and excitement. The result? Happier guests who spend more and a better bottom line for you. Ready to turn waits into wins? Visit accesso.com/ROIClinic. The queues are virtual. The results are real. Kim Welch is the founder of Welcome Hub. After growing up as an attractions fan, she started at Enchanted Forest Water Safari, learning front gate ticketing, retail, food, and games. She later moved to Orlando, spent years in entertainment at Universal Orlando, then shifted into IT and digital ticketing, becoming a subject matter expert working with marketing and operations. Roles at Universal, Gateway Ticketing Systems, and SSA Group led her to launch Welcome Hub to reimagine how tickets are delivered. In this interview, Kim talks about making digital ticketing better, tickets as a pre-show, and creating unboxing moments. Making digital ticketing better “That's what making it better is all about, is how do we take some of these burdens off of our guests and give them the options they need to make their visit even easier…” For Kim, “better” means removing friction for both guests and teams. She recalls buying tickets at a kiosk, then photographing each printed ticket just to share them with her family because there was no flexible digital option. When guests must invent workarounds like this, the system is failing them. Behind the scenes, she notes, teams juggle separate setups for PDFs, Apple Wallet, Google Wallet, and event tickets, often updating the same content in multiple places. This complexity pushes organizations to scale back branded content even though that weakens the experience. Kim's answer is a unified delivery layer like Welcome Hub that pulls ticket data via APIs and centralizes links, wallets, and messaging so information stays accurate and guest-friendly. Tickets as a pre-show “Coming from entertainment, I have a bit of a flair for the dramatic theatrical. So I always think of the tickets as the pre-show.” Drawing on her entertainment background, Kim argues that tickets should be treated as part of the show, not just a barcode. Just as a pre-show sets story and context, ticket communications can orient guests, answer key questions, and build anticipation long before arrival. She points out that operators invest heavily in onboarding staff, yet rarely design equally thoughtful onboarding for guests. Kim suggests enhancing confirmation emails and ticket pages with brand voice, clear “need-to-know” information, and links that adapt over time. Simple improvements, like structured data that lets email platforms surface trip details, can help guests find what they need quickly. Even small, incremental changes can transform ticketing from a dry transaction into a stage-setting moment. Creating unboxing moments “Why aren't we doing this for attractions that spend multi-millions of dollars on beautiful themed physical spaces? They don't have these other tangible moments pre-visit.” Kim believes attractions are overlooking powerful “unboxing” opportunities. Guests might spend thousands of dollars on a vacation yet receive nothing more than a plain confirmation email or generic ticket. She compares this to retailers and credit card brands that design packaging specifically to be unboxed and shared. She imagines destinations sending pre-visit kits or postcards that tease dining, merchandise, and stories, paired with digital content and QR codes. These touchpoints help guests visualize their spend, plan their visit, and feel excited well before they arrive. Kim also notes that when attractions do not create these moments, influencers and third parties fill the gap with messaging that may not align with the brand. Kim can be reached via email at Kim@welcomehub.org, and more information about her work and Welcome Hub can be found at welcomehub.org, where she shares a manifesto on guest-centric ticketing. She is also active on LinkedIn, and encourages industry professionals to connect, share ideas, and explore small, incremental steps that make digital ticketing and pre-visit engagement better for both guests and operators. This podcast wouldn't be possible without the incredible work of our faaaaaantastic team: Scheduling and correspondence by Kristen Karaliunas To connect with AttractionPros: AttractionPros.com AttractionPros@gmail.com AttractionPros on Facebook AttractionPros on LinkedIn AttractionPros on Instagram AttractionPros on Twitter (X)
Scott and Wes break down the biggest web platform features that reached Baseline in 2025, separating the genuinely useful APIs from the niche and forgettable ones. From same-document view transitions and the Popover API to Promise.try, content-visibility, and modern CSS goodies, they share what's actually ready to use today. Show Notes 00:00 Welcome to Syntax! 01:37 24 new web APIs that reached baseline in 2025. 01:49 Same-document view transitions for single-page applications. 05:28 abs() 08:22 Brought to you by Sentry.io. 09:20 JSON Module Scripts. 10:10 Popover API. 13:07 Base64 to UInt8Array. Better Binary Batter Mixing 16:11 @starting-style Scott's A CSS Only Accordion with Scott's Mobile Nav 17:39 allow-discrete 21:31 Promise.try 22:51 content-visibility Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads
Brett and Christina host an OG episode. Christina talks about her upcoming spinal surgery and navigating insurance hassles. Brett talks about his sleep issues, project progress, and coding routines. They dive into the complexities of USB-C cables, from volts to data rates. And TV’s just ‘okay’ now, except for some softcore gay porn. Kagi search saves the day. Happy holidays — and get some sleep. Sponsor Copilot Money can help you take control of your finances. Get a fresh start with your money for 2026 with 26% off when you visit try.copilot.money/overtired and use code OVERTIRED. Shopify is the commerce platform behind 10% of all eCommerce in the US, from household names like Mattel and Gymshark, to brands just getting started. Get started today at shopify.com/overtired. Show Links CaberQu BLE cable tester Umami Analytics Plausible Analytics Kagi The Comfortable Problem of Mid TV – The New York Times Fallout Heated Rivalry (TV Series 2025– ) – IMDb Chapters 00:00 Introduction and Greetings 00:40 Christina’s Health Update 05:05 Brett’s Sleep and Work Routine 12:19 USB-C Cable Confusion 22:03 Sponsor Break: Shopify 24:26 Sponsor Break: Copilot Money 26:57 Exploring Rocket Money and Web Interfaces 27:21 Discovering Umami Analytics 28:06 Nostalgia for Mint and Fever 28:44 The Decline of RSS and Google Reader 31:45 Switching to Kagi Search Engine 32:33 The Rise of AI-Generated Content 40:46 TV Shows: Is TV Just Okay Now? 47:24 The Cultural Phenomenon of Heated Rivalry 52:50 Wrapping Up and Holiday Wishes Join the Conversation Merch Come chat on Discord! Twitter/ovrtrd Instagram/ovrtrd Youtube Get the Newsletter Thanks! You’re downloading today’s show from CacheFly’s network BackBeat Media Podcast Network Check out more episodes at overtiredpod.com and subscribe on Apple Podcasts, Spotify, or your favorite podcast app. Find Brett as @ttscoff, Christina as @film_girl, Jeff as @jsguntzel, and follow Overtired at @ovrtrd on Twitter. Transcript Universal Serial Bitching Introduction and Greetings [00:00:00] Brett: Hey, you’re listening to Overtired. I am Brett Terpstra, and it’s just me and Christina Warren this morning. How you doing, Christina? Christina: Doing pretty good. Doing pretty good. Yeah. This is the, this is the OG Overtired configuration. Brett: right back to basics. Um, Christina: We do miss you Jeff, though. Ho, ho, ho. Hope that Jeff is having a great holiday with his family. Brett: we’ll have to have some, uh, gratuitous Wiki K hole that you go down just to, to commemorate the olden days. Um, so yeah, let’s, uh, let’s, let’s do a quick check-in. Christina’s Health Update Brett: Um, I’m curious about your health and all of the wildness that’s going on with your spine and whatnot. Christina: Yeah. Yeah. Um, same. I wanna hear about you too. Um, so, uh, Christina’s cervical spine update, as it were. Um, I am [00:01:00] still waiting to, as we’re recording this, which is like. Uh, three days before Christmas, uh, I’m still waiting to hear from the, uh, hospital to see if I can, when I can get scheduled. Um, insurance has sort of been a pain in the ass, so when I talked to them last week, they were like, we sent them some paperwork. We’re still waiting for some things back then. I called the insurance company and the, the, uh, like my insurance is like, has like an intermediary service that is supposed to contact the insurance company on your behalf and that person, but like, I can’t contact them directly. And then that person was like, oh, you don’t need pre-authorization. Go ahead and schedule the surgery. And I’m like, this doesn’t feel right. Um, so, but, but we, we went ahead and we called back the, you know, the, the surgeon, um, his office and they were very nice and we were like. They say that we can get on the books. So I don’t know when that will be. I’m hoping that it will be, you know, like the first week of January, um, or, or, or thereabouts. Um, but I don’t know. Um, [00:02:00] so I am still kind of in this like limbo stage where I don’t know exactly when I’m gonna have the surgery, except hopefully soon. And, um, and, and for anyone who hasn’t caught up, I, uh, I have a bulging disc on C seven on my cervical spine, and I’m going to get a, um, artificial disc replacement. Um, so they’re gonna take out the, you know, bulging bone and all that and put in, uh, some synthetic piece and then hopefully that will immediately relieve the, the pain that has been primarily through the left side of, uh, my arm and my shoulder, um, uh, down through my fingers. But it’s been on my right side a little bit too. So hopefully when that is done, it’ll be a relatively short recovery. Um, I’ll have an early scar and um, I will be, you know, not. Uh, the pain right now, like the levels aren’t terrible, but I’m pretty numb, uh, on my, my, my left arm, my, my right arm, um, uh, or right fingers I guess too, but, but really it’s, it’s, uh, the, the, the left side [00:03:00] that’s the worst. And traveling. Um, I’m, I’m in Atlanta with my family right now and, you know, kind of doing other things is just not, it’s not great. So, um, hopefully I’ll be getting surgery sooner rather than later. But obviously all that stuff does impact your mental health too, when you’re in pain and, and you, you know, are freaked out too about, you know, like, even though like they do, you know, it, it’s not an uncommon surgery and, and it, and it should be fine, but you know, there’s always these things in the back of your mind. You’re like, okay, well what if something goes wrong or whatever. So I’m just, I’m looking forward to, um, you know, light at the end of the tunnel, but um, still kind of in a holding pattern with that. So Brett: Wow. So that scar’s, that scar’s gonna be on your throat. Christina: Yeah, Brett: Wow. Christina: yeah. Like probably like. No, not really. I’m, I mean, I’m hoping that it’ll be, uh, like no, it really won’t be at all. Brett: I, I, I would like to have it. I can understand why you wouldn’t. Christina: yeah, I mean, you know, I will obviously, you know, uh, hopefully it’ll be like low enough to be [00:04:00] primarily covered by shirts or other things, although, who knows? ’cause I do like to wear like, lower cut things sometimes. I don’t know. It, it’ll hopefully, you Brett: I heard chokers are coming back. Christina: Yeah, I don’t, unfortunately. I think it’s gonna be too, uh, low for that. Brett: Okay. Christina: uh, like, it, it’s gonna be, I think like it might hit against my laryn is, is what they say. That’s the other thing too. I might have, you know, some hoarseness after, won’t we permanent? Um, you know, knock on wood. Um, Brett: go on Etsy, you can get, um, they’re for BDSM, they’re like neck, uh, they hold your chin up. They’re like posture enhancers. Uh, but they sell them within leather with like corset straps. ’cause they’re like A-B-D-S-M accessory. That would work. Christina: No, no. Not even once. Uh, not even once. I mean, look, a good group of people who wanna do that, uh, I I will not be wearing a collar of any sort of that sort of thing. Uh, I, I, I don’t, I don’t really wanna, wanna be part [00:05:00] of, uh, one of that, those types of, you know, uh, Harlequin romance novels. , Brett’s Sleep and Work Routine Brett: All right, well, I will go ahead and check in. Um, I, I’m sleeping really well for like two days at a time, and then I’ll have. A string of like five or six hours of sleep, which isn’t nothing. Um, but it’s not quite enough for me to not feel tired all the time. And two nights of sleep is not enough for me to catch up on sleep. And, um, so I’m kind of, this has been going on for like a year though, so it’s, I’m just kind of, I’m used to it and I’ve learned to operate pretty well on six or seven hours of sleep, even though historically like I need eight and a half. Um, but I’m doing okay and I get up about four every morning and I start coding and I usually code from like four to noon, so an eight [00:06:00] hour workday, uh, with a breakfast somewhere in there. And, um, I’ve made really good progress. Marked is, as far as I can tell, ready to go wide with the beta. Um. I think I’ve solved every bug that’s been reported so far. I only have about a hundred testers right now, um, but I’m gonna open it up, uh, try to get maybe a thousand testers for a couple weeks and then go for a live release. The biggest thing that I’m running into is problems with getting the, like free trial and the purchase mechanisms working, which is the exact same thing that’s holding up NV Ultra right now. Um, so if I can figure it out for Mark, I can port it to NV Ultra. I can have two apps out there making money, hopefully never have to get a job again. Um, I’m teamed up right now with Dan Peterson, formerly of One Password. Um, and we’re [00:07:00] working on some iOS apps and. And, uh, apex. My, my, all my Universal markdown processor is, it’s coming along really well. I’ve, I’ve put it out there. Um, I’ve talked to John Gruber a little bit about it. He’s gonna give it more of a workout and get back to me. Um, but I think, I think it’s getting to a point where I would be comfortable integrating it into Mark and even talking to some other, uh, apps about using it as their default processor, um, and kind of alleviating some of the issues people run into with, uh, differences in syntax. Um, I. I, I, I talked to Devon, think, uh, Eric from Devon think about using it. ’cause they use multi markdown right now, uh, which has a lot of cool features, but is not [00:08:00] really in sync with what most of the web is using these days. Um, so I talked to them about it and they’re like, oh, we had the exact same idea and we’re almost done with our own universal processor. Um, and theirs is gonna output like RTF and things that I don’t need apex to do. ’cause you can just pipe apex into panoc and do everything you need. So anyway, I’m, I’m tired. I’m, I’m in good spirits. I. I’m dealing fine with winter. My, I’m alone on Christmas, which is gonna be weird. Um, my family’s outta town. Elle is house sitting I’ll, I’ll go visit Elle, but most of the day I’m gonna be like by myself on Christmas and I don’t drink anymore. And I, I don’t, I don’t know how that’s gonna go yet. Um, initially I thought, oh, that’s fine. I like being alone. But then, [00:09:00] then the idea of like, not having anyone to talk to you on Christmas day started to feel a little depressing. Christina: Yeah. Yeah. Um, but, um, hopefully, um, when, when will, uh, when will I’ll be back from, from house sitting. How long is, uh, are, are they going to be Brett: I think. I think the people, the, the house owners come back Thursday or Friday. Christina: Okay. Brett: Then we’re gonna take off and go up to Minneapolis to hang out with her family for a weekend. So, I don’t know. It’ll, it’s gonna be fine. It’s gonna be fine. We’re gonna like cook on Christmas Eve and, and have leftovers on Christmas day. It’ll be fine. Christina: Yeah, yeah. Well, but, but it, but, but that is weird. Like, I’m sure like to be, you know, not, not, not, not with like your usual crew, but, um, [00:10:00] especially without the alcohol there. But that’s probably a good thing too. Brett: Yeah, I guess. Um, I will have all the cats. I’ll be fine. I have to take care of the dog too. Christina: Have, have you heard any updates, like, um, I guess, um, about when you were, you know, you were in the hospital a few times over the last year with, with various things. Did you ever get any definitive update on what that was? Brett: On which one? I have so many symptoms. Which one are we talking about? Christina: Well, I guess I, I guess when you, you know, you’ve had to be like hospitalized or Brett: The pancreatitis. Christina: had the pancreatitis. Brett: the, the fact that it hasn’t happened again since I stopped drinking, um, really does indicate that it was entirely alcohol that was causing the problem. Um, so yeah, I’m just, I’m never gonna drink again. That’s fine. It’s, it’s all fine. Um, I did, I did get approved to get back on Medicaid. Um, so [00:11:00] yeah, I haven’t gotten the paperwork in the mail yet. Uh, but my old card should just start working and I’ll be able to, my, my new doctor wants a whole bunch more tests, including an MRI of my pituitary gland. Um. Like testosterone tests and stuff that I guess is more specific to what she thinks might be going on with me. Um, but now I can, I can actually get those tests That would’ve been just a huge out-of-pocket expense over the last couple months. So I’m excited. I’m excited to be back on Medicaid. I wish everyone could have Medicaid. Christina: Yeah, that would be really nice. That would be really nice if, if, if we had systems like that available, um, for everyone. Um, but. Instead, you know, if they’re, like, if you have really great health, I mean, you, you pointed those out. Like you have really great health insurance if you [00:12:00] can prove that you, you know, make absolutely no money. Um, but, but that opens up so many other, you know, issues that most people aren’t lucky enough to be able Brett: right. Yeah, totally. Christina: right. Brett: All right, well do you, okay, first topic. USB-C Cable Confusion Brett: How much do you know about USBC cables and the various specs? Christina: Uh, Brett: you know a shit ton. Christina: I do, unfortunately, I know a lot. Brett: So I, I had been operating under the assumption that there were basically, you had like data USBC cables, you had, uh, thunderbolt USBC cables and you had like, power only USPC cables. It turns out there’s like 18 different varieties of different, uh, like vol, uh, voltage, uh, amperage, uh, levels, like total wattage basically. And, um, and transfer speeds. And, [00:13:00] um, and there’s like maximum links for different types of cable. And it, it, I started to understand why like. One device would charge with one cable and another device would not charge with the same cable, even though they all have the same connector. Christina: Yeah. Yeah. I mean, I think this is, this is why, um, some of us have been really like eye rolly at the EU for their pronouncements about certain things, because simply mandating a connector type doesn’t actually solve the problem. Brett: No, it actually confuses it a little bit Christina: I think Yeah, I was going to say exactly. I think in some cases it makes it worse. Right? And, and then you have different, like, and, and then getting SB four into it, uh, uh, versus like, like, like, like various Thunderbolt versions. Like that adds complications too, because technically SB four and Thunderbolt four should basically be the same, but they’re not really, there are a couple of things that Thunderbolt might have that [00:14:00] USB four doesn’t necessarily have to have, although for all intents and purposes they might be the same. And then of course, thunderbolts five is its own thing too. So like I bought off of Kickstarter, I got like this, you know, like a cable charger, basically like, like a connector thing. It was like $120. For this, this, this thing that basically you can plug a cable into and you can see its voltage and um, or not voltage, I guess it’s uh, you know, amperage or whatever. And you can see like, it, it, it’s transfer speed and you can basically like check that on like a little display, which is useful, but the fact that like, you have to buy that sometimes. So like figure out, well, okay, well which cable is this? Right? And then, uh, to your point about lengths, right? So like, okay, so you want something that’s going to be fast charging but also high speed data transfer. Alright, well that means that you, the cable’s gonna have to be stiff. It’s not gonna be able to be something that’s really bendable. Um, which of course is what most people are going to want. So like you can get a fast charge, like a 240 wat or a hundred and, you know, 20 wat or, or [00:15:00] whatever, um, like a USB 2.0 transfer speed cable. But if you want one that’s, uh, going to be, you know, fast charging and. Fast data transfer, then like that’s a different type. And they have like limited lengths, which again, can also be associated with like Thunderbolt or Thunderbolt. You know, cables are much more expensive. Um, and, uh, uh, you know, the, the, the, but their, their lengths are limited. Um, yeah. Uh, it’s very confusing. Brett: Did you know that in rare circumstances there are even devices that will only charge with an A to C cable. Christina: Yes, Brett: That’s so insane. Christina: yeah, no, I’ve run into that myself and then that’s a weird thing and I don’t even know how that should work. ’cause it’s, it’s, it’s a bizarre thing. You’re like, okay, well I thought this was just like a, you know, maybe like a dumb end, but it’s like, no, there’s like, you know, basically a microchip Brett: Like a two pin to two pin. Christina: at this point. Brett: Like two pen to two pen, no pd like you would think that would work with C to C, [00:16:00] but somehow it has to be A to c. I am getting one of those cable testers. I asked for one for Christmas so I could figure out this pile of cables I have and like my Sonos Ace headphones are very particular about which cables and what, um, charging hub I hooked them up to Christina: Right. Oh, yeah, hubs. I was gonna say, hubs introduce a whole other complication into this too, because depending on what hub you’re using, if you’re using a USB hub, it may or may not have certain things versus a Thunderbolt hub versus something else, versus just like, um, you know, a power brick. Like, yeah. Brett: Yeah. It’s fun stuff you. Christina: Yeah. No, it’s annoying. And, um, like, and what, what’s frustrating about this is like some of the cables that they’re better, like you can look at the, you know, the bottoms of them and you can see like they will have like the USB like four, or they might have 3.2, or they might have, you know, like the thunderbolt, you know, um, uh, icon [00:17:00] with, with, with its version. So you can figure out is this 20 gigabits, is this 40, is this 80? Um, but um. That’s not a guaranteed thing, and that also doesn’t guarantee authenticity of stuff, right? So a lot of the cables, you know, you buy off the internet can be, you know, and they might be, or even at stores, right? Like you’re, you’re not buying something from, even if you get things from Belkin or whoever, like, those things can have issues too. Um, although they at least tend to have better warranties. I bought a Balkan, um. Uh, like a, a, a PD cable, like a two 40 cable that I think it was like, you know, uh, 10 feet longer something. It was supposed to have some sort of long warranty and, and because the, the, you know, um, faster transfer ones, um, are, even though it was braided, you know, it stiff and it, it broke, like there was, uh, the, like the, you know, the connect with the part of the, the, the cable near the, the end, um, did that thing that typically apple cables do, where like, it, it sort of [00:18:00] fraying and you started like seeing the exposed wires and then like, you start to like, feel like, you know, like an electric charge, like Brett: A little tingle. Christina: you’re Yeah. And you’re like, okay, this isn’t good. Um, and so I at least had my Amazon receipt, so I was able to like. Get them to mail me a new one relatively easily. And like Anchor has an okay warranty too. But it’s one of those things you’re like, okay, when did I buy this? I was like, I didn’t even buy this a year ago, and this thing already crapped out. Um, versus, you know, you can get some really nice braided cables that are flexible, but they’re just gonna be 2.0 speeds. Um, and, and then if you buy, you know, you just buy like some random cable, you know, like at the airport or whatever. You’re like, all right, well, I don’t even know Brett: Great. Christina: anything about this. Uh, yeah, Brett: I have heard good things. I’ve heard good things about the company. Cable Matters. Christina: Yeah. Yeah. They make good stuff. They make good stuff. But again, at least the cables matters, cables that I have have been primarily stiffer cables because they tend to be like the, the higher transfer [00:19:00] speeds. So, um, like I have a cable, cable matters Thunderbolt cable, and I have like a USB four cable, I think. Um, but like, these are cables that like. I don’t, I mean, I, I have one that I, I kind of travel with, but I don’t, um, either keeping it as little cable matters, uh, uh, plastic, um. Like, so they come in like these, these case, uh, not these cases. Uh, they come in like these, uh, almost like Ziploc bag type of things. Um, which is a great way to ship cables honestly, you know, rather than using a box and, and like I, and I might toss one of those in a suitcase or a backpack, um, rather than having like the cable just out there loose. But I do that primarily because again, like they’re stiff and they’re not the sorts of things that I necessarily want, like in the bottom of my bag, you know, potentially getting broken and, and, and, and twisted and all of that. Um, they are overpriced for what they are and they are definitely not like, they’re not a high transfer cable, but if you can find ’em on sale, the beats, cables, the, the, the, the, the, the branded Beats cables, I actually like them better [00:20:00] than the apple cables that are the same thing, because they are, they’re longer, uh, by, you know, um, a, a few inches than, um, the, the Apple ones. But they’re still braided and they’re nice. And I was able to get, I dunno, this was a, this was not even Black Friday, but this was. Um, you know, sometime in like early November, I think, um, or maybe it was like late October. It might’ve been a Prime Day thing, I don’t know, but they were like eight or $9 a piece, and so I bought like five or six of them. Um, and they are, you know, uh, uh, PD and like, like, like fast charging peoples, they might not be 240, but I think they’re, they’re, they were like a hundred and you know, like 20 watts or whatever. But, um, you know, not high transfer speeds, but if you’re wanting to just quickly charge something and have it, you know, be a, a decent length and be like flexible. Those I don’t, those I don’t hate. Um, anchor makes pretty good cables. You green seems to be the company that’s sponsoring everyone now for various things. [00:21:00] But, um, I don’t know. I’ve started using MagSafe more and more, uh, like wireless charging when I can for some things, at least for phones, Brett: yeah. I actually have some U green wireless charging solutions that are really good. Christina: Yeah. Yeah. I just got one of their, uh, their 10,000 million pair battery fast charging battery things because now the MagSafe, uh, can be like up to, you know, 30 watts or whatever, or 25 watts or, or, or, or whatever it is. Like it’s, um, a lot more, um, usable than, you know, when it was like 10 or, or, or even 15. You’re like, okay, this, this is actually not going to be like the, the slowest, you know, charging thing known to man. But of course, obviously it’s like you can use it with your phone and with your AirPods, but the rest of the things out there don’t, don’t all support shi too, so, Brett: Right. Christina: yeah. Brett: All right. So, um, I want to talk about TV a little bit. Christina: Yeah. I think before we do that though, we should probably Brett: oh, we should, we [00:22:00] have two sponsors to fit in Jesus. I should get on that. Sponsor Break: Shopify Brett: Um, let’s start with, uh, let’s start with Shopify. This episode is brought to you by Shopify. Have you been dreaming of owning your own business? In addition to having something to sell, you’ll need a website, a payment system, a logo, a way to advertise to new customers, et cetera, et cetera. It can all be overwhelming and confusing, but that’s where today’s sponsor, Shopify comes in. Shopify is the commerce platform behind millions of businesses around the world, and 10% of all e-commerce in the us From household names like Mattel and Gym Shark to brands. Just getting started, get started with your own design studio with hundreds of ready to use templates. Shopify helps you build beautiful online store to match your brand style, accelerate your content creation. Shopify is packed with helpful AI tools that write product descriptions, page headlines, and even enhance your product photography.[00:23:00] Get the word out like you have a marketing team behind you. Easily create email and social media campaigns wherever your customers are scrolling or strolling. And best yet, Shopify is your commerce expert with world-class expertise and everything from managing inventory to international shipping, to processing returns and beyond. If you’re ready to sell, you’re ready for Shopify. Turn your big business idea into with Shopify on your side. Sign up for your $1 per month trial and start selling today@shopify.com slash Overtired. Go to shopify.com/ Overtired. That is shopify.com/ Overtired. Thanks Shopify. Christina: Thank you Shopify. Brett: It’ll be, it’ll be just tight as hell by the time people hear it. But that was rough. I, that, that, that, that read, you just heard I [00:24:00] edited like six places. ’cause I kept, I, I don’t know. I’m tired. I’ve been up since, I’ve been up since two today. Christina: Yeah. Shit, man. That’s, yeah, you again, like you’ve been having like sleep issues. It’s, it’s, Brett: Maybe, maybe I shouldn’t be doing sponsor reads. Christina: No, no, no, no, no. Uh, no. We definitely wanna talk about tv. Do you wanna do, do we wanna do our second, um, uh, uh, ad break Brett: let’s do a block. Let’s make it a Christina: Let’s do it. Block. Alright, fantastic. Sponsor Break: Copilot Money Christina: Alright, well, since we are about to go into 2026, this is a great time to, uh, think about your finances. So are you ready to take control of your finances? Well meet copilot money. This is the personal finance app that makes your money feel clear and calm with a beautiful design. Smart automation copilot money brings all of your spending, saving and investment accounts into one place. It’s available on iOS, Mac, iPad, and now on the web, which is really great, uh, because I know, uh, for me anyway, that’s one of my one kind of things [00:25:00] about some of these like tools like this is that there’s not a web app. I’m really bothered by it. This is, you know, it’s a frustration that like the Apple card, for a long time, you know, you couldn’t really access things on, on the web. Even now it’s still kind of messy, like being able to handle things on the web. But as we enter 2026, it is time for a fresh start. And so with the, uh, mint shutdown and rising financial uncertainty, consumers are seeking clarity and control. And this is where copilot money comes in. So copilot money can help you track your budgets, your savings goals, and your net worth seamlessly. Plus, with the the new, um, web launch, you can enjoy a sudden experience on any device, which is really good. And guess what? For a limited time, you can get 26% off your first year when you sign up through the web app. New Year’s only don’t miss out on the chance to start the new year with confidence. There are features like automatic subscription tracking, so you’ll never miss upcoming charges again. Copilot money’s privacy first approach ensures that your data is secure and their team is dedicated to helping you stress less [00:26:00] about money. So whether you’re a finance pro or just starting out, copilot money is there to help you make better decisions. Visit, try dot copilot money slash Overtired and use the code Overtired to sign up for your one month free trial and embrace financial clarity. That’s try.copilot.money/ Overtired. Use the coupon Overtired. And again, that is 26% off for your first year. So thank you copilot money for, uh, sponsoring this week’s, uh, uh, episode. Oh, one other note about copilot money. They were, um, an apple, uh, design award finalist. So it’s a really well designed app and, um, we love to see, um, apps like this available on, on the web as well as iOS and, and MAC os. Brett: I have started using it very much because of the web version, and it is, it is really good. Christina: yeah, yeah. No, yeah. For, yeah, for me, that is like a, an actual like. Concrete requirement. Exploring Rocket Money and Web Interfaces Christina: Any money Brett: Like I’ve, I’ve [00:27:00] paid, I have about eight months left. I paid for a year of, of Rocket Money or whatever it’s called now. Um, and I’ve always loved that app, but yeah, it does not have a web interface. And once I started trying copilot out, I realized how much I really did want a web interface for that stuff, you know? What else have you seen? Discovering Umami Analytics Brett: Umami the analytics platform. Christina: Yes. Brett: It is so good. And it’s, it’s open source and you can self-host. And it is like, I, I’ve been using Fathom Analytics for a long time and I like Fathom, but Umami is, it has like all of the, uh, advanced stuff you would get with Google Analytics, but with like way more privacy focus and you’re not giving information to Google for one. Um, and the interface is beautiful. I love that. It’s so good. Christina: Yeah. Um, umami is really good. I think, uh, there’s another one, I’m [00:28:00] trying to think of what it was called. There are a number of these various, um, analytics, uh, hosted things, but no, umami is definitely a really good one. Nostalgia for Mint and Fever Christina: And I like, um, it reminds me, um, it was, what was it? It was Mint. It was Mint, Sean Edmond’s Mint. Which Brett: I was just gonna ask you if you remembered that. Christina: yeah, which was, which was one of the, uh, plausible analytics. It’s another one too. Um, which is also like, um, they, they have a hosted version, but you can also self-host. Um, and then that’s also a, a, a, another, uh, good one. But yeah. Um, was like my, my all time favorites, uh, you know, app. I, I, I loved that. Brett: Um, what was his RSS one? Uh, fever? Fever. Christina: was, was the best fever, was the best. The Decline of RSS and Google Reader Christina: And it was funny, like I, I think I’ve talked about this before, I was more insulated and like less upset than some people by the, the Google reader death because I had a, a, I’d been using Fever for so long, and then obviously, you know, stuff being updated and doesn’t really work [00:29:00] super well with like, the latest versions of PHP and things like that. But, you know, a lot of people were really, understandably and, and still more than a decade on, you know, very upset by the death of, um, Google reader. But I think because I, I had paid for and used, you know, my own, um, self-hosted fever installation, and then there were apps that people used for, you know, APIs and whatnot to build, you know, Macs or iOS apps or, or whatever. Like, I, I was obviously upset about Google Reader being shut down, but I was like, okay, you know, I, I can just, you know, move on to something else. And, um, and I’ve used, uh, feeder, um, not, not, not feeder, um, Brett: Reader Christina: is. No, no. Maybe, uh, it’s, uh, not Feed Demon. Um, that was like the OG one. Um, it’ll come to me, um, because I, I, yes. Thank you. Feed Ben. Thank you, thank you. One of the ones that’s still around, uh, from like the, of the, you know, various Google reader alternatives, like many of them. You know, closed up shop.[00:30:00] Brett: Yeah. Christina: if they kind of realized, you know, by Google reader, like this is the, unfortunately a niche market. Um, now that didn’t help the fact that like, you know, when people, when web browsers Safari, I think started at first and then Firefox did, and then, you know, uh, Chrome was, was fairly early too. Like when all the web browsers took away like RSS buttons to make it easy to subscribe to feeds or to auto discover feeds, and you had to like install like a, an extension or whatever to do that. Like, that all helped with the, the demise of RSS in a lot of ways. And of course, people moving everything into closed platforms and, and social networks and stuff that, you Brett: In, in the tech world though. So I have, my blog gets about 20,000 visits a week, but it gets 30,000 RSS downloads, like, uh, like daily, 30,000 readers are, are, are pulling my site. Um, so RSS is far from dead in the tech world. Christina: Right. Well, [00:31:00] well, I think, I think in a certain demographic, right? I think if you were to ask like a new, like college grads, I don’t think that any of them are using RSS at least not actively, right? Like, I mean, you might have a few, but like it’s, it’s just not gonna be like a thing where they’re gonna be, act like they might be using some apps that do similar types of things and might even pull in feed sources maybe. But it, it’s, it’s just not like a, like when, when I was graduating from college or in college, like everybody had, you know, RSS clients and that was just kind of a, a known thing. Brett: Yeah. So speaking of traffic, um, I don’t, did I mention that I got delisted on Bing and Christina: You did, Brett: I am, I’m back Christina: figure that out? You’re back now. Okay. Brett: I’m back now. Switching to Kagi Search Engine Brett: And, um, I have switched to using Kaji, um, as my primary search engine and they replicate all of duck duck go’s bang searches. Christina: Yes. Brett: So I Christina: one of the things I love about them. [00:32:00] Yes. Brett: I was pleased to see there’s a Bang Turp search on Kaji. Um, I actually use Christina: or is it kgi? Because I think I’ve always called it kgi. Yeah, it’s KA, it’s K, it’s KAGI. For anybody who’s who’s, uh, I don’t know how to, how, how, if it’s kgi, kgi, um, uh, you know, Kaji, whatever, Brett: It’ll be in the show notes. What the fuck ever, we’ll just call it KGI. Um, and yeah, so like I was super happy ’cause I used the Bang Turp to search my own site. I just got used to doing that. The Rise of AI-Generated Content Brett: Um, and, but it is like you can, the reason I switched to said web, uh, search engine is um, because you can report sites that are just AI slop and they will verify those reports and remove or flag slop sites in your search results. ’cause I was getting sick, even with DuckDuckGo, like five out [00:33:00] of 10 results were always, I’d get in, I’d get there, I’d get one, maybe two paragraphs into, uh, an article and realize, oh, someone just typed in my search term into chat GPT and then Christina: Oh yeah. Brett: automated it. Christina: Oh, I was gonna say there, there it is. Automated at this point. And, and like, to be clear, like a lot of search results, even before like the rise of like genre of AI were a variant of this, where you would see like people like buying older domain names that expired. Well, yeah, but even before that happened mean that, that obviously when, when, when the Christina Warren and Brett Terpstra and then they, they changed your name. Um, I Brett: know, like Jason Turra or Christina: Or something like that. Yeah, it was, it was, it was, it was weird. Um, I mean, you know, um, does that site, did, did have they given up the ghost on that? I’m curious. Um, yeah. Wow. Okay. They are still, well, no, they haven’t published anything since November 30th. So something has happened where they, uh, are [00:34:00] they, they’re definitely cutting down on, on various things. Um, oh no. Paul Terpstra. Oh my God. Paul Terpstra. You are still, Brett: Yeah. Christina: you were like the one author there that I see on this website. Um, now what was, what was messed up about, about this? Um, although no. Okay. Their homepage, the last one they say is like, OCT is like, uh, November, um, uh, 30th. But if you click on the, the Paul trips to handle, then like you see, um, December 22nd, uh, which is, which is today as we’re recording this, Brett: Wow, I didn’t even realize. Christina: Yeah. So, alright. So that is still, somehow that grift is still going on. But yeah, I mean, even before the rise of those things, you would see, you know, sites that would either buy up dead domains and then like, have like very similar looking content, but slightly different maybe, you know, like, uh, you know, injected with a bunch of, you know. Links or whatever, or you would see people who would, you know, do very clearly SEO written and, and probably, you know, [00:35:00] like, again, pre generative ai, but, you know, assisted slop content. But yeah, now it’s, it’s just, it’s crazy. Like, and it doesn’t help that, like the AI summaries, which can be useful, but, um, and they’re getting better, which is good only because they’re so prominent. Like, I’m not a fan of them. But if you’re not using an alternative search engine, like, you know, you see these AI summaries and like if they’re bad and sometimes they are then. Brett: Often Christina: You know, well, they’re, they’ve gotten better, uh, is the only thing I would say. I, I still wouldn’t rely on them, but I’ve, I’ve noticed a, like, I’ve noticed a, a genuine, like uptick in like, improvements and in like, how awful they are probably in like the last six weeks, which is damning with faint praise. I’m not at all saying it’s good. I am simply saying, it’s like, I’m primarily thinking for like, people who are like, like less tech savvy relatives who are going to just go to, you know, bing.com or, or google.com and then see those sorts of things. Right. Um, and, uh, you know, we’re not gonna be able to convince them to go to a, a, a third [00:36:00] party search engine. Um, although, you know, some people, like, I think my mom was using Duck to Go for a while as like her default on her iPhone, um, which I was, I was like proud of her about, but I was also kind of like, uh, that’s got its own issues. But no, I, I like ka a lot. Um, I, I’ve Brett: Well, and it’s so keyboard driven, like DuckDuckGo has good keyboard shortcuts. KAGY slash Kaji has even better keyboard shortcuts. Like you can navigate and control everything with, uh, like Gmail style, single key keyboard shortcuts, which I really like. Christina: Yeah. Yeah, I like that too. And then they, they, of course, they make like a, a web kit, um, like a browser, um, that, that has, they’ve back ported, um, you know, a lot of chrome extensions too. I personally don’t see the point in that. Um, I, I think that if you’re going to be like that committed to, like, using like the, you know, the web extension format and like using like more popular extensions, you might as well [00:37:00] just use a Chrome fork if you don’t wanna use Chrome, which is fine, but like, you could use a browser like Helium, which, which we talked about last show, which has, um, the, the, the hash bangs kind of integrated in, or you could use, you know, if you wanted to use, um, um, you know, the, the, the, the Brett: o is Orion, is Orion the one you’re talking about that? Yeah. Christina: that, that, yeah, that, that, that, that, that, that’s Katy’s thing. And that was actually originally how I heard about them was because it was like, oh, this is interesting. Um, you know, this is a kind of an interesting, you know, kind of alternative browser. And then it turned out that that was just kind of a, in some ways, kind of a front to promote the, the search engine, which is the real, you know, thing. Um, which is fine, right? I mean, that, that was Google’s model. Um, Brett: Well, and we should mention for anyone who hasn’t tried it, it is a paid service. Um, and you are getting search results with no ads and, and spam, uh, ai, slot protection and all of the benefits you would expect from a paid service. So [00:38:00] I think, like for me, five bucks a month gets me, I think 300 searches, which is. Plenty for me, like, I guess I, I’m still waiting to see, I’ve never counted how many searches I do a month, Christina: Yeah, Brett: you know, like three searches a day, uh, would come out to like 90 searches a month and I have 300 available, so I think I’ll be fine. Christina: yeah, yeah. I mean, yeah, basically being able to get to do 10 a day, which in most cases is fine. What I’ve done is I’m on, like, they have a, a, a family plan, um, and they don’t care. They even, I think in their documentation, or at least they did, they do not care if you are like actually in a family with the people that you are on or not. So if you, you know, find some folks that you wanna kind of sync up with, you can like, you know, be on a family plan together and you can save money, um, on, uh, whatever their, uh, um, their pricing [00:39:00] stuff is. So, um, so me, me and Justin Williams are, uh, in a, uh, Brett: Justin Williams, I haven’t heard that name in forever. Christina: Yeah. Yeah. We went to C Oasis together. We went both nights in Los Angeles, um, in August. Yeah. Um, or September rather. Um, yeah, so, okay, so this is how this works. They have, their starter plan is, is $5 a month, which includes, and they do have an AI assistant too. So it was funny, they had the AI slot protection, but they also have like an AI assistant that you can use and like an AI summarizer and whatnot. Um, that’s $5 a month. And then there’s the professional plan, which is, so that’s for 300 searches a month for the standard AI for starter $5 a month. The professional plan is unlimited searches and standard ai, that’s $10 a month. And then the ultimate is, um. Uh, everything in professional plus you get like premium model access, which, okay, but the family plan, um, is, is the, so you can do one of two things. You have a duo [00:40:00] plan, which is two professional accounts for a couple, which is $14 a month plus sales tax. So it’s, uh, you know, average of $7 per person, which I think is what Justin and I are on. And then there’s a family plan with up to six family members. And again, they don’t care if you are actually in a family or not, and that’s $20 a month. So the real thing to do if you’re wanting to like, you know, save on this is like find five friends, Brett: Yeah. Christina: get on the $20 a month, you know, family plan thing. Spread the, spread the cost, and that way you can get the, you know, professional plan for, for, for less. But to your Brett: All right. Christina: most people, it’s probably $300, 300 searches a month is probably plenty. And if you search a lot like we do, I, I think it is worth paying for. Brett: yeah, yeah. All right. TV Shows: Is TV Just Okay Now? Christina: anyway, but we wanted to talk about tv, so let’s Brett: Well do, we’re, we’re at 50 minutes already, so I think we need to choose whether we do TV or gratitude. What Christina: do you have a [00:41:00] gude, like a good one? Brett: I, I, no, I have a, I have a throwaway one. Christina: Okay. Brett: I, it was one of those, like, I looked at my doc and I was like, oh, I don’t think I’ve talked about that even though I probably have, um, yeah, let’s just talk about tv. So I, I have been noting, and my question in the show notes was, is TV just okay now? Because I’ve been watching, I watched Stranger Things, pluribus Down, cemetery Road, platonic, and all of it was, it was entertaining, but it wasn’t like, must watch tv. None of it was like, none of it was as good as like Modern Family. Modern Family was fucking good. Tv, like family friendly and just like I’ve, I’ve been through that series so many times and it’s always fun and it’s always better than like pluribus. I like the, I like the concept kind of, it’s not. not all that, um, engaging, I guess.[00:42:00] Christina: I like it. But, Brett: Yeah. I don’t hate it like I do, I do like it, but it’s not like, I don’t, I don’t count the days until the next episode comes out and I miss, I miss things being really good. So you had a couple responses to that though. Christina: Well, I mean, I tend to agree with you. So first of all, there, I put in the, in the show notes, um, there’s a link to a thing that, uh, that James and Pozak wrote for the, the New York Times, uh, God a year and a half ago now called, um, the Comfortable Problem of Mid tv. And he said it, it, it’s got a great cast, it looks cinematic, it’s, um, fine and is everywhere. And kind of talking about like, you know, we went from like the era of like peak TV to now being, um. You know what, what he’s dubbed like mid tv and I think that there’s, there’s some truth to that. Um, and, and, and he even says at the beginning, let me say up front, this is not an essay about how bad TV is today, just the opposite. There’s, um, little truly bad high profile television made anymore, um, is it’s more talking about, um, like [00:43:00] what we have instead Today is something less awful, but in a way more sad, the willingness to retreat, to settle to trade, the ambitious for the defendable. And I think that there’s some truth to that. Um, I think that we see this movies now too, and with movies it’s actually much more of a problem. Like there’s some really high highs. Um, but because the movie industry is in such a bad place, um, it, it’s that much more notable when like, you don’t have like a big strong slate of, of things. And so, you know, it, it, it’s more of a problem. TV for, for better or worse, has become the dominant entertainment form. And yeah, I think that it, it, it’s fine. Uh, but there are very few things that I’m like, oh, wow, yeah, that, that’s like, you know, the wire. Um, not that anything is, but you know what I mean? But is, but even like, you know, pluribus, which I really like. I actually think that’s, um, my, my favorite show of, of, um, 2025, um, at least new show. Um, well, maybe the studio. The studio. I might have, I, I, I might put, Brett: That was pretty Christina: above that. But, but, but, but [00:44:00] like, it’s one of those things where I’m like, okay, you know, um, it’s not breaking bad, right? Like, if we’re gonna be comparing Vince Gilligan shows, and maybe that’s unfair, but, you know, it just, but, but still, like, you know, you’re gonna be compared to your last hit. And, and, and, and that is what it is. Um, I will say though, like, I haven’t watched Stranger Things in years, and I don’t, I don’t, I don’t think I can force myself to like, care about that again, but I’ve heard kind of mixed Brett: That’s where L is too, L doesn’t care. And, and then there’s the whole like two cast members being Zionists kind of turned a whole bunch of people off and Christina: Well, and well, David Harbor, David Harbor’s whole Lily Allen thing. Are you, are you, are you familiar with this floor at all? Brett: No. Christina: Okay. You know who Lily Allen is? Brett: Yes. Christina: Okay. So she and David Harbor were married and, um, she wrote an album called, uh, uh, west End Girl that, that came out, uh, like in November, which is actually a really good album, [00:45:00] which is like White Girl Lemonade, where she just basically reads him to filth for being an absolute piece of shit. Like, apparently like, you know, they were together, they were married or whatever. She goes off to London to perform in a play and he’s like. Oh, we’re gonna be away for months. I, I wanna sleep with other people. And so they kind of like, she kind of accepts getting into an open relationship with him, even though she didn’t really want to be, which look that her, that’s her bad, whatever. But then he proceeds to like, do things that was not what they’d agreed upon on, upon the parameters of their, of their relationship. And then she’s just like brutally honest about the entire thing. And so as you’re listening to this album, you’re just learning more and more about like, David Harbor’s like sex life and, um, and stuff. And, and like, it’s just on blast. It’s incredible. Um, but, uh, yeah, so there’s, there’s some of that stuff. There’s, I, I don’t know, like I don’t, I don’t really follow the rest of the cast stuff except that, uh, the girl who plays, um, 11 like. Frequently want to smack because just the most annoying [00:46:00] celebrity in on the planet. But like, putting that aside, um, I just, I stopped caring. It took them too long between seasons and the, and, and, and the budget for that show was also so insane. I’m like, you, you cost more than strain than thinking of Thrones. Game of Thrones is, was even at its worst, was a better show than Stranger Things. So like it, yeah. But but that goes to your point. Like, it’s like, it’s okay. Brett: Yeah. Yeah, Christina: Um, I will say the new season of Fallout just, um, premiered and so far I I’m still really enjoying that. Um, Brett: yet to see it. Christina: you should, you should definitely watch the Brett: What is it on? Christina: uh, Amazon Brett: Okay. Christina: and, uh, and it’s, and it’s really, really good. Um. And this year they are doing the episodic, um, not episodic, the weekly drop, right. Rather than the binge thing. So the first season, uh, they dropped it all at once and um, and I was a little bit worried. I was like, fuck, does that mean they don’t [00:47:00] believe in this? What are they going to do? Wound up being like Amazon’s biggest hit after their Lord of the Rings, um, you know, thing. And so it was immediately kind of picked up for a second season and it was picked up for a third season before the second season even, uh, premiered. Um, and uh, and that might be the final one. Um, they’re saying, but, but, but, but who knows? But, but so far anyway, like they’ve only, there’s only been one episode, but it’s, it’s been good so far. The Cultural Phenomenon of Heated Rivalry Christina: Um, but, but what I was gonna talk to you about is the gay hockey show. Brett: Which is. Christina: It’s called Heated rivalry. It’s on HBO Max. It was originally just supposed to be on, uh, a Canadian streamer called Crave. And um, then at the, like, the, the like 11th hour, HBO Max picked it up and was like, okay, we’ll play this in, um, some of our territories and other things. And I wanna be very clear, this is not high art at all. This is like, no way. Like this actually in some ways it, it personifies [00:48:00] the TV is just okay now thing, but in other ways it’s actually a little bit more interesting just because the cultural phenomenon that has happened around it in like the last, like, like it hasn’t even been out a month and it’s only six episodes, although they are also going to be getting a second season. Um, it’s sort of wild how, like I went from, I’d seen a trailer for it and I was like, okay, whatever. And like it came out, I think like right after Thanksgiving. Then like within like two or three weeks, like literally I wasn’t following anything around it, but my Instagram, my TikTok, Twitter, everything that I was seeing was just all about the discourse around the show. And it’s like a bunch of us all seem to have to have discovered it. Like one weekend where we were like, okay, we’re gonna actually sit down and watch the gay hockey show. Um, and this is exactly what it is. It is a gay hockey show. So it is based on, there was a series of books that this, uh, female, uh, writer Rachel Reed wrote, um, uh, about like, uh, I think like they were like eBooks, types of thing. Um, uh, I think although there, there is now I [00:49:00] think like a, a hard cover release because they’ve been so popular and they’re just, it’s just ero, it’s just smut, right? It’s basically fanfic dressed up in something else. And the idea was like, okay, you have like these, you know, male like hockey players who are closeted and kind of have like this, this romance that, that starts from like 2008, um, through like, I dunno, like, like 2017 or 2018. And there are a number of different. Books or stories in the universe. But the one that people liked the most was the, the second book, which is called Heed Rivalry. You don’t really need to know any about that. The big thing about the show is that it is essentially like soft core gay porn. Um, but yet it’s like weirdly compelling in a way. Like, it, it is very, like, there’s, there’s some sweet aspects to it. Like you were before the, the show, you were saying, oh, it’s kinda like Heart Stopper could not be further from Heart Stopper. ’cause Heart Stopper is very sweet and twee and kind of like loving and like whatnot. This is like. You know, like guys in their twenties with amazing asses, [00:50:00] you know, like doing things to one another kind of an in secret. And, and the, the thing is, there’s not a whole lot of plot. Like the plot is the porn. Because, because the whole thing is, is that like they don’t spend, they don’t have a time to spend a lot of time together because they’re, they’re closeted and their rivals. Oh, that’s the whole conceit. It’s like they’re these two great hockey players and they, they, they, um, you know, um, play for opposing teams and they’re like, each other’s biggest rivals, but like, they’re, they’re fucking, um, and uh, it, it’s, uh, again, it’s not high art at all, but Brett: the target audience for this? Christina: And here’s the interesting thing. So the books are almost entirely read by women, um, and which, which makes sense. There’s, there’s a lot of like, you know, like, male, male, like, um, like the history of slash fiction goes back to like, like Fanfic in general, like goes back to like women writing, like Spock and, and, uh, um, what’s the space together? Kirk Together. Yeah. Um, and so the books are almost entirely, uh, consumed by, by women and probably straight women, although probably some queer women too. Um, but the [00:51:00] show seems to be a mix of gay men, straight women, all, although I’ve seen a lot of lesbians. As well. Um, yeah, yeah, because again, like the discourse is just kind of ridiculous and, and the memes are fun. Um, the guy who created it, he’s gay or created the, the, the television adaptation. He’s gay and, uh, I think he’s done a, a, a pretty good job with it. The, the leads are the thing that’s like incredible, like the, especially the guy who plays the, the Russian character, Ilya, uh, that actor is really, really good and he’s Texan, and yet he does like a great Russian accent and, um. And, and he’s very attractive. And like I, I, I can see like why a lot of people are into it, but it’s funny ’cause like New York Magazine, like they weren’t even covering the show, which, why would you, it was like some Canadian kind of, you know, you know, thing that barely gets picked by HBO. Then it takes off and now like they’re covering it. The, the last time I remember New York Magazine covering a show like this, like Vociferously was Gossip Girl, like 18 years ago. Um, [00:52:00] and it kind of reminds me of that, where like everybody woke up one day when they’re like, oh, this is like a cultural moment now. So again, not good television, probably not gonna necessarily be for everyone, but, but it’s a moment. And like, I kept seeing edits, I kept seeing Mo, I kept seeing edits on TikTok and stuff and I was like, okay, do I have to watch the gay hockey show? All right, I have to watch the gay hockey show so that it’s, we might be at the point where like TV is just okay, but at least there are some good like moments about, whereas the culture, we can all like agree. Okay, we’re all gonna be talking about this one thing. Brett: That sounds like what I’ll be doing on Christmas Day. Christina: Oh my God. Actually that would be a great thing to watch on Christmas. And I think that the final episode is gonna come out like the day after Christmas, so there you go. Brett: Done Deal. Cool. Wrapping Up and Holiday Wishes Brett: All right, well thanks for, we’re recording this the same morning. The show’s supposed to come out, so I gotta do some editing, but uh, but [00:53:00] thanks for showing up while you’re in Atlanta and yeah, this has been a classic, a fun classic Overtired. Christina: absolutely. Well, um, get some sleep, uh, take care of yourself. Um, happy holidays. Um, uh, hope that a, a Christmas isn’t too weird for you. And, um, and happy New Year. Brett: you too. Get some sleep.
Serve No Master : Escape the 9-5, Fire Your Boss, Achieve Financial Freedom
Welcome to the Artificial Intelligence Podcast with Jonathan Green! In this episode, we dive into how AI is reshaping the world of website building and small business marketing with our special guest, Pedro Sostre, a seasoned digital marketer and key leader at Builderall.He and Jonathan break down why so many “AI website builders” fail, what business owners actually need, and how to future‑proof your skills in an AI‑driven market.They explore the growing gap between what AI tools promise and what they actually deliver, especially for small business owners who are busy, overwhelmed, and not interested in becoming “prompt engineers.” Pedro explains how Builderall is tackling that challenge with pre-built, strategy‑driven funnels and AI‑assisted tools that do the heavy lifting in the background—so business owners can focus on running their business, not wiring together tech.You'll hear them discuss why design alone doesn't sell, how bad AI content is clogging the internet, and why the people who win won't be AI itself—but the humans who learn to use it better and faster than everyone else.Notable Quotes:“Right now people are expecting all sorts of different things, and the reality is they're generally getting junk, even if it looks good.” – [Pedro Sostre]“Whatever you think you have secure job security in today is probably not gonna exist in two years… You should be doing something different in three years.” – [Pedro Sostre]“People do not care which AI they're using. They don't care if the backend is Grok or DeepSeek or ChatGPT. They only care if it works.” – [Jonathan Green]“We're not gonna be replaced by AI. We're gonna be replaced by people who are better at AI than us.” – [Jonathan Green]“Train it to do what you do now, because your job needs to be different in two years.” – [Pedro Sostre]Pedro highlights how Builderall is evolving from “a big toolbox” into a guided, AI‑assisted marketing platform. With their new “builds,” a course creator, agency owner, or realtor can log in, choose their business type, and instantly see which tools to use, in what order, and how they all connect—without needing to touch APIs, Zapier, or complex integrations. It's like having a marketing consultant baked into the software, helping you deploy proven funnels instead of guessing your way through 25 different tools.Connect with Pedro Sostre:Website: https://www.builderall.com/ LinkedIn: https://www.linkedin.com/in/psostre/Pedro shares how Builderall is integrating AI behind the scenes to write copy, build pages, and connect tools for small business owners who don't have time (or desire) to learn complex prompting. Their focus is on making AI simple, contextual, and results‑driven—so users see more leads and sales, not just prettier websites.If you're a small business owner, agency, or creator wondering how to actually use AI to grow your business—without becoming a full‑time tech expert—this episode is a must‑listen!Connect with Jonathan Green The Bestseller: ChatGPT Profits Free Gift: The Master Prompt for ChatGPT Free Book on Amazon: Fire Your Boss Podcast Website: https://artificialintelligencepod.com/ Subscribe, Rate, and Review: https://artificialintelligencepod.com/itunes Video Episodes: https://www.youtube.com/@ArtificialIntelligencePodcast
Are legacy intermodal systems holding your operation back, and how long can the industry keep duct-taping technology together before it costs real market share? In today's episode, Alyssa Norcross from Revenova breaks down why intermodal freight still leans on AS/400 legacy systems that work but don't integrate, forcing teams to juggle multiple platforms, spreadsheets, and manual processes just to move freight. We dig into how fragmented tools create inefficiencies, data risks, and slow response times, why AI-driven automation inside a unified TMS is the real path forward for intermodal logistics, how Revenova is embedding automation to streamline tendering, rate management, load building, and visibility, while railroads step up real-time shipment tracking through APIs to meet rising shipper expectations shaped by the Amazon effect, the multi-modal cost comparison tools that will let shippers transparently weigh intermodal, truckload, and LTL options, and why operational execution, visibility, and reliability are now just as important as price in today's freight market!
After an 18-year rise through corporate HR—from recruiter to group president across Canada and the U.S.—Dom walked away from a “safe” executive career to build something on his own terms. In this conversation, we unpack why large organizations quietly trade momentum for bureaucracy, how technology and automation empower lean founders, and why “stability” often comes at the cost of creativity, speed, and meaning.We explore intrapreneurship vs. entrepreneurship, the hidden traps of bloated systems, and how founders can use data, automation, and open APIs to move faster without burning capital. The throughline isn't rebellion—it's agency. Building work that's fun, aligned, and alive again.No anti-corporate rant. Just lived experience, hard trade-offs, and a clear-eyed look at what it really takes to step off the stable path—and thrive.TL;DR* Stability is conditional: Corporate safety disappears the moment priorities shift.* Intrapreneur vs. founder: Big-company success doesn't equal personal leverage.* Tech as leverage: Automation and BI (not hype AI) unlock speed for lean teams.* Systems can trap you: CRMs and ERPs either enable growth—or become prisons.* Innovation dies slowly: Bureaucracy rewards optics over outcomes.* Work-life blend > balance: Fun, purpose-driven work creates sustainability.* Momentum matters: Small teams with clarity outperform slow giants.Memorable lines* “Stability often costs more than risk—you just don't see the bill right away.”* “Big systems don't fail fast. They fail quietly.”* “AI isn't magic—it's leverage if you know what problem you're solving.”* “Careers don't collapse overnight; they stall one approval layer at a time.”* “Fun isn't a perk—it's fuel.”GuestDominic Levesque — HR executive turned founder; CEO of NextWave; author and advisor on leadership, technology, and organizational transformation.