Podcasts about philosophy degree

Dr. Jerri Johnson has served 20-plus years in the field of education. She has had the honor of serving as District English Language Arts Supervisor, Principal, Assistant Principal, Instructional Coach, Reading Specialist, and Classroom Teacher at various grade levels. She is a Consultant and Author. Previously, she assumed the role of Assistant Professor for the Teachers College at Columbia University and founding Principal of a PreK-2nd grade school in Texas. Before this, she was Director of Education for the Community Impact Network, a place-based non-profit organization in Saint Louis, Missouri. In addition, Dr. Johnson has taught at the post-secondary level as an Adjunct Professor at the University of Missouri. She earned her bachelor's degree in elementary education from Harris-Stowe State University. Subsequently, earning advanced degrees at the University of Missouri: Master's and Educational Specialist Degrees in Educational Administration, then a Doctor of Philosophy Degree in Education, with an emphasis on Teaching and Learning. Jerri is a member of the Association of Supervision and Curriculum Development, the International Literacy Association, and the National Council of Social Studies.You can reach Dr Jerri at fromthedeskofthedr.com https://www.spreaker.com/podcast/inspiring-stories--2917948/support

Are you ready to be inspired by a conversation with Dr. Tania Bubb, APIC's 2024 president? Listen to this podcast to learn about her volunteerism, journey to the APIC presidency, initiatives, and values that she will promote during her leadership. Hear her discuss the importance of trust and collaboration, active listening, and valuing others' lived experiences in the infection prevention and control industry. Hosted by: Kelly Holmes, MS, CIC and Lerenza Howard, MHA, CIC, LSSGB About our Guest: Tania Bubb, PhD, RN, CIC, FAPIC Dr. Tania Bubb is the 2024 APIC President. She is Senior Director of Infection Prevention & Control at the Memorial Sloan Kettering Cancer Center in New York, NY. She has worked as an Infection Preventionist since 2006 at major academic medical centers with responsibilities spanning the continuum of care. She's served her local and national APIC Board of Directors. Prior to serving at the national level, Dr. Bubb chaired the APIC Professional Development Committee, was a member of the American Journal of Infection Control Editorial Review Board, and APIC's Practice Resource Editorial Panel. Most recently, Dr. Bubb co-chaired APIC's Health Inequities and Disparities Taskforce. She is an experienced speaker and author, having presented at local and national APIC events as well as other conferences, and authored publications related to the field of infection prevention and control. Dr. Bubb received Bachelor and Master of Science Degrees in Nursing from City University of New York Herbert H. Lehman College and earned a Doctor of Philosophy Degree in Nursing from New York University.

Show Notes: Chris Cowell, a computer science major, shares an anecdote about his college experience. He mentioned that the computer science major concentration at Harvard was different from today, and how he worked with paper and pencil more than computers. Chris talks about the multiple paths taken in life after graduating from Harvard, including working for a public service program called Vista, which was started during the Vietnam War as a way for conscientious objectors to provide service to the country. Chris was assigned to an adult literacy group in Lansing, Michigan, where he was in charge of matching tutors and literacy tutors with students who needed to learn how to read. This experience was unpleasant and lonely, but it was also a good antidote to the occasional preciousness of Harvard. Through this experience, he was able to understand the struggles of a large portion of the population, including students who struggled with brain problems, mental health issues, and other struggles. This experience helped him understand that life doesn't come easy for many people. Chris shares a few anecdotes from his time in the program, including how the term dyslexia is used, how his experience taught him that there are many reasons an adult may have difficulty learning how to read, and how he would match teachers to students. Pursuing a Philosophy Degree and Moving into Consulting Chris initially had a side interest in philosophy and decided to pursue a philosophy degree. He took two years at the University of Michigan in Ann Arbor, taking more undergraduate philosophy classes and decided to pursue a PhD in philosophy. He went on to Berkeley for grad school and spent six years there, but felt like he was barely hanging on and didn't have much to contribute. He finished the program in 2001 but decided he wouldn't pursue a career in the academic field and decided to go back into computer science. Chris was recruited by Anderson Consulting, a company that had just spun off from Arthur Andersen, which had been involved in the Enron scandal. Chris' experience with Anderson Consulting was not what he expected. He was assigned to an eight-year in-town project in Sacramento, which was a contract with the government of California to set up a child welfare website, which was unfortunate because, although he had learned theory of computer science, he didn't have the practical coding skills  to complete the project. He was given the opportunity to learn programming but later transitioned to Accenture and moved into their research and development lab in Palo Alto during the height of the innovation era in the San Francisco Bay area.  Starting a Technical Training Company Chris moved to Portland, where he worked for Oracle as a computer programmer. He worked for different companies in the Portland area, specializing in testing programs that test other programs. However, he realized that he had only been promoted once over the course of his 20-year career. This realization led him to change their focus from tech to doing technical training. Chris started a one-person technical training company, teaching people how to use software. He sold classes and in-person training to local companies and had fun building the curriculum. He also enjoyed public speaking. However, the COVID pandemic hit, but he had no marketing savvy and his company was failing.  After a few years, he got a job with a real software company, teaching people how to use their software. He recently shifted to another company, and their career now focuses on technical training, building materials, and giving presentations on software usage. Influential Harvard Courses and Professors Chris remembers a few courses from college, but he found the core science courses the most interesting. David Lazarus' Space, Time and Motion, the Recent History of Iran course, and Diana Eck's Comparative Religion course. He loved the music appreciation course taught by Louise vos Gershon, who was described as the only faculty member at Harvard without a PhD. The skills learned in music appreciation have been useful in his singing and guitar playing ever since. Chris also values learning basic music theory, which is essential for musicians who want to understand how music theory works. He also joined the Harvard Speech in Parliament and Debate society where he may have debated Ted Cruz.  Timestamps: 03:23 Adult Literacy group in Lansing, Michigan 08:51 How to pick the right student 11:19 How Chris decided to pursue a Phd 15:25 How Chris started his career in tech 22:39 On starting his own technical training company 25:41 Courses and professors that have stayed with him CONTACT:  Facebook: Cowell-shah Email. Chris@post.harvard.edu  

Getting to know Dr. James (JC) Cooley and Dr. Michelle D. Cooley• Celebrating Wedding Anniversaries and the lessons learned each year.• Why love, and a lifelong commitment despite trials and tribulations is important• What does having each other's back mean?Dr. James JC Cooley and Dr. Michelle Cooley are the Host and Co-Host of The James Cooley Show…It's Your Life Live on e360tv. They are also the Host and Co-Host of the National Live Radio/Podcast The James Cooley Show…It's Your Life. Dr. James Cooley is the recipient of The 44th (President Obama) Presidential Legacy Lifetime Achievement Award (2023) and the 46th (President Biden) Presidential Lifetime Achievement Award (2022). He also holds a Doctorate of Philosophy Degree from Trinity International University Ambassadors (T.I.U.A School of Business and part of the United Nations). Dr. Cooley is a motivational speaker and a retired Navy Officer (23 years) born in Chattanooga, Tennessee.Dr. Michelle Cooley has a Doctorate of Philosophy Degree from Trinity International University Ambassadors. She has a Bachelor's Degree in Marketing Management, and a Masters Degree in Marketing from Concordia University Nebraska. She has been part of the JC Cooley Foundation since its inception in 2014. Her continued focus is on giving back to the community and finding ways to inspire and help those in need.  Website: www.cooleyfoundation.orgBrought to you by J.C. Cooley Foundation "Equipping the Youth of Today for the Challenges of Tomorrow."Support the show: http://www.cooleyfoundation.org/See omnystudio.com/listener for privacy information.

Dr. Cheryl Wood is the CEO of Global Speakers University, a training and development company that equips women entrepreneurs and leaders with the tools to master the art of sharing their unique voice, story, message, and expert knowledge. Wood is an international 2x TEDx keynote speaker, executive speaker development coach, and 20x best-selling author who has delivered riveting keynotes for clients including NASA, Verizon, Prudential, Capital One, U.S. Department of Defense, U.S. Department of Agriculture, the FBI, The United Nations, Federally Employed Women, Blacks In Government, and a host of law firms, corporations, and international conferences.    Wood's signature conference, SpeakerCon, reaches thousands of entrepreneurs and leaders annually to provide them with strategies and techniques to “transform the world one word at a time!”    Wood has helped over 150,000 women leaders to exponentially increase their impact, influence and income by helping them to polish their stage presence, increase their platform confidence, and develop transformational messages that move audiences into decisive action that produces desired results.      Wood is the recipient of the 2021 President's Lifetime Achievement Award for dedicating more than a decade to helping women amplify their voices.  In 2019 she was awarded an Honorary Doctorate of Philosophy Degree for her commitment to educating and empowering women globally to get outside of their comfort zone and into their power zone while becoming the best version of themselves. Wood believes a woman's legacy, impact and wealth is connected to her voice and that it's time for more women to speak up!    In this episode, you will learn: Why speaking up is pivotal in your life What makign an impact does to aging well Why community is important in Midlife

This week on the KORE Women podcast, Dr. Summer Watson welcomes Dr. Jerri Johnson, who has over 20 years of experience in education, she has held multiple positions in the field, such as District English Language Arts Supervisor, Principal, Assistant Principal, Instructional Coach, Reading Specialist, she has her doctorate in Education, authored and released her new book “Imagine That! Chronicles of an Urban School Principal” and is the owner and sole consultant for EJUC8U (Educate You) Consulting LLC. She was most recently the founding Principal of a PreK-2nd grade school in DeSoto ISD, located in DeSoto, Texas. Before this, she held the position of Director of Education for the Community Impact Network, a non-profit organization that is place-based within the Normandy School Collaborative footprint in St. Louis, MO. Over her 20 plus years in education, she has had the honor of holding the positions of District English Language Arts Supervisor, Principal, Assistant Principal, Instructional Coach, Reading Specialist, and Classroom Teacher at various grade levels. In addition, Dr. Johnson taught at the post-secondary level, serving as an Adjunct Professor at the University of Missouri-St. Louis. She earned her bachelor's degree from Harris-Stowe State University in Elementary Education. Subsequently earning advanced degrees at the University of Missouri-St. Louis: Masters and Educational Specialist Degrees in Educational Administration; then a Doctor of Philosophy Degree in Education with an emphasis in Teaching and Learning. Dr. Johnson is a member of the Association of Supervision and Curriculum Development, International Literacy Association, and National Council of Social Studies.  You can follow Dr. Jerri Johnson on LinkedIn and her website at: FromtheDeskoftheDr.com and you can find her book at Barnes and Noble and on Amazon! LinkedIn:  www.linkedin.com/in/jerri-johnson-ph-d-7ba7552a Website: fromthedeskofthedr.com Book Links https://www.amazon.com/Imagine-Chronicles-Urban-School-Principal/dp/1891282255/ref=sr_1_1?crid=3KKVTHRFS95SQ&keywords=imagine+that+jerri+johnson&qid=1647108609&sprefix=imagine+that+%2Caps%2C1028&sr=8-1  https://www.barnesandnoble.com/w/imagine-that-chronicles-of-an-urban-school-principal-jerri-a-johnson/1140998697;jsessionid=4D8E41C74B8860253C68A60EAB7757E5.prodny_store01-atgap06?ean=9781891282256   ***Thank you for taking the time to listen to the KORE Women podcast and being a part of the KORE Women experience. You can listen to The KORE Women podcast on your favorite podcast directory - Pandora, iHeartRadio, Apple Podcast, Google Podcast, YouTube, Spotify, Stitcher, Podbean, JioSaavn, Amazon and at: www.KOREWomen.com/podcast. Please leave your comments and reviews about the podcast and check out KORE Women on Instagram, Twitter, and Facebook. You can also learn more about Dr. Summer Watson and KORE Women at: www.korewomen.com

Pre-Order the Leading Equity Book Today! About Jerri A. Johnson, Ph.D. Dr. Jerri Johnson is author of the book “Imagine That! Chronicles of an Urban School Principal." In addition to this she is the owner and sole consultant for EJUC8U (Educate You) Consulting LLC. In the field of education, she was most recently the founding Principal of a PreK-2nd grade school located in DeSoto, Texas. She held the position of Director of Education for the Community Impact Network, a non-profit organization that is place-based within the Normandy School Collaborative footprint in St. Louis, MO. Over her 20 plus years in education, she has had the honor of holding the positions of District English Language Arts Supervisor, Principal, Assistant Principal, Instructional Coach, Reading Specialist, and Classroom Teacher at various grade levels. In addition, Dr. Johnson taught at the post-secondary level, serving as an Adjunct Professor at the University of Missouri-St. Louis. She earned her bachelor's degree from Harris-Stowe State University in Elementary Education. Subsequently earning advanced degrees at the University of Missouri-St. Louis: Masters and Educational Specialist Degrees in Educational Administration; then a Doctor of Philosophy Degree in Education, with an emphasis in Teaching and Learning. Dr. Johnson is a member of the Association of Supervision and Curriculum Development, International Literacy Association, and National Council of Social Studies. Show Highlights Understanding a students background and trauma Supports needed for students healing from trauma Self-care as a school leader Connect with Jerri Instagram LinkedIn Website Imaging That! Chronicles of an Urban School Principal Additional Resources Learn more about the Advocacy Room Free Course on Implicit Bias 20 Diversity Equity and Inclusion Activities Annihilating Racial Injustice in School Course FREE AUDIO COURSE: Race, Advocacy, and Social Justice Studies

