Podcasts about principles

14. Guest Peter Berkowitz outlines reforms for the Department of Defense, including cutting bureaucratic red tape and encouraging technological competition. He stresses the importance of higher education in teaching the free-market principles necessary for national security.,, (15)1943

I love cupping coffee. It is a great way to assess a coffee and learn how to identify defects, attributes, and nuances that allow you to make decisions about buying coffee and how to maintain consistency in roasting. But the issue we have in a lot of coffee is that cupping, a practice designed for the above scenarios, has been miss used in the front of house customer facing world of retail.  Today on Shift Break we will be talking about cupping's place in coffee quality control and what we should be doing instead of cupping to better manage the quality of our coffee and more clearly communicate a coffee's attributes to customers.    APPLICATIONS ARE OPEN!  KEY HOLDER COACHING GROUPS  Are you a coffee shop owner looking to join a community of other owners to help bring perspective, insight, encouragement, and accountability in a well curated setting?  Then you need to apply to join Key holder Coaching Groups!  Applications are now open for Spring 2026 Cohort: APPLY TO KEY HOLDER COACHING GROUPS   KEYS TO THE SHOP®  1:1 CONSULTING AND COACHING If you are a cafe owner and want to work one on one with me to bring your shop to its next level and help bring you joy and freedom in the process then email  chris@keystothshop.com of book a free call now:  https://calendly.com/chrisdeferio/30min    Related Episodes:    586: How to Dial In Your Cafe   SHIFT BREAK! How to Think About Quality 533: Principles of Quality Control 406 : Five Ways to Immediately Improve Your Coffee Quality

How do you earn the loyalty that supports real influence? You won't change lives or amplify your results without the ability to connect authentically. In this week's episode, John Maxwell is sharing how to do that, as he teaches the five essential qualities that define an authentic leader!  After his lesson, Mark Cole and Chris Robinson provide practical strategies you can use right away to embody authenticity and deepen your impact as a leader.  Key takeaways:  Leading with heart—through empathy, courage, and genuine care—creates meaningful connections that drive lasting results. Consistently practicing transparency, humility, and good listening skills builds trust and invites collaboration. "People will walk through fire for a leader that's true and a leader that's human." — Pat Lencioni Our BONUS resource for this episode is the Qualities of an Authentic Leader Worksheet, which includes fill-in-the-blank notes from John's teaching. You can download the worksheet by visiting MaxwellPodcast.com/Authentic and clicking "Download the Bonus Resource."  This episode is sponsored by BELAY:  Leaders, stop trying to do it all yourself. The best leaders know their limits, operate out of their strengths, and set others up for success. Find freedom with BELAY — pairing you with vetted U.S. virtual assistants so you can focus on what matters.  To help you get started, BELAY is offering Maxwell Leadership listeners a free download of their resource, The Leadership Toolkit. Just text MAXWELL to 55123 for FREE access. References:  Watch this episode on YouTube! Get the High Road Leadership online course for 33% off Get 15% off your copy of John's leadership development guide The 21 Indispensable Qualities of a Leader now through 3/31 (use code PODCAST at checkout!) Accelerate your growth with the Maxwell Leadership App (start your 7-day free trial today with code PODCAST7!) Principles that Guide Your Life Podcast Episode 5 Ways to Win With People Podcast Episode Join the Maxwell Leadership Certified Team

In this episode, Andrew Pudewa and Julie Walker discuss the prompts for the annual IEW Writing Contest. Listen to this episode to learn why does IEW have a writing contest, what the value of entering a writing contest is for students, and how a writing contest fits into the types of motivation. Andrew breaks down the prompts and talks about how a writer might approach this essay. Referenced Materials IEW Writing Contest Other Writing Contests “The Benefits of Entering Writing Contests” Principles of Motivation audio talk by Andrew Pudewa Magnum Opus Magazine Transcript of Podcast Episode 521 If you have questions for Andrew, send them to podcast@IEW.comPerhaps your question will be answered at the next Ask Andrew Anything (AAA). If you have questions about IEW products or classes, contact customer service at 800.856.5815 or info@IEW.com

As we continue to celebrate the centennial of the birth of Murray Rothbard, Wanjiru Njoya reminds us that he never compromised his principles and stood for liberty throughout his all-too-brief life.Original article: https://mises.org/mises-wire/rothbard-never-abandoned-his-principles

As we continue to celebrate the centennial of the birth of Murray Rothbard, Wanjiru Njoya reminds us that he never compromised his principles and stood for liberty throughout his all-too-brief life.Original article: https://mises.org/mises-wire/rothbard-never-abandoned-his-principles

What does the Bible really say about sex, romance, and marriage? Pastor Todd Fletcher joins us to break down 10 powerful keys drawn from King Solomon's life and writings — including Song of Solomon, Proverbs, and Ecclesiastes — that can transform your relationship and marriage.This episode is sponsored by The Master's University. To learn more about how you can invest in a college education devoted to Christ & Scripture, visit https://www.masters.eduIn this episode, we cover:✅ Rejecting the sins of your parents✅ How to choose a godly spouse✅ Why avoiding sexual sin protects your future✅ The importance of faithfulness in marriage✅ Pursuing excellence together as a couple✅ Making your wedding day special✅ Taking courtship and dating seriously✅ Enjoying marital intimacy as a gift from God✅ How to work through conflict and marital problems✅ Building a new life together — for the long haulTodd Fletcher has been the lead pastor of Chapel in the Hills Church in Golden, Colorado for 12 years and wrote his doctoral dissertation on the Song of Solomon.Whether you're single, dating, engaged, or married for decades — this conversation is packed with timeless biblical wisdom on love and relationships.

I am making this premium members only episode free as a preview to show you what you could be missing out on by not upgrading to premium membership. This is a free preview of my exclusive 9-part series on “The Principles Of Magic”. This episode is part 6 of 9.Reading from a book titled, "Magic", by Dr. A.S. Raleigh, Official Scribe Of The Hermetic Brotherhood Of Luxor, originally published specifically for Dr. Raleigh's students only.www.alchemicaltechrevolution.com

Kindness and equity are not the same thing. I can give a stranger a sandwich without giving him the keys to my house. God has given us specific understanding in Scripture about how a nation can live together cohesively, and we need to consider how to apply those principles today. Immigration is one of those cultural issues that we need to examine through the lens of biblical thinking.

Once you are saved, you must understand that this is not IT! IT is just the commencement! A commencement to NOW discovering the POWER and PRINCIPLES of the Kingdom of God of which you are NOW a citizen. This message unleashes this reality!

Pastor Phelps preaches on Ezekiel 3, an often overlooked passage with some important lessons for all of us. Message originally preached Sunday evening March 8, 2026.

Robert Panariello, MS, PT, ATC, CSCS, respected physical therapist, strength coach, and former NFL Director of Health Performance and Innovation, joins host Phil Plisky to tackle a big question: How do we bring elite performance principles into the rehab setting? Together, Rob and Phil explore the art and science behind adapting strength, speed, and plyometric progressions for patients recovering from ACL reconstruction and other injuries. You'll hear real-world insights on Vermeil's hierarchy, programming plyometrics, and building true return-to-play readiness. Whether you're early in your career or refining your advanced clinical skills, this conversation helps you reimagine how you apply performance principles—starting day one.Learning OutcomesAnalyze the evidence around the application of Vermeil's hierarchy of athletic development modified for ACL rehabilitation to guide progression planningApply evidence-based, practical strategies to actionably address plyometric exercise design considerations for athletes with differing body masses in the sports rehabilitation settingSolve patient case scenarios involving the clinical progression and return-to-sport decision-making for ACL athletes using Vermeil's hierarchy frameworkTimestamps(00:00:00) Welcome(00:00:05) Introduction to athletic development in rehab(00:02:30) The evolution of rehab techniques(00:04:19) Load and velocity in rehabilitation(00:07:35) Understanding high intensity in rehab(00:08:48) The pyramid of athletic development(00:12:14) The role of isometrics in rehab(00:20:10) Testing and assessing athletic performance(00:24:53) Applying Olympic lifts in rehab(00:28:05) Understanding ACL rehabilitation and strength training(00:33:32) The importance of agility and early movement(00:35:25) Plyometrics: balancing load and recovery(00:45:00) A comprehensive approach to ACL recovery(00:49:50) Key takeaways for effective rehabilitationRehab and Performance Lab is brought to you by Medbridge. If you'd like to earn continuing education credit for listening to this episode and access bonus takeaway handouts, log in to your Medbridge account and navigate to the course where you'll find accreditation details. If applicable, complete the post-course assessment and survey to be eligible for credit. The takeaway handout on Medbridge gives you the key points mentioned in this episode, along with additional resources you can implement into your practice right away.To hear more episodes of Rehab and Performance Lab, visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.medbridge.com/rehab-and-performance-lab⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠If you'd like to subscribe to Medbridge, visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.medbridge.com/pricing/

Due to its position as the 13th American Colony as well as the last colony to support the American Revolution, the role Georgia played in the founding of our country is often overshadowed by colonies like Virginia and Massachusetts.  But Georgia should not be overlooked.  To shed light on the role Georgia played and its historical significance in the American Revolution and our country's founding, our guest this week is Dr. Stan Deaton.  Dr. Deaton is the Dr. Elaine B. Andrews Distinguished Historian at the Georgia Historical Society as well as the Emmy-winning writer and host of "Today in Georgia History."

In this solo episode, Joel Smith explores the principles of programming for speed and power training. Drawing from his own evolution as an athlete and coach, he discusses early influences like high-volume jump programs, Soviet-inspired plyometrics, and classic periodization models. Joel outlines five key programming systems: high-low structure, potentiation sequencing, weekly changeovers, factorization, and autoregulation, while highlighting common mistakes such as excessive volume, overemphasis on one training variable, and over-programming. He emphasizes balancing speed, strength, and capacity, keeping systems simple, and using tools like AI as a thinking partner rather than a replacement for coaching intuition. Today's episode is brought to you by Hammer Strength. Use the code “justfly20” for 20% off any Lila Exogen wearable resistance training, including the popular Exogen Calf Sleeves. For this offer, head to Lilateam.com Use code “justfly10” for 10% off the Vert Trainer View more podcast episodes at the podcast homepage. (https://www.just-fly-sports.com/podcast-home/) Timestamps 3:30 – Early Training Influences 18:50 – The Big Three: Speed, Strength, Capacity 22:25 – System 1: The High-Low System 31:14 – System 2: Potentiation-Based Training 33:38 – System 3: Australian Jumps & Factorization 38:53 – System 4: Bondarchuk's Pyramid of Abilities 43:24 – System 5: Triphasic & Wave Loading 49:00 – Programming Mistakes 57:25 – Principles that Work 1:06:31 – Using AI as a Programming Sparring Partner Joel Smith Quotes "We have to zoom out and look at that more slow-cooked, patient, or planned process to get the big picture of things." "Training is not just going out and doing skills; it is doing a set structure over a set of time." "We should understand what it's like to have that high-end training day and how long it takes to recover from it because a lot of training setups don't really account for that." "How do you know which of those stakeholders is really, if we look to the 80-20 principle, 20% of the program being 80% of the neural stimulus? How do we know how that thing is contributing?" "To maximally simplify any training process, we want to achieve a polarization." "Doing those easy days really well is one of the pieces of the art of coaching that's not talked about so much." "The system of an athlete is an amazing thing; it can adapt to the simplest thing. That's actually what makes humans and training and adaptability pretty cool, we don't need that much complexity to adapt." "Do simple better. It's an important place to start and remind ourselves." "With aggressive programs, use them strategically, not permanently." "Don't live inside one system. I think it's valuable to have a few tools in the toolkit with the systems you're familiar with, so you know when and how to use them." "Make [AI] a sparring partner, challenge your thinking. If you can use it as play and challenge, don't let it do your thinking for you." About Joel Smith Joel Smith is the founder of Just Fly Sports and host of the Just Fly Performance Podcast, one of the leading podcasts in strength and conditioning and track and field coaching. A former collegiate strength and track coach, Joel has spent over a decade studying speed, power, and human movement. He is the author of multiple books and online courses on sprinting, jumping, and elastic training, and works with athletes and coaches around the world to develop more powerful and creative approaches to training.

