Podcast appearances and mentions of james allworth

Anthony Pompliano — investor, entrepreneur, and media powerhouse — returns four years and 228 episodes later to discuss his new book, How To Live an Extraordinary Life, a collection of 65 heartfelt letters to his two children. At just 36, Anthony has already invested in circa 200 companies, served in Iraq with the U.S. Army, built and sold multiple businesses, and created one of the world's largest independent media platforms. You don't accomplish all that without learning a thing or two, and in this episode we dig into his hard-earned insights — from the uniting traits of the world's smartest people, to the luxury of pessimism, to why luck isn't real. I hope you enjoy this conversation as much as I did. For the full transcript, episode takeaways, and bucketloads of other goodies designed to make you go, “Hmm, that's interesting!”, check out our Substack. Important Links: How To Live an Extraordinary Life Website Twitter The Pomp Letter Anthony's Previous Episode Show Notes: The hidden power of “I don't know” Why Anthony started writing letters to his children Today is practice for tomorrow Carve your ethics in stone, but your opinions in sand How bad positioning poisons decision-making Are there any parts of the book Anthony no longer believes in? What unites the smartest people in the world Why luck isn't real The luxury of pessimism Power laws everywhere! Anthony as Emperor of the World MORE! Books, Articles & Podcasts Mentioned: Adventures of a Bystander; by Peter F. Drucker The Art of Learning: An Inner Journey to Optimal Performance; by Josh Waitzkin How Will You Measure Your Life?: A thought-provoking approach to measuring life's success; by Clayton M. Christensen, James Allworth and Karren Dillon Rules for a Knight; by Ethan Hawke The Rise and Fall of American Growth: The U.S. Standard of Living since the Civil War; by Robert J. Gordon Why Writing Letters to Your Kids Is the Best Gift You Can Give Them as Adults; by Polina Pompliano Shane Parrish on the Clear Thinking podcast Lucky vs, Repeatable; by Morgan Housel What Kind of Lucky Are You?; by Jim O'Shaughnessy

Anne Chow demonstrates how embracing inclusion enhances performance and transforms workplaces. — YOU'LL LEARN — 1) Why busyness destroys opportunities 2) How inclusion boosts success 3) Why consensus is over-rated Subscribe or visit AwesomeAtYourJob.com/ep1002 for clickable versions of the links below. — ABOUT ANNE — As the former CEO of AT&T Business, Anne Chow was the first woman and first woman of color to hold the position of CEO at AT&T in 2019, overseeing more than 35,000 employees who collectively served 3 million business customers worldwide during her time there. She is currently the Lead Director on the board of Franklin Covey, serves on the board of 3M and CSX, and teaches at Northwestern University's Kellogg School of Management. • Book: Lead Bigger: The Transformative Power of Inclusion • Book: The Leader's Guide to Unconscious Bias: How To Reframe Bias, Cultivate Connection, and Create High-Performing Teams • LinkedIn: Anne Chow • Website: TheAnneChow.com — RESOURCES MENTIONED IN THE SHOW — • Book: How Will You Measure Your Life? by Clayton M. Christensen, James Allworth, Karen Dillon • Study: Women in the Workplace by LeanIn.Org and McKinsey & Company— THANK YOU, SPONSORS! — • Jenni Kayne. Use the code AWESOME15 to get 15% off your order!• LinkedIn Jobs. Post your job for free at LinkedIn.com/beawesomeSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Unlock the secrets to a life of purpose and fulfillment with How Will You Measure Your Life? by Clayton M. Christensen—a profound guide that marries business wisdom with personal growth. Read on your terms. Get the PDF, infographic, full ad-free audiobook and animated version of this summary of How Will You Measure Your Life? and unlimited bestselling book insights on the top-rated StoryShots app: https://www.getstoryshots.com/ ⭐️⭐️⭐️⭐️⭐️ Help us grow to create more amazing content for you! Don't forget to subscribe, rate and review the StoryShots podcast now.  What should our next book be? Suggest and vote it up on the StoryShots app. Get the audiobook for free: https://geni.us/how-you-measure-life StoryShots Book Summary and Review of How Will You Measure Your Life? By Clayton M. Christensen, James Allworth, and Karen Dillon Life moves fast. Has How Will You Measure Your Life? by Clayton M. Christensen, James Allworth, and Karen Dillon been lingering on your reading list? Let's dive into the key takeaways right now. We're just scratching the surface here. If you haven't yet grabbed this insightful book on self-help, personal development, or career advice, order it now or grab the audiobook for free and explore all the juicy details. Introduction Imagine living a life that's not just about financial success but also brimming with personal fulfillment and meaningful relationships. *How Will You Measure Your Life?* by Clayton M. Christensen, along with co-authors James Allworth and Karen Dillon, isn't just a book—it's a guide to living with purpose. Known for his pioneering work in business theory, Christensen uses his unique perspective to connect principles from his professional life to your personal journey. The wisdom in this book springs from Christensen's experiences as a Harvard Business School professor. It blends personal stories with deep business insights to help you chart a course for a balanced and satisfying life. Christensen's reflections, especially after facing a serious illness, led him to question what truly matters in life. Each chapter is crafted to help you navigate life's complexities—whether it's making career choices, handling family dynamics, or chasing happiness. It's all about aligning your actions with your core values and making strategic decisions that lead to lasting satisfaction. Whether you're at the beginning of your career or in the thick of it, this book offers relatable and transformative insights. Christensen's narrative encourages you to continuously evaluate your life's direction and make choices that align with your values and goals. Through engaging stories and practical advice, *How Will You Measure Your Life?* pushes you to redefine what success means and to live a life you can proudly reflect on. About Clayton M. Christensen Clayton M. Christensen was a giant in the world of business and academia. Born in 1952 in Salt Lake City, Utah, he later made significant contributions as a professor and researcher at Harvard University. After earning a BA in Economics from Brigham Young University and an MPhil in Applied Econometrics from Oxford University, he completed his academic journey with an MBA and DBA from Harvard Business School. Christensen's career was groundbreaking, particularly his work on disruptive innovation—a term he coined to explain how smaller companies can successfully challenge industry giants. His book, *The Innovator's Dilemma*, introduced this concept and became a foundational text in understanding technological change and business strategy. StoryShot 1: Discovering Your Purpose is Vital for a Fulfilling Life StoryShot 2: Translating Your Purpose into Actionable Strategies is Key StoryShot 3: Setting Priorities Helps Balance Career and Family Life Learn more about your ad choices. Visit megaphone.fm/adchoices

If you're a small or medium-sized business hoping that all the buzz about AI and other recent technological innovation will just die down without you having to do anything about it… well, you're already behind the 8-ball. The time to take advantage is now — or you risk being left behind quickly by your competition.   Our latest guest is someone who knows innovation — and how to use it — well. Trent Gillespie helps companies out-innovate Amazon, based on his 9 years as a senior leader there managing major global expansion and innovation programs, and his over 20 years of technical experience.    Tune into the full episode for more on the rapid evolution of AI in recent years, what businesses can do to stay ahead of the curve, how companies can build cultures of innovation internally, and a lot more.   Here's a Glimpse of What You'll Learn:    What Trent believes is one of the most valuable skills you can learn, especially in the face of technological development, AI, and more Some of the recent innovations in the AI space, and what they mean for the future of business The top use cases for AI in business, especially ChatGPT, and where small to medium-sized businesses can do now to take advantage of this technology Whether businesses should be worried about AI, and why Trent believes they really only have 5 years to respond to today's technological innovations How Trent has transformed his experience at Amazon into his current work now The one characteristic that every successful company should structure their business around  What “sustainable innovation” is, why it's so important for businesses to invest in, and why Amazon actually isn't great at this type of innovation How to create a culture that embraces innovation, and what that means for an organization's incentive programs Why innovation should factor prominently into your hiring strategy How Trent measures success in his own business, with his clients, and in his personal life Why Trent has shifted the measure of his happiness from simply money to quality of life   Resources Mentioned in This Episode:  Trent's company, Day One Innovation Trent Gillespie on LinkedIn “The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail (Management of Innovation and Change)” by Clayton M. Christensen “[Non] Human Intelligence: AI, Automation, and How Robots Will Make Us Better People” by Cesar Keller “Good to Great: Why Some Companies Make the Leap and Others Don't” by Jim Collins “How Will You Measure Your Life?” by Clayton Christensen, James Allworth, and Karen Dillon Buy a copy of “Lost at CEO: An Entrepreneur's Guide to Strategy” by Carl J. Cox  40 Strategy Contact 40 Strategy Carl J. Cox on LinkedIn  

Renata Faber, Head de ESG na Exame, é nossa convidada para iniciar a quinta temporada do Abrindo Caminhos: Caminhando para a Regeneração. Renata é, além de uma das maiores referências do Brasil em ESG, uma amiga, nós trabalhamos juntos há um tempo e hoje tenho a alegria de receber uma das pessoas mais influentes no conhecimento em sustentabilidade aqui no podcast. Com mais de 20 anos de experiência no mercado financeiro, migrou pra ESG para ajudar os investidores a investirem de acordo com seus princípios e as empresas se tornarem mais sustentáveis. Tivemos um papo leve e fluido, com muito conhecimento prático para quem se interessa por sustentabilidade, seja para trabalhar, se engajar ou entender porque o ESG é tão importante. Apresentado por Riq Lima, empreendedor social, CEO e cofundador da Worldpackers, eleito pela Veja um dos 10 jovens mais inspiradores do Brasil, palestrante do TEDx, além de ganhar prêmios como empreendedor Estadão, WYSE travel tech, também deu entrevistas ao Globo Repórter e The Washington Post. Apresentador e idealizador do Podcast Abrindo Caminhos, o podcast mais relevante em ESG do Brasil, com convidados como Marina Silva, Sidarta Ribeiro e muito mais. CITAÇÕES Nizan Guanaes - Embaixador da boa vontade da UNESCO BTG - Banking and Trading Group Renato Mimica - CEO Exame Exame - Revista brasileira Larry Fink - CEO da BlackRock All-In Podcast REDE SOCIAL Linkedin: Renata Faber - https://www.linkedin.com/in/renata-faber-03b38a17b/?originalSubdomain=br LIVROS How Will You Measure Your Life? - Clayton Christensen, James Allworth e Karen Dillon Impacto positivo: Como empresas corajosas prosperam dando mais do que tiram - Paul Polman e Andrew Winston Trailblazer: The Power of Business as the Greatest Platform for Change - Marc Benioff Let My People Go Surfing: The Education of a Reluctant Businessman - Yvon Chouinard A terra inabitável: Uma história do futuro - David Wallace-Wells Não deixe de conferir o site www.riqlima.com e me acompanhar no Instagram https://www.instagram.com/riqlima/. Edição do podcast + vídeo e roteiro por Fita Filmes https://youtube.com/fitafilmesbr Artes por Brunno Marques https://www.behance.net/brnn

About Joe :Growing up, I was just your average kid. It wasn't until high school that I realized I had no direction and no plan for my life. So, after I graduated high school, I joined the United States Marine Corps where I spent 5 years learning life lessons of discipline, raising the standards I hold myself too and a commitment to excellence.When I transitioned out of the USMC I embarked on a new journey in the Network Marketing space. Here, I found myself learning people skills, tools to create change for people and myself and ultimately how to create results. There was just one problem….I was stuck in self-sabotaging patterns that destroyed my relationships because of insecurities. I was emotionally unstable and I had no clue what made me happy and ultimately….I didn't love myself at all. I was far from being a positive example for anyone. I knew I wanted more out of life. I knew there had to be more. I hit a breaking point.With nothing else to lose, I started investing the little resources I had into mentorship, hiring coaches and feeding my brain every day.I was suffering and knew I had to make changes if I wanted to go to the next level of life. I had to start mastering myself and not just toe-dipping around. As I developed the rituals and habits in my life that have taken me from victim to victor….I now live a truly blessed life. I built a 6 bedroom home that overlooks a golf course, have an amazing wife that I'm so in love with and a healthy son. Now, I know who I am, am constantly growing and I am beyond happy and fulfilled. I figured some things out along my journey and have now made it my mission to help others do the same. It's time to put an end to suffering and master life by design.Links From The Podcasthttps://www.masterlifebydesign.com/https://www.masterlifebydesign.com/podcast/https://www.facebook.com/MasterLifeByDesignhttps://twitter.com/MLBDTeamMoffetthttps://www.youtube.com/user/MasterLifeByDesignmasterlifebydesign@gmail.comhttps://www.peer2peerrealestate.com/@Willliamp2pre (twitter)facebook.com/peer2peerrealestatehttps://www.linkedin.com/in/williemorales/Book(s)RecommendedPersonal Power- Tony RobbinsRelentless- Tim GroverWho Not How- Dan Sullivan & Dr Benjamin Hardy How Will You Measure Your Life-Clayton Christensen, James Allworth, et al Untethered Soul-Michael Singer Thank you Joseph for being on the podcast.What did you think about today's subject?Please go to apple podcasts look for us at peer 2 peer real estate podcast, please subscribe and leave a review.Don't give up on your dreams, fight for it and guard it.Keep the momentum going, Good things will happen.Thanks for listening and be safe Hosted on Acast. See acast.com/privacy for more information.

In this episode, I'm sharing two of my favorite lessons from my current Founder's Book Club Book, “How Will You Measure Your Life?” by Clayton Christensen, James Allworth, and Karen Dillon.  Check out the full transcript at https://foundersjournal.morningbrew.com to learn more, and if you have any ideas for our show, email me at alex@morningbrew.com or my DMs are open @businessbarista.

