Podcasts about API

More .well-known scans Attackers are using API documentation automatically published in the .well-known directory for reconnaissance. https://isc.sans.edu/diary/More%20.well-known%20Scans/32340 RedHat Patches Openshift AI Services A flaw was found in Red Hat Openshift AI Service. A low-privileged attacker with access to an authenticated account, for example, as a data scientist using a standard Jupyter notebook, can escalate their privileges to a full cluster administrator. https://access.redhat.com/security/cve/cve-2025-10725#cve-affected-packages TOTOLINK X6000R Vulnerabilities Paloalto released details regarding three recently patched vulnerabilities in TotalLink-X6000R routers. https://unit42.paloaltonetworks.com/totolink-x6000r-vulnerabilities/ DrayOS Vulnerability Patched Draytek fixed a single memory corruption vulnerability in its Vigor series router. An unauthenticated user may use it to execute arbitrary code. https://www.draytek.com/about/security-advisory/use-of-uninitialized-variable-vulnerabilities

I often wonder if we in the insurance industry have any idea how lucky we are that there are so many smart people out there looking to help make the way we do business easier, more efficient, more productive and ultimately, more profitable. Today's guest, Matt Hicks, is one of these people. Matt is the co-founder of Recorder, a next-generation broker management system that connects producers directly with underwriters and gives those underwriters instant quote and bind capabilities. Matt is a serial entrepreneur who has already been involved in two successful fintech ventures and now has some very well-known insurance investors on board this one. The product Matt and his team have produced is laser-focused on what adds the most value in the commercial insurance value chain. It's all about reducing admin and freeing producers, whether they are brokers, coverholders or frontline underwriters, up to do what they do best. The initial productivity gains claimed are eye-opening. The term serial entrepreneur may give you a misleading impression, so I'd say the best way of describing Matt would be that he would always be the most investable guest on an episode of Dragon's Den or Shark Tank. By the time he had finished with them, he would have all the investors fighting to be involved. The key I think is that special humility and empathy you get with really successful entrepreneurs. In my time as an insurance journalist I have lost count of the number of entrepreneurs I have met with who have undoubtedly superb technology, but who ultimately failed because they had zero empathy or understanding of how insurance professionals actually work and therefore what help they really need. Matt and his team are in insurance for the long run and know that the sort of API-lead revolution they are proposing will take time. But at the same time they know that history is on their side if they are patient enough. So I can highly recommend a listen. Matt is incredibly easy to talk to and his experienced and down-to-earth approach means he knows exactly how to go about making Recorder the sort of tool that over time the best producers are going to be clamouring for.   LINKS:  https://www.recorder.tech/ https://www.recorder.tech/contact  

In this episode, Mark Longo dives into the day's top options activities as of Thursday, October 2nd. The report covers notable trades and market movements for key products including VIX, SPY, small caps, QQQ, AMD, Intel, Nvidia, and Tesla. Despite low volumes in some areas, SPY stands out with a significant contract volume. The episode also highlights the performance of options on individual stocks like Robinhood, Palantir, Amazon, Apple, and more.  00:00 Introduction and Welcome 01:02 Hot Options Report Overview 02:21 VIX Analysis 03:02 SPY and S&P 500 Insights 03:58 Small Caps and QQQ Breakdown 05:15 Single Name Stocks Analysis 11:57 Conclusion and Upcoming Events ------------------------------------------------------------------------ All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.  

