Podcasts about XML

Povinná elektronická fakturácia zasiahne od začiatku budúceho roka prakticky každý podnik na Slovensku. Zostáva polroka na prípravu, ako od budúceho roka fungovať s e-faktúrou E-faktúra nie je „pdf poslané emailom". Je to štruktúrovaný elektronický dokument vo formáte XML, vytvorený podľa európskej normy, ktorý umožňuje automatizované spracovanie v informačných systémoch. Povinnosť vystavovať e-faktúru sa od 1. januára 2027 vzťahuje na všetkých tuzemských platiteľov DPH pri transakciách s inými tuzemskými podnikateľmi, nezdaniteľnými právnickými osobami alebo orgánmi verejnej moci. No povinnosť prijímať e-faktúru je omnoho širšia — dotkne sa všetkých tuzemských zdaniteľných osôb vrátane živnostníkov, advokátov, notárov či prenajímateľov nehnuteľností, hoci sami platiteľmi DPH nie sú. „Táto prijímacia povinnosť je rovnako dôležitá ako povinnosť vystavenia e-faktúry, keďže sa týka oveľa širšieho okruhu osôb," upozorňuje Veronika Chválová Rajnohová, senior daňová manažérka z TPA Slovakia. Kľúčovým prvkom celého systému je takzvaný digitálny poštár — certifikovaný poskytovateľ doručovacej služby, prostredníctvom ktorého sa e-faktúry odosielajú, prijímajú a zároveň v reálnom čase oznamujú Finančnej správe SR. „Pri výbere digitálneho poštára je dôležité zamerať sa na spoľahlivosť a technické možnosti riešenia. Ak s ním nebudete spokojní, môžete ho kedykoľvek vymeniť," hovorí Miroslava Kvočáková, senior účtovná manažérka TPA Slovakia. Zoznam certifikovaných poskytovateľov priebežne zverejňuje finančná správa na svojom webe. Viac podrobností sa dozviete v podcaste.

In this episode of Partnerships Unraveled, we sit down with Eltjo Hofstee, Global Sales Director at EasyDMARC. Eltjo joined nearly four years ago with a clear brief: build a scalable sales organization around a product with strong market fit. That journey has taken him deep into how MSPs grow, sell, and redefine the value they bring to end customers.Eltjo opens with a concept reshaping how EasyDMARC thinks about its partner program: the shift from managed service provider to managed intelligence provider. The idea, which Eltjo credits to Pax8, moves MSPs away from SLA-driven metrics toward a more proactive, data-informed advisory role. MSPs already sit on a significant amount of customer data, and using that data to get ahead of issues is what separates a vendor from a genuine partner. EasyDMARC's own program reflects this: the company now helps MSPs not just deploy DMARC, but find new customers and sell adjacent services.DMARC generates an XML report for every email sent from a protected domain, and those reports tend to reveal more than end users expect. Organizations that assume they are too small to be targeted routinely discover, once they set up DMARC, that their domain is being impersonated constantly. The data also surfaces shadow IT, such as a marketing tool sending emails from an unconfigured source. That ongoing visibility is what keeps EasyDMARC relevant after initial setup: MSPs can build a proactive early warning system that adds clear, measurable value to every end customer conversation.What ties it together is a shift in orientation: from fixing problems to anticipating them. That is where the MSP role finds its next level of relevance._________________________Learn more about Channext

Strategic Technology Consultation Services This episode of The Modern .NET Show is supported, in part, by RJJ Software's Strategic Technology Consultation Services. If you're an SME (Small to Medium Enterprise) leader wondering why your technology investments aren't delivering, or you're facing critical decisions about AI, modernization, or team productivity, let's talk. Show Notes "It is providing you a… unified stack, a cloud ready stack for building distributed applications where the configuration… you can say the configuration files that we usually maintain, like YAML files, XML files, json files. So it is generally taken care of those nitty gritties."— Joydip Kanjilal Hey everyone, and welcome back to The Modern .NET Show; the premier .NET podcast, focusing entirely on the knowledge, tools, and frameworks that all .NET developers should have in their toolbox. I'm your host Jamie Taylor, bringing you conversations with the brightest minds in the .NET ecosystem. Today, Joydip Kanjilal returned to the show to talk about Aspire and where it fits in the modern enterprise application stack. We also talk about how Aspire isn't just for microservices or nanoservices, it will work quite well with modular monoliths, too. As long as your application code isn't highly coupled. "Maintaining large scale distributed systems requires deep visibility into… how the services are interacting, how the services are behaving over a period of time. So that helps enterprises to understand how the applications are behaving. If something goes wrong, what went wrong? Why is it that the application is not being able to scale? why is it not… able to handle, more you know, requests in a specific period? What are the security loopholes and everything?"— Joydip Kanjilal One side note: we recorded this episode shortly before Aspire was rebranded from ".NET Aspire". So if you're listening in wondering, "wait. That's not what it's called," please bear with us because we both used the old branding for half of the episode. Let's hope that the PM for Aspire, Maddy Montaquila, doesn't notice. Sorry Maddy. Before we jump in, a quick reminder: if The Modern .NET Show has become part of your learning journey, please consider supporting us through Patreon or Buy Me A Coffee. Every contribution helps us continue bringing you these in-depth conversations with industry experts. You'll find all the links in the show notes. Anyway, without further ado, let's sit back, open up a terminal, type in `dotnet new podcast` and we'll dive into the core of Modern .NET. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-8/aspirifying-the-enterprise-building-modern-apps-with-aspire-with-joydip-kanjilal/ Useful Links: Joydip's website Joydip's blog Joydip's GitHub Joydip's newsletter Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in Touch: Via the contact page Joining the Discord Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast. Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show. Editing and post-production services for this episode were provided by MB Podcast Services.

