Podcasts about Nic

What happens behind the closed doors of a strip club? Pole dancing, booming basslines … and in Nic Stone's new novel, the chilling mystery of a missing exotic dancer. In Boom Town, the manager of a fictional Atlanta strip club sets out to find a missing dancer named Charm. The book offers a shadowy taste of Atlanta's notorious adult entertainment scene … but it's also a look into the lives of the regular women who live and dance in the city. This week, Nic joins Mattea Roach to talk about growing up in Atlanta, why strip clubs are cultural epicentres and writing her first novel for adults. Liked this conversation? Keep listening:Pitbull, Scarface and a whale walk into a bookHere's what you have wrong about teen moms Check us out on Instagram @cbcbooks and TikTok @cbcbooks

February was my highest revenue month ever—not because I did more, but because I did less. My mentor Nic taught me a framework called the Four Lenses. Every activity has to answer four questions: Does it make me money? Does it save me time? Does it save me money? Is it a forcing function? The rule: It has to hit at least THREE of the four. If it only hits one or two, don't do it. Free summits that generate $14? One lens. Creating content on my own platform? Four lenses. Same hours, completely different return. Your homework: Pick three activities from last month. Run them through the four lenses. What should you stop doing? What should you do MORE of? Want help clearing your calendar? In Momentum, we run your commitments through the lenses together. $200/month. Link is here Leave a 5-star review if this gave you a new filter.  

「トランプ大統領「戦いは続く」イランとの和解の意思なしと主張　次期指導者選びに介入する意向も」　アメリカのトランプ大統領は7日、イランでの軍事作戦について「イランは和解を望んでいるが、我々は望んでいない」と一方的に主張し、今後も軍事作戦を続ける考えを示しました。アメリカ・トランプ大統領：我々は圧勝している。邪悪な帝国を壊滅させた。戦いはまだ続く。トランプ大統領はイランの海軍と空軍を壊滅させたと自賛し、イランが和解を望んでいるものの、アメリカはその意思はないと主張しました。さらに「イランを戦争に導かない指導者を選びたい」とも述べ、改めてイランの次の指導者選びに介入する意向を示しています。一方、アメリカのワシントン・ポストは7日、NIC（国家情報会議）が「大規模攻撃を行ったとしてもイランの体制転換は難しい」と分析する報告書を、攻撃開始の約1週間前にまとめていたと報じています。報告書は「限定的、または大規模な攻撃を行ったとしても、イランの指導部はハメネイ師の殺害を見越して事前に定めた手順に従って体制を維持するだろう」と結論づけていたということです。イランへの軍事攻撃に対しては、アメリカ各地やヨーロッパで大規模な抗議活動が行われ、停戦を求める声が広がっています。

「イランへの地上部隊派遣「正当な理由がある場合に限る」トランプ大統領は慎重姿勢　小学校攻撃は“米軍による誤爆”と米メディア報じる」　アメリカのトランプ大統領は7日、イランでの軍事作戦について「非常に順調だ」と主張する一方で、地上部隊の派遣には否定的な考えを示しました。トランプ大統領の発言には戦略の「ぶれ」が見え隠れします。アメリカ・トランプ大統領：我々は圧勝している。邪悪な帝国を壊滅させた。戦いはまだ続く。トランプ大統領はイラン軍を壊滅させたと自賛した上で、今後も軍事作戦を続ける考えを示しました。一方で、「躊躇（ちゅうちょ）しない」と言っていた地上部隊の派遣については「正当な理由がある場合に限る」と述べ、慎重な姿勢に転じました。さらにトランプ大統領は、160人以上の女子児童が殺害されたとされるイラン南部・ミナブの小学校への攻撃について、「イランの仕業だ。イランの兵器は精度が悪い」と一方的に主張しました。アメリカメディアは、小学校のすぐそばにはイラン革命防衛隊の関連施設があり、攻撃はアメリカ軍による誤爆だという見方を衛星写真とともに報じています。ワシントン・ポストは7日、NIC（国家情報会議）が「大規模攻撃を行ったとしてもイランの体制転換は難しい」と分析する報告書を攻撃開始の約1週間前にまとめていたと報じました。トランプ大統領が作戦開始前に報告書を目にしたかどうかは不明です。

http://www.mofpodcast.com/http://www.pbnfamily.comhttps://www.facebook.com/matteroffactspodcast/https://www.facebook.com/groups/mofpodcastgroup/https://rumble.com/user/Mofpodcastwww.youtube.com/user/philrabhttps://www.instagram.com/mofpodcasthttps://twitter.com/themofpodcasthttps://www.cypresssurvivalist.org/Support the showMerch at: https://southerngalscrafts.myshopify.com/Shop at Amazon: http://amzn.to/2ora9riPatreon: https://www.patreon.com/mofpodcastPurchase American Insurgent by Phil Rabalais: https://amzn.to/2FvSLMLShop at MantisX: http://www.mantisx.com/ref?id=173*The views and opinions of guests do not reflect the opinions of Phil Rabalais, Andrew Bobo, Nic Emricson, or the Matter of Facts Podcast*Phil and Nic can barely read, are both functional idiots, and make up all of the nonsense they spout off on this show literally off the cuff. The idea of researching any sort of information is the peak of tediousness. But, if you believe in expanding your horizons, give this episode a watch and listen while the MoF boys talk you through various options to add to your own Prepper Library.Prepper Library: https://drive.google.com/drive/folders/1hx_LdX1-mF98YF7QtF2XUlV0KCYmpl__?usp=drive_linkMatter of Facts is now live-streaming our podcast on our YouTube channel, Facebook page, and Rumble at 7:30 PM Central on Thursdays . See the links above, join in the live chat, and see the faces behind the voices. Intro and Outro Music by Phil Rabalais All rights reserved, no commercial or non-commercial use without permission of creator prepper, prep, preparedness, prepared, emergency, survival, survive, self defense, 2nd amendment, 2a, gun rights, constitution, individual rights, train like you fight, firearms training, medical training, matter of facts podcast, mof podcast, reloading, handloading, ammo, ammunition, bullets, magazines, ar-15, ak-47, cz 75, cz, cz scorpion, bugout, bugout bag, get home bag, military, tactical 