Thank you to the folks at Sustain (https://sustainoss.org/) for providing the hosting account for CHAOSSCast! CHAOSScast – Episode 120 In this episode of CHAOSScast, Harmony Elendu hosts a discussion with Dawn Foster and Bob Killen to discuss their extensive experience in open source and detail the motivations behind the creation of the CHAOSS Practitioner Guides. These guides aim to help practitioners navigate the overwhelming amount of data related to open source projects and understand how to improve project health and sustainability. The discussion covers strategies for communicating the business value of open source efforts to leadership, framing contributions in a way that resonates with organizational priorities, and prioritizing investments in critical projects. Press download now! [00:00:31] Dawn and Bob introduce themselves and their backgrounds. [00:02:24] Dawn explains why CHAOSS created Practitioner Guides: to help navigate the “tsunami of data” from open source metrics. The new guide is different and is focused on demonstrating organizational value. [00:04:36] Harmony asks about the inspiration for the guide. Dawn credits Bob and how the guide was built largely from his talks at KubeCon and the Linux Foundation Member Summit. [00:05:22] Bob talks about macroeconomic pressures where open source is often first cut. The guide helps orgs tell compelling stories to leadership about open source ROI. [00:07:14] Bob shares a case study: maintainers reframed contributions in leadership's language- revenue impact, bug fix turnaround, and resource efficiency and how this secured leadership support. Dawn adds that every organization values different things and provides an example. [00:11:36] Bob introduces the formula: Priority = Criticality x Health. [00:13:36] Dawn emphasizes formula helps orgs prioritize strategically critical but under-resourced projects (example: Kubernetes cluster API at VMware). Bob notes criticality differs by company and even department. [00:16:51] Harmony ask how to report open source value to leadership. Bob explains the importance of framing in leadership's language, not just raw contribution counts. Dawn warns against poor framing and explains about being careful about how you talk to leadership about your open source efforts. Value Adds (Picks) of the week: [00:20:47] Dawn's pick is discovery how easy it was to build a static site with GitHub Pages and Jekyll. [00:21:38] Bob's pick is dosu.dev. [00:22:18] Harmony's pick is exploring AI models for fraud detection and system tracking. Panelists: Harmony Elendu Guests: Dawn Foster Bob Killen Links: CHAOSS (https://chaoss.community/) CHAOSS Project X (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) CHAOSS YouTube (https://www.youtube.com/@CHAOSStube/videos) podcast@chaoss.community (mailto:podcast@chaoss.community) Harmony Elendu X (https://x.com/ogaharmony) Dawn Foster X (https://twitter.com/geekygirldawn?lang=en) Bob Killen Website (https://mrbobbytabl.es/) CHAOSS Practitioner Guides (https://chaoss.community/about-chaoss-practitioner-guides/) CHAOSS Practitioner Guides (YouTube) (https://www.youtube.com/playlist?list=PL60k37cxI-HSHV4-rEsWMzExw2y2Oq79Z) CHAOSS Data Science Working Group: New Guides, Research, and More (Blog Post by Dawn Foster (https://chaoss.community/chaoss-data-science-working-group-new-guides-research-and-more/) CHAOSS Practitioner Guide: Getting Started with Sunsetting an Open Source Project (https://chaoss.community/practitioner-guide-sunset/) CHAOSS Practitioner Guide: Getting Started with Building Diverse Leadership (https://chaoss.community/practitioner-guide-diverse-leadership/) GitHub Pages documentation (https://docs.github.com/en/pages) Jekyll (https://jekyllrb.com/) Dosu (https://dosu.dev/) Special Guest: Bob Killen.

Recent studies have shown how AI Agents have expanded the attack surface for federal agencies.   Today, we sit down with three leaders who demonstrate why fundamentals, such as visibility, inventory, runtime, and least-permissive access control, will be more critical than ever.   Rob Roser from Idaho National Labs looks at the proliferation of API in the past decade.  Although they facilitate communication, they can also give a path to attackers. He notes that today's attackers are interested in much more than money, the seek intellectual property that can compromise American security.   Phishing and security training are good starting points, but developers must learn what tools to use to be able to use AI an appropriate manner.   Where to start?  Steven Ringo from Akamai give four key points for handling the drastic increase in data generated by AI   ·       One: Discovery -  build an API inventory  ·       Two: Posture – implement policies that can control the APIs ·       Three: Run Time protection - design how to alert and take action to block ·       Four:  Active testing prevention that is continuous   The webinar underscored the urgency of integrating API security into comprehensive cybersecurity strategies and recommends programs to test and validate APIs before production deployment.

On this episode of the Scouting For Growth podcast, Sabine VdL talks to Amit Santhirasenan, co-founder and CEO of hyperexponential, an actuary and software engineer who has built the AI native pricing and underwriting platform used by leading specialty carriers. In this episode we cover how to turn messy submissions into structured signals your pricing model can trust – without hiring an army, multi agent architectures, the agentic AI mesh, and the human in the loop controls executives need for auditability and speed, and where agentic underwriting is ready today (and where it isn't), plus the metrics executives should track—cycle time, hit ratio, and loss ratio uplift. KEY TAKEAWAYS Email submissions were a luxury at the start of my career! What's been so exciting for me, as a self-professed nerd, is the pace at which the capabilities of core models have got so good that even 6 months ago was a whole product's capability and feature set is now within the gift of Gemini or GPT5. If you're an underwriter filling out a spreadsheet/renew model, in 2025 you need to be working with hx underwriting , actuary or agent inside a renew model to have your paired partner helping you get to the best result. Why can't you have deep risk research on every single risk? Why can't you say: Tell me the most important characteristics in the world that you can tell me about the top 3 exposures? No human can do this work, the cost/benefit trade off there isn't economic, but you can run an OpenAI deep risk API call to do that on every single risk you underwrite today. We do it for you, it's what we do. All of a sudden it's dramatically easier to bring that level of differentiation and specialism in the way that great underwriting has always been done to every single risk you want to touch. BEST MOMENTS ‘You won't see that many places with a $7 trillion contribution to GDP, with such a small number of companies and people responsible for this.' ‘We demonstrated the first API machine vision algorithm in the market in 2017, now kids coming out of university are doing that as toy projects before they get to our clients.' ‘You can have an army of digital agents helping you now, all for $20 per month!' ‘Generative AI models have unlocked the ability to pull data so quickly out of the information required for underwrite that you can put a very quick red/amber/green status on risks, several orders of magnitude greater than ever before.' ABOUT THE GUESTS Amit Santhirasenan is the Co-founder and CEO of Hyperexponential (hx), the AI native pricing and underwriting platform for P&C insurers. Under his leadership, hx Renew has become known for delivering executive level outcomes: ~50% faster submission to bind, 10× faster model build and deployment, and a platform that supports $45bn+ in GWP for 20+ enterprise customers worldwide. A qualified actuary and computer scientist, Amrit previously spent over a decade in the London Market. He served as Head of Pricing & Analytics at Tokio Marine Kiln, building the managing agent's first technical pricing team to support ~£1.5bn GWP, and earlier held actuarial roles at Catlin (including standing up the Canadian actuarial function). ABOUT THE HOST Sabine is a corporate strategist turned entrepreneur. She is the CEO and Managing Partner of Alchemy Crew a venture lab that accelerates the curation, validation, & commercialization of new tech business models. Sabine is renowned within the insurance sector for building some of the most renowned tech startup accelerators around the world working with over 30 corporate insurers, accelerated over 100 startup ventures. Sabine is the co-editor of the bestseller The INSURTECH Book, a top 50 Women in Tech, a FinTech and InsurTech Influencer, an investor & multi-award winner. Twitter LinkedIn Instagram Facebook TikTok Email Website This Podcast has been brought to you by Disruptive Media. https://disruptivemedia.co.uk/

#318: In this episode, we explore how AI is fundamentally reshaping the world of API development and testing with Tom Akehurst, CTO & Co-founder at WireMock. As AI agents become more prevalent in software development, the tools and practices around API design, testing, and maintenance are evolving rapidly. Tom shares insights on how WireMock is adapting to this new landscape and what it means for developers and organizations building distributed systems.   Tom's contact information  X: https://x.com/TomAkehurst LinkedIn: https://www.linkedin.com/in/tomakehurst/   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

In this episode of the Hot Options Report, Mark Longo reviews significant movements in the options market on Wednesday, October 1st, despite the U.S. government shutdown. Highlights include unchanged VIX activity, increased trading volumes in SPY, SPX, small caps, and major single names like Amazon, Meta, Nvidia, and Tesla. The show also promotes Public.com as a cost-effective platform for trading options.    00:00 Introduction and Welcome 02:35 VIX Market Analysis 03:38 SPY and SPX Insights 05:09 Small Caps and QQQ Breakdown 06:32 Single Name Options Activity 12:22 Conclusion and Next Steps   ----------------------------------------------------------------------- All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

Healthcare providers waste $950 billion annually on manual workarounds caused by fragmented EHR systems and integration costs that don't scale. Shadowbox has developed a patented browser technology that functions as an API, enabling instant EHR data access without traditional integration expenses. In this episode of Category Visionaries, we sat down with Gregory Stein, CEO of Shadowbox, to dissect how the company evolved from serving desperate lab diagnostics customers to building strategic partnerships with established healthcare IT players like HC1 to reach health systems.   Topics Discussed: How the 21st Century Cures Act information blocking provisions remain largely unenforced, allowing EHR vendors to maintain data monopolies through integration fees Shadowbox's technical architecture: a white-labeled browser that accesses the document object model and API endpoints to extract HIPAA-compliant data without custom integrations Market entry strategy—targeting financially distressed lab diagnostics providers who couldn't afford traditional integration costs The HC1 partnership model: splitting the market by use case rather than geography, with HL7/API integrations going to HC1 and rapid, low-cost deployments going to Shadowbox Sequential interoperability capabilities that enable multiple vendor touchpoints (prior authorization, eligibility verification, billing) from a single data extraction   GTM Lessons For B2B Founders: Target customers facing existential financial pressure, not optimal market conditions: Shadowbox entered through lab diagnostics—a commoditized, low-margin segment hemorrhaging money where providers faced $5K-$50K integration costs per connection taking 3-6 months. Greg acknowledged labs are "the redheaded stepchild of healthcare" but their desperation made them willing to pilot unproven technology. The lesson: segments with severe unit economics problems become early adopter pools because status quo costs exceed perceived risk of new vendors. Build a partnerships function before you have market leverage: Shadowbox hired a partnerships-focused employee early to cultivate relationships with RCM vendors and lab information system providers already selling to target customers. Rather than waiting for customer traction to attract partners, they used partnerships to generate initial traction. Greg emphasized healthcare adoption requires credible references—partnerships provide instant credibility entrepreneurs can't buy. Map your ecosystem's existing vendor relationships and pursue co-sell arrangements before achieving meaningful ARR. Use early customer feedback to migrate upmarket, not pivot laterally: Shadowbox started with labs, expanded to imaging centers, but their true ICP emerged as health systems with 500-1,000 community providers on disparate EHRs where traditional integration economics break down. Greg noted: "health systems that have major outreach programs where it doesn't pencil out to have them on their EPIC system." The migration path moved from small, desperate customers toward larger organizations facing the same core problem at scale. Don't mistake initial ICP for ultimate ICP—use early segments as beachheads to validate technology before pursuing customers with better economics. Partner with horizontal competitors when you solve orthogonal use cases: The HC1 deal splits the interoperability market—structured, predictable integrations go to HC1's traditional approach while rapid deployments to fragmented provider networks go to Shadowbox. This isn't channel partnership but market segmentation by use case economics. Greg explained they bring "something complementary to and in some ways competitive" but combined create offerings competitors can't match. Evaluate whether your "competitors" actually serve different jobs-to-be-done within the same category, then structure partnerships around use case delineation rather than territorial splits. Leverage policy expertise as product moat in regulated markets: Greg's Capitol Hill background enabled Shadowbox to support the Coalition for Innovative Lab Testing's successful lawsuit blocking FDA regulation of lab-developed tests—directly protecting their customers' business models. This wasn't marketing but strategic positioning that demonstrates commitment beyond vendor relationships. In heavily regulated industries, founders with policy expertise or advisors who can shape regulatory outcomes create defensibility that pure technology cannot. Consider how industry advocacy amplifies customer loyalty while potentially expanding TAM through favorable regulatory changes.   //   Sponsors: Front Lines — We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. www.FrontLines.io The Global Talent Co. — We help tech startups find, vet, hire, pay, and retain amazing marketing talent that costs 50-70% less than the US & Europe. www.GlobalTalent.co   //   Don't Miss: New Podcast Series — How I Hire Senior GTM leaders share the tactical hiring frameworks they use to build winning revenue teams. Hosted by Andy Mowat, who scaled 4 unicorns from $10M to $100M+ ARR and launched Whispered to help executives find their next role.   Subscribe here: https://open.spotify.com/show/53yCHlPfLSMFimtv0riPyM

Welcome back to Fintech Takes. I'm Alex Johnson, joined (as always) by my partner-in-recapping, Jason Mikula.  First up: the uneasy détente in open banking is over. Jason and I haven't had a chance to debrief on Plaid's deal with JPMorgan Chase to pay for API access (so we do). Payments use cases remain the most expensive, Plaid is eating the fees (at least for now), and Chase looks like it's succeeded in hobbling Pay by Bank. We unpack why Plaid did the deal, what it means for other aggregators.  Next up, color us nostalgic; back to BaaS Island we go! The FBI is probing Evolve. The scope reportedly extends to board members (including a16z), and new details suggest international money movement in Southeast Asia (tied to a $15M pig-butchering scheme). As the saying goes, bankers almost never go to jail; will this time be any different? Then, we turn to AI. FICO has announced a new product called a foundation model for financial services. The idea is to build smaller, domain-specific models that are cheaper, faster, and more reliable than generic LLMs, while adding predictive lift on top of existing analytics. The open questions: is this hype dressed up for Wall Street, or a clever way to squeeze extra predictive power out of structured financial datasets? And most of all: who is this really for? Plus, in our Can't Let It Go corner, Jason bristles about being labeled as “partisan” (in response to his response about the “Debanking” Executive Order) while I puzzle over Tether reportedly raising at a $500B valuation (the same as OpenAI, except Tether's core product is…not getting audited and telling everyone to “just trust us.”) Sign up for Alex's Fintech Takes newsletter for the latest insightful analysis on fintech trends, along with a heaping pile of pop culture references and copious footnotes. Every Monday and Thursday: https://workweek.com/brand/fintech-takes/  And for more exclusive insider content, don't forget to check out my YouTube page. Follow Jason: Newsletter: https://fintechbusinessweekly.substack.com/ LinkedIn: https://www.linkedin.com/in/jasonmikula/   Follow Alex:  YouTube: https://www.youtube.com/channel/UCJgfH47QEwbQmkQlz1V9rQA/videos LinkedIn: https://www.linkedin.com/in/alexhjohnsonTwitter: https://www.twitter.com/AlexH_Johnson

How serious is the cargo theft crisis, and what real solutions are available today? How do we solve the connectivity challenges in freight tech, and why are APIs critical to the future of logistics?  Listen to our guests from the 2025 IANA Conference, Curtis Spencer of Bloodhound Tracking Device and Keith Peterson of NMFTA, as we dive into cargo security, advanced tracking systems, the market transformation that's happening right now in freight, the mission of the Digital Standards Development Council (DSDC), and their push to create common API language across carriers, shippers, 3PLs, and technology providers.   Curtis' Website: https://btdtracker.com/  Keith's Website: https://nmfta.org/  / https://dsdc.nmfta.org/home  

In this episode of the Hot Options Report, Mark Longo provides an in-depth analysis of the options market activities for Tuesday, September 30th. The report covers key market indicators such as VIX, SPY, SPX, and individual equities including Apple, Intel, Amazon, and Nvidia. Mark also highlights significant options trades, volume insights, and closing prices. Additionally, listeners are informed about Public, a cost-effective trading platform that offers rebates on options trades.    00:26 Welcome to the Hot Options Report 01:05 Today's Market Overview 02:24 VIX Analysis 03:22 SPY and SPX Insights 04:30 Small Caps and QQQ Breakdown 06:04 Single Name Equity Options Highlights 14:03 Conclusion and Final Thoughts ------------------------------------------------------------------------ All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereMatt McLarty - CTO at Boomi & Co-Author of "Unbundling the Enterprise"Erik Wilde - Principal Consultant at INNOQRESOURCESMatthttps://bsky.app/profile/mattmclartybc.bsky.socialhttps://x.com/MattMcLartyBChttps://www.linkedin.com/in/mattmclartybcErikhttps://www.linkedin.com/in/erikwildehttps://github.com/dretLinkshttps://www.hbs.edu/faculty/Pages/profile.aspx?facId=6417https://cloud.google.com/blog/products/application-development/richard-seroter-on-shifting-down-vs-shifting-lefthttps://platformengineering.org/blogDESCRIPTIONMatt McLarty and Erik Wilde explore the nuanced world of platform engineering, challenging conventional approaches and highlighting the critical importance of aligning technological capabilities with business outcomes. They discuss the evolution from DevOps, the role of APIs, and the need to create flexible, reusable technological building blocks that drive true organizational innovation.RECOMMENDED BOOKSStephen Fishman & Matt McLarty • Unbundling the EnterpriseCarliss Y. Baldwin • Design Rules, Vol. 2Matthew Skelton & Manuel Pais • Team TopologiesForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookGene Kim, Kevin Behr & George Spafford • The Phoenix ProjectCrossing BordersCrossing Borders is a podcast by Neema, a cross border payments platform that...Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Client SDKs: Die schöneren APIs?APIs sind das Rückgrat moderner Softwareentwicklung, doch wer kennt nicht das Dilemma? Die API ändert sich, Fehlermeldungen stapeln sich im Postfach, und plötzlich hängt dein Workflow am seidenen HTTP-Thread. Genau dort kommen Client SDKs ins Spiel. Sie machen aus kryptischen API-Endpunkten handliche, sprachnahe Werkzeuge, die dir nicht nur Nerven, sondern auch Zeit sparen.In dieser Episode schauen wir hinter die Kulissen der SDK-Entwicklung. Wir sprechen aus Maintainer-Perspektive über Supportdruck, Burnout und die (oft unterschätzte) Verantwortung in Open Source. Gleichzeitig tauchen wir tief in die Praxis ein: Was ist ein Client SDK genau? Wann lohnt sich Handarbeit, wann die Code-Generation? Warum ist idiomatisches SDK-Design mehr als nur Style – und weshalb boosten einige SDKs wie das von Stripe oder AWS sogar den wirtschaftlichen Erfolg ganzer Unternehmen?Gemeinsam werfen wir einen Blick auf Architektur, Best Practices, Edge Cases, Testing, Dokumentation und Wartung. Und natürlich diskutieren wir, wann ein SDK wirklich sinnvoll ist – und in welchen Fällen du lieber einen simplen HTTP-Aufruf selbst schreibst.Bonus: Wieso Atlassian Merch statt Sponsoring schickt.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

In een markt gedomineerd door complexe CRM-systemen, bouwden broers Rob en Bart Sauer een revolutionair eenvoudige oplossing: Cirqll CRM. In deze aflevering van de StoryBrand Podcast delen zij hun visie op eenvoud, hun groei van 100 naar 250+ klanten in slechts 10 maanden, en hoe ze concurreren met giganten als Salesforce.In deze aflevering zijn Rob en Bart Sauer te gast, oprichters van Cirqll CRM. Deze broers hebben een missie: het leven van ondernemend Nederland makkelijker maken met het meest eenvoudige CRM-systeem. Rob, met zijn achtergrond in sales, en Bart, de strategische denker, vormen samen een krachtig team dat in korte tijd indrukwekkende resultaten heeft geboekt. Ze delen hoe hun complementaire kwaliteiten bijdragen aan hun succes en waarom complexiteit hun grootste vijand is.Belangrijkste gespreksonderwerpenDe oorsprong van Cirqll: hoe corona en een schets op papier leidden tot een nieuw bedrijfWaarom 90% van de CRM-systemen faalt door onnodige complexiteitDe filosofie van eenvoud die doorsijpelt in alles wat ze doen - van productontwikkeling tot bedrijfscultuurVan Excel sheets naar een eenvoudig CRM-systeem: hoe Cirqll binnen 2,5 jaar naar 250+ klanten groeideHet belang van open API's en mobiele applicaties voor moderne CRM-oplossingenDe balans vinden tussen nieuwe technologie (zoals AI) en het behouden van eenvoudDe complementaire kwaliteiten van de broers en hoe hun verschillen bijdragen aan het succesPraktische tips voor ondernemers die worstelen met klantbeheer en complexe toolsDe moed om 'nee' te zeggen tegen klanten die niet bij je passenRelevante links en bronnenWebsite van Cirqll CRMRob Sauer op LinkedInBart Sauer op LinkedInBoek: That Will Never Work van Marc Randolph - Het verhaal achter de oprichting van NetflixBoek: No Rules Rules van Reed Hastings - Over de unieke bedrijfscultuur bij NetflixNetflix-documentaire over Spotify - Over hoe de muziekindustrie veranderdeLaat jij omzet liggen door een onduidelijke marketingboodschap?Doe de gratis Heldere Marketingboodschap Zelfassessment en ontdek waar je kansen laat liggen. Beantwoord 20 korte vragen (duurt maar 2 minuten), ontvang een persoonlijk adviesrapport met praktische tips en krijg een goed beeld van de kansen voor jouw bedrijf. Ga naar form.buzzlytics.nl/storybrand-marketingboodschap en zorg dat jouw team overal dezelfde heldere boodschap communiceert.

　HENNGE株式会社は9月24日、「HENNGE One」が株式会社オロのSaaS管理ツール「dxeco」とのAPI連携に対応したと発表した。

In Episode 124 of Entangled Things, Patrick is joined by Vijoy Pandey, Senior Vice President of Outshift by Cisco. Together, they explore the future of quantum networking, the power of entanglement, and how these breakthroughs will shape the next generation of technology. Vijoy also shares an exciting announcement: the launch of Cisco's Quantum Software Stack.Want to dive deeper? Don't miss the Cisco Quantum Summit, happening September 30 and October 1: https://research.cisco.com/quantum-summit.Vijoy Pandey is GM and Senior Vice President of Outshift by Cisco, leading the company's internal incubation engine that delivers what's next and new for Cisco. Outshift focuses on emerging technologies that target adjacent markets and personas, with current initiatives spanning AI-enabled infrastructure, quantum networking, and next-generation infrastructure solutions.Outshift operates as a series of startup-like teams inside Cisco, rapidly validating which emerging technologies can become meaningful businesses for the company's future. Under Vijoy's leadership, these teams work across three key layers: agentic AI, next-gen infrastructure, quantum networking, and more. This model allows Outshift to move quickly and test multiple opportunities simultaneously while leveraging Cisco's enterprise strengths and established processes.Vijoy oversees a broader strategic scope that includes several critical Cisco-wide initiatives. He also leads Cisco Research, driving foundational research across quantum networking, security, observability, and emerging technologies. He directs Cisco's Open Source initiatives and the Developer Network (DevNet), which leads API consistency and programmability across Cisco's portfolio while pioneering AI-native infrastructure tools. Additionally, he co-chairs Cisco's Responsible AI committee.Vijoy holds a Ph.D. in Computer Science from the University of California, Davis, and is an inventor on over 80 patents in cloud computing, AI/ML, and distributed systems. Through his leadership of Outshift, Vijoy continues to guide Cisco's exploration of emerging technologies, ensuring the company can move quickly to capture opportunities in new markets before they fully mature.

Is Apple serious about AI now with a new internal model?

English is now an API. Our apps read untrusted text; they follow instructions hidden in plain sight, and sometimes they turn that text into action. If you connect a model to tools or let it read documents from the wild, you have created a brand new attack surface. In this episode, we will make that concrete. We will talk about the attacks teams are seeing in 2025, the defenses that actually work, and how to test those defenses the same way we test code. Our guides are Tori Westerhoff and Roman Lutz from Microsoft. They help lead AI red teaming and build PyRIT, a Python framework the Microsoft AI Red Team uses to pressure test real products. By the end of this hour you will know where the biggest risks live, what you can ship this quarter to reduce them, and how PyRIT can turn security from a one time audit into an everyday engineering practice. Episode sponsors Sentry AI Monitoring, Code TALKPYTHON Agntcy Talk Python Courses Links from the show Tori Westerhoff: linkedin.com Roman Lutz: linkedin.com PyRIT: aka.ms/pyrit Microsoft AI Red Team page: learn.microsoft.com 2025 Top 10 Risk & Mitigations for LLMs and Gen AI Apps: genai.owasp.org AI Red Teaming Agent: learn.microsoft.com 3 takeaways from red teaming 100 generative AI products: microsoft.com MIT report: 95% of generative AI pilots at companies are failing: fortune.com A couple of "Little Bobby AI" cartoons Give me candy: talkpython.fm Tell me a joke: talkpython.fm Watch this episode on YouTube: youtube.com Episode #521 deep-dive: talkpython.fm/521 Episode transcripts: talkpython.fm Developer Rap Theme Song: Served in a Flask: talkpython.fm/flasksong --- Stay in touch with us --- Subscribe to Talk Python on YouTube: youtube.com Talk Python on Bluesky: @talkpython.fm at bsky.app Talk Python on Mastodon: talkpython Michael on Bluesky: @mkennedy.codes at bsky.app Michael on Mastodon: mkennedy

Topics covered in this episode: * PostgreSQL 18 Released* * Testing is better than DSA (Data Structures and Algorithms)* * Pyrefly in Cursor/PyCharm/VSCode/etc* * Playwright & pytest techniques that bring me joy* 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: PostgreSQL 18 Released PostgreSQL 18 is out (Sep 25, 2025) with a focus on faster text handling, async I/O, and easier upgrades. New async I/O subsystem speeds sequential scans, bitmap heap scans, and vacuum by issuing concurrent reads instead of blocking on each request. Major-version upgrades are smoother: pg_upgrade retains planner stats, adds parallel checks via -jobs, and supports faster cutovers with -swap. Smarter query performance lands with skip scans on multicolumn B-tree indexes, better OR optimization, incremental-sort merge joins, and parallel GIN index builds. Dev quality-of-life: virtual generated columns enabled by default, a uuidv7() generator for time-ordered IDs, and RETURNING can expose both OLD and NEW. Security gets an upgrade with native OAuth 2.0 authentication; MD5 password auth is deprecated and TLS controls expand. Text operations get a boost via the new PG_UNICODE_FAST collation, faster upper/lower, a casefold() helper, and clearer collation behavior for LIKE/FTS. Brian #2: Testing is better than DSA (Data Structures and Algorithms) Ned Batchelder If you need to grind through DSA problems to get your first job, then of course, do that, but if you want to prepare yourself for a career, and also stand out in job interviews, learn how to write tests. Testing is a skill you'll use constantly, will make you stand out in job interviews, and isn't taught well in school (usually). Testing code well is not obvious. It's a puzzle and a problem to solve. It gives you confidence and helps you write better code. Applies everywhere, at all levels. Notes from Brian Most devs suck at testing, so being good at it helps you stand out very quickly. Thinking about a system and how to test it often very quickly shines a spotlight on problem areas, parts with not enough specification, and fuzzy requirements. This is a good thing, and bringing up these topics helps you to become a super valuable team member. High level tests need to be understood by key engineers on a project. Even if tons of the code is AI generated. Even if many of the tests are, the people understanding the requirements and the high level tests are quite valuable. Michael #3: Pyrefly in Cursor/PyCharm/VSCode/etc Install the VSCode/Cursor extension or PyCharm plugin, see https://pyrefly.org/en/docs/IDE/ Brian spoke about Pyrefly in #433: Dev in the Arena I've subsequently had the team on Talk Python: #523: Pyrefly: Fast, IDE-friendly typing for Python (podcast version coming in a few weeks, see video for now.) My experience has been Pyrefly changes the feel of the editor, give it a try. But disable the regular language server extension. Brian #4: Playwright & pytest techniques that bring me joy Tim Shilling “I've been working with playwright more often to do end to end tests. As a project grows to do more with HTMX and Alpine in the markup, there's less unit and integration test coverage and a greater need for end to end tests.” Tim covers some cool E2E techniques Open new pages / tabs to be tested Using a pytest marker to identify playwright tests Using a pytest marker in place of fixtures Using page.pause() and Playwright's debugging tool Using assert_axe_violations to prevent accessibility regressions Using page.expect_response() to confirm a background request occurred From Brian Again, with more and more lower level code being generated, and many unit tests being generated (shakes head in sadness), there's an increased need for high level tests. Don't forget API tests, obviously, but if there's a web interface, it's gotta be tested. Especially if the primary user experience is the web interface, building your Playwright testing chops helps you stand out and let's you test a whole lot of your system with not very many tests. Extras Brian: Big O - By Sam Who Yes, take Ned's advice and don't focus so much on DSA, focus also on learning to test. However, one topic you should be comfortable with in algortithm-land is Big O, at least enough to have a gut feel for it. And this article is really good enough for most people. Great graphics, demos, visuals. As usual, great content from Sam Who, and a must read for all serious devs. Python 3.14.0rc3 has been available since Sept 18. Python 3.14.0 final scheduled for Oct 7 Django 6.0 alpha 1 released Django 6.0 final scheduled for Dec 3 Python Test Static hosting update Some interesting discussions around setting up my own server, but this seems like it might be yak shaving procrastination research when I really should be writing or coding. So I'm holding off until I get some writing projects and a couple SaaS projects further along. Joke: Always be backing up

In this episode of The Cybersecurity Defenders Podcast, we discuss some intel being shared in the LimaCharlie community.A recent investigation by the U.S. Secret Service claims to have uncovered a massive swatting infrastructure centered around New York City.Check Point researchers are tracking an Iran-linked cyber-espionage group known as Nimbus Manticore, which appears to be expanding its operations into Western Europe.A new wave of malicious advertising is targeting macOS users by impersonating widely used software and services through search engine ads.A new tool called SpamGPT is drawing attention in the cybersecurity community for effectively lowering the barrier to entry for large-scale spam and phishing campaigns.In light of increasing attacks on open source ecosystems, GitHub has disclosed recent security incidents affecting the npm registry, including the Shai-Hulud worm.Support our show by sharing your favorite episodes with a friend, subscribe, give us a rating or leave a comment on your podcast platform.This podcast is brought to you by LimaCharlie, maker of the SecOps Cloud Platform, infrastructure for SecOps where everything is built API first. Scale with confidence as your business grows. Start today for free at limacharlie.io.

Ryan Doran is a Partner in Lead Creative and Head of UI/UX for Turkois, with over 17 years of experience in monetization strategy, payments, and scaling technology businesses.  Danny Smith is a Solution Architect at Stripe, working on AI-driven commerce innovations and partnering with AWS. In this episode, Ryan and Danny explore the critical intersection of pricing strategy and payment infrastructure, discussing how AI is transforming both the mechanics of pricing implementation and the challenge of pricing AI products themselves.   Why you have to check out today's podcast: Understand the difference between billing systems and payment systems and how they work together. Learn why flexible technical infrastructure is essential for modern pricing strategies. Discover how AI is enabling hyper-personalized shopping experiences with built-in guardrails.   "Your pricing strategy is only as good as the background tech that you have to operationalize it. If you have a legacy monolithic stack and you can come up with these great strategies, but it takes you six months to implement that strategy, then you've probably been left behind already." – Danny Smith   Topics Covered: 02:15 - How Ryan got into pricing through product development and payment flows. 04:30 - Danny's journey from cloud architecture to payments infrastructure. 06:45 - The difference between billing systems and payment systems. 10:20 - Why new billing companies continue to emerge despite established players. 14:15 - How AI is accelerating data utilization in pricing decisions. 17:30 - The dual challenge: using AI for pricing vs. pricing AI products. 19:45 - Hyper-personalized shopping with AI agents and built-in guardrails. 23:10 - The ethical concerns of "sleazy price segmentation" and AI pricing. 28:40 - Agent-to-agent negotiations and policy engines. 31:20 - How AI products are changing pricing models: tokens, credits, and hybrid approaches. 35:15 - Creating "action units" to translate technical complexity into business value.   Key Takeaways: "Data is basically the new margin. What you can do with it is only gaining in value." - Ryan Doran "We've implemented API level technology that will create a budget... and it will create a virtual debit card on the backend for that exact amount, tied to today as an expiration date, tied to that particular transaction." - Danny Smith   People / Resources Mentioned: Turkois: https://turkois.io/ Vanilla POS: https://vanillapos.io/ Stripe: https://stripe.com Perplexity: https://www.perplexity.ai/ OpenAI: https://openai.com/ Chargebee, Chargeify, Zora: Alternative billing platforms MCP Server: Technology enabling AI agents to interact with Stripe for dynamic pricing   Connect with Ryan Doran: Website: https://turkois.io/ Email: ryan@turkois.io   Connect with Danny Smith: Contact through Ryan Doran   Connect with Mark Stiving: LinkedIn: https://www.linkedin.com/in/stiving/ Email: mark@impactpricing.com  

John, VP of Product at Horizen Labs, breaks down how Zero-Knowledge Proofs (ZKPs) shift us from “trust” to “zero doubt.” We cover what ZK is (with an intuitive cave/password analogy), why ZK rollups matter, and how ZK Verify aims to be a dedicated, hyper-efficient proof-verification blockchain (think “B2B chain” living behind apps). We discuss tradeoffs (security/decentralization/throughput), SNARKs vs STARKs, real use cases (logins, proof of personhood, high-frequency trading privacy), why some things are over-hyped (prediction markets), and what's next (mainnet, grants, API tools, and massive proof scalability). If you care about scaling Web3 without sacrificing trustlessness, this one's for you.Timestamps[00:00] John's path from banking product to ZK & Horizen Labs[00:03] What Horizen Labs builds; the through-line of ZK across products[00:05] ZK explained: proving without revealing (the cave & secret door)[00:08] Why ZK rollups: decongesting Ethereum and lowering gas[00:10] ZK Verify: a dedicated chain for proof verification (Celestia-style specialization)[00:13] Product vision: mainnet, throughput, efficiency; exploring more of the ZK stack[00:14] Who uses it: “B2B blockchain” for high-volume proofs (DEX/HFT, logins, identity)[00:16] The trilemma still exists; where ZK helps and where tradeoffs remain[00:18] SNARKs vs STARKs; trusted setups & security nuance[00:21] Scaling challenges: fast-moving ZK landscape; substrate upgrades; mainstream timing[00:24] Adoption: UX, stablecoins, institutions, and avoiding another FTX moment[00:31] “Zero doubt” > “trust”: why ZK removes the need to trust[00:32] Most over-hyped now? Prediction markets (and a caveat)[00:36] Roadmap: capacity, aggregation, sample apps, grants, dev onboarding[00:40] Ask: builders, followers, grant applicants, API usersConnecthttps://horizenlabs.io/https://www.linkedin.com/company/horizenlabs/https://x.com/horizenlabshttps://www.linkedin.com/in/johncamardo/https://x.com/john_camardoDisclaimerNothing mentioned in this podcast is investment advice and please do your own research. Finally, it would mean a lot if you can leave a review of this podcast on Apple Podcasts or Spotify and share this podcast with a friend.Be a guest on the podcast or contact us - https://www.web3pod.xyz/

In this episode, Sean and Kelly welcome Pritesh Patel, a computer scientist specializing in AI who brings over 20 years of experience from companies like Turner Broadcasting, Walmart, and GE to his current role at Fisher Phillips law firm. Pritesh shares fascinating insights about implementing AI in knowledge-based industries, from automating his parents' frozen yogurt shop to helping lawyers transform their workflows. The conversation explores crucial concepts like the "Jobs to Be Done" framework, which emphasizes focusing on outcomes rather than getting stuck in existing processes. Pritesh explains how he approaches AI education through playfulness and intuition-building—whether that's getting Batman to sing "Twinkle, Twinkle Little Star" in ChatGPT or creating AI personalities that debate humans. The discussion touches on the importance of maintaining accountability while delegating responsibility to AI tools, the power of curiosity in adoption, and how reinforcement learning might shape the future of AI integration. Key resources mentioned: - Strategyn Jobs to Be Done Framework (https://strategyn.com/) - Tony Ulwick's innovation methodology - NotebookLM (https://notebooklm.google.com/) - Google's AI-powered research tool - Suno.ai (https://suno.com/) - AI music generation platform - OpenAI's Real-time API for voice interactions Special Guest: Pritesh Patel.

In this CPQ Podcast episode, host Frank Sohn speaks with Tarak Patel, Sr. Vice President of Product and Technology at Aleran Software, about how Aleran is bringing sustainable innovation to Configure, Price, Quote (CPQ) and digital commerce. Aleran's Connected Commerce platform is designed for mid-size manufacturers ($20M–$1B) and their channel partners. Built on headless, API-first, cloud-native architecture, the platform integrates with leading ERP systems(SAP, Epicor, Microsoft Dynamics, Infor, Acumatica and more) and CRM solutions (Salesforce, SugarCRM). It also offers native eCommerce, pre-built connectors, Avalara tax, payment gateways, and shipping integrations—helping companies move beyond spreadsheets and home-grown tools. Tarak explains how Aleran supports CTO and ETO products, with a feature- and rules-based configuration engine, plus AI-driven guided selling and automated product content generation. With low-code/no-code flexibility and an average 2-month implementation, manufacturers can achieve fast ROI. Beyond technology, Tarak shares insights on trust-based leadership, Aleran's rapid growth, and how his philosophy of “sustainable innovation” drives both the company and his personal life—including golfing with his two teenage sons.

In this episode I'm going to try to settle a debate of what's the best dividend portfolio. I'll then end things by sharing some blunt financial truths that became painfully real as I helped my mother-in-law move this weekend. Join the world's largest free Dividend Discord ➜ https://discord.gg/kkSr5FY Join my channel membership as a GenEx Partner to access new perks: https://www.youtube.com/channel/UCuOS-UH_s4KGhArN6HdRB0Q/join Seeking Alpha Affiliate Referral Link ➜ https://link.seekingalpha.com/2352ZCK/4G6SHH/ Click my FAST Graphs Link (Use coupon code AFFILIATE25 to get 25% off your 1st payment) ➜ https://fastgraphs.com/?ref=GenExDividendInvestor Please use my Amazon Affiliates Link ➜ https://amzn.to/2YLxsiW Thanks! As an Amazon Associate I earn from qualifying purchases. Support me & get Patreon perks ➜ https://www.patreon.com/join/genexdividendinvestor Use my Financial Modeling Prep affiliate link for awesome stock API data (up to a 25% discount) ➡️ https://site.financialmodelingprep.com/pricing-plans?couponCode=genex25

DTOs (Data Transfer Objects) aren't mentioned anywhere in the Laravel docs, but some devs use them heavily in their applications, whereas other devs never use them at all.In the latest episode of the No Compromises podcast, we weigh the pros and cons of DTOs in everyday Laravel apps, comparing them to form requests, PHPDoc-typed arrays, and service-layer boundaries, and share one area where DTOs truly shine. The takeaway: keep DTOs in the toolbox, but reach for them intentionally, not by habit.(00:00) - Framing DTOs in a stricter PHP world (01:15) - Our current practice: hybrids, few true DTOs (02:45) - Form requests, `safe()`, and typed inputs (03:45) - Reuse across API and form layers rarely aligns (04:30) - Where DTOs shine: normalizing multiple APIs (05:45) - Service boundaries: wrapping vendor objects (e.g., Stripe) (06:15) - PHPDoc-typed arrays vs DTO overhead (06:45) - Conventions, Larastan levels, and avoiding ceremony (07:45) - Treat DTOs as a tool, not a rule (09:15) - Silly bit Want to discuss how we can help you with an architecture review?

Welcome to this classic episode. Classics are my favorite episodes from the past 10 years, published once a month. These are N of 1 conversations with N of 1 people. This Business Breakdowns on Rolex is a long-time stand out. The founder and executive chairman of Hodinkee, Ben Clymer, was the perfect person to take us through the ins and outs of this legendary brand. For the full show notes, transcript, and links to the best content to learn more, check out the episode page ⁠here⁠. ----- This episode is brought to you by ⁠⁠⁠⁠⁠⁠WorkOS⁠⁠⁠⁠⁠⁠. WorkOS is a developer platform that enables SaaS companies to quickly add enterprise features to their applications. With a single API, developers can implement essential enterprise capabilities that typically require months of engineering work. By handling the complex infrastructure of enterprise features, WorkOS allows developers to focus on their core product while meeting the security and compliance requirements of Fortune 500 companies. Visit ⁠⁠⁠⁠⁠⁠WorkOS. ----- Business Breakdowns is a property of Colossus, LLC. For more episodes of Business Breakdowns, visit⁠ joincolossus.com/episodes⁠. Editing and post-production work for this episode was provided by The Podcast Consultant (⁠https://thepodcastconsultant.com⁠). Show Notes (00:00:00) Welcome to Business Breakdowns (00:03:01) His favorite Rolex watch ever (00:04:24) What makes the Rolex Daytona such a special watch  (00:07:19) The job-to-be-done for high-end watches beyond just telling them the time (00:12:18) The strategy behind marketing luxury products: ⁠The Luxury Strategy⁠ (00:14:34) An overview of the Rolex business (00:19:38) The history of Rolex  (00:38:45) Their genius in marketing and distribution  (00:41:55) How they make decisions and what others can learn from them (00:47:14) The financials of Rolex and other luxury watch brands (00:49:02) Most important business lessons others can learn from Rolex (00:52:54) Other luxury brands worth studying  (00:57:26) Negative lessons gleaned from Rolex

Seth Williams (00:00) I was able to buy a lot of land at dirt cheap prices. So there's no mortgages or anything on it. And when you buy anything for a small fraction of its actual market value, it's not hard to turn around and sell that thing and make money on it. Jason Hull (00:14) All right, I am Jason Hull, the founder and CEO of DoorGrow, the world's leading and most comprehensive coaching and consulting firm for long-term residential property management entrepreneurs. For over a decade and a half, we have brought innovative strategies and optimization to the property management industry. At DoorGrow, we have spoken to thousands of business owners, coached, consulted, and cleaned up hundreds of property management businesses, helping them add doors, improve pricing, increase profit. simplify operations and build and replace entire teams, we are like bar rescue for property managers. In fact, we have cleaned up and rebranded over 300 businesses and we run the leading property management mastermind with more video testimonials and reviews than any other coach or consultant in the industry. At DoorGrow, we believe that good property managers can change the world and that property management is the ultimate high trust gateway to real estate deals, relationships and residual income. At DoorGrow, we are on a mission to transform property management business owners and their businesses. We want to transform the industry, eliminate the BS, build awareness, change perception, expand the market, and help the best property management entrepreneurs win. Now, let's get into the show. And my guest today I'm hanging out with is Seth Williams. Welcome, Seth. Seth Williams (01:28) Hey, Jason, good to be here. Thanks for having me. Jason Hull (01:31) Yeah, it's great to have you and of REtipster. so Seth, let's get into a little bit of your background. You've done a lot of different things connected to real estate. Give us the background on your journey and how you got it kind of got into entrepreneurism and what made you start all this crazy stuff. Seth Williams (01:48) Yeah, sure. Yeah. Well, my journey kind of starts back in about 2005, 2006 when I was still in college. And like most people, I was trying to find houses I could buy that I could flip or rent that kind of thing. Just get into the real estate game. But I didn't really know anything about how to do it. I had no competitive advantage. I was looking on the MLS. That was the only place I knew I could look for to find deals. And there weren't any deals. It was horrible. I spent hundreds of hours and found nothing that made any financial sense. And I was just like, man, how do people do this? Like, how do people find good real estate deals if I can't find them? I was looking everywhere and there was nothing out there. And it was around, you know, after struggling with this for a couple of years, I discovered two things that kind of worked hand in hand. The first was the land business. So buying vacant land and Like most people, when I first heard that I was like, what? Picket land? Like, why would I do that? That makes no sense. It's just dirt. Like, where's the cash flow? Where's the income? The other thing that I discovered though was how to find deals off market through something called the delinquent tax list. And this is basically a list of property owners that every county has of properties that are currently back due on their property taxes. This is not the same thing. Jason Hull (02:52) Yeah. Seth Williams (03:11) as the tax sale list. So it's not the list of properties that's going to go up for auction soon. It's people who still own their property, but they're back doing taxes. If they don't pay them off soon, they're going to get their property taken from them. And these two things together, land and the delinquent tax list, I was able to find and contact people who had land with delinquent taxes on it. And because there were delinquent taxes, they're in a situation where it's like, Jason Hull (03:18) Yeah, they're just behind. Seth Williams (03:37) You got to pay off these taxes in like weeks or you're going to lose everything. So why are you in this situation? Is it because you don't care about the property? Like what is the issue? And in many cases, that was it. Maybe they just inherited it. Maybe they bought it 20 years ago, but for whatever reason, they didn't care about the thing. And I'm sitting there saying, Hey, I'll pay you a few hundred dollars, maybe a few thousand dollars, and I'll pay off your taxes and I'll make this problem go away. And because a lot of these people didn't want their property anyway, and I was kind of taking care of a nuisance in their life, I was able to buy a lot of land at dirt cheap prices. And I could also buy it free and clear. So there's no mortgages or anything on it. And when you buy anything for a small fraction of its actual market value, it's not hard to turn around and sell that thing and make money on it. So that was the business I got into. And it's been awesome. It's changed a lot over the years, but It's just been a really great way to, you know, without needing a whole lot of cash, finding properties, getting them for a very cheap price, and then making money without having to change anything on the property. Jason Hull (04:45) Yeah, got it. Okay, cool. Is that still the go-to strategy? Delinquent tax lists. Seth Williams (04:52) So, it's definitely still effective, but the drawback of the delinquent tax list is that they're kind of a pain to get, and then even when you do get them, they're kind of a mess to sort through. So, if you're willing to go through the nuisance of getting the list and sorting through it, there's a ton of value on that. But there's another way that's actually easier through a data service that I use called the LAN portal. And it's basically just a much more streamlined Jason Hull (05:04) Yeah. Yeah. Seth Williams (05:20) seamless, organized way to get lists of landowners. They don't necessarily have delinquent taxes, but I can find specifically the types of properties I want and then either send the mail or a cold column, that kind of thing. So both ways work. They both have pros and cons. The delinquent tax list is more of an annoying way to do it, but it's probably the more effective way. The land portal is a lot easier, but you get a little bit less motivation on that list because people don't have this delinquent tax problem. Jason Hull (05:48) Yeah, less of a mess to clean up, but probably a little quicker. so cool. you're going to unpack today the secrets of building wealth through land investing. This is like your number one specialty. And we'll chat a little bit about self storage. And I'm sure there's some property managers that are listening that might be like, haven't done that yet. Like I have not gotten into. That sort of investment and most of the property managers listening you if you're on a property management business your number one goal Should not be to just manage other people's properties. It should probably be to build up your own portfolio of stuff and and make some money That's probably a bigger better play and leveraging your company to attract deals and to attract Real estate so let's get into this. Where do we start? Seth Williams (06:37) Yeah, well, what I just described, there's kind of the high level view of how you find properties in the first place. And I mean, in terms of like people out there who are property managers who might invest in houses and that kind of thing, there's only one tax list or the land portal can work for those kinds of properties to the main difference is that you're going to find usually less competition when dealing with vacant land, because most people aren't thinking about land, thinking about houses. They think that's the way they have to do it. And that's fine if you want that. But the problem with houses, as you probably know, in property management, there's a lot more wrinkles. There's a lot more people problems. There's things falling apart that are broken and get stolen and destroyed. With land, there's none of that. It's a much simpler animal to deal with. But if your strategy is to find rentals or something like that, you could certainly scope out rental properties using the same method. You would just be targeting different types of property owners than I do. Jason Hull (07:10) Thank got it. So how does this connect to self storage? Seth Williams (07:34) Well, self storage is a totally different business than buying and selling vacant land, but there is some crossover. So back in 2021, I found a piece of land that was zoned residential. It was 6.7 acres and I bought it and I rezoned it to commercial. And then I got approval to build a self storage facility because I had always wanted to get into this business. A land business is great for generating big influxes of cash. It's like a cash generating machine. But self storage is a little bit different. At least the way that I do it, it's more of a cash flow play. you know, all in all, took me a couple million dollars to buy the land and build this facility. It took me basically a year to design it and build it. And it's comparatively speaking, more of a trickle of cash, cash flow, but it's permanent cash flow. There's also a lot of depreciation write offs. It's also very scalable. So it's easy to increase every single person's rent by $5 and the value effectively goes way up because of that. But like nobody moves out because it's just five bucks and most people don't care about a $5 increase per month. So it's a very different business. And for me, my long-term goal is to do more of that because the benefit of self-storage is that unlike land, it's not like a thing that you have to keep peddling for it to keep working. Land is a very active, you know, got to keep peddling or the cashflow is going to stop. Whereas self-storage is, well, you can buy one facility and the management is not terribly difficult for that, at least compared to like a rental property and the cashflow will come in for as long as you own the thing. So that was why I made that shift. Jason Hull (09:12) Nice. well, tell us a little bit about cell storage. How does that work? How can maybe property managers potentially get in? Seth Williams (09:21) Yeah, well, it's when I first got into it, what I tried to do is buy an existing facility from somebody within like an hour driving radius of where I lived. And I think that's probably the best first move is to do that if you can, because you don't have to deal with all of the work of construction and there's cash flow on day one. So like right when you buy the thing, money is already coming in. Whereas when you build a new one, it takes months for the thing to fill up. So that was what I tried to do at first, but problem was in my market, I couldn't find anybody who wanted to sell their property at anywhere near a reasonable price. People wanted like twice as much as what their facilities were worth. And people were paying it like it was just crazy. You couldn't find good deals. And when I saw that, was like, wow, I would normally never build something. But if people are being dumb and overpaying for self storage facilities, I could probably give this a go. And even if I screw it all up, I could still sell it and get out if I needed to. So that was why I decided to do that. And it's nice in that you get to design it and lay it out the way you want, but it's also a much longer runway required to put the cash in and then wait for it to fill up and start cash flow. Jason Hull (10:29) Yeah, this is our market to building these things out and then just selling them even though they're empty. Seth Williams (10:35) Yeah, that's what some people do. Selling them empty. I mean, that's not the ideal play. The real value of these things comes from paying tenants, that kind of thing. Maybe what most people would do is build them or maybe even buy an existing one that's half empty and then fill it up. Like do whatever you have to do to get tenants in there, whether it's changing the pricing or advertising more. And then once it's at least reasonably full, then you could cash out and do whatever you want. Buy another one or do something else. Jason Hull (10:39) Right. Got it. Okay. Got it. Cool. So vacant land, self storage, and then you're also like, you do a lot of content creation stuff in the real estate space. So tell us a little bit about that. Seth Williams (11:12) Sure. Yeah. So I started a website called REtipster back in 2012. And it was really kind of a place to store a lot of the lessons and knowledge that I had gained from my experience in land investing and in owning rental properties and everything I had done to that point. And I didn't really know what the plan was. I just knew, like, it's kind of fun for me to take my ideas and thoughts and things I've learned and distill them down into like bite sized chunks and help other people. figure out how to do the business from where they're at. And it turned out to be a lot of fun. And it didn't make money for like probably the first year that I was running it. But eventually I found ways to monetize it. Started a podcast, a YouTube channel. And a lot of what we talk about is land, but we also talk about self storage and occasionally rental properties, other things that are ancillary related to real estate investing. Jason Hull (12:07) Okay, well cool. Let me do a quick word from our sponsor and then we can get into a little bit more. So our sponsor for this episode is Vendoroo Many of you listening tell me that maintenance is probably the least enjoyable part of being a property manager and definitely the most time consuming. But what if you could cut that workload by up to 85 %? That's exactly what Vendoroo has achieved. They've leveraged cutting edge AI technology to handle nearly all of your maintenance tasks from initiating work orders. and troubleshooting to coordinating with vendors and reporting. This AI doesn't just automate, it becomes your ideal employee, learning your preferences and executing tasks flawlessly, never needing a day off and never quitting. This frees you up to focus on the critical tasks that really move the needle for your business, whether that's refining operations, expanding your portfolio, or even just taking a well-deserved break. Over half the room at last year's DoorGrowLive event conference signed up with Vendoroo right there. And then a year later, they're not just satisfied, they're raving about how vendor is transformed their business. Don't let maintenance drag you down. Step up your property management game with vendor. Visit vendor.ai slash door grow today and make this the last maintenance hire you'll ever need. All right, cool. So, Seth. Where should we go from here? We've been talking a little bit about vacant land, a little bit about self storage, talking a little bit about RE tipster. What do you think would be of the most benefit to property management business owners that are exploring some of this stuff? Seth Williams (13:42) Well, you know, maybe we could have a little conversation, you and me. So I've got a few questions I always go to when I'm talking to other real estate investors that are always kind of brings out some interesting perspectives. How long have you been in real estate, Jason? Jason Hull (13:55) Well, so I've been involved with coaching and consulting property management companies. So I'm more of a business coach for like since 2008. Seth Williams (14:04) Mm OK, gotcha. Well, interesting. Here's a question for you. What's one thing that you see new property managers focusing on that you think is actually a distraction from long term success? Jason Hull (14:09) so while. That's a good one. So the most common thing that I see that's a big distraction from long-term success is digital marketing. So a lot of property managers think in order to get more doors or get business, they need to do SEO. They need to do Google ads like pay per click, content marketing, social media marketing. The problem is the dirty secret marketers don't want to tell property managers because they like making money off of them. is that there's very little search volume of people looking on the internet for property management. So they can go on Google trends right now, put in property management backdated to 2004 when Google started tracking data and metrics to the present. And what you'll see is there's very little search volume. And if you compare it to any other term, like compared to AI is a good one lately, it has the same search volume of AI a decade ago. Whereas AI has this meteoric rise. Seth Williams (15:13) Mm, sure. Jason Hull (15:15) And compared to AI, property management is just a little line at the bottom. It like doesn't even register. And so there's plenty of business out there of people that don't want to manage their own property. There's no shortage in the U.S. There's no scarcity, but they're not looking for a property manager actively because they're either not aware that property managers are a viable option or exist, or they are aware, but most property managers suck. So they've written it off. Seth Williams (15:44) Yeah. So how do you find those people then if you don't know where they're looking or maybe you do know where they're looking. Jason Hull (15:44) and they're not really looking. We get them to do crazy things like pick up the phone and call non owner occupied property owners or like connect with real estate agents and create relationships to help the real estate agents get more deals from investors, stuff like that. So. Seth Williams (16:02) Yeah. I'll tell you, there's a ton of power in somebody who's willing to pick up the phone. I mean, so many people don't even want to think about that. But if you can do that, man, you're already way, way ahead of the crowd. Jason Hull (16:09) And there we go. Yeah, I mean, it's the one thing that we can teach clients that they can create business on demand at any time and not have to hope and pray that a market is able to give them something. yeah. Okay. Seth Williams (16:20) Mm-hmm. Yeah. Well, here's another question. What's something that you hear novice property managers or critics of property managers complain about that makes you roll your eyes? Jason Hull (16:35) Well, the first that comes to mind is a lot of novice property managers complain about the potential clients being cheap. yet they're cheap. And so that's kind of the blind spot that I think there's a lot of property managers that have. They're like, like, I had a client once and he was complaining that, about, you know, I'm tired of getting all these people wanting discounts or asking for us to lower our pricing, all these people that are so cheap about related to property management. And then I saw the same person post in a Facebook group for property managers saying, hey, does anybody have a discount for this? property management software or this then like, what is it? A maintenance software that exists because I don't want to pay full price. And so the irony wasn't lost on me. you know, usually the blind spot that we have is we, you know, kind of project that and create that in others. And so if you're cheap and you have a cheap mindset, then you're going to attract cheap clients. It's far more likely not only that, but you're going to be a lot more sensitive to it. It's going to impact you differently. Seth Williams (17:16) Hmm. Jason Hull (17:36) and people will pick up on that and they'll feel more anxious and be more price sensitive because you are. Seth Williams (17:40) Yeah. For those property managers who are willing to pick up the phone and call around and find their customers, what do they do to avoid those cheap clients? Is there some red flag they can look out for to say, you're not a good fit. We're going to go look here instead. Like, how do you find people that are willing to pay what they have to pay? Jason Hull (17:58) Well, I think I just had Dustin Heiner on as an interview. And yeah, I know him from some masterminds that we're in together. And Dustin's a really cool guy. Dustin had this, we did this great episode where he's like our client's ideal client, really. Because he's like, the first thing I do is I try to find a property manager before I even get a rental property. Seth Williams (18:03) Yeah, Essence Mm. Jason Hull (18:24) And I want to ask them where I should get a rental property and ask them for their advice. And I want a good property manager I can trust before I go find a property. But it's like, usually everyone does it backwards. They go get a realtor, they get a property. Then they go and try and see if there's a good property manager. And he wants to be hands off. He doesn't want to call his property manager. He doesn't want to be involved in it. He wants them to just take care of stuff. That's the ideal. So I think the challenge is when property managers are looking on the internet for clients. They're like getting them through SEO or pay per click. These are the worst investor clients. They view property management as a commodity. They think all property managers are the same and they're not right. Not all property measures the same and most property managers are not very good. So to find the exceptional ones, usually you're going to find the better clients for a property management business by doing stuff that is Seth Williams (19:11) Mm-hmm. Jason Hull (19:20) more towards the strategies that we would rely on, which are warmer leads, warmer connections, so that you're not getting the crappy scraps that fall off the word amount table that are now searching on the internet looking for the cheapest manager. And if you build your portfolio off of digital marketing and the cheapest and most price sensitive owners, then you're going to have the highest operational costs, more than my clients at least, and it's going to be expensive to run your business. So. Seth Williams (19:43) Yeah. Yeah. What do you think makes somebody a good property manager? Because I've had my share property managers that were terrible. had one that was pretty, pretty decent. And in my case, I thought what made them stand out was just really good communication. Like I was always in the loop. I was never questioning where things were at. Like I just, I just felt like I knew what was going on. I don't know if that's true for everybody, though, in your mind, like the ones that really stand out and just kill it in this business and have no problem. finding clients and keeping them happy. Like what is it they're doing that makes them so good? Jason Hull (20:16) Okay, this is a great question and I love that you shared your perspective. And tell me a little bit more, what do you think makes a good property manager? And then I'll share my thoughts, which might be a little different. You said good communication. Seth Williams (20:28) Yeah. mean, I just kind of mentioned that. Yeah. And I will say one thing, you know, one of my nightmare experiences with a bad property manager was and maybe this is just foolish on my part, but I relied on them to find some subcontractors to, you know, make some improvements and repairs on my property. And they just found horrible people that totally screwed up the property. And and they just kind of walked around all flustered, like, I can never find good people. And like. I don't care. Like if he can't do it, then don't don't do it. Yeah. Like tell me you can't don't just, you know, find somebody who's going to ruin my property. So that really annoyed me. ⁓ Jason Hull (20:59) to the next. Hmm. Yeah, that's yeah, that's hot. Okay, so I mean, according to studies and surveys, the number one reason that people leave a property management company is communication. And so I think a lot of property managers mistakenly think they need to over communicate. But I think what a lot of property managers do is they give their tenants and their owners a blank check to steal all their profits in some instances, because that's The number one source of financial leaks that I've seen in companies is interruptions. so they just, every phone call from every tenant, every owner, constant interruptions means they need way more team, way more staff. This is the business. What I've found is really effective property management companies aren't communicating all the time. Good communication is what the clients want if they don't trust the property manager. Seth Williams (21:41) Mm-hmm. Jason Hull (21:55) If they trust the property manager, they want zero communication. So that's very different. So the best property managers, what I think is they set really good boundaries. It's different. It's not like, hey, I'm going to talk to you all the time. So for example, my wife, Sarah, she managed 260 units part-time in 20 hours a week, basically by herself. She had one time, one part-time person boots on the ground, C-class properties, average rent below a grand, difficult tenants. and she had plenty of time and she had 60 to 90 % profit margin in her business. One of the most ridiculous like case studies I've ever seen. Like she was really successful, very profitable, but she basically had a conversation with her owners at the beginning said, hey, it's been great getting to know you, getting to know your property from here on out. You're not going to be hearing from me much. If I call you, if my name shows up on your phone, I'm asking for money because there's a problem. So you're probably not going to want to hear from me. And she was said as a joke, but she was setting boundaries and they would laugh. But that was how they trusted her. They trusted her because she set really strong boundaries. And so that reduced their anxiety and it lessened the amount of times they had to call. They weren't like, hey, Sarah, did we get that tenant yet? Who's looking at the property? Anyone look at it this week? Like what's going on with the maintenance? What happened with this? Are we getting this handled? Like they weren't anxious. They trusted her to manage and she was good at managing. So one, you got to be good at managing. Seth Williams (22:57) Mm Yeah. Jason Hull (23:17) Like you've got to have good vendors. You know, you've got to have good resources. Otherwise, why would they use you? Why don't they just do it themselves? As a good property manager, you should be way better at it than your clients. You're the professional. Which means you're not relying on them to tell you what to do. They should not be micromanaging the manager. They didn't want, they didn't hire you to micromanage you if you're a property management business owner, right? And so I think that there's good communication. Seth Williams (23:27) Yeah. Jason Hull (23:44) This is the superficial thing that everybody sees. The better thing is having really good service and really good boundaries is even better. Seth Williams (23:52) Yeah. Well, it seems like the boundaries thing works as long as you are good at your job, right? I mean, if you do let a place sit vacant or if you do find a subcontractor who screws the property all up, your trust is gone now and they are going to be harassing you. Jason Hull (23:58) Yeah. Yeah, you can't say, don't call me. I'll let you know when I get this taken care of, you know, because their anxiety is going to go through the roof. Right. Yes, exactly. You have to be on top of your stuff and you have to be good. but the conversely, you can't be good if you are over communicating with everybody. It's not it's not a scalable business. You just can't do it. And so if you are giving everybody all the attention all the time, Seth Williams (24:12) Yeah. Jason Hull (24:31) it's going to be very little attention and it means you're not going to be able to pay attention to and focus on the things that actually matter and do a good job. So setting boundaries is required in order to do have a really healthy business that does perform well. Especially if you're a business owner. Seth Williams (24:43) Yeah. Yeah. I guess like say if you're managing a property that's in the armpit of town and it's going to take a long time to find a tenant. I mean, maybe it's starts by just telling that property owner, hey, it's going to be a while. Like set the expectations. Like don't make them think it's going to happen fast when it's not. Is that what you do? Jason Hull (24:55) Good expectations. Absolutely. Yep, setting good expectations, setting good boundaries is absolutely critical. And I think that goes for any business. Any business that involves humans, right? If they can land, there's not a whole lot of people involved, but maybe in the deal, you need to set boundaries and expectations, right? In self storage, same thing. You have tenants, there are people involved. It's a little less than dealing with toilets, and termites, but. Seth Williams (25:17) Mm-hmm. Yeah. Jason Hull (25:27) There's still humans that are involved and you have to be willing to set boundaries. know, there's self-storage places in LA that have a problem with homeless people trying to build homes inside of them. Right. Like that's probably outside of like what you wanted to be selling, you know, it's not probably legal for them to live there. Right. And so, yeah, setting boundaries, setting expectations. And they say an ounce of prevention is worth a pound of cure. And that's probably true in any business. Yeah. Seth Williams (25:51) Yeah. Yeah. Yeah, totally. I'm wondering if you could wave a magic wand and fix anything about the real estate industry right now, what would that be? Anything come to mind? Jason Hull (26:03) Ooh, fixing the real estate. Seth's interviewing me now, everybody. and yeah, you are. You are good at this. so, well, why don't you go first? This is a great question. So Seth, what would you wave your magic wand and change about the real estate industry? Seth Williams (26:07) Yeah. I'm pretty good at this. Yeah, mean, mine would be mostly related to the niches that I'm in. So like land and self storage and on the self storage front. So the way that we manage our properties, the software is a huge component. mean, it's it's a very, very important. It's how we assign gate codes. It's how we get people's payments. It's how we communicate with them. Like it's a big deal. But a lot of the software out there is terrible. Like it is just garbage software. It looks like it was designed 20 years ago and it's It's like antiquated, but it's expensive. And the problem is, once you start using it, they kind of hold you hostage. So like, even though it's bad, you got to keep paying for it and rewarding this broken system. So it's just a it's just a pain. So if I could wave a wand, I would probably make it super easy to jump ship and switch softwares without them holding all of my customers information hostage. That's what I'd fix. Jason Hull (26:55) Yeah, you're in bed forever. Got it. You might be able to wave that one now with vibe coding and AI. It's probably possible. Get a nerd, they create a prompt for you. They could probably import the API or the data or the information from an existing company software, or at least get a CSV export and you could probably create your own software from scratch. It does exactly what you want. And kids are making software every day now. Somebody just made vibe coding software and some women made this app. Seth Williams (27:17) Cool. Jason Hull (27:41) called T or something like this. And it was like rating men for dating. So women could say, this guy's like not a great guy to date or something like this. and it was like at the top of the app store, like you can, you can create stuff now through AI. And the only problem with that app is they had a big security flaw that some guys probably didn't like what was on the app about them easily hacked it. And they doxxed all of the women's Seth Williams (27:51) interesting. No. Jason Hull (28:09) Credit or not credit cards, but their drivers licenses that they had submitted to verify their profiles and they made it all public Right. So if you're doing vibe coding people make sure you have somebody take a look at the security side of it All right. Yeah, so but that you know that could be that that could be a magic wand that could be waived My magic wand in line with what you said I would selfishly do something towards the property management industry is I would change the licensing requirements throughout the US, because the licensing requirements in each state to be a property manager have nothing to do usually with property management. Usually you have to have a real estate broker's license in order to manage rental properties, and that doesn't qualify them to manage rental properties at all. But it does create a big hurdle for them to be able to do it, and so it keeps probably some good actors out. Seth Williams (28:48) Yeah. ⁓ Jason Hull (29:03) and probably makes people feel overconfident to do something that they probably aren't prepared to do. And very few states have a separate property management license. So, yeah. Seth Williams (29:12) What is the connection there? Like, is it because you have to effectively list properties? Like, you're not selling it, but you have to list it publicly and then respond to people who are interested in that kind of thing. Jason Hull (29:19) Yeah, I think it's related to leasing and renting properties. The number one source of complaints at most board of realtors is related to leasing, not real estate. so, yeah, so there are some things in which, but there should be separate licensing, separate rules specific to property management and that maybe raise the bar for property management so that they come in, you know, understanding some things legally. Seth Williams (29:29) Mm-hmm. Hmm. Jason Hull (29:46) that are related to that because there's a lot of real estate agents that are doing some stuff that's probably not legal when it comes to leases or having conversations or probably breaking laws, you know, and so that can be dangerous. we have one of our lead magnates that we have that we have clients build out is a 411 on leasing course. And it's basically a course property managers can download, put their branding on and go scare the shit out of real estate agents in handling leases. And so that these agents will refer business to them, which isn't hard to do because a lot of real estate agents are dabbling in leases and they should not be messing with it because it puts the real estate license at risk. So. Yeah, so that would be my magic wand. Well, that's to tell us a little bit about your podcast and some of the stuff that you're up to lately and how people can get a hold of you. Seth Williams (30:26) Yeah. Hmm. Interesting. That's cool. Yeah. Sure. Yeah, the REtipster podcast, it's really creative name, just REtipster podcast. I've been running it since 2018 and every week, just talk to people that I find really fascinating. Sometimes they're in land, sometimes self storage, sometimes neither. They just have a really cool thing going on and I like to grill them and ask them questions and really get to the bottom of like how they're doing what they're doing. So not surfacey questions, but like really getting into it. It's a ton of fun. So Yeah, feel free to check it out or anything at retipster.com. That's kind of the home base where you can find all the stuff I have out there. Jason Hull (31:18) Perfect. Very cool. Well, Seth, it's been fun. Appreciate you asking me some questions. That's always a surprise. And it's great having you here on the the DoorGrow show. If those of you listening, if you've been stuck or stagnant in your property management business, you want to take it to the next level, reach out to us at door grow dot com. Also join our free Facebook community just for property management business owners at door grow club dot com. And if you found this even a little bit helpful, don't forget to subscribe and leave us a review. We'd really appreciate it. And until next time. Seth Williams (31:22) Yeah, likewise. Jason Hull (31:46) Remember the slowest path to growth is to do it alone. So let's grow together. Bye everyone.

In this episode, Mark Longo navigates the fast-moving world of options markets for Friday, September 26th. The episode covers various segments such as VIX, SPY, S&P 500, small caps, NASDAQ (Qs), and key single-name options including AMD, Intel, Tesla, Palantir, and more. Mark provides detailed insights into the trading volumes, notable contracts, and market activities, highlighting major trades and significant trends.    00:26 Welcome to the Hot Options Report 00:54 Public: The Cost-Effective Way to Trade Options 01:28 Scanning the Tape: VIX and SPY Analysis 04:02 Small Caps and NASDAQ Insights 05:29 Single Name Options 15:20 Conclusion and Next Steps -------------------------------------------------------------------- All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

In this episode, Mark provides insights into the fast-moving options market for Thursday, September 25th. The show highlights dominant options products from Apple to VIX, examining significant trades and market trends. Key points include VIX's lower than average volume, SPY's explosive activity, SPX closing down slightly, and notable performances in the single names category including Oracle, Core Weaver, MicroStrategy, Palantir, Amazon, Opendoor, Apple, Intel, Tesla, and Nvidia.  00:00 Introduction and Welcome 01:55 Public: Cost-Effective Options Trading 02:39 VIX Market Analysis 03:38 SPY and SPX Market Insights 05:34 Small Caps and QQQ Market Activity 06:52 Single Name Stocks: Oracle, CoreWeave, and More 11:57 Tech Giants: Apple, Intel, and Tesla 14:34 Nvidia and Conclusion --------------------------------------------------------------------- All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

The Secretary joined Greg for an in-person sit down at the API dinner. The two discuss issues related to elections and cutting of state government spending. They also discuss Allen's campaign to become Alabama's next Lt. Gov and some of the issues related to his campaign.

Change CEO Sonia Nigam joins The Nonprofit Lab to unpack the hidden rails behind online giving. From compliance pitfalls and paper checks to donor-advised funds and API-first solutions, Sonia shares how Change is simplifying fundraising infrastructure and unlocking more dollars for nonprofits.

In episode 22 of Open Source Ready, Brian and John sit down with Benji Kalman, co-founder of Root, to explore the intersection of AI, software development, and security. They unpack "vibe coding," its impact on API proliferation, and the hidden costs of increased technical debt. Learn why a security vulnerability is just a bug with a purpose, and discover how AI agents can be used not just to write code, but to automatically find and remediate vulnerabilities in open-source containers.

In this episode of the Hot Options Report, Mark provides a detailed analysis of the day's key options activity for Wednesday, September 24th. The report covers a range of products dominating the options chains, including VIX, SPY, SPX, small caps, Nasdaq, single names such as Palantir, AMD, Alibaba, Micron, Amazon, Apple, Intel, Open, Nvidia, and Tesla. Each segment highlights the most notable contracts traded, their pricing, and market implications.    00:00 Introduction 01:29 Hot Options Report: VIX Analysis 03:15 SPY and SPX Market Activity 05:07 Small Caps and Nasdaq Insights 06:26 Single Names Spotlight 14:35 Conclusion and Upcoming Content ---------------------------------------------------------------------- All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

Send us a textThe gap between cloud-native and traditional networking has never been more evident. As organizations struggle with hybrid environments, finding a unified management strategy feels like searching for the mythical "one ring to rule them all."In this thought-provoking episode, we welcome Eric Chou, author, instructor, and podcast host with over a decade of experience at AWS and Azure. Eric brings a rare insider perspective on how hyperscalers approach networking fundamentally differently than traditional vendors.We explore why cloud providers built their infrastructure API-first from day one, while traditional networking vendors had to retrofit APIs onto existing hardware. This architectural distinction creates significant challenges when trying to manage both environments cohesively. Eric explains why cloud tools excel at declarative configurations while traditional networking tools often take a more procedural approach, and when each might be appropriate for your organization.The conversation takes a fascinating turn when we discuss how AI is reshaping network engineering. Are we headed toward a dangerous knowledge gap as junior engineers rely on AI without developing foundational skills? Eric advocates for an "enhance, not replace" philosophy that values human expertise while leveraging AI as a productivity multiplier. We debate whether simulation can ever truly replace the hard-earned lessons of 3 AM network outages.Whether you're managing a hybrid network environment or wondering how to prepare for an AI-driven future, this episode offers practical insights and a surprisingly optimistic outlook on the future of networking. Listen now to understand how bridging the gap between cloud and on-premises networking might be less about finding a universal tool and more about developing the right mindset and approach.Connect with Eric:Network Automation Nerds Podcast: https://packetpushers.net/podcast/network-automation-nerds/ Amazon Author Page: https://www.amazon.com/author/ericchouLinkedIn: https://www.linkedin.com/in/choueric/ Network Automation Nerds Website: https://networkautomationnerds.com/ Purchase Chris and Tim's new book on AWS Cloud Networking: https://www.amazon.com/Certified-Advanced-Networking-Certification-certification/dp/1835080839/ Check out the Monthly Cloud Networking Newshttps://docs.google.com/document/d/1fkBWCGwXDUX9OfZ9_MvSVup8tJJzJeqrauaE6VPT2b0/Visit our website and subscribe: https://www.cables2clouds.com/Follow us on BlueSky: https://bsky.app/profile/cables2clouds.comFollow us on YouTube: https://www.youtube.com/@cables2clouds/Follow us on TikTok: https://www.tiktok.com/@cables2cloudsMerch Store: https://store.cables2clouds.com/Join the Discord Study group: https://artofneteng.com/iaatj

“Taxes are a monster, but we tame it and make it digestible,” says CeeJay Barber, Vice President of Business Development at Datagate. At Navigate 25, Barber sat down with Doug Green, Publisher of Technology Reseller News, to explain why billing is one of the toughest challenges facing managed service providers (MSPs)—and how Datagate is helping them streamline the process. Datagate provides a billing platform purpose-built for MSPs in telecom. The system automates everything from call detail record (CDR) ingestion and taxation to PSA integration and unified invoicing. With over 500 service providers on the platform, Barber stressed the importance of compliance in an increasingly fragmented regulatory landscape: “If you try to take it on by yourself, you'll overcomplicate your processes, overspend, and still risk getting it wrong.” One highlight of the discussion was Datagate's new Halo PSA integration for AT&T's Apex channel. The solution allows provisioning, billing, and customer management to occur within a single workflow, eliminating the need for multiple AT&T portal logins and ensuring billing flows seamlessly back into Datagate. Barber emphasized that Datagate is deeply API-driven, making it a strong fit with Alianza and Metaswitch partners. “Any Alianza partner can work with Datagate,” he noted. “If you're providing voice and need it billed and taxed accurately, we can integrate it into your workflow.” With AI-driven innovation, regulatory complexity, and growing MSP demand for bundled services, Barber positioned Datagate as a critical enabler for service providers looking to scale without sacrificing compliance. For more information, visit datagate-i.com.

“Fire alarms, elevators, emergency phones—these systems are mandated by law, and they require reliable communication paths,” says Jake Jacoby, Founder & CEO of TELCLOUD. At Navigate 25, Jacoby spoke with Doug Green, Publisher of Technology Reseller News, about the growing urgency of replacing traditional copper POTS lines as carriers abandon legacy infrastructure. With deregulation driving up costs and carriers shifting investment to wireless and fiber, millions of POTS-dependent systems are at risk. TELCLOUD provides a backend platform that enables reseller partners to deliver next-generation POTS replacement services. Unlike one-size-fits-all box solutions, TELCLOUD's flexible platform integrates with partners such as Ericsson, Digi, Peplink, and others, ensuring reliable connectivity, 24-hour battery backup, and compliance with NFPA, CAL FIRE, and local fire department codes. Jacoby emphasized that POTS replacement is no longer optional modernization but a legal requirement. “Elevator phones, fire panels—if those lines go down, buildings become unsafe and unusable. Our platform ensures compliance, monitoring, and future-proof reliability.” TELCLOUD has also built direct API integrations with Metaswitch and Alianza, allowing partners to bring their own switching infrastructure and leverage TELCLOUD's expertise to deliver code-compliant solutions. “We're not customer-facing—we're the engine behind the resellers. Customers trust their providers, sometimes for decades. We help those providers deliver POTS replacement the right way.” For more information, visit telcloud.com.

Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

"le modèle nous fait du feedback directement sur la satisfaction de l'utilisateur" Le D.E.V. de la semaine est Frédéric Barthelet, CTO @ Alpic. Frédéric nous fait découvrir le Model Context Protocol (MCP), une innovation technologique qui ouvre les portes de nos applications et plateformes favorites aux agents IA.Si les applications mobiles et les sites web ont permis aux entreprises de proposer leurs produits et services à leurs utilisateurs, et si les API leur ont permis d'être intégrées chez leurs partenaires, ce sont leurs serveurs MCP qui leur permettront demain d'être découvertes et utilisées par des IA.Frédéric nous partage les enjeux de conception d'un serveur MCP pour maximiser son taux de succès, la métrique phare de la qualité d'un serveur. Réduire le nombre d'outils via le polymorphisme, limiter la portée de ses réponses, utiliser les erreurs comme mécanisme de découvrabilité : autant de stratégies pour développer le meilleur serveur possible.Enfin, il évoque l'avenir du protocole et les potentiels mécanismes de découvrabilité (marketplace et régie pub) qui sont mis en place côté client par des géants comme Anthropic, OpenAI ou Mistral pour amener ses clients sur ce support et canal d'acquisition dernière génération.Chapitrages00:00:55 : Model Context Protocol, kezako ?00:03:53 : Tools, resources et prompts d'un serveur MCP00:05:45 : Améliorer le taux de succès de son serveur00:10:08 : Agentic Experience, ou l'art de désigner des parcours pour agents IA00:13:22 : Limitations et Perspectives00:17:30 : MCP, un nouveau canal d'acquisition pour les business00:23:26 : Contrôle et Autonomie des Agents00:25:39 : Ellicitation, ou comment solliciter l'utilisateur quand l'agent ne suffit plus00:29:10 : Passer à la v2 de son serveur00:53:47 : Perspectives Futures du Protocole MCP01:01:18 : Conclusion Liens évoqués pendant l'émission Alpic pour déployer son serveur MCPTalks de MCP Dev Summit sur YoutubeTalk de Laurie Voss sur toutes les alternatives MCP 🎙️ Soutenez le podcast If This Then Dev ! 🎙️ Chaque contribution aide à maintenir et améliorer nos épisodes. Cliquez ici pour nous soutenir sur Tipeee 🙏Archives | Site | Boutique | TikTok | Discord | Twitter | LinkedIn | Instagram | Youtube | Twitch | Job Board |Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

In this episode of the Hot Options Report, Mark delves into the day's most significant developments in the options market for Tuesday, September 23rd. The focus is on key instruments like VIX, SPY, SPX, small caps, QQQ, and various single stocks, including AMD, Micron, Plug Power, Intel, Palantir, Apple, Amazon, Tesla, and Nvidia. Listen to detailed insights about trading volumes, striking prices, and expected market movements.  00:00 Introduction and Welcome 00:26 Hot Options Report Overview 02:37 VIX Analysis 03:25 SPY and SPX Insights 04:37 Small Caps and QQQ Breakdown 06:03 Single Names Spotlight 16:02 Conclusion and Wrap-Up ----------------------------------------------------------------- All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

In this episode of Quality Talks with Peggy O'Kane, Peggy welcomes Anna Taylor, Associate Vice President for Population Health and Value-Based Care at MultiCare Connected Care in Tacoma, Washington. From the outset, Peggy is captivated by Anna's clarity, conviction and optimism. Anna doesn't just understand the technical challenges of digital transformation—she makes them accessible and inspiring. With a natural gift for storytelling and empathy for patients and providers alike, Anna explains why interoperability and value-based care are not just buzzwords but essential pathways to a better system. Anna's personal anecdotes, including her father's experience with AFib, bring urgency and humanity to the conversation. Peggy calls Anna an ally in the movement for quality, and it's easy to see why: Anna's vision is practical, inclusive and motivating.Listen to learn about:Embracing Imperfection to Drive Innovation: Anna challenges the perfectionist mindset in the quality world, advocating for iterative improvement and a willingness to try, fail and learn.Reengineering Workflows for Better Care: Anna has a specific vision for redesigning administrative tasks like prior authorization so clinicians are free to focus on meaningful patient interactions.Proving the Power of Web-Based Reporting: Anna discusses an initiative that shows how API-driven reporting can scale quality measurement affordably and accurately.This episode will resonate with clinicians, policymakers and technology leaders who are eager to rethink how care is delivered—and who appreciate the power of clear, passionate communication to drive change.Key Quote: I know there's a better way to do this because you can see it in your mind how it can flow. It's just not the culture that's built into a fee-for-service world. We have to go on a cultural journey and exploration on why we're really here to do this work and figure out how do we get to those workflows that are going to: Number one, give us more space in our schedule for patients. Number two, get the patients who need the most care, be able to stratify patients and be able to monitor more. Getting that cultural mind shift is hard. And the quality outcomes could be better if we can get all this data together to make better decisions about a care plan. I'm really thankful for my dad's ability to outlive his father and so on because of modern medicine. We can do better. We can do so much better in the care we provide our patients.-- Anna TaylorTime Stamps:(06:22) Value-Based Care and Misaligned Incentives(09:45) Anna's Story: Technology, Data, and Her Father's Care(12:48) How Digitalization Helps Primary Care(17:59) Embracing Imperfection and Driving Innovation(27:45) Peggy's ReflectionsLinks:Connect with Anna Taylor Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Jean-Baptiste Martinoli, créateur de la tablette québécoise ExoPC en 2010, explore aujourd'hui les frontières de l'intelligence artificielle. Il s'intéresse désormais aux IA dotées de mémoire à court et long terme, capables d'interagir entre elles et d'adapter leur caractère. Ses recherches portent sur la conscience artificielle, le raisonnement et les garde-fous éthiques, tout en soulignant l'importance d'une souveraineté numérique québécoise. Il invite le grand public à expérimenter directement avec les API pour mieux comprendre et maîtriser ces outils, en dehors des interfaces limitées des grandes plateformes.

Craig Jeffery talks with Steven Peterson of Chick-fil-A about their journey from RPA to APIs to agent-based AI. They discuss use cases in bank connectivity, forecasting, and document summarization, as well as the progression from bots to orchestration. How does a lean treasury team innovate at scale? Listen in to hear how curiosity and strategy are driving real transformation.

In this episode of The Cybersecurity Defenders Podcast, we discuss some intel being shared in the LimaCharlie community.ESET Research has uncovered what it believes to be the first documented case of AI-powered ransomware, dubbed PromptLock.Multiple CrowdStrike-branded npm packages were recently discovered to be compromised, marking a new wave in the ongoing “Shai-Hulud” supply chain attack campaign.Researchers at AI security firm EdisonWatch have uncovered a new vulnerability in the ChatGPT calendar integration, revealing how it can be exploited to execute attacker-controlled commands.The most mature and globally distributed FileFix campaign observed to date is now active in the wild, according to researchers at Acronis.Support our show by sharing your favorite episodes with a friend, subscribe, give us a rating or leave a comment on your podcast platform.This podcast is brought to you by LimaCharlie, maker of the SecOps Cloud Platform, infrastructure for SecOps where everything is built API first. Scale with confidence as your business grows. Start today for free at limacharlie.io.

У свіжому дайджесті DOU News поговоримо про рекламу на холодильниках Samsung та нові смарт-окуляри від Meta. А також про те, хто реально користується ChatGPT та інші новини українського ІТ та світового тек-сектору. Таймкоди 00:00 Інтро 00:26 Галактика IT: портрет українського айтівця 2025 04:04 Атака «Shai-Hulud» в npm: постраждало 180+ пакетів 06:02 Тематичні спільноти на DOU — чому варто підписатися 07:08 Google додає Gemini у Chrome для всіх користувачів 09:10 Італія вводить перший комплексний закон про ШІ в ЄС 10:25 Gemini виграв світовий фінал Міжнародної олімпіади 12:53 OpenAI оновила Codex: думає до 7 годин 14:57 Meta показала нові смарт-окуляри з дисплеєм 19:01 Meta спричинила DDoS-атаку на власному заході 20:43 Samsung запускає рекламу на холодильниках у США 22:25 Хто реально користується ChatGPT і як саме 25:23 Критики атакують угоду Трампа про TikTok 27:20 Що цього тижня рекомендує Женя: пошук API та гру

This episode of the Hot Options Report provides an in-depth analysis of the most impactful options activity for Monday, September 22nd. Mark Longo breaks down significant trades in major market segments including VIX, SPY, SPX, and single names like Apple, Nvidia, and Tesla. The episode also highlights standout trades such as the November 50 VIX calls, SPY 666 calls, and notable activities in smaller cap names.    00:00 Introduction and Welcome 01:02 Hot Options Report Overview 02:35 VIX Land Analysis 03:23 SPY Land Insights 04:01 S&P 500 (SPX) Highlights 05:06 Small Caps Activity 05:34 NASDAQ QQQ Breakdown 06:23 Single Name Stocks Review 14:49 Conclusion and Upcoming Events ------------------------------------------------------------------------ All investing involves risk. Brokerage services for US listed securities, options and bonds in a self-directed brokerage account are offered by Open to the Public Investing Inc, member FINRA & SIPC. Not investment advice. Options trading entails significant risk and is not appropriate for all investors.  Customers must read and understand the Characteristics and Risks of Standardized Options before considering any options strategy.  Options investors can rapidly lose the value of their investment in a short period of time and incur permanent loss by expiration date. Certain complex options strategies carry additional risk, including the potential for losses that may exceed the original investment amount, and are only available for qualified customers.  Index options have special features and fees that should be carefully considered, including settlement, exercise, expiration, tax, and cost characteristics.  See Fee Schedule for all options trading fees. There are additional costs associated with option strategies that call for multiple purchases and sales of options, such as spreads, straddles, among others, as compared with a single option trade. Rebate rates vary monthly from $0.06-$0.18 and depend on the particular security, whether the trade was placed via API, as well as your current and prior month's options trading volume. Review Options Rebate Terms here. Rates are subject to change. Go to public.com/optionsbrief to learn more.

Scaling CI/CD for mobile apps is hard. Faster test runs often lead to more tests, more infrastructure, and more complexity. So how do you keep your pipelines healthy and reliable while still shipping at speed? In this episode, we sit down with Anton Malinski of Marathon Labs to explore the real-world lessons he's learned building and optimizing mobile CI/CD pipelines. You'll discover: How to scale mobile test automation without introducing friction What “healthy CI growth” looks like in practice Why real devices still matter, even with a massive emulator fleet How backend mocking and dedicated mobile API gateways transform shift-left testing Practical advice for teams evolving from weekly releases to on-every-commit confidence Whether you're a QA leader, automation engineer, or DevOps practitioner, this conversation gives you the insights and metrics you need to take your mobile testing pipelines to the next level.

Michael Nicosia is the Co-founder and COO of Salt Security, a company that protects APIs from threats using cloud-scale big data, AI, and ML. Under his leadership, Salt has raised $271 million, reached a $1.4 billion valuation, and has become a leader in API security with patented AI technology and Fortune 500/Global 1000 clients. With over 20 years of experience in enterprise software sales and marketing, Michael helped lead Adallom as COO from its founding to its $327 million acquisition by Microsoft. In this episode… APIs power nearly every modern digital service, yet most companies remain unaware of just how vulnerable these connections can be to breaches. With AI agents, MCP protocols, and microservices expanding rapidly, how do you ensure that sensitive data isn't leaking through unseen cracks in your API infrastructure? Michael Nicosia, a serial entrepreneur and technology executive, shares how he took the leap from corporate roles to building a platform that safeguards APIs. He describes starting with only an idea, refining it through Y Combinator, and securing early validation from security leaders. Along the way, Michael emphasizes the importance of focusing on customer outcomes, building the right team, and persevering through uncertainty. His journey shows that protecting digital services isn't just about software — it's about resilience, trust, and staying ahead of attackers. In this episode of the Inspired Insider Podcast, Dr. Jeremy Weisz interviews Michael Nicosia, COO and Co-founder of Salt Security, about scaling cybersecurity solutions for the modern digital world. Michael discusses lessons from Y Combinator, navigating the fundraising journey, and securing enterprise clients. He also shares insights on pricing models, hiring top talent, and the role of mentorship in building a lasting company.