Doug McHoney (PwC's International Tax Services Global Leader) is joined by Will Morris, PwC's Global Tax Policy Leader, at PwC's Asia-Pacific Global Tax Symposium in Hong Kong. Will previously chaired the Business and Industry Advisory Committee (BIAC) Tax Committee for 10 years. Doug and Will discuss the acute uncertainty surrounding Pillar Two filing readiness as initial 2024 calendar-year deadlines approach, including the OECD's May 18, 2026, common understanding document, GIR central filing, local filing portals, XML schema differences, penalty relief, safe harbor elections, QDMTT and top-up tax returns, taxpayer outreach to BIAC, the OECD, and national governments, the OECD implementation toolkit, 52/53-week fiscal-year UTPR guidance, and unresolved dispute resolution questions. 

After a long hiatus, Podcast Idiot returns with a simple, local podcast RSS feed creator built with AI, supporting modern podcast tags, feed editing, and standalone XML generation without servers or subscriptions.

An airhacks.fm conversation with Martin Kouba (@martunek) about: ZX Spectrum Didaktik clone, Basic listings from ABC magazine, Laser Squad and Wall Breaker games, writing a Pascal fantasy strategy game called Fury as a teenager, first Java 1.4 contact at university, pushing Java 5 annotations against XML configuration in a first telco job, OC4J as Oracle Application Server with Orion lineage, switching to JBoss, seam framework as glue between backend and frontend, Hibernate, reporting a Seam security issue and being invited to Red Hat, CDI TCK migration from JBoss Test Harness to arquillian and from Subversion to GitHub, writing CDI and Bean Validation TCK with XML-based assertion extraction from the specification text, normative specifications producing high-quality LLM code generation for CDI, JAX-RS and JPA, prototype-first approach to writing API specifications, deprecation annotations needing since-version, removal-version and replacement, asynchronous CDI events and fireAsync, transactional observers, Java SE CDI container standardization and its removal from the MicroProfile Core profile, joining the Quarkus team from day one, building ArC as the build-time CDI implementation, why @Specializes is not supported in Quarkus, Qute templating library, Quarkus WebSocket Next and the limits of the Jakarta WebSocket API, Quarkus scheduler with Duration-based intervals, Quartz integration, Quarkus component test based on Weld JUnit, MCP Java SE STDIO server with zero dependencies using ServiceLoader and Function, building the Quarkiverse MCP server from the first MCP specification version, the missing MCP TCK and the new conformance test suite Martin Kouba on twitter: @martunek

Tune in to our weekly LIVE Mastermind Q+A Podcast for expert advice, peer collaboration, and actionable insights on success in the Probate, Divorce, Late Mortgage/Pre-Foreclosure, and Aged Expired niches!  Becky leads today's session, breaking down how to show up in Google search and AI overviews, map packs, and knowledge panels, while teaching four core components of SEO: on-site, off-site, technical, and local optimization. She demonstrates how to prove experience, expertise, authoritativeness, and trustworthiness (EEAT) with real results, credentials, client testimonials, and public mentions, and explains how to structure content and FAQs to feed AI tools like ChatGPT and Claude. The talk covers local SEO essentials: claim and optimize your Google Business Profile, maintain NAP consistency, gather recent reviews, respond to feedback, and manage local citations to strengthen the knowledge panel and map pack presence. We also discuss the shift toward AI summaries reducing clicks to organic results, the importance of mobile-first indexing, page speed, schema markup, XML sitemaps, and Google Search Console for crawl and error reporting. Finally, Becky walks through practical next steps, including a free site audit offer to diagnose gaps, present a tailored SEO plan, and set up a strategy call with a limited number of spots. Tune in for concrete actions you can implement today to build credibility online, attract more leads in probate, real estate, and other niches, and start generating consistent traffic from both organic listings and AI-driven results.   Key Takeaways:  - Build credibility with EEAT signals by showing experience, expertise, authoritativeness, and trustworthiness.  - Strengthen local visibility by claiming and optimizing your Google Business Profile and keeping NAP consistent.  - Prepare for AI-driven search by structuring content and using clear question-and-answer formats.  - Target high-intent keywords, keep content skimmable with headings and bullets.  - Grow via map pack and local citations to capture local searches.  - Use the free audit to identify gaps and create a tailored SEO plan.  - Collect fresh reviews after closings and encourage referrals to boost credibility.  To learn more, visit https://www.AllTheLeads.com or call (844) 532-3369 to check how many leads are available in your market.  #GoogleSEO #DigitalMarketing #LocalSEO #RealEstateMarketingPrevious episodes: AllTheLeads.com/probate-mastermindInterested in Leads? AllTheLeads.comJoin Future Episodes Live in the All The Leads Facebook Mastermind Group:  https://facebook.com/groups/alltheleadsmastermindBe sure to check out our full Mastermind Q&A PlaylistSupport the show

Lucas Allman joins the PowerShell Podcast for a conversation that starts with practical beginner wins and builds into bigger questions about AI, learning, community, and career growth in IT. The episode covers hands-on PowerShell use cases like event logs, scheduled tasks, and writing functions directly in the terminal, then shifts into Lucas's experience as a first-time PowerShell Summit speaker and his evolving perspective on AI as a tool for both productivity and learning. It lands on a strong human note, with Lucas reflecting on impostor syndrome, keeping up with change, and why curiosity and community still matter just as much as technical skill. Key Takeaways: · Event logs are a great early PowerShell win. Lucas walks through using Get-WinEvent to explore logs, filter for errors, search messages, and troubleshoot faster without waiting on the Event Viewer GUI. He also shares a practical tip for reusing XML or XPath filters from Event Viewer inside PowerShell scripts. · You can do more from the terminal than most people realize. Lucas explains how he writes full functions directly in the interactive shell, then saves them with a custom helper function so good code does not disappear when the session closes. It is a simple idea, but it opens the door to faster experimentation and building tools in the flow of work. · AI is changing how technical people work, but not eliminating the need for judgment. A big part of the Summit discussion centered on using AI as a collaborator, not a replacement. Lucas argues that the real opportunity is to offload repetitive work, learn faster, and free up more time for higher-value problem solving, while still applying technical knowledge and critical thinking to the results. Guest Bio: Lucas Allman is an IT automation specialist with a passion for building practical, scalable solutions using PowerShell. With deep experience in endpoint management, configuration as code, and Microsoft cloud services like Intune and Graph API, Lucas focuses on making complex workflows maintainable, secure, and efficient. He's an advocate for knowledge sharing and enjoys helping others level up their scripting and automation skills through real-world examples and interactive problem-solving. He had ChatGPT write this bio and says it's close enough. Resource Links: · Lucas Allman website: https://lucasallman.com · Connect with Andrew: https://andrewpla.tech/links · PDQ Discord: https://discord.gg/PDQ · PowerShell.org GitHub organization: https://github.com/powershellorg The PowerShell Podcast on YouTube: https://youtu.be/kcjkCS0QN64  

https://clearmeasure.com/developers/forums/ Chet Husk is a Product Manager on the .NET Tools team at Microsoft, where he leads the .NET SDK, MSBuild, Template Engine, and Install Scripts teams -- shaping how millions of .NET developers build, publish, and containerize their applications. Before joining Microsoft in 2021, Chet was deeply embedded in the F# open-source community, serving on the F# Software Foundation Board and co-maintaining Ionide, the popular F# extension for VS Code. At Microsoft, he drove the built-in container publishing support that lets developers create container images with just "dotnet publish" -- no Dockerfile required -- and recently shipped SLNX, the new XML-based solution file format for the .NET CLI. He is also exploring the intersection of AI and build tooling with an open-source MCP server that lets AI assistants analyze MSBuild binary logs. Mentioned in this Episode GitHub LinkedIn .NET Blog Recent projects / posts Blog: "Introducing support for SLNX, a new, simpler solution file format in the .NET CLI" (Mar 2025, .NET Blog)  mcp-binlog-tool: MCP server for AI-assisted MSBuild binary log analysis  Blog: "Announcing built-in container support for the .NET SDK" (.NET Blog) .NET Conf 2023 talk: ".NET Containers advancements in .NET 8"  .NET Conf 2022 Keynote presenter  SLNGEN .NET Tool /dotnet/skills GitHub repo structed nuget package - devlooped EBNF Grammar (Extended Backus–Naur Form) https://msbuildlog.com/ https://github.com/devlooped/StructId Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Favour Obasi-ike, MBA, MS breaks down why every business website needs an active, well-structured blog. He introduces content pillars — long-form foundational articles around 3,000 words — and content clusters, shorter supporting articles around 700 words that link back to the pillar to build semantic authority. The session also covers how embedding multimedia like YouTube videos and infographics increases "in-view" time and reduces bounce rates. It closes with Favour revealing his background as a music producer and playing an original instrumental track live.Who is this for?Business owners, content creators, and digital marketers who want to turn their website blog into a long-term traffic and authority asset — especially anyone publishing content inconsistently or without a proper content structure.Key Moments & Timestamps01:33 — Why every business website needs an active blog and a structured sitemap.04:21 — How embedding YouTube videos retains traffic and intellectual property on your domain.65:01 — Understanding content pillars (3,000 words) vs. content clusters (700 words).68:00 — How infographics increase content shares by up to 300% and lower bounce rates.143:10 — Favour reveals his music production background and plays an original instrumental track live.FAQsQ: Why embed a YouTube video instead of sharing the link?A: Embedding keeps traffic and intellectual property on your domain, increasing "time on page" and sending positive ranking signals to search engines.Q: What is the difference between a content pillar and a cluster?A: A pillar is a comprehensive long-form article on a broad topic. A cluster is a shorter article that links back to the pillar, building semantic authority over time.Q: Do people still read blogs in 2026?A: Yes. While many people skim, search engine bots read everything — and AI tools like ChatGPT, Siri, and Alexa pull answers directly from published blog content.Action StepsAudit Your Sitemap: Confirm your blog is active and properly indexed in your XML sitemap.Embed Your Media: Keep traffic on-site by embedding YouTube videos and podcast episodes directly into blog posts.Build Content Pillars: Write one comprehensive pillar article, then support it with 3–5 shorter cluster articles that link back to it.Use Infographics: Add visual elements to increase screen time and lower your bounce rate.Refresh Old Content: Update popular older posts with new information to keep them evergreen and re-indexable by search engines.Ready to Rank? Book Your SEO & Web Dev Services Today

Welcome to an inside look at how our devs are testing out where AI can help versus hinder every day work conundrums. Our team's focus in this meeting is Claude Cowork, a tool designed to track everything within a specified local folder.As for team demonstrations and discussions, Xandon uses a plugin that parses FileMaker XML to generate web-based code reviews and actionable recommendations. Nick showcases a clever approach to token efficiency, using Python scripts to convert verbose XML data into a concise format that LLMs like Claude and Gemini can process with greater accuracy.Beyond development, the team shares their real-world applications of AI assistants, like John generating precise 3D printing step files based on scanned images and measurements.

An airhacks.fm conversation with Christofer Dutz (@christofer-dutz) about: discussion about Apache PLC4X as the JDBC of industrial automation, the API and SPI architecture with Java service loader for driver discovery, Modbus protocol for HVAC systems and heating devices, PLC4X core API operations including discovery and browsing and reading and writing and subscribing and publishing, multi-language support with PLC4J for Java and PLC4Go for Go and PLC4Py for python and C#, code generation from protocol definitions using language-specific templates, XML-based cross-language unit tests, OPC UA as the Esperanto of industrial protocols versus PLC4X speaking native device protocols, OPC UA overhead causing PLC strain and network congestion, comparison of OPC UA to CORBA and grpc, CORBA IIOP protocol on devices, bidirectional communication for reading sensor data and writing control flags, subscription-based event-driven data collection to reduce PLC polling load, founding ToddySoft to provide commercially supported open source industrial products, the gap between open source libraries and industrial consumption, ToddySoft Connect as bubble-wrapped PLC4X drivers for platforms like Inductive Automation Ignition, eliminating edge gateway boxes on shop floors, native protocol communication reducing network load on 100 Mbit industrial networks, unified namespace concept as JMS for industrial automation, Apache IoTDB as time series database with push queries and callback features, Apache TsFile storage format for writing time series data directly on PLCs, shifting from polling to pushing in industrial data collection, ToddySoft File as C libraries compiled for PLCs, ToddySoft DB as embedded stripped-down IoTDB for edge devices, ToddySoft Edge as the combined platform resembling an application server for industrial automation, Industry 4.0 definition and evolution from manual labor through steam power through PLC automation to connected production, compressed air as a service business model, early failure detection in multi-step production lines, OSGi runtime driver loading, Eclipse Tycho build system difficulties, Kafka Connect PLC connectors, SPS fair in Nuremberg as one of the largest industrial automation fairs, signal theory and Nyquist sampling rate in PLC polling Christofer Dutz on twitter: @christofer-dutz

System.Xml.XmlElement

For all those who missed out on London, see you in Miami next week!Notion, the knowledge work decacorn, has been building AI tooling since before ChatGPT, with many hits from Q&A in 2023 and unified AI in 2024 and Meeting Notes in 2025. At the end of their last Make user conference, Ryan Nystrom teased Notion 3.0's Custom Agents - and they are finally embracing the Agent Lab playbook!Sarah Sachs and Simon Last of Notion join us for a deep dive into how Notion built Custom Agents, why it took years and multiple rebuilds to get right, and what it means to turn a productivity tool into an agent-native system of record for enterprise work.We go inside the product, engineering, evals, pricing, and org design decisions behind one of the most ambitious AI product efforts in software today — from early failed tool-calling experiments in 2022 to agent harnesses, progressive tool disclosure, meeting notes as data capture, and the long-term vision for software factories and agentic work.We discuss:* Sarah and Simon's path to launching Notion Custom Agents, and why the feature was rebuilt four or five times before it was ready for production* Why early agent attempts failed: no tool-calling standard, short context windows, unreliable models, and too much complexity exposed to the model* The “Agent Lab” thesis: not just wrapping a model, but understanding how people collaborate and building the right product system around frontier capabilities* How Notion thinks about roadmap timing: not swimming upstream against model limitations, but also building early enough that the product is ready when the models are* Why coding agents feel like the kernel of AGI, and how Notion is thinking about “software factories” made up of agents that spec, code, test, debug, review, and maintain codebases together* How Sarah runs AI engineering at Notion (“notes from Token Town”): objective-setting over idea ownership, low-ego teams comfortable deleting their own work, and a culture designed to swarm around fast-changing opportunities* The “Simon Vortex,” company hackathons, and why security gets pulled in early rather than late* How Notion organizes AI: core AI capabilities and infrastructure, product packaging teams, and a broader company mandate that every product surface must increasingly work for both humans and agents* Why prototypes have become much easier to build internally, and how “demos over memos” changes product development inside a tool the whole company already uses every day* Notion's eval philosophy: regression tests, launch-quality evals, and “frontier/headroom” evals that intentionally only pass ~30% of the time so the company can see where model capabilities are going* What a “Model Behavior Engineer” is, and why Notion treats eval writing, failure analysis, and model understanding as a distinct function rather than just software engineering* The changing role of software engineers in the age of coding agents, and why the new job looks less like typing code and more like supervising a rigorous outer system of agents, PRs, and verification loops* How the “software factory” should work: specs, self-verification, bug flows, subagents, and minimizing human intervention while preserving the invariants that matter* A live walkthrough of a Notion Custom Agent handling coworking space tenant applications by triaging email, enriching applicants with web search, and writing structured data into a Notion database* How agents compose inside Notion: shared databases as primitives, agents invoking other agents, “manager agents” supervising dozens of specialized agents, and memory implemented simply as pages and databases* Notion's take on MCP vs CLI: why Simon is bullish on CLI's self-debugging nature, where MCP still makes sense, and how Sarah thinks about capability, determinism, permissioning, and pricing alignment* The evolution of Notion's internal agent harness: from early JavaScript coding agents, to custom XML, to Markdown and SQL-like abstractions, to tool definitions, progressive disclosure, and a much shorter system prompt* Why Notion cares about teaching “the top of the class,” building for sophisticated operators rather than abstracting away too much capability for everyone* How agent setup works today: agents that can configure themselves, inspect their own failures, and edit their own instructions — with guardrails around permissions* How Notion prices Custom Agents: credits as an abstraction over tokens, model type, serving tier, web search, and future sandbox costs; why usage-based pricing was necessary; and how “auto” tries to match the right model to the right task* Why Notion is not eager to train a foundation model, where they do fine-tune and optimize today, and why retrieval/ranking is one of the most important investment areas as more searches come from agents rather than humans* Why Meeting Notes became one of Notion's strongest growth loops: not just as transcription, but as high-signal data capture that powers search, custom agents, follow-up workflows, and the broader system of record for company collaboration* Why Notion is more interested in being the place where collaboration data lives than in building hardware themselves — and how wearables or other capture devices may eventually feed into that systemSarah SachsLinkedIn: https://www.linkedin.com/in/sarahmsachsX: https://x.com/sarahmsachsSimon LastLinkedIn: https://www.linkedin.com/in/simon-last-41404140X: https://x.com/simonlastFull Video EpisodeTimestamps* 00:00:00 Introduction and launching Notion Custom Agents* 00:01:17 Why Notion rebuilt agents four or five times* 00:03:35 Building for where models are going, not just where they are* 00:05:32 The Agent Lab thesis, wrappers, and product intuition* 00:08:07 User journeys, leadership, and low-ego AI teams* 00:13:16 The Simon Vortex, hackathons, and bringing security in early* 00:16:39 Team structure, demos over memos, and building for agents* 00:20:25 Evals, Notion's Last Exam, and the Model Behavior Engineer role* 00:27:37 Evals as an agent harness and the changing role of software engineers* 00:30:42 The software factory: specs, verification, and agent workflows* 00:32:18 Live demo: a custom agent for coworking space applications* 00:35:08 Composing agents, manager agents, and memory as pages* 00:38:15 Notion Mail, Gmail, native integrations, and tools* 00:39:43 MCP vs CLI and the cost of capability* 00:44:13 When Notion uses MCP vs building its own integrations* 00:47:43 The history of Notion's agent harness rebuilds* 00:55:35 Power users, public tools, and the setup agent* 00:58:01 Self-fixing agents, permissions, and “flippy”* 01:01:13 Pricing, credits, and choosing the right model automatically* 01:09:01 Why Notion isn't training its own frontier model* 01:14:07 Retrieval, ranking, and search built for agents* 01:17:27 Meeting Notes as data capture and workflow automation* 01:21:18 Wearables, hardware, and Notion as the system of record* 01:23:45 OutroTranscript[00:00:00] Alessio: Hey everyone. Welcome to the Latent Space podcast. This is Alessio founder of Kernel Labs and I'm joined by swyx, editor of the Latent Space.[00:00:11] swyx: Hello. Hello. We're back in the beautiful studio that, uh, Alessio has set up for us with Simon and Sarah from Notion. Welcome.[00:00:18] Sarah Sachs: Thanks for having us.[00:00:19] Alessio: Thanks for having us. Yeah.[00:00:20] swyx: Congrats on the launch recently the custom agents, finally it's here. How's it feel?[00:00:26] Sarah Sachs: We ship things slowly. So it had been in Alpha for a little bit and at the point at which is it's an alpha, um, there's a group of people that are making sure it's ready for prod, and then there's a group of people working on the next thing.So sometimes some of these launches are a bit delayed satisfaction, so it's quite nice to remind yourself all the work you did because we do have a habit of like. Being two or three milestones ahead. Uh, just ‘cause you have to be, you know, you can't get complacent. Um, but it's been great that people understood how this is helpful.And I think that's just easier in general building AI tools today than it was two, three years ago. People kind of get it and so that user education, um, there's just, it was our most successful launch in terms of free trials and converting people and things like that. It was really successful, so yeah.But there's a lot to build.[00:01:12] swyx: Making it free for three months helps.[00:01:16] Sarah Sachs: Yep.[00:01:17] Simon Last: It was definitely super exciting for me because it's probably the fourth or fifth time that we rebuilt that.[00:01:22] swyx: Yes.[00:01:23] Simon Last: And I mean,[00:01:24] swyx: you've been building this since like 20, 22.[00:01:26] Simon Last: Yeah, I mean, like, it was even right when we got access to like GPT four in late 20 22, 1 of the first ideas we had is like, oh, okay, let's make an agent that I, we used the word assistant at the time, there wasn't really the word, the word agent yet, but, oh, we'll give an access to all the tools the notion can do, and then it, we run in the background like, like do work for us.And then we just tried that many times and it just. Was too early. Um,[00:01:48] swyx: I need to force you to like double click on that. What is too early? What didn't work?[00:01:52] Sarah Sachs: We were fine to, like, before function calling came out. We were trying to fine tune with the Frontier Labs and with fireworks, like a function calling model on notion functions.This is right when I joined. I joined because, um, we needed a manager as Simon was needed to be able to go on vacation. So, uh, that's, that's around when I joined, so you can speak much more to it.[00:02:11] Simon Last: Yeah, we did partnerships with both philanthropic and open AI at different times, uh, to try to, at the time the, I mean, when we first tried, there wasn't even a constant of like tools yet.We, we sort of designed our own like, like tool calling framework and then we tried to fine tune the models to, uh, to use it over multiple turns. Um, and because it, it didn't work well out the box, I think. Yeah. The models are just too dumb and the context thing was also way too short.[00:02:37] Alsesio: Yeah.[00:02:37] Simon Last: Um, and yeah, we just kind of banged our head against it for a long time.Uh, unfortunately it was always like, there was always like sort of. Glimmers that it was working, but um, it never felt quite robust enough to be like a useful, delightful thing. Um, until I would say, uh, the big unlock was probably like Sonic 3.6 or seven, uh, early last year. And that's when we started working on our agent, which we shipped last year.Um, and then, and then uh, uh, custom agents, kinda a similar capability and that, that one just took longer because we, we just wanted to get the reliability up a lot higher. ‘cause it's actually running in the background.[00:03:14] Sarah Sachs: And the product interface of like permissions and understanding, you know, this custom agent is shared in a Slack channel with X group of people and has access to documents that are surfaced to Y group of people.And the intersect experts, Y might not be whole. And so how do you build the product around making sure administrators understand that permissioning took multiple swings.[00:03:35] Alsesio: Everything is hard back at the end of the day. Yeah. I'm curious, like when the models are not working, how do you inform the product roadmap of like, okay, we should probably build, expecting the models to be better at some reasonable pace, but at the same time we need to, you know, you had a lot of customers in 2022.It's not like you were a new company or like no user base.[00:03:54] Simon Last: Yeah, I mean I think there's always the balance of, you know, like you want to be a GI pilled and thinking ahead and building for where things are going. Uh, but also you wanna be like shipping useful things. And so we always try to like, like keep a balance there.You know, we. We try to take clear, like a portfolio approach. You know, we're always working on multiple projects and, and we're always trying to work on, you know, maintaining things where that have already shipped, like, like shipping new things that are like eminently working well and make them really good.And, and then we wanna always have a few projects that are a little bit crazy. Um,[00:04:23] Alsesio: and what are the a GI peel projects that you have today? I'm curious about, uh, you don't have to share exactly what you're working on, but I'm curious what are things today that maybe in 18 months people will be like, oh, obviously this was gonna work[00:04:35] Sarah Sachs: 18 months.[00:04:37] Alsesio: Yeah, 18 months is, you know,[00:04:37] Sarah Sachs: it's a long time and Yeah. Yeah.[00:04:39] Simon Last: I mean, there's a number of things happening. I think one thing that's becoming more clear is I think like, like, uh, coding agents are the kernel of EGI, sort of, everything is a coding agent. Mm-hmm. I think that's, that's sort of one, one direction.Um, and then, yeah, the exciting thing about that is sort of your agent can sort of bootstrap its own software and capabilities and actually debug and maintain them. And so yeah, we're, we're, we're thinking a lot about that. And then, yeah, like, like another category of things that I'm, I'm really excited about is like, uh, we call the software factory also.People are using this, uh, this, this sort of word. Um, basically it just means can you create sort of like a, as automated as possible, a workflow for developing debugging. Mm-hmm. Merging, reviewing, and maintaining a code base and a service where there's a bunch of agents working together inside, and like, like how does that work?[00:05:28] Sarah Sachs: If you think back to your initial question, like, why did this take so long? I think something,[00:05:32] swyx: I didn't say that, but Yes. Okay. Go ahead.[00:05:34] Sarah Sachs: Why, what, what changed over the three and half years of trying[00:05:37] swyx: it? Exactly. Right. Because most people always say like, it didn't work yet. Then reasoning models came, then it worked.I was like, okay, let's go a little[00:05:43] Sarah Sachs: bit. That's, I mean, that's part of it, but I think the other part of it that I actually think is really what will set notion apart for every new capability is we have like. Two skills that are crucial when it comes to frontier capabilities. One is not letting yourself swim upstream.So like quickly realizing if you're just pressing against model capabilities versus not exposing the model to the right information, not having the right infrastructure set up. That and of itself is the skill of intuition. And the second is to see, okay, you're not swimming upstream. Which direction is the river flowing and what is like, how do we think ahead about the product and start building it even if it's not great yet, so that when it is there, we're ready for it.Right? And like those can sometimes feel like counterintuitive things. Like we can be trying to fine tune a tool calling model when they don't exist yet. And that the trick is to not do that for too long, but realize that there was something there. And we've had a lot of things which like, um, we're just like not swimming in the right direction with the streams.I think we had multiple versions of transcription before we got meeting notes, right? Oh, I gotta talk[00:06:39] swyx: about that. Yeah.[00:06:40] Sarah Sachs: Yeah. Um, and so. I, I, I think that like we, we really closely partner with the Frontier Labs on capabilities and we also have to have strong conviction on, as those capabilities move.Notion is about being the best place for you to collaborate and do your work. And how does that narrative change if the way that we work changes?Yeah.[00:06:58] swyx: Yeah. You told me you were a fan of the Agent Lab thesis, and this is, this is kind of it, right?[00:07:02] Sarah Sachs: Right. I show that thesis to so many candidates. Like I have it as like micro chrome autofill.Um, at this point, like it's one of my most visitations[00:07:10] swyx: because like, is this the, here's why you should work in notion and not open, open eye. I, it's like,[00:07:14] Sarah Sachs: here's, here's what's different about it.[00:07:16] swyx: Yeah.[00:07:16] Sarah Sachs: And here's why. It's not just a rapper. I actually think more and more people understand it's not just a wrapper.[00:07:21] swyx: Yeah.[00:07:22] Sarah Sachs: Um, and by the way, like in the beginning, parts of what we build are wrappers on functionality. That works well, of course, but that's not really the most, um. I would say that's not the product that, that drives revenue. And that's not necessarily always what users need.[00:07:35] swyx: I mean, you know, notion is the AWS wrapper, but like the, the wrapper is very beautiful and like very, very well polished.So[00:07:40] Sarah Sachs: like the analogy,[00:07:41] swyx: like[00:07:42] Sarah Sachs: the analogy that I've been coming back to his Datadog in AWS[00:07:45] swyx: Yeah.[00:07:46] Sarah Sachs: So, uh, Datadog could not exist with, without cloud storage. Right. That it's kind of fundamental that that works. Um, and AWS has like a CloudWatch product, but Datadog is an expert on understanding how people want observability on the products they launch.And we're experts in understanding how people wanna collaborate, and that's really where our expertise lies.[00:08:04] swyx: Totally.[00:08:04] Sarah Sachs: Um, regardless of the tools that we use,[00:08:07] Alsesio: I'm kind of curious how you think about implicit versus explicit expertise. I feel like Datadog is half and half implicit and explicit. It's like they understand across markets and industries what engineering teams usually look for.With notion, it's almost like more of the expertise is at the edge because you as a platform, you're like so horizontal that the end user is not really the same. Mm-hmm. Like with Datadog, the end user is always like, yeah, an engineering lead, a kinda like SRE related person with notion. It can be anything.So I'm curious how you put that expertise into a product versus, you know, obviously it, WS cannot build notion. It's, that doesn't quite work in this case, but[00:08:44] Simon Last: it's, it's a little bit differently shaped. I think, you know, a classic vertical SaaS, like the data is kind of like that. They understand their individual customer very deeply.It's kinda a narrow slice, um, notion has always been super horizontal. And our, our task has always been to sort of balance these two somewhat opposing forces of like, we're listening to our customers and what they want us to build. It's a broad slice. And then also we're thinking about like, okay, how do we decompose what they want into, uh, nice primitives that are, that are really nice to use and we'll, we'll get us like as much bang for the buck as possible.And then, you know. Maintain the whole system, make it all like, like super clean and nice to use.[00:09:22] Sarah Sachs: We still have user journeys. I mean, we still focus on like core. I actually think the failure of our team is when we focus too much on what are cools that are, what are tools that are[00:09:31] Simon Last: mm-hmm.[00:09:31] Sarah Sachs: Cool tools. I actually think that's when we make have the least velocity because you still need some sort of focus on a user journey.So like for instance, we'll all sit down every Friday and look at the P 99 of like the most token exhaustive custom agent transcript and just look at why it didn't do well and cut a bunch of tasks. Like we still focus on like, this has, like this should work. Email triaging should work. Mm-hmm. Right. And similarly, like when we're talking about before building, um, chatting, um, before we started filming about, okay, how can I do PDF export?Well that's functionality that then merits. Maybe we should build a tool that has access to a computer sandbox in a file system and the ability to write code. Right? Right. Um, but it's because we're thinking about the fact that our users to do their, to do their daily work, need to export PDFs, not because we're like, Hmm, I think a computer tool could be cool.Like, let's just see what happens. Mm-hmm. Like we, we have to focus on some user journeys, otherwise we just don't have like, enough strategy to, to prioritize.[00:10:29] swyx: I think there's a lot of like really strong opinions that you've had. Do you have like sort of like a towel of Sarah Sachs? Like, you know, like what, how do you run your team?Like I feel like you just have accumulated all these strong opinions. Obviously part, part of this is your, your token town thing.[00:10:43] Sarah Sachs: I think the TAs working with Service X is, um, you'd have to, it depends who you ask. Um, I think it depends if you're on my team or a partner Right. Or a vendor.[00:10:54] swyx: Yeah. There other people want to run their teams the way that you're Yeah.You're like bringing these things. And then also similarly, uh, Simon, when you did the custom agents demo, you had like, well, we've been using custom agents and here's the super long list of everything that we do. No humans ever read it. Right? That's what you said. I was like,[00:11:07] Sarah Sachs: yeah. So I think for, for me, um, something that I learned very quickly and became very comfortable with was that my job was not to be the ideas per person or the technical expert.My job was to make it so that everybody understood the objective, had a resource to help prioritize what they should work on, and had an avenue to prioritize what they thought was important. And I think that's true with all, all leadership, but I think especially on the AI team. Almost all of our best ideas come from prototypes, from people that have a cool idea because they saw a user problem, and it's a huge disservice if all of those ideas have to pass, like the sniff test of what me and a product partner or Simon and Ivan decided were the direction, right?Because a lot of what we're doing is leaning into capabilities, so. I think that's the first thing is like, I don't really view like the role of engineering leadership as like, uh, hierarchical, nor has it ever been, but especially now, like very willing to change direction based on, um, like proof is in the pudding.Yeah. And like, and I think we have rebuilt our harness three or four times. And when you do that, then the second rule of engineering leadership is like you need to build a team that's comfortable deleting their own code and is very low ego and is driven by what's best for the company. And, um, doesn't write design docs because they think it's their promotion packet.Right. And that's a culture that notion had long before I joined, but like our willingness to just swarm on different problems and um, redo things that we've built before because something has changed. Like, there's a lot of friction that can happen at companies when you do that. And it doesn't happen at Notion.And because it doesn't happen when new people join. Like they don't wanna be the ones that are saying, we shouldn't do this. I wrote that code. So then it's, you know, you, you create a culture that everyone thoughts and that culture comes directly, I think from Simon and Ivan though, um, because they're very open-minded.[00:12:50] swyx: Anything that you,[00:12:50] Simon Last: you'd add? I'm not a manager, like, like, like Sarah is. Um, a lot of my role is really to try to think a little bit ahead, make sure that we're, we're building on the right capabilities and then like the prototyping stuff. And yeah, it's really, really critical to always just be starting again.It's like, okay, this is new thing. What does this mean? What if we just rethought everything or wrote everything? And so I, I'm, I'm basically just doing that in a loop every six months.[00:13:16] swyx: Yeah. Do you believe in internal hackathons for this stuff?[00:13:19] Sarah Sachs: I think there's like two different versions. So one is like, we just have a, a, a solid bench of senior engineers that come and go on what we call the Simon Vortex and Productionizing what we built, right?Because when you're in the Simon Vortex, the velocity is super high. The direction changes daily, and it's meant to be like the equivalent of a SC Works lab. We don't need to do hackathons for that. We need to have senior engineers that we trust to come in and out of those projects. For instance, like management boundaries are really loose.Like you report to him, but you work for her right now. Yeah. That's something that when we hire managers, it's important they don't care about because we tend to form more structures. Yeah. Don't be too[00:13:54] swyx: territorial.[00:13:55] Sarah Sachs: We form more. It's after we ship things, not not before, just historically. Um, the second thing is we do have companywide hackathons.Actually we just had our demos day for the hackathon we had last week this morning. That's more for people that aren't directly working on the project, feeling like they have the time to pause and learn how to make themselves more productive or how they would use notion custom agents to build something.Or part of the hackathon was actually encouraging everyone across the company to build their own agentic tool loop, calling from scratch. Follow like an every blog post on how to do what I think because we want[00:14:26] swyx: just with the compound engineering one. Yeah.[00:14:28] Sarah Sachs: We want everyone to use cloud code in the company or whatever the coding agent they please and understand that fundamental.So we set aside a day and a half. We're all leadership, encourage everyone on their teams across the company to do it. So we have hackathons like that. I would say like kind of facetiously, like everything we build is a little bit like a hackathon until it graduates and puts on big boy pants and as a product ops rollout leader and has a assigned data scientists and stuff like that,[00:14:54] swyx: security review enterprise stuff,[00:14:56] Sarah Sachs: actually security reviews one of the things that we bring in first because it just slows us down way more and, um, causes a lot of tension and they build better product if they're involved early.So, um, that is probably the first person to get involved in something that's the[00:15:09] swyx: right PR approved answer.[00:15:10] Sarah Sachs: No, but it's not just PR approved. It like, um, um, it's[00:15:13] swyx: actually real. It's actually real. It's like, um, I'm just saying scar[00:15:15] Sarah Sachs: tissue.[00:15:15] swyx: Yeah,[00:15:16] Sarah Sachs: because like, you know, my background's also, I worked at Robinhood for a number of years.Yes. So like, uh, compliance and things like that, um, are a little bit more, you learn the hard way when it doesn't come naturally.[00:15:26] Simon Last: Yeah. I think the. The hackathon is really important for uplifting the general population, but like, if that's the only way you can build new things, you're kind of toast. I mean, it, it has to be like the daily processes, like, you know, building these new things.Um, and it has to be about, I think like, I think in the AI era a lot more leverage accumulates to the most curious and excited people. And so it's like we're all about just like activating that energy. You know, like if someone's protesting something on the weekend that they're excited about and it's important, that should be the main thing that we're doing.Yeah. Um, it's not a hackathon that we schedule once a quarter, it's just like, yeah. Daily process. Part of the culture.[00:16:02] Sarah Sachs: I mean, that's how we shift image generation and notion now. It was always this thing that would be kind of nice to have, but it wasn't really clear where that was necessarily aligned in product priorities.It'd be a lot of work. And we had someone on the database collections team, Jimmy, who was like. I really wanna do image generation for cover photos and inside notion. And we're like, if you wanna build it, like it's, do it please. Like we encourage you. We gave ‘em all the resources of working directly with Gemini and being able to like track the token usage and it working through endpoints.We gave them eval, support, everything, and then became a, a full project.[00:16:34] Alsesio: Yeah.[00:16:35] Sarah Sachs: That's why you can't have like ego as a, a leader. Like that's, that's how we work.[00:16:39] Alsesio: What's the size of the team today, both engineering and overall?[00:16:43] Sarah Sachs: I manage, uh, the team. That's what we'll call it. Core AI capabilities and infrastructure.That's about 50 people. But then we have per i partner teams that do packaging. So how it shows up in the corner chat versus custom agents versus meeting notes, that's another 30, 40 people. And, and then every team that has a product service at Notion that a user can interface with owns the tool that the agent interfaces with the editor team.The team that did CRDT for offline mode is the same team that handles how two agents, um, edit competing blocks. Mm-hmm. Right? It's the same problem. The team that built the underlying SQL engine is the same team that owns how the agent asks it to run a SQL query, and it does it performantly. And so from that regard, anyone working on product engineering is tasked with making them work for customers that are humans and agents because over time the majority of our traffic will be coming from agencies using in our interface, not humans.And so. Our objective is to make it so that the whole product org is building for agents.[00:17:40] Alsesio: Yeah. How has it changed internally? The activation bar is kind of lowered a lot. Like anybody can kind of create a prototype very, somewhat easily, especially if you're like an existing code base. Have you raised the bar on like what type of prototype people need to bring forward to gonna be taken?Not like seriously, but like, you know what I[00:17:58] Simon Last: mean? Yeah. I think the bar is lowered in many ways. Be like, one thing our, uh, our team built that is really cool is our, uh, our, our design team made a whole separate GitHub repo, uh, called the, the design Playground. And it's basically just to create a bunch of like, like helper components and you, uh, for, for quickly a throwing together UIs.And it's become like actually quite sophisticated. Like it has like an agent in there and like, uh, that's pretty fun. So like, we pretty much, like, they don't do mocks, they just make like, like full, full prototypes.[00:18:27] swyx: Here it is. It works.[00:18:28] Simon Last: They give you like a u rl. They're like, okay, all right. So we have to make the, like the real production version of that.Um, and then for engineers. A prototype looks like just making it a feature flag that actually works. Like that's sort of the bar.[00:18:39] Sarah Sachs: Something to understand that's really unique about notion. One of the reasons I joined we're super lucky is no one uses Notion in their job as much as people that work at Notion.[00:18:46] Simon Last: Of course.[00:18:47] Sarah Sachs: So I think there's very few companies, maybe if you worked on Chrome I guess, but like everything that we ship, we ship internally first and get a lot of really quick feedback. And also sometimes our dev instance is totally borked and you have to change a bunch of flags to get things done. And that's kind of like, but everyone, so people that do it ticketing, people that do supply chain procurement, recruiting, everyone is using the same instance of notion with like a lot of flags on for these prototypes people build.Um, and so we have this, Brian Levin, one of the designers on our team, I think evangelize this concept of demos over memos.[00:19:18] swyx: Ooh, too[00:19:20] Sarah Sachs: good. Um, which has been, uh, very good for building demos, and I think it's put a big pressure point on us to have really strong product conviction, because if anything can be demoed, you really need a strong filter of making sure that if you know, you're doing X amount of work, you're making the, you're, you're focusing on one tower, you're not just building a really flat hill.Right. That's actually where I think there has to be more conviction from our PMs, um, and our designers and, and well, the company really to have conviction of what journey we're going on.[00:19:52] Simon Last: But overall, I feel like it works pretty well. Like people, almost all the engineers have good enough taste to realize that like, this prototype doesn't actually make sense in the product, or, or it does.So it's not that common that I would see a prototype. It's like, oh, this makes no sense. Mm-hmm. It's like, you know, people are doing reasonable things and, and, and then it's just a matter of. Which things we build first and then often just, just figuring out how to turn it on and off. There's our, in the, in our like experimental chat ui, there's this, there's probably like, like a hundred check boxes in there.[00:20:22] Sarah Sachs: Kills me[00:20:23] Simon Last: the things you could turn on and off.[00:20:25] Sarah Sachs: Uh, but I think that, okay, so that is kind of true, Simon, but like being the person that manages the evals team, like there is a level of intensity that it adds to the platform team. So, you know, if we're gonna do image generation and notion, all of a sudden the way that we do attachments and the way that we, um, our LLM completion like cortex talks and expects tokens back and now it's getting images back.Like there's a lot of platform work that we do need to, like solidify a little bit. So sometimes it'll be in dev for a couple weeks before it makes it to prod just because we still have to like, make it robust, make it HIPAA compliant, ZDR compliant, figure out the right contracting with the vendor, whatever it is.And we need to eval it because we want the team. To still maintain what they build. That's the one thing is like if we have a bunch of prototypes, it can't just be like a small group of people that then maintain whatever end prototypes. So we have invested a lot of people in an eval and model behavior understanding teams that, we call it agent dev velocity.So your dev velocity building agents can be faster if we invest in that platform. And so we have a whole org dedicated to Asian, um, platform velocity so that you can build your own eval and then maintain it once you ship it. So if a new model release comes out and we, every[00:21:38] swyx: team maintains their own eval,[00:21:40] Sarah Sachs: we maintain the eval framework.Every team owns their own evals and a lot of them we've integrated to Optin, to ci, or we run them nightly and we have a team, uh, a custom agent that triggers to a team to look at the major failures. That's really critical because if we have like all these different surfaces now, a lot of it's on the same agent harness, so it's easier to maintain.It's just packaging of different agent harnesses, but new functionality of the agent. Let's say that like we wanna update like. Uh, you know, they deprecated, sonnet, um, four or whatever it is and we need to auto update. Are[00:22:11] swyx: they already? That's so, okay. Yeah. Actually wasn't that long ago.[00:22:14] Alsesio: Theywere[00:22:14] Alsesio: just 3.5.[00:22:15] Sarah Sachs: 3.537. Just got deprecated.[00:22:18] swyx: 3 7, 5 0.2 or, yeah. No,[00:22:20] Sarah Sachs: it's not. 5.2 is five point. Five point no. Yeah, five four is 40% more expensive than five two. So if they deprecated five two, you would hear they can, you would hear from me about that one. Um, but, uh, another conversation to have.[00:22:35] swyx: I have a cheeky evals question for you.Have you noticed any secret degradation from any of the major model providers?[00:22:40] Sarah Sachs: Secret degradation,[00:22:42] swyx: like. During the War Bay, when it's high traffic, it suddenly gets dumber.[00:22:47] Sarah Sachs: Yeah. I mean, not just between the, I mean, we definitely notice flakiness, we've definitely noticed, particularly for some providers, that things are slower during working hours and[00:22:57] swyx: there's a latency argument.Yes. Not a quality argument.[00:22:59] Sarah Sachs: No. I think the quality difference that's interesting is, um, even though companies that say they're selling the same, a, it's really into like quanti quantization, but like companies that say they're selling the same model through different vendors, whether it be through first party or Bedrock, Azure, et cetera.We do see different qualities sometimes, and that's not necessarily what's advertised.[00:23:21] swyx: Yeah. Kidney went to the point of like, if we, they shipped like this, like eval across all the providers and it was like very obvious we were secret equalizing and it was very,[00:23:28] Sarah Sachs: yeah. But[00:23:29] swyx: that's very embarrassing.[00:23:30] Sarah Sachs: You know, um, we hire Subprocess to figure that out for us.So we just wanna understand where it's regressing or where it's optimized. And sometimes we're okay with regressions that optimize latency if they're the appropriate regressions. Our job is to make sure we have the evals to understand the changes that are important to us. And even like when we're partnering with labs on pre-releasees of models, they'll send us multiple snapshots.And this is less about quantization, but more just regressions. Like they have shipped models that were not the snapshots that we wanted, and they have changed the snapshots that they shipped based on the feedback that we give. Because our feedback tends to be more enterprise work focused and not coding agent focused.And definitely those can be bummers, like, you know, uh, we know that this wasn't the version you wanted, but we'll help you make it work. I mean, we always make it work, but that definitely happens.[00:24:16] Alsesio: Yeah. Do you have, um, failing evals that you're just hoping, oh, that will have success eventually when a good model comes out?[00:24:23] Sarah Sachs: Uh, I mean, yeah. So I think. I mean, I could talk about this for 60 minutes, so I will limit myself. I think it's a real issue when people say evals and it's just like, that's quality, that's like unit, I mean, it's like saying testing. It's not just unit tests, right? So. We have the equivalent of unit test.Regression test. Those live in ci, those have to pass a certain percent, you know, within some stochastic error rate. Then we have, as you're building a product, evals of these aren't passing right now, and this is launch quality. So we have a report card and we need to, on these categories, you know, be it 80 or 90% of all of these user journeys to launch, and then what we have what we call frontier or headroom evals, where we actively wanna be at 30% pass rate.And that's actually been a effort that we took in partnership with philanthropic and OpenAI in the past maybe two or three months, because we actually hit a point where our evals were saturated and we weren't able to really give insightful feedback other than it wasn't worse. And not only is that not helpful for our partners, it's not helpful for us to understand where the stream is going.You know, going back to that analogy. And so we spent a lot of time thinking about. What notions last exam looks like, right? Mm-hmm. Not just humanities, last exam. Ooh, notions last exam. Mm-hmm. And, um, there's a lot of, you know, dreams about what that would look like. I know we've talked a lot about benchmarking, um, swix, but, uh, yeah.Notions last exam is a big thing inside the company and we have people, full-time staff to it exclusively. Mm. We have a data scientist, a model behavior engineer, and an full-time, um, evals engineer just dedicated to the evals that we pass 30% of the time.[00:25:56] swyx: What you're hiring for[00:25:57] Sarah Sachs: MBEs? I am hiring[00:25:58] swyx: What is an MBEA[00:25:59] Sarah Sachs: model?Behavior Engineer Model. Behavior engineers started with a title data specialist before I joined when they were working with Simon on like, uh, Google Sheets and like Simon just needed someone to look through Google Sheets and say, yes, no, this looks bad. This looks good. Right? And so we hired people with kind of diverse linguistics background.We had like a linguistics PhD dropout. Mm-hmm. And a Stanford ate new grad. And they're amazing. And they formed a new function basically. And over time we've built a whole team, um, with a manager who's now kind of reinventing what that role is with coding agents. So they used to be kind of manually inspecting code.Now they're primarily building agents that can write evals for themselves or LLM judges. There's a really funny day I can send you the picture where Simon, about a year and a half ago, was teaching them how to use GitHub. Um, and they're on the whiteboard and it was like, okay, I think it would be so much faster if our data specialists learned how to use GitHub and like learned how to commit these things in Dakota.And, and that was then and now I think, you know, coding has been a lot more accessible. Um, but moving forward it's this mix of like data scientist PM and prompt engineer because there's craft in understanding like even like what models can and can't do things. How do we define like that headroom? How do we define like what a good journey is?Um, is this model better or not? Why is this failing? There's some qualitative work, but then there's also like a lot of instinct and taste to it, and that's not necessarily software engineering. And so we have like very firm conviction and we have had for a number of years now that that is its own career path and we have always welcomed the misfits, so to speak.So we really firmly believe that you don't need an engineering background to be the best at this job. And that's what's quite unique about this particular role.[00:27:37] Simon Last: Yeah, this is something that I've been pretty excited about recently is we made an effort basically to treat the eval system as like an agent harness.So if you think about it, like, you know, you should be able to have an agent end-to-end, download a dataset, run an eval, iterate on a failure, debug, and, and then implement a fix. And ultimately you should be able to, you know, drive the full time process with a human sort of observing the, you know, the outer uh, system.So yeah, we went, went pretty hard on that. And that's, that's worked extremely well so far. It's like basically just to turn it into a coding agent, uh, uh, problem.[00:28:11] swyx: Your coding agent or just whatever[00:28:13] Simon Last: harness No coding agent. Yeah, code, cloud code. It should be totally general. Yeah. I think if it would be a mistake to like, like fix it on any, any particular coding agent.At the end of the day, it's just like CLI tools.[00:28:21] Sarah Sachs: It's like the same way that you would've a coding agent write the unit test. You should have a coding agent write the eval.[00:28:26] swyx: Yeah.[00:28:26] Sarah Sachs: But there's a lot of supervision in that still. We just don't believe that supervision has to come from software engineers because a lot of it is like, um, kind of you XREE and whatever, and these are the people that also triage failures and tell us where we should be investing next.[00:28:40] swyx: Yeah. I'm gonna go ahead and ask a spicy question. Is there a data, there are no software engineers at Notion.[00:28:46] Simon Last: Um,[00:28:46] Sarah Sachs: what does it mean to be a software engineer?[00:28:47] swyx: Exactly.[00:28:48] Simon Last: I mean, I think the way things are going is like we're on some continuum where. If, if you look back three years ago, humans were typing all the code and then we had auto complete, you're typing list of the code.Then we had sort of like filling agents, filling lines, and now we're getting into like agents doing longer range tasks where you can debug and implement a fix and then verify it works and you know, get your, get your PR even like, like Merion deployed. I think we're sort of just moving up the abstraction ladder and then the human role becomes more about observing and maintaining the outer system.There's a string of agents flowing through, like me prs what's going off the rails. Like what do I need to approve? Is there like a learning or memory mechanism that that works? So it's kind of a hard engineering problem. There's a, you know, there's, there's a lot to do there. I think we're just sort of moving up stack[00:29:34] Sarah Sachs: the same transition machine learning engineers have made, right?Like I haven't looked at a PR curve in a while.[00:29:39] swyx: Yeah. You used to do this stuff and now, um, auto research can do it,[00:29:42] Sarah Sachs: right? Like I think it depends on what you define as a software engineer.[00:29:46] swyx: Yes. It's, that's changing for sure.[00:29:49] Sarah Sachs: I think every software engineer in notion this summer went through like this, um, sheer, um, one of our engineering leads of the company called it, like every software engineer is going through the, the, uh, identity crisis that every manager goes through, where all of a sudden they realize their ability to write code is less important than their ability to delegate in context switch.And I think that is a transition out of being a software engineer. But[00:30:12] Simon Last: yeah. Yeah, there's a critical difference to being a manager, which is that like, it is actually very deeply technical. The problem, you know, humans are very like, like, like fuzzy and you can't like treat a team of humans like a, like a rigorous system where like, you know, prs like, like flow through and can be in like a block status and then what happens when they're blocked, right.With a set of agents, you actually can do that. And, and, and I think it's actually, there's a lot of interesting technical rigor that that goes into that it's like it's a technical design problem. Ultimately.[00:30:42] Alsesio: What is the design of the software factory that you're building?[00:30:46] Simon Last: Yeah, I mean, I think we're. Trying a lot of different things.I mean, ultimately you want to design a system that requires as little human intervention as possible, but like still maintaining the in variance that, that you care about. So yeah, we're exploring a lot different ideas there. I mean, I think I could talk about a few things I think are important there.Like, one thing I think is really important is, um, having some kind of like specification layer you can just commit marked on files. Mm-hmm. That works pretty well, but[00:31:15] swyx: it's nice to be notion man. I'm just saying like the spec, like Yeah. The natural home for specs is notion.[00:31:21] Simon Last: Yeah. Right. It can be a database of pages.Yeah. I mean, it needs to be something that is, you know, human readable and I viewable and I think that's pretty key. Another really key component is like the, the self verification loop. Yes. You need really, really good testing layers, basically. And that's a really deep, uh, uh, problem. But by getting that right, you know, and then, and then it's kinda like the workflow of like.What happens when there's a bug? How does it flow into the system? Like, is it like a subagent working on it? How does it make a PR and how does that get reviewed? And me, and then, you know, so there's like the, the flow or process.[00:31:56] swyx: Yeah. Cool. Uh, you know, one thing we did work out before you guys came in was this demo or this[00:32:01] Simon Last: agents[00:32:02] swyx: agent demo.Uh,[00:32:03] Simon Last: so every,[00:32:04] Alsesio: every time we do an episode, we try the product. Right. I don't think there's ever been an episode that I haven't tried. Yeah. Um,[00:32:11] swyx: and we, we try, try is a, a big word. Like since day one lane space has been on Notion, but this is the, this is the net new thing. Yes.[00:32:18] Alsesio: So this is for Nel Labs, which is the space we're in.So next week we're opening applications for tenants. So there's a web form, let me, we got this form done here. Uh, so, uh, before. Uh, the workflow would be I get an email, then I look at the person. It was like, should I spend time talking to this person? Then I respond, they respond back. So I build this. So the name it came up for on its own.Can you maybe h how do, how does it come up with its own name?[00:32:43] Simon Last: Yeah, that's a pretty app name. It's, it, it is just a random, it's a random, a name generator.[00:32:47] Alsesio: Oh, that's funny. It just came,[00:32:49] Simon Last: the fact that it picked that is, is kind of hilarious. I'm pretty sure it's just determined,[00:32:54] Sarah Sachs: resilient collector. I, I think I've never looked at the code for that.I've never second guessed it. I think it's kind of like a madlib situation.[00:33:00] Simon Last: Yeah, I think you're right. Yeah. It's, it's totally a, a deterministic. Oh, I thought it was great. Yes. Although, although when the, if you use the AI to set itself up, it can update its own name, so. Okay. Um,[00:33:11] Sarah Sachs: how did you create it? It, did you just do[00:33:12] Alsesio: classroom?I,[00:33:13] Sarah Sachs: okay.[00:33:13] Alsesio: I did, yeah. I'll say just check my inbox for applications for a coworking space. Keep a people, so it created the database for me. Which I have here. And I guess database is like an notion table because everything is notion. Um, and then whenever um, an email comes in, like here, it just creates a new role for the person.Mm-hmm. And then it uses web search to enrich the mm-hmm. The profile. So it kind of like searches the web and it's like, this is who this person is, this is when they say they wanna move in and kind of updates everything else. This is, I mean, it's not a GI, but to me, I don't wanna do this work. So it feels like, I mean, it took me maybe like 15 minutes to set up the whole thing.Um, and I really like that most of the information should live here. You know, it is not like some other tool asking me[00:34:01] Sarah Sachs: Yeah.[00:34:01] Alsesio: To like, bring my stuff there. It's like I would've probably already created an ocean thing.[00:34:06] Sarah Sachs: Mm-hmm.[00:34:06] Alsesio: So[00:34:07] Sarah Sachs: most of our biggest use cases and gains are from. That extra layer of human involvement in the process to make it so right.And so like one of our biggest use cases is bug triaging. So if someone posts something in Slack, can you just have a custom agent that lives there that has its own routing constitution of what team this belongs to, creates a task in your task database and then posts in that Slack channel, right? Like that's like one of the first things that we built internally, I think.And it's completely changed the way that notion functions as a company. Nothing falls through, well, most things don't fall through the crack. We don't know what we don't know. But it's not replacing people, it's replacing processes.[00:34:44] Alsesio: Yeah.[00:34:44] Sarah Sachs: Right.[00:34:45] Alsesio: And I'm curious how you think about composability of these things.So the other one I was working on is like a. These filler. So whenever somebody signs up as a tenant, kind of he'll sell the lease for them. There should probably some agent that is like office manager agent mm-hmm. That can handle the request, make the lease, and then, uh, give them a ADA access to the office and all of that.How do you think about that feature?[00:35:08] Simon Last: Yeah, so I mean, there's, there's two ways you can compose. One way is by using like the data primitives. So you can, you know, you, you could give, you have one agent, uh, be writing to the database and there's another agent that's walked in the database. So that's, that's one way that they, they can coordinate that's like a little bit more decoupled and mm-hmm.Works really well. Or you, you can couple them. So I, I think it's actually not released yet. Releasing it like next week is, uh, in the settings for an agent, you can give access to invoke any other agent.[00:35:34] swyx: Hmm.[00:35:34] Simon Last: So you can have them just. Just, uh, uh, talk directly. So[00:35:37] swyx: you, was there a limit on like, number of recursions or just,[00:35:40] Simon Last: um, probably,[00:35:42] swyx: you know what I mean?Like, you can just get an infinite loop that way there's[00:35:45] Simon Last: some kind of Yeah,[00:35:46] Sarah Sachs: I think it's, there is actually a number somewhere.[00:35:49] swyx: I believe I'm just, you know, like, you're, you're, someone's gonna screw up. You[00:35:51] Simon Last: should you try to see[00:35:53] swyx: Yeah. I mean, everything's gonna be paperclips.[00:35:55] Simon Last: Oh, yeah. Yeah. But, uh, but, but that's really useful.Yeah. So we, you know, like I just, I, I helped, uh, someone internally the other day, they had, they had built like over 30 custom agents for, uh, for our go to market team doing all kinds of different things. You know, for example, like researching, you know, like, like filling information about, about a customer or like, like triaging customer feedback or like, uh, something like that.Literally over 30 of them. And, and then he, and then he even made like a database of all the agents and then he is like, okay, and, and now I'm getting 70, over 70 notifications per day with just the agents are blocked on various things. Uh, and then I was like, oh, okay, cool. You know, the obvious thing to do there is to make a manager agent,[00:36:32] Sarah Sachs: right?[00:36:33] Simon Last: That's gonna sort of blocks be another abstraction layer in between your, your, uh, uh, 30 agents. Uh, so yeah, we, we send out with like a manager agent and then has access to invoke all the other agents and it's sort of like, like watching and observing them and then it sort of, it just creates a layer of abstraction.So instead of 70 notifications per day, it's like, like five. And then, and then the manager agent can help like, uh, debug and fix any problems with the,[00:36:54] swyx: does this is a concept of like an inbox or something like piece, you're basically saying that they can message each other?[00:37:00] Simon Last: Yeah.[00:37:01] Sarah Sachs: Well[00:37:01] swyx: they use the system of record, which, which is[00:37:02] Sarah Sachs: notion, so we[00:37:03] Simon Last: actually, yeah, we didn't make any special concepts at all.[00:37:06] swyx: They're interested to the motion notifications that I would've got,[00:37:09] Sarah Sachs: they can just like write a task to a database that the other agent's task to listening to, or they can actually call a web book to the agent, like they can just add the agent. Okay.[00:37:17] Simon Last: Yeah, I mean, this is something that, that we're still working on.I, I think we, you know, like, like generally, generally the way we do these things is, you know, you first make it possible, maybe like a sort of janky way. So I, I, I think the way I set ‘em up is like, you know, we created like a new database that was sort of like issues mm-hmm. That the custom agents were, were experiencing, and then gave them all access to file an issue and then the manager has access to, to read the issues.Um, and that works pretty well, essentially like, like give it its own like internal issue tracker just for the agents. And then, you know, if that becomes a, a concept that seems useful, generally maybe we will think of how to package it in. But I mean, generally we try to just keep it to composing the primitive if we can.You know, another example of this is we have no built-in memory concept. Memory is, is just pages and databases. And so if you wanna give a memory, just give it a page and give it. Edit access to that page and the[00:38:03] swyx: human can edit it. Agent can edit[00:38:04] Simon Last: it. Yeah. And so that works, that pattern works extremely well on it.And you know, depending this case, you can have it be just a page or it could be an entire database with, you know, or, you know, I can have sub pages is is pretty on what you can do with that.[00:38:15] Alsesio: So when I was setting this up, uh, I connected my inbox and it was like, do you wanna use Gmail or Notion Mail? And I'm like, I don't wanna use Eater, I just want you to do it.I'm curious how you think about, you know, notion, mail, notion, calendar, all of these kind of ui ux interfaces, full stack[00:38:29] Simon Last: notion.[00:38:30] Alsesio: Yeah. When like at the same time you have the agents abstracting them away from you in a way, you know, how do you spend like the product calories so to speak?[00:38:37] Simon Last: Yeah, I mean, I think it's pretty important that you don't have to use, not your mail to connect to the mail capability.So we can just connect to Gmail or, or whatever you want, uh, to use. And we're thinking of the mail service as being really great to the extent that it's really agent built, right? So maybe the mail app is just sort of a prepackaged agent that helps you automate your, your inbox.[00:39:00] Alsesio: Yeah, the auto labeling is great.Think[00:39:03] Sarah Sachs: the, when we, um, integrate with Gmail for instance, we have a series of tools available that are available via MCP or API to Gmail. When we integrate with Notion Mail, we have the Notion Mail engineering team to build us the, um, exact right tools that optimize latency, optimize performance and quality.They own that quality. Um, there's product leads there. They're directly thinking about the user problems that happen in mail. So it tends to be when we build integrations and connections, we build natively first. Um, and then think about, um, extending them generally just because it's also easier. Mm-hmm. Um, um, to build natively first.Um, so that tends to be how we phase things out.[00:39:43] swyx: Talking about integrations, you prompted me, so I gotta ask. M-C-P-C-L-I. What's going on? What's the[00:39:48] Simon Last: Yeah. Opinion. I think, I mean, I'm, I'm definitely bullish and excited about cli. I think there's a few really cool things about cli. So one really cool thing is like, um, is that it's in the terminal environment, so it gets a bunch of extra power.So it, you know, for example, it can like, like paginating and cursor through like long outputs. Um, and it has a progressive disclosure inherently. Uh, so, you know, you don't see all the tools at once. It's just, you see the CLI wrapper and you can like use the, the help commands and, and, and read files. And then I think the most important thing that's, that's super cool is that there, it's also inherently a, a bootstrapped.So if there's an issue, uh, the agent can debug and fix itself within the same environment that it uses the tool.[00:40:30] swyx: Mm.[00:40:30] Simon Last: Right. Like, you know, I think I saw a tweet this morning. Someone said, you know, my agent didn't have a browser, so I asked it to make all a browser tool and within a hundred lines of code, it gave itself a little browser, like, like wrapping the, the, the chromium API, um.That's pretty incredible. And then if there was a bug, it would just immediately try to fix it. Mm-hmm. Right. On the other hand, if you use an, you know, if you use like of, of the Chrome dev tools, MCP, I've had this issue where like, like sometimes the transport gets like messed up. If it gets messed up, the agent has no way to fix itself.It, it no longer has a browser, it's, it's not broken. Right. I think that's, that's pretty fundamental, but I would say like a lot of the, the bad things about it can be fixed. Uh, so I think like, as a progressive disclosure, that can be fixed with, with right harness. Like, it, it obviously doesn't make sense to show it all the tools all the time.That's not really inherent to the MCP protocol. It's just like how you wrap it and use it.[00:41:16] swyx: There's many poorly built MCPs because we didn't know.[00:41:19] Simon Last: Yeah, yeah. I mean it was just early, like, like the obvious thing is, uh, you know, to start with is, is to just show it all the tools and it's like, okay, now we have a hundred tools.Yeah. And like the tool calling actually works. So let's of[00:41:28] swyx: your success[00:41:29] Simon Last: give it a way to like, like filter to source the tools. So yeah, I would say like broadly speaking, I'm really bullish on cli. I'm still bullish on CPS and in a certain environment. I think in, in particular, CP is really great for when you want sort of like a narrow, lightweight agent.I think there's, there's definitely a lot of use cases where, where you don't want like a full coding agent with a compute run time. And also you want it to be like more tightly permissioned. MCP inherently has a really strong permission model, like all you can do is call the tools. A CLI is a little bit murkier.It's like, can I access the, if PI token are you, like, properly sort of like re-encrypt the token so it can't like exfiltrate it, it introduce a lot of like, like new issues, which are. Real and hard to solve. And MCP is just like the dumb simple thing that works and it that it's pretty good.[00:42:12] Sarah Sachs: I'll add two more perspectives, not from it working well for Notion, but how notion like commits to both platforms.Notion is dedicated to being the best system of record for where people do their enterprise work. So we will always support our MCP and so far as other people are using cps, right? So regardless of our perspective, we've put a lot of effort into our MCP and we have a fantastic team that we're building, um, to do more there.And the second thing I'll say, I think, um, we all think a lot, but lately I've been thinking a lot about making sure there's a value alignment and pricing, um, with capability.[00:42:43] swyx: Literally our next question[00:42:44] Sarah Sachs: and. Needing language to execute deterministic tasks feels wasteful and requiring on a language model to interface with third party providers seems wasteful for tasks that don't require it.And particularly because our custom agents are using usage-based pricing. We think of pricing as like the barrier of entry for use of our product, and we're quite committed to making sure that it's not wasteful. Um, not just because it's a bad deal for our customers, but it's also bad business. We wanna have as many buyers, like there's a, there's an elasticity of demand and so if we can have our agents properly execute code that calls on CLI deterministically, it's a one-time cost, right?Versus constantly having a language model integrate with an MCP over and over and over and paying those like repeated token fees and it's happening outside the cash window, then you're paying for it over and over and over and it's just kind of unnecessary and less deterministic when it doesn't have to be.[00:43:36] Alessio: Yeah, the open-endedness I think is like, the main thing is like, well, if I go write code to just call an API, I would never use an MCP. But then you need an NCP sometimes when you know what to call, but you don't want it to restart versus like, I think the it built a browser from scratch is like, it's great when you're doing it on your own, but like if your customers were having your AI write a browser from scratch every time and you had to pay the token cost of that, yeah.You'd be like, no, no. The Chrome dev tools CP is actually pretty great. Just use that. I'm curious, how do you make that decision? Like should it be. Just straight API call very narrow. Should it be an MCP? Should it be super open-ended?[00:44:10] Sarah Sachs: Do you mean for when we ship notion capabilities or when we add capabilities to[00:44:13] Alessio: notion[00:44:14] Sarah Sachs: AI or,[00:44:14] Alessio: I mean, you might have a capability that the only way to do is an open-ended agent, like an agent with a coding sandbox.[00:44:21] Sarah Sachs: Yeah. In Notion ai they're not explicit, not We also ship an MCP.[00:44:24] Alsesio: Yeah. Yeah. In B,[00:44:25] Sarah Sachs: yeah.[00:44:26] Alsesio: Internally. Okay. Like is there ever a discussion of like, we're not gonna ship it because we're not able to tie it down? Or are you happy to just like,[00:44:33] Sarah Sachs: um, no. I mean, there are a lot of things where we choose not to use MCP because we wanna add more high touch to quality.I think search an agent to find is like the largest instance of that, where we have. Um, slack and linear and Jira search and notion that is not using necessarily the search MCP functionality that is provided by those companies. And that's because it's quite critical we think, to how our agent trajectories work is for us to have a little bit more control on the functionality of the search journey.And so it usually comes from quality and there's a long tail of things and that's why we built an MCP client or an MCP server, excuse me, so that people can connect whatever they want. There's that long tail, right. But we, for search particularly, I would say that's like the primary entry point, but there are other connections as well that it's a little bit of secret sauce a

Bienvenue dans le trois-cent-et-unième épisode de CacaoCast! Dans cet épisode, Philippe Casgrain et Philippe Guitard discutent des sujets suivants: Apple - toutes sortes d'annonces Skip - Maintenant gratuit et en code-source libre SiriMote - Contrôlez votre mac avec votre télécommande d'AppleTV Xylem - Pour votre XML en Swift pur MHGP - Avez-vous l'impression que Github n'est plus très stable? Mockdown - Faites vos dessins en ASCII sur le web Ecoutez cet épisode

In an April 2nd community call hosted by Chris Hoyt of CareerXroads, Indeed detailed significant policy changes aimed at transitioning the platform toward a more controlled "pay-to-play" marketplace. The key shift involves the sunsetting of traditional XML feed support, requiring employers to integrate their Applicant Tracking Systems (ATS) directly or post manually, which effectively ends the "single source" free visibility many companies relied on. https://www.linkedin.com/pulse/what-indeed-told-us-summary-april-2nd-community-call-chris-hoyt-r37dc/ Oracle today announced Fusion Agentic Applications for HR. The new agentic applications are powered by coordinated teams of specialized AI agents that are outcome-driven, proactive, reasoning-based, and engineered for enterprise execution. Built into Oracle Fusion Cloud Applications, Fusion Agentic Applications for HR can make and execute decisions within business processes by securely accessing unified enterprise data, workflows, policies, approval hierarchies, permissions, and transactional context. https://hrtechfeed.com/oracle-introduces-fusion-agentic-applications-for-hr/ https://hrtechfeed.com/ai-agents-now-have-their-own-job-board/ Paylocity (NASDAQ: PCTY), a leading provider of HCM, Finance, and IT solutions, today announced the acquisition of Grayscale Labs, Inc. (“Grayscale”), an AI-powered recruiting automation company that helps businesses hiring at scale move faster without compromising quality. Grayscale expands Paylocity's recruiting capabilities with AI-powered recruiting automation that helps employers engage candidates earlier and move faster through time-sensitive hiring workflows—while keeping hiring decisions firmly in the hands of recruiters and hiring managers. The platform helps organizations keep pace with the ongoing hiring demands of high‑volume, high‑turnover workforces without sacrificing quality or control. https://hrtechfeed.com/paylocity-acquires-grayscale-to-expand-ai-powered-recruiting-capabilities/ Wizehire, the leading hiring platform for small and growing businesses, announced the launch of Jobs by Wizehire, a new app available in ChatGPT to help job seekers easily find and apply to local jobs through conversations. https://hrtechfeed.com/wizehire-launches-jobs-app-in-chatgpt/ In a move that signals a fundamental shift in how corporations view their workforce, monday.com (NASDAQ: MNDY) has officially launched Agentalent.ai, a first-of-its-kind managed marketplace designed specifically for “hiring” enterprise AI agents. Learn more about your ad choices. Visit megaphone.fm/adchoices

Are duplicate URLs quietly destroying your website's search rankings and AI visibility? Favour Obasi-ike, MBA, MS breaks down the technical SEO power of canonical tags, revealing how proper URL structuring prevents duplicate content, boosts visibility on AI platforms, and drives sustainable online revenue.

XML Sitemaps & Robots.txt Technical Optimization: Actionable AI SEO Steps Demystified (The Brain of Your Website) with Favour Obasi-ike, MBA, MSWho is this for?This technical deep dive episode with Celese Williams is essential listening for business owners, content creators, and marketers who want to stop losing organic traffic and start building a sustainable foundation for search engine visibility. Whether you manage a complex e-commerce site, a localized service business, or a growing blog, understanding how to communicate effectively with search engines and AI crawlers is critical.If you've ever wondered why your latest content isn't ranking or why your traffic is dipping despite consistent publishing, this deep dive into XML sitemaps and technical SEO is for you.Book Web Dev SEO Services?

This is a recap of the top 10 posts on Hacker News on March 14, 2026. This podcast was generated by wondercraft.ai (00:30): Ageless Linux – Software for humans of indeterminate ageOriginal post: https://news.ycombinator.com/item?id=47381791&utm_source=wondercraft_ai(01:57): What happens when US economic data becomes unreliableOriginal post: https://news.ycombinator.com/item?id=47378638&utm_source=wondercraft_ai(03:25): Games with loot boxes to get minimum 16 age rating across EuropeOriginal post: https://news.ycombinator.com/item?id=47371692&utm_source=wondercraft_ai(04:52): RAM kits are now sold with one fake RAM stick alongside a real oneOriginal post: https://news.ycombinator.com/item?id=47375085&utm_source=wondercraft_ai(06:20): Montana passes Right to Compute act (2025)Original post: https://news.ycombinator.com/item?id=47376767&utm_source=wondercraft_ai(07:48): XML is a cheap DSLOriginal post: https://news.ycombinator.com/item?id=47375764&utm_source=wondercraft_ai(09:15): Claude March 2026 usage promotionOriginal post: https://news.ycombinator.com/item?id=47380647&utm_source=wondercraft_ai(10:43): GIMP 3.2 releasedOriginal post: https://news.ycombinator.com/item?id=47380465&utm_source=wondercraft_ai(12:11): Head of FCC threatens broadcaster licenses over critical coverage of Iran warOriginal post: https://news.ycombinator.com/item?id=47380294&utm_source=wondercraft_ai(13:38): Please do not A/B test my workflowOriginal post: https://news.ycombinator.com/item?id=47375682&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

AI is reshaping both sides of the cybersecurity battlefield — and fast. In this episode, we break down five stories that prove it: the first Chrome zero-day of 2026 (CVE-2026-2441), a near-perfect CVSS 9.9 in Microsoft's Semantic Kernel SDK (CVE-2026-26030), a supply chain attack on AI coding assistant Cline that silently installed autonomous agents on thousands of developer machines, the first-ever Android malware using Google's Gemini AI at runtime (PromptSpy), and a Russian-speaking threat actor who used commercial AI tools to breach over 600 FortiGate firewalls across 55 countries in just five weeks. Whether you're a developer, security professional, or just someone who uses a browser — this one's worth your time.

Zakaj borza vlagatelje hitro nauči ponižnosti? Matej Rigelnik, direktor nepremičninske družbe Equinox, o investiranju na slovenski borzi, nepremičninah, aktivističnem delničarstvu, nizkem prometu z delnico Equinox in inflaciji, ki jo najbolje ponazori kar cena bureka. Pred mikrofonom: Matej Rigelnik, direktor nepremičninske družbe Equinox ______________________ Ups, zamudil sem oddajo davčne napovedi. Ni panike. TAXISTENT, davčni asistent, pomaga tudi pri samoprijavi :) Uvažate lahko poročila IBKR; Trade Republic, Revolut, eToro in Trading 212. Z nekaj kliki ustvarite XML za uvoz v eDavek. Če zamudite, lahko v Taxistentu pripravite tudi dokument za Samoprijavo. Več na https://money-how.si/taxistent/ ______________________ Bootcamp za mlade Vse, kar mora vaš otrok vedeti o upravljanju denarja Termini: Ljubljana - 27. april 2026 med 10.00 Info: https://money-how.si/dogodki/ ____________________________ PONATIS KNJIGE: Mami, oči, ali smo mi bogati? Od žepnine do investiranja. Vodnik za starše, ki želijo razumeti upravljanje denarja in to znanje samozavestno prenesti na otroke. Tiskana knjiga https://money-how.si/knjiga/mami-oci-ali-smo-mi-bogati/ E-knjiga + bootcamp https://money-how.si/knjiga/mami-oci-ali-smo-mi-bogati-2/ ____________________________ Money-How Premium: https://money-how.si/narocnine/ vključuje: - Modri AI - Finančni asistent, ki pomaga pri raznih finančnih dilemah https://money-how.si/modri-ai/ - Taxistent - Davčni asistent, ki pomaga pri oddaji davčne napovedi https://money-how.si/taxistent/ (deluje za IBKR; Revolut, Trade Republic... in kombinacijo vseh) - poglobljene članke ____________________________ Bootcamp v živo: Investiranje – kako sploh začeti Že dolgo razmišljaš o vlaganju in ne veš, kje in kako začeti? Nimaš energije, da bi raziskoval vse podrobnosti. Skrbijo te davki? Presekaj in se nam pridruži v živo, kjer bomo skupaj naredili prvi korak v svet investiranja! Termini: Ljubljana - 22. april 2026 med 17.00 in 20.30 Info: www.money-how.si/dogodki/ __________________ Finančna delavnica je lahko čudovito darilo. Več preveri https://money-how.si/izobrazevanja ______________________ (delavnica) Investiranje v delnice: Kaj moram vedeti, ko se odločam za investiranje v delnice Prijava: https://money-how.si/izobrazevanja _____________________ (delavnica) Investiranje za začetnike. Praktično o osnovah investiranja. Prijava: https://money-how.si/izobrazevanja _________________________________ DISCORD skupnost: V finančnih zagatah nismo sami, pridružite se nam na Discord Money-How / discord _____________________________ Več o Money-How na https://money-how.si/