In Episode 125, Quinn asks: How can venture capital offer solutions to two of the biggest problems of our time? His guests are Vida Asiegbu and Anthony Oni, two incredible climate venture capitalists with Elevate Future Fund. Vida Asiegbu is a Principal within the Elevate Future Fund, working to make sure that the companies and organizations that they represent within their portfolio meet all of their goals and values. Anthony Oni is the Managing Partner of the Elevate Future Fund, part of Energy Impact Partners, focused on creating a transition into clean energy through investments – while also building a more diverse, inclusive, and equitable future. Together, Vida and Anthony ask (and answer): How do we build new systems that help and support all people, as we face this incredible crisis (and opportunity)?  How do we approach the obligation we have to help others? How do we address the very personal – and very local – effects of climate change?  And how the hell do we find and invest in companies that are moving the needle in both directions? Today's episode is brought to you by Avocado Green Brands, where sustainability comes first. They craft their GOTS certified organic mattresses, pillows, and bedding with natural materials sourced from their organic farms in India, in their own clean-energy powered facility in Los Angeles, where their team shares a singular purpose: To raise the bar for what it means to be a sustainable business. Avocado is Climate Neutral Certified for net zero emissions and donates one percent of all revenue to environmental nonprofits through its membership with 1% For the Planet. https://www.avocadogreenmattress.com/?utm_medium=partner&utm_source=email&utm_campaign=INI_November (Find out what it means to sleep organic at AvocadoMattress.com). Have feedback or questions?http://www.twitter.com/importantnotimp ( Tweet us), or send a message to questions@importantnotimportant.com New here? Get started with our fan favorite episodes athttp://podcast.importantnotimportant.com ( podcast.importantnotimportant.com). Important, Not Important Book Club: https://bookshop.org/shop/importantnotimportant (“How Will You Measure Your Life?” by Clayton Christensen, Karen Dillon, and James Allworth) https://bookshop.org/shop/importantnotimportant (“Resisting Happiness” by Matthew Kelly) https://bookshop.org/shop/importantnotimportant (https://bookshop.org/shop/importantnotimportant) Links: https://www.energyimpactpartners.com/ (energyimpactpartners.com) https://www.linkedin.com/in/anthonyoni (linkedin.com/in/anthonyoni) https://www.linkedin.com/in/vidaasiegbu (linkedin.com/in/vidaasiegbu) https://propelcenter.org/ (propelcenter.org) Twitter: https://twitter.com/vidaasiegbuinc (@vidaasiegbuinc) Connect with us: Subscribe to our newsletter at http://newsletter.importantnotimportant.com (newsletter.importantnotimportant.com)! Follow us on Twitter: http://twitter.com/ImportantNotImp (twitter.com/ImportantNotImp) Follow Quinn: http://twitter.com/quinnemmett (twitter.com/quinnemmett) Like and share us on Facebook: http://facebook.com/ImportantNotImportant (facebook.com/ImportantNotImportant) Intro/outro by Tim Blane: http://timblane.com/ (timblane.com) Important, Not Important is produced by http://crate.media/ (Crate Media) Support this podcast