Notice a theme today? Valentine's Day has NOTHING on Friday, March 6 2026 a day that will forever go down in KISSTORY. Today on the Show, Payton wanted the world's last remaining Sweet Tomatoes for lunch, but at what cost? Then, EVERYBODY is asking 1 final question about Kyle's Disneyland Trip... EASTON and MASCOTS. But first, Payton asks the room about their morning routines, Nic lost a burrito and respect for his Dog Betty Waffle, and an ALL NEW HASH IT OUT! Plus, MINUTE TO WIN IT, The DRUNK DIAL LOUNGE, and THE FUNNIEST EXCUSES TO GET OUT OF WORK and MUCH MUCH MORE today on a KISSY KISSY FRIDAY! And use the talkback feature on the iHeartRadio App to tell us YOUR favorite track on the new Harry Styles Album!See omnystudio.com/listener for privacy information.

Matt and Nic are back for another week of news and deals. In this episode:  What Dario Amodei and SBF have in common Trump wades in to the market structure debate and asks the banks to come to the table Why stablecoins are not like banks Kraken Financial gets a skinny Fed master account Visa and Bridge are rolling out stablecoin-linked cards The FBI arrests a suspect accused of stealing $46m in BTC from the US marshalls Morgan Stanley is coming out with their own Bitcoin ETF The Aave token governance controversy rumbles on Kalshi's traders are upset about their "death market" policy Content mentioned in this episode: The CIV Youtube Channel Alpen Labs, Size Matters: Architecting BTC Credit Markets

You'd expect reaching $5 million or $10 million to feel like a finish line, but for many families, it's where the anxiety actually begins. We spend our entire lives building a savings plan, but when it's finally time to flip the switch, most people realize they never built a spending plan or the internal confidence to actually use what they've earned. In today's conversation, Nic, Randy, and Aaron dig into the strange psychology of wealth and why a rising bank balance isn't always a cure for financial insecurity. Together, we explore how to move past a "thousand-dollar mindset" in a millionaire reality, the critical difference between accumulation and stewardship, and why chasing a financial horizon will never lead to true contentment. If you've ever felt like the more you have, the more you have to lose, this conversation is for you. ⸻ ⏱️ Episode Highlights [01:17] – Why anxiety often rises alongside your net worth and the "more to lose" trap. [03:27] – Savings Plan vs. Spending Plan: Why most retirees are missing the second half of the equation. [04:45] – The "Pension Paradox" and how the shift to defined contribution plans killed our retirement confidence. [07:56] – Breaking the "Code of Saving": Why spending can feel like breaking the law for the greatest generation. [10:34] – The Stewardship Test: A simple mental shift to help you manage your own money with more logic and less fear. [14:48] – The Charlie Munger Lesson: Why every successful person needs a "second set of eyeballs" on their life and money. [18:38] – Chasing the Horizon: Why "just a little bit more" is a recipe for perpetual frustration. ⸻ Links & Resources Mentioned • Email: connect@yourretirementcoach.com  • Website: www.yourretirementcoach.com ⸻ Closing Thoughts If today's episode resonated with you, please like, follow, share, and drop a comment. This will help us reach more people who are ready to stop accumulating in fear and start living with confidence. A healthy retirement isn't just about what's in the account. It's about building the mindset and the plan, actually, to spend it well. Thanks for filling your cup with us today. Stay coachable! ________________________________ Disclaimer: Yeomans Consulting Group, Inc. is a registered investment adviser. Information presented is for educational purposes only and does not intend to make an offer or solicitation for the sale or purchase of any specific securities, investments, or investment strategies. Investments involve risk and, unless otherwise stated, are not guaranteed. Be sure to first consult with a qualified financial adviser and/or tax professional before implementing any strategy discussed herein. Past performance is not indicative of future performance.  

Dans cet épisode passionnant des Grands dossiers de l'Histoire, le talentueux Franck Ferrand nous plonge dans les origines de la photographie.

Within the Vonindod, the party finds themselves in trouble...______________________________________________________________________________________________________________Imagine your best game of D&D. The shocks, the twists and turns, the moments that can't be caught because you just had to be there. That's Dice Shame.Join our DM Jo, her husband Harlan, their brother Alex & their friends Nic & Timm as they experience those unmissable, gut-wrenching, heart-aching, joy-filled moments.This legendary AP releases a brand new episode every Thursday morning at 1:20 am!Content Warning: animal death, swearing, violence, claustrophobia Hosted on Acast. See acast.com/privacy for more information.

Send a textThis week, we've got enough chaos for a Netflix documentary! The True Comedy guys tackle another wild fill-in-the-blank episode. It starts weird, gets dumber, becomes chaotic, turns criminal, and ends completely unhinged. How is Nic going to handle the chaos? Will Kirstan turn the crimes into comedy? Will Nic answer a single question right? Take your best guess and laugh with your favorite podcast hosts. Hosted by Nicholas Finch & Kirstan Cunningham New Episodes every Thursday!! Please subscribe, rate, and review! Listen on Apple Podcasts, Spotify, Google Podcasts, or wherever you listen to podcasts! Head to truecomedypod.com for all things True Comedy! Follow us on social media! Facebook: facebook.com/truecomedypodcast Instagram: instagram.com/truecomedypodcast Twitter: twitter.com/podcast_true