Our guests today is Waco Police Chief Sheryl Victorian.  Chief Victorian is a native Texan and a 28-year law enforcement professional. She was sworn in as the City of Waco's Chief of Police on March 15, 2021, after serving with the Houston Police Department for 28 years. In her role with the Houston Police Department – she served as an Assistant Chief of the Patrol Region 2 Command.  Her law enforcement experience includes assignments in the Major Offenders, Homicide, Special Victims, Internal Affairs, Training and the South Central and Southeast Patrol Divisions.  She has received a number of outstanding law enforcement awards throughout her career.She holds a Bachelor of Science degree in Administration of Justice from Texas Southern University, a Master of Science Degree in Criminal Justice from the University of Houston, and a Doctor of Philosophy Degree in Administration of Justice from Texas Southern University. In her spare time, Chief Victorian is a playwright, and enjoys traveling, mentoring, teaching, and spending time with her family. Waco PDChasing What Matters Instagram Chasing What Matters Website

Professor Jargon, Mayberry Mob, Karl & Adam's Garden, Philosophy Degree. www.charlesbursell.com

Jonathon Kendall (CEO of DealRaise, COO of LeadNurture) is an investor, author, copywriter, speaker, and avid reader. He stopped by the 4Media office to discuss personal growth, becoming an author, and why taking big risks leads to big rewards. From leading college mission trips in Guatemala to becoming CEO of multiple companies, Jonathon's path to success was filled with unexpected career changes, international moves, and a lot of philosophical thinking (though that last one is partially explained through his Philosophy Degree from Michigan State). In this episode, he chats with Eddie and Andrew about the internal keys to success, why you should focus on your personal goals as much as your career goals, and how self-awareness is the true secret behind creating success.FOLLOW JONATHON:Instagram: https://www.instagram.com/jonathon.kendall/ YouTube: https://www.youtube.com/user/jonkenda TikTok: https://www.tiktok.com/@jonathonkendall DealRaise: https://dealraise.com/LeadNurture: https://leadnurture.com/   TIMESTAMPS:00:00 - Intro01:57 - Podcast Start02:19 - Growing up in a family of coal miners05:55 - Eddie lied to his parents about his GPA18:22 - Jonathon gets invited to DC for his Voting Registration Campaign21:17 - Make a ton of money to make a ton of impact22:22 - Thought experiment - How many times can you fold a paper in half?27:18 - Building a reputation by offering value before the sale30:37 - What Eddie wants from a mentor31:15 - The impact that Agency Founders will have on the future33:47 - Jonathon humbled Ivy League students in Guatemala38:13 - Why Culture Shock is like a Psychedelic Trip41:35 - Why Mike Tyson is one of Jonathon's favorite philosophers46:01 - Jonathon published his first novel while managing a restaurant49:16 - Why Jonathon lives the “Four Hour Work Week”50:52 - If someone listened to every podcast they could write a book about Andrew52:57 - How Jonathon discovered MentorBox56:37 - Jonathon wins a copywriting competition59:04 - How Jonathon convinced his wife to move to San Francisco1:04:16 - Grinding 24/7 was Jonathon's normal1:07:57 - Why 80 hour weeks are unsustainable1:09:06 - “Show up even when it's uncomfortable”1:12:06 - Jonathon explains why investing big money into big people pays off1:16:55 - Why streaming services should have an education section1:19:08 - Why Universities should feel threatened1:20:08 - Jonathon explains what being CEO at MentorBox was like1:23:19 - WHO YOU KNOW is more important than WHO KNOWS YOU1:24:22 - The 2 things Jonathon wished they did to grow MentorBox1:29:58 - Eddie explains what an attractive acquisition offer looks like1:32:42 - Raising capital is just like selling a new product to new leads1:36:27 - "Don't be a pansy"1:37:01 - Ironman competitors are normal people too1:40:27 - Chasing goals won't fill the emotional holes in your life1:41:47 - How getting shredded taught Eddie to push through suffering1:47:11 - You have to work with the circumstances you're given1:48:37 - Never eat junk food again, but add 5 years to your life?1:51:00 - How micro decisions impact the next 50 years1:53:00 - How to approach the devil's paradox?1:58:34 - The marshmallow test2:00:17 - Do you want to live a pleasurable life now or a longer life later?2:03:24 - Jonathon explains why self awareness is necessary to create purpose2:07:35 - How many hours of useless information have you consumed?2:10:52 - Jonathon's “F U” money goals2:15:54 - The only way to guarantee that you'll make it2:16:41 - The #1 signifier of success2:21:06 - How will you compete with technological advancements?2:27:37 - Why Artists will become the gatekeepers of entertainment2:33:37 - Jonathon is next door neighbors with the governor of Puerto Rico2:43:57 - Jonathon's two companies and how they work2:49:46 - Be realistic about what you actually want2:56:57 - Your ability to stay on the edge of the next thing is more important than skills3:02:57 - Where to follow Jonathon   FOLLOW 4MEDIA:Main YouTube Channel: https://www.youtube.com/4mediamarketing Clips Channel: https://www.youtube.com/channel/UCNx7auVTseV865Mu1CZX0WQ Website: https://4media.marketing/Join Our Team: https://4media.marketing/jobs Instagram: https://www.instagram.com/4media.marketing/ TikTok: https://www.tiktok.com/@4media.marketing? EDDIE Instagram: https://instagram.com/eddiemaalouf Twitter: https://twitter.com/imakegreatads Marketing Course: https://www.brilliantmarketers.com/ ANDREW Instagram: https://instagram.com/andrew_deitsch Website: https://andrewdeitsch.comYouTube: https://www.youtube.com/andrewdeitsch