An airhacks.fm conversation with Thorsten Hoeger (@hoegertn) about: first computer experience with an IBM 8086 and learning programming by modifying the QBasic Gorilla game, early programming journey from QBasic to Visual Basic and the discovery of event-driven programming, building a password security script for autoexec.bat as a childhood project, transition from Visual Basic to Java around 2005 starting with Java 1.4.2, working at a small bank in Stuttgart building a core banking system, experience with Eclipse RCP rich client platform and the overhead of plugin architecture in business software, migration from Swing to Eclipse RCP frontend with JBoss application server backend, building a custom Spring-based microservice framework called Dwallin (Icelandic for dwarf) before Spring Boot existed, using Apache CXF for REST and RPC over messaging with ActiveMQ, comparison of Java development trajectories between annotation-based and XML-heavy approaches, discussion of the infamous Java and XML O'Reilly book that popularized XML configuration, xdoclet as a precursor to Java annotations, contrasting approaches of JBoss-based thin WAR deployments versus Spring-based embedded server microservices, university experience learning Ada programming language and its strict compiler as excellent for learning programming, PL/SQL's Ada-based origins, brief experience with OSGi and strong criticism of its complexity and poor developer experience, comparison of OSGi with Java Platform Module System (JPMS), founding Taimos consulting company 10 years ago originally building BlackBerry enterprise software, pivoting to AWS migration consulting for regulated industries including banks and insurance companies, strong preference for serverless architecture with lambda Step Functions API Gateway and DynamoDB, criticism of running kubernetes on AWS versus using native services like ECS Fargate, the distinction between running "in the cloud" versus "on the cloud", detailed discussion of why GraalVM native images are unnecessary on AWS Lambda due to compliance overhead and memory allocation model, quarkus and SnapStart as solutions for Lambda cold start problems, Java's cost efficiency on Lambda due to fast execution times, involvement with AWS CDK since 2018-2019 including building L2 constructs for EC2 and AppSync, shift from code contributions to community organizing and prioritization work with the CDK team, launching CDK Terrain as successor to CDK for Terraform, nuanced discussion of open source economics when the project primarily benefits a paid cloud provider, using GitHub as a personal index and dashboard for reusable project templates, consulting perspective on contributing to open source for code reuse across multiple clients, teaser for a future deep-dive episode on CDK internals and promoting Java usage with CDK Thorsten Hoeger on twitter: @hoegertn