Turbopuffer came out of a reading app.In 2022, Simon was helping his friends at Readwise scale their infra for a highly requested feature: article recommendations and semantic search. Readwise was paying ~$5k/month for their relational database and vector search would cost ~$20k/month making the feature too expensive to ship. In 2023 after mulling over the problem from Readwise, Simon decided he wanted to “build a search engine” which became Turbopuffer.We discuss:• Simon's path: Denmark → Shopify infra for nearly a decade → “angel engineering” across startups like Readwise, Replicate, and Causal → turbopuffer almost accidentally becoming a company • The Readwise origin story: building an early recommendation engine right after the ChatGPT moment, seeing it work, then realizing it would cost ~$30k/month for a company spending ~$5k/month total on infra and getting obsessed with fixing that cost structure • Why turbopuffer is “a search engine for unstructured data”: Simon's belief that models can learn to reason, but can't compress the world's knowledge into a few terabytes of weights, so they need to connect to systems that hold truth in full fidelity • The three ingredients for building a great database company: a new workload, a new storage architecture, and the ability to eventually support every query plan customers will want on their data • The architecture bet behind turbopuffer: going all in on object storage and NVMe, avoiding a traditional consensus layer, and building around the cloud primitives that only became possible in the last few years • Why Simon hated operating Elasticsearch at Shopify: years of painful on-call experience shaped his obsession with simplicity, performance, and eliminating state spread across multiple systems • The Cursor story: launching turbopuffer as a scrappy side project, getting an email from Cursor the next day, flying out after a 4am call, and helping cut Cursor's costs by 95% while fixing their per-user economics • The Notion story: buying dark fiber, tuning TCP windows, and eating cross-cloud costs because Simon refused to compromise on architecture just to close a deal faster • Why AI changes the build-vs-buy equation: it's less about whether a company can build search infra internally, and more about whether they have time especially if an external team can feel like an extension of their own • Why RAG isn't dead: coding companies still rely heavily on search, and Simon sees hybrid retrieval semantic, text, regex, SQL-style patterns becoming more important, not less • How agentic workloads are changing search: the old pattern was one retrieval call up front; the new pattern is one agent firing many parallel queries at once, turning search into a highly concurrent tool call • Why turbopuffer is reducing query pricing: agentic systems are dramatically increasing query volume, and Simon expects retrieval infra to adapt to huge bursts of concurrent search rather than a small number of carefully chosen calls • The philosophy of “playing with open cards”: Simon's habit of being radically honest with investors, including telling Lachy Groom he'd return the money if turbopuffer didn't hit PMF by year-end • The “P99 engineer”: Simon's framework for building a talent-dense company, rejecting by default unless someone on the team feels strongly enough to fight for the candidate —Simon Hørup Eskildsen• LinkedIn: https://www.linkedin.com/in/sirupsen• X: https://x.com/Sirupsen• https://sirupsen.com/aboutturbopuffer• https://turbopuffer.com/Full Video PodTimestamps00:00:00 The PMF promise to Lachy Groom00:00:25 Intro and Simon's background00:02:19 What turbopuffer actually is00:06:26 Shopify, Elasticsearch, and the pain behind the company00:10:07 The Readwise experiment that sparked turbopuffer00:12:00 The insight Simon couldn't stop thinking about00:17:00 S3 consistency, NVMe, and the architecture bet00:20:12 The Notion story: latency, dark fiber, and conviction00:25:03 Build vs. buy in the age of AI00:26:00 The Cursor story: early launch to breakout customer00:29:00 Why code search still matters00:32:00 Search in the age of agents00:34:22 Pricing turbopuffer in the AI era00:38:17 Why Simon chose Lachy Groom00:41:28 Becoming a founder on purpose00:44:00 The “P99 engineer” philosophy00:49:30 Bending software to your will00:51:13 The future of turbopuffer00:57:05 Simon's tea obsession00:59:03 Tea kits, X Live, and P99 LiveTranscriptSimon Hørup Eskildsen: I don't think I've said this publicly before, but I just called Lockey and was like, local Lockie. Like if this doesn't have PMF by the end of the year, like we'll just like return all the money to you. But it's just like, I don't really, we, Justine and I don't wanna work on this unless it's really working.So we want to give it the best shot this year and like we're really gonna go for it. We're gonna hire a bunch of people. We're just gonna be honest with everyone. Like when I don't know how to play a game, I just play with open cards. Lockey was the only person that didn't, that didn't freak out. He was like, I've never heard anyone say that before.Alessio: Hey everyone, welcome to the Leading Space podcast. This is Celesio Pando, Colonel Laz, and I'm joined by Swix, editor of Leading Space.swyx: Hello. Hello, uh, we're still, uh, recording in the Ker studio for the first time. Very excited. And today we are joined by Simon Eski. Of Turbo Farer welcome.Simon Hørup Eskildsen: Thank you so much for having me.swyx: Turbo Farer has like really gone on a huge tear, and I, I do have to mention that like you're one of, you're not my newest member of the Danish AHU Mafia, where like there's a lot of legendary programmers that have come out of it, like, uh, beyond Trotro, Rasmus, lado Berg and the V eight team and, and Google Maps team.Uh, you're mostly a Canadian now, but isn't that interesting? There's so many, so much like strong Danish presence.Simon Hørup Eskildsen: Yeah, I was writing a post, um, not that long ago about sort of the influences. So I grew up in Denmark, right? I left, I left when, when I was 18 to go to Canada to, to work at Shopify. Um, and so I, like, I've, I would still say that I feel more Danish than, than Canadian.This is also the weird accent. I can't say th because it, this is like, I don't, you know, my wife is also Canadian, um, and I think. I think like one of the things in, in Denmark is just like, there's just such a ruthless pragmatism and there's also a big focus on just aesthetics. Like, they're like very, people really care about like where, what things look like.Um, and like Canada has a lot of attributes, US has, has a lot of attributes, but I think there's been lots of the great things to carry. I don't know what's in the water in Ahu though. Um, and I don't know that I could be considered part of the Mafi mafia quite yet, uh, compared to the phenomenal individuals we just mentioned.Barra OV is also, uh, Danish Canadian. Okay. Yeah. I don't know where he lives now, but, and he's the PHP.swyx: Yeah. And obviously Toby German, but moved to Canada as well. Yes. Like this is like import that, uh, that, that is an interesting, um, talent move.Alessio: I think. I would love to get from you. Definition of Turbo puffer, because I think you could be a Vector db, which is maybe a bad word now in some circles, you could be a search engine.It's like, let, let's just start there and then we'll maybe run through the history of how you got to this point.Simon Hørup Eskildsen: For sure. Yeah. So Turbo Puffer is at this point in time, a search engine, right? We do full text search and we do vector search, and that's really what we're specialized in. If you're trying to do much more than that, like then this might not be the right place yet, but Turbo Buffer is all about search.The other way that I think about it is that we can take all of the world's knowledge, all of the exabytes and exabytes of data that there is, and we can use those tokens to train a model, but we can't compress all of that into a few terabytes of weights, right? Compress into a few terabytes of weights, how to reason with the world, how to make sense of the knowledge.But we have to somehow connect it to something externally that actually holds that like in full fidelity and truth. Um, and that's the thing that we intend to become. Right? That's like a very holier than now kind of phrasing, right? But being the search engine for unstructured, unstructured data is the focus of turbo puffer at this point in time.Alessio: And let's break down. So people might say, well, didn't Elasticsearch already do this? And then some other people might say, is this search on my data, is this like closer to rag than to like a xr, like a public search thing? Like how, how do you segment like the different types of search?Simon Hørup Eskildsen: The way that I generally think about this is like, there's a lot of database companies and I think if you wanna build a really big database company, sort of, you need a couple of ingredients to be in the air.We don't, which only happens roughly every 15 years. You need a new workload. You basically need the ambition that every single company on earth is gonna have data in your database. Multiple times you look at a company like Oracle, right? You will, like, I don't think you can find a company on earth with a digital presence that it not, doesn't somehow have some data in an Oracle database.Right? And I think at this point, that's also true for Snowflake and Databricks, right? 15 years later it's, or even more than that, there's not a company on earth that doesn't, in. Or directly is consuming Snowflake or, or Databricks or any of the big analytics databases. Um, and I think we're in that kind of moment now, right?I don't think you're gonna find a company over the next few years that doesn't directly or indirectly, um, have all their data available for, for search and connect it to ai. So you need that new workload, like you need something to be happening where there's a new workload that causes that to happen, and that new workload is connecting very large amounts of data to ai.The second thing you need. The second condition to build a big database company is that you need some new underlying change in the storage architecture that is not possible from the databases that have come before you. If you look at Snowflake and Databricks, right, commoditized, like massive fleet of HDDs, like that was not possible in it.It just wasn't in the air in the nineties, right? So you just didn't, we just didn't build these systems. S3 and and and so on was not around. And I think the architecture that is now possible that wasn't possible 15 years ago is to go all in on NVME SSDs. It requires a particular type of architecture for the database that.It's difficult to retrofit onto the databases that are already there, including the ones you just mentioned. The second thing is to go all in on OIC storage, more so than we could have done 15 years ago. Like we don't have a consensus layer, we don't really have anything. In fact, you could turn off all the servers that Turbo Buffer has, and we would not lose any data because we have all completely all in on OIC storage.And this means that our architecture is just so simple. So that's the second condition, right? First being a new workload. That means that every company on earth, either indirectly or directly, is using your database. Second being, there's some new storage architecture. That means that the, the companies that have come before you can do what you're doing.I think the third thing you need to do to build a big database company is that over time you have to implement more or less every Cory plan on the data. What that means is that you. You can't just get stuck in, like, this is the one thing that a database does. It has to be ever evolving because when someone has data in the database, they over time expect to be able to ask it more or less every question.So you have to do that to get the storage architecture to the limit of what, what it's capable of. Those are the three conditions.swyx: I just wanted to get a little bit of like the motivation, right? Like, so you left Shopify, you're like principal, engineer, infra guy. Um, you also head of kernel labs, uh, inside of Shopify, right?And then you consulted for read wise and that it kind of gave you that, that idea. I just wanted you to tell that story. Um, maybe I, you've told it before, but, uh, just introduce the, the. People to like the, the new workload, the sort of aha moment for turbo PufferSimon Hørup Eskildsen: For sure. So yeah, I spent almost a decade at Shopify.I was on the infrastructure team, um, from the fairly, fairly early days around 2013. Um, at the time it felt like it was growing so quickly and everything, all the metrics were, you know, doubling year on year compared to the, what companies are contending with today. It's very cute in growth. I feel like lot some companies are seeing that month over month.Um, of course. Shopify compound has been compounding for a very long time now, but I spent a decade doing that and the majority of that was just make sure the site is up today and make sure it's up a year from now. And a lot of that was really just the, um, you know, uh, the Kardashians would drive very, very large amounts of, of data to, to uh, to Shopify as they were rotating through all the merch and building out their businesses.And we just needed to make sure we could handle that. Right. And sometimes these were events, a million requests per second. And so, you know, we, we had our own data centers back in the day and we were moving to the cloud and there was so much sharding work and all of that that we were doing. So I spent a decade just scaling databases ‘cause that's fundamentally what's the most difficult thing to scale about these sites.The database that was the most difficult for me to scale during that time, and that was the most aggravating to be on call for, was elastic search. It was very, very difficult to deal with. And I saw a lot of projects that were just being held back in their ambition by using it.swyx: And I mean, self-hosted.Self-hosted. ‘causeSimon Hørup Eskildsen: it's, yeah, and it commercial, this is like 2015, right? So it's like a very particular vintage. Right. It's probably better at a lot of these things now. Um, it was difficult to contend with and I'm just like, I just think about it. It's an inverted index. It should be good at these kinds of queries and do all of this.And it was, we, we often couldn't get it to do exactly what we needed to do or basically get lucine to do, like expose lucine raw to, to, to what we needed to do. Um, so that was like. Just something that we did on the side and just panic scaled when we needed to, but not a particular focus of mine. So I left, and when I left, I, um, wasn't sure exactly what I wanted to do.I mean, it spent like a decade inside of the same company. I'd like grown up there. I started working there when I was 18.swyx: You only do Rails?Simon Hørup Eskildsen: Yeah. I mean, yeah. Rails. And he's a Rails guy. Uh, love Rails. So good. Um,Alessio: we all wish we could still work in Rails.swyx: I know know. I know, but some, I tried learning Ruby.It's just too much, like too many options to do the same thing. It's, that's my, I I know there's a, there's a way to do it.Simon Hørup Eskildsen: I love it. I don't know that I would use it now, like given cloud code and, and, and cursor and everything, but, um, um, but still it, like if I'm just sitting down and writing a teal code, that's how I think.But anyway, I left and I wasn't, I talked to a couple companies and I was like, I don't. I need to see a little bit more of the world here to know what I'm gonna like focus on next. Um, and so what I decided is like I was gonna, I called it like angel engineering, where I just hopped around in my friend's companies in three months increments and just helped them out with something.Right. And, and just vested a bit of equity and solved some interesting infrastructure problem. So I worked with a bunch of companies at the time, um, read Wise was one of them. Replicate was one of them. Um, causal, I dunno if you've tried this, it's like a, it's a spreadsheet engine Yeah. Where you can do distribution.They sold recently. Yeah. Um, we've been, we used that in fp and a at, um, at Turbo Puffer. Um, so a bunch of companies like this and it was super fun. And so we're the Chachi bt moment happened, I was with. With read Wise for a stint, we were preparing for the reader launch, right? Which is where you, you cue articles and read them later.And I was just getting their Postgres up to snuff, like, which basically boils down to tuning, auto vacuum. So I was doing that and then this happened and we were like, oh, maybe we should build a little recommendation engine and some features to try to hook in the lms. They were not that good yet, but it was clear there was something there.And so I built a small recommendation engine just, okay, let's take the articles that you've recently read, right? Like embed all the articles and then do recommendations. It was good enough that when I ran it on one of the co-founders of Rey's, like I found out that I got articles about, about having a child.I'm like, oh my God, I didn't, I, I didn't know that, that they were having a child. I wasn't sure what to do with that information, but the recommendation engine was good enough that it was suggesting articles, um, about that. And so there was, there was recommendations and uh, it actually worked really well.But this was a company that was spending maybe five grand a month in total on all their infrastructure and. When I did the napkin math on running the embeddings of all the articles, putting them into a vector index, putting it in prod, it's gonna be like 30 grand a month. That just wasn't tenable. Right?Like Read Wise is a proudly bootstrapped company and it's paying 30 grand for infrastructure for one feature versus five. It just wasn't tenable. So sort of in the bucket of this is useful, it's pretty good, but let us, let's return to it when the costs come down.swyx: Did you say it grows by feature? So for five to 30 is by the number of, like, what's the, what's the Scaling factor scale?It scales by the number of articles that you embed.Simon Hørup Eskildsen: It does, but what I meant by that is like five grand for like all of the other, like the Heroku, dinos, Postgres, like all the other, and this then storage is 30. Yeah. And then like 30 grand for one feature. Right. Which is like, what other articles are related to this one.Um, so it was just too much right to, to power everything. Their budget would've been maybe a few thousand dollars, which still would've been a lot. And so we put it in a bucket of, okay, we're gonna do that later. We'll wait, we will wait for the cost to come down. And that haunted me. I couldn't stop thinking about it.I was like, okay, there's clearly some latent demand here. If the cost had been a 10th, we would've shipped it and. This was really the only data point that I had. Right. I didn't, I, I didn't, I didn't go out and talk to anyone else. It was just so I started reading Right. I couldn't, I couldn't help myself.Like I didn't know what like a vector index is. I, I generally barely do about how to generate the vectors. There was a lot of hype about, this is a early 2023. There was a lot of hype about vector databases. There were raising a lot of money and it's like, I really didn't know anything about it. It's like, you know, trying these little models, fine tuning them.Like I was just trying to get sort of a lay of the land. So I just sat down. I have this. A GitHub repository called Napkin Math. And on napkin math, there's just, um, rows of like, oh, this is how much bandwidth. Like this is how many, you know, you can do 25 gigabytes per second on average to dram. You can do, you know, five gigabytes per second of rights to an SSD, blah blah.All of these numbers, right? And S3, how many you could do per, how much bandwidth can you drive per connection? I was just sitting down, I was like, why hasn't anyone build a database where you just put everything on O storage and then you puff it into NVME when you use the data and you puff it into dram if you're, if you're querying it alive, it's just like, this seems fairly obvious and you, the only real downside to that is that if you go all in on o storage, every right will take a couple hundred milliseconds of latency, but from there it's really all upside, right?You do the first go, it takes half a second. And it sort of occurred to me as like, well. The architecture is really good for that. It's really good for AB storage, it's really good for nvm ESSD. It's, well, you just couldn't have done that 10 years ago. Back to what we were talking about before. You really have to build a database where you have as few round trips as possible, right?This is how CPUs work today. It's how NVM E SSDs work. It's how as, um, as three works that you want to have a very large amount of outstanding requests, right? Like basically go to S3, do like that thousand requests to ask for data in one round trip. Wait for that. Get that, like, make a new decision. Do it again, and try to do that maybe a maximum of three times.But no databases were designed that way within NVME as is ds. You can drive like within, you know, within a very low multiple of DRAM bandwidth if you use it that way. And same with S3, right? You can fully max out the network card, which generally is not maxed out. You get very, like, very, very good bandwidth.And, but no one had built a database like that. So I was like, okay, well can't you just, you know, take all the vectors right? And plot them in the proverbial coordinate system. Get the clusters, put a file on S3 called clusters, do json, and then put another file for every cluster, you know, cluster one, do js O cluster two, do js ON you know that like it's two round trips, right?So you get the clusters, you find the closest clusters, and then you download the cluster files like the, the closest end. And you could do this in two round trips.swyx: You were nearest neighbors locally.Simon Hørup Eskildsen: Yes. Yes. And then, and you would build this, this file, right? It's just like ultra simplistic, but it's not a far shot from what the first version of Turbo Buffer was.Why hasn't anyone done thatAlessio: in that moment? From a workload perspective, you're thinking this is gonna be like a read heavy thing because they're doing recommend. Like is the fact that like writes are so expensive now? Oh, with ai you're actually not writing that much.Simon Hørup Eskildsen: At that point I hadn't really thought too much about, well no actually it was always clear to me that there was gonna be a lot of rights because at Shopify, the search clusters were doing, you know, I don't know, tens or hundreds of crew QPS, right?‘cause you just have to have a human sit and type in. But we did, you know, I don't know how many updates there were per second. I'm sure it was in the millions, right into the cluster. So I always knew there was like a 10 to 100 ratio on the read write. In the read wise use case. It's, um, even, even in the read wise use case, there'd probably be a lot fewer reads than writes, right?There's just a lot of churn on the amount of stuff that was going through versus the amount of queries. Um, I wasn't thinking too much about that. I was mostly just thinking about what's the fundamentally cheapest way to build a database in the cloud today using the primitives that you have available.And this is it, right? You just, now you have one machine and you know, let's say you have a terabyte of data in S3, you paid the $200 a month for that, and then maybe five to 10% of that data and needs to be an NV ME SSDs and less than that in dram. Well. You're paying very, very little to inflate the data.swyx: By the way, when you say no one else has done that, uh, would you consider Neon, uh, to be on a similar path in terms of being sort of S3 first and, uh, separating the compute and storage?Simon Hørup Eskildsen: Yeah, I think what I meant with that is, uh, just build a completely new database. I don't know if we were the first, like it was very much, it was, I mean, I, I hadn't, I just looked at the napkin math and was like, this seems really obvious.So I'm sure like a hundred people came up with it at the same time. Like the light bulb and every invention ever. Right. It was just in the air. I think Neon Neon was, was first to it. And they're trying, they're retrofitted onto Postgres, right? And then they built this whole architecture where you have, you have it in memory and then you sort of.You know, m map back to S3. And I think that was very novel at the time to do it for, for all LTP, but I hadn't seen a database that was truly all in, right. Not retrofitting it. The database felt built purely for this no consensus layer. Even using compare and swap on optic storage to do consensus. I hadn't seen anyone go that all in.And I, I mean, there, there, I'm sure there was someone that did that before us. I don't know. I was just looking at the napkin mathswyx: and, and when you say consensus layer, uh, are you strongly relying on S3 Strong consistency? You are. Okay.SoSimon Hørup Eskildsen: that is your consensus layer. It, it is the consistency layer. And I think also, like, this is something that most people don't realize, but S3 only became consistent in December of 2020.swyx: I remember this coming out during COVID and like people were like, oh, like, it was like, uh, it was just like a free upgrade.Simon Hørup Eskildsen: Yeah.swyx: They were just, they just announced it. We saw consistency guys and like, okay, cool.Simon Hørup Eskildsen: And I'm sure that they just, they probably had it in prod for a while and they're just like, it's done right.And people were like, okay, cool. But. That's a big moment, right? Like nv, ME SSDs, were also not in the cloud until around 2017, right? So you just sort of had like 2017 nv, ME SSDs, and people were like, okay, cool. There's like one skew that does this, whatever, right? Takes a few years. And then the second thing is like S3 becomes consistent in 2020.So now it means you don't have to have this like big foundation DB or like zookeeper or whatever sitting there contending with the keys, which is how. You know, that's what Snowflake and others have do so muchswyx: for goneSimon Hørup Eskildsen: Exactly. Just gone. Right? And so just push to the, you know, whatever, how many hundreds of people they have working on S3 solved and then compare and swap was not in S3 at this point in time,swyx: by the way.Uh, I don't know what that is, so maybe you wanna explain. Yes. Yeah.Simon Hørup Eskildsen: Yes. So, um, what Compare and swap is, is basically, you can imagine that if you have a database, it might be really nice to have a file called metadata json. And metadata JSON could say things like, Hey, these keys are here and this file means that, and there's lots of metadata that you have to operate in the database, right?But that's the simplest way to do it. So now you have might, you might have a lot of servers that wanna change the metadata. They might have written a file and want the metadata to contain that file. But you have a hundred nodes that are trying to contend with this metadata that JSON well, what compare and Swap allows you to do is basically just you download the file, you make the modifications, and then you write it only if it hasn't changed.While you did the modification and if not you retry. Right? Should just have this retry loops. Now you can imagine if you have a hundred nodes doing that, it's gonna be really slow, but it will converge over time. That primitive was not available in S3. It wasn't available in S3 until late 2024, but it was available in GCP.The real story of this is certainly not that I sat down and like bake brained it. I was like, okay, we're gonna start on GCS S3 is gonna get it later. Like it was really not that we started, we got really lucky, like we started on GCP and we started on GCP because tur um, Shopify ran on GCP. And so that was the platform I was most available with.Right. Um, and I knew the Canadian team there ‘cause I'd worked with them at Shopify and so it was natural for us to start there. And so when we started building the database, we're like, oh yeah, we have to build a, we really thought we had to build a consensus layer, like have a zookeeper or something to do this.But then we discovered the compare and swap. It's like, oh, we can kick the can. Like we'll just do metadata r json and just, it's fine. It's probably fine. Um, and we just kept kicking the can until we had very, very strong conviction in the idea. Um, and then we kind of just hinged the company on the fact that S3 probably was gonna get this, it started getting really painful in like mid 2024.‘cause we were closing deals with, um, um, notion actually that was running in AWS and we're like, trust us. You, you really want us to run this in GCP? And they're like, no, I don't know about that. Like, we're running everything in AWS and the latency across the cloud were so big and we had so much conviction that we bought like, you know, dark fiber between the AWS regions in, in Oregon, like in the InterExchange and GCP is like, we've never seen a startup like do like, what's going on here?And we're just like, no, we don't wanna do this. We were tuning like TCP windows, like everything to get the latency down ‘cause we had so high conviction in not doing like a, a metadata layer on S3. So those were the three conditions, right? Compare and swap. To do metadata, which wasn't in S3 until late 2024 S3 being consistent, which didn't happen until December, 2020.Uh, 2020. And then NVMe ssd, which didn't end in the cloud until 2017.swyx: I mean, in some ways, like a very big like cloud success story that like you were able to like, uh, put this all together, but also doing things like doing, uh, bind our favor. That that actually is something I've never heard.Simon Hørup Eskildsen: I mean, it's very common when you're a big company, right?You're like connecting your own like data center or whatever. But it's like, it was uniquely just a pain with notion because the, um, the org, like most of the, like if you're buying in Ashburn, Virginia, right? Like US East, the Google, like the GCP and, and AWS data centers are like within a millisecond on, on each other, on the public exchanges.But in Oregon uniquely, the GCP data center sits like a couple hundred kilometers, like east of Portland and the AWS region sits in Portland, but the network exchange they go through is through Seattle. So it's like a full, like 14 milliseconds or something like that. And so anyway, yeah. It's, it's, so we were like, okay, we can't, we have to go through an exchange in Portland.Yeah. Andswyx: you'd rather do this than like run your zookeeper and likeSimon Hørup Eskildsen: Yes. Way rather. It doesn't have state, I don't want state and two systems. Um, and I think all that is just informed by Justine, my co-founder and I had just been on call for so long. And the worst outages are the ones where you have state in multiple places that's not syncing up.So it really came from, from a a, like just a, a very pure source of pain, of just imagining what we would be Okay. Being woken up at 3:00 AM about and having something in zookeeper was not one of them.swyx: You, you're talking to like a notion or something. Do they care or do they just, theySimon Hørup Eskildsen: just, they care about latency.swyx: They latency cost. That's it.Simon Hørup Eskildsen: They just cared about latency. Right. And we just absorbed the cost. We're just like, we have high conviction in this. At some point we can move them to AWS. Right. And so we just, we, we'll buy the fiber, it doesn't matter. Right. Um, and it's like $5,000. Usually when you buy fiber, you buy like multiple lines.And we're like, we can only afford one, but we will just test it that when it goes over the public internet, it's like super smooth. And so we did a lot of, anyway, it's, yeah, it was, that's cool.Alessio: You can imagine talking to the GCP rep and it's like, no, we're gonna buy, because we know we're gonna turn, we're gonna turn from you guys and go to AWS in like six months.But in the meantime we'll do this. It'sSimon Hørup Eskildsen: a, I mean, like they, you know, this workload still runs on GCP for what it's worth. Right? ‘cause it's so, it was just, it was so reliable. So it was never about moving off GCP, it was just about honesty. It was just about giving notion the latency that they deserved.Right. Um, and we didn't want ‘em to have to care about any of this. We also, they were like, oh, egress is gonna be bad. It was like, okay, screw it. Like we're just gonna like vvc, VPC peer with you and AWS we'll eat the cost. Yeah. Whatever needs to be done.Alessio: And what were the actual workloads? Because I think when you think about ai, it's like 14 milliseconds.It's like really doesn't really matter in the scheme of like a model generation.Simon Hørup Eskildsen: Yeah. We were told the latency, right. That we had to beat. Oh, right. So, so we're just looking at the traces. Right. And then sort of like hand draw, like, you know, kind of like looking at the trace and then thinking what are the other extensions of the trace?Right. And there's a lot more to it because it's also when you have, if you have 14 versus seven milliseconds, right. You can fit in another round trip. So we had to tune TCP to try to send as much data in every round trip, prewarm all the connections. And there was, there's a lot of things that compound from having these kinds of round trips, but in the grand scheme it was just like, well, we have to beat the latency of whatever we're up against.swyx: Which is like they, I mean, notion is a database company. They could have done this themselves. They, they do lots of database engineering themselves. How do you even get in the door? Like Yeah, just like talk through that kind of.Simon Hørup Eskildsen: Last time I was in San Francisco, I was talking to one of the engineers actually, who, who was one of our champions, um, at, AT Notion.And they were, they were just trying to make sure that the, you know, per user cost matched the economics that they needed. You know, Uhhuh like, it's like the way I think about, it's like I have to earn a return on whatever the clouds charge me and then my customers have to earn a return on that. And it's like very simple, right?And so there has to be gross margin all the way up and that's how you build the product. And so then our customers have to make the right set of trade off the turbo Puffer makes, and if they're happy with that, that's great.swyx: Do you feel like you're competing with build internally versus buy or buy versus buy?Simon Hørup Eskildsen: Yeah, so, sorry, this was all to build up to your question. So one of the notion engineers told me that they'd sat and probably on a napkin, like drawn out like, why hasn't anyone built this? And then they saw terrible. It was like, well, it literally that. So, and I think AI has also changed the buy versus build equation in terms of, it's not really about can we build it, it's about do we have time to build it?I think they like, I think they felt like, okay, if this is a team that can do that and they, they feel enough like an extension of our team, well then we can go a lot faster, which would be very, very good for them. And I mean, they put us through the, through the test, right? Like we had some very, very long nights to to, to do that POC.And they were really our biggest, our second big customer off the cursor, which also was a lot of late nights. Right.swyx: Yeah. That, I mean, should we go into that story? The, the, the sort of Chris's story, like a lot, um, they credit you a lot for. Working very closely with them. So I just wanna hear, I've heard this, uh, story from Sole's point of view, but like, I'm curious what, what it looks like from your side.Simon Hørup Eskildsen: I actually haven't heard it from Sole's point of view, so maybe you can now cross reference it. The way that I remember it was that, um, the day after we launched, which was just, you know, I'd worked the whole summer on, on the first version. Justine wasn't part of it yet. ‘cause I just, I didn't tell anyone that summer that I was working on this.I was just locked in on building it because it's very easy otherwise to confuse talking about something to actually doing it. And so I was just like, I'm not gonna do that. I'm just gonna do the thing. I launched it and at this point turbo puffer is like a rust binary running on a single eight core machine in a T Marks instance.And me deploying it was like looking at the request log and then like command seeing it or like control seeing it to just like, okay, there's no request. Let's upgrade the binary. Like it was like literally the, the, the, the scrappiest thing. You could imagine it was on purpose because just like at Shopify, we did that all the time.Like, we like move, like we ran things in tux all the time to begin with. Before something had like, at least the inkling of PMF, it was like, okay, is anyone gonna hear about this? Um, and one of the cursor co-founders Arvid reached out and he just, you know, the, the cursor team are like all I-O-I-I-M-O like, um, contenders, right?So they just speak in bullet points and, and facts. It was like this amazing email exchange just of, this is how many QPS we have, this is what we're paying, this is where we're going, blah, blah, blah. And so we're just conversing in bullet points. And I tried to get a call with them a few times, but they were, so, they were like really writing the PMF bowl here, just like late 2023.And one time Swally emails me at like five. What was it like 4:00 AM Pacific time saying like, Hey, are you open for a call now? And I'm on the East coast and I, it was like 7:00 AM I was like, yeah, great, sure, whatever. Um, and we just started talking and something. Then I didn't know anything about sales.It was something that just comp compelled me. I have to go see this team. Like, there's something here. So I, I went to San Francisco and I went to their office and the way that I remember it is that Postgres was down when I showed up at the office. Did SW tell you this? No. Okay. So Postgres was down and so it's like they were distracting with that.And I was trying my best to see if I could, if I could help in any way. Like I knew a little bit about databases back to tuning, auto vacuum. It was like, I think you have to tune out a vacuum. Um, and so we, we talked about that and then, um, that evening just talked about like what would it look like, what would it look like to work with us?And I just said. Look like we're all in, like we will just do what we'll do whatever, whatever you tell us, right? They migrated everything over the next like week or two, and we reduced their cost by 95%, which I think like kind of fixed their per user economics. Um, and it solved a lot of other things. And we were just, Justine, this is also when I asked Justine to come on as my co-founder, she was the best engineer, um, that I ever worked with at Shopify.She lived two blocks away and we were just, okay, we're just gonna get this done. Um, and we did, and so we helped them migrate and we just worked like hell over the next like month or two to make sure that we were never an issue. And that was, that was the cursor story. Yeah.swyx: And, and is code a different workload than normal text?I, I don't know. Is is it just text? Is it the same thing?Simon Hørup Eskildsen: Yeah, so cursor's workload is basically, they, um, they will embed the entire code base, right? So they, they will like chunk it up in whatever they would, they do. They have their own embedding model, um, which they've been public about. Um, and they find that on, on, on their evals.It. There's one of their evals where it's like a 25% improvement on a very particular workload. They have a bunch of blog posts about it. Um, I think it works best on larger code basis, but they've trained their own embedding model to do this. Um, and so you'll see it if you use the cursor agent, it will do searches.And they've also been public around, um, how they've, I think they post trained their model to be very good at semantic search as well. Um, and that's, that's how they use it. And so it's very good at, like, can you find me on the code that's similar to this, or code that does this? And just in, in this queries, they also use GR to supplement it.swyx: Yeah.Simon Hørup Eskildsen: Um, of courseswyx: it's been a big topic of discussion like, is rag dead because gr you know,Simon Hørup Eskildsen: and I mean like, I just, we, we see lots of demand from the coding company to ethicsswyx: search in every part. Yes.Simon Hørup Eskildsen: Uh, we, we, we see demand. And so, I mean, I'm. I like case studies. I don't like, like just doing like thought pieces on this is where it's going.And like trying to be all macroeconomic about ai, that's has turned out to be a giant waste of time because no one can really predict any of this. So I just collect case studies and I mean, cursor has done a great job talking about what they're doing and I hope some of the other coding labs that use Turbo Puffer will do the same.Um, but it does seem to make a difference for particular queries. Um, I mean we can also do text, we can also do RegX, but I should also say that cursors like security posture into Tur Puffer is exceptional, right? They have their own embedding model, which makes it very difficult to reverse engineer. They obfuscate the file paths.They like you. It's very difficult to learn anything about a code base by looking at it. And the other thing they do too is that for their customers, they encrypt it with their encryption keys in turbo puffer's bucket. Um, so it's, it's, it's really, really well designed.swyx: And so this is like extra stuff they did to work with you because you are not part of Cursor.Exactly like, and this is just best practice when working in any database, not just you guys. Okay. Yeah, that makes sense. Yeah. I think for me, like the, the, the learning is kind of like you, like all workloads are hybrid. Like, you know, uh, like you, you want the semantic, you want the text, you want the RegX, you want sql.I dunno. Um, but like, it's silly to like be all in on like one particularly query pattern.Simon Hørup Eskildsen: I think, like I really like the way that, um, um, that swally at cursor talks about it, which is, um, I'm gonna butcher it here. Um, and you know, I'm a, I'm a database scalability person. I'm not a, I, I dunno anything about training models other than, um, what the internet tells me and what.The way he describes is that this is just like cash compute, right? It's like you have a point in time where you're looking at some particular context and focused on some chunk and you say, this is the layer of the neural net at this point in time. That seems fundamentally really useful to do cash compute like that.And, um, how the value of that will change over time. I'm, I'm not sure, but there seems to be a lot of value in that.Alessio: Maybe talk a bit about the evolution of the workload, because even like search, like maybe two years ago it was like one search at the start of like an LLM query to build the context. Now you have a gentech search, however you wanna call it, where like the model is both writing and changing the code and it's searching it again later.Yeah. What are maybe some of the new types of workloads or like changes you've had to make to your architecture for it?Simon Hørup Eskildsen: I think you're right. When I think of rag, I think of, Hey, there's an 8,000 token, uh, context window and you better make it count. Um, and search was a way to do that now. Everything is moving towards the, just let the agent do its thing.Right? And so back to the thing before, right? The LLM is very good at reasoning with the data, and so we're just the tool call, right? And that's increasingly what we see our customers doing. Um, what we're seeing more demand from, from our customers now is to do a lot of concurrency, right? Like Notion does a ridiculous amount of queries in every round trip just because they can't.And I'm also now, when I use the cursor agent, I also see them doing more concurrency than I've ever seen before. So a bit similar to how we designed a database to drive as much concurrency in every round trip as possible. That's also what the agents are doing. So that's new. It means just an enormous amount of queries all at once to the dataset while it's warm in as few turns as possible.swyx: Can I clarify one thing on that?Simon Hørup Eskildsen: Yes.swyx: Is it, are they batching multiple users or one user is driving multiple,Simon Hørup Eskildsen: one user driving multiple, one agent driving.swyx: It's parallel searching a bunch of things.Simon Hørup Eskildsen: Exactly.swyx: Yeah. Yeah, exactly. So yeah, the clinician also did, did this for the fast context thing, like eight parallel at once.Simon Hørup Eskildsen: Yes.swyx: And, and like an interesting problem is, well, how do you make sure you have enough diversity so you're not making the the same request eight times?Simon Hørup Eskildsen: And I think like that's probably also where the hybrid comes in, where. That's another way to diversify. It's a completely different way to, to do the search.That's a big change, right? So before it was really just like one call and then, you know, the LLM took however many seconds to return, but now we just see an enormous amount of queries. So the, um, we just see more queries. So we've like tried to reduce query, we've reduced query pricing. Um, this is probably the first time actually I'm saying that, but the query pricing is being reduced, like five x.Um, and we'll probably try to reduce it even more to accommodate some of these workloads of just doing very large amounts of queries. Um, that's one thing that's changed. I think the right, the right ratio is still very high, right? Like there's still a, an enormous amount of rights per read, but we're starting probably to see that change if people really lean into this pattern.Alessio: Can we talk a little bit about the pricing? I'm curious, uh, because traditionally a database would charge on storage, but now you have the token generation that is so expensive, where like the actual. Value of like a good search query is like much higher because they're like saving inference time down the line.How do you structure that as like, what are people receptive to on the other side too?Simon Hørup Eskildsen: Yeah. I, the, the turbo puffer pricing in the beginning was just very simple. The pricing on these on for search engines before Turbo Puffer was very server full, right? It was like, here's the vm, here's the per hour cost, right?Great. And I just sat down with like a piece of paper and said like, if Turbo Puffer was like really good, this is probably what it would cost with a little bit of margin. And that was the first pricing of Turbo Puffer. And I just like sat down and I was like, okay, like this is like probably the storage amp, but whenever on a piece of paper I, it was vibe pricing.It was very vibe price, and I got it wrong. Oh. Um, well I didn't get it wrong, but like Turbo Puffer wasn't at the first principle pricing, right? So when Cursor came on Turbo Puffer, it was like. Like, I didn't know any VCs. I didn't know, like I was just like, I don't know, I didn't know anything about raising money or anything like that.I just saw that my GCP bill was, was high, was a lot higher than the cursor bill. So Justine and I was just like, well, we have to optimize it. Um, and I mean, to the chagrin now of, of it, of, of the VCs, it now means that we're profitable because we've had so much pricing pressure in the beginning. Because it was running on my credit card and Justine and I had spent like, like tens of thousands of dollars on like compute bills and like spinning off the company and like very like, like bad Canadian lawyers and like things like to like get all of this done because we just like, we didn't know.Right. If you're like steeped in San Francisco, you're just like, you just know. Okay. Like you go out, raise a pre-seed round. I, I never heard a word pre-seed at this point in time.swyx: When you had Cursor, you had Notion you, you had no funding.Simon Hørup Eskildsen: Um, with Cursor we had no funding. Yeah. Um, by the time we had Notion Locke was, Locke was here.Yeah. So it was really just, we vibe priced it 100% from first Principles, but it wasn't, it, it was not performing at first principles, so we just did everything we could to optimize it in the beginning for that, so that at least we could have like a 5% margin or something. So I wasn't freaking out because Cursor's bill was also going like this as they were growing.And so my liability and my credit limit was like actively like calling my bank. It was like, I need a bigger credit. Like it was, yeah. Anyway, that was the beginning. Yeah. But the pricing was, yeah, like storage rights and query. Right. And the, the pricing we have today is basically just that pricing with duct tape and spit to try to approach like, you know, like a, as a margin on the physical underlying hardware.And we're doing this year, you're gonna see more and more pricing changes from us. Yeah.swyx: And like is how much does stuff like VVC peering matter because you're working in AWS land where egress is charged and all that, you know.Simon Hørup Eskildsen: We probably don't like, we have like an enterprise plan that just has like a base fee because we haven't had time to figure out SKU pricing for all of this.Um, but I mean, yeah, you can run turbo puffer either in SaaS, right? That's what Cursor does. You can run it in a single tenant cluster. So it's just you. That's what Notion does. And then you can run it in, in, in BYOC where everything is inside the customer's VPC, that's what an for example, philanthropic does.swyx: What I'm hearing is that this is probably the best CRO job for somebody who can come in and,Simon Hørup Eskildsen: I mean,swyx: help you with this.Simon Hørup Eskildsen: Um, like Turbo Puffer hired, like, I don't know what, what number this was, but we had a full-time CFO as like the 12th hire or something at Turbo Puffer, um, I think I hear are a lot of comp.I don't know how they do it. Like they have a hundred employees and not a CFO. It's like having a CFO is like a runningswyx: business man. Like, you know,Simon Hørup Eskildsen: it's so good. Yeah, like money Mike, like he just, you know, just handles the money and a lot of the business stuff and so he came in and just hopped with a lot of the operational side of the business.So like C-O-O-C-F-O, like somewhere in between.swyx: Just as quick mention of Lucky, just ‘cause I'm curious, I've met Lock and like, he's obviously a very good investor and now on physical intelligence, um, I call it generalist super angel, right? He invests in everything. Um, and I always wonder like, you know, is there something appealing about focusing on developer tooling, focusing on databases, going like, I've invested for 10 years in databases versus being like a lock where he can maybe like connect you to all the customers that you need.Simon Hørup Eskildsen: This is an excellent question. No, no one's asked me this. Um, why lockey? Because. There was a couple of people that we were talking to at the time and when we were raising, we were almost a little, we were like a bit distressed because one of our, one of our peers had just launched something that was very similar to Turbo Puffer.And someone just gave me the advice at the time of just choose the person where you just feel like you can just pick up the phone and not prepare anything. And just be completely honest, and I don't think I've said this publicly before, but I just called Lockey and was like local Lockie. Like if this doesn't have PMF by the end of the year, like we'll just like return all the money to you.But it's just like, I don't really, we, Justine and I don't wanna work on this unless it's really working. So we want to give it the best shot this year and like we're really gonna go for it. We're gonna hire a bunch of people and we're just gonna be honest with everyone. Like when I don't know how to play a game, I just play with open cards and.Lockey was the only person that didn't, that didn't freak out. He was like, I've never heard anyone say that before. As I said, I didn't even know what a seed or pre-seed round was like before, probably even at this time. So I was just like very honest with him. And I asked him like, Lockie, have you ever have, have you ever invested in database company?He was just like, no. And at the time I was like, am I dumb? Like, but I think there was something that just like really drew me to Lockie. He is so authentic, so honest, like, and there was something just like, I just felt like I could just play like, just say everything openly. And that was, that was, I think that that was like a perfect match at the time, and, and, and honestly still is.He was just like, okay, that's great. This is like the most honest, ridiculous thing I've ever heard anyone say to me. But like that, like that, whyswyx: is this ridiculous? Say competitor launch, this may not work out. It wasSimon Hørup Eskildsen: more just like. If this doesn't work out, I'm gonna close up shop by the end of the mo the year, right?Like it was, I don't know, maybe it's common. I, I don't know. He told me it was uncommon. I don't know. Um, that's why we chose him and he'd been phenomenal. The other people were talking at the, at the time were database experts. Like they, you know, knew a lot about databases and Locke didn't, this turned out to be a phenomenal asset.Right. I like Justine and I know a lot about databases. The people that we hire know a lot about databases. What we needed was just someone who didn't know a lot about databases, didn't pretend to know a lot about databases, and just wanted to help us with candidates and customers. And he did. Yeah. And I have a list, right, of the investors that I have a relationship with, and Lockey has just performed excellent in the number of sub bullets of what we can attribute back to him.Just absolutely incredible. And when people talk about like no ego and just the best thing for the founder, I like, I don't think that anyone, like even my lawyer is like, yeah, Lockey is like the most friendly person you will find.swyx: Okay. This is my most glow recommendation I've ever heard.Alessio: He deserves it.He's very special.swyx: Yeah. Yeah. Yeah. Okay. Amazing.Alessio: Since you mentioned candidates, maybe we can talk about team building, you know, like, especially in sf, it feels like it's just easier to start a company than to join a company. Uh, I'm curious your experience, especially not being n SF full-time and doing something that is maybe, you know, a very low level of detail and technical detail.Simon Hørup Eskildsen: Yeah. So joining versus starting, I never thought that I would be a founder. I would start with it, like Turbo Puffer started as a blog post, and then it became a project and then sort of almost accidentally became a company. And now it feels like it's, it's like becoming a bigger company. That was never the intention.The intentions were very pure. It's just like, why hasn't anyone done this? And it's like, I wanna be the, like, I wanna be the first person to do it. I think some founders have this, like, I could never work for anyone else. I, I really don't feel that way. Like, it's just like, I wanna see this happen. And I wanna see it happen with some people that I really enjoy working with and I wanna have fun doing it and this, this, this has all felt very natural on that, on that sense.So it was never a like join versus versus versus found. It was just dis found me at the right moment.Alessio: Well I think there's an argument for, you should have joined Cursor, right? So I'm curious like how you evaluate it. Okay, I should actually go raise money and make this a company versus like, this is like a company that is like growing like crazy.It's like an interesting technical problem. I should just build it within Cursor and then they don't have to encrypt all this stuff. They don't have to obfuscate things. Like was that on your mind at all orSimon Hørup Eskildsen: before taking the, the small check from Lockie, I did have like a hard like look at myself in the mirror of like, okay, do I really want to do this?And because if I take the money, I really have to do it right. And so the way I almost think about it's like you kind of need to ha like you kind of need to be like fucked up enough to want to go all the way. And that was the conversation where I was like, okay, this is gonna be part of my life's journey to build this company and do it in the best way that I possibly can't.Because if I ask people to join me, ask people to get on the cap table, then I have an ultimate responsibility to give it everything. And I don't, I think some people, it doesn't occur to me that everyone takes it that seriously. And maybe I take it too seriously, I don't know. But that was like a very intentional moment.And so then it was very clear like, okay, I'm gonna do this and I'm gonna give it everything.Alessio: A lot of people don't take it this seriously. But,swyx: uh, let's talk about, you have this concept of the P 99 engineer. Uh, people are 10 x saying, everyone's saying, you know, uh, maybe engineers are out of a job. I don't know.But you definitely see a P 99 engineer, and I just want you to talk about it.Simon Hørup Eskildsen: Yeah, so the P 99 engineer was just a term that we started using internally to talk about candidates and talk about how we wanted to build the company. And you know, like everyone else is, like we want a talent dense company.And I think that's almost become trite at this point. What I credit the cursor founders a lot with is that they just arrived there from first principles of like, we just need a talent dense, um, talent dense team. And I think I've seen some teams that weren't talent dense and like seemed a counterfactual run, which if you've run in been in a large company, you will just see that like it's just logically will happen at a large company.Um, and so that was super important to me and Justine and it's very difficult to maintain. And so we just needed, we needed wording for it. And so I have a document called Traits of the P 99 Engineer, and it's a bullet point list. And I look at that list after every single interview that I do, and in every single recap that we do and every recap we end with.End with, um, some version of I'm gonna reject this candidate completely regardless of what the discourse was, because I wanna see people fight for this person because the default should not be, we're gonna hire this person. The default should be, we're definitely not hiring this person. And you know, if everyone was like, ah, maybe throw a punch, then this is not the right.swyx: Do, do you operate, like if there's one cha there must have at least one champion who's like, yes, I will put my career on, on, on the line for this. You know,Simon Hørup Eskildsen: I think career on the line,swyx: maybe a chair, butSimon Hørup Eskildsen: yeah. You know, like, um, I would say so someone needs to like, have both fists up and be like, I'd fight.Right? Yeah. Yeah. And if one person said, then, okay, let's do it. Right?swyx: Yeah.Simon Hørup Eskildsen: Um. It doesn't have to be absolutely everyone. Right? And like the interviews are always the sign that you're checking for different attributes. And if someone is like knocking it outta the park in every single attribute, that's, that's fairly rare.Um, but that's really important. And so the traits of the P 99 engineer, there's lots of them. There's also the traits of the p like triple nine engineer and the quadruple nine engineer. This is like, it's a long list.swyx: Okay.Simon Hørup Eskildsen: Um, I'll give you some samples, right. Of what we, what we look for. I think that the P 99 engineer has some history of having bent, like their trajectory or something to their will.Right? Some moment where it was just, they just, you know, made the computer do what it needed to do. There's something like that, and it will, it will occur to have them at some point in their career. And, uh. Hopefully multiple times. Right.swyx: Gimme an example of one of your engineers that like,Simon Hørup Eskildsen: I'll give an eng.Uh, so we, we, we launched this thing called A and NV three. Um, we could, we're also, we're working on V four and V five right now, but a and NV three can search a hundred billion vectors with a P 50 of around 40 milliseconds and a p 99 of 200 milliseconds. Um, maybe other people have done this, I'm sure Google and others have done this, but, uh, we haven't seen anyone, um, at least not in like a public consumable SaaS that can do this.And that was an engineer, the chief architect of Turbo Puffer, Nathan, um, who more or less just bent this, the software was not capable of this and he just made it capable for a very particular workload in like a, you know, six to eight week period with the help of a lot of the team. Right. It's been, been, there's numerous of examples of that, like at, at turbo puff, but that's like really bending the software and X 86 to your will.It was incredible to watch. Um. You wanna see some moments like that?swyx: Isn't that triple nine?Simon Hørup Eskildsen: Um, I think Nathan, what's calledAlessio: group nine, that was only nine. I feel like this is too high forSimon Hørup Eskildsen: Nathan. Nathan is, uh, Nathan is like, yeah, there's a lot of nines. Okay. After that p So I think that's one trait. I think another trait is that, uh, the P 99 spends a lot of time looking at maps.Generally it's their preferred ux. They just love looking at maps. You ever seen someone who just like, sits on their phone and just like, scrolls around on a map? Or did you not look at maps A lot? You guys don't look atswyx: maps? I guess I'm not feeling there. I don't know, butSimon Hørup Eskildsen: you just dis What about trains?Do you like trains?swyx: Uh, I mean they, not enough. Okay. This is just like weapon nice. Autism is what I call it. Like, like,Simon Hørup Eskildsen: um, I love looking at maps, like, it's like my preferred UX and just like I, you know, I likeswyx: lotsAlessio: of, of like random places, soswyx: like,youswyx: know.Alessio: Yes. Okay. There you go. So instead of like random places, like how do you explore the maps?Simon Hørup Eskildsen: No, it's, it's just a joke.swyx: It's autism laugh. It's like you are just obsessed by something and you like studying a thing.Simon Hørup Eskildsen: The origin of this was that at some point I read an interview with some IOI gold medalistswyx: Uhhuh,Simon Hørup Eskildsen: and it's like, what do you do in your spare time? I was just like, I like looking at maps.I was like, I feel so seen. Like, I just like love, like swirling out. I was like, oh, Canada is so big. Where's Baffin Island? I don't know. I love it. Yeah. Um, anyway, so the traits of P 99, P 99 is obsessive, right? Like, there's just like, you'll, you'll find traits of that we do an interview at, at, at, at turbo puffer or like multiple interviews that just try to screen for some of these things.Um, so. There's lots of others, but these are the kinds of traits that we look for.swyx: I'll tell you, uh, some people listen for like some of my dere stuff. Uh, I do think about derel as maps. Um, you draw a map for people, uh, maps show you the, uh, what is commonly agreed to be the geographical features of what a boundary is.And it shows also shows you what is not doing. And I, I think a lot of like developer tools, companies try to tell you they can do everything, but like, let's, let's be real. Like you, your, your three landmarks are here, everyone comes here, then here, then here, and you draw a map and, and then you draw a journey through the map.And like that. To me, that's what developer relations looks like. So I do think about things that way.Simon Hørup Eskildsen: I think the P 99 thinks in offs, right? The P 99 is very clear about, you know, hey, turbo puffer, you can't run a high transaction workload on turbo puffer, right? It's like the right latency is a hundred milliseconds.That's a clear trade off. I think the P 99 is very good at articulating the trade offs in every decision. Um. Which is exactly what the map is in your case, right?swyx: Uh, yeah, yeah. My, my, my world. My world.Alessio: How, how do you reconcile some of these things when you're saying you bend the will the computer versus like the trade