Transcript:Captain Janet:Welcome to the JP AstroCast, where we are traveling at the speed of thought. Today's episode is brought to you by Hunt Brothers Pizza. Ah, Eyezak, what are you doing?Eyezak:Hey, Captain Janet. I'm just hanging up some pictures on these walls. New crew, new beginnings, new surroundings.Captain Janet:But Eyezak, you're using nails?Isaac:How else would I hang a picture?Captain Janet:Well, I don't know, but you don't put nails in a spaceship. That might puncture our hull, and then we would lose oxygen, and we need that to breathe.Eyezak:Oh, didn't think of that. Hmm.Captain Janet:Did you just hang that picture up with your chewing gum?Isaac:Yep. Problem fixed. Right.Captain Janet:You know, this post-it was supposed to be something entirely different, so okay.Eyezak:That ought to do it. Do you think our new crew will like my decorations?Captain Janet:I'm sure they'll love it, Eyezak.EyezakOkay. Do you think they'll like me?Captain Janet:Of course, they will. Everybody loves you.Eyezak:Usually, but these kids are super genius smart. They read lots of books and do experiments and want to do awesome things in space. What if they don't think I'm smart enough to hang out with them?Captain Janet:Eyezak,I am sure they will love you. And here they come now.Kid 1:Hello.Kid 2:Hey everybody.Captain Jane:Glad you guys are here.Captain Janet:All right, crew. Welcome to Janet's planet and happy to have you aboard. First, unpack your gear in your cabins and then meet Eyezak and me in the galley for some lunch. And then we'll beam up Dr. John Grunsfeld to speak about his work on the Hubble telescope and the newest thing in space, the James Webb Space Telescope.Maggie:That's amazing.Captain Janet:See Eyezak, was that so bad? They're really cool and super accepting kids. I know new beginnings are tough, but you're going to be just fine. And one of the esteemed JP space crew.Isaac:Oh, I sure hope so. I hope I don't ask Dr. Grunsfeld any not-smart questions.Captain Janet:Oh, Isaac. Here's the thing. There are never any not-smart questions. Now let's just go get ready for lunch. Remember it's Hunt Brothers Pizza today.Isaac:Oh, my favorite! Hunt Brothers Pizza is proud to support the JP AstroCast with over 8,000 locations in convenience stores near you, finding a Hunt Brothers Pizza is easy as pie. Choose between Hunt Brothers Pizza's original crust or thin crust. And top your pizza with any of our 10 toppings at no extra charge. With that many options, there's sure to be a topping combo for everyone to enjoy a Hunt Brothers Pizza.Captain Janet:All right, everyone. Quiet, please. I would like to introduce our guest today. He is fittingly an astronaut and astronomer. Dr. John Grunsfeld hails from Highland Park, Illinois, received a Bachelor of Science Degree in physics from MIT, a Master of Science Degree, and a Doctor of Philosophy Degree in physics from the University of Chicago. Dr. Grunsfeld has four NASA space flight medals, three NASA exceptional service medals, a NASA distinguished service medal, and many other special honors.Captain Janet:Dr. Grunsfeld was selected by NASA in March 1992 and reported to the Johnson Space Center in August 1992. A veteran of four space flights, Dr. Grunsfeld has logged over 45 days in space, including five spacewalks, totaling 37 hours and 32 minutes. During STS 1 0 3, Dr. Grunsfeld and his crew installed new gyroscopes and scientific instruments and upgraded systems on the Hubble space telescope, which required three spacewalks. STS 1 0 9 successfully upgraded the Hubble space telescope, installing a new digital camera, a cooling system for the infrared camera, new solar arrays, and a new power system.Captain Janet:Those upgrades required a total of five spacewalks in five consecutive days. He's watched Hubble drift against the background of earth and stars. And he's guided new parts and instruments into the telescope and left it whole and healthy. He has helped the science missions of Hubble and envisioned science goals for the James Webb space telescope. And is now an Emeritus scientist at Godard Space Flight Center, working on Hubble observations of Jupiter's moon, Europa, and collaborating on the design of the next generation of space. serviceable telescopes. Dr. John Grunsfeld, what an honor to have you beam up today?Dr. John Grunsfeld:Well, it's absolutely a pleasure to be on. I'm excited because we are on the cusp of an astronomical revolution. And for me, my telescope is the Hubble space telescope. And what's interesting is about a third to a half of everybody who lives on planet earth has always lived in a world with the Hubble space telescope. And that's because it's been in orbit for 31 years coming up on 32. Your telescope though will be the James Webb space telescope. And you'll be learning about the new universe that the James Webb Space Telescope sees over the coming years. So thanks for having me on board.Evy:How or when did you know you wanted to be an astronomer and an astronaut?Dr. John Grunsfeld:When I was born, 1958, I know that's a long time ago, but there were no astronauts. In fact, the very world's first satellite had just been launched a year before, but as I was going to elementary school, we started sending astronauts off into space. First, there was the Mercury program where one astronaut would go into space at a time in a Mercury capsule. Then Gemini. And that's what I remember are the Gemini missions where two people at a time would go and then the Apollo missions to the moon. And I thought that was all exciting.Dr. John Grunsfeld:So about age six or seven, I was already a young scientist. I was interested in fossils and dinosaurs and insects. But once we moved out of the city lights, I started seeing the night sky and that's when I decided I wanted to be an astronomer. And my grandmother at that time gave me a small telescope. And I started looking at the planets and the stars. That's when I decided I wanted to be an astronomer. And it came from looking up at the stars and wondering if there were other planets out there that had people. Well, whatever people would be, aliens.Eyezak:Aliens! Well, I would think that my presence would more than confirm that question.Captain Janet:Yes. Maggie?Maggie:I just wanted to say what I thought was kind of interesting is my grandma gave me a telescope too, a few years ago for Christmas. So, that was cool.Captain Janet:Really? How old were you?Maggie:I think over three years ago.Captain Janet:That is pretty cool.Lucas:What is it like working on Hubble?Dr. John Grunsfeld:Oh, I love working on the Hubble space telescope. As you know, the Hubble space telescope was designed to be serviced. And that means to be fixed by people in space suits with the big gloves. First of all, doing a spacewalk is just the coolest thing anyway. You get to put on a spacesuit, you get to go outside of the space shuttle or space station and float around in your own spaceship, the suit that wraps around you. You get to see the earth just through your thin visor. So, that's really fun. Plus I'm an astronomer. And so we love telescopes. So I got to be the one to fix the Hubble space telescope. And some of the things we did were really hard. And so we had to figure out new tools and new ways of fixing things in orbit.Dr. John Grunsfeld:Here on planet Earth, I get to use the Hubble space telescope to observe, and that's not as much fun as working on the Hubble up in space because you put in a proposal and NASA approves it, and then you get your observations. It's basically downloading the data from a server. So you don't really get to play with the Hubble at all, but then you get the cool science and you get to see pictures of your Europa. And Jupiter. And that's pretty cool.Eyezak:Look, look, do you have a favorite image from Hubble?Dr. John Grunsfeld:I have a bunch of favorite images from Hubble because I went up three times to fix the Hubble space telescope. And my favorite image each time is the first image that Hubble takes. In the case of my first mission in 1999, it was the Eskimo Nebula. In 2002, it was an image called the Tadpole.Dr. John Grunsfeld:The Eskimo Nebula is a star that's dying. And as it dies, it kind of has these temper tantrums and flows off its outer envelope. And then that glows. And so this particular image looks kind of like an Eskimo in his big parka. The Tadpole is a picture of two galaxies that have collided and they're circling around each other and have thrown out a long tail of material. And in that long tail of gas and dust, new stars are for me.Dr. John Grunsfeld:And on this most recent mission, it was a picture taken a little later, but my favorite image is an image that widefield camera three, the new super-duper digital camera on Hubble, took of the Orion Nebula, the great Nebula, and Orion. And the reason I like these images so much is that it proves that we fixed the telescope and didn't break it. If we got home and they turned the telescope on and it couldn't take images anymore, I'd feel terrible.Kevin:I heard if the James Webb telescope doesn't deploy everything as it should. There's something you can make it do. I think it was called the shimmy?Dr. John Grunsfeld:The James Webb space telescope isn't really assembled completely when we launch it. And that's because it has to be folded up so that it fits in the rocket faring inside the rocket. And once the rocket's launched, it's like a transformer or undoing an origami or both, that it has to slowly unfold and pieces have to come out before it can be a real telescope. There are I think, 40 different mechanisms and 600 pulleys and 150 motors, and 178 individual actuators.Maggie:That's amazing.Dr. John Grunsfeld:And it's incredibly complex for all these things to work. And so if something like the secondary mirror, there's the big mirror, and then there's a little mirror above it. If that doesn't unfold all the way, they can't send me out to give it a shake or to pull it. Astronauts can't go near the telescope. We don't have the capability, but also it's too delicate.Dr. John Grunsfeld:And so what you can do is kind of drive the motors or use the spacecraft to shake it while you're trying to drive the motor and see if you can redeploy it. And so, we'll try everything and anything to make sure everything deploys.Evy:How long will take to unfold?Dr. John Grunsfeld:It's going to unfold in pieces. The very first thing that will unfold, which is actually just a few hours after launch are the solar panels. So you can see on Hubble, there are those big solar panels. Well, we actually put those on ourselves and then unfolded them. So just after launch a few hours after it separates from the launch vehicle, the solar panels will unfold. That'll give it the power it needs to drive all those other motors. Then a few days later, they'll start to unfold the sunshade, and this will be about the size of a tennis court. And so over the course of about two weeks, most of the deployments will be done, but it'll take about a full month before everything is fully deployed because they want to go slow and carefully.Captain Janet:How soon will we be able to get an image from the J W S T?Dr. John Grunsfeld:I don't know exactly what it is, but it's going to be a few months. And that's because not only does James Webb have to deploy, but it has 18 mirrors and those mirrors are aligned to make one big mirror. So they have to go through individually and adjust each mirror so that it works as one mirror and not 18 individual mirrors. And so it's going to take a few days for each mirror while they turn it, adjust it and maybe bend it until the whole telescope works as one.Dr. John Grunsfeld:So probably there'll be some really bad images that'll come out in about three months. I'm not even sure if NASA will show those, but probably they will. And over the next couple of months, those images will sharpen up until they're as good as Hubble. And, and that'll be at about six months. So commissioning of the telescope, which means making sure everything works takes about six months.Eyezak:How does the sun shield work?Dr. John Grunsfeld:The sun shield works like an umbrella. If it's a really bright sunny day and you forgot a hat, because you thought it was going to rain, you can always open your umbrella and use it as a sun shield. And so it works just like that. The problem is with a spacecraft is, there is some space junk out there. And if the space junk goes through your umbrella, there'd be a hole in it. And the sun would go through that hole. So in order to prevent that the James Webb space telescope actually has five layers in its umbrella in its sun shield so that if one layer gets punctured, it won't let the light through all the way to the telescope. The other effect of having those five layers is for thermal reasons, not just blocking the sunlight, but on the sunny side of the James Webb Space Telescope, it's about 200 degrees, really hot.Dr. John Grunsfeld:And with each subsequent layer, it acts like a Thermos bottle. So that on the cold side, the part that faces where the James Webb space telescope will be looking, the temperature will be about minus 400 degrees Fahrenheit, just 40 degrees above absolute zero. And so the sun shield does two things. One, it just blocks the light. You can't see the stars in the daytime and that's because the earth is so bright, the Hubble is so bright, that the camera had to be set to an exposure. And the same is true of our eyeballs that you can't see stars. You need to be at night to see stars so that you can have that sensitivity. The same is true for James Webb. So it has to block the sunlight. That's the main purpose. And the secondary purpose is to allow the telescope to get super cold so that it can see the very faint light from the early universe.Dr. John Grunsfeld:The James Webb space telescope will do so much more than looking back at the very early universe. It will also study the formation of stars, the formation of galaxies, and the time history of galaxies all the way up to the present. It'll look at planets in our own solar system. I'm really excited because one of its first targets will be Europa, around Jupiter, to look to see if it can see those plumes. And then the other big thing that James Webb is going to do is just going to look at the atmospheres of planets around nearby stars so that we can see if there's another planet out there that kind of looks like Earth. So I'm pretty excited about that too.Eyezak:I'm a little embarrassed to ask, but why is it called the James Webb Space Telescope?Captain Janet:Oh, you don't have to be embarrassed. Eyezak. Dr. Grunsfeld, could you please tell our young crew a bit more about James Webb?Dr. Grunsfeld:James Webb was the first, well, one of the first directors, we call them administrators, of NASA. And so he was in charge of trying to get people to the moon and back. But another thing that he did that people don't know a lot about is that he made sure that science was part of NASA and that it was a big part of NASA. And that astronauts would go to the moon and do science. And so in recognition of his contributions to scientific investigations of space, the NASA administrator in 2004, named the telescope after James Webb. So that's why it's called the James Webb space telescope.Captain Janet:I am excited about this new beginning. In reality, when you look through a telescope as an astronomer, a telescope is almost like a cosmic time machine. It's allowing you to see the past in part because of the way that light travels. Can you speak to how, whenever you look up at the stars on a starlet night that we're seeing into the past?Dr. John Grunsfeld:So how many of you have seen a bolt of lightning? And then five seconds later, you hear the thunder, right? Pretty much all of us, right? Why does the thunder take so long to get to us when we see the light almost right away?Ander:It's because light goes faster than sound.Dr. John Grunsfeld:Right. The speed of sound through the air is really pretty slow. It travels about a thousand feet every second. Whereas the speed of light goes 186,000 miles per second. And so the light comes to us really quick, whereas the sound takes longer, but light still has a speed. And that means when we look at the sun, for instance, or you don't look at the sun. When sunlight reaches us, it took about eight minutes to travel from the sun to the earth because it's 93 million miles away. Well, the sun is really close compared to the nearest star. It takes four years for the light to get to us from the nearest star, off of Centauri.Dr. John Grunsfeld:It takes millions of years for light to get from a galaxy to us. And the light that James Webb is going to look at will have taken at the very most distant, will have taken about 13 and a half billion years to get to us. And so when we look at some fuzzy galaxy, that was one of the first galaxies that ever assembled in the universe, the light that left that galaxy will have traveled for 13 and a half billion years to get to us. And that means when we see that light, we're looking at that galaxy as it was when it was just a baby galaxy. And so that allows us to look back in time, really because we have no other choice, it just took that long for the light to get to us.Evy:How long will the James Web telescope work?Dr. John Grunsfeld:Good question. It was designed to last at least five years. And we think if we operate it really carefully, it will last for about 10 or 11 years. And that's just because that's how much fuel it has onboard.Captain Janet:I will point out that NASA is notorious for underestimating the longevity of its hardware, like spirit or opportunity, both outlasted, original projections by a long shot.Speaker 8:You said that, in five to 10 years that the James Webb telescope will run out of fuel. Is there any chance that NASA will send any refueling missions to keep the satellite operating for longer?Dr. John Grunsfeld:It's possible. Right now, there are no plans, but when was in charge of the James Webb space telescope project, I insisted that they put some little details on the telescope. There are like targets so that a robot spacecraft would know where to grab if we did send a refueling spacecraft out there, but right now there are no plans to do that. I hope in the next five years or so, that refueling technology and capability and space will advance to the point where that seems like a very reasonable thing to do.Maggie:Do you think it'll answer the cosmic question of, "Are we alone?"Eyezak:Huh? Yeah. I'm getting really tired of people thinking I live on some made-up street in New York City. No one believes I'm a real alien.Dr. John Grunsfeld:Okay. We're here on earth and we are building these telescopes and we now know that virtually every star you look at in the night sky has planets around it. When I was growing up, we didn't know that I suspected there might be, but we didn't have any scientific proof. Now we have proof that other solar systems are out there. It just seems so likely that if there's life on earth, life should have started somewhere else. If life is a one in a million chance on a planet, there are 200 billion stars in our own galaxy, which means there are at least that many planets. Then there should be lots and lots of life. But if life is a one in a trillion chance, we might be the only life in the whole galaxy. And we just don't know. So that's one of the things that the James Webb space telescope is going to try to look at planets around nearby stars to see if we see atmospheres that could be habitable.Dr. John Grunsfeld:So if there's another planet, even if it's close and they put as much pollution in their atmospheres as we put in ours, there's a tiny chance we might detect that, but probably not. That's going to take a telescope that's a little bit bigger than the James Webb. I think that that question will be answered when we send a probe to Europa or Enceladus, or maybe on Mars, you'll find a microbial fossil, or maybe even a live Martian microbe when you're on Mars. Or with a next-generation telescope beyond James Webb, something that instead of being 20 feet across is 30 or 35 feet across, a 16-meter telescope might be able to answer that question.Captain Janet:Wow. Thank you so much, Dr. Grunsfeld, for beaming up to the JP spaceship to speak with our crew.Speaker 3:Thank you.Speaker 4:Thank you, Mr. Grunsfeld.Eyezak:Thank you.Dr. John Grunsfeld:My pleasure.Captain Janet:We had a great time speaking with you. Would you consider coming back again?Dr. John Grunsfeld:Sure. My pleasure.Eyezak:Wow! Smart and brave and nice?Captain Janet:He truly is a gem. And speaking of gems, let's talk about the newest gem that NASA has launched, the James Webb telescope. December 25th, 2021 may become known as the day. The universe changed from a tropical rainforest to the edge of time itself. Congratulations to the many amazing humans at NASA, the European space agency, the Canadian space agency, and Arian space. Listen to the launch countdown from Kuru, Guyana, and an excited Dr. Thomas Zurbuchen, the associate administrator for NASA science mission directorate, talk about the joy of watching 20 plus years of work finally take flight.ESA Mission Control Manager:[foreign language 00:23:53].NASA:We have lift off.Dr. Thomas Zurbuchen:Whenever we look at launches, they're both an ending in the beginning. They're an ending of an engineering project on the ground and with many amazing hours and challenges that are there. But they're a beginning. JWST is the beginning of one of the most amazing missions that humanity has conceived. And I'm so excited to look forward to the next setup of this telescope and all the signs to come. Thanks to everybody. This is what we can do when we come together as one, humans. It's just absolutely incredible.Captain Janet:I love Dr. Zurbuchen's sentiment, that the engineering marble that is the James Webb telescope, is what can happen when we all come together for space exploration. 100 times more powerful than the 31-year-old Hubble telescope, Webb can see back in time, all the way to the let there be light moment. That instant when a cold dark universe ignited into stars and Webb, made perchance, put an end to some of our biggest cosmic questions. We just can't wait to see the James Webb space telescope unfold the universe for all of us.Captain Janet:So you see Eyezak, just like with the JWST, new beginnings can be scary, but they are also exciting.Eyezak:You're right. I'm excited to explore the universe with this awesome new crew.Captain Janet:Thank you, everyone. For listening to the JP AstroCast, let your mind revolve around this thought.Eyezak:The universe is always expanding.Captain Janet:Let your mind do the same.Captain Janet and EyezaK:And that's the view from the JP AstroCast.The JP ASTROCAST, a galaxy of fun.

In this episode I chat to Tina Kothari. Tina came to England as a small baby. She tells her story from getting a Philosophy Degree, to commerce and banking, to becoming a counsellor and trainer working with people with addiction and eating disorders in Europe and the USA, before working with executives at Blue Chip companies. She explains how her life experiences fired her passion for Human Rights. She has combined this passion with her love of film to launch Another Way Now, an organisation dedicated to shining a light on human rights abuses, changing conversations, and bringing action, to what is happening in the world. Tina shares her experience of the power of stories to motivate and educate. We speak about the difference between money and currency and why money is such a cause of angst in relationships. She explains the three principles that guide her spending on her (adult) children. She finishes off with her best money purchase for around £30 and her Money Pearls of Wisdom. Sit back, grab yourself an espresso (or drink of your choice!) and enjoy the conversation. Tina can be found at Another Way Now - https://www.anotherwaynow.org/team or on Instagram @anotherwaynow