A wideranging convo with Sunil covering the future of React, the Third Age of JavaScript, and the Meta of online discourse.Watch on YouTube: https://www.youtube.com/watch?v=H3h1WICelqsFollow Sunil: https://twitter.com/threepointoneChapters: [00:01:40] React and Temporal, Declarative vs Imperative My Temporal Explainer: https://twitter.com/swyx/status/1417165270641045505 https://www.solidjs.com/  [00:12:57] State Charts and Lucylang https://lucylang.org/ XState and Stately https://stately.ai/viz [00:17:08] The Future of React [00:25:03] React Streaming Server Rendering vs SSR/JAMstack/DSG/DPR/ISR ReactDOMServer.renderToNodeStream() Sunil's Slides: https://www.icloud.com/keynote/0MyOJkDIOVfFit76PqJFLvPVg#react-advanced https://react-lazy.coolcomputerclub.com/  [00:33:13] Next.js and the Open Source Commons [00:38:46] The Third Age of JavaScript Third Age of JS  Benedict Evans (not Sinofsky) on Word Processors: https://www.ben-evans.com/benedictevans/2020/12/21/google-bundling-and-kill-zones [00:45:16] ESbuild vs SWC vs BunBun (Jarred Sumner) https://twitter.com/jarredsumner/status/1390084458724741121  [00:50:46] Let Non-X Do X: Figma vs Canva, Webflow vs Wix/Squarespace Canva vs Figma valuations https://twitter.com/swyx/status/1438102616156917767 [00:52:42] JavaScript Twitter and Notion's 9mb Marketing Site Notion 9mb JS Site Tweet mrmrs' Components.ai [01:06:33] React Server Components and Shopify Hydrogen/Oxygen https://twitter.com/swyx/status/1410103013885108229  [01:09:18] Categorical Imperatives of Web Platforms: Cloudflare vs AWS, MongoDB vs Auth0, Gatsby vs Netlify https://auth0.com/blog/introducing-auth0-actions/  [01:18:34] Wrap-up  Transcript [00:01:40] React and Temporal, Declarative vs Imperative  [00:01:40] swyx: Okay. So the first topic we want to talk about is React and Temporal, right?  [00:01:43] Sunil Pai: I feel Temporal is introducing a shift into the workflow ecosystem, which is very similar to the one that React introduced to the JavaScript framework system.  [00:01:54] swyx: That's the hope. I don't know if like my explanation of Temporal has reached everybody or has reached you. There are three core opinions, right? The first is that whenever you cross system boundaries, when you call it external API. So when you call internal microservices, there's a chance of failure and that multiplies, the more complex the system gets. [00:02:11] So you need a central orchestrator that holds all the retry states and logic, as well as timers And it tracks all the events and is able to resume from it from failure.  [00:02:21] Second opinion that you should have is you should do event sourcing rather than try to just write your business logic and then instrument with observability logs after the fact you should have your logs as the source of truth. And if it's not in the log, it did not happen.  [00:02:34] And then the final piece is the workflows as code, which is the one that you're focusing on, which is the programming model, in the sense that like all the other competitive workflow engines, like, Amazon step functions, Apache airflow, Dagster, like there's a bunch in this category. [00:02:48] They're all sort of JSON and YML DSLs, and the bind that you find yourself in is that basically you're reinventing a general purpose programming language inside of these JSON and YML DSLs because you find a need for loops, branching, variables functions, all the basic stuff. And, people find that like at the end of the day, all this tooling is available, you just have to make it run in inside of a general purpose programming language. So that's what Temporal offers.  [00:03:12] But it's very interesting because it kind of straddles the imperative versus declarative debate, right? [00:03:17] React, people view as declarative. And I think it's mostly declarative, like there's imperative escape hatches, and because it's declarative, people can have a single sort of render model of their entire app for the entire tree. And I think it makes sense to them. [00:03:32] And you're saying that that's better, right? That's better than the imperative predecessor of like jQuery and randomly hooking up stuff and not having things tied up together. You sounded like you want it to  [00:03:42] Sunil Pai: interrupt. So it's actually two things. One is the jQuery had an imperative API, and then they went way too hard into the declarative side with templating languages and then started reinventing stuff there. [00:03:54] So really react was like, no, you need access to an imperative language to create, you need a fully featured programming language to generate description trees like Dom trees or in this case, a workflow graphs.  [00:04:10] swyx: Got it. So it's kind of like a halfway solution, maybe, maybe anyway. So the problem with us is that we're trying to say that imperative is better than declarative, for the purposes of expressing general purpose business logic, which is an interesting sell for me because in all other respects, I'm very used to arguing to declarative is better. [00:04:33] Then there's also an idea that people should build declarative layers on top of us. And I, it's just a very interesting, like back and forth between declarative and imperative that I don't know where I really stands apart from like, wherever we are is never good enough. So we need to add another layer to solve the current problems  [00:04:51] Sunil Pai: there. [00:04:51] So there's a phrase for it and I forget what it's called the mechanism. It says that, uh, the system that allows you to execute stuff should not be the same system that prevents you from doing bad things. So there's a core, which is basically a fully featured API. And then you put guard rails around like the experiences. [00:05:12] For example, as an example, this is like adding TypeScript on top of JavaScript, let's say, unlike reason ML, let's say like, OCAML or a lot of very strongly type a language where if your code doesn't compile, you can't really run the code in TypeScript. There are times when you're like, you know what? [00:05:29] I need an escape hatch to actually like, do something like really funky here, X, Y, and Z, that that's not even well expressed in either the type system or sometimes even the language itself. You need to like hack it. And like, you might even email a couple of things. Uh, and in react, this was, I think when react came. [00:05:47] It wasn't just that it was a, oh, like there's JSX. It was very much, uh, okay. Uh, I have a lot of existing code, so I can add, React to one part of it and then hook onto the DOM, it renders and then have like this whole jQuery widget that I would like render onto the thing. Uh, so it gave you this whole incremental part to adopting the system, but then like after a point, like react consumes all of it. [00:06:11] And the fuck up with react is if you go too hard into react, doing stuff like animations is like impossible, which is why like we are at least a year or two away from a good animation API in React, or while you use, Framer or whatever Framer has become right now. Like frame of  [00:06:27] swyx: motion. No. Um,  [00:06:31] Sunil Pai: Yeah, but he's working. [00:06:32] I think Matt is now working on like a new, new thing. That's got a really funky name. Like, it sounds like a robot or something. All right. But it was curious to me that React's biggest deal was that, Hey, like, They talk about it being declarative, but a whole lot of things you wrote were like in regular-ass JavaScript, you would say on click and get an event and start doing things  [00:06:53] swyx: beautiful. [00:06:54] It's a perfect blend.  [00:06:56] Sunil Pai: Right. And you would suffer with this in. So there was the jQuery prototype phase, which was like directly imperative. And then they went hard in the other direction with type templating languages, like Jade and dust. And, uh, there were a number of popular ones at the time. And that's when like even Angular 1 became super popular because they're like, here's the whole kit and caboodle full whole framework. [00:07:18] And then React came and said, oh, well just the view. But that's because they didn't want to release like really yet. And they were like, yeah, this is all you need and the whole ecosystem. But anyway, so in temporal temporal for me is particularly interesting for that because it is now clearly making that. [00:07:35] I hate the phrase, but it's a good one. The paradigm shift of like how you start thinking about these systems and you just write some fucking code and then like you start adding on bits and guardrails for the things you want to do, which is on for the few hours I spent going through the docs and failing to get it running on my laptop. [00:07:53] That's my understanding of it. Feel free to correct me.  [00:07:56] swyx: Okay. Yeah. And I think you're right, actually, I'll try this messaging on you because, it's something that we're consciously designing for. In fact, I have a, one of my API proposals was, reacts like API for tempo. And so essentially what we enable you to do is bundle up each individual service or job into a component that we happen to call workflow. [00:08:21] And my struggle here is that I currently tie component to workflow because what is the component like? It's, it's something that's self-contained that is a deterministic. Like it has a strict rule of execution from top to bottom, right. It just does the same thing every single time, uh, where we differ and why I struggle with this is because we put all the side effects into things that we call activities. [00:08:44] That's where all the non-deterministic stuff goes. And that one gets retried, basically at Temporal's will and essentially Temporal is serving as the central runtime or framework that has knowledge of all these workflows and activities. And can re-render them based on its internal rules, I retries timeouts, uh, heartbeats, all that good stuff. So I struggled with things like, which is the component and which is the hook or the effect.  [00:09:08] And then there's other concepts. So, uh, we have ways to send signals into individual workflows, right? That's a very important property of the system that you can send data in while it's running and you can get data out while it's running. I'm not sure that's reflected in React at all. So maybe I'm stretching the analogy too much,  [00:09:24] Sunil Pai: Solid, had an answer for that the word signal. So like solid JS. This is by Ryan Carniato the Marco folks, signals are a first-class concept in the framework. Again, I haven't dived into it in detail in a while, but it feels like an important thing. And I always wondered why React actually didn't have it because props are something that you just like pass. [00:09:46] Right. And it's just a value, like if you like plot it on a graph, for example, it's, let's say if you had to have like a graph of binary values, it would be either zero or like one, and that would be the shape of the graph, but signals are something that can be like something that happens and yeah, just pops up and goes down, like pressing a key on the keyboard. [00:10:06] And that's actually not so easy to define in a, in a react like system, like, uh, which is why it's kind of hard to build like audio processing graphs with like React or JSX. Um, I don't have like a good answer. I'd probably have to like hack on Temporal a little more, but the idea of like signals as a channel, through which you can like send information and having it as a first class part of the system is something that's not represented well in well, in React at least. [00:10:33] Yeah. Well,  [00:10:34] swyx: isn't that in an action? For reducers  [00:10:38] Sunil Pai: and event effectively. Yes. Like it's basically one of those actions.  [00:10:42] swyx: The problem is that everything just ties right into the component tree instead of just having the component B and sort of isolated unit that can function independently.  [00:10:50] Sunil Pai: That's the other thing, which is a workflow engine isn't a directed acyclic graph. In fact, it could have cycles, it could have cycles and it could have a number of other things, which is the  [00:11:00] swyx: beautiful thing, by the way.  [00:11:02] For us coding, a subscription platform literally is charged Stripe sleeps 30 days, charged Stripe again, and then infinite loop until you cancel and then you break out of the loop. [00:11:13] That's it.  [00:11:13] Sunil Pai: That's awesome by the way. So I was actually thinking that someone's going to implement not someone's going to implement, uh, someone's going to use Redux saga on top of Temporal, that's what I was thinking, because then you will have generators that define like long running processes that are just talking to each other. [00:11:30] I think that would be good. CloudFlare also loved Temporal, by the way, like we were talking about it, like for awhile, they're like, oh, this is like fundamentally a new thing. And as you can imagine, some engineers were like, well, why isn't this running on workers? I'm like, I don't know why isn't it running on workers? [00:11:43] Like maybe we should get it there. [00:11:45] swyx: It is fairly heavy duty right now. We're trying to reduce that to a single binary, which could maybe run a workers. I'm not sure about the memory requirements that you guys have. It could, it's just not a priority for us based on our existing users.  [00:12:00] Sunil Pai: Um, I was just, I was saying what they're saying. [00:12:04] They want everything to run on workers and I'm like, dude, it's just like one small, weird isolated like condo.  [00:12:10] swyx: Ironically we also using V8 isolates for our TypeScript runtime. And that's just to make sure that people don't do non-deterministic stuff. So we did mock out everything, which is also pretty cool because whenever you use a library with, like setTimeout inside of that library, that persists to us as well. [00:12:25] So we set the durable timer. Your system can go down and we, we bring it back up and you're using our timer, not the JavaScript runtime timer, which is like just awesome. There's a trade off to that, which is, things don't work when you import them, like you would in a normal, Node.js project. [00:12:39] So most of, because you have to inject them into the environment of the V8 Isolate, you can't just randomly import stuff that as freely as you would in a normal node environment. So dependency injection and becomes a topic for us. [00:12:57] State Charts and Lucylang  [00:12:57] swyx: Um, yeah. We actually clashed a little bit with David Khourshid because David is on this warpath of like everything in a state machine, right. Everything in the time-tested 40 year old JSON format that describes state machines. And we actually thought we were going to be competitive with him for a while because for him, the thing about writing imperative code is that it's prone to bugs, right? Like you can not really see the full, possibly the full span of like all the possible states that you're exposing, but in a state machine everything's explicit so he was butting heads with our founder for awhile. [00:13:31] But I think recently he decided that he is better at building on top of us than trying to compete with us on the reliability front. So that's, that's kind of an interesting evolution that has happened over the past year on this topic of declarative versus imperative. [00:13:44] I'm still like coming to terms with it. Like I'm not fully okay with it yet, but, it clearly is more expressive and that's something I am Very in favor of, and I have genuinely looked at like the workflow solution from Google, the workflow solution from Amazon, and they are literally have you write the abstract syntax tree by hand in JSON and that's just absolutely no way that that's going to work. So I'm pretty down with the imperative approach for now.  [00:14:09] Sunil Pai: Well, that's, I figured at some point you will run XState on it and extent should work fairly well. I think contemporary, I don't see why it would. I think that that would actually,  [00:14:19] swyx: Honestly, I'm not really sure what he's going to charge for. He's pushing the idea of state machines and making it more of a commonly accepted thing. [00:14:26] Sunil Pai: Well, his pitch isn't even state machines. It's very specifically state charts and I love state charts. I even bought the book by the way, the Ian Horrocks $700. So when I got it on Amazon, it was $180. I was like, cheap. Let's do it. I got really lucky at the time. It, it fluctuates like mad by the way that that value, well, you should expense it now is what it is. [00:14:46] Um, but, uh, what struck me about the thing? Here's what I tried. I really liked it. And I took a course, a couple of steps back and I was trying to understand, well, why isn't it like a success? Why don't people get into it? And the truth is that this falls not just into the intersection of this is the intersection of like computers and humans in the sense that sure. [00:15:07] There are things that can be correct, but there are things that can be expressible as well. Like I don't even know what code I want to write when I'm sitting down to write it. I love to like discover it while I'm writing it and really. All the syntax that we have created and abstractions, we have created around programming languages have been purely to express these things and have let's call it implicit state machines, even though that implies that it's bad. [00:15:32] Um, so for example, if you look at state charts, there's no real good way to compose two state charts together. You have to like manually start wiring them together. And like, there's, you know, like you've got in react, you say, oh, combo, if you have two components to put it together, you put like a little, uh, function around it. [00:15:49] And now it's two components in one component. So it's important not just to have a good unit of computation, but to have it like be composable with each other so that you can gather it and then make this whole nesting doll react, Dom tree of things. And I think. Until there's an actual language that supports that has state charts as a first class primitive, much like Lucy, I think that's what Matthew Phillips built. [00:16:15] He wrote a, he wrote an actual language that compares to state charts called Lucy Lang. That was very cool by the way. Like, I really like it. Uh, well, and it's fairly young, so it's too early to say whether people like love it or not. And other than, but people like you and me who look at something like, wow, this is awesome. [00:16:33] Let's all use it. No, like to take a while to grow. But I think that's the state charts has a bit of dissonance with the languages that it's written in right now, because it's not a first-class thing. I mean, it's adjacent object with keys and. Okay. Like we can do better maybe. Uh, but I would not bet against David and the people he's hiring. [00:16:53] Like he's hurting some smart people, you know, they're all like pretty intelligent. So I'm curious to see how that plays out.  [00:17:00] swyx: I'm just glad that we're not competing. Uh, so that's, that's something that, that, that resolved itself without any intervention from me, which is very good. [00:17:08] The Future of React  [00:17:08] swyx: Well, let's have this conversation since it's related, should React to be more of a DSL,  [00:17:14] you know, this conversation that happened over this week, so I'll pull it up. [00:17:20] Sunil Pai: Uh, wait, so I've, I'm seeing, is this the whole Svelte versus React thing that's been happening over the last two, three days?  [00:17:25] swyx: Yes. So basically it's saying React is already so far down almost like its own language. [00:17:30] They should just embrace it more. And instead of using linting to catch rule violations, just make a DSL, people are gonna use it. It's fine. And just like build things in so that it's impossible to make these errors that, that people commonly make.  [00:17:47] Sunil Pai: So this is Mike Sherov, uh, he was smoking about it. [00:17:51] He mentioned how it shouldn't be a lint rule. And since we already have customs, insects and GSX, he should introduce a couple of other things. So as you can imagine, the react team has thought about this a lot. So the big problem with this all boils down to that fucking dependency area on use effect, by the way, that's the one that trips, everything else is fine. [00:18:09] Like you stayed all that is like fine. You can get. This is  [00:18:13] swyx: what it was. Yeah. People want like state something memos and things like, you know, just build the reactor primitives into the language.  [00:18:22] Sunil Pai: So yeah, I think this, this actually, isn't a bad idea and I think that was the whole deal with hooks. Whereas what's the phrase that they use in the docks. [00:18:30] A sufficiently advanced compiler might comply with these things at some point, and you're like, oh wow, great job. On pushing that responsibility onto the community, React team, well done.  [00:18:41] swyx: My joke is like it's the react teams equivalent of a assume, a frictionless spherical cow from physics.  [00:18:48] Sunil Pai: Exactly. [00:18:48] That's a perfectly spherical code. [00:18:54] swyx: It will exist.  [00:18:57] Sunil Pai: And it's just the five of them or six of six of them hacking on this. And they have to make sure they don't break like facebook.com whenever they're working on these things. Imagine it's taken this long for Concurrent to show up and Concurrent is nice by the way. And we can talk about the server rendering API. [00:19:14] Okay. Uh, so react right now is, uh, yeah, that's the one like that. It shouldn't just be an intruder, but, uh, inside the inside Facebook only, well, not everybody can see it, but it's an in an internal, uh, uh, Facebook Wiki page, which is a list of potential F projects. You know, how the react team has fiber, whatever the hell. [00:19:47] Right? So there's a list of these projects that, or when we do this, uh, project F F I forget what the one for, uh, uh, animation that's called, is it called flat? Flat was the dumb one. And so there are lists of them and there are about 15, 20. I'm pretty sure my India has done. So Hey, so, uh, there's a list of them. [00:20:09] And if you look at them and you start assigning values in terms of work, oh, this is about six months of work. This is about, uh, another six months of work. It strikes you that there's a roadmap for about five to 10 years. At least if not more than that, I mean, look at how long it took to get like this. Of course this was very more foundational. [00:20:26] Those could probably happen a little quicker when it comes, which means the react team is like solely aware of what's missing in react right now. And to an extent that they can talk about it because if they do it becomes like a whole thing and like don't really engage in that conversation. They don't, I, I, and I don't blame them for it. [00:20:44] It's very hard to have this discourse without somebody coming in and saying, well, have you considered CSS transitions? I like that. Yes, we have. We have, we have considered CSS a lot. Uh, so, uh, so. There are all these projects like a sufficiently advanced compiler that compiles down to hooks. There's the animation API. [00:21:04] There's a welcome current, et cetera. This whole data fetching thing has been going on for years. And now it's finally starting to come to light, thankfully with collaboration, with the relay team and effectively all of the core when they built out facebook.com and, and that is the length that those are the time periods that Sebastian looks at and says, yeah, this is how we can execute on this because it can be prioritized. [00:21:33] It has to be prioritized by either Facebook wanting it or making Facebook wanted. So for example, the pitch was, Hey, let's rewrite facebook.com the desktop version because they haven't, it's a film mishmash of like hundreds of react routes on one page. It should be a single react route that does this thing. [00:21:52] Now that we have gotten management to agree to a rewrite, let us now attach it to the concurrent mode thing. And that was also part of it, which is in the older version, there was a lot of CPU fighting that used to happen between routes, which is why the whole work for the share dealers started and took like two years to like fix effectively. [00:22:08] They're doing cooperative, multitasking VM in JavaScript, which sure. When you're a Facebook, I guess you've got to like do these things. Uh, and how does that all,  [00:22:18] swyx: was that ever offloaded to the browsers, by the way? Like I know there was an effort to split it out of react.  [00:22:24] Sunil Pai: So I think last, I checked they were talking to Chrome literally every week. [00:22:29] Uh, but I think it's also been down to, uh, well, what Chrome wants to prioritize at the time. I think it is still going ahead again. It's the sort of work that takes years, so it's not going ahead. Nice and slowly, uh, which is why. Which is why it's architected inside react for the same reason as like it's attached to global and then read off the global. [00:22:52] I think it's also why you can't have two versions of React on the same page. There's the whole hooks thing. But also if you have two versions of React, and they'll just start fighting with each other on the scheduler, because the scheduler would yield to one than to the other than to the other one. [00:23:08] And there would be no like central thing that controls what is on the scheduling pipeline. That's from the last, again, this conversation is at least two years, or maybe they fixed that, but that's the goal of the dealer. There has to be one scheduler for the thread that everybody comes on to, and like tries to pull stuff, uh, with it. [00:23:26] I think it will become a browser API. It's just a question of like, when, like, yeah, I mean, the shared dealer in react itself has undergone so much change over the last three years. Uh, so maybe we should be glad that it isn't in the browser yet, because like, it's changed so much. It's coming there. It's I mean, the fact that they're releasing in November is a big deal. [00:23:45] swyx: You said there's so many projects that you want to ship, and the way to ship it in Facebook is to either convince them that this feature itself is worth it, or you tie it together with something else, like the Facebook, I think it's called FB5 rewrite. [00:24:00] Sunil Pai: Oh yeah. I think it's good for them. Like it worked because the Facebook, facebook.com is now more performant. Like it actually works well and they don't have CPU fighting. The fact that Facebook itself is becoming slightly irrelevant in the world is a whole other conversation.  [00:24:17] swyx: Well, you know, I still use my billions, so, uh, it's it's, it improves the experience for them. [00:24:23] Sunil Pai: I'm only being snarky.  [00:24:25] swyx: Uh, but I, you know, hopefully hopefully you're like, you know, there's other properties like Instagram and WhatsApp and what is, uh, which hopefully it will apply there. And then obviously like there there's the VR efforts as well. Absolutely. Yeah.  [00:24:39] Sunil Pai: And that is the future. In fact, uh, several components also happened because they suddenly realized what they could do for how the deal with server components and server-side streaming rendering was never about an SSR story, or even a CEO. [00:24:54] Facebook doesn't give a fuck about SEO, right. It was about finally they figured out how to use concurrent mode to have a better UX altogether.  [00:25:03] React Streaming Server Rendering vs SSR/JAMstack/DSG/DPR/ISR  [00:25:03] Sunil Pai: So, okay. I should probably just keep Server components aside for right now.  [00:25:06] And I'll just talk about the new streaming rendering API. Okay. [00:25:09] Okay. So I know there's like about three styles of rendering. [00:25:14] I say legacy, but legacy is such a dirty word. I don't mean it in the form that it's old it's in fact,  [00:25:20] swyx: traditionally, like, sorry.  [00:25:24] Sunil Pai: Uh, heritage Facebook would say heritage, it's a heritage style rendering, um, which is the, Hey, you use something like a rails or spring or some, it could be node as well. And you spit out a bunch of HTML and then you progressively enhance it with sprinkling JavaScript, pick your metaphor there like three or four metaphors that you could use. [00:25:44] Uh, uh, web components actually falls square into this, where it just comes to life only on the browser and then like make stuff interactive. Uh, then there's the whole client fully client side rendered one. So this is create react app or, well, a number of like smaller players then there's server side rendered. [00:26:04] And so as I rendered is actually like, it's not just next year. It's also your Gatsby. I feel like pretty much every, uh, react framework now has some kind of service side rendering story. Okay. So the next slide goes into what types of server-side rendering things happen. [00:26:20] swyx: there are a lot of subdivisions within here, right? [00:26:22] Like, uh, Gatsby is up here trying to reinvent like D S R D P R or something like that, which is like deferred,  [00:26:29] Sunil Pai: static,  [00:26:32] swyx: DSG, deferred static generation. That's the one. My former employer, Netlify also DPR, and is all, these is all like variations of this stuff with,  [00:26:41] Sunil Pai: like, it's a question of where you put the cache is what it is. [00:26:46] It's a TLA three letter acronym to decide where you put the caching in.  [00:26:49] Yeah, so there's the whole JAMstack and that's like the whole Netlify story, but also CloudFlare pages, or even GitHub pages. [00:26:56] There's no real runtime server rendering. You just generate a bunch of static assets and you Chuck it and it just works. Then there's fully dynamic, which would be next JS without any caching. Right? Like every request gets server-side rendered then like a bundle loads on top of it. And, um, like suddenly makes it alive, like sort of like it hydrates it. [00:27:16] And then after that it's effectively a fully clients rendered application then there's okay. So I just said ISR, but like you said, there are like three or four after this as well. There's this whole DSP. Yeah. Oh wait. So the new streaming API is actually fundamentally new because. I don't know if people even know this, but react already has a streaming rendering API. [00:27:37] It's called a render to node stream. I think that's the API for it. And the reason that that exists is so that, uh, only for a performance thing on the server where otherwise synchronous renders would block like other requests. And it would make like if for a server that was very, uh, uh, there was heavily trafficked. [00:27:57] It would become like really slow. So at least with the streaming API, yeah. That's the one learner to notice the stream, at least with this one, it wouldn't clash and you could interleave requests from there happening, but it didn't solve like anything else, like nothing, you couldn't actually do anything asynchronous on it, which is kind of that fucking sucks because like, it looks like it's an asynchronous API, but you can't do anything asynchronous through it. [00:28:18] It's the only thing that, okay, so vendor to readable stream is cool because I can, even if you go to the very last slide last bit, once. You know what this is, where the very first link open it up. Like it says react, lazy.cool computer club. So this is the demo that they have that exists with this new API. [00:28:36] This is what they link to. So if you refresh it a couple of times and I'll show you something that happens here, so you see the little spinner that shows up there and then the content loads. Yep. So, um, you know what, maybe I can share my screen because I want to show like a couple of things. Uh,  [00:28:53] swyx: yeah. I'll fill in some context, like I knew that the renderToNodeStream API was not good enough, basically because everyone who is doing SSR was doing like a double pass render just to get the data in. Um, and I noticed a very big sticking point for Airbnb so much that they were almost like forking react to something like that to,  [00:29:11] Sunil Pai: they invented a caching API. [00:29:13] They did like a whole bunch of things. Okay. So if you have a look here, you'll see that there's a little bit of spinner and then the content comes in. But now what I'm going to do is I'm going to show you the actual HTML. So let's just go to prettier and just pretty far this, for that, we can see the content and I'll show you something that's very like fundament. [00:29:32] That's the playground playground paste, big HTML. All right. So are you looking at this HTML it's rendering rendering by the way, this, these are special comments that mark suspense boundaries. It's very cool. If you come down here, you'll see a dev, which is the spinner. So this is the spinner that you see when you refresh the page. [00:29:52] So this is. And then the rest of like then, like the, like the bits that are below that close and the HTML closes, but content still start stream is streaming in at that point. So like, this is the actual, like devs that are coming in with the content. And then a script tag gets injected that says, Hey, this thing that just came in, shove it into where the spinner was. [00:30:13] This template  [00:30:14] swyx: tag is so small. I would, I would have imagined it was much bigger.  [00:30:18] Sunil Pai: It's not. So by the way, at this point, the react has not loaded. This is happening without react. This is just a little DOM, much like swelled ha uh, just a little operation that does it. So you, you, you get this content. And, uh, so, so that's the first feature which is that suspense. [00:30:35] It not only works out of the box, but fallbacks and replacing or fallbacks with actual content also happened. Um, I want to pull this outside of this main window to show you something. Um, so you can see the content load in, but keep an eye on the loading spinner. Okay. Just to prove a point. So the content loads in, oh man. [00:30:56] Oh, is it cash just that way? Uh, the content loads in, but the spinner is still going on. That's because there's an artificial delay for the react bundle to show, to show up. That's the point of this demo, which is to show that it can do async. Now you can imagine that it's not just one part of the page. [00:31:13] There could be multiple suspense boundaries here, some with something heavy, something with something asynchronous and they're potentially streaming in effectively in parallel in the, like after the HTML tag closes and they load nicely the, the other cool feature, which is a feature, every framework should steal is if you do a second refresh and here, I think if the, if you do a second refresh and at this point, the react bundle, the JavaScript bundle is cached. [00:31:42] So it loads before the react, the server. Finish the streaming. So at that point, the react says, fuck you, I don't care about the streaming bit anymore. I'm taking over, it's now a client set up like just automatically out of the box, because now that would be faster. So it basically raises the client and suicide. [00:31:58] So suspends working out of the box itself is like a big deal first. So people will start using it like with react dot lazy, but then with data fetching and a bunch of slate styling solutions, which they're also working on. Um, but this is the new server entering API. The reason I was talking about this, I keep losing context about these things. [00:32:19] I should stop sharing, I guess. Um, the absolute best feature of this of course is the reason why is something that comes out of Facebook, which is it works with existing applications and you can incrementally add it. So the first thing you will do is you'll take your render to string that one line somewhere in your code base, which says rendered to. [00:32:39] And you'll replace it with vendor to notable readable string. I mean,  [00:32:43] swyx: either way 99% of users have never used render to string. Right. That's what next year is for.  [00:32:51] Sunil Pai: Well, that's the, that's all my God. That's part of a whole other conversation, right?  [00:32:54] swyx: This is rendered a string as a service. [00:32:59] Sunil Pai: The moment you update next, year's your version of next year? So work on yes.  [00:33:04] swyx: Which is good, which is good. Right? Because, uh, people won't even know and they will just benefit, but it's, it's a little bit bad. Okay. [00:33:13] Next.js and the Open Source Commons  [00:33:13] swyx: And this is a little bit of my criticism, which is that your blessing, a meta framework, at the expense of all the others, right? Like which admittedly have not been as successful, but, uh, basically reacts Chrome, picked a winner and it was next year.  [00:33:27] Sunil Pai: I've been thinking about this so much. Oh, look, it let's get into them at our conversation now. So let's standard disclaimers. I think Guillermo is a mench. [00:33:35] I think the people who work there are incredible. There are some people I'm close to. I'm so happy for them. I know people on the Chrome team who work with these folks. I love them as well. Nicole for me is, uh, is a hero. Uh, and of course the React team at all my buddies, I love them. Okay. That being said, the React team is six people and they don't have the time to build the meta framework and Guillermo, uh the one thing he's incredible at is he's great at building relationships. [00:34:03] He's just amazing at that. Like he, uh, in a very genuine way, like this, there's nothing like ulterior about it. Next JS is open-source and runs on any node runtime and it's designed to do so. There's nothing about it. That's become special on Vercel. Because of that the React team felt, feel like, okay, fine. [00:34:20] We can have a primitive and meta frameworks will solve it. And let's just make sure it works with next two years, because so many other people who are just reach out to them and say, Hey, this new API is showing up. Uh, this is not just with next.js. It's a similar thing is with like react testing library. [00:34:34] When the new activity I showed up, right. I made the PRS to react testing library. I was like, what you should do is have every function and react testing library be wrapped in back act. So nobody really has to like use the API by hand. I just, it's now it's the D and it's a very good testing framework, the Chrome team. [00:34:53] And this is my, I'm not saying this, like, it's a bad thing. I think they did the right thing. The Chrome team realized that if they provide performance enhancements to next years directly, they can have so much impact on the internet because so much of the react tool is running on next year. So fixing how the images are loaded in next year certainly makes the internet faster. [00:35:15] Yeah. And maybe that's what we should do also like for the accessibility, just ship acts in, uh, all the acts rules in development mode, either in like react Dom directly, or at least the next years. Oh yeah. The sweatshop, the axles. Yeah.  [00:35:33] swyx: Oh, they're enabled by default. And, uh, your, your app one compile, uh, actually I think it would warn you won't fail by a worn. [00:35:40] Sunil Pai: Okay. So you should be making the swag folks should be making way more noise about that. That is such an incredible draw for accessibility.  [00:35:48] swyx: The thing is like, uh, if you encourage, if you think that your, your problems are solved by X, then you're taking a very sort of paint by numbers approach to accessibility. [00:35:57] Right. Which is actually kind of against the spirits of, of, uh, what people really want, which is, um, real audits with like tap through everything. Like the stuff that machines could catch is so little,  [00:36:08] Sunil Pai: I agree. The whole point of actual SIS to make sure that all the low hanging fruit is done by default. [00:36:15] It's like TypeScript, like I guess, which is a TypeScript. Doesn't solve all your bugs, but the stupid undefined is not a function once it does. Yeah, exactly. Make sure that your images have. Just by default, like we can have stronger conversations about tab order once you make sure all your images have all tags. [00:36:35] swyx: Uh, okay. Anyway, so, so yeah. So first of all, yeah, I agree with you on the, on this Chrome. And, uh, I think this is opensource winning, right? Like, uh, there's a, there's a commons. Vercel built the most successful react framework, Nate. They went the investor really hard at it. They had the right abstraction level, you know, not too much, not too little, just the right one. [00:36:55] Uh, and now everyone is finding them as like the Schelling point, which is a word I'm coming to use a lot, uh, because you know, that is the most impact that you reach. Uh, so no hate on any of them. It's just like it happens that a venture backed startup benefits from all of this.  [00:37:11] Sunil Pai: Can you imagine how hard it makes my job? [00:37:13] We don't run, not on CloudFlare workers, which means Next.js doesn't run on it. It's annoying.  [00:37:19] swyx: Oh, is there any attempt to make it run?  [00:37:22] Sunil Pai: There are a couple of ways where we can get it to work, but it like, it's a lot of polyfill and, uh, we'll get that. Like, I expect it to be fixed within the next three to six months, but out of the box, it doesn't run on it. [00:37:35] And for me in my head, it doesn't, it's not even about CloudFlare workers. I'm like, oh shit. That's what makes Bezos like even richer because everyone's got, has, if you want to use Nadia using AWS or Lambda. And that just means more folks are using AWS. I'm just like, okay, I guess. Sure. I know you work there as well, but it's just very annoying to me where I'm like, shit. [00:37:56] What's even more interesting is that node is now moving to implementing web standard APIs inside of it. So they already have the streams implementations. They will have fetch fetch will be a node API. Like it will be implemented based on standards, which means the request response objects. And once that happens and people, if people build frameworks on that, then you can say that it will run on CloudFlare workers because the cloud fed worker's API is also like a standards based thing. [00:38:21] So it's an interesting shift of like what's happening in the, in the runtime world. Also conveniently the person who implemented the web stream implementation at node just started at CloudFlare like last month, like James. Oh, James  [00:38:38] swyx: now. Okay. Yeah. I recognize  [00:38:39] Sunil Pai: a great guy by the way. Uh, very, I just love these people who have like clarity of thought when they talk James as well. [00:38:46] The Third Age of JavaScript  [00:38:46] swyx: We're kind of moving into the other topic of like JavaScript in 2021. Right. So first of all, I have a meta question of how do you keep informed of all this stuff? Like I ha I had no idea before you told me about this Node stuff. How do you know? [00:38:57] Sunil Pai: I have an internet information junkie problem. [00:39:00] I replaced the weed smoking habit with a Twitter habit. This is what it is.  [00:39:05] swyx: You're not unlike some magic mailing lists that like tells you all this stuff. Okay.  [00:39:09] Sunil Pai: Like reading the tea leaves is what it is. Like. I keep trying to find out what's going on. The problem  [00:39:14] swyx: is I, I, I feel like I'm ready. I'm relatively plugged in, but you're like, you're way more plugged in than me. [00:39:22] and then this development with node adopting web standard APIs, um, is this a response to Deno?  [00:39:28] Sunil Pai: I don't know if it's a response to Deno because I know Mikeal Rogers wrote about this. Like your. That we made a mistake by trying to polyfill note APS and browser code with like modules and stuff. [00:39:41] Right? Like that's what the whole browser, if I, during those days, when we started actually using the same module system and the word isomorphic came up, what ended up happening was naughty APIs were polyfill in web land, but what should have happened is we should have gone the other way. And it would have kept like bundle this bundle size problem would have been a web smaller pro problem right now, just because of that. [00:40:07] So I know that the folks at not have been thinking about it for awhile, maybe Deno finally pushed them to do it, but I don't, I don't, I don't, I don't think it's like that reductive. I don't think it's just, it's just dental. It's very much a, this is the right time to do it and we actually can do it now. [00:40:22] So let's like flesh it out and do it the right way. Uh, and it's hard to do it in, in no, right. It's not just that you can just implement this thing. Like, what does making an HTTP server mean now? Because the request response objects are slightly different in shape. So you have to make sure that you don't break existing code. [00:40:39] So it's not as simple as saying, oh, we're just implementing the APS. That being said, having fetch inside node proper is going to be great. I think. Excellent.  [00:40:47] swyx: Yeah. Yeah, no more node fetch. Um, yeah. You know, my other thoughts on I've been, I've been doing this talk called the third age of JavaScript. Right. [00:40:55] Which is a blog post that I wrote last year that, um, honestly I feel quite a bit of imposter syndrome around it because all I did was name a thing and like it was already happening. It was, you already saw, like, I think basically when, when COVID hit, a lot of people were. I have a lot of time on my hands, I'm going to make new projects or something. [00:41:14] Um, uh, and then, yeah, so I just, I named it and I just called it a few trends. So the, the trends I I'm talking about are the rise of IES modules first, you know, in, in development and in production, uh, concurrently the death of 11, which I'm also tracking.  [00:41:30] Sunil Pai: Yes, those are, those are both come to fruition.  [00:41:34] swyx: Which, by the way, I think the us government will have to drop by 11, uh, sometime in the next six months or so because, uh, the, the use, the usage levels have plummeted. [00:41:43] 3.6% of all visits to the U S government website in November, 2020 was I 11 and now that has dropped to 1.6, um, all  [00:41:51] Sunil Pai: accelerating the drop is actually accelerating.  [00:41:53] swyx: Uh, I don't know if it's accelerated it's everything, but it's under the 2% mark that the us government sets for itself. [00:41:59] They have an opportunity to essentially say like once it's stable, you know, there's no chance that it'll ever go back up again. Uh, they could just deprecate 11 for all government websites and then that, that will be the signal for all enterprises. And that's it. Yeah. So, um, and then the second. [00:42:15] Oh, I was going to move on the second bit. But what was your calling?  [00:42:19] Sunil Pai: Oh, just saying that this happened, like, while I was working in JP Morgan over the last year, they did the same shift, but they're like, yeah, we are now a Chrome company. Literally none of our clients are asking for this and you know, it, it was just in rules somewhere, or we need to target, I 11, some people looked at it and said, okay, fine. [00:42:35] What happened is people are spending money on something that wasn't giving them the returns. And that's when a bank is like, yeah, we don't need  [00:42:41] swyx: to do this anymore. Like you, you can deprecate free support. Right. And, and just make, just charge for 11 support, stop spreading it out among all the other users who are bearing the cost of development and maintenance. [00:42:54] The other one was collapsing layers, which is the death of Unix philosophy. Like , we used to have one tool does one thing, but now we want to combine everything. So, uh, Deno and Rome both have ambitions of linter format or test runner, all of that into a single binary, because the idea of what we want out of a default runtime has changed, uh, from a, for a very minimalist thing. And I always made the comparison to what word processors used to be like. [00:43:18] So, are you aware of Benedict Evans? He has a blog post, which is amazing about what a job of a platform should be. And he talks about like in 1980s word processors used to only let you type words. And if you wanted a horizontal layout, if you wanted word counts, if you wanted footnotes, these are all plugins that you buy and install separately. [00:43:38] Right. Okay. So, but as we evolve, as we just use all these things, we realize that these are just like the same tool that we want out of a word processor. So then they absorb all these features instead of plugins. They're just part of the platform now. They're there now in the new table stakes. [00:43:53] So I make that analogy to the runtimes that already doing, right. Like, Node used to be this like much more minimal thing. And, uh, but now we are expecting more and more out of our default setup with all these tools . Um, it's also very wasteful because when each of these tools don't know each other, they're all parsing their own ASTs running, running their own code. And then yeah, that's the whole  [00:44:12] Sunil Pai: proposition, but yeah.  [00:44:14] swyx: Any, any tool that collapses layers will, we will meet this, like, ESBuild, um, collapsed. Like a standard web pack would do like five or six AST runs. ESBuild collapsed it to two to three. That's a source of its speed as well.  [00:44:27] Sunil Pai: One of my favorite facts about ESBuild is that it is faster to minify the code than to not modify the code when you run. Yes. And the reason for that is because when you try, when it tries to do the full AST, keep comment notes, everything else, it has to do a lot more bookkeeping, but the moment it just ditches all those things, because ESBuild doesn't do like full magnification, like something like a torso, but it does do like a smaller symbol substitution, white space, uh, uh, removes all white spaces. [00:44:59] And it does like some dead code elimination. Uh, and it's a lot more work to keep the bookkeeping for everything and all the white space notes than to not do it. So he has built is actually faster when you have a modification turned on, love it.  [00:45:14] swyx: It's amazing. It's amazing. [00:45:16]   [00:45:16] ESbuild vs SWC vs Zig  [00:45:16] swyx: Do you have opinions on ESBuild versus SWC? [00:45:18] Sunil Pai: Okay. So I like ESBuild. Uh, because I was very strongly looking for something a lot more opinionated. I've noticed that the reason that code basis Surat usually boiled down to the acute decisions that you make. Like in the very beginning of the project, you can do anything. I mean, whichever dumbass came up with the idea of baby plugin, macros has like ruined a lot of lives. [00:45:41] It was me. I came up today, but that is like, then you're like tight. So the thing that ESBuild does is very like its creator, Evan Wallace, which is that it's, it's one of a kind like, he's not really interested so much in having community, uh, uh, PRS or like having suggestions on how it should be built. He has a very strong vision of what it should be like, which is why there are no AST level plugins and all that jazz. [00:46:08] And because of that, because of, like I said, because he's collapsed the lyrics and collapse, the size of the development team to just himself, he has like such a clear vision on what it should be. So it w is good. It would be great for, I want to say 95% of projects that fall under the things he has designed at four. [00:46:28] Okay. Uh, and that's a lot of applications. That's a shit ton of applications. That's like everything, but your host, if you need anything, uh, unique, I'll give you one. That's like a very good use case that is bill will never use. Do you know what, um, uh, really has this idea of persistent queries. Okay. So like for whoever's hearing who doesn't know it, right? [00:46:52] Like you can write a query inside Java. And when it compiles it out, it takes out the query and replaces it just with an identifier, like, like a little eight character identifier. And it hosts that query instead of like on the service side. And it says, oh, that eight, eight character query, you can just hit it as a restaurant point now. [00:47:11] So you can write the code internally in JavaScript where it belongs, but it doesn't add like to your bundle or whatever it is. So ESBuild will never support this, which means if you want to do really optimizations on your react code base, you won't be able to do it all. You have to like add on to yours, which you could do. [00:47:29] I guess like you can still use Babel would, uh, SWC is meant to be a platform and which is why next years will use it because next gen is the meta framework, not just for react, but also for like some programming opinions, extracting get server props, get started, props, which one you want to be that this thing after server components comes into play, but a number of things like there will be people who always want to do. [00:47:54] The emotion macro now is like fairly, uh, popular that they will want to use it. So I assume they will implement it in, uh, interest. I know. Do you know what bun is by the way? Do you mean, do you know, how are you following Jared Sumner? Some  [00:48:10] swyx: summers, no, wait, so  [00:48:13] Sunil Pai: key is reimplementing ESB, but in a language called Zig it's another systems programming language. [00:48:20] And he's his claim is that it's about three times faster than you spell it right now, which is already some 200 times faster than Babel loader. It is just our web pack, but it's a language you said it? No. So the language is called Zig lines at AIG, but the thing he's building is called a, B U N. He hasn't shared it in public yet. [00:48:41] I think he's actually planning on sharing it like next week. Like I think it's that imminent. He's been sharing numbers right now. Yeah. That's the guy, Jared. Uh, I love, I should've followed him like a while ago, create great feed, uh, excellent content. And like, he's, he he's thinking that he's going to like implement. [00:48:57] He might actually implement an AST level, uh, uh, plugin, micro API, possibly just implement the emotion one. I think he was just, yeah. See, oh, that's like literally the tweet would write under the main one right there where he's like, Hey, what if we actually just did this in? Uh, oh,  [00:49:14] swyx: he's right. He's he's right with you. [00:49:17] Yeah. Like he's  [00:49:17] Sunil Pai: just talking about it, like right there. So, uh, so SWC versus ESBuild, I don't think is the conversation. I think ESBuild will have a rise. A bunch of people will use it. The nice thing, the best feature about ESBuild is because there are aren't any like cute decisions. You will be able to move away from it to whatever succeeds. [00:49:39] Th there's nothing customer  [00:49:40] swyx: that I believe that was Evan's original idea. That IES build was a proof of existence that day there's a better way. And that he stuck to it for way longer than I thought he would.  [00:49:51] Sunil Pai: People are using it in production and everything know everything about the designers that it's replaceable. [00:49:56] That it's just a,  [00:49:59] swyx: that's wonderful. Isn't that amazing when people design their stuff? W. You know, it  [00:50:04] Sunil Pai: isn't kind of pressure that he would have had the best. Thank goodness. It was the successful CTO of Figma with money in the bank who is implementing this and didn't have anyone to impress. You know what I mean? [00:50:16] It was like, yeah, let's put a macro API and what else do you want? Like, whatever. No, he doesn't  [00:50:21] swyx: go. Yeah. But he just needs to police himself and no one else. Right. If you don't like it,  [00:50:26] Sunil Pai: this is during his downtime from Figma that he's working on this.  [00:50:30] swyx: Um, my, my secret theory is that he's doing this as an, as a Figma ad. [00:50:33] Like, you know, if he, if the CTO of Figma does this for fun, imagine what it's like to work inside of Figma, you know, like of, I've heard it's pretty great,  [00:50:42] Sunil Pai: pretty great working inside of Figma too. Well, the code is like, it's really cool.  [00:50:46] Let Non-X Do X: Figma vs Canva, Webflow vs Wix/Squarespace  [00:50:46] Sunil Pai: Did you actually point out. Uh, Ken was like six times bigger than Figma. [00:50:51] Now   [00:50:52] swyx: you wanna talk about that?  [00:50:53] Sunil Pai: Oh God. That's. I didn't realize until you pointed it out.  [00:50:58] swyx: Incredible. Imagine all the geniuses working in Figma and go looking at Canada and like, yo, like I, I have like a thousand times your features and your six times in my size as a business.  [00:51:10] Sunil Pai: Uh, but I hope every one of those engineers understands the value of sales and like reaching out to your actual customers because  [00:51:17] swyx: I don't think it's just sales. [00:51:18] It's more like, uh, they're always going to be more non, like, this is a category of software called let Nanex do X, right? Let non-designers do design. Whereas Figma is clearly for designers doing design. Um, and there's always going to be like a tool, three orders of magnitude more non-experts uh, who just want to do basic shit. [00:51:37] Sunil Pai: Oh man. I hope that flow has a multi-billion dollar buyout and at some point,  [00:51:42] swyx: uh, I mean, I, yeah, I mean there's clearly something that w the problem with flow is that. They're too close to code. Right? You have to learn CSS the box model.  [00:51:56] Sunil Pai: Yeah. I mean, they do say there's no code, but really they're a visual,  [00:52:00] swyx: if you don't know CSS when using Webflow you're screwed. [00:52:03] Like   [00:52:04] Sunil Pai: that's right. It's uh, they have, they have the best grid editor on the market too. I have to say that. I  [00:52:10] swyx: mean, the UI is just amazing, right? It's just like, um, yeah, I mean, you know, there's a reason why like the Wix is, and the Squarespaces are actually worth more than the workflow and it's not just cause they were around earlier. [00:52:22] Like, um, they're, they're just easier to use for non-technical people.  [00:52:26] Sunil Pai: That's a good, you you're talking about why did we even start talking about this? What did you want to talk about? Uh, we were talking  [00:52:33] swyx: about like, uh, 32 JavaScript. Um, so I think we kind of like dealt with those, those, uh, those topics.  [00:52:39] Was there anything else that you want to talk about? [00:52:40] Didn't JavaScript land,  [00:52:42] JavaScript Twitter and Notion's 9mb Marketing Site  [00:52:42] Sunil Pai: I don't know if you have noticed, but I've kind of actually stopped engaging in the JavaScript discourse on Twitter specifically, which actually hurts me like a little bit, because that's where all my jobs could friends are. And that's kind of like, I've seen it all. I've seen JavaScript router now for the last 11 years, I would think 10, 11 years that I've seen it. [00:53:02] And I used to like participate very heavily. And back to the thing that you, uh, that we were just discussing about the conversations that happened too, about like SBA versus MPA and about like the whole notion blow up about how they made them thing into like 800 KB. Yep. Uh, the easiest kind of discourse to have is to have like one absolutist opinion, uh, that I saw a number of people in like those threads and the surrounding threads have, which is a, well, this is bad or this is good. [00:53:35] And, uh, that's, that's all I got to say about it. Now give me like 40 likes on this reply industry. Uh, whereas like there's real opportunity here to understand how and yeah, that's the one, that's the one with treat by the way. Clearly it got like attention. No,  [00:53:51] swyx: by the way I phrased it very neutrally. I actually was pretty careful. [00:53:54] Cause I knew that it's going to attract some buzz. I had no idea what's going to be this much, but  [00:54:00] Sunil Pai: no, no, no. But like I'm so interested in talking about, uh, so this is what I was talking to you about, which is like, it's not just about a website at one point of time. It's about the system that generates these kinds of like artifacts, uh, of, so for example, with what, what did they say? [00:54:24] They're there 8 47 KB right now. They're not 8 47 KV today. They were 8 47 KB. When you, uh, Uh, tweeted this, uh, on the 11th, they are not in 47 KB. Now they might be 852, or they might be 841. Are you about to check?  [00:54:43] swyx: No, no, no, no, I'm not. I'm not, it doesn't matter. The exact number. Doesn't matter. I'm going to give you another example, which also came up, which is Netflix. [00:54:49] Remember they ripped out react and he said they have react back  [00:54:54] Sunil Pai: on Netflix. I use, are you serious on that? Wait, did they have like both Netflix, they have both react and jQuery, jQuery and react on that page right now. It's just, but like, for me, it's interesting that, which is like, I think the most insightful tweet in this was very pointed out that nobody noticed this until they told it to us. [00:55:16] Nobody saw it. It bothered. Yeah. That's the one, like nobody bothered about it. It was still making the money. They were happy about it. And they wanted to share that. And we need more of them. We need more people to be like sharing the process because if we react very badly to these things, then fewer people will want to actually share the numbers. [00:55:34] And you won't learn from the industry, but I don't know whether it's a good thing or a bad thing. It does mean that you can make a multi-billion dollar company with a marketing site. That's nine MB of Charles' script. And I think, I think people who have very strong opinions about how much jealous should be on a page to take a step back and wonder how do you make it? [00:55:55] So like, how do you, from the very beginning of like running your company, how do you make it so that it doesn't go up beyond that? Also, what opportunities are you abandoning by focusing on making sure your marketing page, uh, has like 100 KB of JavaScript instead of like nine MB  [00:56:17] swyx: shipping velocity, right? [00:56:19] Sunil Pai: You are somewhere, you are spending effort on it somewhere. Just so we're clear because somebody will look at it and say, fuck you, are you suggesting that we all put in that's not what I'm saying. I'm just saying that the resources, that word, but resources at these companies are limited and they are, they they're prioritized and sequenced and you should ask yourself in what order you want to do it and who you're trying to please, are you trying to please your customers and your users or the peanut gallery on Twitter? [00:56:48] And I think that's something that like, I, it's why I don't engage so much anymore because it's so hard to communicate in once and somebody will come in with a, well, fuck you, you work for Facebook or used to work for Facebook. What would you know? I'm like, you got me that kind of ends the conversation that, right. [00:57:04] Like I'm studying contributed to babies being burned alive or whatever it is like, this is what it is.  [00:57:12] swyx: Um, it's a nuanced debate, like, uh, because they also did some like notion clearly did some stupid stuff here. Right? Like it, it, they could have spent a day. Uh, so do you know why it was 9.9 megabytes?  [00:57:25] Sunil Pai: If I understand it was the whole notion that that was being used, the  [00:57:27] swyx: whole app. [00:57:28] Yeah. They were shipping the whole, there was actually someone from notion, uh, answering me. Uh, it's here. Yeah. This guy's, this guy works at notion before the marketing site was another route in our, at the time 9.1 NBME and app, we load the whole app just to show the sign up button. [00:57:44] So what,  [00:57:45] Sunil Pai: what it's worth Facebook sign up page does start prefetching actual Facebook code so that once you log in it loads instantaneously. So there's a reason to do it. It's just that it shouldn't be nine and B of course. That's  [00:58:00] swyx: yeah, they could have like took a day every, every six months or something like perfect day, you know, and do that. [00:58:06] So that's why I'm hesitant, uh, giving them a pass for like, okay, so what your multi-billion dollar company? This is embarrassing. This is just an unprofessional. Um, so yes,