Send a textYour mind keeps insisting there isn't enough: not enough time, not enough space, not enough money, not enough safety. We slow that whole reflex down and look at a line from A Course in Miracles that cuts straight through it: “The miracle abolishes the need for lower order concerns.” Not the circumstances. The need. The inner urgency that makes the world feel like a threat.We explore what “lower order concerns” really are (schedules, health anxiety, finances, logistics, status, outcomes) and why the miracle is a perceptual correction rather than a form-level fix. From there we move into the Course's radical view of time and space: a miracle is “out of pattern,” not logically caused by the past, which means the script can break. When we choose right-mindedness, we stop treating limitation as primary, and the next practical step becomes cleaner, calmer, and often surprisingly obvious.We also unpack the essential distinction between what is created (eternal spirit) and what is made (the body, the world, identity stories), plus a sharp warning for every would-be miracle worker: never confuse right-mindedness with wrong-mindedness. If we meet miscreation with anything but a desire to heal, we reinforce the confusion. The miracle denies the error and affirms the truth, without repression and without spiritual bypassing.If you want grounded spiritual practice, forgiveness that actually reduces fear, and a more peaceful relationship with “not enough,” press play. Subscribe, share this with a friend who's drowning in urgency, and leave a review with the one lower order concern you're ready to release.Support the show