In this episode of “The Journey of My Mother's Son” podcast, I sit down to talk with Dr. Toni Palermo. Toni was one of the youngest players to play in the AAGPBL.  After her playing days, she entered the convent and became Sister Toni. After Toni became a Nun, she went on to earn her Bachelor of Science Degree in English, History and Math from Alverno College.  She then earned three Master Degrees and a Doctor of Philosophy Degree from the University of Wisconsin-Madison.  She taught in the Physical Education Department and the School of Social Work at the University. We were connected by our mutual friend and fellow supporter of women in baseball, Sandy Kimbrell.  Sandy saw that we were in Wisconsin and reached out to me with Toni's contact information. We conducted the podcast on Toni's front porch and unfortunately, we had some cicadas in the background, so the sound quality is not the greatest, but nonetheless, Toni has a great story to tell.

Melissa is joined by Dr. Todd Cimino-Johnson, a fellow ODU Monarch to discuss his dissertation research into the LGBTQ Community College student experience in Appalachia.   Todd graduated from Old Dominion University in Spring 2021 with his Doctor of Philosophy Degree in Community College Leadership.   

Paul's third interview with Boyd C. Purcell, Ph.D., author of Spiritual Terrorism: Spiritual Abuse from the Womb to the Tomb and Christianity Without Insanity: For Optimal Mental/Emotional/Physical Health. Dr. Purcell is a National Board Certified Counselor, a Licensed Professional Counselor, an Ordained Honorably Retired Presbyterian Minister, and a Board Certified Chaplain. Educationally, he has a Bachelor of Science Degree in Comprehensive Social Studies (World/European/American History, Economics, Geography, Political Science, etc.). He also has a Master of Arts Degree in Counseling, a Master of Divinity Degree in Biblical Studies, and a Doctor of Philosophy Degree in the integration of psychology and theology. In terms of experience, Dr. Purcell has over 40 years of ministry in counseling: agency, clinical, pastoral, psychiatric hospital, school, substance abuse, private practice, and chaplaincy—providing spiritual care at the end of life for hospice patients.   Christianitywithoutinsanity.com  Dr.boydpurcell@gmail.com See omnystudio.com/listener for privacy information.

Paul's second of 3 interviews with Boyd C. Purcell, Ph.D., author of Spiritual Terrorism: Spiritual Abuse from the Womb to the Tomb and Christianity Without Insanity: For Optimal Mental/Emotional/Physical Health.  Dr. Purcell is a National Board Certified Counselor, a Licensed Professional Counselor, an Ordained Honorably Retired Presbyterian Minister, and a Board Certified Chaplain. Educationally, he has a Bachelor of Science Degree in Comprehensive Social Studies (World/European/American History, Economics, Geography, Political Science, etc.). He also has a Master of Arts Degree in Counseling, a Master of Divinity Degree in Biblical Studies, and a Doctor of Philosophy Degree in the integration of psychology and theology. In terms of experience, Dr. Purcell has over 40 years of ministry in counseling: agency, clinical, pastoral, psychiatric hospital, school, substance abuse, private practice, and chaplaincy—providing spiritual care at the end of life for hospice patients.   Christianitywithoutinsanity.com  Dr.boydpurcell@gmail.com See omnystudio.com/listener for privacy information.

Paul's first interview with Boyd C. Purcell, Ph.D., author of Spiritual Terrorism: Spiritual Abuse from the Womb to the Tomb and Christianity Without Insanity: For Optimal Mental/Emotional/Physical Health. Dr. Purcell is a National Board Certified Counselor, a Licensed Professional Counselor, an Ordained Honorably Retired Presbyterian Minister, and a Board Certified Chaplain. Educationally, he has a Bachelor of Science Degree in Comprehensive Social Studies (World/European/American History, Economics, Geography, Political Science, etc.). He also has a Master of Arts Degree in Counseling, a Master of Divinity Degree in Biblical Studies, and a Doctor of Philosophy Degree in the integration of psychology and theology. In terms of experience, Dr. Purcell has over 40 years of ministry in counseling: agency, clinical, pastoral, psychiatric hospital, school, substance abuse, private practice, and chaplaincy—providing spiritual care at the end of life for hospice patients.   Christianitywithoutinsanity.com  Dr.boydpurcell@gmail.com See omnystudio.com/listener for privacy information.

In this episode, we touch on the dialogue surrounding diversity and inclusion efforts in healthcare and infection prevention and control. Unfortunately unconscious bias operates constantly in the workplace. As infection preventionists, we see it in the ways patients of different races and ethnicities are acknowledged and treated. It is present as well in opportunities for promotion and career advancement. Our great panel of guests include Rosa Lozano, Dr. Tania Bubb, and Dr. Devin Jopp, APIC's CEO. Join us as we listen to our guests' experiences and their suggestions towards making infection prevention and control more inclusive. Hosted by: Silvia Quevedo About our Guests: Rosa Lozano, MPH, CIC. Assistant Vice President, Infection Prevention Rosa Lozano joined the Methodist Healthcare System located in San Antonio, Texas in 2019. As the Assistant Vice President of Infection Prevention Rosa mentors a team of facility Infection Preventionists, champions comprehensive infection prevention programs, and collaborates with teams to drive patient and healthcare worker safety. Before moving to San Antonio, Rosa has served as an infection preventionist in acute care, long-term acute care, and rehabilitation facilities in Texas, Colorado and Virginia. She specializes in outbreak/crises management and the prevention of healthcare-associated infections. Rosa is also passionate about mentorship and leadership growth for Infection Preventionists. Rosa received her Bachelor of Arts degree in Biology from The University of Texas, and her Master of Public Health degree in Healthcare Systems, Management, and Policy from the Colorado School of Public Health. She has been certified in infection prevention since 2009. Rosa is an active member of the Association for Professionals in Infection Control and Epidemiology (APIC), serving in several chapter leader roles, and nationally on the Public Policy Committee, and currently on the Communications Committee. Devin Jopp, MS, EdD. CEO, APIC Dr. Jopp joined APIC as CEO on December 7, 2020. He brings to APIC more than two decades of association leadership with a wide array of experience and accomplishments from across the healthcare and nonprofit sectors. He has been recognized as one of the top 100 most influential healthcare leaders by Healthcare Management International Magazine and one of the top 50 healthcare IT experts by Health Data Management Magazine. Prior to APIC, he served as CEO for the American College Health Association, the principal leadership organization for advancing the health and well-being of the nation's 20 million college students and their campus communities through advocacy, education, and research. He has also previously served as president and CEO for the Workgroup for Electronic Data Interchange (WEDI), a national nonprofit advisor to the Secretary of Health and Human Services focused on enhancing the exchange of healthcare information. Before joining WEDI, he served as chief operating officer for the Service Corp of Retired Executives, a national nonprofit organization that provides business mentoring and training to American entrepreneurs. Earlier in his career, Dr. Jopp held leadership positions at URAC, an independent, nonprofit healthcare accreditation organization, and at the Health Insurance Association of America. Dr. Jopp received a Bachelor of Arts in computer information systems from the College of Notre Dame of Maryland, a Master of Science in computer and information sciences from Hood College, and a Doctor of Education in human and organizational learning (EdD) from the George Washington University. Tania Bubb, PhD, RN, CIC, FAPIC. Director, Infection Control Dr. Bubb is currently the director of infection control at Memorial Sloan Kettering Cancer Center in New York City. Most recently she also served as Director for Infection Prevention and Control at Mount Sinai Hospital in New York City. Dr. Bubb has been an infection preventionist (IP) for more than 10 years at major academic medical centers of varying inpatient and outpatient specialties, providing her with the skills, critical thinking and leadership abilities necessary to perform optimally within the field of infection prevention and control, as well as promote and maintain patient safety initiatives. Dr. Bubb has served on the board of directors of her local APIC chapter as the membership chair as well as having chaired APIC's Professional Development Committee. She serves on the editorial review board of the American Journal of Infection Control and is a member of APIC's editorial panel. Dr. Bubb has spoken and presented at local chapter and national APIC events as well as other local and regional conferences. She has authored publications related to the field of infection prevention and control. Dr. Bubb received her Bachelor and Master of Science degrees in nursing from City University New York Herbert H. Lehman College. She was awarded her Doctor of Philosophy Degree in Nursing from New York University. Dr. Bubb is certified in infection prevention and control (CIC) and has earned the Fellow of APIC designation.  

The dudes welcome Chris to the show to discuss freedom of will, and how discernment of our vocations is about surrender and sacrifice! Put on your thinking beanies 'cause this is a good one. Now get off your phone and go spend Mother's Day with your mom, you lovable heathens! Instagram: @the_b.u.i.l.d._show Snapchat: @thebuildshow +Ad Jesum per Mariam+

This episode of In the Car with Shae is also available via my YouTube channel- Growing Forward with Shae!! On this episode you will hear from my dear friend Dr. Daryl Jackson. He will share with us the many barriers he overcame during his childhood. He is keenly aware of those people God placed in his life that helped him to overcome and succeed. You will be inspired by his story. This is an episode you don't want to miss! Dr. Daryl D. Jackson is a published author and his areas of research include African American studies, addiction, mental health, criminal justice, community-based treatment, trauma and trauma-informed care. Dr. Jackson previously served as the program coordinator for the Greater Cleveland Drug Court (Cleveland, Ohio) where he was on the planning implementation team for the organization and execution of several community engagement events for surrounding municipalities through Cleveland Municipal Court’s Federal Suburban Expansion Grant Project. Dr. Jackson is the president of Rhinehart, Rambert & Associates Counseling Firm LLC. He is also on numerous community relations boards throughout the United States and a member of Alpha Phi Alpha Fraternity Incorporated and the National Association for the Advancement of Colored People. Dr. Jackson is a 2007 graduate of Johnson C. Smith University in Charlotte, North Carolina where he earned a Bachelor of Social Work degree focusing in African American studies. He attended Case Western Reserve University and earned his Master of Social Work degree in 2010 and Doctor of Philosophy Degree in Counseling in 2015 at Cleveland State University. Dr. Jackson is currently seeking a graduate certificate in Diversity and Inclusion from Cornell University. Dr. Jackson is certified in Cognitive Behavioral / Motivational Enhancement Therapy. In September 2012 he received his licensure as a Chemical Dependency Counselor by the Ohio Chemical Dependency Professionals Board. Dr. Jackson is a native of Chester, South Carolina and currently resides in the Washington, D.C. metropolitan area. Dr. Jackson's Book is entitled, The Affects of African American Children being raised by their Grandparents can be purchased via Amazon.com or by contacting Dr. Jackson at Darylj2@yahoo.com. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/in-the-car-with-shae/message Support this podcast: https://anchor.fm/in-the-car-with-shae/support

Episode 12. What are the career options for lawyers when they want to move on from a big firms? Two options we explore in this episode include corporate in-house counsel and of course, the entrepreneurial route.Adam Armeland started his career working at a big law firm working long hours on major real estate transactions. Despite being absorbed by that world, after 3.5+ years he left and decided to explore an industry job. As the pace slowed down his mind kept racing towards even more alternatives, including the idea of starting his own business.The world of law is complex, as is the choice of where to work. Host Greg Martin and Adam talk about what it was like at each stage of his law career. Throughout this episode they also discuss the good and bad of the world of law, the path Adam took, what he gets out of being a business owner he couldn't from practicing law and we follow what drives him to do what he does today.