Everyone thinks they're diversified... Until the market proves otherwise. In this podcast episode, Nic Daniels breaks down what diversification really means and why so many investors get it wrong. After years of strong market performance, it's easy to feel confident owning growth-heavy portfolios, tech ETFs, or even multiple S&P 500 funds. But are you truly diversified, or just concentrated in disguise? Nic walks through real-world examples of "fake diversification," including overlapping mega-cap exposure, tech-heavy ETF combinations, U.S.-only portfolios, and the hidden risks inside high-yield income investments. He explains why bull markets mask concentration risk and how volatility quickly exposes it. Most importantly, he outlines practical, tax-aware ways to gradually rebalance and build a portfolio designed not just to grow wealth — but to protect it. Diversification isn't about today's gains, it's about making sure one market shift doesn't rewrite your retirement.   Take Our BetterBuckets™ Assessment https://www.therealmoneypros.com ————————————————————— Ataraxis PEO https://ataraxispeo.com Tree City Advisors of Apollon: https://www.treecityadvisors.com Apollon Wealth Management: https://apollonwealthmanagement.com/ —————————————————————

Co my wiemy o ciśnieniu? Nic albo prawie nic. Lubimy, kiedy ciśnienie rośnie, bo to znaczy, że życie nie jest nudne, wiemy, że na niskie ciśnienie dobra jest kawa, najlepiej w dobrym towarzystwie, domyślamy się, że wielkie ciśnienie jest zabójcze. To znaczy, że złota zasada środka i w tej materii obowiązuje. Czy to jest słuszne przypuszczenie okaże podczas kolejnego wykładu w Szkole Bardzo Wieczorowej. Może się też okazać, że wiedza o ciśnieniu ratuje życie. Do słuchania zaprasza Beata Tomanek i jej goście: prof. Władysław Borgieł oraz prof. Armand Cholewka.

Stooping to a NEW level of KAREN-RY Today on Johnjay and Rich! STREAM NOW to find out what happens when TWO NEIGHBORS FEUD. Also, an UPDATE from FRANK! This has been a nail biter! Then, Johnjay's dog poop hack, or lack therefore of. Plus, 2 GAMES TODAY! Nic and Payton go head to head as per usual. All of this and MUCH MORE!See omnystudio.com/listener for privacy information.

In this episode Ben Pearce and Nic Neate discuss what it's really like to build and be part of an AI native engineering team. Nic shares his experiences and insights on how AI is fundamentally changing the way software is developed, the skills required for engineers in this new landscape, and the challenges organizations face in adapting to these changes. Nic Neate is the CTO of @Nimbus. He has many years working in the software world and previously worked at Metaswitch and Microsoft. Show Links Ben Pearce LinkedIn - https://www.linkedin.com/in/benpthoughts/ Tech World Human Skills Home - https://www.techworldhumanskills.com Nic Neate Linked In - https://www.linkedin.com/in/nic-neate-b3515210/ Nimbus - https://www.nimbusmaps.co.uk/ Takeaways AI is fundamentally changing software engineering. Vibe coding is using AI to write code. AI native means riding the wave of AI tooling. Being AI native enables you to do so much more. AI can do it in 10 minutes what you could do in a week. Context engineering is a key skill for engineers. Decision making is crucial in an AI native world. You need to invest in your tool chain. Recruitment processes need to change for AI roles. Maximize value for people working in AI. Keywords AI native engineering, software development, generative AI, engineering teams, AI tools, context engineering, software productivity, AI integration, engineering leadership, tech transformation

Big J has some interesting brand collab ideas for the show. Nic is all geeked up about Spring cleaning, no really!See omnystudio.com/listener for privacy information.

This week, I sat down with Nic de Angelo to unpack one of the biggest financial shifts of our lifetime: the Greatest Wealth Transfer.Over the next 15 years, we'll witness the largest transfer of wealth in human history, and the implications are massive.

Today on Joe Oltmann Untamed, we're unraveling the escalating war with Iran, Operation Epic Fury is live, and the stakes couldn't be higher. Trump's strikes have taken out key nuclear targets, but Iran hit back hard, killing four U.S. service members and wounding dozens more in attacks on bases in Kuwait and beyond. We're unpacking the real-time chaos: Saudi Aramco reportedly hit by kamikaze drones, the Strait of Hormuz closed, U.S. carrier Abraham Lincoln taking missile fire, and allies like Spain and the UK refusing to let us use their bases for offensive ops. This isn't a skirmish, it's a full-on conflict with massive energy and global fallout.I'm sitting down with Sergeant Nic Phelps, a medically retired USAF veteran who flew MQ-1 Predators, ran interrogations in Iraq, helped rewrite the Army's field manual, and worked closely with General Petraeus. Nic brings razor-sharp insight from the front lines of drone ops and HUMINT to break down Iran's proxy playbook, drone swarm threats, gaps in our ISR, and what happens if we keep hammering IRGC and nuclear sites. We're asking the tough questions: Are we exploiting captured operatives enough? Are we too kinetic and not enough on financial/logistical disruption? And how do we honor the fallen without spiraling into a wider war?This episode is a gut-punch reality check. Four American heroes lost this week, Iran refusing to back down, and the world watching to see if we have the resolve to finish what we started. From battlefield tactics to the human cost, we're laying it all out with no filter. Tune in for the unvarnished truth from a combat vet who's been there because this fight is here, it's now, and it's not over. You won't want to miss it.