In today's episode, we have a fun and insightful conversation with two guests, Bret Nelson and John Cerqueira. In two of our previous episodes, we had amazing conversations with both these guests, and today we're talking about the concept of plateaus.  Throughout the episode, we talk about what it means to be stuck in plateaus, identifying whether we're on a plateau and some of the things we can do to move on from a plateau. Understanding Plateaus  - Throughout our life journey, we might encounter different levels of life; in other words, valleys, peaks, and plateaus. And each of these may mean something different for each of us. We talk about what being stuck on a plateau may feel like.Evaluating Ourselves – In order to move on beyond a plateau, we need to realize that we are on a plateau. Our guests share their thoughts on how to evaluate our lives and identify whether we're at a plateau.People and Relationships – The people we surround ourselves with and people who are closest to us can influence us heavily. We talk about how to manage communications, information, and relationships in a way that helps us move on from our plateaus.Resting – Sometimes, when we're trying to move from one phase of our lives to another, we might need some rest between those phases. And taking these rests does not necessarily mean we're stuck on a plateau. Our guests share their thoughts on distinguishing the difference between the two concepts.  Connect with BretLinkedIn: linkedin.com/in/bretjnelson Website: bretjnelson.comConnect with JohnLinkedIn: linkedin.com/in/john-cerqueira-5a22963/ Mentioned in the episode:How Will You Measure Your Life? by Clayton M. Christensen, James Allworth, Karen Dillon: goodreads.com/book/show/13425570-how-will-you-measure-your-life