From early childhood Malaysia Harrell knew that she was destined to help others. Her focus, determination and positive outlook were vital to those around her. As the oldest of three girls, Malaysia helped to raise her siblings before she moved in with her grandmother. Her childhood was filled with trauma which stemmed from her mother's challenges with mental illness and addictions. Her nurturing spirit as a child helped to fuel her professional endeavors as an adult. It was no surprise that she would study to be a service provider within a helping profession. Malaysia went on to earn a Bachelor in Science degree in Psychology from the University of Massachusetts at Amherst. She knew that she wanted to further her expertise and so she later earned a Master of Social Work degree from the University of Maryland, in Baltimore, Maryland. She is a licensed Psychotherapist and is board certified by the American Board of Examiners in Clinical Social Work. Malaysia Harrell then went on to turn her passions as a provider to a healer by creating Blissful Life Consulting. At Blissful Life Consulting she specializes in helping women heal and shift into alignment to serve their life's purpose. She helps women to move past their traumas to gain clarity with the use of group work, retreats, online courses, coaching, and workshops. For almost 20 years, she has provided mental health services specializing in mental health, substance abuse, and family violence. Malaysia has successfully provided individual treatment, marital therapy, group therapy, employee wellness, leadership, and team building training to over 28,000 individuals, couples, and leaders worldwide. Her vast behavioral health and wellness knowledge with her noted relatable approach; she is a highly sought-after speaker for community organizations, educational institutions and faith-based organizations. Despite her childhood trauma she still held fond memories of the penny candy store from her hometown. She took those delightful candy fragrances and turned them into healing approaches. In 2019, Malaysia decided to share her holistic approaches with others in the form of aromatherapy. She founded Blissful Home Candy to spark joy in the lives of others while adding healing resources through fragrances. With the motto of “Love Your Inner Child”, the company currently offers soy wax candles, wax melts, room sprays and diffusers for your enjoyment towards healing. In April 2020, Blissful Home Candy launched Operation Blissful Acts in the midst of the COVID-19 Pandemic. The campaign is intended to provide joy in the lives of women of color who may be faced with adversity. Operation “Blissful Acts” has gifted women with Bliss Gift Boxes filled with candles, journals and many other wonderful goodies to aid in healing. Malaysia studied for a PhD student at Saybrook University where she is pursuing a Doctor of Philosophy Degree in Mind, Body, Medicine with a specialization in Integrated Mental Health. She is continuing to be dedicated to serving her community and providing mentorship to children, students and colleagues. In addition to her civilian services Malaysia is also a U.S. Veteran who is highly decorated in her service. When Malaysia is not serving her community or country, she enjoys spending quality time with her husband in Upper Marlboro, Maryland. She is also an aspiring author and diligently working on her writing manuscript for publishing. To connect with Blissful Home Candy you may visit: https://linktr.ee/blissfulhomecandy or follow her on social media as @blissfulhomecandy. To connect with Blissful Life Consulting, you may follow her on Instagram as @blissfullifeconsulting Today's Sponsor https://www.candlescience.com/

Spiritual Terrorism - Boyd C. Purcell is a National Board Certified Counselor, a Licensed Professional Counselor, an Ordained Christian Minister, and a Board Certified Chaplain. Educationally, he has a Bachelor of Science Degree in Comprehensive Social Studies (World/European/American History, Geography, Political Science, etc.) He also has a Master of Arts Degree in Counseling, a Master of Divinity Degree in Biblical Studies, and a Doctor of Philosophy Degree in the integration of psychology and theology. In terms of experience, Dr. Purcell has over 40 years of ministry in counseling: agency, clinical, pastoral, psychiatric hospital, school, substance abuse, private practice, and chaplaincy-providing spiritual care at the end of life for hospice patients. Spiritual Terrorism is thus a unique blend of the historical, psychological, and theological perspectives in regard to major world religions. This integrative approach provides the greatest probability of understanding the complex problem of the use and misuse of religion, being liberated from fear-based religion, and finding healing for damaged emotions due to spiritual abuse/terrorism. Dr. Purcell started using the terms "spiritual abuse" and "spiritual terrorism" early in the 1990's. He presented on these topics to counselors, social workers, hospice personnel, chaplains, and other clergy at various local, state, regional, national, and international conferences. Evaluations were always overwhelmingly positive. Many participants reported that they had never heard of these terms but recognized that they had been spiritually abused. Some clergy and mental-health professionals realized that they had failed to recognize it in former patients and had, consequently, not been able to help them very much and had lacked the knowledge to have made a helpful referral. - www.healingspiritualterrorism.com

Spiritual Terrorism - Boyd C. Purcell is a National Board Certified Counselor, a Licensed Professional Counselor, an Ordained Christian Minister, and a Board Certified Chaplain. Educationally, he has a Bachelor of Science Degree in Comprehensive Social Studies (World/European/American History, Geography, Political Science, etc.) He also has a Master of Arts Degree in Counseling, a Master of Divinity Degree in Biblical Studies, and a Doctor of Philosophy Degree in the integration of psychology and theology. In terms of experience, Dr. Purcell has over 40 years of ministry in counseling: agency, clinical, pastoral, psychiatric hospital, school, substance abuse, private practice, and chaplaincy-providing spiritual care at the end of life for hospice patients. Spiritual Terrorism is thus a unique blend of the historical, psychological, and theological perspectives in regard to major world religions. This integrative approach provides the greatest probability of understanding the complex problem of the use and misuse of religion, being liberated from fear-based religion, and finding healing for damaged emotions due to spiritual abuse/terrorism. Dr. Purcell started using the terms "spiritual abuse" and "spiritual terrorism" early in the 1990's. He presented on these topics to counselors, social workers, hospice personnel, chaplains, and other clergy at various local, state, regional, national, and international conferences. Evaluations were always overwhelmingly positive. Many participants reported that they had never heard of these terms but recognized that they had been spiritually abused. Some clergy and mental-health professionals realized that they had failed to recognize it in former patients and had, consequently, not been able to help them very much and had lacked the knowledge to have made a helpful referral. - www.healingspiritualterrorism.com

About Geneva A. Stark, Ph.D., CDP Dr. Geneva A. Stark, servant leader, visionary, educator, achiever, collaborator, and a problem-solver. She is a native of New Orleans, La. that resides in Metro Louisville. She received her BS Degree from Xavier University of New Orleans, Master’s in Education from the University of New Orleans, Rank 1 from Western Kentucky University in Administration (Principal, Instructional Leader and Director of Pupil Personnel).  She received her Doctor of Philosophy Degree as Superintendent and Instructional Leader, from Educational, Leadership, Evaluation, Organization and Development department from the University of Louisville.  Dr. Stark recently obtained a National Professional Certification in Diversity and Inclusion.   Show Highlights Doing diversity is a lifelong experience for many people Racial Equity Policy Checking a box Creating a Racial Equity Policy Accountability Connect with Geneva www.gaspconsultant.com Email: gasp0524@gmail.com Connect with me on Twitter @sheldoneakins

On today's episode, Emily Crookston, founder of The Pocket PhD, shared with me how she turned her background as a philosophy professor into content marketing and, ultimately, ghostwriting. Turns out that philosophy helps turn writers into supermutants, because tapping into the "why" of writing a book, and the "why" of the audience you're trying to reach is one of the hardest things. Find out more about Emily's journey in this episode. Reach out to Emily at https://www.linkedin.com/in/emilycrookston/ or https://www.thepocketphd.com/... ...and enjoy the listen --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app Support this podcast: https://anchor.fm/archdevops/support

Episode Main Points:1) There is a game that you need to understand when entering into the engineering profession. Its still the white man's game.2) Black women need not compete with each other. We have to learn how to support each other, especially in these spaces where we are few and far between.3) It is still necessary for our children to see us in these professional settings doing the job. We are still the minority and therefore it is incumbent on us show our kids examples.Dr. Valerie Bennett Bio:Dr. Valerie Bennett is a native of Atlanta, Georgia. She received a Bachelor of Engineering Degree in Mechanical Engineering, from Vanderbilt University and received her Master of Science and Doctor of Philosophy Degree in Mechanical Engineering, both from the Georgia Institute of Technology. Dr. Bennett then worked as a software consultant for Manhattan Associates then joined Morehouse College as an Assistant Professor where she taught Engineering and Physics courses as part of the Dual Degree Engineering Program for four and a half years. She then joined the faculty at the Westminster Schools in Atlanta where she taught Physics and was one of the two founding Coaches of the Robotics Program. As the Head Coach of the award-winning High School Robotics Team, the team has won several Regional Competitions and has been recognized on the International Level. She has also served on the Georgia FIRST Robotics Regional Committee in the planning of Regional Events and was Co-Coordinator of the Georgia FIRST Robotics Mentor Advisory Council. To expose student to the excitement and importance of STEM, she worked as the Physics Research Coordinator for the TRIO Program as part of the Upward Bound Initiative. She was also awarded the Innovative Teacher award by the Georgia Independent Schools Association and received an Innovation Grant by the Georgia Education and Technology Conference. After teaching at Westminster, she then was an Engineering Professor and Regents’ Engineering Transfer Program Advisor at Georgia Perimeter College. Afterwards, she taught Advanced Placement Physics, IB Physics and led the Physics Professional Learning Community at Westlake High School where she served on the Fulton County Vanguard Team while also completing research with students at Georgia Tech as part of GIFT Program.Dr. Bennett has been a Research Coordinator for the Peach State Louis Stokes Alliance for Minority Participation Program and has been awarded the Innovative Teaching Award by the Georgia Independent Schools Association. She has served as the Morehouse Coordinator for the Dual Degree Engineering Program and Faculty Advisor for several student Organizations such as National Society of Black Engineers, Society of Physics Students, Society of Women Engineers (Spelman College), and Packard Scholars. She has served as a Board Member and STEM Advisory Board Member of the Atlanta Cares Mentoring Organization, which was established by Susan Taylor, former editor of Essence Magazine. In the Greater Metropolitan Atlanta Chapter of Jack and Jill of America, she has organized several community projects. In 2014, she established STEM Compass, Inc., a non-profit organization whose mission is to navigate, educate, and motivate young people in STEM-focused careers and entrepreneurship. The three pillars of the organization are skill-building, mind-building and visioneering through which they have served nearly 1000 students each year. STEM Compass has garnered partnerships with individuals, companies and organizations such as Google, Clorox, City of Atlanta, ATLRead, PPG, LMS Engineering, Georgia Tech, Atlanta Science Festival and FIRST Robotics.website: http://stemcompassinc.org/Support the show (https://cash.app/$drtoshia)

It's not often we meet someone with a Philosophy Degree who ventures into accounting and estate planning but not everyone is Fabio Campanella! On this episode of The Your Life! Your Terms! Show, we chat about the state of the equity markets, the economy, estate planning and get into Fabio's unique back story. You can reach out to Fabio at www.cmllp.com .

This fortnight, we catch up on The Good Place's final season (14:51) which aired while we were on hiatus, and then descend into the more recent Netflix movie The Platform (35:58), with spoilers for both, including ending details for latter from about 46:18. Fuller shownotes at ModerateFantasyViolence.com

Since December 2017, Dr. Stephany C. Coakley has served as the Senior Associate Athletic Director for Mental Health at Temple University. In this role, she is responsible for ensuring that student-athletes, from 19 teams, have access to mental wellness services that they need.   An experienced and certified mental performance consultant (CMPC), she is also the founder/director of Maximum Mental Training Associates (MMTA) LLC, a performance psychology consulting business. She is dedicated to helping athletes, youth to professional, master the fundamentals of mental preparation for training and competition.   Dr. Coakley has worked with the Superbowl Champion Philadelphia Eagles (2015 – 2017) as the clinician and Rookie Success Program facilitator; as Group Doctor, for the NBA Pre-Draft Combine. For 10 years, she worked as a Master Resilience Trainer – Performance Expert with the United States Army.   Dr. Coakley earned both her Bachelor's Degree in Psychology and Master's Degree in Counseling Psychology from Temple University. She received her Doctor of Philosophy Degree in Sport and Exercise Science with a concentration in Sport Psychology from the University of North Carolina in Greensboro, North Carolina.   In this podcast, Stephany and Cindra talk about: The power of our thoughts What to do when you have a disempowering thought What NFL rookies most struggle with How to help NFL rookies overcome pressure Her work with mental training in the Army Her Manifesto of Greatness activity You can find a full description of the Podcast at cindrakamphoff.com/steph. You can reach Dr. Coakley at www.maximumentaltraining.com.

Episode 7: In this special edition of the GLD podcast Boniface Dulani (Chancellor College, University of Malawi) discusses traditional leadership and authority in Malawi and the impact these structures have on the country's political system at both the local and national level. The podcast was recorded live in Malawi during a field visit as part of our ongoing SSA project. Boniface holds a Doctor of Philosophy Degree in Political Science from Michigan State University in the United States (2011). Dr. Dulani brings to IPOR a rich experience in conducting survey research in Africa through his involvement as a senior member of the Afrobarometer- a pan- Africanist research network that undertakes a series of public opinion surveys on governance, democracy, markets, livelihoods and other related topics in over 35 African countries. His areas of research interest include governance and democracy, presidential politics, politics of development, rural development, civil society and other related topics. Dr. Dulani is a Senior Lecturer in Political Science of at Chancellor College of the University of Malawi and also serves as the Fieldwork Operations Manager for Southern and Francophone Africa in the Afrobarometer. Selected Work: Muriaas, R. L., Wang, V., Benstead, L., Dulani, B., & Rakner, L. (2019). Why the gender of traditional authorities matters: Intersectionality and women’s rights advocacy in Malawi. Comparative Political Studies, 52(12), 1881-1924. Available at: https://journals.sagepub.com/doi/full/10.1177/0010414018774369