O burnem začetku trgovanja delnice Vzajemna, pričakovani točki preloma in prvi dividendi. Govorimo o 5-odstotni omejitvi prenosa delnic, koncentraciji lastništva, vlogi države ter vplivu geopolitike in politike na poslovanje. Kakšna je strategija do 2027 in kaj to pomeni za male vlagatelje? Delnica Vzajemne bo 4. marca uvrščena na Ljubljansko borzo. Bo začetek trgovanja res buren? Bo pritisk prodajalcev prevladal nad kupci? Pred mikrofonom: predsednik uprave Matija Šenk ______________________ Ups, zamudil sem oddajo davčne napovedi. Ni panike. TAXISTENT, davčni asistent, pomaga tudi pri samoprijavi :) Uvažate lahko poročila IBKR; Trade Republic, Revolut, eToro in Trading 212. Z nekaj kliki ustvarite XML za uvoz v eDavek. Več na https://money-how.si/taxistent/ ______________________ Bootcamp za mlade Vse, kar mora vaš otrok vedeti o upravljanju denarja Termini: Ljubljana - 27. april 2026 med 10.00 Info: https://money-how.si/dogodki/ ____________________________ PONATIS KNJIGE: Mami, oči, ali smo mi bogati? Od žepnine do investiranja. Vodnik za starše, ki želijo razumeti upravljanje denarja in to znanje samozavestno prenesti na otroke. Tiskana knjiga https://money-how.si/knjiga/mami-oci-ali-smo-mi-bogati/ E-knjiga + bootcamp https://money-how.si/knjiga/mami-oci-ali-smo-mi-bogati-2/ ____________________________ Money-How Premium: https://money-how.si/narocnine/ vključuje: - Modri AI - Finančni asistent, ki pomaga pri raznih finančnih dilemah https://money-how.si/modri-ai/ - Taxistent - Davčni asistent, ki pomaga pri oddaji davčne napovedi https://money-how.si/taxistent/ (deluje za IBKR; Revolut, Trade Republic... in kombinacijo vseh) - poglobljene članke ____________________________ Bootcamp v živo: Investiranje – kako sploh začeti Že dolgo razmišljaš o vlaganju in ne veš, kje in kako začeti? Nimaš energije, da bi raziskoval vse podrobnosti. Skrbijo te davki? Presekaj in se nam pridruži v živo, kjer bomo skupaj naredili prvi korak v svet investiranja! Termini: Ljubljana - 22. april 2026 med 17.00 in 20.30 Info: www.money-how.si/dogodki/ __________________ Finančna delavnica je lahko čudovito darilo. Več preveri https://money-how.si/izobrazevanja ______________________ (delavnica) Investiranje v delnice: Kaj moram vedeti, ko se odločam za investiranje v delnice Prijava: https://money-how.si/izobrazevanja _____________________ (delavnica) Investiranje za začetnike. Praktično o osnovah investiranja. Prijava: https://money-how.si/izobrazevanja _________________________________ DISCORD skupnost: V finančnih zagatah nismo sami, pridružite se nam na Discord Money-How / discord ______________________________ Več o Money-How na https://money-how.si/

