Podcasts about being mortal medicine what matters

Send us a textIf you're in your 50s or 60s, chances are you've either started caring for aging parents… or you see it coming. It's one of the most emotionally complex - and often overlooked - challenges we face in the second half of life. In today's heartfelt and surprisingly humorous episode, I sit down with bestselling author Howard Miller, whose book Burdens & Blessings offers a lighthearted but deeply honest look at what it means to care for your parents as they age. We explore the nuanced emotions of caregiving - guilt, resentment, grief, and even joy - and talk about how to navigate the messy middle ground between being a "good" child and a "dutiful" one. We also dive into sibling dynamics, end-of-life reflections, and how to embrace levity and gratitude in even the toughest moments. Whether you're deep in the caregiving trenches or just beginning to notice your parents slowing down, this conversation is packed with real talk, wisdom, and warmth. In this episode, you'll discover:·      The difference between a “good” son or daughter and a “dutiful” one·      How to handle caregiving without losing your identity - or your mind·      The power of humor and levity in the face of stress and grief·      Lessons in longevity, resilience, and preparing for what's next·      Why the best time to start planning for your own healthy aging is nowJoin Our 10 Week Diet Prep School Group Coaching Program:https://go.silveredgefitness.com/diet-prep-school-pif-orderResources & Links:Get Howard's book: Burdens & Blessings: A Lighter-Hearted Approach for Middle-Aged Folks Dealing with Aging Parentshttps://www.amazon.com/Burdens-Blessings-Lighter-Hearted-Approach-Middle-Aged/dp/0984399526/ Visit Howard's website:https://www.fulcrumpointpartners.com/over50hw Facebook:https://www.facebook.com/profile.php?id=100069856012226 LinkedIn:https://www.linkedin.com/in/howard-miller-1b0210/ In this conversation Howard mentioned the book Being Mortal by Atul Gawande:https://www.amazon.com/Being-Mortal-Medicine-What-Matters/dp/1250076226/Want to rewrite the narrative of your life and health? Visit the link below to see if our 1:1 coaching services are a perfect fit for your long term goals: https://go.silveredgefitness.com/schedule/coaching-inquiry Want more over 50 health and wellness goodness? Check out our private Facebook group: https://www.facebook.com/groups/silveredgefitness

My guest this week on the Over 50 Health & Wellness show is Rudd Crawford.  Rudd is an eighty year old who eight years ago began bodybuilding.  But that’s only a small part of what makes Rudd fascinating.  Join us this week as Rudd talks about his life’s journey and how he has thrived living on the edges of mainstream society.  Along the way we’ll hear exactly how Rudd has managed to build muscle and look – and feel – great at age eighty.  Rudd epitomizes the idea of healthy aging and the “it’s never too late to start” mentality.  You can connect with Rudd in the following ways:Facebook - https://www.facebook.com/rudd.crawfordEmail - ruddac@hotmail.comRudd mentioned the following resources in this episode:Abbreviated Training Facebook Group - https://www.facebook.com/groups/501864470260846Book - Being Mortal: Medicine and What Matters in the End - https://www.amazon.com/Being-Mortal-Medicine-What-Matters/dp/1250076226/You can listen to the Over 50 Health & Wellness show wherever you download podcasts or on my website. 

Assisted living facilities are being hit hard by COVID-19. In Episode 4 of Alz in the Fam, hosts Allan and Poli discuss the shocking news and aftermath of their mom testing positive for COVID-19. In Maryland, where Allan and Poli’s mom lives in a senior living community, a large percentage of coronavirus deaths have been in these senior care facilities and nursing homes. Cases began to appear at their mom’s facility about two weeks ago, so last week every resident and staff was tested for the virus. Turns out, their mom tested positive for the virus too.For the most part, Allan and Poli’s mom is doing well, aside from lack of appetite and no ability to taste food. But this diagnosis led the siblings to having a larger conversation about their mom and her end of life care preferences.The siblings have already taken steps to prepare for their mom’s end of life treatment - they have Advance Care Directive and Orders for Life Sustaining Treatment on file. The Alz In The Fam family urges all caregivers and children to have these conversations with your parents, no matter how difficult they may be. Being prepared is crucial.Currently, some of your parents’ preferences or treatment options may have changed during the COVID-19 pandemic. It is important to have these difficult conversations and be able to understand how different scenarios may unfold for you and your family.Here are the resources that Allan and Poli mentioned during the episode that can help every family navigate difficult end of life care decisions:Maryland Orders for Life Sustaining Treatment: https://marylandmolst.org/pages/molst_form.htm Being Mortal by Atul Gawande: https://www.amazon.com/Being-Mortal-Medicine-What-Matters-ebook/dp/B00JCW0BCY/ref=sr_1_1?dchild=1&keywords=being+mortal&qid=1589922153&sr=8-1 NYTimes OpEd article: https://www.nytimes.com/2020/04/04/opinion/coronavirus-ventilators.htmlIf you enjoy the podcast, would you please consider leaving a short review on Apple/Podcast/iTunes?