Rich Harris talks about Svelte and Reactivity. Rich Harris: Graphics Editor on The New York Times investigations team. Resources: Svelte Please join us in these conversations! If you or someone you know would be a perfect guest, please get in touch with us at contact@frontside.io. Our goal is to get people thinking on the platform level which includes tooling, internalization, state management, routing, upgrade, and the data layer. This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC. Transcript: CHARLES: Hello and welcome to The Frontside Podcast, a place where we talk about user interfaces and everything that you need to know to build them right. TARAS: It's actually a really nice, Rich and I'm really, really happy to have a chance to actually chat with you about this because Svelte is a really fun piece technology. In many ways, it's interesting to see our technology evolve and our industry evolve through innovation, real innovation. I think Svelte 3 has really been kind of that next thought provoking technology that kind of makes you think about different ways that we can approach problems in our space. So, really excited to chat with you about this stuff. RICH: Well, thank you. Excited to be here. TARAS: I think quite a lot of people know, Rich, about your history, like how you got into what you're doing now. But I'm not sure if Charles is aware, so if you could kind of give us a little bit of a lowdown on where you kind of come from in terms of your technical background and such. RICH: Sure. I'll give you the 30-second life history. I started out as a reporter at a financial news organization. I had a Philosophy Degree and didn't know what else to do with it. So, I went into journalism. This was around the time of the great recession. And within a few weeks of me joining this company, I watched half of my colleagues get laid off and it's like, "Shit, I need to make myself more employable." And so gradually, sort of took on more and more technical responsibilities until I was writing JavaScript as part of my day job. Then from there, all these opportunities kind of opened up. And the big thing that I had in mind was building interactive pieces of journalism, data-driven, personalized, all of that sort of thing, which were being built at places like the New York Times, and The Guardian, and the BBC. That was the reason that I really wanted to get into JavaScript. And that's guided my career path ever since. CHARLES: It's interesting that this D3 and all that did come out of journalism. RICH: It's not a coincidence because when you're working under extreme time pressure and you're not building things with a view to maintain them over a long period of time, you just need to build something and get it shipped immediately. But it needs to be built in a way that is going to work across a whole range of devices. We've got native apps, we've got [inaudible], we've got our own website. And in order to do all that, you need to have tools that really guide you into the pit of success. And D3 is a perfect example of that. And a lot of people have come into JavaScript through D3. CHARLES: And so, are you still working for the same company? RICH: No. That's ancient history at this point. CHARLES: Because I'm wondering, are you actually getting to use these tools that you've been building to actually do the types of visualizations and stuff that we've been talking about? RICH: Very much so. I moved to The Guardian some years ago. And then from there, moved to Guardian US, which has an office in New York. And it was there that I started working on Svelte. I then moved to the New York Times and I'm still working on Svelte. I've used it a number of times to build things at the New York Times and the people have built things with it too. And so, yeah, it's very much informed by the demands of building high performance interactive applications on a very tight deadline. CHARLES: Okay, cool. So I've probably used, I mean, I'm an avid reader of both Guardian and the New York Times, so I've probably used a bunch of these visualizations. I had no idea what was driving them. I just assumed it was all D3. RICH: There is a lot of D3. Mike Bostock, the creator of D3, he was a linchpin at the graphics department for many years. Unfortunately we didn't overlap. He left the Times before I joined the Times, but his presence is still very much felt in the department. And a lot of people who are entering the industry, they're still becoming database practitioners by learning from D3 examples. It's been a hugely influential thing in our industry. TARAS: How long is a typical project? How long would it take to put together a visualization for an article that we typically see? RICH: It varies wildly. The graphics desk is about 50 strong and they will turn around things within a day. Like when the Notre Dame burnt down a couple of months ago, my colleagues turned around this interactive scroll driven webGL 3D reconstruction of how the fire spreads through the cathedral in less than 24 hours, which was absolutely mind blowing. But at the same time, there are projects that will take months. I work on the investigations team at the Times. And so, I'm working with people who are investigating stories for the best part of the year or sometimes more. And I'm building graphics for those. And so that, it's two very different timescales, but you need to be able to accommodate all of those different possibilities. CHARLES: So, what does the software development practice look like? I mean, because it sounds like some of this stuff, are you just throwing it together? I guess what I mean by that is, I guess the projects that we typically work on, three months is kind of a minimum that you would expect. So, you go into it, we need to make sure we've got good collaboration practices around source control and continuous integration and testing and all this stuff. But I mean, you're talking about compressing that entire process into a matter of hours. So what, do you just throw right out the window? What do you say? "We're just doing a live version of this." RICH: Our collaboration processes consist of sitting near each other. And when the time calls for it, getting in the same room as each other and just hammering stuff out on the laptop together. There's no time for messing around with continuous integration and writing tests. No one writes tests in the news graphics, it's just not a thing. CHARLES: Right. But then for those projects that stretch into like three months, I imagine there are some. Do you run into like quality concerns or things like that where you do have to take into account some of those practices? I'm just so curious because it sounds like there's actually, the difference between two hours and two months is, that's several orders of magnitude and complexity of what you're developing. RICH: It is. Although I haven't worked on a news project yet that has involved tests. And I know that's a shocking admission to a lot of people who have a development background, but it's just not part of the culture. And I guess the main difference between the codebase for a two-hour project and a two-month project is that the two-month project will strive to have some reasonable components. And that's, I think, the main thing that I've been able to get out of working on the kinds of projects that I do is instead of just throwing code at the page until it works, we actually have a bit of time to extract out common functionality and make components that can be used in subsequent interactives. So, things like scroll driven storytelling, that's much easier for me now than it was when I first built a scroll driven storytelling component like a couple of years ago. CHARLES: Yeah. That was actually literally my next question is how do you bridge that, given that you've got kind of this frothy experimentation, but you are being, sounds like, very deliberate about extracting those tools and extracting those common components? And how do you find the time to even do that? RICH: Well, this is where the component driven mindset comes in really handy, I think. I think that five or 10 years ago when people thought in terms of libraries and scripts, there wasn't like that good unit of reusability that wasn't the sort of all encompassing, like a component is just the right level of atomicity or whatever the word is. It makes sense to have things that are reusable but also very easy to tweak and manipulate and adapt to your current situation. And so, I think that the advent of component oriented development is actually quite big for those of us working in this space. And it hasn't really caught on yet to a huge degree because like I say, a lot of people are still coming with this kind of D3 script based mindset because the news industry, for some interesting and historical reasons, is slightly out of step with mainstream mode development in some ways. We don't use things like Babel a lot, for example. CHARLES: That makes sense, right? I mean, the online print is not like it's a React application or it's not like the application is all encompassing, so you really need to have a light footprint, I would imagine, because it really is a script. What you're doing is scripting in the truest sense of the word where you essentially have a whole bunch of content and then you just need to kind of -- RICH: Yeah. And the light footprint that you mentioned is key because like most new sites, we have analytics on the page and we have ads and we have comments and all of these things that involve JavaScript. And by the time our code loads, all of this other stuff is already fighting for the main thread. And so, we need to get in there as fast as we can and do our work with a minimum fuss. We don't have the capacity to be loading big frameworks and messing about on the page. So that again is one of these sort of downward pressures that kind of enforces a certain type of tool to come out of the news business. TARAS: A lot of the tooling that's available, especially on like the really fatter, bigger frameworks, the tools that you get with those frameworks, they benefit over long term. So if you have like a long running project, the weight of the abstractions, you've experienced that benefit over time and it adds up significantly. But if you're working to ship something in a day, you want something that is just like a chisel. It does exactly what you want it to do. You want to apply it in exactly the right place and you want to get it done exactly, like you want the outcome to be precise. RICH: That's true. And I think a lot of people who have built large React apps, for example, or large Ember apps, they sort of look at Svelte and think, "Well, maybe this isn't going to be applicable to my situation," because it has this bias towards being able to very quickly produce something. And I'm not convinced that that's true. I think that if you make something easier to get started with, then you're just making it easier. If you build something that is simple for beginners to use, then you're also building something simple for experts to use. And so, I don't necessarily see it as a tradeoff, I don't think we're trading long-term maintainability for short term production. But it is certainly a suspicion that I've encountered from people. TARAS: This is something that we've also encountered recently. It's been kind of a brewing discussion inside a front side about the fact that it seems to be that certain problems are actually better to rewrite than they are to maintain or refactor towards an end goal. And we found this, especially as the tools that we create have gotten more precise and more refined and simplified and lighter, it is actually easier to rewrite those things five times than it is to refactor it one time to a particular place that we want it to be. And it's interesting, like I find this to be very recent, this idea is blossoming in my mind very recently. I didn't observe this in the past. CHARLES: Do you mean in the sense that like if a tool is focused enough and a tool is simple enough, then refactoring is tantamount to a rewrite if you're talking about 200 or 300 lines of code? Is that what you mean? TARAS: Yeah. If you're sitting down to make a change or you have something in mind, it is actually easy to say, "Let's just start from scratch and then we're going to get exactly the same place in the same amount of time." But this kind of mantra of not rewriting makes me think about that, makes me question whether that's actually something that is always the right answer. RICH: I definitely question that conventional wisdom at all levels, as well. I started a bundler called Rollup as well as Svelte more recently. And Rollup was the second JavaScript bundler that I wrote, because the first one that I wrote wasn't quite capable of doing the things that I wanted. And it was easier to just start from scratch than to try and shift the existing user base of its predecessor over to this new way of doing things. Svelte 3 is a more or less complete rewrite. Svelte has had multiple, more or less, complete rewrite. Some of them weren't breaking changes. But Svelte itself was a rewrite of an earlier project that I'd started in 2013. And so in my career, I've benefited massively from learning from having built something. But then when the time comes and you realize that you can't change it in the ways that you need to change it, just rewrite it. And I think that at the other end of the spectrum, the recent debate about micro frontend has largely missed this point. People think that the benefit of the micro frontend is that people don't need to talk to each other, which is absolute nonsense. I think the benefit of this way of thinking about building applications is that it optimizes for this fact of life that we all agree is inevitable, which is that at some point, you're going to have to rewrite your code. And we spend so much energy trying to optimize for the stability of a code base over the long term. And in the process, lock ourselves into architectural and technical decisions that don't necessarily make sense three or four years down the line. And I think as an industry, would be a lot better placed if we all started thinking about how to optimize for rewrites. CHARLES: So for those of us who aren't familiar, what is the debate surrounding micro frontends? This is actually something I've heard a lot about, but I've actually never heard what micro frontends actually are. RICH: Yeah. I mean, to be clear, I don't really have a dog in this fight because I'm not building products, but the nub of it is that typically if you're building a website that maybe has like an admin page, maybe it has a a settings page, maybe it has product pages, whatever. Traditionally, these would all be parts of a single monolithic application. The micro frontend approach is to say, "Well, this team is going to own the settings page. This team is going to own the product page." And they can use whatever technologies they want to bring that about. And the detractors sort of attack a straw man version of this, "You're going to have different styles in every page. You're going to have to load Vue on one page. You're going to have to load React on the other page. It's going to be a terrible user experience," when actually its proponents aren't suggesting that at all. They're suggesting that people from these different teams coordinate a lot more that are free to deviate from some kind of grand master architectural plan when it's not suitable for a given task. And darn right. I think it means that you have a lot more agility as an engineering organization than you would if you're building this monolithic app where someone can't say, "Oh, we should use this new tool for this thing. We should use microstates when the rest of the organization is using Google docs." It's not possible. And so, you get locked into the decisions of a previous generation. CHARLES: Right. No, it makes sense. It's funny because my first reaction is like, "Oh my goodness, that's a potential for disaster." The klaxon's going to go off in your head, but then you think, really then the work is how do you actually manage it so it doesn't become a disaster. And if you can figure that out, then yeah, there is a lot of potential. RICH: Yeah. People always try and solve social problems with technology. You solve social problems with social solutions. CHARLES: Right. And you have to imagine it too, it depends on the application, right? I think Amazon, the Amazon website is developed that way where they have different teams that are responsible even down to little content boxes that are up on the toolbar. And the site doesn't really, it shows, right? Like it shows like this is kind of like slapped together, but that's not what they need. They don't need it to not look like there's slight variation with the different ways that things behave. They need to be showing for their business to work. They need to be showing the right thing at the right time. And that's the overriding concern. So having it look very beautiful and very coherent isn't necessarily a thing. Same thing in Spotify, used as another example of this. I didn't know if it was called micro frontends, but I know that they've got a similar type thing, but they are clearly the experience and having it look coherent is more important. And so, they make it work somehow. And then like you're saying, it probably involves groups of people talking to other groups of people about the priorities. So yeah, it doesn't sound to me like just like you're going to adopt micro frontends guarantees one particular set of outcomes. It really is context dependent on what you make of it. RICH: Totally. TARAS: I'm curious though, so with Svelte, essentially for your reactivity engine, you have to compile to get that reactive behavior. RICH: Yeah. TARAS: How does that play with other tools like when you actually integrate it together? I've never worked with Svelte on a large project, so I can't imagine what it looks like at scale. I was wondering if you've seen those kind of use cases and what that ends up, if there's any kind of side effects from that. RICH: As you say, the reactivity within a component is only in the local state within that component or to state that is patched in as a prop from a parent component. But we also have this concept called a store. And a store is just a project that represents a specific value and you import it from svelte/store. And there are three types of store that you get out of the box. A writable, a readable and a derived. And a writeable is just, var count = writable (0) and then you can update that and you can set it using methods on that store. Inside your marker, you can reference or in fact inside the script block in the component, you can reference the value of that store just by prefacing it with a dollar sign. And the compiler sees that and says, "Okay, we need to subscribe to this store as value and then assign it and apply the reactivity." And that is the primary way of having state that exists outside the component hierarchy. Now, I mentioned the writable, readable, and derived are the built in stores that you get, but you can actually implement your own stores. You just need to implement this very simple contract. And so,, it's entirely possible to use that API to wrap any state management solution you have. So you can wrap redux, you can wrap microstates, you can wrap state, you can wrap whatever it is, whatever your preferred state management solution is, you can adapt it to use with Svelte. And it's very sort of idiomatic and streamlined. Like it takes care of unsubscriptions when the component is unmounted. All of that stuff is just done for you. CHARLES: Digging a little bit deeper into the question of integration, how difficult would it be to take wholesale components that were implemented in Svelte and kind of integrate them with some other component framework like React? RICH: If the component is a leaf node, then it's fairly straightforward. There is a project called react-svelte which is, I say project, it's like 20 lines of code and I don't think it's [inaudible] they did for Svelte 3, which I should probably do. But that allows you to use a Svelte component in the context of React application, just using the component API the same way that you would [inaudible] or whatever. You can do that inside a React component. Or you could compile the Svelte component to a web component. And this is one of the great benefits of being a compiler is that you can target different things. You can generate a regular JavaScript class and you've got an interactive application. Or you can target a server side rendering component which will just generate some html for some given state which can then later be hydrated on the client. Or you can target a web component which you can use like any other element in the context of any framework at all. And because it's a compiler, because it's discarding all of the bits of the framework that you're not using, it's not like you're bundling an entire framework to go along with your component. And I should mention while I'm talking about being able to target different outputs, we can also, as a NativeScript project, you can target iOS and Android that same way. Where it gets a little bit more complicated is if it's not a leaf node. If you want to have a React app that contains a Svelte component that has React [inaudible], then things start to get a little bit more unwieldy, I think. It's probably technically possible, but I don't know that I would recommend it. But the point is that it is definitely possible to incrementally adopt Svelte inside an existing application, should that be what you need to do. CHARLES: You said there's a NativeScript project, but it sounds to me like you shouldn't necessarily need NativeScript, right? If you're a compiler, you can actually target Android and you could target iOS directly instead of having NativeScript as an intermediary, right? RICH: Yes. If, if we had the time to do the work, then yes. I think the big thing there would be getting styles to work because Svelte components have styles. And a regular style tag just to CSS and you can't just throw CSS in a native app. CHARLES: Right. Sometimes, I feel like it'd be a lot cooler if you could. [Laughter] RICH: NativeScript really is doing a lot of heavy lifting. Basically what it's doing is it's providing a fake dom. And so, what the NativeScript does is it targets that dom instead of the real dom and then NativeScript turns that into the native instructions. CHARLES: Okay. And you can do that because you're a compiler. TARAS: Compilers has been on our radar for some time, but I'm curious like what is your process for figuring out what it should compile to? Like how do you arrive at the final compile output? Manually, have you written that code and then, "I'm going to now change this to be dynamically generated." Or like how do you figure out what the output should be? RICH: That's pretty much it. Certainly, when the project started, it was a case of, I'm going to think like a compiler, I'm going to hand convert this declarative component code into some framework plus JavaScript. And then once that's done, sort of work backwards and figure out how a compiler would generate that code. And then the process, you do learn certain things about what the points of reusability are, which things should be abstracted out into a shared internal helper library and what things should be generated in line. The whole process is designed to produce output that is easy for a human to understand and reason about. It's not like what you would imagine compile [inaudible] to be like, it's not completely inscrutable. It's designed to be, even to that level of being well formatted, it's designed to be something that someone can look at and understand what the compiler was thinking at that moment. And there's definitely ways that we could change and improve it. There are some places where there's more duplication than we need to have. There are some places where we should be using classes instead of closures for performance and memory benefits. But these are all things that once you've got that base, having gone through that process, that you can begin to iterate on. CHARLES: It's always curious to me about when is the proper time to move to a compiler, because when you're doing everything at runtime, there's more flexibility there. But at what point do you decide, "You know what? I know that these pathways are so well worn that I'm going to lay down pavement. And I'm going to write a compiler." What was the decision process in your mind about, "Okay, now it's time." Because I think that that's maybe not a thought that occurs to most of us. It's like, "I had to write a compiler for this." Is this something that people should do more often? RICH: The [inaudible] of 'this should be a compiler' is one that is worth sort of having at the back of your head. I think there are a lot of opportunities not just in DUI framework space but in general, like is there some way that we can take this work that is currently happening at runtime and shift it into a step that only happens once. That obviously benefits users. And very often we find that benefits developers as well. I don't think there was a point at which I said, "Oh, this stuff that's happening at runtime should be happening at compile time." It was more, I mean, the actual origin has felt that it was a brain worm that someone else infected me with. Judgment is a very well known figure in the JavaScript world. He had been working on this exact idea but hadn't taken it to the point where he was ready to open source it. But he had shared like his findings and the general idea and I was just immediately smitten with this concept of getting rid of the framework runtime. At the time, the big conversation happening in the JavaScript community was about the fact that we're shipping too much JavaScript and it's affecting startup performance time. And so the initial thought was, "Well, maybe we can solve that problem by just not having the runtime." And so, that was the starting point with Svelte. Over time, I've come to realize that that is maybe not the main benefit. That is just one of the benefits that you get from this approach. You also get much faster update performance because you don't have to do this fairly expensive virtual dom different process. Lately, I've come to think that the biggest win from it is that you can write a lot less code. If you're a compiler, then you're not kind of hemmed in by the constraints of the language, so you can almost invent your own language. And if you can do that, then you can do the same things that you have been doing with an API in the language itself. And that's the basis of our system of reactivity, for example. We can build these apps that are smaller and by extension, less bug prone and more maintainable. I just wanted to quickly address the point you made about flexibility. This is a theoretical downside of being a compiler. We're throwing away the constraints about the code needing to be something that runs in the browser, but we're adding a constraint, which is that the code needs to be statically analyzable. And in theory, that results in a loss of flexibility. In practice, we haven't found that to affect the things that we can build. And I think that a lot of times when people have this conversation, they're focusing on the sort of academic concepts of flexibility. But what matters is what can you build? How easy is it to build a certain thing? And so if empirically you find that you're not restricted in the things that you can build and you can build the same things much faster, then that academic notion of flexibility doesn't, to my mind, have any real value. CHARLES: Hearing you talk reminded me of kind of a quote that I heard that always stuck with me back from early in my career. I came into programming through Perl. Perl was my first language and Perl is a very weird language. But among other things, you can actually just change the way that Perl parses code. You can write Perl that makes Perl not throw, if that makes any sense. And when asked about this feature, the guy, Larry Wall, who came up with Perl, he's like, "You program Perl, but really what you're doing is you're programming Perl with a set of semantics that you've negotiated with the compiler." And that was kind of a funny way of saying like, "You get to extend the compiler yourself." Here's like the default set of things that you can do with our compiler, but if you want to tweak it or add or modify, you can do that. And so, you can utilize the same functionality that makes it powerful in the first place. You can kind of inject that whole mode of operation into the entire workflow. Does that make sense? That's like a long way of saying, have you thought about, and is it possible to kind of extend the Svelte compiler as part of a customization or as part of the Svelte programming experience? RICH: We have a very rudimentary version of that, which is pre-processing. There's an API that comes with Svelte called preprocess. And the idea there is that you can pass in some code and it will do some very basic, like it will extract your styles, it will extract your script and it will extract your markup. And then it will give you the opportunity to replace those things with something else. So for example, you could write some futuristic JavaScript and then compile it with Babel before it gets passed to the Svelte compiler, which uses acorn and therefore needs to be able to have managed other scripts so that it can construct an abstract syntax tree. A more extreme version of that, people can use [inaudible] to write their markup instead of html. You can use Sass and Less and things like that. Generally, I don't recommend that people do because it adds these moving parts and it makes like a lot of bug reports of people just trying to figure out how to get these different moving parts to operate together. I don't know, it means that your editor plugins can't understand what's inside your style tag all of a sudden and stuff like that. So, it definitely adds some complexity, but it is possible. At the other end, at a slightly more extreme level, we have talked about making the cogeneration part plugable so that for example, the default renderer and the SSR renderer are just two examples of something that plugs into the compiler that says, "Here is the component, here's the abstract syntax tree, here's some metadata about which values are in scope," all of this stuff and then go away and generate some code from this. We haven't done that so far, partly because there hasn't been a great demand for it, but also because it's really complicated. As soon as you turn something into a plugin platform, you just magnify the number of connection points and the number of ways that things could go wrong by an order of magnitude. And so, we've been a little bit wary of doing that, but it is something that we've talked about primarily in the context of being able to do new and interesting things like target webGL directly or target the command line. There are renders for React that let you build command line apps using React components. And like we've talked about, maybe we should be able to do that. Native is another example. The NativeScript integration as you say, it could be replaced with the compiler doing that work directly, but for that to work presently, that would mean that all of that logic would need to sit in core. And it would be nice if that could be just another extension to the compiler. We're talking about a lot of engineering effort and there's higher priority items on our to do list at the moment. So, it's filed under one day. CHARLES: Right. What are those high priority items? RICH: The biggest thing I think at the moment is TypeScript integration. Surprisingly, this is probably like the number one feature request I think is that people want to be able to write Typescript inside the Svelte components and they want to be able to get TypeScript when they import the Svelte component into something else. They want to be able to get completion [inaudible] and type checking and all the rest of it. A couple of years ago, that would've been more or less than thinkable but now it's like table stakes is that you have to have first-class TypeScript support. CHARLES: Yeah, TypeScript is as popular as Babel these days, right? RICH: Yeah, I think so. I don't need to be sold on the benefits. I've been using TypeScript a lot myself. Svelte is written in TypeScript, but actually being able to write it inside your components is something that would involve as hacking around in the TypeScript compiler API in a way that, I don't know if anyone actually or any of us on the team actually knows how to do. So, we just need to spend some time and do that. But obviously when you've got an open source project, you need to deal with the bugs that arise and stuff first. So, it's difficult to find time to do a big project like that. CHARLES: So, devil's advocate here is if the compiler was open for extension, couldn't a TypeScript support be just another plugin? RICH: It could, but then you could end up with a situation where there's multiple competing TypeScript plugins and no one's sure which ones are used and they all have slightly different characteristics. I always think it's better if these things that are common feature requests that a lot of people would benefit from, if they're built into the project themselves. I go really light in the batteries included way of developing and I think this is something that we've sort of drifted away from in the frontend world over the last few years, we've drifted away from batteries included towards do it yourself. CHARLES: Assemble the entire thing. Step one, open the box and pour the thousand Lego pieces onto the floor. RICH: Yeah, but it's worse than that because at least, with a Lego set, you get the Lego pieces. It's like if you had the Lego manual showing you how to build something, but you were then responsible for going out and getting the Lego pieces, that's frontend development and I don't like it. CHARLES: Right. Yeah. I don't like that either. But still, there's a lot of people advocating directly. You really ought to be doing everything completely and totally yourself. RICH: Yes. CHARLES: And a lot of software development shops still operate that way. RICH: Yeah. I find that the people advocating for that position the most loudly, they tend to be the maintainers of the projects in question. The whole small modules philosophy, they exist for the benefit primarily of library authors and framework authors, not for the benefit of developers, much less users. And the fact that the people who are building libraries and frameworks tend to have the loudest megaphones means that that mindset, that philosophy is taken as a best practice for the industry as a whole. And I think it's a mistake to think that way. TARAS: There is also, I think, a degree of a sliding scale where you start off with like as the more experience you get, because there is more experience you get closer, you get to that kind of wanting granular control and then they kind of slides down towards granular control and then slice back up to, once you've got a lot of experience, you're like, "Okay, I don't want this control anymore." And then you kind of cast that and you get into like, "I'm now responsible for tools that my team uses," and now you're back to wanting that control because you want things to be able to click together. It's kind of like a way that your interest in that might change over time depending on your experience level and your position in the organization. So yeah, there's definitely different motivating factors. Like one of the things that we've been thinking a lot about is designing tools that are composable and granular at individual module level, but combined together into a system for consumption by regular people. So like finding those primitives that will just click together when you know how to click them together. But when you're consuming them, just feel like a holistic whole, but at the same time not being monolithic. That's a lot of things to figure out and it's a lot of things to manage over time, but that's solely the kind of things we've been thinking about a lot. RICH: I think that's what distinguishes the good projects that are going to have a long lifespan from the projects that are maybe interesting but don't have a long shelf life is whether they're designed in such a way that permits that kind of cohesion and innovation tradeoff, if you think of it as a trade off. Anyone can build the fastest thing or the smallest thing or the whatever it is thing. But building these things in a way that feels like it was designed holistically but is also flexible enough to be used with everything else that you use, that's the real design challenge. CHARLES: It's hard to know where to draw that line. Maybe one good example of this and, these are actually two projects that I'm not particularly a fan of, but I think they do a good job of operating this way. So, I guess in that sense, it means I can even be more honest about it. I don't particularly care for Redux or like observables, but we ended up using, in one of our last React projects, we had to choose between using Redux-Saga and Redux-Observable. The Redux-Observable worked very well for us. And I think one of the reasons is because they both had to kind of exist. They had to kind of co-exist is their own projects. Like Redux exists as its own entity and Observables exist as their own kind of whole ecosystem. And so, they put a lot of thought in like what is the natural way in which these two primitives compose together? As opposed to the Saga, which I don't want to disparage the project because I think it actually is a really good project. There's a lot of really good ideas there but because it's more like just bolted on to Redux and it doesn't exist outside of the ecosystem of Redux and the ideas can't flourish outside and figure out how it interfaces with other things. Like the true primitive is still unrevealed there. And so, whereas I feel like with Redux you actually have to really, really true primitives. Now, they're not necessarily my favorite primitives, but they are very refined and very like these do exactly what they are meant to do. And so when you find how they connect together, that experience is also really good. And the primitive that arises there I think ends up being better. Is that an example of what you guys are talking about? RICH: Maybe. [Laughs] TARAS: No, I think so. I mean, it's distilling to the essence, the core of what you're trying to do and then be able to combine it together. I mean, that's been kind of the thing that we've been working on at the Frontside. But also within this context, it makes me think of how does a compiler fit into that? How does that work with the compiler? It's just like when you add the compiler element, it just makes it like my mind just goes poof! [Laughter] CHARLES: Yeah, exactly. That's why I keep coming back to like, how do you, and maybe I haven't, you just have to kind of go through the experience, but it feels like maybe there's this cycle of like you build up the framework and then once it's well understood, you throw the framework away in favor of like just wiring it straight in there with the compiler and then you iterate on that process. Is that fair to say? RICH: Kind of, yeah. At the moment, I'm working on this project, so I referred a moment ago to being able to target webGL directly. At the moment, the approach that I'm taking to building webGL apps is to have webGL components inside Svelte in this project called SvelteGL. And we've used it a couple of times at the Times. It's not really production ready yet, but I think it has some promise. But it's also slightly inefficient, like it needs to have all of the shade of code available for whichever path you're going to take, whatever characteristics your materials have, you need to have all of the shade of code. And if we're smart about it, then the compiler could know ahead of time which bits of shade of code it needed to include. At the moment, it just doesn't have a way of figuring that out. And so that would be an example of paving those cow paths. Like if you do try and do everything within the compiler universe, it does restrict your freedom of movement. It's true. And to qualify my earlier statements about how the small modules philosophy is to the benefit of authors over developers, it has actually enabled this huge flourishing of innovation, particularly in the React world. We've got this plethora of different state management solutions and CSS and JS solutions. And while I, as a developer, probably don't want to deal with that, I just want there to be a single correct answer. It's definitely been to the advantage of the ecosystem as a whole to have all of this experimentation. Then in the wild, there are projects like Svelte they can then take advantage of. We can say, "Oh well, having observed all of this, this is the right way to solve this problem." And so, we can kind of bake in that and take advantage of the research that other people have done. And I think we have made contributions of our own but there is a lot of stuff in Svelte like the fact that data generally flows one way instead of having [inaudible] everywhere. Things like that are the results of having seen everyone make mistakes in the past and learning from them. So, there are tradeoffs all around. TARAS: One thing on topic of data flow here and there, one thing that I've been kind of struggling to compute is the impact of that as opposed to something where you have like one directional data flow because it seems like conceptually it's really simple. You set a property like in two way balance system, like you just propagate through stuff but we don't really have a way, you don't have any way of assessing what is the true impact of that computation. Like what is the cost of that propagation where I think it's almost easier to see the cost of that computation if you have like one directional data flow because you know that essentially everything between the moment that you invoke transition to computing the next state, that is the cost of your computation where you don't have that way of computing the result in a two way balance system. Something like Ember Run Loop or mobx or zones, Vues, reactive system. All these systems make it really difficult to understand what is the real cost of setting state. And that's something that I personally find difficult because this clarity that you have about the one directional data flow and what it takes to compute the next state, it's almost like because that cost is tangible where you're thinking about like mutation of objects and tracking their change like that cost is almost immeasurable. It just seems like a blob of changes that they have to propagate. I don't know. That's just something that I've been thinking a lot because especially with the work that we'll be doing with microstates because as you're figuring out what the next state is, you know exactly what operations are performed in a process where that might not be the case with the system that tracks changes like where you'd have with zones or with Ember Run Loop, or Vue. RICH: I would agree with that. The times that I found it to be beneficial to deviate from the top-down ideology is when you have things like form elements and you want to bind to the values of those form elements. You want to use them in some other computation. And when you do all that by having props going in and then events going out and then you intercept the event and then you set the prop, you're basically articulating what the compiler can articulate for you more effectively anyway. And so conceptually, we have two way bindings within Svelte, but mechanically everything is top down, if that makes sense. CHARLES: Is it because you can analyze the tree of top down and basically understanding when you can cheat. This might be really over-simplistic, but if you're kind of with the event, you're collecting the water and then you have to put it way up on top of the thing and it flows down. But if you can see the entire apparatus, you can say, "Actually, I've got this water and it's going to end up here, so I'm just going to cheat and put it over right there." Is that the type of thing that you're talking about where you're effectively getting a two way binding, but you're skipping the ceremony. RICH: It's kind of writing the exact same code that you would write if you were doing it using events. But if you're writing it yourself, then maybe you would do something in a slightly inefficient way perhaps. For example, with some kinds of bindings, you have to be careful to avoid an infinite loop. If you have an event that triggers a state change, the state change could trigger the event again and you get this infinite loop. A compiler can guard against that. It can say this is a binding that could have that problem, so we're going to just keep track of whether the state changes as a result of the binding. And so, the compiler can sort of solve all of these really hairy problems that you had faced as a developer while also giving you the benefit in terms of being able to write much less code and write code that expresses the relationship between these two things in a more semantic and declarative way without the danger. TARAS: This is one of the reasons why I was so excited to talk to you about this stuff, Rich, because this stuff is really interesting. I mentioned that we might, so we have a little bit more time. So I just want to mention, because I think that you might find this interesting, the [inaudible], the stuff that we were talking about that I mentioned to you before. So, I want to let Charles talk about it briefly because it's interesting, because it essentially comes down to managing asynchrony as it ties to life cycle of objects. Life cycle of objects and components are something we deal with on a regular basis. So, it's been an interesting exercise and experimenting with that. Charles, do you want to give kind of a low down? CHARLES: Sure. It's definitely something that I'm very excited about. So, Taras gets to hear like an earful pretty much every day. But the idea behind structure concurrency, I don't know if you're familiar with it. It's something that I read a fantastic -- so people have been using this for a while in the Ember community. So Alex Matchneer, who's a friend and often time guest on the podcast created a library called ember-concurrency where he brought these ideas of structure concurrency to the ember world. But it's actually very prevalent. There's C libraries and Python libraries. There's not a generic one for JavaScript yet, but the idea is just really taking the same concepts of scope that you have with variables and with components, whether they be ember components, Svelte components, React components or whatever there is, you have a tree of components or you have a of parents and children and modeling every single asynchronous process as a tree rather than what we have now, which is kind of parallel linear stacks. You call some tick happens in the event loop and you drill down and you either edit an exception or you go straight back up. The next tick of the event loop comes, you drill down to some stack and then you go back up. A promise resolves, you do that stack. And so with structure concurrency, essentially every stack can have multiple children. And so, you can fork off multiple children. But if you have an error in any of these children, it's going to propagate up the entire tree. And so, it's essentially the same idea as components except to apply to concurrent processes. And you can do some just really, really amazing things because you don't ever have to worry about some process going rogue and you don't have to worry about coordinating all these different event loops. And one of the things that I'm discovering is that I don't need like event loops. I don't really use promises anymore. Like actually, I was watching, I think it was why I was watching your talk when you're talking about Svelte 3, when you're like -- or maybe did you write a blog post about we've got to stop saying that virtual doms are fast? RICH: Yes, I did. CHARLES: So I think it was that one. I was reading that one and it jived with me because it's just like, why can't we just go and do the work? We've got the event, we can just do the work. And one of the things that I'm discovering is with using the construction concurrency with generators, I'm experiencing a very similar phenomenon where these stack traces, like if there's an error, the stack traces like three lines long because you're basically doing the work and you're executing all these stacks and you're pausing them with a generator. And then when an event happens, you just resume right where you left off. There's no like, we've got this event, let's push it into this event queue that's waiting behind these three event loops. And then we're draining these queues one at a time. It's like, nope, the event happens. You can just resume right where you were. You're in the middle of a function call, in the middle of like [inaudible] block. You just go without any ceremony, without any fuss. You just go straight to where you were, and the stack and the context and all the variables and everything is there preserved exactly where you left it. So, it's really like you're just taking the book right off the shelf and going right to your bookmark and continuing along. Rather than when you've got things like the run loop in ember or the zones in angular where you have all these mechanics to reconstruct the context of where you were to make sure that you don't have some event listener. An event listeners created inside of a context and making sure that that context is either reconstructed or the event listener doesn't fire. All these problems just cease to exist when you take this approach. And so, if it's pertinent to this conversation, that was a surprising result for me was that if you're using essentially code routines to manage your concurrency, you don't need event loops, you don't need buffers, you don't need any of this other stuff. You just use the JavaScript call stack. And that's enough. RICH: I'm not going to pretend to have fully understood everything you just said but it does sound interesting. It does have something not that dissimilar to ember's run loop because if you have two state changes right next to each other, X+=1, Y+=1, you want to have a single update resulting from those. So instead of instruments in the code such that your components are updated immediately after X+=1, it waits until the end of the event loop and then it will flush all of the pending changes simultaneously. So, what you're describing sounds quite wonderful and I hope to understand that better. You have also reminded me that Alex Matchneer implemented this idea in Svelte, it's called svelte-concurrency. And when he sent it to me, I was out in the woods somewhere and I couldn't take a look at it and it went on my mental to do list and you just brought it to the top of that to do list. So yeah, we have some common ground here, I think. CHARLES: All right. TARAS: This is a really, really fascinating conversation. Thank you, Rich, so much for joining us. CHARLES: Thank you for listening. If you or someone you know has something to say about building user interfaces that simply must be heard, please get in touch with us. We can be found on Twitter at @thefrontside or over just plain old email at contact@frontside.io. Thanks and see you next time.