Host: Annik Sobing Guest: Kenneth G. Peters Published: February 2026 Length: ~20 minutes Presented by: Global Training Center GTM Software Prep: Don't Install Until You've Done These 3 Things First In this Simply Trade Roundup, Annik talks with Kenneth G. Peters, President at MIC US and Director of Commercial Operations in North America, about Global Trade Management (GTM) software—specifically, what trade teams must do before implementation to avoid creating “digital chaos.” Ken shares real talk from his ATCC presentation on data cleanup, process mapping, and testing, plus why “cleaning your data like you're hosting the in-laws” is now his signature advice. Shoutout to Alison for the killer slides.​ What You'll Learn in This Episode Ken's new grandpa status (the little guy is 7 months old—congrats!) and why it's the “next step in life” that keeps him energized for trade tech.​ The #1 mistake companies make with GTM software Data cleanup first: Don't dump junk into GTM. Scrub inactive vendors, obsolete parts, invalid HS codes (like 111111 or all zeros). Clean it like you're hosting the in-laws—no mess allowed. Why: GTM amplifies what you give it. Bad data in = faster mistakes out.​ Avoid the “Big Bang” implementation trap Don't try to do everything at once (denied party screening + classification + FTA rules + solicitation). Start small: Classification (builds the foundation—parts, HS codes, values). Denied party screening (uses your vendor/part data). FTA analysis (relies on classification/HS from step 1). Why: Master data dependencies mean you build once and reuse everywhere.​ Processes over pixels GTM won't fix broken workflows. Map your processes before going live. If your current setup is emailing Excel files between systems, you're not automating—you're digitizing chaos. True automation: ERP ↔ GTM via SFTP, APIs, XML—no human hands on keyboards. Reduces errors, speeds everything up.​ Who owns what after go‑live MIC US (GTM provider): Manages the software backend—reg updates, HS databases, platform maintenance. Your team: Owns the process (classification, entry creation, decision‑making). Someone still reviews outputs for accuracy. No “managed services” from MIC—GTM is a tool, not a full‑service outsource.​ Testing: where most implementations fail Allocate real time and resources to testing—don't rush it. Test end‑to‑end: data flow, workflows, edge cases. Why: Skipped or rushed testing = live problems that cost more to fix later.​ “If your systems are emailing Excel files to each other, you're not automating” Ken's golden rule: Hands‑off data flow (ERP → GTM) eliminates errors. Excel handoffs = manual errors waiting to happen.​ Key Takeaways Clean data first: Active parts, valid HS, no ghosts—GTM makes good data shine and bad data explode.​ Start small, build smart: Classification → screening → FTA, not “big bang everything.”​ Fix processes before pixels: GTM won't save broken workflows; it speeds them up.​ Testing = non‑negotiable: Rushed testing = expensive live fixes.​ GTM is a force multiplier—if your foundation is solid.​ Credits Host: Annik Sobing Guest: Kenneth G. Peters, President, MIC US Producer: Annik Sobing  Listen & Subscribe Simply Trade main page: https://simplytrade.podbean.com​ Apple Podcasts: https://podcasts.apple.com/us/podcast/simply-trade/id1640329690​ Spotify: https://open.spotify.com/show/09m199JO6fuNumbcrHTkGq​ Amazon Music: https://music.amazon.com/podcasts/8de7d7fa-38e0-41b2-bad3-b8a3c5dc4cda/simply-trade​ Connect with Simply Trade Podcast page: https://www.globaltrainingcenter.com/simply-trade-podcast​ LinkedIn: https://www.linkedin.com/showcase/simply-trade-podcast​ YouTube: https://www.youtube.com/@SimplyTradePod​ Join the Trade Geeks Community Trade Geeks (by Global Training Center): https://globaltrainingcenter.com/trade-geeks/  

Po nedavnih ameriško-izraelskih udarih na Iran in iranskih povračilnih potezah ostaja ena najpomembnejših neznank svetovnih finančnih trgov cena nafte. Hormuška ožina, skozi katero poteka skoraj 20 odstotkov svetovne nafte, je šibka točka globalne dobavne verige. Vsaka motnja tam lahko potisne cene goriva in energentov bistveno višje. Zaradi tega se lahko poviša inflacija, kar zmanjšuje manevrski prostor centralnim bankam za zniževanje obrestnih mer. Posledično lahko pride do upočasnitve globalna rast. Kaj to pomeni za naše portfelje? Pred mikrofonom: Andraž Grahek, nekdanji upravljavec premoženja, soustanovitelj Tivoli Ventures in Capital Genetics (snemali smo v živo) ______________________ TAXISTENT - davčni asistent, ki pomaga oddati davčno napoved Uvažate lahko poročila IBKR; Trade Republic, Revolut, eToro in Trading 212. Z nekaj kliki ustvarite XML za uvoz v eDavke. Če zamudite, lahko v Taxistentu pripravite tudi dokument za Samoprijavo. Več na https://money-how.si/taxistent/ ______________________ Bootcamp za mlade Vse, kar mora vaš otrok vedeti o upravljanju denarja Termini: Ljubljana - 27. april 2026 med 10.00 Info: https://money-how.si/dogodki/ ____________________________ KNJIGA: Mami, oči, ali smo mi bogati? Od žepnine do investiranja. Vodnik za starše, ki želijo razumeti upravljanje denarja in to znanje samozavestno prenesti na otroke. Tiskana knjiga https://money-how.si/knjiga/mami-oci-ali-smo-mi-bogati/ E-knjiga + bootcamp https://money-how.si/knjiga/mami-oci-ali-smo-mi-bogati-2/ ____________________________ Money-How Premium: https://money-how.si/narocnine/ vključuje: - Modri AI - Finančni asistent, ki pomaga pri raznih finančnih dilemah https://money-how.si/modri-ai/ - Taxistent - Davčni asistent, ki pomaga pri oddaji davčne napovedi https://money-how.si/taxistent/ (deluje za IBKR; Revolut, Trade Republic... in kombinacijo vseh) - poglobljene članke ___________________________ Bootcamp v živo: Investiranje – kako sploh začeti Že dolgo razmišljaš o vlaganju in ne veš, kje in kako začeti? Nimaš energije, da bi raziskoval vse podrobnosti. Skrbijo te davki? Presekaj in se nam pridruži v živo, kjer bomo skupaj naredili prvi korak v svet investiranja! Termini: Ljubljana - 19. marec ali 22. april 2026 med 17.00 in 20.30 Info: www.money-how.si/dogodki/ __________________ Finančna delavnica je lahko čudovito darilo. Več preveri https://money-how.si/izobrazevanja ______________________ (delavnica) Investiranje v delnice: Kaj moram vedeti, ko se odločam za investiranje v delnice Prijava: https://money-how.si/izobrazevanja _____________________ (delavnica) Investiranje za začetnike. Praktično o osnovah investiranja. Prijava: https://money-how.si/izobrazevanja _________________________________ DISCORD skupnost: V finančnih zagatah nismo sami, pridružite se nam na Discord Money-How / discord ______________________________ Več o Money-How na https://money-how.si/

In This Episode: The Internet Archive saves an old car. AI Bird IDs. Claude code. Ringing Lost Dogs. This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media. (You’ll find longer Bios on the Hosts page.) Top Stories 0:00 LN: Internet Archive to the rescue My wife is visiting my sister-in-law, and the parking brake in her 2000 Honda CRV (originally my mother’s car) froze up. The pull-lever i the center wouldn't budge. I got messaged for help. I searched for “2000 honda crv maintenance manual”. The second entry is The Internet Archive's scan of the ~1400 page manual. https://archive.org/details/HondaCRV19972000  I was able to send her images from the manual about how to access and lubricate the pull lever. This isn't the first time IA has popped up randomly to help. It's an amazing resource. 5:45 LN: What bird is  that? Another story of things coming together. My wife takes a photo with her phone (Pixel 4a) of a hawk sitting on a fence in our neighborhood. https://flic.kr/p/2rVhrLG  The photo is auto-uploaded to her Google Photos account. I grab a copy and crop it. Original is 4032×3024, so there are lots of opportunities. Not bad. https://flic.kr/p/2rVjh8d  7:00 I fire up Topaz Gigapixel AI, and, with a little adjustment of settings, upscale the image 4x. I then crop it further to focus more closely on the bird. Also not bad, though there are some tell-tale signs that this was AI upscaled. https://flic.kr/p/2rVisjk  9:15 My wife asks me what kind of hawk that might be. No clue. So I decided to try … ChatGPT. I upload the upscaled image, and ask simply, “What kind of bird is this?” Likely ID: Red-tailed Hawk (juvenile) Based on the bulky buteo shape, overall brown upperparts, the pale “checkerboard” pattern on the wings, and the strongly banded tail (common in young birds before they develop the classic red tail), this looks most consistent with a juvenile Red-tailed Hawk. We do indeed have red-tailed hawks around here. It’s interesting that it ID'd a juvenile. 15:00 Identify birds. https://merlin.allaboutbirds.org/  18:00 LN: Claude Code Installed on my PC because it promised to be able to work on local data 20:00 Non-trivial install (at least for Windows – WSL, and then you're running in an Ubuntu bash shell). 21:10 Scenario 1: My Obsidian vault – all plain text (.md) files. I can now ask questions and run analyses across the entire collection of notes. 24:00 Scenario 2a: My personal blog. Pointed it at leo.notenboom.org – did OK, but incomplete. 25:00 Scenario 2b: exported by personal blog content from WordPress as an XML file. Dense, lots of cruft. Gave that to Claude and got a very complete, detailed analysis / summary of what I've been doing there since 2004. 27:00 Scenario 3: downloaded the contents of 23 years of Ask Leo! Articles. https://askleo.com/ask-leo-analysis-via-claude-code/  38:00 GR: Ring Doorbell Superbowl Ad ? Pretty sure I was “ringing this bell” many years ago right here LN: We Rate Dogs take on it: https://www.tiktok.com/@weratedogs/video/7605333665031245069 Ain’t it Cool GR: Dungeon Crawler Carl LN: Archive.org BSP: Blatant Self-Promotion LN: Managing Windows File Explorer's Navigation Pane – https://askleo.com/188995 GR: How To Keep Using Pages, Numbers and Keynote If You Don’t Want Apple Creator Studio Transcript teh_260 Video https://youtu.be/Q7JXOLNvLi4

An airhacks.fm conversation with Christofer Dutz (christofer-dutz) about: first computer was a Commodore C64 from Hannover Messe, early programming in Basic, playing Wizards of War game on cassette tape, growing up in Melbourne Australia until age ten, visiting Ayers Rock and seeing prehistoric armored fish in puddles, learning C and C++ at Volkshochschule around 1992, memory management challenges with DOS gaming like X-Wing vs TIE Fighter and Wing Commander, starting Java at Technical University of Darmstadt in 1998 with version 1.0.7, appreciating Java's simplicity compared to C++ and no system crashes from memory errors, early involvement with Apache Cocoon for XML and XSL transformations, contributing to eXist-db XML database as committer number two, working with XML XSL and XSLT for data transformation, frustrations with YAML compared to XML, transition from Cocoon to Adobe Flex after Cocoon switched to Spring and Maven, becoming co-maintainer of Flex Mojos Maven plugins, Adobe donating Flex to Apache Software Foundation, attending ApacheCon in Sinsheim and connecting with Apache committers, committer and PMC member of 12 active Apache projects, firefighting role fixing Maven builds for stuck projects, retiring Apache Cocoon project, strong focus on industrial IoT projects, Apache IoTDB as best time series database, Apache StreamPipes for cloud IoT orchestration, Apache Camel and Apache NiFi involvement, founding Apache PLC4X in 2017 at codecentric, Apache PLC4X as JDBC-like interface for industrial equipment communication, spending 80-90 hours per week on PLC4X for nine years, challenges with industrial automation industry not understanding open source, anecdote about steel melting plant operator expecting free enterprise support, Germany being a difficult market for industrial automation consulting, founding ToddySoft company end of last year, building installable products and plugins for industrial solutions, ethical approach to open source by only selling products from projects he contributes to, real-time definitions varying from tens of milliseconds in cloud to nanoseconds in industrial systems, ToddySoft named after PLC4X mascot Toddy the palm civet (toddy cat), plans for future episode discussing IoTDB StreamPipes PLC4X and NiFi use cases Christofer Dutz on LinkedIn: christofer-dutz

This episode unpacks how Eventbrite marketing and SEO can be used to grow a business and sell tickets through organic search. Favour Obasi-ike emphasizes that placing targeted keywords at the beginning of event titles is crucial for creating effective URL (uniform resource locators) slugs that rank well on search engines. To build trust and boost visibility, event organizers should also embed YouTube videos and utilize back-linking strategies within event descriptions. Real-world case studies discussed illustrate that scheduling events at least one month in advance allows search algorithms sufficient time to index the content and reach potential attendees. Even after an event concludes, Favour notes that active links continue to drive traffic, serving as a long-term asset for brand awareness. Ultimately, the source advocates for a data-driven approach that combines strategic messaging with technical SEO to ensure sustainable audience growth.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 OnlineEpisode Timestamps[00:00:00] Introduction: Why Eventbrite is a Hidden SEO GoldmineThe episode begins by positioning Eventbrite as a critical platform for business marketing, lead generation, and product promotion, beyond mere event discovery. The emphasis is on creating every listing with the "searcher's benefit" in mind, focusing on how the event serves the needs of a potential attendee actively searching for a solution. This strategic mindset is the key to unlocking the platform's potential and leads directly into the most critical setup step for organic success.[00:05:30] The Single Most Important SEO Factor: Your Event TitleThe event title is presented as the most crucial element for SEO success because it directly generates the event's URL slug. Placing primary keywords at the beginning of the title ensures they appear at the start of the URL, dramatically improving visibility on Google and Eventbrite. Conversely, placing keywords at the end creates a less effective URL and weakens search ranking from the outset. Getting this step wrong can undermine the entire organic marketing effort.[00:12:15] The Long-Term Value of an Eventbrite ListingA unique feature of Eventbrite is that its event links remain active and discoverable long after an event ends. These expired listings function as permanent digital assets that continue to house links to websites, YouTube videos, and other resources. As such, an old event page acts as a long-term digital billboard, continuously driving traffic and brand visibility for months or years. This sets the stage for a practical case study.[00:17:45] Case Study 1: The Wreath-Making Workshop (A Paid Event Strategy)This case study demonstrates timing, targeting, and iterative improvement by combining organic SEO with minimal paid ads. A client's first workshop failed due to a two-week lead time, which was insufficient for search engine indexing. For the second attempt, strategic changes were made: scheduling four weeks in advance for algorithm indexing, creating a high-quality 4K promotional video, and running hyper-targeted Facebook ads with a $5/day test budget aimed at building community. The result was a sold-out event, providing a repeatable formula for marketing local, paid events.[00:31:00] Technical SEO Deep Dive: Why Your Website Pages Get De-IndexedThis section explains technical reasons for losing search ranking over time. Key factors include the "Last Modified" date in a website's XML sitemap, which signals content freshness to search engines; the 24-month lifespan of a blog post's SEO relevance if left untouched; and the actionable "update rule" of updating two old pages for every new one published. A contrast is drawn with podcast RSS feeds, which re-index the entire channel with each new episode, highlighting a unique SEO benefit of podcasting. This reinforces the importance of an updated digital presence to support event marketing.[00:48:15] Case Study 2: The Junk Journaling Workshop (A Free Event Strategy)This case study proves the core SEO principles work for a free event launched by a brand-new account with zero prior audience. The client created a new Eventbrite listing for a niche craft workshop with one month of lead time. Relying purely on organic discovery, all 10 free slots sold out to unknown attendees. The 10 conversions came from just 88 page views, indicating a highly effective, targeted listing. Page views continued to climb after sell-out, proving Eventbrite pages remain active SEO assets. The next step is community building.[00:55:30] The Post-Event Pivot: From Attendees to a CommunityThe conclusion shifts focus to the true metric of success: not just tickets sold, but building a returning community. The recommended strategy involves using a post-event QR code linked to a survey to gather feedback. For free events, this is a critical opportunity to ask attendees if they would return for a paid event, gauging future viability and gaining consent for upselling. This final step transforms a single event into a sustainable, community-driven business model.Memorable Quotes:"The fault begins with the message. And if the message is wrong, everybody is confused.""It's not about how many tickets were sold. It's how many people came, saw, went back, and came back again.""For every one page that you publish, update the last two that I just want to make it easy."Actionable Takeaways & Memorable QuotesTop 3 Actionable Takeaways:1. Prioritize Your Title: Always place your primary keywords (e.g., "Marketing Workshop," "Cooking Class") at the very beginning of your Eventbrite title to create an SEO-optimized URL slug.2. Respect the 3-Week Rule: Launch your event at least three to four weeks in advance. This gives search engine algorithms the necessary time to index your page and show it to relevant audiences organically.3. Plan the Post-Event Follow-Up: The event isn't over when it ends. Use a simple QR code survey to collect feedback and, for free events, to ask attendees if they would be willing to pay for a future version.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Would you like access to our advanced agency training for FREE? https://www.agencymastery360.com/training If AI can now write, design, and build faster than your team, what does a profitable agency actually sell next? Most agency owners have experienced a weird mix of excitement and anxiety about AI. On the surface, it feels like everything is changing overnight, including websites, content, search, development, and even how clients perceive value. Underneath that panic, though, there's a calmer truth: the fundamentals of running a great agency haven't changed at all. The tools have. Today's featured guest talks candidly about where AI actually helps agencies, where it's wildly overhyped, and why agency owners who focus on systems, relationships, and leverage will win while everyone else burns out chasing shiny tools. Eric Weidner is the founder of Workbox, a digital agency specializing in websites and custom applications for pharmaceutical companies and pharma marketing agencies. With a background that stretches back to the early days of the web, Eric has built, rebuilt, and adapted his agency multiple times, and today he's deep in the practical application of AI for real agency work, not just demos and hype. In this episode, we'll discuss: How agencies are positioned to win with AI. Avoid creating client disappointment with incorrect use of AI. The brutal reality for agencies that rely on "set it and forget it" marketing. Subscribe Apple | Spotify | iHeart Radio Sponsors and Resources E2M Solutions: Today's episode of the Smart Agency Masterclass is sponsored by E2M Solutions, a web design, and development agency that has provided white-label services for the past 10 years to agencies all over the world. Check out e2msolutions.com/smartagency and get 10% off for the first three months of service. The Road to Becoming a Long-Term Agency Operator Eric fell into web development in the mid-90s while working as a secretary administrator at a law firm in San Francisco. Exposure to early tech including computer networks, WordPerfect, XML, and eventually HTML turned into freelance work. That freelance work led to clients and eventually an agency. His story mirrors how most agencies actually begin, with skill, opportunity, and momentum. The problem is that what gets you started is rarely what helps you scale. Eric's longevity comes from his willingness to evolve without abandoning the fundamentals that keep agencies profitable. And that's the trap many agency owners fall into today: assuming AI is a complete reset instead of a force multiplier for the right business model. Why AI Feels Like a Career Defining Moment for Agencies When ChatGPT first came out, Eric didn't treat it like a novelty. He went all in because, for the first time in years, the intellectual challenge of building and running an agency felt exciting again. For a lot of seasoned agency owners, the business had become… static. Same services. Same delivery challenges. Same team bottlenecks. AI cracked that open. Suddenly, there were new problems to solve, new efficiencies to unlock, and new ways to multiply output without multiplying headcount. Ai introduced a chance to rethink how work gets done, how fast ideas move, and how agencies create leverage, not just more work. Eric has no blind optimism when it comes to AI. It isn't magic, and it's not ready to replace strategic thinking. But it is a force multiplier for agencies that understand systems. That's the opportunity most agencies are missing. Instead of asking, "How do we sell AI to clients?" the smarter question is: "How do we use AI to reduce friction, speed up delivery, and improve results—then package that advantage?" Agencies that do this become faster, leaner, and more profitable. Agencies that don't end up stuck in fulfillment, competing on price, and drowning in tools they don't fully understand. AI Is Powerful But It Still Needs a Human Brain AI tools can feel like a superpower, especially if you've never loved certain parts of your job. Writing, development, ideation, and prototyping are faster than ever. But there's a catch. AI works best at the first pass. Ask it to build a landing page, mock up a system, or outline functionality, and it shines. Ask it to make nuanced, detailed changes across a complex system, and it starts to fall apart. In a  sense, AI is like a drunk intern—brilliant on the first assignment, frustrating when you ask for revisions. For agency owners, this matters because selling AI as a silver bullet is a fast way to create client disappointment. The agencies that win will be the ones who understand where AI increases leverage and where human judgment still matters. Websites, Search, and the Shift Nobody's Talking About One of the most important things to understand if you're building a website nowadays is that we're not building websites just for humans anymore. As AI-driven search becomes more dominant, users don't always need to click through to a site to get answers. That changes how content, SEO, and authority work. Eric points to GEO—Generative Engine Optimization—as the next evolution of SEO, where freshness, clarity, and structured authority matter more than volume. This creates a brutal reality for agencies that rely on "set it and forget it" marketing. To stay visible, brands must publish consistently. Content often needs to be less than 90 days old to stay relevant in AI-driven systems. For agency owners already stuck in fulfillment, this is a warning sign. More services, more content, more tools without better systems just equals faster burnout. Content Alone Isn't Enough. Your Voice Builds Trust With AI flooding the internet with content, differentiation matters more—not less. People don't just consume content, they build relationships with voices they trust. That's why podcasts, communities, and consistent thought leadership outperform random marketing tactics. When people hear you think out loud for years, trust compounds. In an AI-saturated world, that human connection becomes the advantage. Or as Jason puts it: when agency owners say they need more leads, the answer is often boring but effective. Build a platform. Build trust. Stay visible. Do You Want to Transform Your Agency from a Liability to an Asset? Looking to dig deeper into your agency's potential? Check out our Agency Blueprint. Designed for agency owners like you, our Agency Blueprint helps you uncover growth opportunities, tackle obstacles, and craft a customized blueprint for your agency's success.