Audio, eng_t_norav_2026-03-12_lesson_achana-le-kenes_n1_p3. Lesson_part :: Lessons_series. Principles of Spiritual Work in the Top Ten :: Daily_lesson 1

Video, eng_t_norav_2026-03-12_lesson_achana-le-kenes_n1_p3. Lesson_part :: Lessons_series. Principles of Spiritual Work in the Top Ten :: Daily_lesson 1

Principles of Spiritual Work in the Top Ten

Kenneth Batcheldor was a British clinical psychologist who, during the final two decades of his life, investigated the paranormal through direct experiments in table-turning. The final fruit of that work was an essay, compiled from Batcheldor's notebooks by Patric Giesler, entitled “Notes on the Elusiveness Problem in Relation to a Radical View of Paranormality.” Published in the Journal of the American Society for Psychical Research in 1994, it remained unknown to JF and Phil until Shannon Taggart called their attention to it quite recently. Since the theory Batcheldor presents here with admirable lucidity is deeply attuned to ideas they have been discussing on Weird Studies for nearly a decade, they decided to devote an episode to it. The core idea is by far the weirdest of all—in a sense, it is the weird itself. Read Batcheldor's essay on the Weird Studies Patreon. Visit Weirdosphere to enroll in Phil's upcoming 5-week course, "A Musical Tarot." Pierre-Yves Martel's Weird Studies: Volume 3 will be available for preorder on March 13. Visit his Bandcamp page for details. REFERENCES K. M. Wehrstein, “Kenneth Batcheldor” in Psi Encyclopedia   Kenneth Batcheldor, “Notes on the Elusiveness Problem in Relation to a Radical View of Paranormality,” ed. Patric Giesler, The Journal of the American Society for Psychical Research 88, no. 2 (1994): 90-116.  Kenneth Batcheldor, “Contributions to the Theory of PK Induction from Sitter-Group Work,” Journal of the American Society for Psychical Research 78 (1984): 105-122.  George P. Hansen, The Trickster and the Paranormal  Quintin Meillassoux, After Finitude  Joshua Ramey, “Contingency Without Reason: Speculation after Meillassoux”  Kenneth Batcheldor, Videos of Table Tipping  Weird Studies, Episode 24 with Lionel Snell  David Lynch, Wild at Heart  William James, The Principles of Psychology Tom Cheetham, Imaginal Love  A. Irving Hallowell, Ojibwa Ontology, Behavior, and World View  Learn more about your ad choices. Visit megaphone.fm/adchoices