It's a HOT TOPIC in Today's SECOND DATE UPDATE! Today on the Show, KYLE RETURNS FROM DISNEYLAND and JOHNJAY SHOWED UP?!? Then, Johnjay has END OF THE WORLD Shock Trivia because of a show he is watching. Also, WE ARE WORKING ON GETTING AN UPDATE FROM FRANK AND THE SOUTH KOREAN AI CHAT LADY!!! Plus, Nic's BEER game, Minute To Win It, and MORE!See omnystudio.com/listener for privacy information.

While Saving Elephants is dedicated to offering the conservative intellectual tradition in mercifully modern vernacular, fellow podcaster Nic Dunn has been on a similar mission: making the work of policy institutions more digestible.  Nic joins Josh for a conversation around the important role policy can play in defusing political tension, alleviating poverty, and expanding the freedom and opportunities all Americans seek.   About Nic Dunn Bio from Sutherland Institute   Nic Dunn serves as Vice President of Strategy and Senior Fellow at Sutherland Institute. As VP of Strategy, Nic oversees the execution and strategic external impact of Sutherland's written and multimedia policy content. In his capacity as Senior Fellow, he leads the policy research, coalition building, and public advocacy for policies that strengthen opportunity and upward mobility. This policy focus includes social safety net reform, workforce issues, and support for the well-being of men and boys. His expert commentary and analysis can be found on Sutherland's weekly podcast, Defending Ideas, which he hosts, as well as in major outlets like Deseret News, Washington Examiner, National Review, and other Utah print and radio outlets.   Nic brings more than 13 years of experience in public policy and strategic communications spanning state and local government and the private sector. Prior to Sutherland, Nic served as director of Utah Community Builders, the Salt Lake Chamber's nonprofit social impact foundation. In that role, Nic worked with the private sector to advance statewide initiatives in mental health, family policy, and upward mobility. Nic is also a member of the AEI Leadership Network, and the co-chair of the Salt Lake County Intergenerational Poverty Task Force.   In other previous work, Nic ran public policy for the Utah Valley Chamber, served as senior policy advisor to Salt Lake County Councilwoman Aimee Winder Newton, directed media relations for the Utah Department of Workforce Services, and worked on Gov. Gary Herbert's communications staff as lead speechwriter.   Nic has a master's degree in public policy from the University of Utah and dual bachelor's degrees in broadcast journalism and political science from the University of Nevada, Reno. Nic and his wife, Lizzie, live in Eagle Mountain with their two sons.   Introducing Conservative Cagematches Ever since Leo Strauss published his magnum opus Natural Right and History, which ends by heavily implying Edmund Burke opened the door for the evils of historicism in the modern world, a great fissure in conservative nerddom erupted between those who align with either titan.   Were Strauss' criticism of Burke warranted? Did Burke disavow natural rights and pave the way for the evils of authoritarianism, fascism, Marxism, and progressivism to come? Does a careful, esoteric reading of Natural Right and History reveal the Strauss secret family chili recipe?   On Wednesday, March 4 at 6PM EST / 5PM CST, Saving Elephants will assemble an all-star panel to answer these questions and more.   Representing Edmund Burke: Greg Collins of Yale University and Lauren Hall of the Rochester Institute of Technology   Representing Leo Strauss: Steve Hayward of Pepperdine and the international woman of mystery, Lucretia of the University of Arizona   You can watch the livestream on YouTube or Facebook  

Nic judged a grade school speech competition and had to tell a couple of kids, “No snacks for you.” He enjoyed it because he got to exercise one of his spiritual gifts: judging people. Tarina also points out that Nic is hard to make toast for.The idea of this episode is to build the profile of your ideal week. If you don't have a profile and life just happens. It's better to be intentional. What Nic and Tarina found out that life fills up spaces not blocked off. Your schedule reflects what you care about, says Tarina. Whether it's vacation, work, relaxation, or a workout—it's important to have it scheduled.Nic says it's important to ask the question, “What do I want?” Then says we have to ask, “What am I willing to do to get it?” This helps identify our priorities and our non-negotiables.If you don't put what's most important to you on your calendar, someone will be happy to fill your calendar for you. If you enjoy Nic and Tarina's podcast and get something from listening to “all this Nic Bittle Crap,” please hit the like button, share it with a friend, or both. Your recommendation goes a long way in helping us reach more people.Also if you have questions that you want Nic and Tarina to answer, email them at info@nicbittle.com. ---

This week Kat and Nic talk about menopause! GASP! Don't worry, it's not as scary as you think! Hot flashes, mood swings, brain fog, sleep that vanishes at 2 a.m.—menopause isn't “just a phase,” it's a full-body plot twist. We'll break down what's happening, the symptoms nobody warned you about, what can actually help, and how to advocate for yourself without being dismissed.No shame, no fluff—just honest talk and practical takeaways for the season of change.-----------Being a working mom is the craziest, most amazing, powerful, frustrating, and loving experience you will ever have in your entire life. The Working Mommy's Manual podcast, hosted by Nicole Corning & Kathleen Wilson.-----------Tune in for new episodes every other Tuesday!-----------CONNECT WITH US ELSEWHERE:• TikTok: @workingmommysmanualpod• Instagram: @workingmommypodcast• YouTube: @TheWorkingMommysManual• LinkTree: linktr.ee/WorkingMommyManual• Website: theworkingmommysmanual.com• Email: workingmommypod@gmail.com