If there's one thing that we absolutely knew would be coming along with the increased interest and use of AI, it would be… more acronyms! And, along with the acronyms, we pretty much could predict that we see a lot of online flexing through casual dropping of said acronyms as though they're deeply understood by everyone who's anyone. We tackled one such acronym on this episode: MCP! That's "model context protocol" for those who like their acronyms written out, and Sam Redfern joined us to help us wrap our heads around the topic. You see, MCP is kinda' like some other more familiar acronyms like API and XML. But, it's also like… fingers? Sam's enthusiasm and explanation certainly had us ready to dive in! This episode's Measurement Bite from show sponsor Recast is an explanation of model robustness from Michael Kaminsky! For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

An airhacks.fm conversation with Johan Haleby (@johanhaleby) about: first computer experience with Commodore C64 and typing Basic programs from instruction manuals, early gaming experiences and interest in understanding load commands, transition to Amiga 500 Plus for demo scene scripting and composition, moving to PC era with 486 SX25 and four megabytes of RAM, learning Turbo Pascal and creating 2D Super Mario-inspired games, experimenting with inline assembler in Pascal and reading "The Art of Assembly Programming", reverse engineering games using Win32 disassembler to bypass license checks, studying computer science at Blekinge and Lund University in Sweden, first job at JayWay consultancy firm working on IKEA project in 2005, early adoption of Spring framework and automated testing practices, comparison of old-style EJB with heavy XML configuration versus Spring's lightweight approach, the evolution from XML-based configuration to annotation-based Java EE 5 and 6, creating PowerMock with colleague Jan Kronqvist to mock static methods and final classes, using asm and JavaAssist for bytecode manipulation instead of AspectJ, implementing custom class loaders where each JUnit method executed in different class loader, deep clone module for cloning object graphs between class loaders, tight coupling challenges between PowerMock and Mockito/EasyMock/JUnit versions, transition from EasyMock's record-replay pattern to Mockito's when-then approach, modern preference for avoiding mocks and testing against real cloud environments, optimizing for fast CI/CD pipelines rather than local simulation, structuring code to separate infrastructure concerns from pure business logic, using Java Records as pure data carriers versus adding behavior to records, Clojure-inspired philosophy of decoupling state from behavior and identity, Rich Hickey's "Simple Made Easy" talk and definitions of simple versus easy, multi-methods in functional languages as alternative to polymorphism, domain modeling example with network devices and fiber channel connections, benefits of object-oriented polymorphism for transparent persistence and simple code, avoiding religious adherence to patterns in favor of pragmatic solutions, Maven's stability and opinionated approach versus Gradle's flexibility, reducing external dependencies and Maven plugins in favor of CI/CD automation, the NPM ecosystem's over-modularization compared to Java's more reasonable approach, decline of OSGi hype and return to simpler monolithic architectures, Johan's current work on Occurrent Event Sourcing library and cloud events Johan Haleby on twitter: @johanhaleby

More React2Shell Exploits CVE-2025-55182 Our honeypots continue to detect numerous React2Shell variants. Some using slightly modified exploits https://isc.sans.edu/diary/More%20React2Shell%20Exploits%20CVE-2025-55182/32572 The Fragile Lock: Novel Bypasses For SAML Authentication SAML is a tricky protocol to implement correctly, in particular if different XML parsers are used that may not always agree on how to parse a specific message https://portswigger.net/research/the-fragile-lock December Updates Causes issues with Microsoft Message Queuing https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#message-queuing--msmq--might-fail-with-the-december-2025-windows-security-update

AI has exploded across the legal industry but for many lawyers, it still feels overwhelming, risky, or simply “not for them.” Today's guest has made it his mission to change that. Joining us is Robert Eder an intellectual property lawyer, legaltech educator, and one of Europe's leading voices on AI prompting for lawyers. Robert designs legal automation solutions, and teaches lawyers around the world how to use AI safely, effectively, and creatively. Robert has trained hundreds of lawyers across Europe and is one of the clearest voices on how to use AI responsibly, safely and with real legal precision.  Here are a few standout takeaways:  Lawyers aren't bad at prompting they're undersold. Their analytical mindset actually gives them an advantage.  Most people still treat AI like Google. Adding structure through XML tags, roles and answer-levelling changes everything.  The first AI skill every lawyer should learn isn't drafting it's controlling output. Structure before substance.  Hallucinations aren't a deal-breaker. Responsible AI frameworks give you quality control, not guesswork.  You don't need 70% of AI tools on the market. With the right prompting, one model + the right workflow beats shiny software every time.  Legal prompting is not the same as general prompting. Law has edge cases, nuance, and risk your prompts must reflect that. Two general points to reflect on:Lawyers don't need to become engineers. They need to become better communicators with machines.If you don't understand prompting, you'll always think AI is unreliable — when in reality, it's only as clear as the instructions you give it. It's practical, hands-on and genuinely career-shifting. AI isn't replacing lawyers. Lawyers who understand AI are replacing the ones who don't.

Power of Pinterest and Evergreen Content Marketing Masterclass for Businesses with Favour Obasi-Ike | Sign up for exclusive SEO insights.

Podcasting 2.0 December 5th 2025 Episode 243: "Nuts & Logs" Adam & Dave poddy training, junie, major dev talk and more! ShowNotes We are LIT NYC? Alby Hub? AI stats analysis Alt Enclosure Video New aggregatory open build GitHub - Podcastindex-org/feedparser: The XML parser that converts saved podcast feeds into intermediary files for SQL ingestion. TTS Podcasts on OP3 Cloudflare Outage Decentralization Transcript Search What is Value4Value? - Read all about it at Value4Value.info V4V Stats Last Modified 12/05/2025 14:32:55 by Freedom Controller

Fake adult websites pop realistic Windows Update screen to deliver stealers via ClickFix The latest variant of ClickFix tricks users into copy/pasting commands by displaying a fake blue screen of death. https://www.acronis.com/en/tru/posts/fake-adult-websites-pop-realistic-windows-update-screen-to-deliver-stealers-via-clickfix/ B2B Guest Access Creates an Unprotected Attack Vector Users may be tricked into joining an external Teams workspace as a guest, bypassing protections typically enabled for Teams workspaces. https://www.ontinue.com/resource/blog-microsoft-chat-with-anyone-understanding-phishing-risk/ Geoserver XXE Vulnerability CVE-2025-58360 Geoserver patched an external XML entity (XXE) vulnerability. https://helixguard.ai/blog/CVE-2025-58360

An airhacks.fm conversation with Ondrej Mihalyi (@OndroMih) about: OmniFish company founding with former Payara employees, Arjan Tijms as Jakarta EE Security lead and Jakarta EE 10 coordinator, David Matejczyk as Glassfish project lead and main contributor, OmniFish as the main maintainer and driver of GlassFish development, GlassFish optimization and bug fixes, embedded GlassFish improvements for command-line execution, comparison with Payara Micro, Slovak and Czech Christmas traditions including cemetery visits on Christmas Eve, traditional Christmas cookies like medovník (honey cookies) and perník, carp preparation for Christmas dinner with potato salad variations, fish scales tradition for wealth, Jakarta EE stability and backward compatibility over 15 years, migration from Java EE to Jakarta EE namespace changes, comparison between Jakarta EE and Spring regarding XML configuration history, Convention over Configuration in Java EE 5 and 6, WebSphere and WebLogic legacy issues, GlassFish as reference implementation advantages, runtime vs application server distinction, JSON-P usage for serverless lambda events, MicroProfile Health clean room implementation, Piranha experimental framework with new Servlet container implementation, AI and LLMs excellent knowledge of Jakarta EE specifications, no hallucinations when generating Jakarta EE code, separation of runtime and application deployment Ondrej Mihalyi on twitter: @OndroMih

The Dental A-Team often hears from team members who feel like they're not good enough. In this episode, Kiera shares with listeners how to switch from harmful self sabotage and comparison to a healthy awareness of growth and positivity. Episode resources: Subscribe to The Dental A-Team podcast Schedule a Practice Assessment Leave us a review Transcript: Kiera Dent (00:00) Hello, Dental A Team listeners. This is Kiera and today I want to dive into something that I think is really important. I feel, hear this from a lot of people. I've coached a lot of dentists. I've worked with a lot of team members. And so I feel like I've got a pretty good background on how to talk about this. And I think just as human nature, and I'm not saying that all of us are there, but   Every dentist, every office manager, every team member I talk to, no matter how successful or how terrible they're doing, they say, I'm not doing well. I'm not doing enough. Like I'm not doing good enough. And I just wanna like dig into this a little bit today because I think it's a lie that we all believe to some level. We feel this imposter syndrome. We feel this... ⁓   I don't know. It's just this weirdness that I want to help you rewire that story and to maybe give a different perspective on that, because the reality is you're doing better than you think you are. And I want to reset and reframe that internal dialogue because I believe being your own best cheerleader or your own worst critic, both of them have pros and cons. And I think like there's so much icky in the world that why don't we start to become your best cheerleader? I truly do believe the quote that ⁓ Tony Robbins says like where   where focus goes energy flow. So if we're focused on not being good enough or why am I not good enough or I don't know how to do this. Well, yes, there's a line of humility that I appreciate. There's also a line of self sabotage that I think we need to start to cut that script and become even stronger. really, Dental A Team's mission is to positively impact the world of dentistry in the greatest way possible and to help you build thriving practices, thriving leaders, not just surviving, not just hoping and like skirting along. Dentists always want to know how they're doing compared to other dentists.   And so really just giving you kind of that baseline to help you out. ⁓ This is the emotional side of leadership. This is the self-worth, the confidence that rewiring the not enough trap that I wanna just like dig into. And it's just more of a conversation and hopefully bringing some insights and some highlights to help you stop that narrative to really highlight the growth that you can have and just to give you some better. I don't know, just a hug. You're doing so good out there. And I think like as a proud mom of you.   ⁓ Just reminding you of how good you are doing, not better than you are, not worse than you are, but realistically where you are. And I think so many of us accidentally self-sabotage the goodness that we have rather than celebrating how great we're doing. ⁓ And again, momentum builds. So let's build momentum of positivity rather than momentum of negativity. So ⁓ I think the first thing that I like to look at is like, what is the root belief that causes you to have it? So like these thoughts are coming from somewhere. So is it past experiences? Is it comparisonism? Is it perfectionism?   ⁓ I went to a Tony Robbins conference. I do love Tony so much. I have a great time there. I don't think everything's perfect, but I think a lot of great things are, are good in it. And I went to, my favorite thing is date with destiny. And I went to it last year and, ⁓ Tony always has this talk about our towards values and our way values. And, he says, why is it that we try it? We do so good in life, making it hard to feel good and easy to feel bad. And I think about this a lot. And so last year, my word was comparison and.   He actually has you go on this whole rant. So if you can imagine, I feel I present in such a different way than how I was at that conference. ⁓ The beast was unleashed, we'll put it that way. One of my dear friends was with me and they said that they've never seen Kiera like 4.0 version come out. And what Tony has you do is you actually go through, cause comparison was actually one of the biggest things that was holding me back in life. I was comparing to all these other women about my body, about my looks, about my business, about everything.   I realized that my self-sabotaging was from a deep-rooted piece and like prior to that, ⁓ was fear that I let go of. was fear of all these things. And what Tony has you do is you go on this monologue, this rant to basically just see how much of life you've lost by having this. So I went into comparison and I said like, Kiera Dent, see, hear, feel, and know that I will never, ever succumb.   to the limiting and self-sabotaging and ludicrous lie of comparison. And then you go on a rant. And luckily Eminem, I do have a side nickname of DJ Skittlez. Yep, I wanted to be a rapper with Eminem. So I figured Skittlez with a Z was gonna be my rapper DJ name. So if you ever come voting with me, DJ Skittlez does come out voting to make your perfect playlist.   But Eminem was on and it was such a good thing for me. And I remember just unleashing the beast of this comparison and you yell and you scream and you just like, you know, like, and the goal is that you, you look at your life from this lens of how much has this self sabotaging piece taken from you. And when I looked at it, like I wasn't participating fully with my family. wasn't working out at the gym because I didn't want to be compared to other women. I wasn't, ⁓   being as bold in business because I was comparing myself to what other people did and just how much of life was being sucked away from me. And so with that, if that's something like for you to just look to see where is it and what's maybe the one or two ⁓ values that you're holding onto that make you feel bad, that I would encourage to be a way value, not something we want to go towards. So for me, I have on comparison and like comparison only shows up for me when I forget that I am like just, ⁓   For me, like what I will say, I do believe in God, that I am God's greatest creation. when I, so now what I've done is I've taken comparison and I flipped it. So like, if I ever start comparison, it's only due to me forgetting that I'm God's greatest creation. And that quickly for me eliminates that. And so, and it's like fear only if I forget that I have like magic and brilliance that spews from me.   So what the goal is, is you take that root belief and you flip it and you figure out what it is. And then what is something like, it's only if I were to forget that I am like brilliant and have like unlimited potential within me. So like for fear or comparison or perfectionism or whatever it is. And so what is that? Where did that story begin? And maybe you don't know. ⁓ And maybe go through a rant if you want, or maybe just write a new definition and make it harder to feel that. So for me,   It's actually pretty hard for me now to feel comparison. Like I can go back to that, like Kiera 4.0, if you were to call my friend Pierce, he's been on the podcast, he will tell you Kiera 4.0 came out on that comparison rant to where I feel like I literally was able to obliterate it to where it's not there. And for you looking at why am I not good enough, maybe if we can find one or two of your route towards values and away values, what are those away values? And could we...   Could we acknowledge it? Could we see why it's there? And could we maybe decide to put that to rest for a little while? ⁓ And I think when I do this exercise and I write out what success means, it's crazy how many weird rules I have to put in to be successful. And maybe even for yourself, writing out like today what you feel you have to do to be successful. Oftentimes this is why we feel like we're not enough is because we've made this laundry list where it's impossible for any person.   ourselves or someone else to ever hit that level. ⁓ I talked to a friend once and she was like, yeah, for me to be successful, I have to have, I think she told me like 10 million in her bank account, which she was not even close to that. She had to have her body size be X. She had to drive a certain car. She had to live in this. And it was like, wow, well, no wonder we feel this. That's the root belief. It's so hard for us to even feel successful versus I feel successful anytime I make a patient happy.   What you do on that is we're not changing the rules of the game, but we are making it easier to feel good and harder to feel bad. So the only time I'm ever going to feel comparison is when I forget that I'm God's greatest creation. Well, yeah, like I'm not going to forget that. Like I really do think that. And not to say that I'm better than anybody else. I just truly do believe that all of us in our own way are truly God or the universe or whatever's greatest creation. I, gosh, like I feel emotional about that. I really do just believe that that's who you are.   I believe that human souls are that way. I believe that. and so it's one of those things like as a proud mom for you, if you want to take that on for a hot minute, go for it if you want to write it. But when doctors can rewrite, when you feel behind or you feel like you're not enough, maybe what enough feels like you could look at it, like list it off, but then maybe make it a bit easier for you to feel enough today. maybe being enough is reminding myself that like just being alive is enough.   Like think about how the magic of being a living soul is. Well, shoot, that is enough. And like, what does enough even mean? What does success even mean? And what's wild about that is this, there's maybe a few pieces to it. So call to action on it. Cause I like to make this tactical, even though it's such a soft skill is one, let's think of where these thoughts came from. So like, what are the top two things that are holding you back?   from feeling like you're enough. Like what are those? Is it comparison? Is it experiences? Is it like maybe someone told you that? I don't know what it is, but like, can you identify what that is? Then can you find an area where you don't feel like you're doing enough or you're not good enough and ask where that belief started and then rewrite how you're going to feel that. So what does enough mean or what does being perfect mean or what does success mean? And can we change the rules of making it harder to feel bad?   and easier to feel good. Now I know this won't be perfect and I know you're gonna like be clunky with me doing this, but really try it, take it on because if we can even change it just a smidge, I feel like that's a win. That's number one. Let's identify the root. Let's change our identity. Let's let it go. Let those pieces go and make it harder to feel bad and easier to feel good. Okay? Then we wanna measure what like honestly matters because sometimes we might be measuring against the wrong measuring stick.   So many people are like, well, I'm not enough or I'm not far enough along. And I'm like, but why? And like, because I have to be like so and so. And I'm like, but do you want their life? I'm not here to say like compare, like, I just want to know what's your life, what's your version of success. And that's where in Dental A Teaem people are like, well, Kiera, what do all your clients have to hit? And I'm like, there is no standard of what you have to hit. You have to be profitable. Yes. And you have to be growing for your own self. I don't care what that looks like, but those are like pretty much the only measurements that we have. There's no set standard. There's none of that because I want you to   truly be measuring against your own yardstick. So ⁓ for this next piece is going to be like, let's measure what success really is for you. ⁓ Maybe it's on value, values, maybe it's on lifestyle, but not on volume. And then I want you to like reflect on your life of what have you done to get closer to that, that goal or that success or being enough. ⁓   where you're focused more on that outcome and the life you're living rather than measuring up against someone else's yardstick. So, and sometimes it's like pilots, right? Like if you were a pilot and you're on a course and you're like, well, shoot, I'm going to end up over in Sweden, but I was really trying to get over to Bora Bora. Well, great. We just were on the wrong path. We're, focusing on the wrong target. And so for you measure what really matters and go for the right target, go for where you ultimately want to end up in life, go for those pieces rather than just like,   I don't know, being on the success metrics that doesn't actually matter for you. When I wrote out success last year, it was like, I have to be making XML, I have to be working this amount. And I was like, Kiera, you know better than this, why do you do this? And I think it's like, I don't know, I don't know where this stems from. I don't know why as a society we're obsessive with not being good enough, no matter how great we do, not.   Not being proud of ourselves, not being our biggest fans. ⁓ And so for that, I really think like step one is find the root. Step two is going to be figure out what success is and rewrite it to where it's easier to achieve it rather than harder to achieve it. And again, I'm not trying to move the goalpost on you. I'm just trying to build the momentum and fuel because the happier people do better in life, the more depressed and the ones who feel worthless and that they're not doing well enough, they don't do as good. So I'm trying to make it easier for you to hit success today and to realize you are successful rather than   having a harder to ever achieve it and making it so impossible you'll never achieve it. And then number three is, rewire this. So kinda like what I did, we're gonna rewire. So ⁓ confidence, certainty, being proud of yourself is a muscle and you have to train it. So every single day I literally write in my journal, things I love about myself or things where I've been successful or things that like whatever it is,   where like I've been proud of myself or whatever it is, but you start to train in an actual way. So like we can replace our negative thoughts with affirmations. We can surround ourselves with people who are great. We can celebrate the the wins. Like every day I have to write down three great things that I did from the day before. Sometimes saying it out loud, sometimes writing it down. But when you start to do this and you start to even shift that into your team where we start to focus on the wins that we've had every single day.   Like we always heard our offices out of like, are the wins you've been having? And it's purposely because I want to build a snowball of momentum rather than a snowball of negativity. It's very easy when we've trained ourselves, like a pencil groove in like old school desks when we used to be in school and we'd have those pencils and we just keep digging deeper and digging deeper. We are now rewiring you to start focusing on how you've been successful. Like for me, like comparison, like it used to be like, my gosh, like every day, like I literally, you guys used to be consumed by comparison.   I would sit here day in and day out and be like, I'm just not that great. I will tell you, and it's been seven months since I did that exercise. I'm not exaggerating. I can count probably on one hand, the number of times I've compared and I catch myself pretty quickly. I'll tell my husband like, gosh, like there was one time and I'm like, business are doing X, Y, Z and like, like, why am I not doing that? And I'm like, because I'm living my own freaking life over here. Like, yeah, I can be doing different things, but   I am so intentional with the life I'm building and I'm so proud of what I've done. And then I just like flip into this, like, Carrie, you're freaking killing it. And like, these are the great things that you've done. I'm like, let's start celebrating the wins. while yes, like comparison serving me nothing, you playing small is serving you nothing. You thinking that you're not good enough is serving you nothing, but you having the confidence in yourself, you reminding yourself of the good things you freaking took a risk to be a business owner. You go in day in, day out, you have led a team. became a dentist.   Those are some pretty big milestones and to be proud of yourself and then to figure out how we can start to do this every single day and to train that muscle. ⁓ I know this sounds fluffy and I know this sounds woo woo and I know this sounds like I'm not doing that. I would just encourage you to try to figure out one, where's the root and what are the one or two things that are really keeping you back. Then two, what's your success ladder and how can we make success more achievable rather than further away?   And then three, can we rewire that and make it to where we are continually writing who we want to become? ⁓ Another great quote by Tony Robbins, I tell you, it just comes to me constantly. He says, are you the creator of your life or the manager of your circumstances? And I think by all these things I've talked about today on the podcast, this is helping you be the creator of your life, not the manager of your circumstances. You're creating the success you want. You're creating the identity that you want. You're creating the person you want to be.   And if it's tricky for you, reach out like I have literally there's a client, Corey. I'll actually say his real name. I know he listens to the podcast periodically. Uh, and I know he's an amazing human and Corey will tell you that I have done these exercises with him and we joke about it, but he and I have such a close relationship. And I'm like, it's because we saw the real raw versions of each other. We created these new pieces. We celebrate the wins together. We don't allow each other to get into these darker holes. We remind each other like   It's accountability buddies on living our best life. And so for you, get the identity right, redefine your success metric, measuring thing, and then retrain your brain and the words you say to where hopefully in six months from now, when we come back to this, you can say, just like I can say, I'm not perfect. And I literally was able to let go of so much of the comparison that used to suffocate me from the joy of life that used to rob me from that.   and to not have it be obsessive. Now there's other obsessive things that will come up, but at least that one I feel is tempered, is tamed, is not there as much and being able to bring that on. So for you, you already are enough. gosh, like if you could look back at who you were when you were 10 and then tell them who you'd be today, I you'd be shocked and so proud of that. If you could think of like a little child, think of yourself that way and like, you're not going to tell that kid like, hey, freaking walk already, like stop crawling.   You'd be so proud of them, of the little milestones. And we celebrate children. And I feel like let's celebrate ourselves as adults. Let's change that if we can. Let's create a different path. Let's create a different model. That way you can thrive. And really, truly leading from the truth that you are enough, not the insecurity of that. I believe that this, like doing this is just as important as systems and strategy. I believe that doing the inner work makes you the   The boss, the leader that your practice, your team and your patients need you to be. And it's not fluff and it's not that. So don't skip this inner work. ⁓ And I'm happy to help you share this with someone that you know, needs to hear that they are enough ⁓ that you're doing better than you think you are. That your success is so freaking amazing. It doesn't matter what other people are doing. We look at other people for examples, if it's what we choose to do, but we're so committed to living our best lives and the best version of ourselves.   ⁓ I only use other people as an example of what's possible, not of a comparison of what I'm not doing. And for you, whatever it is for you, truly, let's help you achieve that. And if I can be a cheerleader in your back corner, if I can be like a little Jiminy cricket on your shoulder, if our team can help you, this really truly is a zone for you to look to see where is it coming from? What can I change? How can I make it easier to feel successful today and that I am enough today? And then reinforcing that with daily habits.   It sounds so silly, but I promise you the fastest, the strongest force in the human nature is the need to stay consistent with who you believe you are, not who you actually are. So let's change that belief. Let's change that identity and help you get the happiness that you deserve. This is something I'm very passionate about, something that I love so much. And I'm so grateful to be able to chat with you guys on the podcast. So reach out if I can help in any way. Hello@TheDentalATeam.com. And as always, thanks for listening. I'll catch you next time on The Dental A Team podcast.  