Join us for a great interview with Jeff Haugland, EOD (ret) Army combat veteran, and co-founder of  Invictus Project.  He shares his own personal story with TBI, PTSD, suicidal ideation  and how he found hope. Jeff is dedicated to helping other veterans that may share a similar story through his work with Invictus Project. Their mission is " To empower veterans to live more fulfilled lives by treating the root cause of traumatic brain injuries (TBI), Post-Traumatic Stress Disorder (PTSD) and Depression. Resources: Invictus Project – www.invictusproject.orgTed Talk – Prisoners of the Mind - https://www.ted.com/talks/jeff_haugland_prisoners_of_the_mindBooks: The Alchemist by Paulo Coelho How will you measure your life?  Clayton Christensen, James Allworth, Karen DillonSupport the show (http://weblink.donorperfect.com/BehindTheWarrior)

James Allworth is a man of many talents. He is co-author of How Will You Measure Your Life w/ Clay Christensen & Karen Dillon, co-host of the Exponent Podcast 7 Head of Innovation at Cloudfare. James shares life & work lessons from the Late Prof Clay Christensen. We discuss work culture & work/life balance. We also discuss Big Tech and market power. We also discuss Tik Tok and Hauwei and privacy concerns. You don’t want to miss this engaging episode that covers a range of topics. Show Notes:  Podcasts:  James likes podcasts that play electronic dance.  He says these are great to work out to.  Books: The Innovators Dilemma by Clay Christensen; Guns, Germs & Steel: The Fate of Human Societies by Jared Diamond; The Black Swan:  The Impact of the Highly Improbable by Nassim Nicholas Taleb    