In this episode of Critical Matters, we explore the intersection of high-altitude medicine and physiology with critical care. Our guest is Robert B. Shoene, MD, FACP. Dr. Shoene is Associate Director, ICU and Critical Care, at St. Mary’s Medical Center in San Francisco. Dr. Shoene is a prolific author and researcher with more than 100 publications. His research has focused on pulmonary physiology and altitude medicine, and he has been part of numerous research expeditions to locations such as Mt. Everest and Denali. Additional Resources: Arterial Blood Gases and Oxygen Content in Climbers on Mount Everest: https://www.nejm.org/doi/full/10.1056/NEJMoa0801581 A comprehensive review on illnesses at high altitude: https://journal.chestnet.org/article/S0012-3692(08)60216-0/fulltext Everest: The West Ridge by Thomas Hornbein: https://www.amazon.com/Everest-West-Ridge-Thomas-Hornbein/dp/1594857075/ref=sr_1_1?ie=UTF8&qid=1520812701&sr=8-1&keywords=everest+the+west+ridge Endurance: Shackleton’s Incredible Journey by Alfred Lansing: https://www.amazon.com/Endurance-Shackletons-Incredible-Alfred-Lansing/dp/0465062881/ref=sr_1_1?s=books&ie=UTF8&qid=1520812797&sr=1-1&keywords=endurance Being Mortal: Medicine and What Matters in the End by Atul Gawande: https://www.amazon.com/Being-Mortal-Medicine-What-Matters/dp/1250076226/ref=sr_1_1?s=books&ie=UTF8&qid=1520812921&sr=1-1&keywords=Being+mortal Intensive Care, a poem by Dr. Robert Schoene: https://www.jstor.org/stable/1348231?seq=1#page_scan_tab_contents