"Your Customers Aren't as Loyal as You Think They Are - The Fragile Nature of Loyalty"A CMO Confidential Interview with Nicolas Chidiac, Chief Strategy Officer of Razorfish, formerly Chief Strategy Officer of Rokkan and EVP/Head of Planning at Leo Burnett. Nic discusses why brands often overestimate consumer loyalty, why repeat purchase trends can be misleading, and the dramatic increase in speed and velocity of competition. Key discussion topics include: why it has never been easier to try a new product; how influencers have "democratized celebrity endorsement;" why marketers should focus on "removing relative friction;" and how to measure your loyalty deficit. Tune in to hear stories about White Lotus, Chewy, Dubai Chocolate and Pop Tarts. Your customers aren't as loyal as you think. Razorfish Chief Strategy Officer Nic Chidiac joins Mike Linton to unpack groundbreaking research revealing the fragile nature of brand loyalty — and why most marketers are dangerously overconfident about it.65% of marketers believe repeat buyers stay out of emotional connection to their brand. Only 15-17% of consumers agree. That gap is costing companies billions. Nic breaks down the loyalty deficit, why switching has never been easier, and what confident marketers should actually be measuring.Whether you're defending a market-leading brand or building a challenger, this episode will change how you think about loyalty programs, customer retention, and the metrics you're relying on.

Nejbohatší Češi se do tuzemských investic nijak zvlášť nehrnou a nezmění to ani nová vládní hospodářská strategie. Říkají v novém díle pořadu Nic osobního, prostě byznys hlavní ekonomická analytička Českého rozhlasu Jana Klímová a publicista Petr Šimůnek. Potvrzují to podle nich i nedávno ohlášené zahraniční investice Pavla Tykače nebo Daniela Křetínského. Právě na jeho impérium a především poslední investice se podívali podrobněji.

Hey well read baddies! We're back with another bonus episode, and this one is for the girls who are fans of Gone Girl and are impatiently waiting for season three of P-Valley to drop. We're joined by New York Times bestselling author Nic Stone to talk about her latest release, Boom Town. We get into what it was like for Nic to step into adult fiction after writing dozens of YA books (many of which have been challenged and banned), why she wanted to expand the thriller genre to include characters we can actually relate to and root for, and the real-world conversations the book taps into, from missing persons cases involving Black women to power, privilege, and who society decides is “worthy” of concern. We also revisit the Dear Martin series and talk book bans, censorship, and what it feels like when your work becomes both celebrated and targeted. Tap in, then leave us a voice note with your reaction to the episode and your favorite moment :) Learn more about Nic and her work here and the next book on her tbr here We can't wait to hear from you! :) Please send any questions or comments about this episode to shewellread@gmail.com OR leave us a Voice Note at https://www.speakpipe.com/shewellread‬ Follow SHE WELL READ! Instagram: https://www.instagram.com/shewellread/ TikTok: https://vm.tiktok.com/ZMeDCLdTX/ Threads: https://www.threads.net/@shewellread Substack- https://substack.com/@shewellread Bookum- https://app.bookumapp.com/clubs/668ad565858c97a7faafafb1 Bookshop Storefront- https://bookshop.org/shop/shewellread More links including discount codes: https://bio.site/shewellread Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode, Nic explores the profound purpose behind salvation and guides new believers on their spiritual journey after obeying the gospel. Discover how God's intentional plan, your new identity, and ongoing growth shape your walk with Christ.Please support: https://www.paypal.com/donate/?hosted_button_id=7RQYM5XD6U6CJSocial Media/Follow Us:Website:https://www.calledbygodpodcast.com/IG: https://www.instagram.com/cbg.podcast/Twitter: https://twitter.com/CalledbyGodPodTikTok: https://www.tiktok.com/@calledbygodpodcast

What if you could build your own streaming service from scratch? On this episode of The Nerdiest Podcast, we hold a fantasy draft where each of us creates our own streaming platform. We draft movies, TV shows, franchises, and exclusives to see who can build the ultimate streaming service. Would you subscribe to ours? Or would you cancel immediately?❯ Follow Us on the Internet:https://linktr.ee/thenerdiestpodcast❯ Merch:https://thenerdiestpodcast.com❯ YouTube:The Nerdiest Podcast - https://www.youtube.com/@thenerdiestpodcastNic With No ‘K' - https://www.youtube.com/@nicwithnokThe Glas Studios - https://www.youtube.com/@TheGlasStudios❯ Twitter:The Nerdiest Podcast - https://twitter.com/NerdiestPodNic - https://twitter.com/NerdiestNicJackson - https://twitter.com/GlasStudios❯ Instagram:The Nerdiest Podcast - https://www.instagram.com/thenerdiestpodcast/Nic - https://www.instagram.com/nic._.barrett/Jackson - https://www.instagram.com/theglasstudios_/

Content Advisory: As we explore Jesus' teaching on anger, lust, and divorce, some mature themes are discussed. Parents are encouraged to use discretion with younger viewers. Our lead pastor Nic brought a timely message from Matthew 5:21-23. Let's dig into the Word and learn about how to guarding ourselves against a mad world. 18:07 The Message begins   Want to know more? Weekly teaching notes and discussion questions are available on the website link below for this message and others in this series. https://www.goodlife.org.au/kingskingdom-series ---

And now for something completely different... Hilary and Nic celebrate the 20th Anniversary of Iron Man: The Animated Series.

Today on the Show, an Upside Down PIZZA ruined someone's night, Payton tells us about her unfortunate driving habits, Johnjay's live photos led him down a path of confusion, and MORE! Also, CARDI B-EAT SHAZAM courtesy of Nic and REVERSE THE VERSE for NEW MUSIC FRIDAY BRUNO MARS! Plus, JAKE MISPOKE so we asked you about your BRAIN STUCK TONGUE STUCK MISPOKE moments.See omnystudio.com/listener for privacy information.