Today’s guest on the “Phil with F30” podcast is Farryn Weiner – Founder of FarrynHeight Forbes List: USA Year: 2014 Category: Marketing & Advertising By recognizing her skills as a storyteller and marketer, Farryn Weiner positioned herself as the leader of social strategy for Michael Kors. When social media was in its infancy, Farryn took a risk in creating the first Instagram ad ever! That risk paid off and proved that Farryn was ahead of the trend in creating social media and understanding consumer behavior shifts. Farryn has also held social media positions at Jetsetter.com and the Sweet Green restaurant chain. When the entrepreneurial itch came, she started FarrynHeight. Her work is still about telling stories to build brands while helping companies identify and solve their marketing challenges. I’m impressed with Farryn’s ability to inspire business leaders to access their core values. It’s also a reflection of how she leads her life and her business. We discuss: The excitement of creating the first Instagram ad. Using critical feedback. The importance of authenticity in brand building. Her focus on strengths, not weaknesses. Self-funding success. Shedding fear. Big sister leadership style. Hiring for strengths and values, and not skills. Farryn shares valuable work and life lessons.  It’s also a common theme in her new podcast.  I hope you enjoy our conversation. “Under 30 Seconds Round” 1. What is the book you’ve gifted more often than any other book, and why? How Will You Measure Your Life? by Clayton Christensen, James Allworth and Karen Dillon.  Clayton is the first person who got me thinking about how I can be happy and successful in my career at the same time. 2. What’s one of the best investments and one of the worst investments you’ve ever made and why? Best - Investing in myself. Worst - Thinking about what I should invest in. 3. What’s the most impactful thing you do in your Morning and Evening routines? AM - Concentrate on breathing. PM - Take a bath when I can as it’s a forced calm. 4. Pretend you won the Peter Thiel Fellowship and you were going to get money to start a business instead of going to college, what’s the very first thing you’d do to start a new business? I would “ask why,” start understanding the why, and look for the problem rooted in the why. 5. What’s something you never knew you needed? An infrared sauna and a heated blanket. In the REVIEW SECTION, please let me know… The city / country you’re tuning in from! How Farryn Weiner’s story has inspired you! And, your favorite part of this episode! Tell me the questions you’d like me to ask future Forbes 30 Under 30 Members!   GUEST INFO: Farryn Weiner - Founder of FarrynHeight CONTACT: Twitter @jetsetfarryn and Instagram @jetsetfarryn WEBSITE: https://www.farrynheight.com/ PODCAST:  www.farrynheight.com/podcast HOST INFO: Phil Michaels SOCIAL: @iamphilmichaels YOUTUBE: www.youtube.com/philmichaels PODCAST WEBSITE: www.philwithF30.com PHIL’s WEBSITE: www.iamphilmichaels.com Learn more about your ad choices. Visit megaphone.fm/adchoices

Hear key takeaways from the book How will you measure your life by Clayton Christensen, James Allworth and Karen Dillon. Our featured guest for this episode is Madhavi Ravanan. Madhavi Ravanan is a Technology Executive based in Chennai, India. She is currently the SI Delivery Head for Nokia Telco Cloud and held past roles at Wipro and Aricent. She loves leading global teams and solving complex business problems.   

We use Clay Christensen's framework of marginal costs vs full costs to talk about what's wrong with the way so many Americans are thinking about the coronavirus:- Bryan shares his day-to-day experience of being in Japan and how much more unified the Japanese response compared to America- The bad logic many people use when they distrust organizations who don't get everything right from the beginning- The problem of too many voices and too much distrust- Why Bryan is cynical about the media and its structural bias toward manipulating emotions to sustain attention- The responsibility we need to take to make good decisions for everyone in our community- Clay Christensen's idea of marginal costs and full costs, and how we tend to put a lot of emphasis on the marginal costs and not enough attention on the full costs- What may have been true about the coronavirus three months ago can be different today, and the full costs need to be taken more seriously now- The importance of seriously asking the question: "What will I do if somebody in my life gets it?" and having a plan for that unlikely scenario because even though it's unlikely, the effects are huge- The reality of how we overestimate the effect of marginal costs and why that leads us to make bad decisions- Why we can think this way even if we don't believe the worst case scenario is going to happen; and why using driving is a good way to compare the current situation to something we do consistently- Why we felt it is important to address these topics as a mission-based company focused on helping people chase their dreams- Why it's important to stick with it, don't get yourself down about the inconveniences and sacrifices, and make sure you come out of this healthyIf you liked this episode, you may also like our interviews with Ben Auerbach and Ron Sarmiento.Recorded July 15, 2020.ReferencesJapan's "3 C's" - Ministry of Health, Labor & WelfareHow Will You Measure Your Life? by Clay Christensen, James Allworth & Karen Dillon - AmazonYou Can't Go Be More if You're Dead - Go Be More BlogCoronavirus is a Local Challenge and Your Actions Matter - Go Be More BlogPlans are Worthless but Planning is Everything - Go Be More BlogHosts:Bryan Green, @sendaibry, Go Be More BlogJon Rankin, @chasejonrankin, Go Be MoreLinks:Go Be More websiteGo Be More YouTube ChannelFeedbackSubscribe on your favorite player:Simplecast

Mark Johnson is the co-author of the book, Lead from the Future: How to Turn Visionary Thinking into Breakthrough Growth. Mark offers creative and different ways of approaching the future. Timing is always everything and it can be tricky for leaders to gauge when it makes sense to act. To navigate, you need a north-star vision for your company.   Key Takeaways [3:15] Mark discusses the passing of Clayton Christensen and the impact he has made on his life and the lives of many others. [6:45] Small businesses have the opportunity (and flexibility) to reinvent themselves. You don’t have to go down with the sinking ship. [11:10] Nobody has a crystal ball about the future, but business is in business for the customer. Look to the customer and their needs when adapting your services. [13:35] Timing is always everything and it can be tricky for leaders to gauge when it makes sense to act. To navigate this, you need a north-star vision for your company. [15:10] It’s a risky time for businesses, which means they need to start getting good at learning, and quickly adapting from those insights. [22:05] We often look for constraints before a project has even begun. However, if we put constraints on it prior to the request, the mind is forced to think outside of the box to solve the task at hand. It’s a creative way to use psychology to help spark innovation. [23:55] With information technology, our brains get easily distracted, which means our room for creativity becomes less and less. [24:55] The cavalry is not coming. You have to break free from your biases. [25:55] Mark shares examples of companies thinking in the future instead of the present. Like, how do you completely prevent a disease from occurring, and prove that you’ve actually prevented a disease? [32:45] The truth is, we’re not necessarily risk-averse, we just don’t know how to properly manage risk. [39:55] Develop a compelling vision, align the organization, and then motivate/reward to allow it to stick.   Quotable Quotes “It’s not an either/or. Yes, you want to have a good professional career, but it can’t be a replacement for your family.” “Entrepreneurs, to begin with, are resourceful people, they are imaginative people, they are visionaries.” “It’s more important to have the right way of thinking and a process that enables you to be forward-looking at the same time as operationally-oriented.” “It’s a risky time and the only way to mitigate risk is to be good about learning. In order to be good about learning, you’ve got to be good at running experiments.” “With information technology, we’re much more hunkered down with the volatility and uncertainty of the world to try and address the here and now.” “Everybody in the organization doesn’t need to be creative. However, you’ve got to bring everyone in your organization along through your communication and explain the reasons why creativity is important, even for those who are not involved directly.”   Resources Mentioned Innosight.com Connect with Mark on Twitter: @InnosightTeam & LinkedIn Mark’s book: Lead from the Future   How Will You Measure Your Life?, by Clayton M. Christensen, James Allworth, and Karen Dillon   “Leaders, Do You Have a Clear Vision for the Post-Crisis Future?” “The Innovator’s DNA”   The Leadership Podcast is Sponsored by:     Cultivate Grit. Amplify Action. Investing in yourself isn’t selfish. Click HERE to get gritty!     Free downloads of Quick Reference Guides on Delegation, Time Management, Sales, and more.    

Sam Bakhtiar is a doctor, CEO, author, world-class bodybuilder, and multi-millionaire entrepreneur. He runs a fitness franchising business, The Camp Transformation Center, with 110 locations and two different supplement and nutrition companies. With a Bachelor’s degree from Pennsylvania State University in sports science and life science and a doctorate from Los Angeles College of Chiropractic, Dr. Bakhtiar has helped over one hundred thousand people transform physically and mentally. He specializes in helping people get to the top 1% in any and every aspect of their life. Dr Bakhtiar applies his business acumen and coaching to The 1% Club, helping others to become a 1%er by rising above. He is also the author of the popular books The Total Body Transformation Secrets and Becoming a One Percenter. Dr. Bakhtiar’s passion for transformations began by transforming his own physique from a scrawny, awkward kid to a Champion bodybuilder with 23 major bodybuilding titles including Mr. Orange County, Mr. Pittsburgh, Mr. California, Emerald Cup, Tournament of Champions, as well as placing runner up in Mr. USA. He has over 18 years experience in coaching professional, collegiate, and recreational athletes from all sports. Today, he is a proud husband and father of two beautiful girls and a devoted family and businessman because “Success without fulfillment is the ultimate failure.”   Connect Linkedin – https://www.linkedin.com/in/sambakhtiar/ Facebook – https://www.facebook.com/OfficialSamBakhtiar/ Twitter – https://twitter.com/fitnessconcepts Instagram – https://www.instagram.com/sambakhtiar/ Youtube – https://www.youtube.com/channel/UC_z9K2VaB3DNBxxyzkoIIjw/videos Website – https://sambakhtiar.com/   People Mentioned Kobe Bryant – https://twitter.com/kobebryant Dwayne Johnson – https://twitter.com/TheRock   Resources Calm – https://www.calm.com/ Spotify – https://www.spotify.com/   Books How Will You Measure Your Life? by Clayton M. Christensen, James Allworth,  and  Karen Dillon: https://amzn.to/3chggqg