An airhacks.fm conversation with Olimpiu Pop (@olimpiupop) about: Romanian developer's journey from 486 computers to Transylvania Java User Group, early programming with Turbo Pascal at age 9-10, playing games like Jazz Jackrabbit and Prince of Persia, influence of Star Trek and science fiction on career choice, mathematics olympiads participation, computer science high school education, learning C and FoxPro, Java vs .net ecosystem in Romania during 2000s, Microsoft's university infiltration strategy, first Java exposure with version 1.4, Siemens internship on telecommunications servers, neighborhood network building projects, working without home internet until 2005-2006, nearshoring company experience, EJB and Spring framework with XML configuration, master's studies at Johannes Kepler University Linz 2008-2011, working with fabasoft on observability systems, .NET development for two years with C#, attributes vs annotations comparison, Java ME micro edition development, implementing DTOs and service architectures, agile methodology adoption, iterative development practices, data gravity concept from Ruby on Rails, working for Uniqa with WebMethods, brueckner Group spin-off developing industrial software, DevOps implementation with Jenkins and Git, choosing between Mercurial and Git version control, Broadridge financial technology work, stock exchange monitoring systems, low-latency Java implementations, Mechanical Sympathy and Disruptor pattern, taking over Java User Group from Gabi Pop, managing Java Advent Calendar for 15 years, WordPress to Java migration plans using quarkus-roq, transition from coding to management roles, challenging microservices adoption, modular monolith advocacy, Java verbosity improvements and scripting capabilities, young developers returning to Java, typescript developers discovering Java patterns, Romanian tech scene evolution, Cluj coffee culture and steampunk bars Olimpiu Pop on twitter: @olimpiupop