We've discussed healthy habits, desire and interception, but now is the time to focus our artist eyes! This week on Schauer Thoughts we're going over an abridged understanding of design elements and factors to consider when creating your own course curriculum. I strongly encourage mood boarding this episode but taking notes or just listening are fine as well. Enough chit chat - to the communal Schauer we go! My Substack Post: How To Start Researching as a Hobby https://substack.com/home/post/p-168506463  Resources to Learn for Fun & Free (or Fun & Free) https://substack.com/home/post/p-175242020  I also give tips on how to create your own “syllabus” with these resources.  Resources: Ruth Asawa and the Artist-Mother at Midcentury - Jordan Troeller To Photograph Is To Learn How To Die - Tim Carpenter Sin and Syntax: How to Craft Wickedly Effective Prose - Constance Hale The Story Grid: What Good Editors Know  - Shawn Coyne Bargaining for Advantage: Negotiation Strategies for Reasonable People - G. Richard Shell This Is What It Sounds Like - Susan Rogers and Ogi Ogas The Psychology of Fashion - Carolyn Mair Your Brain on Art - Susan Magsamen and Ivy Ross Breath: The New Science of a Lost Art - James Nestor This is the book on breathing I was talking about. Decisionscape: How Thinking Like an Artist Can Improve Our Decision-Making - Elspeth Kirkman I also wanted to recommend this book for understanding the importance of “word tense” when it comes to internal thoughts and rumination - I cannot stress this enough. She goes through first person, third, active, passive - language really does shape a lot of our decisions and life.  Visual Thinking: The Hidden Gifts of People Who Think In Pictures, Patterns, and Abstractions - Temple Grandin  The Activism of Art: A Decentered Anthology - Dipti Desai and Stephen Duncombe The Knowledge Illusion: Why We Never Think Alone - Steven Sloman and Philip Fernbach  The 7 Principles of Design and How To Use Them (w/ Infographic)  https://www.vistaprint.com/hub/principles-of-design#:~:text=The%20principles%20of%20design%20are,Proportion%2C%20Movement%20and%20White%20Space Not sponsored by Vistaprint lol Chronic Back Pain Makes the World Sound Harsher https://neurosciencenews.com/chronic-pain-sound-sensitivity-30237/  Scientists have found a fascinating link between breathing and memory https://www.psypost.org/scientists-have-found-a-fascinating-link-between-breathing-and-memory/ Nature Exposure Triggers Brain Reset   https://neurosciencenews.com/nature-brain-reset-30204/ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Discovering Your Life and Career Map. Join us on A New Direction for an exploration of the mental frameworks that define a successful life and career map. We are sitting down with Ed Hajim, author of The Island of the Four Ps, to dissect the structural philosophy behind his modern-day fable that is your life and work map. This session isn't about the past; it's about the mechanics of the future. We will focus entirely on the inner workings of the “Four Ps”—Passions, Principles, Partners, and Plans—and how these four distinct pillars interact to create a stable foundation for any ambitious journey for your life and career. The core of our discussion will center on the protagonist Marketus's arrival at the Four Capes, where the abstract becomes concrete on your life and career map. We'll examine why Passions are the fuel, but Principles are the engine that keeps you on course. Ed will explain how to distinguish between fleeting interests and the deep-seated drives that can sustain a lifelong career. We'll challenge the idea that success is a solo endeavor by analyzing the “Partner” quadrant, looking at how to identify the right collaborators who align with your internal compass. Planning is often where the best intentions fall apart, and we intend to spend significant time on the “Plans” aspect of the book. We will discuss the balance between rigid discipline and the flexibility required to survive “The Forest of Choices.” This conversation is designed to be a technical deep-dive into the book’s logic, offering listeners a literal life and career map for their own decision-making processes. If you've ever felt like your goals were missing a cohesive structure, this live stream will provide the blueprints you need to build a more intentional life. This is a unique opportunity to see the “Four Ps” framework applied to the complexities of the our modern world, and the life and career map we need to find our way. Whether you are navigating a major transition or simply looking to refine your daily output, the principles found on Ed's metaphorical island offer a universal language for achievement. Prepare to shift your perspective from wandering around your life and career map to winning. Ed Hajim’s book, ” The Island of the Four Ps: A Modern Fable About Preparing for Your Future” is a fun, insightful quick read that brings life to all of our journey in finding our life and career map.  He lays out for us in this fable featuring Marketus that we need to dig deep into ourselves in order for us to find our place. This fable asks us to look at four areas of our life: Our Passions, Principles, Partners, and Plans.  And as we take the deep dive into discovering them we must all recognize that is is not easy, it can be more complicated than we think, and things often will change.  But then we have to look at them and how each of these intersect with our self, family, work and community. The book may sound like it is for the very young, high school etc.  However, this book is for everyone in any stage of life.  It begs us to take an inventory of ourselves, regardless of our stage of life and start asking the hard questions that can change us.  One of the biggest take-aways is this: It is not an overnight process.  In fact, is a life long journey that we will return to again and again as we discover new things about ourselves and our different environments. Fabulous read.  This was not a book I would typically read, but I am so glad I did.  Even being what I might term stable in my career, I found that the Ideas and Question after the chapters challenged me to rethink about myself, where I am at on my career and life road map, and where I am heading and where I may go next. Get your copy of The Island of the Four Ps by clicking here. Please say thank you to our sponsors of A New Direction: Linda Craft Team, Realtors, they have been serving people in the real estate world for more than 40 years. And in so doing their customers rave about them, by saying they have “legendary customer service”. When you have customers from more than 40 years ago still stopping in to say “hello” and “thank you” that says there is something special about Linda and her dedication to her clients and her team. When you are ready to sell or buy why not start with Linda Craft & Team, www.LindaCraft.com Here is the truth: You tune into A New Direction because you want to grow. But consuming content and executing strategy are two different things. If you are leading a company between $5M and $50M and you feel like you are hitting a ceiling, the problem isn't a lack of information. It's likely a “human” bottleneck. I am Coach Jay, a Behavioral Strategist who specializes in fixing the friction that kills profit. I don't just look at your P&L; I look at the psychology of the people driving it. I recently helped a stalled mid-market firm save $3 Million and secure new capital—not by firing people, but by realigning their behavior. Stop guessing. Let's find the millions trapped in your org chart. Reach out for a discreet conversation: 919-369-2121 or visit TheCoachJay.com.