Lumost'un 15. bölümünde bir platform şirketini analiz ederken nelere bakmamız gerektiğini anlamaya çalışıyoruz. Platform şirketlerini analiz ederken kullanabileceğimiz 6 farklı kriteri detaylı şekilde analiz ediyoruz.1) Network Etkisi2) Rekabet Avantajı3) Network Yapısı4) Kullanıcı Bağlılığı5) Geleneksel Sistemlere Uyumluluk6) Tedarikçi GücüBölümün sonunda platform şirketlerine yatırım yapmak isteyenler için, WisdomTree'nin PLAT isimli etf ile ilgili de küçük bir bilgi var. Podcast'in tam metnine ve kullandığım kaynakların detayına lumost.net'den ulaşabilirsiniz.Bu podcast'i hazırlarken kullandığım kaynaklardan ilki stratechery. Ben Thompson tarafından hazırlanan blog benim başucu kaynaklarımdan biri. Yine Ben Thompson ve James Allworth tarafından hazırlanan exponent isimli podcast de bu podcast'i hazırlarken oldukça yol gösterici oldu. Kullandığım ikinci kaynak da geleneksel işletmelerin platform iş modeline dönüşmeleri için danışmanlık hizmeti veren Applico. Şirketin sahibi Alex Moazed de platform konusuna takıntılı bir isim. Onun da haftalık olarak yayınlanan Winner Take All isimli bir podcast’i var. Ayrıca Applico’nun web sitesinde de düzenli olarak platformlar üzerine yazılar kaleme alıyor.Kullandığım bir diğer kaynak da Harvard Business Review dergisi makaleleri.

So reads the title of a chapter in the book by Professor Clay Christensen, Efosa Ojomo and Karen Dillon, The Prosperity Paradox. The concept of looking at markets from different perspectives is at the heart of this optimistic yet practical book, in which the authors apply robust management theories to help leaders uncover and capture opportunities in developing markets. Read the full article at https://outsidelens.com/see-the-world-through-new-lenses/  Links and Resources Mentioned in This Episode: The Prosperity Paradox: How Innovation Can Lift Nations Out of Poverty by Clayton Christensen, Efosa Ojomo and Karen Dillon Efosa Ojomo's Website Christensen Institute How Will You Measure Your Life by Clayton Christensen, James Allworth and Karen Dillon Transforming Standards of Patient Care with Vas Narasimhan