Shawn Tierney meets up with Henrik Pedersen and Jacob Abel to learn about OTee Virtual PLCs in this episode of The Automation Podcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Listen to The Automation Podcast from The Automation Blog: The Automation Podcast, Episode 252 Show Notes: Special thanks to Henrik Pedersen and Jacob Abel for coming on the show, and to OTee for sponsoring this episode so we could release it “ad free!” To learn about the topics discussed in this episode, checkout the below links: OTee Virtual PLCs website Schedule an OTee demo Connect with Henrik Pedersen Connect with Jacob Abel Read the transcript on The Automation Blog: (automatically generated) Shawn Tierney (Host): Thank you for tuning back into the automation podcast. Shawn Tierney here from Insights. And this week on the show, I meet up with Henrik Pedersen and Jacob Abel to learn all about virtual PLCs from OTee. That’s o t e e. And, I just thought it was very interesting. So if you guys have ever thought about maybe running virtual PLCs to test some processes out, I think you’ll really enjoy this. With that said, I wanna welcome to the show for the very first time, Hendrik and Jacob. Guys, before we jump into your presentation and learn more about what you do, could you first introduce yourself to our audience? Henrik Pedersen (OTee): Yeah. Sweetly. So my name is Hendrik. I am the cofounder, COO, OT, a new industrial automation company, that, we’re really glad to present here today. I have a background from ABB. I worked eleven years at ABB. In terms of education, I have an engineering degree and a master degree in industrial economics. And, yeah, I’m I’m excited to be here. Thanks, Rom. And I’ll pass it over to Jake. Jacob Abel (Edgenaut): I’m, Jacob Abel. I’m the principal automation engineer at Edgnot. EdgeNaught is a systems integrator focusing on edge computing and virtual PLCs. My background is in mechanical engineering, and I’m a professional control systems engineer, and I have thirteen years experience in the machine building side of industrial automation, specifically in oil and gas making flow separators. And I’ll hand it back to Henrik here. Henrik Pedersen (OTee): K. Great. So OT, we are a a new industrial automation company, the new kid on the block, if you will. We’re a start up. So, we only started, about three years ago now. And, we focus solely on virtual PLCs and and the data architectures allow you to integrate virtual PLCs in in operations. And, you know, some of the listeners will be very familiar with this first, thing I’m gonna say, but I think it’s valuable to just take a take a little bit step back and and remember what has happened in in history when when it comes to to IT and OT and, and and what really what really happened with that split. Right? So it was probably around the ‘9 you know, around nineteen nineties where the the the domain computer science were really split into these two domains here, the IT and OT. And, and that, that was, that was kind of natural that that happened because we got on the, on the IT side of things, we got Internet, we got open protocols and, you know, we had the personal computers and innovation could truly flourish on the IT side. But whereas on the OT side, we were we were kind of stuck still in the proprietary, hardware software lock in situation. And and that has that has really not been solved. Right? That that that is still kind of the the situation today. And it this is what this is obviously what also, brought me personally to to really got really super motivated to solve this problem and and really dive deep into it. And I experienced this firsthand with with my role in NAD and, how how extremely locked we are at creating new solutions and new innovation on the OT side. So so we’re basically a company that wants to to truly open up the the the innovation in this space and and make it possible to adopt anything new and new solutions, that that sits above the PLC and and, you know, that integrate effectively to to the controller. So I I have this this, you know, this slide that kind of illustrates this point with with some some, you know, historical events or or at least some some some big shifts that has happened. And, Aurene mentioned a shift in nineteen nineties. And it wasn’t actually until ’20, 2006 that Gartner coined this term OT, to explain the difference really what what has happened. And and, you know, as we know, IT has just boomed with innovation since since the nineties and OT is, is, is slowly, slowly incrementally getting better, but it’s still, it’s still the innovation pace is really not, not fast. So, this is also, of course, illustrated with all the new developments in in GenAI and AgenTic AI, MCP, and things like that that is kinda booming on on the IT side of things. And and and yeah. So, but we do believe that there is actually something happening right now. And and we have data that they’re gonna show for for that. Like, the the large incumbents are now working on this as well, like virtual PLCs, software defined automation and all kinds of exciting things going on on the OT side. So we do believe that that we will see, we will see a shift, a true big shift on the OT side in terms of innovation, really the speed in which we can, we can improve and adopt new solutions on the OT side. And this is kind of exemplified by, like, what what is the endgame here? Like, you could say that the endgame could be that IT and OT once once again becomes the same high paced innovation domain. Right. But then we need to solve those underlying problems, the infrastructural problems that are still so persistent on the OT side of things. The fine point of this slide is to just illustrate what’s happening right now. It’s like cloud solutions for control is actually happening. Virtual PLC, software based automation, AI is happening all at once. And we see it with the big suppliers and and also the exciting startups that’s coming into this space. So I think there’s there’s lots of great excitement now that we can we can expect from the OT side, in in next few years. Shawn Tierney (Host): Yeah. You know, I wanna just, just for those listening, add a little, context here. If we look at 1980, why was that so important? Why is this on the chart? And if you think about it, right, we got networks like Modbus and, Data Highway in nineteen seventy eight, seventy nine, eighty. We also got Ethernet at that time as well. And so we had on the plant floor field buses for our controls, but in the offices, people were going to Ethernet. And then when we started seeing the birth of the public Internet, right, we’re talking about in the nineties, people who are working on the plant floor, they were like, no. Don’t let the whole world access by plant floor network. And so I think that’s where we saw the initial the the divide, you know, was 1980. It was a physical divide, just physically different topologies. Right? Different needs. Right? And then and and as the Internet came out in the early nineties, it was it was now like, hey. We need to keep us safe. We know there’s something called hackers on the Internet. And and I think that’s why, as you’re saying in 2006, when Gartner, you know, coined OT, we were seeing that there was this hesitant to bring the two together because of the different viewpoints and the the different needs of both systems. So I think it’s very interesting. I know you listeners, you can’t see this, but I kinda want to go back through that and kinda give some context to those early years. And and, you know, like Henrik says, you know, now that we’re past all that, now that we’re using Ethernet on the plant floor everywhere, right, almost everywhere, on all new systems, definitely, that that becomes the right now on this on the today on the, on the chart. And I’ll turn it back to you, Henrik. Henrik Pedersen (OTee): Yeah. I’ll search that. I just wanna echo that as I think that there are really good reasons for why this has happened. Like, the there has you could argue that innovation could flourish on the IT side because there was less critical systems, right, less, more, you know, you can do to fail fast and you can do, you can test out things on a different level. And so so there’s really lots of good reasons for why this has happened. We do believe that right now there is some really excitement around innovation, the OT side of things and and this pent up kind of, I wouldn’t call it frustration, but this pent up potential, I think is the right word, is is can be kind of unleashed in our industry for for the next, next decade. So so we are like this is really one of the key motivators for me personally. It’s, like, I truly believe there’s something truly big going on right now. And and I I do I do encourage everyone, everyone listening, like, get in get in on this. Like, this is happening. And, you know, be an entrepreneur as well. Like, build your company, build and, you know, create something new and exciting in this space. I think I think this is this is a time that there hasn’t been a better time to create a new new technology company or a new service company in this space. So this this, this is something at least that motivates me personally a lot. So let me move over to kind of what we do. I mentioned I mentioned that we focus solely on the virtual PLC. This this is now presented in the slide for those that are listening as a as a box inside a open hardware. We can deploy a virtual PLC on any, ARM thirty two thirty two and and sixty four bit processor and x eighty six sixty four bit with the Linux kernel. So so there are lots of great, options to choose from on the hardware side. And and, and yeah. So you can obviously when you have a Virtual PLC you can think of it new in terms of your system architecture. You could for instance, you know deploy multiple Virtual PLCs on this on the same hardware and you can also, think about it like you can use a virtual PLC in combination with your existing PLCs and could work as a master PLC or some kind of optimization deterministic controller. So it’s it’s really just opening up that, you know, that architectural aspect of things. Like you can think new in terms of your system architecture, and you have a wide range of hardware to choose from. And, and yeah, So the the flexibility is really the key here, flexibility in how you architect your system. That CPU that you deploy on will will obviously be need to be connected to to the field somehow, and that’s that’s true, classical remote IO, connections. So we currently support, Modbus TCP and Ethernet IP, which is kind of deployed to to, our production environment, as it’s called. So moving on to the next slide. Like, this is kind of the summary of our solution. We have built a cloud native IDE. So meaning anyone can can basically go to our website and log in to into the solution and and give it a spin. And, we’ll show you that afterwards with with Jake. And the system interacts through a PubSub data framework. We use a specific technology called NUTS, for the PubSub communication bus. And you can add MQTT or OPC UA to the PubSub framework, according to your needs. So, and from that, you can integrate with, whatever whatever other, software you might have, in your system. So we have these value points that we always like to bring up. Like, this obviously breaks some kind of vendor lock in in terms of the hardware and the software. But it’s also, our virtual PLC is based on on the six eleven thirty one. So it’s not a lock in to any kind of proprietary programming language or anything like that. There is, there’s obviously the cost, element to this that you can potentially save a lot of cost. We have, we have verified with with with some of our customers that they estimate to save up to 60% in total cost of ownership. This is there is obviously one part is the capex side and the other part is is the opex. And and is this data framework, as I mentioned, is in in in which itself is is future proof to some extent. You can you can integrate whatever comes comes in in a year or or in a few years down the line. And, there’s environmental footprint argument for this as you can save a lot on the on the infrastructure side. We have one specific customer that estimates to save a lot on and this this particular point is really important for them. And then final two points is essentially that we have built in a zero trust based security, principle into this solution. So we have role based access control. Everything is encrypted end to end, automatic certification, and things like that. The final point is, is that this is the infrastructure that allows you to bring AI and the classical, DevOps, the the thing that we’re very used to in the IT side of things. Like, you you commit and merge and release, instead of, instead of the traditional, way of working with your automation systems. So I know this is like, this is pro pretty much, like, the boring, sales pitch slide, but, but, yeah, I just wanted to throw this this out there for for the guys that there is some there is some, intrinsic values underneath here. The way the system works, you will you will see this very soon, through the demo, but it’s basically you just go to a website, you log in, you create a project. In there, you would create your your PLC program, test, you code, you simulate. You would onboard a device. So onboard that Linux device that you you want to deploy on. This can be as simple as a Raspberry Pi, or it can be something much more industrial grade. This depends on on on the use case. And then you would deploy services like, as I mentioned, MQTT and OPC UA, and then you would manage your your your system from from the interface. And, I have this nice quote that we got to use from one of the customers we had. This is a global, automotive manufacturer that, basically tells us that it’s, they they highlighted the speed in which you can set this up, as as one of the biggest values for them, saving them a lot of hours and setting setting up the system. So I also wanted to show you a real you know, this is a actual real deployment. It was it was deployed about a year ago, and this is a pump station, or a water and wastewater operator with around 200 pump stations. They had a mix of of Rockwell and Schneider PLCs, and they had a very high upkeep, and they were losing a lot of data from these stations because they were connected over four g. When the Internet was a bit poor, they lost a bit of data in their SCADA systems, so they had these data gaps and things like that. So pretty pretty, you know, standard legacy setup to be to be honest. Quite outdated PLCs as well. So what they what they did for the first, pump station was they they, you know, removed the PLC. They put in a Raspberry Pi for for, like, €60 or, like, $70, connected it to to a to a remote IO Ethernet IP module they had, in in the storage, and deploy this data framework as I’m showing on the screen now. So so they that was that was the first station they put online, and they they chose a Raspberry Pi because they thought, okay, this is interesting, but will it work? And then they chose a pump station, which was was really just poor from before. So they had very little to to to lose to to deploy on this station. So so, yeah, this has been running for a year now without any any problems on a Raspberry Pi. We have obviously advised against using a Raspberry Pi in a critical environment, but they just insisted that that what that’s what they wanted to do for this first case. Shawn Tierney (Host): And I’ll back that up too. Your generic off the shelf Raspberry Pi is just like a generic off the shelf computer. It’s not rated for these type of environments. Not that all pump houses are really bad, but they’re not air conditioned. And I think we’ve all had that situation when it’s a 120, 130 out that, you know, off the shelf computer components can act wonky as well as when they get below freezing. So just wanted to chime in there and agree with you on that. For testing, it’s great. But if you’re gonna leave it in there, if you were in my town and you say you’re gonna leave that in there permanently, I would ask to have you, assigned somewhere else for the town. Henrik Pedersen (OTee): Yeah. Yeah. Exactly. No. So and and that point is also illustrated with the second station they brought online. So there they chose a much more industrial grade CPU, that, that, was much, you know, cost cost a bit more, but it’s more suited for the environment. And, and yeah. So this was, I can disclose it was a Bayer Electronics, CPU. So so yeah. And, and they reported, some good, good metrics in terms of, like, the results. They they said around 50 on the hardware, 75% on the management of the PLC system. So this relates more to that they have very a lot of, you know, driving out with the car to these stations and doing changes to their systems and, and updates. They no longer have any, any data loss. It’s local buffer on the data framework. They’ve increased tag capacity with 15 x, resulting in in four fifty five x better data resolution and a faster scan frequency. And this is actually on the Raspberry Pi. So so just just think of it as as the the even the even the, kind of the lowest quality IT off the shelf, computers, are are able to to, to execute really fast in in in, or fast enough for for, for these cases. So, Shawn, that was actually what I wanted to say. And, and also, you know, yeah, we are we are a start up, but we do have, fifth users now in 57 different countries across the world. And it’s it’s really cool to see our our our, our technology being deployed around the world. And, and yeah. I’m really, really excited to to, to get more, users in and and hear what they what they, think of the solution. So so yeah. I’ll I’ll with that, I don’t know if, Shawn, you wanna you shoot any questions or if we should hand it over to Jake for for for a demo. Shawn Tierney (Host): Yeah. Just before we go to Jake, if somebody who’s listening is interested, this might be a good time. It said that, you already talked about being cloud based. It’s, o t e e. So Oscar Tom, Edward Edward for the the name of the company. Where would they go if if they like what Jake’s gonna show us next? Where will they go to find out more? Henrik Pedersen (OTee): Yeah. So I would honestly propose that they just, reach out to to me or Jake, on on one of the QR codes that we have on the presentation. But they can also obviously go to our website, 0t.io,0tee.io, and just, either just, log in and test the product, or they could reach out to us, through our website, through the contact form. So yeah. Shawn Tierney (Host): Perfect. Perfect. Alright, Jake. I’ll turn it over to you. Jacob Abel (Edgenaut): Thanks, Shawn. Fantastic stuff, Henrik. I wanna take a second too to kinda emphasize some of the technical points that you, presented on. Now first, the the fact that you have the built in zero trust cybersecurity is so huge. So, I mean, the OT cybersecurity is blowing up right now. So many certifications, you know, lots of, consulting and buzz on LinkedIn. I mean, it’s a very real concern. It’s for a good reason. Right? But with this, zero trust built in to the system, I I mean, you can completely close-up the firewall except for one outgoing port. And you have all the virtual PLCs connected together and it’s all done. You know, there’s no incoming ports to open up on the firewall to worry about, you know, that security concern. You know, it’s basically like, you know, you’ve already set up a VPN server, if you will. It’s it’s not the same, but similar and, you know, taking care of that connection already. So there’s an immense value in that, I think. Shawn Tierney (Host): And I wanted to add to the zero trust. We’ve covered it on the show. And just for people, maybe you’ve missed it. You know, with zero trust is you’re not trusting anyone. You authorize connections. Okay? So by default, nobody’s laptop or cell phone or tablet can talk to anything. You authorize, hey. I want this SCADA system to talk to this PLC. I want this PLC to talk to this IO. I want this historian to talk to this PLC. Every connection has to be implicitly I’m sorry. Explicitly, enabled and trusted. And so by default, you know, an an integrator comes into the plant, he can’t do anything because in a zero trust system, somebody has to give him and his laptop access and access to specific things. Maybe he only gets access to the PLC, and that makes sense. Think about it. Who knows whether his laptop has been? I mean, we’ve heard about people plug in to the USB ports of the airport and getting viruses. So it’s important that person’s device or a SCADA system or a historian only has access to exactly what it needs access to. Just like you don’t let the secretary walk on the plant floor and start running the machine. Right? So it’s a it’s an important concept. We’ve covered it a lot. And and, Jake, I really appreciate you bringing that up because zero trust is so huge, and I think it’s huge for OT to have it built into their system. Henrik Pedersen (OTee): Yeah. Absolutely. Absolutely. Jacob Abel (Edgenaut): I wanted to highlight too the Henrik mentioned that the the backbone of the system is running on a technology called NATS. That’s spelled n a t s. And why that’s important is this is a a lightweight messaging, service, and it’s designed to send millions of messages per second. You know, that’s opposed to, you know, probably the best Modbus TCP device that you can find. You might get a couple 100 messages through per second. It’s millions of messages per second. It’s, you know, especially with, you know, we’re dealing with AI machine learning, you know, training models. I mean, we’re data hungry. Right? So this gives you the backbone too. You know, it’s like it can push an immense amount of tag data, you know, with ease. I think that’s another really important point. With that, though, I’ll I’ll get on to the demo. Henrik Pedersen (OTee): Oh, that’s great. We do we do see that, Jay, that most of our customers report on that, you know, 400 or 700 x better data resolution. And so it’s it’s a step change for for for the data resolution there. Yeah. Jacob Abel (Edgenaut): Excellent. So one of the things that I personally love about OT is how quickly you can get into the PLC once everything’s set up. So this is OT’s website, obviously, ot.io. So once you’re here, you just go to log in. And that brings in the login screen. Now I’m are I’m using my Google account for single sign on, so I can just click continue with Google. And this brings me into the main interface. And another thing that I love is that, you know, it is very simple and straightforward, you know, and simple is not a bad thing. Simple is a good thing. I mean, the way that things should be is that it should be, it should be easy and the finer details are taken care of for you. So right here, we have our main project list. I just have this one benchmarking program that I’ve imported in here. And you also have device lists, just a a test device that I’ve installed the runtime on. Just real quick. You know, you have a Martha, the AI assistant in the corner here. And, the documentation guides is up here. So you can get help or look into reference material very easily. It’s all right there for you. So I’m gonna open up this program here. So just a quick tour here. Right up here in the top left is basically where where most everything’s done. So if you click on this little down arrow, you can choose what virtual PLC runtime to attach it to. I’ve already attached it to the device. I installed the runtime on. You can add, you know, a new program, driver, function blocks, custom data types real quick here. Compile your program, download it to the device. Check the release history, which is really, really great. As you can, you can go into release history and you can revert to a prior version very easily. We got built in, version control, which is another, great feature. Henrik Pedersen (OTee): I can also just comment on that, Jake, that we do have we do have, in the quite short term roadmap to also expand on that with Git integration, that, a lot of our customers are are asking for. So yeah. Jacob Abel (Edgenaut): Awesome. Yeah. I mean, that’s that’s another, very hot topic right now. It’s, you know, getting getting the revision control systems, as part of, you know, at least the textual, programming languages. See, so, you know, we have a few, like, housekeeping things here. I mean, you can delete the program, export it. It’s a good good point here is that, OT complies with the PLC open, XML specification. So you can import or export programs, in this XML format, and it should work with solid majority of other automation software out there. You know, if you need to, you want to transition over to OT, you know, you can export it from your other software and import it rather easily. Got your program list here and, you know, just the basic configuration of, you know, you can add global variables that you wanna share between the different programs and POUs or, you know, change the, cycle rate of the periodic tasks, add more tasks. Let’s just get jump into this program here. Both the system uses the IEC sixty one one thirty one dash three standard structured text. So here’s just a little, quick benchmark program that I’ve been using to do some performance testing. Like you, you have the, the code right here, obviously. And on our, our right, the variable list, very easy to add a new variable and pick out the type. You can set a set of default value, add some notes to it. Super easy. So let’s go online. So if you have these little glasses up here in the top, right, you display live tag values. And so it’s grabbing from the runtime that’s running and plopping it right in here in the editor, which I I love the way it’s displayed. It makes it. And, you know, it’s one of the question marks is if you’re doing structured text instead of letter logic, like how it’s gonna show up and how readable is it gonna be. I think the, the text, like the color contrast here helps a lot. It’s very, very readable and intuitive. And we also have the tag browser on the right hand side. Everything is, organized into, you know, different groups. There’s the the resources and instances that you’ve set up in the configuration tab. So the by default, the tag the tags are all listed under there. And here too, you know, you can set tag values doing some performance testing, as I said. So this is, recording some some jitter and task time metrics. And that’s that’s really it. That’s the that’s the cloud IV in a nutshell. Super easy, very intuitive. I mean, it’s there there’s zero learning curve here. Shawn Tierney (Host): For the, audio audience, just a little comment here. First of all, structured text to me seems to be, like, the most compatible between all PLCs. So, you know, everybody does ladder a little bit differently. Everybody does function blocks a little bit differently. But structured text and, again, I could be wrong if you guys think out there in the in listening, think I’m wrong about that. But when I’ve seen structured text and compared it between multiple different vendors, it always seems to be the closest from vendor to vendor to vendor. So I can see this makes a great a great place to start for OT to have a virtual PLC that supports that because you’re gonna be able to import or export to your maybe your physical PLCs. The other thing is I wanted to comment on what we’re seeing here. So, many of you who are familiar with structured text, you know, you may have an if then else, or an if then. And and you may have, like, tag x, equals, you know, either some kind of calculation, you know, maybe, you know, z times y or just maybe a a constant. But what we’re seeing here is as we’re running, they have inserted at a in a different color the actual value of, let’s say, tag x. So in between you know, right next to tag x, we see the actual value changing and updating a few times a second. And so it makes it very easy to kinda monitor this thing while it’s running and see how everything’s working, and I know that’s that’s huge. And I know a lot of vendors also do this as well, but I love the integration here, how it’s so easy to see what the current values are for each of these variables. And, I’ll turn it over to you, Hendrick. I think I interrupted you. Go ahead. Henrik Pedersen (OTee): Yeah. No. I was just gonna comment on that. Jake said, like, this is the this is the POC editor, and the next the next big feature that we’re releasing very soon is essentially the service, manager, which is the, which is the feature that will allow our users to deploy any kind of service very efficiently, like another runtime or OPC UA server or an entity server or or or whatever other, software components that that, you want to deploy, like a Knox server or things like that. So and that’s that’s, we were really excited about that because, that will kind of allow for a step change in how you kind of orchestrate and manage your system and your, your system and your, your, you have a very good overview of what’s going on with versions of, of the different software components running in your, your infrastructure and your devices and things like that. So we’re really excited about that, that it’s coming out. And it might be that actually when when this, episode airs, who knows if it’s if it’s done or or not, but we’re very close to release the first version of that. So excited about that. Shawn Tierney (Host): Now I have a question for you guys, and maybe this is off topic a little bit. So let’s say I’m up here in the cloud. I’m working on a program, and I have some IO on my desk I wanna connect it to. Is that something I can do? Is there a connector I can download and install my PC to allow the cloud to talk to my IO? Or is that something where I have to get a a, you know, a local, you know, like we talked about those industrial Linux boxes and and test it here with that? Henrik Pedersen (OTee): Yeah. So I think you what you what you’re you’re after is, like, the IO configuration of, if you wanna deploy a driver, right, or, like, a modbus driver and how you figure out the system. Right? Shawn Tierney (Host): Yeah. Because this is in the cloud. It’s not on my desk. The IO is on my desk. So how would I connect the two of them? How would I is is that something that can be done? Henrik Pedersen (OTee): Yep. Yeah. Exactly. That’s that’s actually the you know, I I think, Jake, you might just wanna show why you deploy a driver. Right? Jacob Abel (Edgenaut): Sure. Sure. And I just wanna take a second to, clarify. You know, it’s something that kinda comes up often, and I I don’t I don’t think it gets it’s it’s cleared up enough is that so, you know, we have this cloud ID here. So, you know, you can open this from anywhere in the world. But the virtual PLC run times get installed on computers preferably very locally, you know, on the machine, on the factory floor, something like that. I I’ve got, an edge computer right here. Just as an example. I mean, this is something you would just pop in the control panel and you can install OT on this. So to answer your question better, Shawn, you know, to get to, you know, the remote IO that you need essentially, or actually in the, in the case of this, this has onboard IO. You know, you’re looking at connecting with MOBAs, PCP, Ethernet IP. I I know that a lot more protocols are coming. Profinet. So how you would do that is that you have that plus sign up here and add a driver config. We’re just gonna do, Modbus real quick. Henrik Pedersen (OTee): Mhmm. Jacob Abel (Edgenaut): And we wanna add a TCP client. So you can name the client, tell it how fast to pull, you know, any delays, put in the IP address. Just an example. Do the port number if you need and then add your requests. You know, you have support for, all the main function codes and mod bus right here, you know, read holding, read input, you know, write multiple coils, all that good stuff, you know, tell address how many registers you wanna do, timeouts, slave ID. And then, you know, once you’ve done that, so let’s say, you know, I’m gonna read, and holding registers here, the table on the right auto updates. You can do aliases for each one of these. You can just do register one Mhmm. As an example Shawn Tierney (Host): It’s showing just for the audio audience, it’s showing the absolute address for all these modbus, variables and then, has the symbols, and he’s putting in his own symbol name. It has a default symbol name of symbol dash something, and he’s putting his own in, like, register one, which makes it easier. Yeah. Jacob Abel (Edgenaut): Good point. Yeah. Good point. Thanks, Shawn. So, yeah, once once you put in your request and you can throw in some aliases, for the different registers, you know, you can go back to your program and here’s this, sample variable that I just added from earlier. You know, you can the registers are 16 bits. I’m gonna select, an int. And what you can do here now is select those modbus requests that you just set up. So it automatically maps these to those variables for you. So that that way you don’t have to do anything anything manual, like have a separate program to say, you know, this tag equals, you know, register 40,001. You know, it’s already mapped for you. So that’s that’s essentially how you would connect to remote IO is, just add a client in the driver configs and, fill in all your info and be off and running. Shawn Tierney (Host): That’s excellent. I really liked how you were able to easily map the register to the modbus value you’re reading in or writing to to your, variable so you can use that in your program. That was very easy to do. Jacob Abel (Edgenaut): Oh, yeah. Yeah. It’s that it’s like I said, that’s one of the things that I love about this interface is that everything is just very straightforward. You know, it’s it’s super easy to just stumble upon whatever it is you need and figure it out. Henrik Pedersen (OTee): And just just, to add to to kinda your your processors, like, once you have created that connection between the IO and and and the program, you basically just, compile it and download it to the to the runtime again, and and it executes locally the based on the yeah. Nice. Jacob Abel (Edgenaut): Oh, right. Good point. Yeah. Of of course, after we add something, we do have to redownload. So Shawn Tierney (Host): Very interesting. Well, that answers my question. Jacob Abel (Edgenaut): I think that’s that’s about it for the the demo. I mean, unless, Shawn, you have any more questions about the interface here. Shawn Tierney (Host): No. It looked pretty straightforward to me, Hendrik. I don’t know. Did you have anything else you wanted to discuss while we have the demo up? Henrik Pedersen (OTee): Nope. Not nothing related to this except for that, you know, this is probably something that’s quite new in the OT space is that this is a software service, meaning that there are continuous development going on and releases, and improvements to the software all the time. Like literally every week we deploy new improvements. And, and what, I typically say is that like, the, you know, if you if you if you sign up with OT, what you what you will experience is that the actual software keeps on becoming better over time and not is not going to become outdated. It’s going to be just better over time. And I think that’s part of what I really loved about the innovation space, innovation happening around IT is that that, that has become the new de facto standard in how you develop software and great software. And I think we in, in, in the OT space, we need to adopt that same methodology of developing software, something that continuously becomes better over time. Shawn Tierney (Host): Yeah. And I would just say, you know, if you’re if you’re on the OT side of things, you wanna be in six eleven thirty one dash three languages, because these are things that your staff, you know, what you know, your electricians and technicians and even engineers, you know, should know, should be getting up to speed. I don’t know. We’re at the automation school. We’re teaching, structured text. And so, easier. I look at this, and I’m like, this is a lot easier than trying to learn c plus or or JavaScript. So in any case, I think, you know, if it’s an OT side real IO control, real control system or data collection, you know, you know, very important, you know, mission critical data collection, then, you know, I’d rather have this than somebody trying to write some custom code for me and, you know, use some kind of computer language who doesn’t understand, you know, the OT side of things. So, I could definitely see the advantage of your system, Henrik. Henrik Pedersen (OTee): Yep. I I I also wanted to say to that, Stike, the I I do not believe the EIC standards in general will disappear. They exist for a very good reason. Right. Exists to standardise to to ensure safety and determinists, determinism in this. So I don’t think they will disappear. But there are obviously advances now with AI and things like that that can can help us create these things much faster and much more efficient and things like that. So, so but, but the EIC standards, I think, will be there for a very long time. Obviously, the 06/4099 standard is is really exciting, and and we believe that that can be, yeah, that that can clearly be there, but it’s still a new EIC standard. So, Shawn Tierney (Host): it’s not think what we’re gonna see is we’re gonna see a lot more libraries fleshed out. There’ll be a lot less writing from scratch. We’ve interviewed on the History of Automation podcast. We’ve interviewed some big integrators, and they’re at a point now, you know, twenty, thirty years on that they have libraries for everything. And I think that’s where we’ll see, you know, much like the DCS, I think, vendors went two years ago. But I still think that the there’s a reason for these languages. There’s a reason to be able to edit things while they run. There’s a reason for different languages for different applications and different, people maintaining them. So I agree with you on that. I don’t I don’t think we’re we’re gonna see the end of these, these standard languages that have done us very well since the, you know, nineteen seventies. Jacob Abel (Edgenaut): I just wanna add a bit on there about, Shawn, you mentioned, you know, doing less code. I I did show earlier in the bottom right hand corner here, we have our our little AI assistant, Martha. I don’t believe the feature, it has been released yet. You know, Henrik, correct me if I’m wrong, but I know one of the things that’s coming is, AI code generation, you know, similar to that of cloud or chat GPT. So it’s going to, you know, you can open this guy up here. You know, right right now, I think it’s just for, help topics, but you’ll be able to talk to Martha and she’s gonna generate code for you in your program there all built in. Henrik Pedersen (OTee): Yeah. Yeah. That’s that’s coming really fast now. So, it’s it’s not been implemented yet, but it’s, it’s right around the corner. Shawn Tierney (Host): Yeah. And it’s it’s not gonna be able to it’s you’re not gonna be able to hook a camera up to it and, like, take pictures of your machine and say, okay. Write the control code for this. But, you know, if you had a, you know, process that had 12 steps in it, the AI could definitely help you generate that code and and other code. And we’ll have to have Henrik and Jake back on to talk about that when it comes out, but, you know, it’s gonna be able to save you, reduce the tedious part of the the coding. You know, if you need an array of so many tags and so many dimensions or, you know, the stuff that, you know, it would just be the typing intensive, it’s gonna be able to help you with that, and then you can actually put the context in there. Just like, you can pull up a template in Word for a letter, and then you can fill in the blanks. You know? And and, of course, AI is helping make that easier too. But, in any case, Henrik, maybe you can come back on when that feature launches. Henrik Pedersen (OTee): Yeah. Absolutely. And I’m also excited about just a simple a use case of of translating something. Right? Translating your existing let’s say if it’s a proprietary code or something like that, like, getting it getting it standardized and translating it to the ESE six eleven thirty one standard, for instance, or, so so the obviously AI is, like, perfect for this space. It’s there is no doubt, And and it’s, like, that’s also why I’m so excited about, like, what’s going on at the moment. It’s like there’s so much innovation potential, in the on the OT side now that, they are with all these new technologies. Shawn Tierney (Host): Yeah. Absolutely. Absolutely. Well, gentlemen, was there anything else you wanted to cover? Henrik Pedersen (OTee): I think just just one final thing from from me is, like, we thought a lot about it, like, before this this episode, and we thought, like, let’s offer let’s offer the listeners something something of of true value. So so we thought, the, you know, after this after this episode launched, we want to want to offer anyone out there that’s listening a free, completely hands on trial of our technology, in their in their in their environment or on their Raspberry Pi or whatever. So just just reach out to us if you wanna do that. And, and I yeah. We’ll get you set up for for for testing this, and it’s not gonna cost you anything. Shawn Tierney (Host): Well, that’s great. And, guys, if you’re listening, if you do take advantage of that free trial, please let me know what you thought about it. But, Henrik, thank you so much for, that offer to our listening audience. Guys, don’t be bashful. Reach out to him. Reach out to Jake. Jake, thank you for doing the demo as well. Really appreciate it. My pleasure. Any final words, Henrik, before we close out? Henrik Pedersen (OTee): No. It’s been great. Great, being here, Shawn, and thanks for for helping us. Shawn Tierney (Host): Well, I hope you enjoyed that episode. I wanna thank Hendrik and Jacob for coming on the show, telling us all about OT virtual PLCs, and then giving us a demo. I thought it was really cool. Now if any of you guys take them up on their free trial, please let me know what you think. I’d love to hear from you. And, with that, I do wanna thank OT for sponsoring this episode so we could release it completely ad free. And I also wanna thank you for tuning back in this week. We have another podcast coming out next week. It’ll be early because I will be traveling and doing an event with a vendor. And so expect that instead of coming out on Wednesday to come out on Monday if all goes as planned. And then we will be skipping the Thanksgiving, week, and then we’ll be back in the in the, in December, and then we have shows lined up for the new year already as well. So thank you for being a listener, a viewer, and, please, wherever you’re consuming the show, whether it’s on YouTube or on the automation blog or at iTunes or Spotify or Google Podcasts or anywhere, please give us a thumbs up and a like or a five star review because that really helps us expand our audience and find new vendors to come on the show. And with that, I’m gonna end by wishing you good health and happiness. And until next time, my friends, peace. Until next time, Peace ✌️  If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

Topics covered in this episode: httptap 10 Smart Performance Hacks For Faster Python Code FastRTC Explore Python dependencies with pipdeptree and uv pip tree Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training The Complete pytest Course Patreon Supporters Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: httptap Rich-powered CLI that breaks each HTTP request into DNS, connect, TLS, wait, and transfer phases with waterfall timelines, compact summaries, or metrics-only output. Features Phase-by-phase timing – precise measurements built from httpcore trace hooks (with sane fallbacks when metal-level data is unavailable). All HTTP methods – GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS with request body support. Request body support – send JSON, XML, or any data inline or from file with automatic Content-Type detection. IPv4/IPv6 aware – the resolver and TLS inspector report both the address and its family. TLS insights – certificate CN, expiry countdown, cipher suite, and protocol version are captured automatically. Multiple output modes – rich waterfall view, compact single-line summaries, or -metrics-only for scripting. JSON export – persist full step data (including redirect chains) for later processing. Extensible – clean Protocol interfaces for DNS, TLS, timing, visualization, and export so you can plug in custom behavior. Example: Brian #2: 10 Smart Performance Hacks For Faster Python Code Dido Grigorov A few from the list Use math functions instead of operators Avoid exception handling in hot loops Use itertools for combinatorial operations - huge speedup Use bisect for sorted list operations - huge speedup Michael #3: FastRTC The Real-Time Communication Library for Python: Turn any python function into a real-time audio and video stream over WebRTC or WebSockets. Features

In this episode, we discuss MuleSoft and Camel similarities and take a brief tangent on the prevalence of XML as a data format, vibe-coding, SaaS fatigue, subscription overload, and Illuminated Cloud's support for GraphQL.

Doug McHoney (PwC's International Tax Services Global Leader) is joined by Pieter Dere, a partner in PwC Belgium's International Tax Services practice who leads Belgium's Pillar Two initiative and co‑hosts the Tax Bites Podcast. Doug and Pieter recorded in Prague at PwC's Global Transfer Pricing, Customs, and Indirect Tax Conference. They discuss Belgium's Pillar Two compliance landscape: 2024 applicability of QDMTT/IIR/UTPR, a late‑November 2025 filing cycle; the new e‑platform and XML‑only submissions; transitional safe harbors and JV scope; the ‘general representative' and joint and several liability; DAC 9 and the OECD MCAA; uncertainty around a G7 side‑by‑side and implications for US‑parented groups; estimated payments; Belgian litigation targeting UTPR; and practical steps to be ready now.