Communication is a major challenge in any relationship. FAMILY: SPOUSE, CHILDREN, PARENTS.FRIENDSHIPS: COMMUNICATION CAN BE EASILY MISUNDERSTOOD. WORKPLACE: TECHNOLOGY IS HOW SO MUCH COMMUNICATION IS DONE; SO THESE WAYS VIA TEXTING OR EMAIL CAN BE TERRIBLY MISUNDERSTOOD. CHURCH: MAY BE ONE OF THE PLACES AND PEOPLE WHERE COMMUNICATION IS MANY TIMES INEFFECTIVE AND CHALLENGING. Often, our communication with God is also ineffective and transactional. However, our communication with God should be meaningful and transformative. 

Audio, eng_t_norav_2026-03-11_lesson_achana-le-kenes_n1_p3. Lesson_part :: Daily_lesson 1 :: Lessons_series. Principles of Spiritual Work in the Top Ten

Video, eng_t_norav_2026-03-11_lesson_achana-le-kenes_n1_p3. Lesson_part :: Daily_lesson 1 :: Lessons_series. Principles of Spiritual Work in the Top Ten

Principles of Spiritual Work in the Top Ten

Seventh lecture of Principles of Economics explores technology as non-scarce knowledge that raises productivity and drives long-term growth, explaining why innovation creates new work instead of destroying it, and examining the economic arguments surrounding intellectual property.Get all course notes and slides on saifedean.com/poecourse