(NOTAS Y ENLACES DEL CAPÍTULO AQUÍ: https://www.jaimerodriguezdesantiago.com/sin-categoria/47-un-mundo-estancado-guerras-mundiales-cohetes-espaciales-y-un-bote-de-ketchup/)Quizás decir que todo es mentira es exagerado. Pero… ¿y si nos estamos engañando a nosotros mismos?Hará unos 6 meses escuché el primer capítulo de un podcast realmente peculiar. Se llama The Portal y su autor es Eric Weinstein, que es el director del fondo de inversión de Peter Thiel. A su vez, Thiel fue uno de los fundadores de PayPal y a día de hoy es uno de los inversores más exitosos y también polémicos de Silicon Valley.Me recordó que, hace unos cuantos años ya, la revista del MIT, el MIT Technology Review, hizo una entrevista y una portada sensacional con Buzz Aldrin, el primer hombre - junto a Neil Armstrong - en pisar la luna. En la portada había una frase que nunca se me olvidará:“Me prometistéis que colonizaríamos Marte. En su lugar, tengo Facebook”Y es que llevamos ya muchos años repitiéndonos un mantra sin cuestionarlo. Nos asombramos, una y otra vez, de la increíble velocidad a la que avanza la tecnología. Es algo que yo mismo te he dicho muchas, muchas veces en este podcast.Pero también hay quien piensa, y es lo que denunciaba esa portada, que parece que hemos renunciado a resolver grandes problemas. Que en un momento dado, pasamos de enviar nuestras mejores mentes a campos como la mecánica cuántica o la investigación médica a dedicarlas a inventarse algoritmos para vender anuncios o a hacer trading de alta frecuencia en bolsa para especular aún más rápido.Incluso en el mundo de los bits estamos empezando a ver una cierta desaceleración. El iPhone es, esencialmente, el mismo cacharro que hace 6 o 7 años. Sí, te permite hacer fotos más cuquis, se puede mojar y cargar sin cables… pero digamos que estos no son avances tecnológicamente revolucionarios.Y es que es difícil ir más allá de acceder a todo desde cualquier lugar y en cualquier momento.En este capítulo de kaizen quiero intentar explorar estas ideas y mis propias dudas. Y en cierto modo, también, desafiar mis convicciones.

How can you find satisfaction in your career? How can you find happiness in your relationships? How can you live a life of integrity? Clayton Christensen, James Allworth, & Karen Dillon teach management theories to answer these crucial life questions. Anonymous Feedback: bit.ly/MagnaVitaFeedback

Books Reviewed: Upheaval: Turning Points for Nations in Crisis by Jared Diamond Then It Fell Apart by Moby Fall; or, Dodge in Hell: A Novel by Neal Stephenson To Live and Die in LA (Podcast) Hosted by Neil Strauss Left For Dead: 30 Years On - The Race is Finally Over by Nick Ward and Sinead O'Brien Alone: Britain, Churchill, and Dunkirk: Defeat into Victory by Michael Korda How Will You Measure Your Life? by Clayton M. Christensen, James Allworth, and Karen Dillon Bloodchild and Other Stories by Octavia E. Butler

(NOTAS DEL CAPÍTULO AQUÍ: http://www.jaimerodriguezdesantiago.com/kaizen/17-mis-podcasts-preferidos-tres-meses-de-kaizen-y-cambios-profesionales/) Te advierto que el capítulo de hoy va a ser un poco raro... más que nada porque va a ser bastante más personal de lo habitual. Pero es que se me han juntado un par de cosas que contarte, así que he decidido mezclarlas con un tema que tenía pendiente desde hace tiempo y que no tenía claro si daba para un capítulo propio: te voy a recomendar algunos de mis podcasts preferidos. ¡A ver qué sale!

Ben & Jay have the unique pleasure of speaking with Karen Dillon, NYT best-selling author and former editor of the Harvard Business Review, about her being in “the front seat of the Clay Christensen experience” through years of collaboration with Clay and some of their incredible colleagues.  Karen may refer to herself as “semi-retired”, but she sounds pretty busy and is having great impact on the world as a co-author of The Prosperity Paradox with Clay and Efosa Ojomo (featured in Episode 40), and as Editorial Director of BanyanGlobal Family Business Advisors.  In addition to talking about The Prosperity Paradox, Karen provides a master class on writing, reflects on her collaboration with Clay and James Allworth on How Will You Measure Your Life, and what it was like to work with Bob Moesta on Competing Against Luck.  Take a “time dash” with the Sherpas and Karen to hear how Clay's theories have evolved – and how they can impact an individual on a personal basis.@KarDillon #ProsperityParadox @CompetingvsLuck #HowWillYouMeasureYourLife@claychristensen @jamesallworth @EfosaOjomo @bmoestaStick around past the closing music for an outtake on how Twitter fulfills a Job to be Done for Karen and Jay.Medium - Why I Hired Twitter - A Sherpa's Guide to Innovation is a proud member of the Health Podcast Network @HealthPodNet -Support the show (https://healthpodcastnetwork.com/)

Janet shares Just 3 books in the "Personal Development" category to help improve yourself and your life. She also announces "Recommendations," a brand-new feature on Nonfiction4Life podcasts.  00:20   Another episode of “Editor’s Picks” from the “Personal Development” category 00:25   Two other EP episodes (#20-Home & Family; #47-Biographies & Memoirs) 00:40   N4L adding “Recommendations” to the podcast; stay tuned to the end! 01:10   Just 3 Personal Development books 01:40   1st book: How Will You Measure Your Life by Clayton Christensen, James Allworth, and Karen Dillon 01:50   Impressive resume includes being named “the world’s most influential thinker 02:50   Health fails; he’s a Harvard Business School professor, but he can’t write or speak 03:20   Relearning is demanding, slow, and discouraging 03:35   Arrives at a “fork in the road” where he decides his true purpose in life 03:50   1. Encourages his students to use time at school to figure out their lives’ direction 04:30   2. Gives smart people permission to make family and home life top priority 06:00   HBS class reunions full of extremely successful, very unhappy people 06:55   3. Helps students use theories to predict the trajectory of their lives 07:30   Bottom line: he helps people choose happiness and joy over everything else 07:50   2nd book: Designing Your Life: How to Build a Well-Lived, Joyful Life by Bill Burnett and Dave Evans 08:10   Authors teach popular design course at Stanford University 08:15   Apply design principles and processes to help people design their own lives 08:45   1. Visual dashboards: how you’re spending time; “Odyssey Planning 101” (5-year plans) 09:30   2. Emphasizes the positive (look back at “peak experiences"; focus on offers, not jobs) 10:00   3. Being, Doing, and Becoming cycle emphasizes growth 10:55   3rd book: Grit: The Power of Passion and Perseverance by Angela Duckworth 11:05   Good news for non-geniuses working hard: grit can be learned! 11:15   Duckworth supports ideas with research 11:25   1. Found grittiest adults in their late 6os, and the least gritty in their 20s 12:15   2. Finding your true passion takes time, sometimes years 12:40   3. How to grow grit from the inside out 12:50   “Grit Grid” charts commitment to outside activities and attached recognition 13:45   Follow-through & commitment to extra-curricular requires selection and cultivation 14:35   Discover your own level of grit using Duckworth's 10-Question Grit Scale. 14:50   Intro to N4L’s first-ever Recommendation 14:55   Janet’s mother, Mrs. Tanner, just turned 98 years old and has dementia         15:10   Story of her forgetting how many children she has 15:30   Janet chooses to laugh; takes comfort knowing part of her brain works really well 15:45   Mom knows all the lyrics to hundreds of songs 16:10   Other older people suffering from memory loss can also be amazing, but changed 16:20   Teddy from the UK got Alzheimer’s and became aggressive and ill-tempered 16:30   His son Simon wanted to remember his father’s better side and his strong tenor voice 16:45   Simon takes Teddy for drives, plays music familiar to his father 16:50   Simon records father-son duets of Teddy’s signature songs; posts on YouTube 17:00   Teddy named “The Songaminute Man” 17:10   Videos go viral 17:15   Janet recommends "The Songaminute Man" YouTube video "Cuando, Cuando, Cuando" 17:25   Simon crowdsources to fund professional recordings; proceeds help Alzheimer’s research BUY How Will You Measure Your Life? BUY Designing Your Life: How to Build a Well-Lived, Joyful Life BUY Grit: The Power of Passion and Perseverance Connect with Nonfiction4Life:  Facebook Instagram Twitter YouTube  Website Special thanks… Music Credit Sound Editing Credit  

Today's guest is David Lancefield. David is a Partner in Strategy&, PwC. David is a TEDx speaker and has been featured In the Harvard Business Review, Huffington Post, Financial Times and numerous other publications. He is also the host of his own podcast ‘transformation talks' which I'd highly recommend checking it out David's approach and outlook are hugely refreshing and something that anyone with aspirations of make Partner should take note of. If you want to get a flavour for this you can check him out on twitter @Dlancefield and see the thought provoking posts he puts out on a daily basis. David has a huge amount of experience and shares so many great insights in this conversation including: The importance of being yourself at work and what this means both for project managers and project team members. How to find your sweet spot and let others know what you're good at. The importance of feedback both up and down a Consulting firm's hierarchy and the mistakes people make in giving and receiving feedback that hold them back. How to make Partner in a big 4 firm and the common mistakes that those who fail to get there make. The importance of developing and managing your personal brand as a Consultant both within and outside your firm. And much, much more! Having listened to the first episode of David's Transformation Talks I thought this would be a good interview and I have to say it exceeded all of my expectations! In-depth and actionable advice from a senior leader in one of the world's biggest Consulting firms. I hope you enjoy it. You can find out more about  David on his Linked In Page https://www.linkedin.com/in/davidclancefield/    And on Twitter - https://twitter.com/Dlancefield?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor   Specific Things We Discuss in the show: Dan Cable - https://www.linkedin.com/in/dan-cable-a0b581a0 Transformation Talks by PwC - https://itunes.apple.com/us/podcast/transformation-talks/id1400295044?mt=2   PwC's apprenticeship scheme - https://www.pwc.co.uk/careers/school-jobs/jobs.html   David's TED talk “How business can tap into all of our special needs“ - https://www.youtube.com/watch?v=ezXZ4z9QqiI The Alchemist by Paulo Coelho - http://amzn.eu/enn0cvN How will you measure your life? by Clay Christiensen, Karen Dillon and James Allworth - http://amzn.eu/3zScfNe   Alive at Work by Dan Cable - http://amzn.eu/04NezdI

Workplace messaging app Slack provided a much needed centralized solution to teams that had been struggling to stay connected via a convoluted mish mash of email, Skype, text, WhatsApp. But with only eight employees, none of them in marketing or sales, the question became: "how to share this with the world?" Slack's Ali Rayl and Stewart Butterfield explain how various levels of the customer experience were key to its roll out and quick rise. James Allworth of the podcast Exponent explains why it stuck, and Nate Brown of the CX Accelerator breaks down Slack's exemplary customer support. While customers Kevin Susman of Matrixx Software, and Jeanette Jordan and Amber Carson Miller of the AdRoll Group, describe why Slack is now an integral part of their work day. Repeat Customer is an original podcast from Zendesk, because the best customer experiences are built on Zendesk. Learn more about the podcast at zendesk.com/repeatcustomer You can rate or review Repeat Customer at Apple Podcasts. We'd love to know what you think.

Your Innovation Engine Sherpas explore the new Amazon-Berkshire Hathaway-J.P. Morgan Chase venture through the lens of Aggregation Theory. So what's that? Don't worry, we'll explain it! Special thanks (an understatement) to Ben Thompson of Stratechery and the ExponentFM Podcast and his podcast partner James Allworth. Ben's understanding of Amazon's strategy and business model, and his formulation of Aggregation Theory are absolute must-reads for anyone trying to sort out what might transpire in the years ahead. We are grateful to Ben and James for their insight, and for teaming up on our favorite podcast. Yes, some of us in health care are listening, and we totally grok it! https://stratechery.com/2018/amazon-health/ https://itunes.apple.com/us/podcast/episode-139-amazon-and-health-care/id826420969?i=1000401315874&mt=2 https://stratechery.com/2016/the-amazon-tax/ https://stratechery.com/2017/amazons-new-customer/ https://stratechery.com/2018/amazons-go-and-the-future/ Support the show (https://healthpodcastnetwork.com/)

Two days ago I had the privilege of moderating a roundtable with some of the smartest futurists and forward thinkers in the industry. Our panelists included Tim O'Reilly, James Allworth, Ben Gilbert and Jeff Morris Jr. [VIDEO REPLAY] The State of Consumer Tech Roundtable with Tim O'Reilly, James Allworth, Ben Gilbert… It was an interesting... The post  Why Your J Curve is Actually an S Curve and TAM is a Meaningless Metric appeared first on The Syndicate.

Two days ago I had the privilege of moderating a roundtable with some of the smartest futurists and forward thinkers in the industry. Our panelists included Tim O'Reilly, James Allworth, Ben Gilbert and Jeff Morris Jr. [VIDEO REPLAY] The State of Consumer Tech Roundtable with Tim O'Reilly, James Allworth, Ben Gilbert… It was an interesting... The post  Why Your J Curve is Actually an S Curve and TAM is a Meaningless Metric appeared first on The Syndicate.

The Syndicate hosted The Future of Consumer Tech and Humanity Roundtable on 12/20/17. Our Expert Panelists: Tim O'Reilly is a futurist that has reshaped the computer industry, coined the terms “open source software”, “web 2.0” and “the Maker movement” and had a hand in framing each of those big ideas. He is the founder, CEO, and... The post The Future of Consumer Tech and Humanity Roundtable with Tim O'Reilly, James Allworth, Ben Gilbert and Jeff Morris Jr. appeared first on The Syndicate.

The economy is important — very important. But is that because it matters in and of itself, or because it's the engine for achieving the things we really do care about? Here at Techdirt we've always been strong advocates of the free market, but we've never been absolutists about things like regulation, and we believe it's very important to explore these issues in detail. This week on the podcast we're joined by James Allworth, co-host of the Exponent podcast and author of a recent post entitled Prioritizing Economics is Crippling the U.S. Economy, to discuss entrepreneurship, democracy, the economy and more. Read the article: https://medium.com/@jamesallworth/the-slow-decay-of-americas-entrepreneurial-society-f9aeb6145891

For the second episode of Season 2 extra-special US-based guest corespondent Courtney Mitchel joins Morris for a wide-ranging discussion of work and labor. Show NotesA clip of Ronald Reagan in Bedtime for Bonzo (1951)Some of the best episodes of Accidental Tech Podcast are when they (despite some initial reluctance) talk about gender and sexism in tech: Episode 57, Episode 58, Episode 116, Episode 117, etc.John Siracusa and Casey Liss talk about misspeaking on sensitive and charged subjects in Episode 57, a discussion followed quickly by Casey unintentionally misspeaking.Harajuku Data Lake Episode 2: Why do we work?Indiana’s anti-LGBT law, signed by then-Governor Mike PenceNo I don’t want to “be a man”: 15 Problems Only Butch Lesbians Understand (Cosmopolitan)A Schmierkase/“Cup Cheese” recipe. There are surprisingly few results for “Schmierkase” online, and most seem to be on personal blogs, forgotten forums, or minor recipe sites that appear to have last seen a redesign in the early 2000s.Incidentally, this is sort of how the web felt in the mid-90s: Many small independent sites, lots of quirky and amateur graphic design, search engine results where the most interesting link was just as likely to be on the fifth page as the first, and a sense of hope and excitement that came from knowing that you–yes you!!!–could make the #1 schemierkase site in the world in just a few hours on a weekend. (Being the 1990s, it would almost certainly be called “Schemierkase World,” have a rotating 3D globe on a beige background as the logo, and be hosted on GeoCities with a WebRing on the splash page.)The ACA (Affordable Care Act), also known as ‘ObamaCare’ (Wikipedia)‘Too big to fail’: Systemically important financial institution (Wikipedia)An excellent description of the post-World War II ‘lifetime employment’ system in Japan. While this system did begin to break down in the 1990s, even in 2017 many of its features (and particularly the practice of hiring new graduates en masse based on their perceived future potential rather than what they may or may not have studied in college) remain fully intact.Bachman Turner Overdrive - Lookin’ Out for No. 1 (YouTube)Converse closing Chuck Taylor All-Star plant [2001]Nike sweatshops (Wikipedia). Two decades after the peak of the anti-sweatshop movement of the mid-1990s, Michael Hobbes offers an excellent review of its legacy, successes, and failures: The Myth of the Ethical Shopper.Shit Out of Luck (SOL)(Wiktionary)Ben Thompson and James Allworth’s excellent podcast ExponentCron (Wikipedia)Basic income (Wikipedia)“Could ‘single-payer’ be Trump’s trump card?,” an incredibly optimistic opinion piece that appeared in the Baltimore Sun in January. At this point the answer is clearly ‘No.’“Can we cure all diseases in our children’s lifetime?”

James Allworth was the Director of Strategy at Medallia, a Sequoia-backed experience startup. He writes for Harvard Business Review and is the author of the New York Times best-seller - How will you measure your life?. He also co- hosts the hugely popular exponent.fm podcast with Ben Thompson. We talk to James about ERP systems, financial and customer focused companies, and how the new economy calls for new measurement tools. For transcripts and more on the Subscription Economy, head over to www.zuora.com/podcast

Karen Dillon is co-author of Clayton Christensen's new book, Competing Against Luck: The Story of Innovation and Customer Choice” (HarperCollins, October 2016), a groundbreaking book with the potential to reframe industries. It is based on a simple yet profound idea put forward by Christensen in “The Innovator’s Solution”: customers don’t buy products and services; they hire them to do a job. And understanding which jobs your customers need done is key to innovation success. The former editor of Harvard Business Review (HBR), Karen has long chronicled the successes and failures of businesses and their leaders. Currently a contributing editor to HBR focused on the topics of leadership, managing people, managing yourself and entrepreneurship, Dillon has worked closely with some of the world’s greatest thought leaders, including Clayton Christensen, Michael Porter, Vijay Govindarajan, Daniel Isenberg and A.G. Lafley. A talented, award-winning writer, she is also a passionate, engaging speaker – and is especially skilled at personalizing the themes of her books to make them actionable and relevant to each audience. Dillon is co-author of several best-selling titles, including “How Will You Measure Your Life?” (HarperCollins, May 2012), with Christensen and James Allworth. The book, born out of a series of powerful lectures and seminars by Christensen, began with an article conceived by Dillon for HBR.   Topics Discussed: - Her new book, “Competing Against Luck” - What is a ‘job to be done’ - Identifying customer jobs to be done - “The story of the milkshake!” - Looking through a different lens, to improve innovation. - The anxiety of customer switch and buying patterns - Customer journey mapping and more - Prioritising jobs to be done ("which jobs should I build a product around?")   Show Notes:   Books: 1) Competing Against Luck - Christensen & Dillon: https://amzn.to/2DfR46q 2) The Innovator's Dilemma - Christensen: https://amzn.to/2DexZSc 3) measureyourlife.com - Karen’s story and her first book. 4) Karen's Twitter: twitter.com/kardillon ‍ --- I hope you enjoyed this episode. If you’d like to receive a weekly email from me, complete with reflections, books I’ve been reading, words of wisdom and access to blogs, ebooks and more that I’m publishing on a regular basis, just leave your details at www.futuresquared.xyz/subscribe and you’ll receive the very next one. Listen on Apple Podcasts @ goo.gl/sMnEa0 Also available on: Spotify, Google Play, Stitcher and Soundcloud Twitter: www.twitter.com/steveglaveski Instagram: www.instagram.com/@thesteveglaveski Future Squared: www.futuresquared.xyz Steve Glaveski: www.steveglaveski.com Medium: www.medium.com/@steveglaveski ‍

James Allworth, co-author of “How will you measure your life” with Clay Christensen and Karen Dillon, joined us in an interesting discussion on the book and his reflections on disruption theory. From discussing motivational factors to why you should not outsource your childcare, James offered his thoughts and perspectives to how we can draw valuable The post Episode 66: How will you measure your life with James Allworth appeared first on Analyse Asia.

In this week’s episode Ben and James discuss why California is unique, diversity and inequality, James’ work on “How Will You Measure Your Life”, making decisions, and whether or not business school was worth it for us. Links Clayton Christensen, James Allworth, Karen Dillon: How Will You Measure Your Life – Website, Amazon Hosts Ben Thompson, @monkbent, Stratechery James Allworth, @jamesallworth, Harvard Business Review Podcast Information Feed iTunes SoundCloud Twitter Feedback

In this week’s episode Ben and James discuss why California is unique, diversity and inequality, James’ work on “How Will You Measure Your Life”, making decisions, and whether or not business school was worth it for us. Links Clayton Christensen, James Allworth, Karen Dillon: How Will You Measure Your Life – Website, Amazon Hosts Ben Thompson, @monkbent, Stratechery James Allworth, @jamesallworth, Harvard Business Review Podcast Information Feed iTunes SoundCloud Twitter Feedback

Weekly JourneywithJesus.net postings, read by Daniel B. Clendenin. Essay: *"Horror Grips Me:" Remembering Congo* for Sunday, 22 September 2013; book review: *How Will You Measure Your Life?* by Clayton M. Christensen, James Allworth and Karen Dillon (2012); film review: *Fruitvale Station* (2013); poem review: *The Journey Prayer* (Celtic prayer).

James Allworth, regular contributor to HBR and coauthor of the Nieman Reports article "Breaking News: Mastering the Art of Disruptive Innovation in Journalism."

James Allworth, Harvard Business School Forum for Growth and Innovation fellow and co-author of How Will You Measure Your Life joins Horace for an in-depth discussion of the vulnerability of Apple to low-end disruption. Specifically, assuming the iPhone reaches a point of over-service, did Apple arm its suppliers with the means to create its replacement? We dip into case studies of Dell, HP, HTC and Microsoft and touch on how iPod escaped this fate.

James Allworth, Harvard Business School Forum for Growth and Innovation fellow and co-author of How Will You Measure Your Life joins Horace for an in-depth discussion of the vulnerability of Apple to low-end disruption. Specifically, assuming the iPhone reaches a point of over-service, did Apple arm its suppliers with the means to create its replacement? We dip into case studies of Dell, HP, HTC and Microsoft and touch on how iPod escaped this fate.

Total Duration 17:33 Download episode 77 Sara Adam: Making a Difference With Her Life I am recording this episode from Kuala Lumpur, Malaysia where I have the privilege of speaking at a conference this week. Since this is a very special destination, my wife and family have joined me on the trip, which included prior stops in London, Nairobi, and Doha. If all goes as planned, we hope to go all the way around the world as a family over the course of three weeks. While in Nairobi we had the opportunity to spend time with some very close family. And one of the real treats was spending time with my niece Sara Adam. Sara will soon be starting up her senior year at Duke, but she's not waiting until graduation to make a difference. Despite her age, Sara is building an amazingly cool clothing and accessory business that is based in Kenya. Along with her business partner Anna, they are growing a business they name Judith and James. They are developing marketable sewing skills for vulnerable women, most of whom live in a Nairobi area slums. As these skills are developed, they begin working on merchandise that will be sold in the U.S. and other countries. In turn, the proceeds from that merchandise will produce a sustainable income stream for the women. It's an inspiring model being driven by an inspiring young lady. Sara is in the process of making a remarkable difference in this world. How Will You Measure Success? How do you measure success in life? As professionals who lead projects, we know that defining measurable success criteria for projects is a very important and helpful practice. But what about life? There will be a day when you've finished your last project at work. Whether it's when you hang up your Gantt charts, so to speak, or come to the end of your life, how will you measure it? It's an intriguing question that is also the title of one of the most anticipated business books of this year. How Will You Measure Your Life? is authored by Clayton Christensen, James Allworth, and Karen Dillon. I recently had an opportunity to have a discussion with Karen and look forward to sharing that interview with you over the next two episodes. By the way, if you're a premium subscriber, your extra episode will show up in the podcast stream when the second part of my discussion with Karen goes live. For now, let's hear from Karen about her work with the book entitled, How Will You Measure Your Life? Thank you for joining me for this episode of The People and Projects Podcast! Have a great week!

Scott and Anders discuss the book "How Will You Measure Your Life?" by Clayton M. Christensen, Karen Dillon and James Allworth. Turning the lens from his popular business books toward the planning our lives, Clay Christensen and his fellow authors dissect the decision making processes that impact us in the most fundamental ways.