In this episode, Caleb talks with Dean Nelson about the lessons he's learned from over 40 years of interviews. ------------- *Guest Links* ------------- Dean's website ( https://deannelson.net ) Dean on Facebook ( https://www.facebook.com/dean.nelson.370 ) Dean on Twitter ( https://twitter.com/deanenelson ) ----------------- *Links Mentioned* ----------------- A Man Called One by Fredrik Backman ( https://www.amazon.com/Man-Called-Ove-Novel/dp/1476738017/ref=sr_1_1?crid=391YTGGJFWZV6&keywords=a+man+called+ove&qid=1557186135&s=gateway&sprefix=a+man+%2Caps%2C201&sr=8-1 ) Beartown by Fredrik Backman ( https://www.amazon.com/Beartown-Novel-Fredrik-Backman/dp/1501160761/ref=tmm_hrd_swatch_0?_encoding=UTF8&qid=&sr= ) Being Mortal by Atul Gawande ( https://www.amazon.com/Being-Mortal-Medicine-What-Matters/dp/0805095152/ref=sr_1_1?crid=2OW2RJULLB7X3&keywords=being+mortal+atul+gawande&qid=1557186227&s=gateway&sprefix=being+more%2Caps%2C218&sr=8-1 ) ------------------------------------------- *The Learner's Corner Recommended Resource* ------------------------------------------- How to Handle Your Critics Like a Pro, Not a Toddler by Carey Nieuwhof ( https://careynieuwhof.com/how-to-handle-your-critics-like-a-pro-not-a-toddler/ ) ----------------- *What We Learned* ----------------- The interviews that go the best are the ones where there is a connection of humanity between the interviewer and interviewee. Most people want to tell their story How to prepare for an interview How Dean ends every interview Why you need to take control of an interview and how to do it You should know the answers to the questions you're asking before they're even asked. Preparation is 90% of a good interview. Dean's note taking strategy How to interview when you have a conflict of interest "Is this how you thought things were going to turn out for you?" - Ira Glass You can't be a good writer if you aren't a good reader. Don't just read or expose your mind to the same people. Intentionally complicate your thinking. Read above your skillset. ------------------------ *New Episode Every Week* ------------------------ Thank you for listening to the Learner's Corner Podcast. We hope you'll join us for next week's episode. Until next time, keep learning and keep growing.

Christine Walker, Owner of Christine Walker Physical Therapy, comes on the show to discuss her experience, education, and perspective working in various pediatric rehabilitation settings. She discusses her journey that led her to pediatrics, what she learned from school regarding pediatrics, pros and cons of her pediatrics training in school, how to overcome the most difficult aspects of working in pediatrics, her biggest mistakes she has made working with kids, tips on being the most successful with treating kids and dealing with parents, and much more! "Capital Gaines: Smart Things I Learned Doing Stupid Stuff" by Chip Gaines: https://www.amazon.com/Capital-Gaines-Things-Learned-Stupid/dp/0785216308/ref=sr_1_1?ie=UTF8&qid=1531022767&sr=8-1&keywords=capital+gaines+chip+gaines  "Being Mortal: Medicine and What Matters in the End" by Atul Gawande: https://www.amazon.com/Being-Mortal-Medicine-What-Matters/dp/1250076226/ref=sr_1_3?s=books&ie=UTF8&qid=1531026268&sr=1-3&keywords=being+mortal&smid=ATVPDKIKX0DER    Christine's PT Website Secrets Website: www.ptwebsitesecrets.com       Christine Walker Physical Therapy Website: http://www.drwalkerpt.com/   Christine's Facebook Page: https://www.facebook.com/christine.walker.5055    Christine Walker's PT Website Secrets Facebook Page: https://www.facebook.com/ptwebsitesecrets/    Christine's Twitter Page: https://twitter.com/DrWalkerPT    Christine's Instagram Page: https://www.instagram.com/walkercsw/  The PT Hustle Website: https://www.thepthustle.com/  Schedule an Appointment with Kyle Rice: www.passtheptboards.com    HET LITE Tool: www.pteducator.com/het       Biography: Christine Walker's interest in physical therapy started as a youth athlete when she was battling injuries in order to return to competitive soccer and springboard diving. Before becoming a physical therapist, she founded a springboard diving program at a local pool and provided sports-specific performance training to youth soccer players. Christine graduated with a B.A. in Exercise and Sports Science from UNC-Chapel Hill, and then completed her Doctor of Physical Therapy degree from the Medical University of South Carolina. Christine specializes in working with pediatrics (particularly youth athletes) and active adults. Currently, she is pending graduation as a Professional Yoga Therapist (PYT) through Ginger Garner's Professional Yoga Therapy Institute. She is also certified by the National Academy of Sports Medicine as a Performance Enhancement Specialist. Three years after PT school graduation, Christine started her own cash-based physical therapy practice, Christine Walker Physical Therapy, located in Charlotte, NC. She addresses movement dysfunction with a whole-body approach through exercise, manual therapy, yoga, stress management techniques, diet, and healthy lifestyle choices.

In this episode I am joined by Sarah Taylor Ph.D (https://uk.linkedin.com/in/sarahholiday) where we explore her research and practice into the ways we can enrich workplaces by humaising it and how we can also bureaucratise it too.  Our focus is her research in an elderly care setting and what employees and care workers in that setting really enjoy about their work, and how it is not necessarily what lines up with any set of 'professional standards'.  We begin with setting a philospohical and sociological backdrop and then dive into a lot of detail as to what her research has found.  We close by learning more about how Sarah is taking her research into a more corporate setting and looking at how her findings can inform ways that her organisation manages performance.  A really great conversation and as always... the references: Rupert Sheldrake - https://www.sheldrake.org   Theory U - https://en.m.wikipedia.org/wiki/Theory_U - Scharmer, C. O. (2009). Theory U: Leading from the Future as it Emerges. San Francisco: Berrett-Koehler.   The 5th wave of public health - http://www.thelancet.com/journals/lancet/article/PIIS0140-6736(13)62341-7/abstract Non paywalled/access limited article -  http://blog.policy.manchester.ac.uk/featured/2014/05/will-new-wave-bring-a-tide-of-progress-for-public-health/ Hanlon, P., Carlisle, S., Hannah, M., Reilly, D., & Lyon, A. (2011). Making the  case for a ―fifth wave‖ in public Health. Public Health, 125(1), 30–36.    Atul Gawande - Being Mortal: Medicene and what matters in the end https://www.amazon.co.uk/Being-Mortal-Medicine-What-Matters/dp/0805095152 https://www.youtube.com/watch?v=mviU9OeufA0 Martin Buber: I - Thou relationship https://en.wikipedia.org/wiki/I_and_Thou   - Andrews, N. (2014). We Need to Talk about Love‘. Co-production Walves.  Available from:  https://allinthistogetherwales.files.wordpress.com/2013/05/who-is-helping-who.pdf   - Kitwood, T. (2012). Dementia Reconsidered: The Person Comes First. Berkshire: Open University Press.   Loss of practical wisdom  https://www.ted.com/talks/barry_schwartz_on_our_loss_of_wisdom/up-next   Owen & Mayer - beautiful moments of connection http://www.myhomelife.org.uk/wp-content/uploads/2015/02/JRF-report-on-care-home-quality-of-life-full.pdf

AiA 148: What’s New in NativeScript with TJ VanToll On today's episode of Adventures in Angular, we have panelists Alyssa Nicoll, Ward Bell, and Charles Max Wood. We have a special guest, TJ VanToll of Progress. If you want to stay current with NativeScript, tune in! [00:01:55] – Introduction to TJ VanToll TJ works as a Developer Advocate for Progress, which is a software development company behind KendoUI, NativeScript, and few other tools. [00:02:20] – NativeScript NativeScript is completely free, completely open-source tool that lets you build iOS and Android native apps with Native user interfaces using JavaScript. It also provides built-in support for both TypeScript and Angular, as well. If you’re an Angular developer, it’s a tool that you can use to take Angular and build for Native iOS and Native Android. [00:03:15] – Native apps using JavaScript core or v8 on Android NativeScript uses Native UI components so they’re not using web view, the DOM, HTML, etc. For people that are coming from an Angular background, your apps look like Native apps. They’re using the same building blocks that you’d use if you’re building your app straight up in Xcode or Android Studio. You’re still building your apps the same way, the same file and folder structure, routing, etc. But the real learning curve that it takes to build NativeScript apps is that you have to use their user interface components to build your apps. [00:05:35] – Template syntax If you’re building a fairly complex Angular app, when you have all custom components, it’s going to look exactly like a NativeScript app. It’s basically using a suite of custom Angular components vs. using divs and spans as you’re building blocks. Angular is an optional dependency. NativeScript, at its lowest level, it’s just a technology that’s allowing the communication between JavaScript and these Native objects. The reason why the team spends a lot of time working with Angular integrations is that the model that Angular uses happens to be a really good fit for NativeScript. Any JavaScript developer who doesn’t really like using frameworks at all, using these components and syntax that they’re not familiar with could make their learning curve a little bit heavy. [00:08:05] – What’s new in NativeScript Over the last 6 months or a year, the team’s focus has been performance, tooling, and plug-ins. Performance: In the last release, specifically, NativeScript 3.0 was shipped back in May. That release is really the combination of profiling over the NativeScript source-code based on how fast your apps start up, how you can render your UI, etc. There is a cost to working with NativeScript because we are letting you write your source code in JavaScript. The team’s effort has been in really optimizing how fast you can paint your UI’s, how fast you can transition from one page to the next, the startup time, etc. One of the performance penalties that NativeScript has is because you’re using JavaScript, there is one step that truly Native apps don’t have. Specifically, Angular is not necessarily known for being the world’s smallest JavaScript framework. But Angular is being known for being very tool able. So the team shipped a Webpack plug-in that helps you reduce the footprint of your app, which means faster start-up times when you’re using Angular with NativeScript. Tooling: The other thing that’s related to tooling with NativeScript is the command line interface. You build NativeScript apps with the command line interface. The team is working on adding some more visual tooling, more like a companion to the CLI. There are problems that visual tooling can solve like how do you build your icons? How do you deal with splash screens? How do you deal with some of these Native configuration files? There is a thing called NativeScript Sidekick that can help you with some of these tasks. There’s an early beta out now. Plug-ins: The team purposely try to keep NativeScript core light, trying to keep our footprint small. TJ encourages developers, on your own team, and the NativeScript community to do that to your plugins because the NativeScript plug-in ecosystem explodes over the last few months. There are somewhere over 500 plug-ins. Their new plug-ins market place is plugins.nativescript.org/ that shipped several months ago. Now, they’re trying to work to add some consistencies to the plug-ins and adding some documentation around as well. [00:13:25] – NativeScript 3.0 upgrade and compatibility with NativeScript 2.0 It’s like Angular 2.0 to Angular 4.0 in a sense that there are few breaking changes but for most apps, it’s going to be fairly transparent or fairly trivial to update. It had some breaking changes with NativeScript plug-ins and one of the main reasons that they bumped the version number up is part of that performance changes to specifically render your interface faster. They also have to change their layout mechanism and some of the API with the NativeScript visual tree. Those are things that are unlikely to hit your common app because you’re probably just coding using their Angular components, in which case, you don’t necessarily need to know what’s going on under the hood. The team also worked with the plug-in authors of the top 30 or 40 most downloaded plugins out there to make sure that they were absolutely ready to go for the launch date for 3.0. If you are getting trouble with the upgrade, you can reach out on their forums. They’ve been trying to tackle these issues when they come up. [00:15:30] – Communication, upgrade, breaking things, and bugs Progress, as a company, haven’t done project quite like NativeScript before. It’s a project that’s completely open-source and completely free. They want to give people some freedom to of experiment and build their own things. But they try to be as transparent as possible on what we’re trying to do and reach out for feedback. They have a NativeScript Slack channel, which has a lot of people in there. They’re the first point of contact when making changes. And for the actual upgrade process, they try to actually put a good effort to get plug-ins where people have put on a considerable amount of effort into them. [00:17:35] – NativeScript 4.0 Debugging: If you’re a Visual Studio Code user, you can now just directly do this step debugging directly within the debug tab in VS Code for your completely Native iOS and Android apps. The team also launched support for the Chrome developer tools for NativeScript but they’re only available at a very limited capacity right now. Right now, in the Chrome dev tools, the console works and you can see network request but it’s not the full experience that you’d expect if you’re using those tools for web apps. Visual tree: One of the big pinpoints when it comes to learning NativeScript is learning how to build a visual tree with NativeScript. You can mess with CSS in your web apps, you can play around with layouts, play around with colors, etc. That’s possible to break that to NativeScript as well. Performance: The other big thing is again related to performance. We’ve got a lot of efforts going on at the moment, specifically, around start-up time. I mentioned we shipped a lot of performance-related things for NativeScript 3.0 but most of those were focused on the runtime experience – how fast we can paint your UI, how fast we can paint more complex Native user interfaces. We’re not turning our attention more to just how fast we can start-up your app and what sort of things we can do to optimize that and bring that number down as much as possible. A lot of that involves how can we fight with web configuration files to get exactly what we want, what are the best ways to reduce the number of files we’re using, use whatever we can to reduce that bundle size. The last that’s related to toolings is some of the visual tooling that we have. They think they can bring some fairly powerful behavior to NativeScript developers. In the past progress, they've had some premium tools for working with mobile apps that let you do things like build apps in the cloud. Say, you are a Windows developer and you want to build iOS apps, we have some premium tooling that could do that today. We think we’re going to be able to bring that to the open-source version of NativeScript, sort of make that work with directly within the NativeScript CLI. [00:21:15] – Store on distribution of apps With NativeScript, things are going to work exactly the same as if you’re building things from the ground up with Xcode or Android Studio. NativeScript CLI spits out the Native app package - that’s .apk file for Android and .ipa file for iOS. You just head out to the Native stores and actually register your apps and use those stores as the distribution model to get your app out to your users. There are certain people, especially companies, that don’t need to distribute their apps publicly. Think an app that you need your internal people to have, maybe they’re sales rep, maybe they’re doing an inventory job. In Progress, they sell some of the tools that you can use to distribute your apps locally to users. Because it’s generating those exact same Native binaries, once you have that, you can use any iOS or Android distribution model that you want to use. [00:22:30] – Start-up performance One of the big performance advantages that Native apps have is you don’t necessarily have to deal with a network. In terms of media files, a web app might need to worry about your initial load of image assets or video assets. But with Native apps, you have the ability to package that in the file. The specific cost when it comes to start-up time is not getting JavaScript from the network. The cost is actually the registration of your JavaScript code with v8 or JavaScript core. It’s the same reason that there’s a cost for that in the browser if you feed Angular into v8. There’s a cost that it will take to be able to parse that thing and run with it. [00:25:30] – Lower cost for low-powered devices TJ has zero concerns about NativeScript start-up performance on a high-end iPhone7. Startup time is like a millisecond. It’s not something that a person’s going to care about on a typical Native app. The bigger cost is on Android. It’s not because Android is necessarily slower. It’s because it has a wider range of performance characteristics from Google Pixel to some crappy Android 4.2 device that is still on the market. The team uses v8 on Android to run JavaScript. V8 has this feature called heap snapshots so you can pre-register some of your JavaScript codes directly in the heap memory of v8. Essentially, it’s a trick to shave-off some of those milliseconds when your app starts up. [00:27:10] – Service workers In NativeScript, there’s no service worker. You’re just using NativeScript API’s, which are abstracting away completely Native iOS or Android API. All of the things that a service worker does, you can accomplish in NativeScript. You can run in the background. You can get a user’s location in the background. You can send push notifications in the background. Anything that an app on your phone can do today that you’ve seen is possible to do on NativeScript apps. One of the reasons to build on NativeScript is your app can send push notifications when it is offline in iOS. It’s something that you can’t do on the web today. [00:29:05] – Getting started with NativeScript Javascript If you go to nativescript.org, there’s a Get Started button. There are 2 different tutorials you can go through to learn NativeScript. There’s one on Getting Started with NativeScript with straight up JavaScript if you’re the person who doesn’t like dependencies on framework completely. Angular And then, if you want to learn how to use Angular to build Native apps, there’s the other tutorial on NativeScript that’s on Angular. Video tutorials Also, community members just launch nativescripting.com, which is a companion to those tutorials but it’s the video-version of them [00:30:00] – Testing Unit test Unit testing on NativeScript is built directly into the NativeScript CLI. You can use any of the normal unit testing libraries that you might think of using – Mocha, Chai, Jasmine. For CI, there is NativeScript Travis. The team has articles and information on how you can build NativeScript on an automated way. Functional test And because NativeScript is generating Native iOS and Android apps, there are a lot of tools out there that lets you automate starting up and running application if you want a functional test. They start your apps, click the buttons, and make sure those behaviors still work. Internally, the team use a tool called Appian, which lets you automate our iOS and Android apps. Picks Ward Bell Being Mortal by Atul Gawande Alyssa Nicoll Hyper.is – JavaScript, HTML, CSS terminal Charles Max Wood Ego is the Enemy by Ryan Holiday TJ VanToll  Pokemon Go My Dad Wrote a Porno podcast NativeScript Newsletter Twitter @NativeScript  

AiA 148: What’s New in NativeScript with TJ VanToll On today's episode of Adventures in Angular, we have panelists Alyssa Nicoll, Ward Bell, and Charles Max Wood. We have a special guest, TJ VanToll of Progress. If you want to stay current with NativeScript, tune in! [00:01:55] – Introduction to TJ VanToll TJ works as a Developer Advocate for Progress, which is a software development company behind KendoUI, NativeScript, and few other tools. [00:02:20] – NativeScript NativeScript is completely free, completely open-source tool that lets you build iOS and Android native apps with Native user interfaces using JavaScript. It also provides built-in support for both TypeScript and Angular, as well. If you’re an Angular developer, it’s a tool that you can use to take Angular and build for Native iOS and Native Android. [00:03:15] – Native apps using JavaScript core or v8 on Android NativeScript uses Native UI components so they’re not using web view, the DOM, HTML, etc. For people that are coming from an Angular background, your apps look like Native apps. They’re using the same building blocks that you’d use if you’re building your app straight up in Xcode or Android Studio. You’re still building your apps the same way, the same file and folder structure, routing, etc. But the real learning curve that it takes to build NativeScript apps is that you have to use their user interface components to build your apps. [00:05:35] – Template syntax If you’re building a fairly complex Angular app, when you have all custom components, it’s going to look exactly like a NativeScript app. It’s basically using a suite of custom Angular components vs. using divs and spans as you’re building blocks. Angular is an optional dependency. NativeScript, at its lowest level, it’s just a technology that’s allowing the communication between JavaScript and these Native objects. The reason why the team spends a lot of time working with Angular integrations is that the model that Angular uses happens to be a really good fit for NativeScript. Any JavaScript developer who doesn’t really like using frameworks at all, using these components and syntax that they’re not familiar with could make their learning curve a little bit heavy. [00:08:05] – What’s new in NativeScript Over the last 6 months or a year, the team’s focus has been performance, tooling, and plug-ins. Performance: In the last release, specifically, NativeScript 3.0 was shipped back in May. That release is really the combination of profiling over the NativeScript source-code based on how fast your apps start up, how you can render your UI, etc. There is a cost to working with NativeScript because we are letting you write your source code in JavaScript. The team’s effort has been in really optimizing how fast you can paint your UI’s, how fast you can transition from one page to the next, the startup time, etc. One of the performance penalties that NativeScript has is because you’re using JavaScript, there is one step that truly Native apps don’t have. Specifically, Angular is not necessarily known for being the world’s smallest JavaScript framework. But Angular is being known for being very tool able. So the team shipped a Webpack plug-in that helps you reduce the footprint of your app, which means faster start-up times when you’re using Angular with NativeScript. Tooling: The other thing that’s related to tooling with NativeScript is the command line interface. You build NativeScript apps with the command line interface. The team is working on adding some more visual tooling, more like a companion to the CLI. There are problems that visual tooling can solve like how do you build your icons? How do you deal with splash screens? How do you deal with some of these Native configuration files? There is a thing called NativeScript Sidekick that can help you with some of these tasks. There’s an early beta out now. Plug-ins: The team purposely try to keep NativeScript core light, trying to keep our footprint small. TJ encourages developers, on your own team, and the NativeScript community to do that to your plugins because the NativeScript plug-in ecosystem explodes over the last few months. There are somewhere over 500 plug-ins. Their new plug-ins market place is plugins.nativescript.org/ that shipped several months ago. Now, they’re trying to work to add some consistencies to the plug-ins and adding some documentation around as well. [00:13:25] – NativeScript 3.0 upgrade and compatibility with NativeScript 2.0 It’s like Angular 2.0 to Angular 4.0 in a sense that there are few breaking changes but for most apps, it’s going to be fairly transparent or fairly trivial to update. It had some breaking changes with NativeScript plug-ins and one of the main reasons that they bumped the version number up is part of that performance changes to specifically render your interface faster. They also have to change their layout mechanism and some of the API with the NativeScript visual tree. Those are things that are unlikely to hit your common app because you’re probably just coding using their Angular components, in which case, you don’t necessarily need to know what’s going on under the hood. The team also worked with the plug-in authors of the top 30 or 40 most downloaded plugins out there to make sure that they were absolutely ready to go for the launch date for 3.0. If you are getting trouble with the upgrade, you can reach out on their forums. They’ve been trying to tackle these issues when they come up. [00:15:30] – Communication, upgrade, breaking things, and bugs Progress, as a company, haven’t done project quite like NativeScript before. It’s a project that’s completely open-source and completely free. They want to give people some freedom to of experiment and build their own things. But they try to be as transparent as possible on what we’re trying to do and reach out for feedback. They have a NativeScript Slack channel, which has a lot of people in there. They’re the first point of contact when making changes. And for the actual upgrade process, they try to actually put a good effort to get plug-ins where people have put on a considerable amount of effort into them. [00:17:35] – NativeScript 4.0 Debugging: If you’re a Visual Studio Code user, you can now just directly do this step debugging directly within the debug tab in VS Code for your completely Native iOS and Android apps. The team also launched support for the Chrome developer tools for NativeScript but they’re only available at a very limited capacity right now. Right now, in the Chrome dev tools, the console works and you can see network request but it’s not the full experience that you’d expect if you’re using those tools for web apps. Visual tree: One of the big pinpoints when it comes to learning NativeScript is learning how to build a visual tree with NativeScript. You can mess with CSS in your web apps, you can play around with layouts, play around with colors, etc. That’s possible to break that to NativeScript as well. Performance: The other big thing is again related to performance. We’ve got a lot of efforts going on at the moment, specifically, around start-up time. I mentioned we shipped a lot of performance-related things for NativeScript 3.0 but most of those were focused on the runtime experience – how fast we can paint your UI, how fast we can paint more complex Native user interfaces. We’re not turning our attention more to just how fast we can start-up your app and what sort of things we can do to optimize that and bring that number down as much as possible. A lot of that involves how can we fight with web configuration files to get exactly what we want, what are the best ways to reduce the number of files we’re using, use whatever we can to reduce that bundle size. The last that’s related to toolings is some of the visual tooling that we have. They think they can bring some fairly powerful behavior to NativeScript developers. In the past progress, they've had some premium tools for working with mobile apps that let you do things like build apps in the cloud. Say, you are a Windows developer and you want to build iOS apps, we have some premium tooling that could do that today. We think we’re going to be able to bring that to the open-source version of NativeScript, sort of make that work with directly within the NativeScript CLI. [00:21:15] – Store on distribution of apps With NativeScript, things are going to work exactly the same as if you’re building things from the ground up with Xcode or Android Studio. NativeScript CLI spits out the Native app package - that’s .apk file for Android and .ipa file for iOS. You just head out to the Native stores and actually register your apps and use those stores as the distribution model to get your app out to your users. There are certain people, especially companies, that don’t need to distribute their apps publicly. Think an app that you need your internal people to have, maybe they’re sales rep, maybe they’re doing an inventory job. In Progress, they sell some of the tools that you can use to distribute your apps locally to users. Because it’s generating those exact same Native binaries, once you have that, you can use any iOS or Android distribution model that you want to use. [00:22:30] – Start-up performance One of the big performance advantages that Native apps have is you don’t necessarily have to deal with a network. In terms of media files, a web app might need to worry about your initial load of image assets or video assets. But with Native apps, you have the ability to package that in the file. The specific cost when it comes to start-up time is not getting JavaScript from the network. The cost is actually the registration of your JavaScript code with v8 or JavaScript core. It’s the same reason that there’s a cost for that in the browser if you feed Angular into v8. There’s a cost that it will take to be able to parse that thing and run with it. [00:25:30] – Lower cost for low-powered devices TJ has zero concerns about NativeScript start-up performance on a high-end iPhone7. Startup time is like a millisecond. It’s not something that a person’s going to care about on a typical Native app. The bigger cost is on Android. It’s not because Android is necessarily slower. It’s because it has a wider range of performance characteristics from Google Pixel to some crappy Android 4.2 device that is still on the market. The team uses v8 on Android to run JavaScript. V8 has this feature called heap snapshots so you can pre-register some of your JavaScript codes directly in the heap memory of v8. Essentially, it’s a trick to shave-off some of those milliseconds when your app starts up. [00:27:10] – Service workers In NativeScript, there’s no service worker. You’re just using NativeScript API’s, which are abstracting away completely Native iOS or Android API. All of the things that a service worker does, you can accomplish in NativeScript. You can run in the background. You can get a user’s location in the background. You can send push notifications in the background. Anything that an app on your phone can do today that you’ve seen is possible to do on NativeScript apps. One of the reasons to build on NativeScript is your app can send push notifications when it is offline in iOS. It’s something that you can’t do on the web today. [00:29:05] – Getting started with NativeScript Javascript If you go to nativescript.org, there’s a Get Started button. There are 2 different tutorials you can go through to learn NativeScript. There’s one on Getting Started with NativeScript with straight up JavaScript if you’re the person who doesn’t like dependencies on framework completely. Angular And then, if you want to learn how to use Angular to build Native apps, there’s the other tutorial on NativeScript that’s on Angular. Video tutorials Also, community members just launch nativescripting.com, which is a companion to those tutorials but it’s the video-version of them [00:30:00] – Testing Unit test Unit testing on NativeScript is built directly into the NativeScript CLI. You can use any of the normal unit testing libraries that you might think of using – Mocha, Chai, Jasmine. For CI, there is NativeScript Travis. The team has articles and information on how you can build NativeScript on an automated way. Functional test And because NativeScript is generating Native iOS and Android apps, there are a lot of tools out there that lets you automate starting up and running application if you want a functional test. They start your apps, click the buttons, and make sure those behaviors still work. Internally, the team use a tool called Appian, which lets you automate our iOS and Android apps. Picks Ward Bell Being Mortal by Atul Gawande Alyssa Nicoll Hyper.is – JavaScript, HTML, CSS terminal Charles Max Wood Ego is the Enemy by Ryan Holiday TJ VanToll  Pokemon Go My Dad Wrote a Porno podcast NativeScript Newsletter Twitter @NativeScript  

AiA 148: What’s New in NativeScript with TJ VanToll On today's episode of Adventures in Angular, we have panelists Alyssa Nicoll, Ward Bell, and Charles Max Wood. We have a special guest, TJ VanToll of Progress. If you want to stay current with NativeScript, tune in! [00:01:55] – Introduction to TJ VanToll TJ works as a Developer Advocate for Progress, which is a software development company behind KendoUI, NativeScript, and few other tools. [00:02:20] – NativeScript NativeScript is completely free, completely open-source tool that lets you build iOS and Android native apps with Native user interfaces using JavaScript. It also provides built-in support for both TypeScript and Angular, as well. If you’re an Angular developer, it’s a tool that you can use to take Angular and build for Native iOS and Native Android. [00:03:15] – Native apps using JavaScript core or v8 on Android NativeScript uses Native UI components so they’re not using web view, the DOM, HTML, etc. For people that are coming from an Angular background, your apps look like Native apps. They’re using the same building blocks that you’d use if you’re building your app straight up in Xcode or Android Studio. You’re still building your apps the same way, the same file and folder structure, routing, etc. But the real learning curve that it takes to build NativeScript apps is that you have to use their user interface components to build your apps. [00:05:35] – Template syntax If you’re building a fairly complex Angular app, when you have all custom components, it’s going to look exactly like a NativeScript app. It’s basically using a suite of custom Angular components vs. using divs and spans as you’re building blocks. Angular is an optional dependency. NativeScript, at its lowest level, it’s just a technology that’s allowing the communication between JavaScript and these Native objects. The reason why the team spends a lot of time working with Angular integrations is that the model that Angular uses happens to be a really good fit for NativeScript. Any JavaScript developer who doesn’t really like using frameworks at all, using these components and syntax that they’re not familiar with could make their learning curve a little bit heavy. [00:08:05] – What’s new in NativeScript Over the last 6 months or a year, the team’s focus has been performance, tooling, and plug-ins. Performance: In the last release, specifically, NativeScript 3.0 was shipped back in May. That release is really the combination of profiling over the NativeScript source-code based on how fast your apps start up, how you can render your UI, etc. There is a cost to working with NativeScript because we are letting you write your source code in JavaScript. The team’s effort has been in really optimizing how fast you can paint your UI’s, how fast you can transition from one page to the next, the startup time, etc. One of the performance penalties that NativeScript has is because you’re using JavaScript, there is one step that truly Native apps don’t have. Specifically, Angular is not necessarily known for being the world’s smallest JavaScript framework. But Angular is being known for being very tool able. So the team shipped a Webpack plug-in that helps you reduce the footprint of your app, which means faster start-up times when you’re using Angular with NativeScript. Tooling: The other thing that’s related to tooling with NativeScript is the command line interface. You build NativeScript apps with the command line interface. The team is working on adding some more visual tooling, more like a companion to the CLI. There are problems that visual tooling can solve like how do you build your icons? How do you deal with splash screens? How do you deal with some of these Native configuration files? There is a thing called NativeScript Sidekick that can help you with some of these tasks. There’s an early beta out now. Plug-ins: The team purposely try to keep NativeScript core light, trying to keep our footprint small. TJ encourages developers, on your own team, and the NativeScript community to do that to your plugins because the NativeScript plug-in ecosystem explodes over the last few months. There are somewhere over 500 plug-ins. Their new plug-ins market place is plugins.nativescript.org/ that shipped several months ago. Now, they’re trying to work to add some consistencies to the plug-ins and adding some documentation around as well. [00:13:25] – NativeScript 3.0 upgrade and compatibility with NativeScript 2.0 It’s like Angular 2.0 to Angular 4.0 in a sense that there are few breaking changes but for most apps, it’s going to be fairly transparent or fairly trivial to update. It had some breaking changes with NativeScript plug-ins and one of the main reasons that they bumped the version number up is part of that performance changes to specifically render your interface faster. They also have to change their layout mechanism and some of the API with the NativeScript visual tree. Those are things that are unlikely to hit your common app because you’re probably just coding using their Angular components, in which case, you don’t necessarily need to know what’s going on under the hood. The team also worked with the plug-in authors of the top 30 or 40 most downloaded plugins out there to make sure that they were absolutely ready to go for the launch date for 3.0. If you are getting trouble with the upgrade, you can reach out on their forums. They’ve been trying to tackle these issues when they come up. [00:15:30] – Communication, upgrade, breaking things, and bugs Progress, as a company, haven’t done project quite like NativeScript before. It’s a project that’s completely open-source and completely free. They want to give people some freedom to of experiment and build their own things. But they try to be as transparent as possible on what we’re trying to do and reach out for feedback. They have a NativeScript Slack channel, which has a lot of people in there. They’re the first point of contact when making changes. And for the actual upgrade process, they try to actually put a good effort to get plug-ins where people have put on a considerable amount of effort into them. [00:17:35] – NativeScript 4.0 Debugging: If you’re a Visual Studio Code user, you can now just directly do this step debugging directly within the debug tab in VS Code for your completely Native iOS and Android apps. The team also launched support for the Chrome developer tools for NativeScript but they’re only available at a very limited capacity right now. Right now, in the Chrome dev tools, the console works and you can see network request but it’s not the full experience that you’d expect if you’re using those tools for web apps. Visual tree: One of the big pinpoints when it comes to learning NativeScript is learning how to build a visual tree with NativeScript. You can mess with CSS in your web apps, you can play around with layouts, play around with colors, etc. That’s possible to break that to NativeScript as well. Performance: The other big thing is again related to performance. We’ve got a lot of efforts going on at the moment, specifically, around start-up time. I mentioned we shipped a lot of performance-related things for NativeScript 3.0 but most of those were focused on the runtime experience – how fast we can paint your UI, how fast we can paint more complex Native user interfaces. We’re not turning our attention more to just how fast we can start-up your app and what sort of things we can do to optimize that and bring that number down as much as possible. A lot of that involves how can we fight with web configuration files to get exactly what we want, what are the best ways to reduce the number of files we’re using, use whatever we can to reduce that bundle size. The last that’s related to toolings is some of the visual tooling that we have. They think they can bring some fairly powerful behavior to NativeScript developers. In the past progress, they've had some premium tools for working with mobile apps that let you do things like build apps in the cloud. Say, you are a Windows developer and you want to build iOS apps, we have some premium tooling that could do that today. We think we’re going to be able to bring that to the open-source version of NativeScript, sort of make that work with directly within the NativeScript CLI. [00:21:15] – Store on distribution of apps With NativeScript, things are going to work exactly the same as if you’re building things from the ground up with Xcode or Android Studio. NativeScript CLI spits out the Native app package - that’s .apk file for Android and .ipa file for iOS. You just head out to the Native stores and actually register your apps and use those stores as the distribution model to get your app out to your users. There are certain people, especially companies, that don’t need to distribute their apps publicly. Think an app that you need your internal people to have, maybe they’re sales rep, maybe they’re doing an inventory job. In Progress, they sell some of the tools that you can use to distribute your apps locally to users. Because it’s generating those exact same Native binaries, once you have that, you can use any iOS or Android distribution model that you want to use. [00:22:30] – Start-up performance One of the big performance advantages that Native apps have is you don’t necessarily have to deal with a network. In terms of media files, a web app might need to worry about your initial load of image assets or video assets. But with Native apps, you have the ability to package that in the file. The specific cost when it comes to start-up time is not getting JavaScript from the network. The cost is actually the registration of your JavaScript code with v8 or JavaScript core. It’s the same reason that there’s a cost for that in the browser if you feed Angular into v8. There’s a cost that it will take to be able to parse that thing and run with it. [00:25:30] – Lower cost for low-powered devices TJ has zero concerns about NativeScript start-up performance on a high-end iPhone7. Startup time is like a millisecond. It’s not something that a person’s going to care about on a typical Native app. The bigger cost is on Android. It’s not because Android is necessarily slower. It’s because it has a wider range of performance characteristics from Google Pixel to some crappy Android 4.2 device that is still on the market. The team uses v8 on Android to run JavaScript. V8 has this feature called heap snapshots so you can pre-register some of your JavaScript codes directly in the heap memory of v8. Essentially, it’s a trick to shave-off some of those milliseconds when your app starts up. [00:27:10] – Service workers In NativeScript, there’s no service worker. You’re just using NativeScript API’s, which are abstracting away completely Native iOS or Android API. All of the things that a service worker does, you can accomplish in NativeScript. You can run in the background. You can get a user’s location in the background. You can send push notifications in the background. Anything that an app on your phone can do today that you’ve seen is possible to do on NativeScript apps. One of the reasons to build on NativeScript is your app can send push notifications when it is offline in iOS. It’s something that you can’t do on the web today. [00:29:05] – Getting started with NativeScript Javascript If you go to nativescript.org, there’s a Get Started button. There are 2 different tutorials you can go through to learn NativeScript. There’s one on Getting Started with NativeScript with straight up JavaScript if you’re the person who doesn’t like dependencies on framework completely. Angular And then, if you want to learn how to use Angular to build Native apps, there’s the other tutorial on NativeScript that’s on Angular. Video tutorials Also, community members just launch nativescripting.com, which is a companion to those tutorials but it’s the video-version of them [00:30:00] – Testing Unit test Unit testing on NativeScript is built directly into the NativeScript CLI. You can use any of the normal unit testing libraries that you might think of using – Mocha, Chai, Jasmine. For CI, there is NativeScript Travis. The team has articles and information on how you can build NativeScript on an automated way. Functional test And because NativeScript is generating Native iOS and Android apps, there are a lot of tools out there that lets you automate starting up and running application if you want a functional test. They start your apps, click the buttons, and make sure those behaviors still work. Internally, the team use a tool called Appian, which lets you automate our iOS and Android apps. Picks Ward Bell Being Mortal by Atul Gawande Alyssa Nicoll Hyper.is – JavaScript, HTML, CSS terminal Charles Max Wood Ego is the Enemy by Ryan Holiday TJ VanToll  Pokemon Go My Dad Wrote a Porno podcast NativeScript Newsletter Twitter @NativeScript  

The death of a Teenage Mutant Ninja Turtle? The Lion King and Palliative Care? Changing the direction a river flows? Intrigued? Well listen on! In this episode Dr Amara Nwosu asks the question "what is culture?" and asks how a society's culture can affect how Palliative Care is considered and delivered. Can we change and create a culture where death and dying are not considered taboo subjects? This is from a UK perspective but hopefully it will be of interest. Topics covered in this podcast: Barbara Gomes - end of life intelligence network - what we know now:http://www.endoflifecare-intelligence.org.uk/resources/publications/what_we_know_now_2013 Andy Couch - Culture Making https://setsnservice.wordpress.com/2008/10/27/a-summary-and-review-of-andy-crouchs-new-book-culture-making-01-05-culture/ Dr Atul Gawande - 2014 BBC Reith Lectures http://www.bbc.co.uk/programmes/articles/6F2X8TpsxrJpnsq82hggHW/dr-atul-gawande-2014-reith-lectures Dr Atul Gawande - Being Mortal http://www.amazon.co.uk/Being-Mortal-Medicine-What-Matters/dp/0805095152 The death of Donatello (Teenage Mutant Ninja Turtles) http://www.techtimes.com/articles/40753/20150321/teenage-mutant-ninja-turtle-44-donatello-gruesomely-killed-in-action.htm Story of the dragonfly http://www.achildofmine.org.uk/The-story-of-the-Dragonfly/I8.htm Copyright Dr Amara Nwosu, KingAmi media 2014. www.amaranwosu.com Music by 'Year of the Fiery Horse' (YOTFH). Soundcloud link: @year-of-the-fiery-horse