For the Season 1 finale of The Grindstone, we dip into the archive to share our interview with Purdue Philosophy grad Tom Scholl. Tom joined us last fall while he was in town for the Scholl Lecture Series, which he sponsors.Tom discusses his journey from starting out as an Electrical Engineering major to graduating with a Philosophy degree, Purdue University in the late '60s, what he might do differently if he were to be a student again, some of the interesting jobs he had post-graduation, how students can put a Liberal Arts degree to work, his time as a CIA systems programmer, why it is that engineers and programmers are often leaning on the philosopher in the room, the ups and downs of entrepreneurship, and how philosophy has helped him in his business career.The 2018 Scholl Lecture was given by Jenann Ismael, Professor of Philosophy at Columbia University. You can see her talk here: "Some Thoughts on Time, Totality and Transcendence" Hosted on Acast. See acast.com/privacy for more information.

A Taste - "Language Always Fails Us One Way or Another..." We have for your listening pleasure Episode 312 of "Troubadours and Raconteurs with E.W. Conundrum Demure." Episode 312 features a very insightful conversation with Playwright and Performer - Eliza Bent. Eliza and I discuss Her Journey from a Philosophy Degree at Boston College to Writing and Staging Plays in NYC, Living in Rome, the Parallel Lives We Live, Regret, Limits & Wonderful Challenges with Language, Ludwig Wittgenstein, Religious Identity, Toilet Fires, Emotional Pain & Digestion, Looking For Your People... Episode 312 also includes an EW Essay titled "Killer Mike." We share the debut of a Radio Play performed by April Holgate and written by our Associate Producer Dr. Michael Pavese titled "This is the Story of My Song."We have an EW poem called "Embroidered." Our music this go round is provided by these wonderful artists: Django Reinhardt, Stephan Grapelli, Mink Deville, Morphine, Luther Dickinson & Sisters of the Strawberry Moon, Ani DiFranco, War, Branford Marsalis and Terrence Blanchard. Commercial Free, Small Batch Radio Crafted In the Endless Mountains of Pennsylvania... Heard All Over The World. Tell your Friends and Neighbors...

Continuing our ongoing study of how capitalism is Just. The. Worst, we took a look at recent Oscar contender The Big Short for an understanding of just how and why the generations that came before us broke the concept of money itself. Do we suddenly understand high finance? Listen and see (no,we don't)!