Matt and Nic are back with another week of news and deals. In this episode:  Kalshi has detected and banned two accounts for insider trading Is Polymarket going to have to add KYC? Is there a tradeoff between informational efficiency and market fairness The OCC de facto bans stablecoin yield in its rulemaking around GENIUS Meta is considering partnering with a stablecoin issuer Stripe is bullish in their annual report ZachXBT determines that Axiom employees have been abusing the platform Terraform labs accuses Jane Street of insider trading WSJ reports that Binance overlooked Iranian sanctions violations Justin Drake unveils a post-quantum roadmap for Ethereum Matt Corallo says Nic is wrong about Bitcoin and quantum Content mentioned: Larry Cermak: How Crypto Actually Works: The Missing Manual  

Gearóidín Nic an Iomaire.

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

As the party takes to the sky it's time to see what makes the Vonindod soar...______________________________________________________________________________________________________________Imagine your best game of D&D. The shocks, the twists and turns, the moments that can't be caught because you just had to be there. That's Dice Shame.Join our DM Jo, her husband Harlan, their brother Alex & their friends Nic & Timm as they experience those unmissable, gut-wrenching, heart-aching, joy-filled moments.This legendary AP releases a brand new episode every Thursday morning at 1:20 am!Content Warning: animal death, swearing, violence, claustrophobia Hosted on Acast. See acast.com/privacy for more information.

Send a textHow are the True Comedy guys celebrating 100 years of Black History? Playing a dangerous game of Black, White, or Other! Nic brings the confidence, and Kirstan is dropping real Black history facts throughout the episode — the ones that don't always make it into textbooks. You will laugh, you'll learn, and sometimes you will guess extremely wrong. Hosted by Nicholas Finch & Kirstan Cunningham New Episodes every Thursday!! Please subscribe, rate, and review! Listen on Apple Podcasts, Spotify, Google Podcasts, or wherever you listen to podcasts! Head to truecomedypod.com for all things True Comedy! Follow us on social media! Facebook: facebook.com/truecomedypodcast Instagram: instagram.com/truecomedypodcast Twitter: twitter.com/podcast_true

Gearóidín Nic an Iomaire.  

In this AMA episode, Pastor Nic tackles a wide range of listener questions — from Brené Brown's framework on shame and guilt, to the moral implications of generative AI. Rather than offering easy answers, Nic consistently pushes listeners to think more carefully and resist reductive thinking. The episode features several explanations of some controversial Psalms, inviting listeners to wrestle honestly with what those passages meant in their original context and why it still matters today.   Engage & Equip is a resource designed to help form substantive disciples for the local church. Find more episodes at highpointchurch.org/podcast Music: HOME—We're Finally Landing, Nosebleed, If I'm Wrong (https://midwestcollective.bandcamp.com/album/before-the-night) Engage & Equip is a resource designed to help form substantive disciples for the local church.Find more episodes at highpointchurch.org/podcastMusic: HOME—We're Finally Landing, Nosebleed, If I'm Wrong (https://midwestcollective.bandcamp.com/album/before-the-night)

Time management is the theme of today's show! First, Kyle and her squad are LATE/On time depending on the day for their sports teams and FISH is PISSED! Fashionably late works in some places but not all. Then, an ALL NEW SECOND DATE UPDATE where she was TOOTIN ALL OVER THE DAMN GUY. After that, the suspense was so strong as we reached a ninth going on tenth question rewriting MINUTE TO WIN IT HISTORY today. Plus, not one but TWO tricky Nic-y games and SO MUCH MORE in an EXTENDED EPISODE of JOHNJAY AND RICHSee omnystudio.com/listener for privacy information.