ResourcesEpisode 232.  5 Principles to Manage Contact Between Homes and Promote Your Child's WellbeingArticle from Navesink Wellness Center:  When Your Child Becomes Your Confidant:  The Trap of Emotional SafetyEpisode 161.  How do Healthy Parent/Child Roles Help Avoid the Pitfalls of Parentification? [with Ron Deal & Lauren Reitsema]Episode 229. The Heavy Burdens Kids Carry: Loyalty Binds, Parental Allegiance, and How to Help  Episode 84. How to Cope with Sadness, Anxiety, and Longing While Your Kids are GoneSuggest a Topic or Ask a Question  Would you like us to discuss something specific or answer your question on the show?  Let us know!We've made it easy.  Just click here:  https://www.blendedfamilybreakthrough.com/shareReady for some extra support?We all need some extra support along the blending journey — we're here to help.  You can connect with us for a free coaching call to see how we might help you experience more clarity, confidence and connection in your home.  Schedule your free call here:  https://www.blendedfamilybreakthrough.com/free-callSubscribe or Follow the Show Are you subscribed or following the podcast yet?  If not, we want to encourage you to do that today so you don't miss a single episode.  Click here to subscribe in Apple PodcastsClick here to follow on SpotifyLeave a Review in Apple PodcastsIf you're feeling extra helpful, we would be so grateful if you left us a review over on Apple Podcasts too. Your review will help others find our podcast — plus they're fun for us to read too! :-)  Just click here to Review, select “Ratings and Reviews” and then select “Write a Review” — let us know what your favorite part of the podcast is.  Thank you, we really appreciate your feedback!

Today I discuss Daggerheart's GM Principles, which are begin and end with the fiction (story); collaborate at all times, especially during conflict; fill the world with life, wonder, and danger; ask questions and incorporate the answers; make every roll important; play to find out what happens; and hold on gently. I talk quite a bit about why you don't want to call for too many rolls, and how to know when to call for a roll versus when not to. I specifically discuss the two main areas where some GMs call for way too many rolls: actions involving perception and knowledge. I also go into preparing for an adventure or game session by creating an inciting event to kick things off, and not planning too much beyond that point. I also share how I prepare to improvise. Finally, I talk a bit about advancing and modifying my setting of Primordia. I originally designed the setting for D&D, so I wanted to make some changes to better fit Daggerheart and allow the players more design space to collaborate with the world building.Play Daggerheart with Me on Start Playing Games.Sign up for my newsletter.Subscribe via RSS, Apple Podcasts, or Spotify.Check out my sci-fi novel, Critical Balance.Have you read Critical Balance? Please leave a review on Amazon.Follow me on Bluesky.Join my Discord server.Email me.Check out my YouTube channel.Join my Book Club, now on Discord.Check Out my OTHER PODCAST - Lex Out LoudCall the Game Master's Journey voice mail: 951-GMJ-LEX1 (951-465-5391).

Did you like the episode? Send me a text and let me know!! How to Validate Your Business Idea Without Building a Single ThingEver had a "billion-dollar idea" only to have it flop at launch? In this episode, we pull back the curtain on why most startups fail and—more importantly—how you can ensure yours doesn't. We're exploring the frameworks of Alberto Savoia, Strategizer, and Rob Fitzpatrick to help you find the truth before you spend a dime on engineering.Key Timestamps:[00:01:30] The FLOP Framework: Why failure is usually about the Premise, not the Launch or Operation.[00:03:30] The Mom Test: Why your friends are lying to you and how to fix it through Pathological Approval Seeking (PAOS) awareness.[00:04:45] Three Rules for Customer Discovery: How to talk about life, not ideas.[00:07:30] Feasibility vs. Desirability: Why the "Can we build it?" question should always come second.[00:10:45] Pretotyping with an "E": Defining YODA (Your Own Data) and skin in the game.[00:11:30] The Fake Door Method: Testing demand for $20 with a "Buy Now" button.[00:13:30] The Facade Method: Lessons from the Zappos origin story.[00:15:30] The Mechanical Turk: How "Josh Bot" saved $500k by using a human in a box.[00:17:30] Guerrilla Validation: The IKEA "Wall Hub" story and testing physical products.[00:22:30] The Ego Trap: Why we use complex engineering to hide from rejection.Featured Books & Resources:"The Mom Test" by Rob Fitzpatrick: The gold standard for customer conversations.Alberto Savoia (Stanford Seminars): The creator of Pretotyping and the Law of Market Failure.The Lean Startup Methodology: Foundational principles for validated learning.Strategizer (Alexander Osterwalder): Tools for testing business models and desirability.The Law of Market Failure: Most products fail because the market doesn't care (Premise failure).Pretotyping vs. Prototyping: A pretotype tests if you  Reclaim your "zone of genius" by letting Opus Clip automatically turn your long-form podcast into dozens of viral-ready shorts—start your free trial today at podnationopus.com For a 15% discount on your first purchase go RYZEsuoerfoods.com use code PODNA15 Thank you for being a Skoobeliever!! If you have questions about the show or you want to be a guest please contact me at one of these social mediasTwitter......... ..@djskoob2021 Facebook.........Facebook.com/skoobamiInstagram..... instagram.com/uepodcast2021tiktok....... @djskoob2021Email............... Uepodcast2021@gmail.com Skoob at Gettin' Basted Facebook PageAcross The Start Line Facebook Community Find out what one of the four hurdles of stop is affecting you the most!!Black Friday coaching Sale now!! 65% off original price! go to stan.store/skoob to book your appointment and take advantage of this limited time offer! On Twitter @doittodaycoachdoingittodaycoaching@gmailcom

What's the actual difference between sensation and perception? And why does the MCAT test it so heavily?In this Jack Westin MCAT Podcast episode, Mike and Molly break down one of the most commonly confused topics in psych/soc: sensation vs. perception. They walk through the key definitions, thresholds, theories, and perceptual principles you need to know, all with real-world examples, MCAT applications, and even a few optical illusions to prove how easily your brain can be tricked.In this episode, you'll learn:

Discover all of the podcasts in our network, search for specific episodes, get the Optimal Living Daily workbook, and learn more at: OLDPodcast.com. Episode 3320: Ross Enamait challenges the obsession with structured routines by showing how instinct-driven outdoor training can build real-world strength and mental freshness. By turning nature into a functional gym, he demonstrates that intensity and effort matter far more than counting sets and reps. His perspective encourages you to trust your body, embrace simplicity, and rediscover the freedom and effectiveness of training beyond the confines of four walls. Read along with the original article(s) here: http://rosstraining.com/blog/2014/04/beyond-sets-and-reps/ Quotes to ponder: "Training outside without specific parameters allows me to stay fresh both physically and mentally." "Pull-ups from thick tree branches will strengthen the hands unlike any conventional gym exercise." "In summary, there is nothing wrong with performing a specific routine, but there is more to training than blindly following what is written on paper." Learn more about your ad choices. Visit megaphone.fm/adchoices

In this special broadcast, Nichel Anderson pulls back the veil on 20 years of creative mastery in her Manifesto journey on MOLIAE.com. This is more than a story; it is a live demonstration of completion. From the ancient MA'at principles infused in MOLIAEBeauty.com to the immutable smart contracts of the PMTR NFTs, the infrastructure of a new world is already ready and moving forward towards destinies. Listen as Nichel invites you to leap beyond the middleman and connect to a reciprocal ecosystem of giving and receiving. The timeline is now. We are the Portal.   Nichel Manifesto | https://moliae.com/production/nichel-anderson-manifesto/ Nichel's Music Album | https://moliae.com/song/moliae-music-album/ Brand of MOLIAE MOLIAE.com MOLIAEBeauty.com MOLIAEWorld.com MINT.MOLIAEWorld.com   Show Notes & Timeline: 0:00 – Opening Frequency 0:14 – The Sovereign Prayer 1:00 – The 20-Year Journey to Mastery 1:26 – MA'at Principles in Commerce: MOLIAEBeauty.com 1:33 – Digital Sovereignty: Ethereum Blockchain & PMTR NFTs 1:45 – The Sound of Completion: My Music Album 2:08 – Coded Destiny: The Symbols of PMTR 3:00 – The Leap: Why We are the Portal Thank you!