Nic received two packages—and on a Saturday of all days. Tarina says she never gets packages on Saturdays. One of them is a new “sock cap” for Nic's bald head because it's still cold in Oklahoma. The most important proof of leadership is Ownership. This is the fifth and final proof. When you make a mistake do you “own it” or do you make excuses? We all struggle with admitting when we mess up, especially when holding a leadership position. For some, there's an explanation for everything. When things go wrong, these folks don't take responsibility and avoid accountability. The work of “owning it” takes development (see Proof #4). This applies whether it is in the rearing of kids or raising up future leaders at your organization. Ownership is fundamental to building trust as a leader and in modeling (see Proof #3) for potential leaders how to build trust.Mistakes are not the problem—perfection isn't the goal. Performance issues often are fixable. When someone justifies their actions or makes excuses, this is an integrity issue. When we bend the truth we risk breaking trust. If you enjoy Nic and Tarina's podcast and get something from listening to “all this Nic Bittle Crap,” please hit the like button, share it with a friend, or both. Your recommendation goes a long way in helping us reach more people.Also if you have questions that you want Nic and Tarina to answer, email them at info@nicbittle.com. ---

As London craft-and-design fair Collect gets under way, Nic Monisse chats with director TF Chan about the philosophy of “fewer, better things”. Plus: buttons and handles are coming back to our vehicles but will Nic and Grace Charlton give them the green light? See omnystudio.com/listener for privacy information.

Jason, Deacon Jon, and Nic explore the messy intersections of Gnostic discourse and the 2026 digital landscape, where the “demiurgic” […]

It's Monday, February 23rd, A.D. 2026. This is The Worldview in 5 Minutes heard on 140 radio stations and at www.TheWorldview.com.  I'm Adam McManus. (Adam@TheWorldview.com) By Adam McManus Utah teacher forces student to wash off Ash Wednesday cross A Utah elementary school faced backlash after a teacher told a Catholic student to remove an Ash Wednesday cross from his forehead, a symbol marking the beginning of Lent, reports WHSV TV. Fourth-grader William McLeod had attended church on Ash Wednesday and arrived at Valley View Elementary School in Bountiful, Utah wearing a traditional ash cross.  He said classmates initially questioned him about it, unaware that the ash cross marked the beginning of Jesus' 40 days in the wilderness before the beginning of His three-year ministry. The boy recalled his teacher asking, “What is that?” He replied, “It's Ash Wednesday. It's the first day of Lent.” She said, “No, it's inappropriate. Go take it off.” In front of his peers, she gave the child a wipe and told him to clean his forehead. McLeod said, “I felt really bad.” His grandmother said he was embarrassed and upset, saying he later went to see the school psychologist “crying.” The Davis School District issued a formal apology, saying the teacher's actions were unacceptable. A spokesman said, “No student should ever be asked or required to remove an ash cross from his or her forehead.” The teacher later apologized. Supreme Court ruled 6-3 against Trump tariffs On Friday, the Supreme Court ruled 6-3 against President Donald Trump's sweeping global tariffs, striking down a central part of his economic agenda, reports The Western Journal. TRUMP: “The Supreme Court's ruling on tariffs is deeply disappointing. I'm ashamed of certain members of the court, absolutely ashamed, for not having the courage to do what's right for our country.” The case focused on tariffs President Trump imposed under a 1977 emergency powers law known as the International Emergency Economic Powers Act. He used that law to impose reciprocal tariffs on most countries beginning last year. Chief Justice John Roberts wrote for the majority that the International Emergency Economic Powers Act “does not authorize the President to impose tariffs.” Associate Justice Amy Barrett and Neil Gorsuch sided with Roberts and the court's three liberals. However, Samuel Alito, Clarence Thomas, and Brett Kavanaugh dissented, reports the Associated Press. President Trump imposes new tariff using different authority On Truth Social, President Trump wrote, “I would like to thank and congratulate Justices Thomas, Alito, and Kavanaugh for your strength, wisdom, and love of our country, which is right now very proud of you. “When you read the dissenting opinions, there is no way that anyone can argue against them. Foreign Countries that have been ripping us off for years are ecstatic, and dancing in the streets — But they won't be dancing for long!” Kavanaugh wrote, “The decision might not substantially constrain a President's ability to order tariffs going forward. That is because numerous other federal statutes authorize the President to impose tariffs and might justify most (if not all) of the tariffs issued in this case. ... Those statutes include, for example, the Trade Expansion Act of 1962 (Section 232); the Trade Act of 1974 (Sections 122, 201, and 301); and the Tariff Act of 1930 (Section 338).” TRUMP:  “Other alternatives will now be used to replace the ones that the court incorrectly rejected. Great alternatives. Could be more money. We'll take in more money.” Inspired by Judge Brett Kavanaugh's dissent, President Trump imposed a new 10% global tariff the same day of the Supreme Court decision last Friday, using Section 122 of the Trade Act of 1974, reports NewsNation. GOP Rep. Tony Gonzales had affair with aide who set herself on fire U.S. Republican Congressman Tony Gonzales of Texas engaged in a romantic relationship with an aide who died last year by setting herself on fire outside her Uvalde home, according to a text message and people close to the aide and her family, reports the San Antonio Express-News. Both she and Gonzales were married to other people at the time of the alleged affair. A former staffer in Gonzales' district office, who worked closely with the aide, Regina Ann Santos-Aviles, said she told him they had an affair in 2024, and that she spiraled into a depression after her husband discovered the relationship and Gonzales abruptly ended their affair. Exodus 20:14 says, “You shall not commit adultery.” He also shared with the San Antonio Express-News a screenshot of a text message from Regina in which she acknowledged having an “affair with our boss.” The staffer, who asked not to be named, citing a fear of retaliation, faulted Gonzales' office for failing to intervene, saying he warned the congressman's district director months before Regina's fiery suicide that he was concerned about her well-being. He described her as his “best friend” and said their families knew each other. Gonzales, a Republican representing Texas' 23rd Congressional District, is currently seeking re-election in a contested primary.  The San Antonio Express-News, which had initially endorsed Gonzales in the March 3rd Republican primary, recently withdrew its endorsement. In the Republican Primary for Congress in District 23, many South Texans are looking to support Francisco “Quico” Canseco during early voting or on Election Day, Tuesday, March 3rd. Texas bobsled gold medalist almost quit And finally, (audio of Olympics theme song) It was a couple of weeks before Christmas. Elana Meyers Taylor, age 41, was in Norway, prepping for a World Cup bobsled weekend. Things were going horribly. Her body was hurting, she wondered if she was doing right by her two deaf children, and the racing results were, well, bad, reports the San Antonio Express-News. So, she texted her husband. The message: I'm done.  She wrote, “This is just impossible. It's never going to work.” She was 10th in the World Cup monobob standings. Eight women won medals on the circuit this winter and she wasn't one of them. Her average finish was 10th and her result during a race on the Olympic track in November was 19th — a whopping 2.43 seconds behind the winning time. FEMALE ANNOUNCER: “She had probably her worst season of monobob in her life.” Her husband, former bobsledder Nic Taylor, is now a performance coach and works with the NBA's San Antonio Spurs. When a Spurs player — the couple won't say who — learned Elana was struggling, he gifted Nic a plane ticket and told him, “Go to Norway immediately!” So, Nic flew to Norway to encourage his wife in person after those discouraging texts to talk her out of quitting.  That strengthened Elana's resolve to compete. Listen to the Olympics announcer during Elana's bobsled run. MALE ANNOUNCER: “Elana Myers Taylor has this magical moment to win another Olympic medal and potentially gold. Her husband Nick and sons, Noah and Nico, are here in the crowd. “This is a promising run for Elana Myers Taylor. Sixteen-hundredths of a second ahead of Kaillie Humphries, 12-hundredths of a second ahead. Elana Myers Taylor has never won a gold medal at the Olympics. She has now. It's gold for the United States, and that elusive gold medal for Eleanor Myers Taylor, is elusive no more. The most prolific female bobsledder in history.” At 41, she became the oldest woman to win an individual gold medal in Winter Games history. It was her sixth Olympic medal. She said, “I was determined to keep fighting, determined to just put down the best runs I could. And look what happened. There were so many moments during this entire season, during this past four years, that I thought it wasn't possible.” And now you know the rest of the story. In 1 Corinthians 9:24, the Apostle Paul asked, “Do you not know that in a race all the runners run, but only one gets the prize? Run in such a way as to get the prize.” Or, in Elana Meyers Taylor's case, slide in such a way as to get the prize. Close And that's The Worldview on this Monday, February 23rd, in the year of our Lord 2026. Follow us on X or subscribe for free by Spotify, Amazon Music, or by iTunes or email to our unique Christian newscast at www.TheWorldview.com.  Plus, you can get the Generations app through Google Play or The App Store. I'm Adam McManus (Adam@TheWorldview.com).  And now, to close the newscast, here's my son, Valor Tyndale, who just turned 11 on Saturday. VALOR: “Seize the day for Jesus Christ.”

Jeremiah and Nic start with a volatile week in the markets following the Supreme Court's decision to strike down President Trump's tariff authority and the market's surprisingly calm reaction. They explain why uncertainty, not bad news itself, drives volatility and how diversified portfolios, including small caps, value stocks, and international exposure, help investors stay resilient when headlines shift. The conversation then turns to one of the most overlooked areas of financial planning: estate planning and account titling. They walk through the differences between wills and trusts, why wills do not avoid probate, and how simple steps like beneficiary audits, TOD and POD designations, and proper account ownership can prevent costly delays and family conflict. They also discuss whether trusts should be named as beneficiaries on IRAs, how inheritance rules differ for individuals versus trusts, and when simplicity is often the best strategy. Rounding out the show, the duo covers tax-season pitfalls, including corrected 1099s, K-1 delays, Roth conversions, backdoor Roth mistakes, and why rushing to file taxes can create unnecessary problems.   Listen, Watch, Subscribe, Ask! https://www.therealmoneypros.com Hosts: Jeremiah Bates & Nic Daniels ————————————————————— Ataraxis PEO https://ataraxispeo.com Tree City Advisors of Apollon: https://www.treecityadvisors.com Apollon Wealth Management: https://apollonwealthmanagement.com/ —————————————————————

Welcome to our FINAL PLAYOFF episode where our hosts Nic, Gabe, and Ally  and special guest Ash listen to Pitchforks top songs of the 1990's! Tune in to hear the hosts listen and debate which are the best of the best and see who will get voted as the best song of the 1990's! To get a behind the scenes look and updates on the show follow our instagram @mixedinthemaking. By following us on instagram you can also submit songs you love in the topics we cover in future episodes. If you would like to join our Discord to discuss the episodes, share music/drink recipes, join our album club and much more, you can do so through this link tap here. Enjoy the show! Theme song by Blaix Logo artwork by Black Sea Foam

https://www.gofundme.com/f/mishawaka-wrestling-modernization-plan White boy of the year Veteran With A Sign is here and Nic's back to tell us what he's been working on! Watch this episode ad-free and uncensored on Pepperbox! https://www.pepperbox.tv/ WATCH THE AFTERSHOW & BTS ON PATREON! https://www.patreon.com/UnsubscribePodcast

Imagine dating Nic and HATING Disney or dating Noah and DESPISING TAYLOR SWIFT? We all have a little bias! HAPPY FRIDAY, today we talk Ultimatums, the GOLD MEDAL of BAD BOYFRIENDS, another FAILED WAR OF THE ROSES FLUB from our JJR VAULT, an unexpected URN AND ASHES PLOT TWIST... and more!See omnystudio.com/listener for privacy information.

Matt and Nic are back with another week of news and deals. In this episode:  Crypto VC funds have some dry powder CFTC chair Mike Selig asserts jurisdiction over prediction markets relative to the States Is Kalshi more reliable than interest rate futures? The CLARITY Act inches closer to passing Shake up at Gemini OpenClaw agents are going to start phishing crypto users Bitwise aims to launch prediction market ETFs Bridge gets their OCC charter Hyperliquid launches a lobbying arm DAT hangover continues Blockfills reveals a $75m hole Ethereum is having an identity crisis Base is moving away from Optimism Neel Kashkari's bad faith stablecoin criticism

The draft starts in Mobile

As the team boards the Vonindod... the stakes get higher...______________________________________________________________________________________________________________Imagine your best game of D&D. The shocks, the twists and turns, the moments that can't be caught because you just had to be there. That's Dice Shame.Join our DM Jo, her husband Harlan, their brother Alex & their friends Nic & Timm as they experience those unmissable, gut-wrenching, heart-aching, joy-filled moments.This legendary AP releases a brand new episode every Thursday morning at 1:20 am!Content Warning: animal death, swearing, violence, claustrophobia Hosted on Acast. See acast.com/privacy for more information.

Send a textFrom chaotic headlines to unhinged hot takes… we made it to TWO HUNDRED. 200 episodes of questionable opinions, chaotic headlines, side-eye commentary, and at least 47 moments where we probably should've been canceled. And we're celebrating the only way we know how — with lists. Aggressive, opinionated, absolutely debatable lists. Nic is counting down his Top 10 Side Hustles (some legal, some… creative and Kirstan is counting down his Top 10 Little-Known Black Facts (education system who?). Hosted by Nicholas Finch & Kirstan Cunningham New Episodes every Thursday!! Please subscribe, rate, and review! Listen on Apple Podcasts, Spotify, Google Podcasts, or wherever you listen to podcasts! Head to truecomedypod.com for all things True Comedy! Follow us on social media! Facebook: facebook.com/truecomedypodcast Instagram: instagram.com/truecomedypodcast Twitter: twitter.com/podcast_true