http://www.CoachMikeD.com Subscribe: Apple Podcasts: https://podcasts.apple.com/us/podcast/impact-and-fulfillment-with-coach-mike-d/id1230596918 Spotify: https://open.spotify.com/show/4oNGxgmdwaTOpWwdf1BGyR#:~:text=Listen%20to%20Impact%20and%20Fulfillment%20with%20Coach%20Mike,practical%20wisdom%20for%20an%20authentic%20life%20of%20purpose. YouTube: https://www.youtube.com/@coachmiked

Tune in as host Nichel, shares an update on her journey that success is not a destination; it is a state of Sovereignty in her Manifesto. In this episode, entrepreneur and creative director Nichel Anderson breaks down the "MOLIAE Mothership" strategy for Direct-to-Consumer (DTC) success. After decades of seeding, the direct alignment is here. Nichel has built the Portal herself over these years and all platforms are open and ready from MOLIAE.com to MOLIAEBeauty.com of the MA'at Principles and from MOLIAEWorld.com of Digital expression to Mint.MOLIAEWorld.com on the Ethereum blockchain, the mothership is tuning into this new wave frequency DTC movement. Explore the link to the MOLIAE Manifesto and learn how to connect to a community-driven model that bypasses the "decision loops" of the old guard.   ✨ THE PORTAL IS OPEN – TAKE THE LEAP:  

In this episode, I'm tackling a common source of confusion in the yoga industry: when teaching methods get mistaken for anatomical/movement principles. Many yoga teachers hear cues or “rules” about certain poses — things like “don't put your foot on the side of your knee in Tree Pose” or “you shouldn't square your hips in Warrior 1 because that forces the hips into an uncomfortable position.” But often these statements aren't well grounded in anatomy or movement science. Instead, they reflect a particular teacher's style, preference, or interpretation of how a pose should be taught. Or, they might simply reflect a lack of anatomical knowledge on the part of the teacher. In this episode, I share why it's important to distinguish between evidence-based anatomy principles and teaching methodology, and why asking “why?” is one of the most powerful tools a teacher can use when evaluating cues and alignment advice. If you've ever heard conflicting guidance about poses and wondered what's actually true, this episode will help you think about anatomy, movement, and cueing with more clarity and confidence.   In the episode, I also speak about how I worked with a yoga teacher to help her get clear on how she wants to teach. This happened inside the Accelerator Program. Here's the link:   https://barebonesyoga.thinkific.com/courses/Yoga-Anatomy-Accelerator   Feel free to reach out to me on IG with any thoughts to share after you listen to the episode.

Discover all of the podcasts in our network, search for specific episodes, get the Optimal Living Daily workbook, and learn more at: OLDPodcast.com. Episode 3320: Ross Enamait challenges the obsession with structured routines by showing how instinct-driven outdoor training can build real-world strength and mental freshness. By turning nature into a functional gym, he demonstrates that intensity and effort matter far more than counting sets and reps. His perspective encourages you to trust your body, embrace simplicity, and rediscover the freedom and effectiveness of training beyond the confines of four walls. Read along with the original article(s) here: http://rosstraining.com/blog/2014/04/beyond-sets-and-reps/ Quotes to ponder: "Training outside without specific parameters allows me to stay fresh both physically and mentally." "Pull-ups from thick tree branches will strengthen the hands unlike any conventional gym exercise." "In summary, there is nothing wrong with performing a specific routine, but there is more to training than blindly following what is written on paper." Learn more about your ad choices. Visit megaphone.fm/adchoices

LISTEN and SUBSCRIBE on:Apple Podcasts: https://podcasts.apple.com/us/podcast/watchdog-on-wall-street-with-chris-markowski/id570687608 Spotify: https://open.spotify.com/show/2PtgPvJvqc2gkpGIkNMR5i WATCH and SUBSCRIBE on:https://www.youtube.com/@WatchdogOnWallstreet/featured  Too many people tie their identity to political parties instead of principles. When loyalty replaces critical thinking, truth becomes negotiable. Holding leaders accountable—regardless of party—is the only way a healthy democracy works. Never compromise your principles for politics.

Welcome to Season 2 of the Orthobullets Podcast.In this episode, we review the high-yield topic of ⁠⁠Biopsy Principles ⁠from the Pathology section.⁠Follow ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Orthobullets⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on Social Media:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠YouTube

Grace Giving, Week 1  Pastor Nathan Zickert · Psalm 24:1 A video recording of this sermon is available here. For more information about Grace Community Church of Riverside, visit us online at https://www.gccriverside.com.

Stephen speaks to Akhona Qengqe about her journey to leading KFC Africa, to Ian Mann about Ray Dalio’s Principles for Dealing with the Changing World Order, to Siphumelele Zondi about the fall of local streaming platforms and YouTube’s rise, and to Bret Dugmore about how Mr Vinyl is keeping South Africa’s physical music culture alive. The Money Show is a podcast hosted by well-known journalist and radio presenter, Stephen Grootes. He explores the latest economic trends, business developments, investment opportunities, and personal finance strategies. Each episode features engaging conversations with top newsmakers, industry experts, financial advisors, entrepreneurs, and politicians, offering you thought-provoking insights to navigate the ever-changing financial landscape.    Thank you for listening to a podcast from The Money Show Listen live Primedia+ weekdays from 18:00 and 20:00 (SA Time) to The Money Show with Stephen Grootes broadcast on 702 https://buff.ly/gk3y0Kj and CapeTalk https://buff.ly/NnFM3Nk For more from the show, go to https://buff.ly/7QpH0jY or find all the catch-up podcasts here https://buff.ly/PlhvUVe Subscribe to The Money Show Daily Newsletter and the Weekly Business Wrap here https://buff.ly/v5mfetc The Money Show is brought to you by Absa     Follow us on social media   702 on Facebook: https://www.facebook.com/TalkRadio702 702 on TikTok: https://www.tiktok.com/@talkradio702 702 on Instagram: https://www.instagram.com/talkradio702/ 702 on X: https://x.com/CapeTalk 702 on YouTube: https://www.youtube.com/@radio702   CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/Radio702 CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

Tench Tilghman did not need a revolution. Yet he risked everything to help win the American Revolution. In this episode of America's Founding Series, discover the forgotten patriot who became George Washington's most trusted aide and carried the official victory dispatch from Yorktown to the Continental Congress. This is the untold story of Tench Tilghman, the wealthy Maryland merchant who chose conviction over comfort and helped secure America's independence. Go behind the scenes of the Continental Army headquarters, the fragile years under the Articles of Confederation, and the decisive moment at Yorktown that changed world history. Learn why Tilghman's loyalty, sacrifice, and refusal of compensation reveal a powerful lesson about character, leadership, and the survival of a republic. What You'll Learn: Why Tench Tilghman abandoned elite comfort to join the Revolutionary War How he became George Washington's trusted right hand The hidden administrative battle that sustained the American Revolution What really happened during the 300-mile ride announcing victory at Yorktown Why republics depend on disciplined, unseen servants of liberty

This sermon was preached by Dr. Timothy Keller at Redeemer Presbyterian Church on December 5, 1993. Series: Splendor in the Furnace: 1 Peter, Part 1. Scripture: 1 Peter 1:22-2:3. Today's podcast is brought to you by Gospel in Life, the site for all sermons, books, study guides and resources from Timothy Keller and Redeemer Presbyterian Church. If you've enjoyed listening to this podcast and would like to support the ongoing efforts of this ministry, you can do so by visiting https://gospelinlife.com/give and making a one-time or recurring donation.

In this message, Adrian Rogers reveals six positive principles to live by, and questions to ask ourselves for a proper daily practice of the Christian faith. To support this ministry financially, visit: https://www.oneplace.com/donate/135/29?v=20251111

In this message, Adrian Rogers reveals six positive principles to live by, and questions to ask ourselves for a proper daily practice of the Christian faith. To support this ministry financially, visit: https://www.oneplace.com/donate/135/29?v=20251111

This episode is an invitation to slow down and explore one of the most ancient and compassionate offerings ever given to humankind : the Four Noble Truths, as taught by the Buddha. Through gentle storytelling and spacious reflection, we walk through: The truth of suffering The origin of suffering The possibility of freedom And the path that leads there These teachings are not abstract philosophies. They are tender, powerful truths about being human, about the pain we all carry, and the peace we can all touch.   All Episodes can be found at ⁠⁠⁠⁠https://www.podpage.com/speaking-podcast/⁠⁠⁠   All about Roy / Brain Gym & Virtual Assistants at ⁠⁠⁠⁠https://roycoughlan.com/⁠⁠⁠⁠   #SylviaWolfer #speaker #griefhealing   Find the full Interview with Sylvia Wolfe    Bio of Sylvia Wolfer   Sylvia Wolfer is a neuroscience-informed mindfulness guide and grief educator. Her work bridges contemplative practice, nervous system regulation, and lived experience after profound loss. A long-term meditation practitioner, Sylvia has explored contemplative traditions for many years. After losing both of her parents and her two brothers, her practice deepened — becoming not just a spiritual discipline, but a steady anchor through grief. Today, she creates grounded, body-aware guided meditations designed to support people through emotional overwhelm, loss, and life transitions. Her approach integrates neuroscience, breath, and embodied awareness to help people build emotional steadiness without bypassing what hurts. Sylvia is the creator of several digital courses and guided meditation series, and she teaches weekly online sessions blending mindfulness and movement.   How to Contact Sylvia Wolfer    ⁠https://sylviawolfer.com/⁠   ⁠https://www.instagram.com/_sylvia_wolfer_grief_support/⁠   ⁠https://www.linkedin.com/in/sylviawolfer/⁠     All about Roy / Brain Gym & Virtual Assistants at ⁠⁠⁠⁠https://roycoughlan.com/⁠⁠⁠⁠    

This sermon was preached by Dr. Timothy Keller at Redeemer Presbyterian Church on November 28, 1993. Series: Splendor in the Furnace: 1 Peter, Part 1. Scripture: 1 Peter 1:22-2:3. Today's podcast is brought to you by Gospel in Life, the site for all sermons, books, study guides and resources from Timothy Keller and Redeemer Presbyterian Church. If you've enjoyed listening to this podcast and would like to support the ongoing efforts of this ministry, you can do so by visiting https://gospelinlife.com/give and making a one-time or recurring donation.

Rebecca Hinds: Your Best Meeting Ever Rebecca Hinds is a leading expert on organizational behavior and the future of work. She founded and led the Work Innovation Lab at Asana and the Work AI Institute at Glean, where she partners with leading experts to help organizations transform their work with AI. She is the author of Your Best Meeting Ever: 7 Principles for Designing Meetings That Get Things Done (Amazon, Bookshop)*. Considering the amount of time we all spend in meetings, it's odd that most organizations do so little to measure meeting results. If that's sounding familiar, this conversation between Rebecca and me will show you exactly how to get started. Key Points Metrics that only measure the costs of meetings (dollars and time) can be useful, but rarely capture the full picture. Use Return on Time Invested (ROTI) anonymously to survey attendees to determine if a meeting was a good use of time. Also ask, “What would it take for you to improve your rating by one point?” Survey sparingly to avoid survey fatigue. Bringing in a survey 10% of the time is a benchmark to start from. If the amount of time in meetings vastly exceeds 10 hours a week, there's likely an opportunity to scale back or redefine the work before or after meetings to use time better. Equal speaking time in meetings is a key indicator of team performance. Be transparent with employees about any technology you use to capture data. Punctuality and attendance rate are indicators of how valued meetings are for people. Resources Mentioned Your Best Meeting Ever: 7 Principles for Designing Meetings That Get Things Done by Rebecca Hinds (Amazon, Bookshop)* Interview Notes Download my interview notes in PDF format (free membership required). Related Episodes How to Lead Meetings That Get Results, with Mamie Kanfer Stewart (episode 358) Moving Towards Meetings of Significance, with Seth Godin (episode 632) How to Lead Engaging Meetings, with Jess Britt (episode 721) Discover More Activate your free membership for full access to the entire library of interviews since 2011, searchable by topic. To accelerate your learning, uncover more inside Coaching for Leaders Plus.