Podcasts about Encapsulation

Dr. Julian E. Kunnie, professor of religious, Latin American, Middle Eastern and North African studies at the University of Arizona. In the denouement of our three-part series with Dr. Julian Kunnie, we discuss the following: The general lack of class consciousness within struggle. An example of how neoliberal/neocolonial policies have had dire consequences for the people of Azania (South Africa). Encapsulation of social movements. And, much more! Dr. Julian Kunnie's forthcoming book, The Earth Mother and the Assault of Capitalism: Living Sustainable with All Life, is scheduled for release June 25, 2025 (new release date as of January 27, 2025). This episode is dedicated to our beloved freedom fighter, distinguished elder, and now former political prisoner, LEONARD PLETIER! Your example of resilience and struggle has inspired many, and will continue to inspire many, well into the future via the beautyful ones that are not yet born. Welcome Home Dear Brother! This episode has featured music from: Rakaa of Dilated Peoples & 2Mex – “Right This Wrong” and Buggin Malone – “Peltier's Beat Goes On”, from the album Free Leonard Peltier: Hip Hop's Contribution to the Freedom Campaign Conscientization 101– "Decolonize This? Properly Defining Settlers – Part 1" Akala – “Welcome to Dystopia” from his album Doublethink A-Alikes (feat. M-1 & Raye 6) – “Whole Life” from their album Us Against Them Raggo Zulu Rebel – “Tears of Gaia (Raggo Recitals)” from his album Arthur Fleck The Podcast Was Just A Snippet Of The Interview. Want to Listen To The Unabridged Interview? Try C-101 Premium Podcast Free For 7 Days!

Fredrik talks to Dejan Milicic about software development - understanding, methods, and stories. We start by talking about encapsulation of knowledge and the essential software in organizations. Almost every organization should - it can be argued - be developing software that solves their unique problems, and yet so many outsource so much of their knowledge encapsulation. Oh, and we can never completely encapsulate our knowledge in code either, so all the more reason to keep people who actually know what the code does and why around. Dejan tells us about his way to Ravendb and a developer relations role - and how you can craft your own job, stepping suitably outside of your comfort zone along the way. We also talk about shortening attention spans, daring to dig down a bit and find out about the context of things. Like the second sentence of some oft-repeated quote. Prohibit bad things, but help automate doing good things and avoid doing the bad things completely. Dejan shares some database backstories - why would someone want to build one more database? Specifically, what lead to the creation of Ravendb? And the very strong opinions which have been built into it. Avoiding falling into marketing-driven development. After that, we drift into talking about processes and how we work. Every organization is unique - which strongly speaks against adapting the “best practices” and methodologies of others. Or keeping things completely the same for too long. Innovation is also about doing what other people are not doing. Why is concurrency still hard? The free lunch has been over for twenty years! Functional programming and immutability offer ways forward, why aren't these concepts spreading even more and faster? We get right back to understanding more context when Dejan discusses how few of us seem to have understood, just for example, the L in SOLID. Dive deeper, read more, and you will find new things and come up with new ideas. Finally, Dejan would like to see software development becoming just a little bit more mathematical. So that things can be established, verified and built on in a different way. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlundand @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Dejan Ravendb Informatics Domain-driven design Event sourcing Data is worthless - said in episode 601 Developer relations Nosql databases Jack of all trades Jimmy - who introduced Fredrik to Dejan at Øredev 2024 Hibernate Relational databases Oren Eini - creator of Ravendb Antipatterns n+1 Couchbase Scrum Agile software development The Toyota approach The Scrum guide Unison programming language - VC funded Dr. Dobb's journal The free lunch is over Concurrency SOLID Liskov substitution principle Repositories on top Unitofwork are not a good idea - by Rob Conery Elm Titles A mathematician turned software developer Coding, but without deadline Saturated with software development Encapsulation of knowledge A bit surreal Accept people as they are There's a second line Professional depression Prevented, not diagnosed The pipeline kind of thinking Frustration-driven development (You shouldn't be) Punished for being successful The largest company of his or her life so far Optimized for maintaining the status quo Wash away all the context Manager of one The proverbial Jira Substantial content Methods of moving forward

Fredrik talks to Dejan Milicic about software development - understanding, methods, and stories. We start by talking about encapsulation of knowledge and the essential software in organizations. Almost every organization should - it can be argued - be developing software that solves their unique problems, and yet so many outsource so much of their knowledge encapsulation. Oh, and we can never completely encapsulate our knowledge in code either, so all the more reason to keep people who actually know what the code does and why around. Dejan tells us about his way to Ravendb and a developer relations role - and how you can craft your own job, stepping suitably outside of your comfort zone along the way. We also talk about shortening attention spans, daring to dig down a bit and find out about the context of things. Like the second sentence of some oft-repeated quote. Prohibit bad things, but help automate doing good things and avoid doing the bad things completely. Dejan shares some database backstories - why would someone want to build one more database? Specifically, what lead to the creation of Ravendb? And the very strong opinions which have been built into it. Avoiding falling into marketing-driven development. After that, we drift into talking about processes and how we work. Every organization is unique - which strongly speaks against adapting the “best practices” and methodologies of others. Or keeping things completely the same for too long. Innovation is also about doing what other people are not doing. Why is concurrency still hard? The free lunch has been over for twenty years! Functional programming and immutability offer ways forward, why aren’t these concepts spreading even more and faster? We get right back to understanding more context when Dejan discusses how few of us seem to have understood, just for example, the L in SOLID. Dive deeper, read more, and you will find new things and come up with new ideas. Finally, Dejan would like to see software development becoming just a little bit more mathematical. So that things can be established, verified and built on in a different way. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We a re @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Dejan Ravendb Informatics Domain-driven design Event sourcing Data is worthless - said in episode 601 Developer relations Nosql databases Jack of all trades Jimmy - who introduced Fredrik to Dejan at Øredev 2024 Hibernate Relational databases Oren Eini - creator of Ravendb Antipatterns n+1 Couchbase Scrum Agile software development The Toyota approach The Scrum guide Unison programming language - VC funded Dr. Dobb’s journal The free lunch is over Concurrency SOLID Liskov substitution principle Repositories on top Unitofwork are not a good idea - by Rob Conery Elm Titles A mathematician turned software developer Coding, but without deadline Saturated with software development Encapsulation of knowledge A bit surreal Accept people as they are There’s a second line Professional depression Prevented, not diagnosed The pipeline kind of thinking Frustration-driven development (You shouldn’t be) Punished for being successful The largest company of his or her life so far Optimized for maintaining the status quo Wash away all the context Manager of one The proverbial Jira Substantial content Methods of moving forward

Breast Implant Illness (BII) is not going away anytime soon! It's something more and more women are experiencing. In this replay episode, I'm joined by Dr. Robert Whitfield to talk more in depth about BII. Dr. Whitfield is a conventionally trained surgeon who has spent decades as a plastic surgeon working with patients with breast cancer, who has developed a unique approach to recovery and healing people with these conditions, as well as using alternative methods for breast reconstruction without implants.  BII is a condition where people who have had breast implants go on to develop conditions, such as chronic fatigue, brain fog, joint pain, hormone imbalance, and premature menopause, all driven by inflammation continuing to react to the implant that is in your body.You will hear more about:The underlying genetic, dietary, and environmental factors contributing to BIIHow functional medicine addresses often-overlooked aspects of breast implant illnessThe rise in demand for explant surgeries and why women are increasingly seeking these proceduresUsing testosterone for wound healing and specific protocols for improving surgery recoveryThe comprehensive hormonal balance checks Dr. Whitfield employs to ensure successful outcomesUsing different techniques like fat transfers if you still want implantsAnd more!If you suspect you might have breast implant illness or are considering an explant surgery, don't hesitate to seek medical help. Trust your instincts and persist until you find the right doctor who will listen and provide the care you deserve. Keep on listening, and remember, your health is your most valuable asset!Thank You for Listening! Ready to deepen your fasting journey? Discover the Fasting Accelerator Collection—your ultimate guide to achieving remarkable fasting results and transforming your health. Don't miss out on the Fast to Faith app, your hub for exclusive recipes, community support, and tools to integrate faith, wellness, and health into your daily life.Build a Purpose-Driven, Profitable Business & Transform Lives? Take the next step with our Fast to Faith Coach Certification Program, crafted for individuals passionate about helping others thrive spiritually and physically. Find all these transformative resources and more at FasttoFaith.com. Start your journey today! Dr. Tabatha's Facebook: https://www.facebook.com/DrTabathaDr. Tabatha's IG: https://www.instagram.com/gutsydrtabatha/Dr. Tabatha's YouTube: https://www.youtube.com/@fasttofaith

Episode: 2808 Plastic encapsulation of microchips, protection from environment and loads.  Today, the encapsulation story.

Steve Smith, founder and principal architect at Nimble Pros, joins host Jeff Doolittle for a conversation about software quality. The episode begins with a discussion of why software quality matters for businesses, customers, and developers. Steve explains some patterns and practices that help teams design for quality. They discuss in detail the practices of testing and quality assurance, and the conversation wraps up with suggestions for fostering a culture of quality in teams and organizations. Brought to you by IEEE Computer Society and IEEE Software magazine.

Join The Community:https://discord.gg/dTb9HDmPhW Consider Supporting Us For A Few Bucks A Month:https://himedia.gg/tipPodcasts:https://himedia.gg/podcastsSubscribe On Youtube:https://bit.ly/himvideoSocial Media:https://himedia.gg/https://facebook.com/HIMediaTVhttps://instagram.com/himediatvhttps://bsky.app/profile/himediatv.bsky.socialhttps://twitter.com/HIMediaTVMerch Store:https://himedia.gg/merchSupport HI Media!

Subhendu Nayak is the Director of Formulation (Probiotics and Herbal) at Vida Herbs. He joins The Drip to talk about the complexities of manufacturing, from blending to storage, and the crucial role of water activity in maintaining probiotic potency. We'll also explore the nuances between CFU and AFU measurements and discuss innovative yet straightforward solutions. In this episode, you'll hear about:Water activity in probioticsColony Forming Units (CFU) versus Active Fluorescent Units (AFU)Spore-forming, non-spore-forming, and next-generation typesManufacturing processes like blending, encapsulation, and packagingHow keeping solutions uncomplicated can lead to better success and innovationJump to:(03:39) How AW measures the vapor pressure ratio in foods.(08:01) Minimize water activity to prevent probiotic die-off.(10:12) Molecular sieves control water activity and maintain potency.(15:20) Preferred sugar alcohols for coolness.(17:34) Granular ingredients ensure better stick-pack sealing.(22:54) Water activity control in oil prevents decay.(25:39) Plate counting measures CFU per gram. (30:20) Viable but unculturable cell health benefits questioned.(32:41) The guest's favorite artist and song(35:09) Featured artist and song(38:25) This episode's MantraFeatured Artist and Song:Sometimes Somehow by Eric E.Links mentioned in this episode:Vidya HerbsOne Dance by Drake, music was chosen by SubhenduConnect with the showAQUALABZachary Cartwright, PhD

In this episode of the podcast, we start our mini-series on how to look at coding with Objects in Java, kicking off with understanding encapsulation. Check out our courses at ⁠⁠⁠⁠https://courses.javaeasily.com⁠⁠⁠⁠ Get your Java Beginner's Starter Kit over at ⁠⁠⁠⁠https://javaeasily.com⁠⁠⁠⁠ This is the Java Easily Podcast where beginning and intermediate Java developers can get all the latest tips, tutorials and advice on Java software development.

Rich Oris hosts the Home Improvement Show, offering advice on home remodeling and maintenance. He emphasizes the importance of routine maintenance for both homes and cars.  

Matheus Albuquerque discusses the basics, benefits, and common pitfalls of Atomic CSS, while giving insights into best practices for using utility-first styling in modern web development projects. Links https://www.ythecombinator.space https://x.com/ythecombinator https://github.com/ythecombinator https://www.linkedin.com/in/ythecombinator We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Matheus Albuquerque.

Join us on the Mob Mentality Show as we sit down with the insightful Artie Gold to explore the pivotal role of scope and cognitive load in coding. In "Artie Gold on Scope is Your Friend: The Less You Need to Know at Any Given Moment, the Better," we delve into practical strategies for enhancing productivity and code quality through smart scope management. ### Scope and Cognitive Load Artie Gold sheds light on the false pride developers often take in handling complex code and high cognitive demands. We discuss the advantages of understanding as needed versus knowing everything at once. Are developers truly like acrobats, balancing multiple logic threads simultaneously? Artie highlights the human mind's limitations and the significant benefits of encapsulation in reducing cognitive load. Key topics include: - The detrimental effects of high scope and cognitive load on development - Encapsulation's role in making code easier to read, scan, and modify - Comparing agile, nimble, and shallow approaches to manage cognitive overload - Artie's amusing analogy of low-level code instructions to a simple task like buying milk - Strategies for helping developers adapt to a new paradigm of encapsulated code reading ### Clarity of Value on Stories We shift our focus to the critical importance of clarity in user stories and the benefits of direct client relationships. Artie discusses the drawbacks of indirect communication and the often humorous complications of serving as the middleman for another middleman. Discussion points include: - The irreplaceable value of direct conversations in understanding "the why" behind requests - Whether good story conversations can be replaced with a template or checklist - The impact of user feedback on delivered products versus theoretical future products - The risks of over-refinement, illustrated by the rock versus ruby MVP delivery example - Challenges in assuming everyone excels at written communication ### Code is Everything. Code is Nothing. In our final segment, we explore the dual nature of code. Code is vital—it produces value, is easier to change than other components, and serves as a repository of knowledge. Yet, code alone is meaningless without context and purpose. Artie elaborates on: - The necessity of keeping code in good shape for ease of future changes - Why "pretty" code isn't the goal—functional, adaptable code is - The inherent truthfulness of code as the ultimate source of software reality **Don't miss this insightful discussion with Artie Gold that can transform your approach to coding, user stories, and the fundamental nature of software development.** Video and Show Notes: https://youtu.be/0z2nQHT8Jvs   

Dr. Zimmerman presented a Real Science Lecture webinar on December 12th, 2023, titled “Not All Rumen-Protected Products Are Created Equal.” You can find the webinar recording at balchem.com/realscience.  Clay outlines four attributes of a good rumen-encapsulated product. They are feed and TMR stable, ruminal stable, nutrient bioavailability, and good efficacy biologically in the animal.  (6:21)Kari describes a TMR stability test that Balchem has been perfecting based on a paper published in 2016. One to two grams of a rumen-protected product (based on the nutrient composition) is mixed with a half pound of TMR in a Ziploc bag, then the mixture incubates for 0, 6, 12 or 24 hours (based on feeding 1x, 2x, or 3x per day). Once a sample is finished incubating, it's placed in a strainer bag in one liter of distilled water for one minute. Then, the amount of nutrient that was leached into the distilled water is measured. She describes some of the observations and trends they've seen from using this technique on different products. (8:24)Mark asks about the impact of abrasion during the mixing process on encap stability. Kari describes a mineral mix technique using a small ribbon and paddle mixer. In this case, 5-10 pounds of encap product are mixed with 90-95 pounds of a mineral mix for three minutes. Then a sample is analyzed for damage to the encap. Clay does not recommend pelleting any encapsulated product because that will only reduce efficacy. It may not be 100% damage, but it will be significant. (12:41)Scott asks about the freeze-thaw stability of encapsulates. Clay mentions that all of Balchem's encapsulated products are freeze-thaw stable. If a product is not, there will be cracks in the coating and some ruminal stability will be lost. (19:34)When it comes to ruminal stability, matrix encapsulates tend to have lower stability in the rumen, but it varies widely. Some have no ruminal stability; some lose less than 10% in the rumen. Encapsulation is a complex process and there are tradeoffs between some of the steps. For example, between TMR stability or rumen stability and bioavailability, the goal is to find the perfect mix of these to make a high-efficacy product on the farm. Kari describes a rumen stability test that can be conducted on-farm for protected choline and lysine products. Mark describes in situ experiments for rumen stability testing using small Dacron bags in rumen-cannulated animals. He mentions that creating an encap with high rumen stability and high intestinal digestibility is key.  (19:58)Bioavailability is key, but methodologies for assessing bioavailability are a limitation. Kari and Mark discuss the pros and cons of various in situ/in vivo techniques, including mobile bag, abomasal pulse dose, and stable isotope. (29:25)Clay mentions that in vitro techniques are a key piece to product development and testing, but may give erroneous results compared to in vivo testing. Kari describes an experiment she conducted with Mark comparing in vivo and in vitro techniques. She suggests that there may be an argument for creating specific in vitro tests built for different types of protected products.  For example, for a pH-sensitive product, a step mimicking abomasal enzymes would be important. For a fat-coated product, a step mimicking intestinal enzymes for fat breakdown would be important. Clay cautions that a product with only in vitro data should be regarded with skepticism. (44:25)Biological response in the animal is the key final step. Ultimately, you want independent, peer-reviewed data to prove the efficacy of a product. Mark reminds the audience that even if animals don't respond to a product, there are a host of different issues that could be causing that unrelated to the product being tested. Things like water quality, water quantity, stress, cow comfort - there's a whole laundry list of things to consider. (50:39)In closing, Kari recommends that when picking an encap product, ask for the research that hits the four pillars: TMR stability, rumen stability, bioavailability, and animal performance. Mark suggests that you can't make a bad encap good, but you can make a good encap bad if you aren't careful. Clay agrees that the more data, the better. Lastly, we need more work on the feed stability pillar which has been overlooked. It is a critical piece to encap products being effective in the field. (55:13)Please subscribe and share with your industry friends to invite more people to join us at the Real Science Exchange virtual pub table.  If you want one of our Real Science Exchange t-shirts, screenshot your rating, review, or subscription, and email a picture to anh.marketing@balchem.com. Include your size and mailing address, and we'll mail you a shirt.

Dr. Cussell discusses the philosophy behind using multiple active ingredients in skincare and the benefits of combining them in one bottle. He explains the process of compounding and formulating active ingredients and how they achieve different categories of action on the skin. The conversation also covers the importance of compliance in skincare and how a pleasure to use product can encourage regular use.  As the founder of Rejuvenation Clinics Australia plus 45 years experience in medicine, the discussion covers the role of skincare in conjunction with aesthetic treatments and the impact of good skincare on treatment results. In this conversation, Dr Garry Cussell breaks down many ingredient myths and helps us understand the factors to consider when choosing products. He emphasises the role of growth factors, collagen, and protein in skincare, as well as the importance of sunscreen and exfoliation. Cussell also highlights the benefits of topical probiotics and different types of hyaluronic acid to protect the skin biome.  Key Takeaways Using multiple active ingredients in skincare can be more beneficial as they work synergistically and can be combined in one bottle for easier use and compliance. Formulating active ingredients involves finding alternate forms of well-known ingredients that work just as well but can be combined without clashing. Encapsulation technology helps stabilise reactive ingredients and ensures slow release for better efficacy. Good skincare can enhance the results of aesthetic treatments and help maintain the improvements over time. Growth factors and collagen peptides are key ingredients in Rejuvaus skincare as they stimulate collagen production and support skin metabolism.  Comprehensive skincare should address multiple factors, including growth factors, collagen, protein, sunscreen, exfoliation, and hydration. Topical probiotics can help maintain a healthy skin microbiome. Different types of hyaluronic acid have varying molecular sizes and absorption capabilities. Physical sunblocks, such as zinc-based ones, provide better protection and do not require frequent reapplication. Using clean ingredients and natural preservatives can ensure the safety and efficacy of skincare products.   Chapters00:00 Introduction and Philosophy of Using Multiple Active Ingredients03:13 Formulating Active Ingredients for Different Categories of Action06:08 The Importance of Compliance and Pleasure in Skincare08:15 The Role of Encapsulation in Stabilizing and Enhancing Efficacy12:52 Skincare in Conjunction with Aesthetic Treatments33:13 Topical Probiotics and Hyaluronic Acid35:52 The Importance of Sunscreen42:44 Using Clean Ingredients45:08 Recommended Products48:01 Future DevelopmentsSee omnystudio.com/listener for privacy information.

Placental encapsulation involves the process of steaming, dehydrating, and grinding the placenta into a power that is then filled into capsules. Recently, there's been a lot of talk about this topic. Check out this episode of the podcast to learn the pros and cons of placental encapsulation (based on my honest opinion). Then, you can make your decision own decision! Download and listen now!

Send us a Text Message.Ready to conquer the CISSP exam? This episode promises to arm you with crucial insights into the OSI model and its real-world applications. We kick things off by unraveling the intricacies of VPN tunnels and the pivotal role the data link layer plays in encapsulating data packets for secure internet travel. Next, you'll grasp how a significant Border Gateway Protocol (BGP) security breach zeroes in on the network layer. We then dissect the limitations of firewalls at the transport layer, ensuring you understand which types of traffic remain beyond their reach.Switching gears, we tackle the security hurdles of converged networks and VLAN segmentation. Discover why adaptive security measures are essential in environments where voice and data traffic coexist and how misconfigurations can open doors to unauthorized access. We also highlight the havoc DDoS attacks wreak across multiple OSI layers and the vulnerabilities of VoIP over wireless LAN. By the end, you'll appreciate the necessity of detecting IP spoofing at the network layer and how VLANs bolster security through tailored policies and isolated broadcast domains. Join us as we not only aim to boost your CISSP readiness but also ignite your passion for a thriving career in cybersecurity.Gain access to 60 FREE CISSP Practice Questions each and every month for the next 6 months by going to FreeCISSPQuestions.com and sign-up to join the team for Free. That is 360 FREE questions to help you study and pass the CISSP Certification. Join Today!

In this episode I chat with Simone Holtznagel, who shares her pregnancy journey, birth story and recovery journey, with baby Gia being born at the end of March.Simone Holtznagel is one of Australia's media personalities, and has appeared in shows such as 'Australia's Next Top Model' and 'I'm A Celebrity Get Me Out Of Here'.In today's podcast episode, Simone opens up about her birth preparation, describes what she would have done differently with her birth preparation (hint, it's to do with her pelvic floor!).Simone also describes her vaginal birth including use of epidural, and she also shares what she did with her placenta, including placental encapsulation and a placenta smoothie!LINKS:Preparing for birth Pelvic health checklistFree 7 Day Trial Pregnancy WorkoutsFree 7 Day Trial Postnatal WorkoutsFitNest Mama WebsiteInstagram @fitnestmamaSimone's Instagram: @simoneholtznagel** This podcast has general information only. Always seek the guidance of your doctor or other qualified health professional with any questions or concerns you may have regarding your health or medical condition. Free Register now: https://www.fitnestmama.com/pregnancyworkshop

Send us a Text Message.Are multi-layer protocols the key to safeguarding our digital world amidst the rising tide of cyberattacks? Join me, Sean Gerber, as I unravel the complexities of these protocols and their vital role in cybersecurity, drawing from the CISSP ISC² domains 4.1.4 and 4.1.5. By sharing my firsthand experiences and highlighting the alarming $22 million ransomware payout by Change Healthcare, I underscore the urgent need for redundancy in critical systems, especially within vulnerable sectors like healthcare.Let's decode the layers of data encapsulation, from the basic principles of TCP/IP to the robust security offered by TLS and IPsec. We'll discuss how VPN tunnels enhance security and tackle the sophisticated challenge of attackers concealing their activities within encrypted traffic. Discover methods to unmask these covert channels using decryption appliances and targeted traffic inspection, and explore the fascinating realm of steganography for data concealment.The journey continues with a deep dive into data exfiltration techniques, including EDI communication and low-level network protocols like ICMP and DNS. Learn how malicious actors bypass detection and how network administrators can stay vigilant. Finally, I'll share my passion for mentorship in cybersecurity, highlighting the enriching experiences and opportunities available through CISSP Cyber Training and my own platforms. Whether you're a seasoned professional or an aspiring expert, this episode offers valuable insights and resources to bolster your cybersecurity knowledge and career.Gain access to 60 FREE CISSP Practice Questions each and every month for the next 6 months by going to FreeCISSPQuestions.com and sign-up to join the team for Free. That is 360 FREE questions to help you study and pass the CISSP Certification. Join Today!

Summary In this episode of Coffee & Christ, Robert Bolden shares his thoughts on the verse of the day from 2 Corinthians 1:3-4. He emphasizes the importance of compassion and how it differs from empathy. Robert believes that many people get stuck in their feelings and live in the past, but Jesus can heal them in the present. He encourages listeners to go to God for comfort and solutions in all their troubles. Robert also discusses the attitude behind actions and the power of thoughts, highlighting the need to maintain a pure heart and seek reconciliation with others. Takeaways Compassion is different from empathy as it allows us to meet people where they are but not leave them there. Jesus can heal us in the present, and we don't need to spend time and money going back into our past to find healing. Going to God first for comfort and solutions in our troubles is key. The attitude behind our actions is important, and wrong thoughts can lead to wrong actions. Maintaining a pure heart and seeking reconciliation with others is crucial. Keywords compassion, empathy, healing, comfort, attitude, actions, thoughts, pure heart, reconciliation Keywords compassion, empathy, healing, comfort, attitude, actions, thoughts, pure heart, reconciliation Titles Seeking Reconciliation with Others Going to God First for Comfort and Solutions Chapters 00:00 Introduction and Verse of the Day 02:18 The Importance of Compassion 08:20 The Encapsulation of Life in 2 Corinthians 1:3-4 09:54 Making Faith a Habit 17:16 Conclusion Ready to become part of the community? http://www.lifetransformed.podia.com, message us and we will give you free access. Check out our website:  http://www.life-transformed.com Schedule a serve call https://www.picktime.com/LifeTransformed Instagram https://www.instagram.com/bbolden18?igsh=cnlvdjQ5eGJwZTM%3D&utm_source=qr YouTube https://www.youtube.com/channel/UCx6sszulCUrjodEyThd-rBw --- Send in a voice message: https://podcasters.spotify.com/pod/show/robert-bolden/message

Join Cleve Gaddis on GoGaddis Real Estate Radio as we explore the ins and outs of crawl space encapsulation. We'll be joined by expert advisor Brett Gordon, President/CEO of World Class Home Inspections LLC and World Class Property Services, to discuss everything you need to know about this important home improvement process. From understanding the benefits to cost considerations, this episode will empower you to make informed decisions about your home's crawl space. Segment Introduction: Welcome back to GoGaddis Real Estate Radio. Today, we have a special guest, Brett Gordon, joining us to dive deep into the topic of crawl space encapsulation. We'll explore what it is, why it's needed, and the many benefits it offers homeowners. If you're considering encapsulating your crawl space, this segment is a must-listen. What is Crawl Space Encapsulation?: Define crawl space encapsulation and explain the process involved. Discuss how encapsulation helps protect your home and improve indoor air quality. Why Would Crawl Space Encapsulation be Needed?: Explore common issues that may necessitate crawl space encapsulation, such as moisture problems, pest infestations, and energy inefficiency. Benefits of Encapsulating a Crawl Space: Highlight the numerous benefits of crawl space encapsulation, including improved indoor air quality, increased energy efficiency, and enhanced structural integrity. Cost Considerations: Discuss the factors that can influence the cost of crawl space encapsulation, such as the size of the crawl space, extent of damage, and choice of materials. Listener Question - Crawl Space Concerns: Address listener questions or concerns about crawl space encapsulation and offer expert advice on how to approach the process. Closing Segment: Thank you for joining us on today's episode of GoGaddis Real Estate Radio. We hope you now have a better understanding of crawl space encapsulation and its benefits. Tune in next time for more valuable insights into homeownership and real estate. Host of GoGaddis Radio, Cleve Gaddis, has been a fixture in metro Atlanta real estate since 2000. He has served Atlanta since 1987 by helping thousands of buyers and sellers make smart decisions. As a Co-Team Leader of Modern Traditions Realty Group, he is able to help clients and real estate agents alike. He has the heart of a teacher and is passionate about helping listeners learn the ups and downs and the ins and outs of smart home buying and selling all throughout metro Atlanta. If you have a question for Cleve, click here : https://gogaddisradio.com/ask-a-question If you are looking to buy or sell your home with Cleve, click here : https://moderntraditionsrealty.net/contact If you are looking to join a real estate team, click here : https://moderntraditionsrealty.net/career-opportunity If you bought a home last year, don't forget to file your Homestead Exemption! https://moderntraditionsrealty.net/homestead-exemption

Welcome to a special Q &A episode of the Evidence Based Birth® Podcast! Today I address some of your burning questions on key childbirth topics! In this episode, I share evidence on the (unproven) relationship between synthetic oxytocin (Pitocin) administration and postpartum depression, the complexities of delayed cord clamping and the power dynamics around requesting delayed cord clamping, the use of Nubain (an IV opioid) for pain relief during labor and its potential impact on babies, and the latest insights into consuming the placenta—whether it's dehydrated, freeze-dried, or consumed raw. EBB Resources: The EBB Pocket Guide to Interventions Evidence on: Pitocin During the Third Stage of Labor Effects of IV Opioids during Labor The Evidence on Placenta Encapsulation Watch the video of this podcast episode on the EBB YouTube channel here!  Join the EBB Pro Membership and get access to contact hours, a doula mentorship, live trainings, and a PDF Library with exclusive handouts (including a 2-page handout on breech) by joining here. Learn advocacy techniques through the EBB Childbirth Class.

This episode is from a webinar presented by Dr. Clay Zimmerman, Director of Technical Services at Balchem. To view the full webinar and access the slides referenced during this podcast, visit balchem.com/realscience and scroll down to the webinar presented on December 12th, 2023.Dr. Zimmerman begins with an overview of Balchem's microencapsulation technologies in both human nutrition and health and animal nutrition and health businesses. (0:31)Encapsulation is a generic term, and huge differences can exist between products that protect the same compound. Balchem's microencapsulation technology consists of packaging a substance in a lipid capsule for protection. Encapsulates can differ in design, technology, and performance. When it comes to performance in ruminant encapsulates, stability in feed mixing and TMRs and animal performance are evaluated. (6:50)Lipid encapsulation usually comes in one of two forms, a matrix encapsulation or a true encapsulation. A good analogy for matrix encapsulation is chocolate chip cookie dough, where some active compound is always at the surface. In the rumen, this leads to reduced protection and stability. True encapsulation, often called single-layer or multiple-layer encapsulation, is analogous to an m&m where there is no active compound at the surface, and this leads to greater protection and stability in the rumen.  (12:00)So why do we encapsulate nutrients for ruminants? In general, for targeted delivery within the gastrointestinal tract of the animal because rumen fermentation often results in massive breakdown of most of these important compounds. For example, choline chloride is almost completely degraded in the rumen. (18:30)When developing or improving rumen-protected products for nutrients such as choline chloride, methionine, lysine, or niacin, the primary goal is to protect them as much as possible from ruminal degradation while achieving post-ruminal absorption. Once prototypes have good ruminal stability and good intestinal release, the next step is feed and mixing stability. Dr. Zimmerman goes on to showcase different research techniques for evaluating encapsulates in these three areas as well as in animal performance. (20:39)In summary, there are many differences in encapsulated products for dairy cows, due to the design of products; types, amount, and composition of coatings; manufacturing differences; and differences in nutrient content, bioavailability, and feed stability. True encapsulates, or multi-layered coating products, are preferred for ruminant applications due to their higher levels of ruminant and feed stability. Four really important features of a good ruminant encapsulate are good ruminal stability, good nutrient bioavailability, feed and TMR stability, and ultimately biological performance. (47:05)Dr. Zimmerman then answers questions from the webinar audiences about in vitro techniques and bioavailability, coating ingredients, the importance of base diet for rumen fluid donors in in vitro techniques, variation in products from in vitro to in vivo results, how long it takes to develop a new encapsulated product (Balchem spends years and even decades researching before a product release), and why nutrient contents differ so much in similar encapsulated products on the market. (49:58) Please subscribe and share with your industry friends to bring more people to join us around the Real Science Exchange virtual pub table.  If you want one of our new Real Science Exchange t-shirts, screenshot your rating, review, or subscription, and email a picture to anh.marketing@balchem.com. Include your size and mailing address, and we'll get a shirt in the mail to you.

New Ebook : US Presidential Election 2024 - Clairvoyant/Psychic predictions for Joe Biden, Donald Trump and each candidate for POTUS 2024 - Who will be poisoned, who will killed, Who will be the next US President 2024, Upcoming coups, scandals... - where? World Predictions for: Russia, Israel and China Author: Clairvoyant Dimitrinka Staikova Published - November 26,2023 Price - 80 British Pounds (GBP) Table of Contents : 1. Clairvoyant/Psychic reading to a photo of Alien object spotted near the Sun (year 2023) - The End and the beginning of the world - when? Facts, Evidences, Climate change . What will happen to the planet Earth and when? What will help for the new beginning of the Earth ? - by Clairvoyant Dimitrinka Staikova - August 14,2023 2. Joe Biden (US President) - 2024 Election, His health, Business, Political battle with Trump and details on his campaign plans, Money, Political predictions for Biden and USA until April 2024 - what will happen with the world and USA? When Joe Biden will be out of the Political game? - Clairvoyant reading/Psychic predictions September 18,2023 - by Clairvoyant Dimitrinka Staikova 3. Yevgeny Prigozhin ( Leader of Wagner Private Mercenary Group) - The creation of the new genetic man, The mystery behind Prigozhin's "death " , His goal, His work, His world crusade - Clairvoyant reading/Psychic predictions September 27,2023 - by Clairvoyant Dimitrinka Staikova 4. Marianne Williamson (Democratic Primary challenger to Joe Biden on 2024 Election) - What is the future of her campaign, Her health, What is Upcoming...? - Clairvoyant reading/Psychic predictions September 28,2023 - by Clairvoyant Dimitrinka Staikova 5. Robert F. Kennedy Jr. (Presidential candidate on US Election 2024) - The future of USA year 2023/2024 seen through his eyes. A new war will appear..., An airplane crash..., What will happen with Biden? When USA will be covered in blood? - Clairvoyant reading/Psychic predictions September 29,2023 - by Clairvoyant Dimitrinka Staikova 6. Donald Trump (Presidential candidate on 2024 Election in USA) - Tough political battle, Clairvoyant predictions for each month until the 2024 Election in USA - Who will win? How will win? A little before the presidential election 2024 one of the candidates is falling - Who will remain? When the Earth will be threatened and by what? - Clairvoyant reading/Psychic predictions September 30,2023 - by Clairvoyant Dimitrinka Staikova 7. Nikki Haley (Running for POTUS - candidate for 2024 Election in USA) - Clairvoyant reading/Psychic predictions October 2, 2023 for : Her health, Money , Nerves, Encapsulation - by Clairvoyant Dimitrinka Staikova 8. Vivek Ramaswamy (Presidential candidate for 2024 Election in USA ) - …….VISIT OUR E-BOOK STORE : https://sites.google.com/site/dimitrinkastaikova/home/new-ebook-us-presidential-election-2024-clairvoyantpsychic-predictions https://clairvoyantdimitrinkastaikova.weebly.com/blog---hottest-news-predictions/new-ebook-us-presidential-election-2024-clairvoyantpsychic-predictions-for-joe-biden-donald-trump-and-each-candidate-for-potus-2024-who-will-be-poisoned-who-will-killed-who-will-be-the-next-us-president-2024-upcoming-coups-scandals-where

Peptide therapies, known for their diverse range of medical applications, are often administered through injections rather than oral pills or liquids. This stems from several important factors that influence the effectiveness and reliability of these treatments and patients' specific needs and preferences. Today, we'll talk about the difference between oral and injectable peptide therapies and when to use them. Peptide Structure and Digestive Process To understand why one would use an injectable peptide therapy over an oral peptide therapy, we must first go over the digestive process and how pills work.  Complexity of Peptides: As a reminder, peptides are made of linked amino acids, forming chains that vary in length and structure. When administered orally, peptides face challenges in surviving the harsh environment of the digestive system. How do oral pills work? When you swallow a pill, it goes to your stomach and intestines. It's then broken down by your digestive system and enters your bloodstream.  When you swallow an oral peptide, it undergoes the "first pass effect ."This is when the body breaks down (metabolizes) a medication before it starts working. This typically happens in the liver but can also occur in the digestive system. When the oral peptide is broken down, its original concentration (amount) is decreased. Because of this, only some of the peptides in pill form enter your bloodstream. Peptides given via injection avoid the first pass and enter the bloodstream directly. When this happens, a higher concentration of the intact peptide reaches the bloodstream and is more predictable and potent. Digestive Enzymes: Digestive enzymes break down food to absorb the nutrients our bodies need. The three main digestive enzymes break down fats, carbohydrates, and proteins.  Proteases in the stomach and intestines break down proteins, including peptides, into their constituent amino acids. Because of this, oral peptides are broken down and rendered ineffective before they reach the bloodstream. Peptides administered through injections are more stable in their original form since they are not exposed to the digestive enzymes that can break them down. Dosage Control: Injectable peptide therapies offer better dosage control than oral administration. Injections allow healthcare providers to administer the required dosage precisely, ensuring consistent and controlled therapy. This is extremely important for therapies requiring individualized dosing or specific amounts for optimal effectiveness. Advancements in Oral Delivery: Despite the current preference for injectable peptide therapies, ongoing research focuses on developing innovative methods for effective oral peptide delivery. Encapsulation technologies, protective coatings, and specialized formulations aim to overcome the challenges of oral administration, potentially improving bioavailability and efficacy. Keep in mind: People dealing with chronic issues like gastrointestinal (GI) problems or those seeking long-term maintenance and support for overall health might prefer the oral form of specific peptide therapies. It is more convenient and non-invasive than injections. Still, it may be more cost-effective for prolonged use in some instances.  A great example of this is BPC 157. It's stable in human gastric juice for 24 hours. People taking it for gut health may prefer to take it orally. And those suffering from acute injury (muscle, tendon, or ligament injury) may want to use the injectable form when quicker healing and recovery is desired.  Thanks again for listening to The Peptide Podcast. We love having you as part of our community. If you love this podcast, please share it with your friends and family on social media, and have a happy, healthy week! Pro Tips We're huge advocates of using daily greens in your routine to help with gut, skin, nail, bone, and joint health. We take AG1 (athletic greens) every day. It has vitamins, minerals, a diverse range of whole-food sourced ingredients, and probiotics to promote a healthy gut microbiome and adaptogens to help with focus and mood balance. It's vegan, paleo, and keto-friendly.

Dealing with moisture problems in your crawlspace? Call Charlotte's most trusted moisture control specialist, Freedom Crawlspace Services (803 493-9902), for inspection.Visit https://freedomcrawlspaceservices.com/services/crawl-space-moisture-control/ to learn more. Freedom Crawlspace Services City: Charlotte Address: 6135 Park S Dr suite 510 Website https://freedomcrawlspaceservices.com/ Phone +1-803-493-9902 Email owners@freedomcrawlspaceservices.com

Part 12 of "Building a church on the inside." There are characteristics that we need to gain. To remain faithful and strive for holiness. It's important that we have good character. These are just a few of the traits we should all add to ourselves.

Today, Casey Merrell, Owner of Midwest Placenta Encapsulation & U Cord Keepsakes, joins me on the podcast. Casey is one of those individuals that you can't help but smile when you are around her as her joy and enthusiasm shines through in everything that she does. This homeschooling mom of 4 has a passion to not only teach her family but to support and love on women who are navigating their post-partum health journeys. After researching and struggling to find a good option for placenta encapsulation for her own post-partum journey, she determined to figure out for herself and as all good things it has grown and blossomed into a business that she could have never imagined. This topic is unique and may not fit everyone's journey but is a fascinating option for those looking for natural ways to support their bodies and healing after having their baby.  Casey is knowledgeable and passionate about this topic and shares a lot of great information on the podcast, but has even more information about this topic on her website, which is linked below. Please listen, like, and share to support the mission of Embrace. Live. Thrive. to destigmatize mental health issues in motherhood and educate women on healthy living. Ways to Find Casey: Website: Midwest Placenta Encapsulation – Encapsulating Since 2015. Certified Placenta Encapsulator. Local Services to St. Louis, St. Charles, Lincoln, & Warren Counties in Missouri. Nationwide Shipping Program.FB: FacebookInstagram: Midwest Placenta Encapsulation (@midwest_placenta_encapsulation) • Instagram photos and videosTik Tok:Midwest Placenta Encapsulation (@midwestplacenta) | TikTokWays to Find Embrace. Live. Thrive.:Website: Embrace, Live, Thrive! (embracelivethrive.com)FB: (1) Embrace, Live, Thrive | FacebookInstagram: Sarah Meyer (@embrace.live.thrive) • Instagram photos and videosCasey Bio: My name is Casey and I'm located in Wentzville, Missouri. I've been encapsulating placentas since 2015. A little back story… I started researching placenta encapsulation when I was first pregnant with my son in 2015, but it was hard to find someone in my area who did placenta encapsulation (at that time I lived in rural mid-missouri). Therefore, I researched how to do it myself, I checked out a few books, I read a million blogs (at least it feels like it), watched hours of video tutorials, etc. I bought all the needed supplies (empty capsules, pill/capsule press machine, nutrabullet, dehydrator, stainless steel pot, etc.) and once my son was born, I encapsulated his placenta right away and I was astounded by the effects. Throughout the next few weeks, I could literally tell a difference in my mood and energy level when I forgot to take the capsules. Then, I was hooked. I started telling every pregnant friend and family member about it! Since I was telling everyone about it… people started asking me to do it for them. So, I casually encapsulated placentas for a friends and family members over a few years, and then again for myself when my daughter was born in 2017. Since opening, I encapsulated over 400 placentas for so many lovely mamas from all walks of motherhood. Other than that, I'm a stay-at-home mom with four ‘littles' and a super supportive husband. I truly love anything to do with pregnancy, labor, birth, cloth diapering, baby wearing, houseplants, and of course placenta encapsulation. I'll be thrilled to work with you if you move forward with placenta encapsulation.

Why is encapsulation good?

Are you worried that moisture in the crawlspace of your home might cause problems down the line? Then have it encapsulated by the experts at Freedom Crawlspace Services (803-493-9902) in Charlotte! Go to https://freedomcrawlspaceservices.com to find out more. Freedom Crawlspace Services 6135 Park S Dr suite 510, Charlotte, NC 28210, United States Website https://freedomcrawlspaceservices.com/ Phone +1-803-493-9902 Email owners@freedomcrawlspaceservices.com

Episode 93! Adam is having a well deserved break this week, so Lachlan Blunt joins us again to chat over some cardboard. We cover- Man cave update- slabd.com.au encapsulation service- Joel Butler listener question- NBA Draft- Offseason moves; how will these moves move the hobby needle over the next 12 months?Reach out to us on socials and tell us what we got right or wrong!Instagram: youcantcompthisTwitter @youcantcompthisGmail youcantcompthis@gmail.comFacebook: https://www.facebook.com/groups/youcantcompthisThankyou to our sponsor EJ Cards www.ejcards.com.auPodcast Links:Spotify: https://open.spotify.com/show/70w10XxmGviovd5T0LUFFcApple: https://podcasts.apple.com/au/podcast/you-cant-comp-this-nba-trading-card-podcast/id1598789687?fbclid=IwAR3taqOe4CMeRixgTkmDIWcMSscwDYZ0F_XRJyR1H1558KMs_J0L_NDuPsY

آموزش مبانی برنامه نویسی شی گرا - بخش 3 - مثال کاربردی این ویدیو سومین بخش از یک سری آموزش سه قسمتی هست که به معرفی مبانی اولیه برنامه نویسی شی گرا میپردازه.در این ویدئو با معرفی یک مثال شبه واقعی، اقدام به طراحی نرم افزار به صورت شی گرا، پیاده سازی طراحی ارائه شده و مقایسه این پیاده سازی با پیاده سازی غیر شی گرا کردملینک بخش اول:https://www.youtube.com/watch?v=5qwZJIsgd6Qلینک بخش دوم:https://www.youtube.com/watch?v=RVSuXUodOywهدف این سری آموزش ها، آشنایی اولیه و ایجاد بستر فکری مناسب برای شروع آموزش مباحث تکمیلی برنامه نویسی می باشد. مباحثی مثلProgramming principles و Design Pattersو ...در ویدیو اول به تشریح مفاهیم اولیه و اجزای اصلی یک سیستم شی گرا پرداختم و درویدیو دوم به کمک مثال هایی عملی به تشریح ارکان اساسی برنامه نویسی شی گرا پرداختم:EncapsulationAbstractionInheritancePolymorphismشروع (0:00)معرفی مساله (0:55)طراحی شی گرا (2:06)پیاده سازی شی گرا (6:13)Abstraction (15:23)Encapsulation (16:23)Encapsulation (16:53)Polymorphism (17:39)پیاده سازی غیر شی گرا (19:02)جمع بندی، معرفی کتاب و قدم های بعدی (25:16)پایان (27:38)---------------------------------------------------------------لینک کانال در سایر شبکه های اجتماعیYouTube:https://www.youtube.com/c/Ardiland1---------------------------------------------------------------Telegram:https://t.me/ardiland_tm---------------------------------------------------------------Instagram:https://www.instagram.com/ardiland_ig/---------------------------------------------------------------Twitter:https://twitter.com/Ardiland3---------------------------------------------------------------GitHub:https://github.com/ardalanebrahimi---------------------------------------------------------------LinkedIn:https://www.linkedin.com/in/ardalan-ebrahimi---------------------------------------------------------------

Dr. Kathleen Kendall-Tackett is a health psychologist and International Board-Certified Lactation Consultant, and the CEO of Praeclarus Press, a small press specializing in women's health. Dr. Kendall-Tackett is Editor-in-Chief of the journal, Psychological Trauma and was Founding Editor-in-Chief of Clinical Lactation. Dr. Kendall-Tackett specializes in women's-health research including breastfeeding, depression, trauma, and health psychology, and has won many awards for her work including the 2019 President's Award for Outstanding Contributions to the Field of Trauma Psychology from the American Psychological Association. Dr. Kendall-Tackett has authored more than 490 articles or chapters and is author or editor of 41 books. Her most recent books include Breastfeeding Doesn't Need to Suck (2022) and Women's Mental Health Across the Lifespan (2017). Her 41st book, Depression in New Mothers, 4th Edition is in press.Dr Kendall Tackett discusses with us not only a vast range of topics specific to her work and new book but also some big and confronting topics in this episode.   A warning: Dr Kendall-Tackett discusses early in the podcast about her research and work with women who have experienced sexual assault. In this episode we delve in to:Postnatal anxiety and guilt The power of oxytocin, a mother's “Spidey senses” and the vulnerability during the early daysSleep, mental health and breastfeedingPostpartum depression Placenta encapsulation and it's potential effects on milk supply. Secondary trauma in midwives and doulas and birth partners Burn out in midwives - shift based vs continuity of carer model How Adverse childhood experiences (ACE) affects adult health How women who have experienced sexual abuse prefer to engage with breastfeeding and what the research is showing.  LINKS :Course Burnout among perinatal workers Book Breastfeeding doesn't need to suck: how to nurture your baby and your mental health  Dr Kendall-Tackett website   Dr Kendall-Tackett mentions her work with Kerstin Uvnäs Moberg  Secondary Traumatic Stress and Moral Injury in Maternity Care Providers: A Narrative and Exploratory ReviewSurvivor moms companionSupport the show Produced and edited by Katie James - Support the show via our Patreon page or at BuyMeACoffee Music Joseph McDade Like this podcast? Then head over to leave us a review here Want more from Katie and Rachel? Katie's website with links to courses and moreRachel's website with links to courses, blogs, books and the collective

CME credits: 1.25 Valid until: 19-12-2023 Claim your CME credit at https://reachmd.com/programs/cme/protecting-insulin-producing-cells-after-transplantation-immunosuppression-and-encapsulation/14640/ This program is designed to increase knowledge of current disease management strategies for severe hypoglycemia and impaired awareness of hypoglycemia (IAH) and create awareness on the emerging stem cell-based treatments for patients with type 1 diabetes (T1D).

CME credits: 1.25 Valid until: 19-12-2023 Claim your CME credit at https://reachmd.com/programs/cme/advances-in-immune-tolerance-induction-and-islet-encapsulation-new-hope-for-t1d/14642/ This program is designed to increase knowledge of current disease management strategies for severe hypoglycemia and impaired awareness of hypoglycemia (IAH) and create awareness on the emerging stem cell-based treatments for patients with type 1 diabetes (T1D).

Episode: 2808 Plastic encapsulation of microchips, protection from environment and loads.  Today, the encapsulation story.

John Ousterhout, professor of computer science at Stanford University, joined SE Radio host Jeff Doolittle for a conversation about his book, A Philosophy of Software Design. They discussed the history and ongoing challenges of software system design, especially the nature of complexity and the difficulties handling it. The conversation also explored various design concepts from the book, such as modularity, layering, abstraction, information hiding, maintainability, and readability.

As many of you know, I consistently have signing events going on for people to send in whatever items they want to be autographed, but without a doubt, the most common items that comes in are trading cards. Along with those cards also comes the common question, "How do I get these graded and slabbed by PSA?"Well, today we are going to tackle that exact question. I am going to show you exactly what you need to do online to get your cards submitted to PSA for grading and put into a slab. It is super easy, so just follow along and you will be ready to go in no time at all!Website: https://www.powerssportsmemorabilia.comInstagram: https://www.instagram.com/powersautographsFacebook: https://www.facebook.com/PowersCollectiblesTwitter: https://twitter.com/powerscoPodcast: https://powerssportsmemorabilia.buzzsprout.com/Text PSM to +1 (878) 217-8574 for texts on our latest drops!On your cell? Click this link to sign up → https://tinyurl.com/bdcv6mj5Want 20% off Sports Card Investors Market Movers software program?  Use my affiliate link below and code POWERS20https://www.sportscardinvestor.com/plans/?ref=49Need jerseys or photos for my upcoming autograph signings?  Fanatics has you covered.  Affiliate link below.If you choose to purchase anything from the above links, please know I may receive a small commission.  Only buy if you will truly use it and it fits into your budget.https://fanatics.ncw6.net/vnN0yj0:00 Today's Topic1:36 Create An Account1:45 Trading Card Slab Submission2:19 Fill Out A Form3:10 Price Check5:00 2nd Page Of Submission Form5:58 Calculate Shipping7:28 Full Service Slab Submission12:15 Print Papers#sportscards #psa10 #psagrading

Placenta encapsulation is the procedure of taking a placenta and making it into pill form for consumption usually following birth. Placenta encapsulation has gained popularity in the past decade as a remedy to aid and assist with postpartum depresssion, lactation, and overall health and well-being following childbirth.   Encapsulation is not the only form of placenta ingestion utlized, but has become the most common.  In this episode, we review the practices that are associated, the rational and the safety.    Our practice website can be found at: Maternal Resources: https://www.maternalresources.org/ Remember to subscribe wherever you get your podcasts.  Please consider leaving us a review on iTunes Our Social Channels are as follows Twitter: https://twitter.com/integrativeob YouTube: https://www.youtube.com/maternalresources IG: https://www.instagram.com/integrativeobgyn/ Facebook: https://www.facebook.com/IntegrativeOB Our practice website can be found at: Maternal Resources: https://www.maternalresources.org/ Remember to subscribe wherever you get your podcasts.  Please consider leaving us a review on iTunes Our Social Channels are as follows Twitter: https://twitter.com/integrativeob YouTube: https://www.youtube.com/maternalresources IG: https://www.instagram.com/integrativeobgyn/ Facebook: https://www.facebook.com/IntegrativeOB  

In episode 23 of 2022, chemists Gloria & Victoria dive into important topics that don't quite fill out a whole episode - what is up with azelaic acid derivatives and encapsulation?

In this episode we are going to look at Data Encapsulation.We will be discussing Segmenting Messages, Sequencing, Protocol Data Units, Encapsulation Example, and an De-encapsulation Example.Thank you so much for listening to this episode of my series on Introduction to Networks for the Cisco Certified Network Associate (CCNA).Once again, I'm Kevin and this is KevTechify. Let's get this adventure started.All my details and contact information can be found on my website, https://KevTechify.com-------------------------------------------------------Cisco Certified Network Associate (CCNA)Introduction to Networks v1Episode 3 - Protocols and ModelsPart F - Data EncapsulationPodcast Number: 23-------------------------------------------------------Equipment I like.Home Lab ►► https://kit.co/KevTechify/home-labNetworking Tools ►► https://kit.co/KevTechify/networking-toolsStudio Equipment ►► https://kit.co/KevTechify/studio-equipment  

One reason this blog post and podcast series came about could likely be due to my meditation practice becoming stale and now provides an outlet for a somewhat more advanced level where details are dived into. If and when exploring this sutta on your own, it's recommended to drop the intricate, sometimes tedious language I go into here to the fullest extent possible. It's important to remember my intent here of placing plenty under a spiritual microscope to merely visit modes of deconstruction and analysis for study and (formal) practice possibilities, not as a general normalized mode of living. And while I go into minute details pertaining to this sutta please keep in mind it's likely more helpful not to keep considering this sutta in isolation but within the broader context of the Buddha's (other) teachings.

In this episode we are going to look at The Rules.We will be discussing Communications Fundamentals, Communication Protocols, Rule Establishment, Network Protocol Requirements, Message Encoding, Message Formatting and Encapsulation, Message Size, Message Timing, and Message Delivery Options.Thank you so much for listening to this episode of my series on Introduction to Networks for the Cisco Certified Network Associate (CCNA).Once again, I'm Kevin and this is KevTechify. Let's get this adventure started.All my details and contact information can be found on my website, https://KevTechify.com-------------------------------------------------------Cisco Certified Network Associate (CCNA)Introduction to Networks v1Episode 3 - Protocols and ModelsPart A - The RulesPodcast Number: 18-------------------------------------------------------Equipment I like.Home Lab ►► https://kit.co/KevTechify/home-labNetworking Tools ►► https://kit.co/KevTechify/networking-toolsStudio Equipment ►► https://kit.co/KevTechify/studio-equipment  

Dr. Luca Benatti is the CEO of EryDel, a biotech company developing and commercializing cell-therapy treatments for rare diseases using autologous red blood cell encapsulation technology to deliver drugs. With a focus on the rare genetic disease Ataxia Telangiectasia (AT), Erydel has just completed a multi-center, multi-national phase III trial for the disease. Their symptomatic treatment has been shown to delay the progression of the disease and could be part of a regular immunoglobulin therapy session for these patients. Luca explains, "The first characteristic of our technology since there are similar technologies that utilize red blood cells to deliver therapeutics, is that we are the only one that has developed a technology that can work at the bedside. So, it's really the only one that can use the patient's blood, and we don't need to have a centralized lab. The beauty of this technology is that it is the only one that can use a sustained release formulations technology - that is, the one that is actually being developed for Ataxia Telangiectasia - on which we have completed phase III study results." "So, from the time of blood withdrawal from the patients and for our lead product, we take 50 milliliters of blood from the patient, a small amount, and within a couple of hours, patients can go home. They are only required to stay for the blood withdrawal and the blood infusions. The rest of the process is done by a small machine that is fully automated and operated by trained personnel." #EryDel #AtaxiaTelangiectasia #EryDex #RareDisease #AT EryDel.com Download the transcript here

Dr. Luca Benatti is the CEO of EryDel, a biotech company developing and commercializing cell-therapy treatments for rare diseases using autologous red blood cell encapsulation technology to deliver drugs. With a focus on the rare genetic disease Ataxia Telangiectasia (AT), Erydel has just completed a multi-center, multi-national phase III trial for the disease. Their symptomatic treatment has been shown to delay the progression of the disease and could be part of a regular immunoglobulin therapy session for these patients. Luca explains, "The first characteristic of our technology since there are similar technologies that utilize red blood cells to deliver therapeutics, is that we are the only one that has developed a technology that can work at the bedside. So, it's really the only one that can use the patient's blood, and we don't need to have a centralized lab. The beauty of this technology is that it is the only one that can use a sustained release formulations technology - that is, the one that is actually being developed for Ataxia Telangiectasia - on which we have completed phase III study results." "So, from the time of blood withdrawal from the patients and for our lead product, we take 50 milliliters of blood from the patient, a small amount, and within a couple of hours, patients can go home. They are only required to stay for the blood withdrawal and the blood infusions. The rest of the process is done by a small machine that is fully automated and operated by trained personnel." #EryDel #AtaxiaTelangiectasia #EryDex #RareDisease #AT EryDel.com Listen to the podcast here

In today's episode I am chatting to Carly Lewis who is a placenta remedies specialist. Carly runs Prism placenta training and also chairs the PRN (Placenta Remedies Network).She shares with us the benefits of placenta encapsulation and talks about the wide variety of remedies that can be made from the placenta. She also answers some of the frequently asked questions that she gets from potential clients.You can find a placenta remedies specialist near you by searching - www.placentaremediesnetwork.orgIf you are interested in training with Carly her website is - www.prismplacentatraining.co.ukYou can follow her on Instagram - @doulafairy_placenta or @placentaremediesnetwork If you would like to buy a copy of the book that accompanies this podcast - click here:-Labour of Love - The Ultimate Guide to Being a Birth Partner — https://bit.ly/LabourofloveOr purchase a copy via my website - www.birthability.co.ukFollow me on Instagram @theultimatebirthpartner @birthabilityBook a 1-2-1 session with Sallyann  -  https://linktr.ee/SallyannBeresfordPlease remember that the information shared with you in this episode is solely based on my own personal experiences as a doula and the private opinions of my guest, based on her own training and experience as a placenta specialist.  Any recommendations made may not be suitable for all, so listeners must do their own research before making decisions.  

We're here to talk about the four pillars of Object Oriented Programming: Abstraction, Polymorphism, Inheritance, and Encapsulation. Ana shares some amazing news about her next piece of tech and we recommend a couple great resources you can use in your next project! Victor Recommends: https://readme.so/Ana Recommends: https://pocoloco.io/Ana Recommends this too for Linux Distribution: https://www.deepin.org/en/Website Victor mentioned: https://www.rockpaperfishandchips.com/Our Patreon: https://www.patreon.com/techheads  

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = T W I T T E R: https://twitter.com/adeasociety T I K T O K: https://www.tiktok.com/@adeasociety? Y O U T U B E: https://www.youtube.com/channel/UCX04NQ5j1beJqzMBOJrjjlg L I N K E D I N: https://www.linkedin.com/in/adeasociety/ P O D C A S T: https://anchor.fm/adeasociety = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = JOIN OUR COMMUNITY: https://www.subscribepage.com/adeasociety Sign up for for coming soon offline group of women in the Dallas Fort Worth, Texas area. This is a moment not a movement. This maybe how we met but it will not be how we interact for the foreseeable future.

We all are experiencing the change in era of Programming languages starting from Fortran, C, embedded C, C++,Java, .net etc we have 100+ Programming Languages starting from Procedural based to object oriented to script based languages .In this podcast I have covered the all three categories with a beautiful stories to make the concept clear for all newbies, non technical people. following concepts are covered as below Procedural Based (C and Embedded C Programming Language for IoT) OOPs Concepts Scripting Language with less syntax Please follow me on Instagram@ Podcasteramit for free workshops on Embedded C,Matlab, Python, R etc Check the oops features definition as mentioned below Abstraction is a process where you show only “relevant” data and “hide” unnecessary details of an object from the user. Encapsulation is the process of binding object state(fields) and behaviors(methods) together in a single entity called “Class”. Inheritance is a process of defining a new class based on an existing class by extending its common data members and methods. It is the concept where an object behaves differently in different situations.Since the object takes multiple forms, it is called Polymorphism. Follow me on Instagram @podcasteramit Listen the episode on all podcast platform and share your feedback as comments here Do check the episode on various platform follow me on instagram https://www.instagram.com/podcasteramit Apple https://podcasts.apple.com/us/podcast/id1544510362 Huhopper Platform https://hubhopper.com/podcast/tech-stories/318515 Amazon https://music.amazon.com/podcasts/2fdb5c45-2016-459e-ba6a-3cbae5a1fa4d Spotify https://open.spotify.com/show/2GhCrAjQuVMFYBq8GbLbwa

visit mindFULLme.org for resources just like this!

There are two words that get the blame more often than not when a problem cannot be rooted: the network! Today, along with special guest, Scott Lowe, we try to dig into what the network actually means. We discover, through our discussion that the network is, in fact, a distributed system. This means that each component of the network has a degree of independence and the complexity of them makes it difficult to understand the true state of the network. We also look at some of the fascinating parallels between networks and other systems, such as the configuration patterns for distributed systems. A large portion of the show deals with infrastructure and networks, but we also look at how developers understand networks. In a changing space, despite self-service becoming more common, there is still generally a poor understanding of networks from the developers’ vantage point. We also cover other network-related topics, such as the future of the network engineer’s role, transferability of their skills and other similarities between network problem-solving and development problem-solving. Tune in today! Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: Duffie Cooley Nicholas Lane Josh Rosso Key Points From This Episode: • The network is often confused with the server or other elements when there is a problem.• People forget that the network is a distributed system, which has independent routers.• The distributed pieces that make up a network could be standalone computers.• The parallels between routing protocols and configuration patterns for distributed systems.• There is not a model for eventually achieving consistent networks, particularly if they are old.• Most routing patterns have a time-sensitive mechanism where traffic can be re-dispersed.• Understanding a network is a distributed system gives insights into other ones, like Kubernetes.• Even from a developers’ perspective, there is a limited understanding of the network.• There are many overlaps between developers and infrastructural thinking about systems.• How can network engineers apply their skills across different systems?• As the future changes, understanding the systems and theories is crucial for network engineers.• There is a chasm between networking and development.• The same ‘primitive’ tools are still being used for software application layers.• An explanation of CSMACD, collisions and their applicability. • Examples of cloud native applications where the network does not work at all.• How Spanning Tree works and the problems that it solves.• The relationship between software-defined networking and the adoption of cloud native technologies.• Software-defined networking increases the ability to self-service.• With self-service on-prem solutions, there is still not a great deal of self-service. Quotes: “In reality, what we have are 10 or hundreds of devices with the state of the network as a system, distributed in little bitty pieces across all of these devices.” — @scott_lowe [0:03:11] “If you understand how a network is a distributed system and how these theories apply to a network, then you can extrapolate those concepts and apply them to something like Kubernetes or other distributed systems.” — @scott_lowe [0:14:05] “A lot of these software defined networking concepts are still seeing use in the modern clouds these days” — @scott_lowe [0:44:38] “The problems that we are trying to solve in networking are not different than the problems that you are trying to solve in applications.” — @mauilion [0:51:55] Links Mentioned in Today’s Episode: Scott Lowe on LinkedIn — https://www.linkedin.com/in/scottslowe/ Scott Lowe’s blog — https://blog.scottlowe.org/ Kafka — https://kafka.apache.org/ Redis — https://redis.io/ Raft — https://raft.github.io/ Packet Pushers — https://packetpushers.net/ AWS — https://aws.amazon.com/ Azure — https://azure.microsoft.com/en-us/ Martin Casado — http://yuba.stanford.edu/~casado/ Transcript: EPISODE 15 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [0:00:41.4] DC: Good afternoon everybody. In this episode, we’re going to talk about the network. My name is Duffie Cooley and I’ll be the lead of this episode and with me, I have Nick. [0:00:49.0] NL: Hey, what’s up everyone. [0:00:51.5] DC: And Josh. [0:00:52.5] JS: Hi. [0:00:53.6] DC: And Mr. Scott Lowe joining us as a guest speaker. [0:00:56.2] SL: Hey everyone. [0:00:57.6] DC: Welcome, Scott. [0:00:58.6] SL: Thank you. [0:01:00.5] DC: In this discussion, we’re going to try and stay away, like we do always, we’re going to try and stay away from particular products or solutions that are related to the problem. The goal of it is to really kind of dig in to like what the network means when we refer to it as it relates to like cloud native applications or just application design in general. One of the things that I’ve noticed over time and I’m curious, what you all think but like, one of the things I’ve done over time is that people are kind of the mind that if it can’t root cause a particular issue that they run into, they’re like, “That was the network.” Have you all seen that kind of stuff out there? [0:01:31.4] NL: Yes, absolutely. In my previous life, before being a Kubernetes architect, I actually used my networking and engineering degree to be a network administrator for the Boeing Company, under the Boeing Corporation. Time and time again, someone would come to me and say, “This isn’t working. The network is down.” And I’m like, “Is the network down or is the server down?” Because those are different things. Turns out it was usually the server. [0:01:58.5] SL: I used to tell my kids that they would come to me and they would say, the Internet is down and I would say, “Well, you know. I don’t think the entire Internet is down, I think it’s just our connection to the Internet.” [0:02:10.1] DC: Exactly. [0:02:11.7] JS: Dad, the entire global economy is just taking a total hit. [0:02:15.8] SL: Exactly, right. [0:02:17.2] DC: I frequently tell people that my first distributed system that I ever had a real understanding of was the network, you know? It’s interesting because it kind of like, relies on the premises that I think a good distributed system should in that there is some autonomy to each of the systems, right? They are dependent on each other or even are inter communicate with each other but fundamentally, like when you look at routers and things like that, they are autonomous in their own way. There’s work that they do exclusive to the work that others do and exclusive to their dependencies which I think is very interesting. [0:02:50.6] SL: I think the fact that the network is a distributed system and I’m glad you said that Duffie, I think the fact the network is a distributed system is what most people overlook when they start sort of blaming the network, right? Let’s face it, in the diagrams, right, the network’s always just this blob, right? Here’s the network, right? It’s this thing, this one singular thing. When in reality, what we have are like 10 or hundreds of devices with the state of the network as a system, distributed in little bitty pieces across all of these devices. And no way, aside from logging in to each one of these devices are we able to assemble what the overall state is, right? Even routing protocols mean, their entire purpose is to assemble some sort of common understanding of what the state of the network is. Melding together, not just IP addresses which are these abstract concept but physical addresses and physical connections. And trying to reason to make decisions about them, how we center across and it’s far more complex and a lot of people understand, I think that’s why it’s just like the network is down, right? When reality, it’s probably something else entirely. [0:03:58.1] DC: Yeah, absolutely. Another good point to bring up is that each of these distributed pieces of this distributed system are in themselves like basically like just a computer. A lot of times, I’ve talked to people and they were like, “Well, the router is something special.” And I’m like, “Not really. Technically, a Linux box could just be a router if you have enough ports that you plug into it. Or it could be a switch if you needed to, just plug in ports.” [0:04:24.4] NL: Another good interesting parallel there is like when we talk about like routing protocols which are a way of – a way that allow configuration changes to particular components within that distributed system to be known about by other components within that distributed system. I think there’s an interesting parallel here between the way that works and the way that configuration patterns that we have for distributed systems work, right? If you wanted to make a configuration only change to a set of applications that make up some distributed system, you might go about like leveraging Ansible or one of the many other configuration models for this. I think it’s interesting because it represents sort of an evolution of that same idea in that you’re making it so that each of the components is responsible for informing the other components of the change, rather than taking the outside approach of my job is to actually push a change that should be known about by all of these concepts, down to them. Really, it’s an interesting parallel. What do you all think of that? [0:05:22.2] SL: I don’t know, I’m not sure. I’d have to process that for a bit. But I mean, are you saying like the interesting thought here is that in contrast to typical systems management where we push configuration out to something, using a tool like an Ansible, whatever, these things are talking amongst themselves to determine state? [0:05:41.4] DC: Yeah, it’s like, there are patterns for this like inside of distributed systems today, things like Kafka and you know, Kafka and Gossip protocol, stuff like this actually allows all of the components of a particular distributed system to understand the common state or things that would be shared across them and if you think about them, they’re not all that different from a routing protocol, right? Like the goal being that you give the systems the ability to inform the other systems in some distributed system of the changes that they may have to react to. Another good example of this one, which I think is interesting is like, what they call – when you have a feature behind a flag, right? You might have some distributed configuration model, like a Redis cache or database somewhere that you’ve actually – that you’ve held the running configuration of this distributed system. And when you want to turn on this particular feature flag, you want all of the components that are associated with that feature flag to enable that new capability. Some of the patterns for that are pretty darn close to the way that routing protocol models work. [0:06:44.6] SL: Yeah, I see what you're saying. Actually, that’ makes a lot of sense. I mean, if we think about things like Gossip protocols or even consensus protocols like Raft, right? They are similar to routing protocols in that they are responsible for distributing state and then coming to an agreement on what that state is across the entire system. And we even apply terms like convergence to both environments like we talk about how long it takes routing protocol to converge. And we might also talk about how long it takes for and ETCD cluster to converge after changing the number of members in the cluster of that nature. The point at which everybody in that distributed system, whether it be the network ETCD or some other system comes to the same understanding of what that shared state is. [0:07:33.1] DC: Yeah, I think that’s a perfect breakdown, honestly. Pretty much every routing technology that’s out there. You know, if you’re taking that – the computer of the network, you know, it takes a while but eventually, everyone will reconcile the fact that, “Yeah, that node is gone now.” [0:07:47.5] NL: I think one thing that’s interesting and I don’t know how much of a parallel there is in this one but like as we consider these systems like with modern systems that we’re building at scale, frequently we can make use of things like eventual consistency in which it’s not required per se for a transaction to be persisted across all of the components that it would affect immediately. Just that they eventually converge, right? Whereas with the network, not so much, right? The network needs to be right now and every time and there’s not really a model for eventually consistent networks, right? [0:08:19.9] SL: I don’t know. I would contend that there is a model for eventually consistent networks, right? Certainly not on you know, most organizations, relatively simple, local area networks, right? But even if we were to take it and look at something like a Clos fabric, right, where we have top of rack switches and this is getting too deep for none networking blokes that we know, right? Where you take top of rack switches that are talking layer to the servers below them or the end point below them. And they’re talking layer three across a multi-link piece up to the top, right? To the spine switches, so you have leaf switches, talking up spine switches, they’re going to have multiple uplinks. If one of those uplinks goes down, it doesn’t really matter if the rest off that fabric knows that that link is down because we have the SQL cost multi pathing going across that one, right? In a situation like that, that fabric is eventually consistent in that it’s okay if you know, knee dropping link number one of leaf A up to spine A is down and the rest of the system doesn’t know about that yet. But, on the other hand, if you are looking at network designs where convergence is being handled on active standby links or something of that nature or there aren’t enough paths to get from point A to point B until convergence happens then yes, you’re right. I think it kind of comes down to network design and the underlying architecture and there are so many factors that affect that and so many designs over the years that it’s hard to – I would agree and from the perspective of like if you have an older network and it’s been around for some period of time, right? You probably have one that is not going to be tolerant, a link being down like it will cause problems. [0:09:58.4] NL: Adds another really great parallel in software development, I think. Another great example of that, right? If we consider for a minute like the circuit breaking pattern or even like you know, most load balancer patterns, right? In which you have some way of understanding a list of healthy end points behind the load balancer and were able to react when certain end points are no longer available. I don’t consider that a pattern that I would relate to specifically if they consent to eventual consistency. I feel like that still has to be immediate, right? We have to be able to not send the new transaction to the dead thing. That has to stop immediately, right? It does in most routing patterns that are described by multi path, there is a very time sensitive mechanism that allows for the re-dispersal of that traffic across known paths that are still good. And the work, the amazing amount of work that protocol architects and network engineers go through to understand just exactly how the behavior of those systems will work. Such that we don’t see traffic. Black hole in the network for a period of time, right? If we don’t send traffic to the trash when we know or we have for a period of time, while things converge is really has a lot going for it. [0:11:07.0] SL: Yeah, I would agree. I think the interesting thing about discussing eventual consistency with regards to the networking is that even if we take a relatively simple model like the DOD model where we only have four layers to contend with, right? We don’t have to go all the way to this seven-layer OSI model. But even if we take a simple layer like the DOD four-layer model, we could be talking about the rapid response of a device connected at layer two but the less than rapid response of something operating at layer three or layer four, right? In the case of a network where we have these discreet layers that are intentionally loosely coupled which is another topic, we could talk about from a distribution perspective, right? We have these layers that are intentionally loosely coupled, we might even see consistency and the application of the cap theorem, behave differently at different layers of their model. [0:12:04.4] DC: That’s right. I think it’s fascinating like how much parallel there is here. As you get into like you know, deep architectures around software, you’re thinking of these things as it relates to like these distributed systems, especially as you’re moving toward more cloud native systems in which you start employing things like control theory and thinking about the behaviours of those systems both in aggregate like you know, some component of my application, can I scale this particular component horizontally or can I not, how am I handling state. So many of those things have parallels to the network that I feel like it kind of highlights I’m sure what everybody has heard a million times, you know, that there’s nothing new under the sun. There’s million things that we could learn from things that we’ve done in the past. [0:12:47.0] NL: Yeah, totally agree. I recently have been getting more and more development practice and something that I do sometimes is like draw out like how all of my functions and my methods, and take that in rack with each other across a consisting code base and lo and behold when I draw everything out, it sure does look a lot like a network diagram. All these things have to flow together in a very specific way and you expect the kind of returns that you’re looking for. It looks exactly the same, it’s kind of the – you know, how an atom kind of looks like a galaxy from our diagram? All these things are extrapolated across like – [0:13:23.4] SL: Yeah, totally. [0:13:24.3] NL: Different models. Or an atom looks like a solar system which looks like a galaxy. [0:13:28.8] SL: Nicholas, you said your network administrator at Boeing? [0:13:30.9] NL: I was, I was a network engineer at Boeing. [0:13:34.0] SL: You know, as you were sitting there talking, Duffie, so, I thought back to you Nick, I think all the times, I have a personal passion for helping people continue to grow and evolve in their career and not being stuck. I talk to a lot of networking folks, probably dating because of my involvement, back in the NSX team, right? But folks being like, “I’m just a network engineer, there’s so much for me to learn if I have to go learn Kubernetes, I wouldn’t even know where to start.” This discussion to me underscores the fact that if you understand how a network is a distributed system and how these theories apply to a network, then you can extrapolate those concepts and apply them to something like Kubernetes or other distributed systems, right? Immediately begin to understand, okay. Well, you know, this is how these pieces talk to each other, this is how they come, the consensus, this is where the state is stored, this is how they understand and exchange date, I got this. [0:14:33.9] NL: if you want to go down that that path, the controlled plane of your cluster is just like your central routing back bone and then the kublets themselves are just your edge switches going to each of your individual smaller network and then the pods themselves have been nodes inside of the network, right? You can easily – look at that, holy crap, it looks exactly the same. [0:14:54.5] SL: Yeah, that’s a good point. [0:14:55.1] DC: I mean, another interesting part, when you think about how we characterize systems, like where we learn that, where that skillset comes from. You raise a very good point. I think it’s an easier – maybe slightly easier thing to learn inside of networking, how to characterize that particular distributed system because of the way the components themselves are laid out and in such a common way. Where when we start looking at different applications, we find a myriad of different patterns with particular components that may behave slightly differently depending, right? Like there are different patterns within software like almost on per application bases whereas like with networks, they’re pretty consistently applied, right? Every once in a while, they’ll be kind of like a new pattern that emerges, that it just changes the behavior a little bit, right? Or changes the behavior like a lot but at the same time, consistently across all of those things that we call data center networks or what have you. To learn to troubleshoot though, I think the key part of this is to be able to spend the time and the effort to actually understand that system and you know, whether you light that fire with networking or whether you light that fire with like just understanding how to operationalize applications or even just developing and architecting them, all of those things come into play I think. [0:16:08.2] NL: I agree. I’m actually kind of curious, the three of us have been talking quite a bit about networking from the perspective that we have which is more infrastructure focused. But Josh, you have more of a developer focused background, what’s your interaction and understanding of the network and how it plays? [0:16:24.1] JS: Yeah, I’ve always been a consumer of the network. It’s something that is sat behind an API and some library, right? I call out to something that makes a TCP connection or an http interaction and then things just happen. I think what’s really interesting hearing talk and especially the point about network engineers getting into thee distributed system space is that I really think that as we started to put infrastructure behind API’s and made it more and more accessible to people like myself, app developers and programmers, we started – by we, you know, I’m obviously generalizing here. But we started owning more and more of the infrastructure. When I go into teams that are doing big Kubernetes deployments, it’s pretty rare, that’s the conventional infrastructure and networking teams that are standing up distributed systems, Kubernetes or not, right? It's a lot of times, a bunch of app developers who have maybe what we call dev-ops, whatever that means but they have an application development background, they understand how they interact with API’s, how to write code that respects or interacts with their infrastructure and they’re standing up these systems and I think one of the gaps of that really creates is a lot of people including myself just hearing you all talk, we don’t understand networking at that level. When stuff falls over and it’s either truly the network or it’s getting blamed on the network, it’s often times, just because we truly don’t understand a lot of these things, right? Encapsulation, meshes, whatever it might be, we just don’t understand these concepts at a deep level and I think if we had a lot more people with network engineering backgrounds, shifting into the distributed system space. It would alleviate a bit of that, right? Bringing more understanding into the space that we work in nowadays. [0:18:05.4] DC: I wonder if maybe it also would be a benefit to have like more cross discussions like this one between developers and infrastructure kind of focused people, because we’re starting to see like as we’re crossing boundaries, we see that the same things that we’re doing on the infrastructure side, you’re also doing in the developer side. Like cap theorem as Scott mention which is the idea that you can have two out of three of consistency, availability and partitioning. That also applies to networking in a lot of ways. You can only have a network that is either like consistent or available but it can’t handle partitioning. It can be a consistent to handle partitioning but it’s not always going to be available, that sort of thing. These things that apply in from the software perspective also apply to us but we think about them as being so completely different. [0:18:52.5] JS: Yeah, I totally agree. I really think like on the app side, a couple of years ago, you know, I really just didn’t care anything outside of the JVM like my stuff on the JVM and if it got out to the network layer of the host like just didn’t care, know, need to know about that at all. But ever since cloud computing and distributed systems and everything became more prevalent, the overlap has become extremely obvious, right? In all these different concepts and it’s been really interesting to try to ramp up on that. [0:19:19.6]:19.3] NNL: Yeah, I think you know Scott and I both do this. I think as I imagine, actually, this is true of all four of us to be honest. But I think that it’s really interesting when you are out there talking to people who do feel like they’re stuck in some particular role like they’re specialists in some particular area and we end up having the same discussion with them over and over again. You know, like, “Look, that may pay the bills right now but it’s not going to pay the bills in the future.” And so you know, the question becomes, how can you, as a network engineer take your skills forward and not feel as though you’re just going to have to like learn everything all over again. I think that one of the things that network engineers are pretty decent at is characterizing those systems and being able to troubleshoot them and being able to do it right now and being able to like firefight those capabilities and those skills are incredibly valuable in the software development and in operationalizing applications and in SRE models. I mean, all of those skills transfer, you know? If you’re out there and you’re listening and you feel like I will always be a network engineer, consider that you could actually take those skills forward into some other role if you chose to. [0:20:25.1] JS: Yeah, totally agree. I mean, look at me, the lofty career that I’ve been come to. [0:20:31.4] SL: You know, I would also say that the fascinating thing to me and one of the reasons I launched, I don’t say this to like try and plug it but just as a way of talking about the reason I launched my own podcast which is now part of packet pushers, was exploring this very space and that is like we’ve got folks like Josh who comes from the application development spacing is now being, you know, in a way, forced to own and understand more infrastructure and we’ve got the infrastructure folks who now in a way, whether it be through the rise of cloud computing and abstractions away from visible items are being forced kind of up the stack and so they’re coming together and this idea of what does the future of the folks that are kind of like in our space, what does that look like? How much longer does a network engineer really need to be deeply versed in all the different layers? Because everything’s been abstracted away by some other type of thing whether it’s VPC’s or Azure V Nets or whatever the case is, right? I mean, you’ve got companies bringing the VPC model to on premises networks, right? As API’s become more prevalent, as everything gets sort of abstracted away, what does the future look like, what are the most important skills and it seems to me that it’s these concepts that we’re talking about, right? This idea of distributed systems and how distributed systems behave and how the components react to one another and understanding things like the cap theorem that are going to be most applicable rather than the details of trouble shooting VGP or understanding AWS VPC’s or whatever the case may be. [0:22:08.5] NL: I think there is always going to be a place for the people who know how things are running under the hood from like a physical layer perspective, that sort of thing, there’s always going to be the need for the grave beards, right? Even in software development, we still have the people who are slinging kernel code in C. And you know, they’re the best, we salute you but that is not something that I’m interested in it for sure. We always need someone there to pick up the pieces as it were. I think that yeah, having just being like, I’m a Cisco guy, I’m a Juniper guy, you know? I know how to pawn that or RSH into the switch and execute these commands and suddenly I’ve got this port is now you know, trunk to this V neck crap, I was like, Nick, remember your training, you know? How to issue those commands, I wonder, I think that that isn’t necessarily going away but it will be less in demand in the future. [0:22:08.5] SL: I’m curious to hear Josh’s perspective as like having to own more and more of the infrastructure underneath like what seems to be the right path forward for those folks? [0:23:08.7] JS: Yeah, I mean, unfortunately, I feel like a lot of times, it just ends up being trial by fire and it probably shouldn’t be that. But the amount of times that I have seen a deployment of some technology fall over because we overlapped the site range or something like that is crazy. Because we just didn’t think about it or really understand it that well. You know, like using one protocol, you just described BGP. I never ever dreamt of what BGP was until I started using attributed systems, right? Started using BGP as a way to communicate routes and the amount off times that I’ve messed up that connection because I don’t have a background in how to set that up appropriately, it’s been rough. I guess my perspective is that the technology has gotten better overall and I’m mostly obviously in the Kubernetes space, speaking to the technologies around a lot of the container networking solutions but I’m sure this is true overall. It seems like a lot of the sharp edges have been buffed out quite a bit and I have less of an opportunity to do things terribly wrong. I’ve also noticed for what it’s worth, a lot of folks that have my kind of background or going out to like the AWS is the Azure’s of the world. They’re using all these like, abstracted networking technologies that allow t hem to do really cool stuff without really having to understand how it works and they’re often times going back to their networking team on prem when they have on prem requirements and being like it should be this easy or XY and Z and they’re almost like pushing the networking team to modernize that and make things simpler. Based on experiences they’re having with these cloud providers. [0:24:44.2] DC: Yeah, what do you mean I can’t create a load balancer that crosses between these two disparate data centers as it easily is. Just issuing a single command. Doesn’t this just exist from a networking standpoint? Even just the idea that you can issue an API command and get a load balancer, just that idea alone, the thousands of times I have heard that request in my career. [0:25:08.8] JS: And like the actual work under the hood to get that to work properly is it’s a lot, there’s a lot of stuff going on. [0:25:16.5] SL: Absolutely, yeah, [0:25:17.5] DC: Especially when you’re into plumbing, you know? If you’re going to create a load balancer with API, well then, what API does the load balancer use to understand where to send that traffic when it’s being balanced. How do you handle discovery, how do you hit like – obviously, yeah, there’s no shortage on the amount of work there. [0:25:36.0] JS: Yeah. [0:25:36.3] DC: That’s a really good point, I mean, I think sometimes it’s easy for me to think about some of these API driven networking models and the cost that come with them, the hidden cost that come with them. An example of this is, if you’re in AWS and you have a connectivity between wo availability, actually could be any cloud, it doesn’t have to be an AWS, right? If you have connectivity between two different availability zones and you’re relying on that to be reliable and consistent and definitely not to experience, what tools do you have at your disposal, what guarantees do you have that that network has even operating in a way that is responsive, right? And in a way, this is kind of taking us towards the observability conversation that I think we’ve talked a little bit about the past. Because I think it highlights the same set of problems again, right? You have to understand, you have to be able to provide the consumers of any service, whether that service is plumbing, whether it’s networking, whether it’s your application that you’ve developed that represents a set of micro service. You have to provide everybody a way or you know, have to provide the people who are going to answer the phone at two in the morning. Or even the robots that are going to answer the phone at two in the morning. I have to provide them some mechanism by which to observe those systems as they are in use. [0:26:51.7] JS: I’m not convinced that very many of the cloud providers do that terribly well today, you know? I feel like I’ve been burned in the past without actually having an understanding of the state that we’re in and so it is interesting maybe the software development team can actually start pushing that down toward the networking vendors out there out in the world. [0:27:09.9] NL: Yeah that would be great. I mean I have been recently using a managed Kubernetes service. I have been kicking the tires on it a little bit. And yeah there has been a couple of times where I had just been got by networking issues. I am not going to get into what I have seen in a container network interface or any of the technologies around that. We are going to talk about that another time. But the CNI that I am using in this managed service was just so wonky and weird. And it was failing from a network standpoint. The actual network was failing in a sense because the IP addresses for the nodes themselves or the pods wasn’t being released properly and because of our bag. And so, the rules associated with my account could not remove IP addresses from a node in the network because it wasn’t allowed to and so from a network, I ran out of IP addresses in my very small site there. [0:28:02.1] SL: And this could happen in database, right? This could happen in a cache of information, this could happen in pretty much the same pattern that you are describing is absolutely relevant in both of these fields, right? And that is a fascinating thing about this is that you know we talk about the network generally in these nebulous terms and that it is like a black box and I don’t want them to know anything about it. I want to learn about it, I don’t want to understand it. I just want to be able to consume it via an API and I want to have the expectation that everything will work the way it is supposed to. I think it is fascinating that on the other side of that API are people maybe just like you who are doing their level best to provide, to chase the cap theorum into it’s happy end and figure out how to actually give you what you need out of that service, you know? So, empathy I think is important. [0:28:50.4] NL: Absolutely, to bring that to an interesting thought that I just had where on both sides of this chasm or whatever it is between networking and develop, the same principles exists like we have been saying but just to elicited on it a little bit more, it’s like on one side you have like I need to make sure that these ETCD nodes communicate with each other and that the data is consistent across the other ones. So, we use a protocol called RAFT, right? And so that’s eventually existent tool then that information is sent onto a network, which is probably using OSPF, which is “open shortest path first” routing protocol to become eventually consistent on the data getting from one point to the other by opening the shortest path possible. And so these two things are very similar. They are both these communication protocols, which is I mean that is what protocol means, right? The center for communication but they’re just so many different layers. Obviously of the OSI model but people don’t put them together but they really are and we keep coming back to that where it is all the same thing but we think about it so differently. And I am actually really appreciating this conversation because now I am having a galaxy brain moment like boo. [0:30:01.1] SL: Another really interesting one like another galaxy moment, I think that is interesting is if you think about – so let us break them down like TCP and UTP. These are interesting patterns that actually do totally relate again just in software patterns, right? In TCP the guarantee is that every data gram, if you didn’t get the entire data gram you will understand that you are missing data and you will request a new version of that same packet. And so, you can provide consistency in the form of retries or repeats if things don’t work, right? Not dissimilar from the ability to understand like that whether you chuck some in data across the network or like in a particular data base, if you make a query for a bunch of information you have to have some way of understanding that you got the most recent version of it, right? Or ETCD supports us by using the revision by understanding what revision you received last or whether that is the most recent one. And other software patterns kind of follow the same model and I think that is also kind of interesting. Like we are still using the same primitive tools to solve the same problems whether we are doing it at a software application layer or whether we are doing it down in the plumbing at the network there, these tools are still very similar. Another example is like UTP where it is basically there are no repeats. You either got the packet or you didn’t, which sounds a lot like an event stream to me in some ways, right? Like it is very interesting, you just figured out like I put in on the line, you didn’t get it? It is okay, I will put another line here in a minute you can react to that one, right? It is an interesting overlap. [0:31:30.6] NL: Yeah, totally. [0:31:32.9] JS: Yeah, the comparison to event streams or message queues, right? There is an interesting one that I hadn’t considered before but yeah, there are certainly parallels between saying, “Okay I am going to put this on the message queue,” and wait for the acknowledgement that somebody has taken it and taken ownership of it as oppose to an event stream where it is like this happened. I admit this event. If you get it and you do something with it, great. If you don’t get it then you don’t do something with it, great because another event is going to come along soon. So, there you go. [0:32:02.1] DC: Yep, I am going to go down a weird topic associated with what we are just talking about. But I am going to get a little bit more into the weeds of networking and this is actually directed into us in a way. So, talking about the kind of parallels between networking and development, in networking at least with TCP and networking, there is something called CSMACD, which is “carry your sense multi,” oh I can’t remember what the A stands for and the CD. [0:32:29.2] SL: Access. [0:32:29.8] DC: Multi access and then CD is collision detection and so basically what that means is whenever you sent out a packet on the network, the network device itself is listening on the network for any collisions and if it detects a collision it will refuse to send a packet until a certain period of time and they will do a retry to make sure that these packets are getting sent as efficiently as possible. There is an alternative to that called CMSCA, which was used by Mac before they switched over to using a Linux based operating system. And then putting a fancy UI in front of it, which collision avoidance would listen and try and – I can’t remember exactly, it would time it differently so that it would totally just avoid any chance that there could be collision. It would make sure that no packets were being sent right then and then send it back up. And so I was wondering if something like that exists in the realm between the communication path between applications. [0:33:22.5] JS: Is it collision two of the same packets being sent or what exactly is that? [0:33:26.9] DC: With the packets so basically any data going back and forth. [0:33:29.7] JS: What makes it a collision? [0:33:32.0] SL: It is the idea that you can only transmit one message at a time because if they both populate the same media it is trash, both of them are trash. [0:33:39.2] JS: And how do you qualify that. Do you receive an ac from the system or? [0:33:42.8] NL: No there is just nothing returned essentially so it is like literally like the electrical signals going down the wire. They physically collide with each other and then the signal breaks. [0:33:56.9] JS: Oh, I see, yeah, I am not sure. I think there is some parallels to that maybe with like queuing technologies and things like that but can’t think of anything on like direct app dev side. [0:34:08.6] DC: Okay, anyway sorry for that tangent. I just wanted to go down that little rabbit-hole a little bit. It was like while we are talking about networking, I was like, “Oh yeah, I wanted to see how deep down we can make this parallel going?” so that was the direction I went. [0:34:20.5] SL: Like where is that that CSMACD, a piece is like seriously old school, right? Because it only applied to half duplex Ethernet and as soon as we went to full duplex Ethernet it didn’t matter anymore. [0:34:33.7] DC: That is true. I totally forgot about that. [0:34:33.8] JS: It applied the satellite with all of these as well. [0:34:35.9] DC: Yeah, I totally forgot about that. Yeah and with full duplex, we totally just space on that. This is – damn Scott, way to make me feel old. [0:34:45.9] SL: Well I mean satellite stuff, too, right? I mean it is actually any shared media upon which you have to – where if this stuff goes and overlap there, you are not going to be able to make it work right? And so, I mean it is interesting. It is actually an interesting PNL. I am struggling to think of an example of this as well. I mean my brain is going towards circuit breaking but I don’t think that that is quite the same thing. It is sort the same thing that in a circuit breaking pattern, the application that is making the request has the ability obviously because it is the thing making the request to understand that the target it is trying to connect to is not working correctly. And so, it is able to make an almost instantaneous decision or at least a very shortly, a very timely decision about what to do when it detects that state. And so that’s a little similar and that you can and from the requester side you can do things if you see things going awry. And really and in reality, in the circuit breaking pattern we are making the assumption that only the application making the request will ever get that information fast enough to react to it. [0:35:51.8] JS: Yeah where my head was kind of going with it but I think it is pretty off is like on a low level piece of code like it is maybe something you write in C where you implement your own queue in that area and then multiple threads are firing off the same time and there is no block system or mechanism if two threads contend to put something in the same memory space that that queue represents. That is really going down the rabbit hole. I can’t even speak to what degree that is possible in modern programming but that is where my head was. [0:36:20.3] NL: Yeah that is a good point. [0:36:21.4] SL: Yeah, I think that is actually a pretty good analogy because the key commonality here is some sort of shared access, right? Multiple threads accessing the same stack or memory buffer. The other thing that came to mind to me was like some sort of session multiplexing, right? Where you are running multiple application layer sessions inside a single sort of network connection and those network sessions getting comingled in some fashion. Whether through identifiers or sequence number or something else of that nature and therefore, you know garbling the ultimate communication that is trying to be sent. [0:36:59.2] DC: Yeah, locks are exactly the right direction, I think. [0:37:03.6] NL: That is a very good point. [0:37:05.2] DC: Yeah, I think that makes perfect sense. Good, all right. Yes, we nailed it. [0:37:09.7] SL: Good job. [0:37:10.8] DC: Can anybody here think of a software pattern that maybe doesn’t come across that way? When you are thinking about some of the patterns that you see today in cloud native applications, is there a counter example, something that the network does not do at all? [0:37:24.1] NL: That is interesting. I am trying to think where event streams. No, that is just straight up packets. [0:37:30.7] JS: I feel like we should open up one of those old school Java books of like 9,000 design patterns you need to know and we should go one by one and be like, “What about this” you know? There is probably something I can’t think of it off the top of my head. [0:37:43.6] DC: Yeah me neither. I was trying to think of it. I mean like I can think of a myriad of things that do cross over even the idea of only locally relevant state, right? That is like a cam table on a switch that is only locally relevant because once you get outside of that switching domain it doesn’t matter anymore and it is like there is a ton of those things that totally do relate, you know? But I am really struggling to come up with one that doesn’t – One thing that is actually interesting is I was going to bring up – we mentioned the cap theorem and it is an interesting one that you can only pick like two and three of consistency availability and partition tolerance. And I think you know, when I think about the way that networks solve or try to address this problem, they do it in some pretty interesting way. It’s like if you were to consider like Spanning Tree, right? The idea that there can really only be one path through a series of broadcast domains. Because we have multiple paths then obviously we are going to get duplicity and the things are going to get bad because they are going to have packets that are addressed the same things across and you are going to have all kinds of bad behaviors, switching loops and broadcast storms and all kinds of stuff like that and so Spanning Tree came along and Spanning Tree was invented by an amazing woman engineer who created it to basically ensure that there was only one path through a set of broadcast domains. And in a way, this solved that camp through them because you are getting to the point where you said like since I understand that for availability purpose, I only need one path through the whole thing and so to ensure consistency, I am going to turn off the other paths and to allow for partition tolerance, I am going to enable the system to learn when one of those paths is no longer viable so that it can re-enable one of the other paths. Now the challenge of course is there is a transition period in which we lose traffic because we haven’t been able to open one of those other paths fast enough, right? And so, it is interesting to think about how the network is trying to solve with the part that same set of problems that is described by the cap theorem that we see people trying to solve with software routine. [0:39:44.9] SL: No man I totally agree. In a case like Spanning Tree, you are sacrificing availability essentially for consistency and partition tolerance when the network achieves consistency then availability will be restored and there is other ways to doing that. So as we move into systems like I mentioned clos fabrics earlier, you know a cost fabric is a different way of establishing a solution to that and that is saying I’d later too. I will have multiple connections. I will wait those connections using the higher-level protocol and I will sacrifice consistency in terms of how the routes are exchanged to get across that fabric in exchange for availability and partition columns. So, it is a different way of solving the same problem and using a different set of tools to do that, right? [0:40:34.7] DC: I personally find it funny that in the cap theorem there is at no point do we mention complexity, right? We are just trying to get all three and we don’t care if it’s complex. But at the same time, as a consumer of all of these systems, you care a lot about the complexity. I hear it all the time. Whether that complexity is in a way that the API itself works or whether even in this episode we are talking about like I maybe don’t want to learn how to make the network work. I am busy trying to figure out how to make my application work, right? Like cognitive load is a thing. I can only really focus on so many things at a time where am I going to spend my time? Am I going to spend it learning how to do plumbing or am I going to spend it actually trying the right application that solves my business problem, right? It is an interesting thing. [0:41:17.7] NL: So, with the rise of software defined networking, how did that play into the adoption of cloud native technologies? [0:41:27.9] DC: I think it is actually one of the more interesting overlaps in the space because I think to Josh’s point again. his is where we were taking I mean I work for a company called [inaudible 0:41:37], in which we were virtualizing the network and this is fascinating because effectively we are looking at this as a software service that we had to bring up and build and build reliably and scalable. Reliably and consistently and scalable. We want to create this all while we are solving problems. But we need it to do within an API. It is like we couldn’t make the assumption with the way that networks were being defined today like going to each component and configuring them or using protocols was actually going to work in this new model of software confined networking. And so, we had an incredible amount of engineers who were really focused from a computer science perspective on how to effectively reinvent network as a software solution. And I do think that there is a huge amount of cross over here like this is actually where I think the waters meet between the way the developers think about the problems and the way that network engineers think about the problem but it has been a rough road I will say. I will say that STN I think is actually has definitely thrown a lot of network engineers under their heels because they’re like, “Wait, wait but that is not a network,” you know? Because I can’t actually look at it and characterize it in the way that I am accustomed to looking at characterizing the other networks that I play with. And then from the software side, you’re like, “Well maybe that is okay” right? Maybe that is enough, it is really interesting. [0:42:57.5] SL: You know I don’t know enough about the details of how AWS or Azure or Google are actually doing their networking like and I don’t even know and maybe you guys all do know – but I don’t even know that aside from a few tidbits here and there that AWS is going to even divulge the details of how things work under the covers for VPC’s right? But I can’t imagine that any modern cloud networking solution whether it would be VBPC’s or VNET’s or whatever doesn’t have a significant software to find aspect to it. You know, we don’t need to get into the definitions of what STN is or isn’t. That was a big discussion Duffie and I had six years ago, right? But there has to be some part of it that is taking and using the concepts that are common in STN right? And applying that. Just as the same way as the cloud vendors are using the concepts from compute virtualization to enable what they are doing. I mean like the reality is that you know the work that was done by the Cambridge folks on Zen was a massive enabler trade for AWS, right? The word done on KVM also a massive enabler for lots of people. I think GCP is KBM based and V Sphere where VM Ware data as well. I mean all of this stuff was a massive enablers for what we do with compute virtualization in the cloud. I have to think that whether it is – even if it wasn’t necessarily directly stemming out of Martin Casado’s open flow work at Stanford, right? That a lot of these software define networking concepts are still seeing use in the modern clouds these days and that is what enables us to do things like issue an API call and have an isolated network space with its own address space and its own routing and satiated in some way and managed. [0:44:56.4] JS: Yeah and on that latter point, you know as a consumer of this new software defined nature of networking, it is amazing the amount of I don’t know, I started using like a blanket marketing term here but agility that it is added, right? Because it has turned all of these constructs that I used to file a ticket and follow up with people into self-service things that when I need to poke holes in the network, hopefully the rights are locked down, so I just can’t open it all up. Assuming I know what I am doing and the rights are correct it is totally self-service for me. I go into AWS, I change the security group roll and boom, the ports have changed and it never looked like that prior to this full takeover of what I believe is STN almost end to end in the case of AWS and so on. So, it is really just not only has it made people like myself have to understand more about networking but it has allowed us to self-service a lot of the things. That I would imagine most network engineers were probably tired of doing anyways, right? How many times do you want to go to that firewall and open up that port? Are you really that excited about that? I would imagine not so. [0:45:57.1] NL: Well I can only speak from experience and I think a lot of network engineers kind of get into that field because it really love control. And so, they want to know what these ports are that are opening and it is scary to be like this person has opened up these ports, “Wait what?” Like without them even totally knowing. I mean I was generalizing, I was more so speaking to myself as being self-deprecating. It doesn’t apply to you listener. [0:46:22.9] JS: I mean it is a really interesting point though. I mean do you think it makes the networking people or network engineers maybe a little bit more into the realm of observability and like knowing when to trigger when something has gone wrong? Does it make them more reactive in their role I guess. Or maybe self-service is not as common as I think it is. It is just from my point of view, it seems like with STN’s the ability to modify the network more power has been put into the developers’ hands is how I look at it, you know? [0:46:50.7] DC: I definitely agree with that. It is interesting like if we go back a few years there was a time when all of us in the room here I think are employed by VMware. So, there was a time where VMware’s thing was like the real value or one of the key values that VMware brought to the table was the idea that a developer come and say “Give me 10 servers.” And you could just call an API or make it or you could quickly provision those 10 servers on behalf of that developer and hand them right back. You wouldn’t have to go out and get 10 new machines and put them into a rack, power them and provision them and go through that whole process that you could actually just stamp those things out, right? And that is absolutely parallel to the network piece as well. I mean if there is nothing else that SPN did bring to the fore is that, right? That you can get that same capability of just stamping up virtual machines but with networks that the API is important in almost everything we do. Whether it is a service that you were developing, whether it is a network itself, whether it is the firewall that we need to do these things programmatically. [0:47:53.7] SL: I agree with you Duffie. Although I would contend that the one area that and I will call it on premises STN shall we say right? Which is the people putting on STN solutions. I’d say the one area at least in my observation that they haven’t done well is that self-service model. Like in the cloud, self-service is paramount to Josh’s point. They can go out there, they can create their own BPC’s, create their own sub nets, create their own NAT gateways, Internet gateways to run security groups. Load balancers, blah-blah, all of that right? But it still seems to me that even though we are probably 90, 95% of the way there, maybe farther in terms of on premise STN solutions right that you still typically don’t see self-service being pushed out in the same way you would in the public cloud, right? That is almost the final piece that is needed to bring that cloud experience to the on-premises environment. [0:48:52.6] DC: That is an interesting point. I think from an infrastructure as a service perspective, it falls into that realm. It is a problem to solve in that space, right? So when you look at things like OpenStack and things like AWS and things like JKE or not JKE but GCE and areas like that, it is a requirement that if you are going to provide infrastructure as a service that you provide some capability around networking but at the same time, if we look at some of the platforms that are used for things like cloud native applications. Things like Kubernetes, what is fascinating about that is that we have agreed on a least come – we agreed on abstraction of networking that is maybe I don’t know, maybe a little more precooked you know what I mean? In the assumption within like most of the platforms as a service that I have seen, the assumption is that when I deploy a container or I deploy a pod or I deploy some function as a service or any of these things that the networking is going to be handled for me. I shouldn’t have to think about whether it is being routed to the Internet or not or routed back and forth between these domains. I should if anything only have to actually give you intent, be able to describe to you the intent of what could be connected to this and what ports I am actually going to be exposing and that the platform actually hides all of the complexity of that network away from me, which is an interesting round to strike. [0:50:16.3] SL: So, this is one of my favorite things, one of my favorite distinctions to make, right? And that is this is the two worlds that we have been talking about, applications and infrastructure and the perfect example of these different perspectives and you even said it or you talked there Duffie like from an IS perspective it is considered a given that you have to be able to say I want a network, right? But when you come at this from the application perspective, you don’t care about a network. You just want network connectivity, right? And so, when you look at the abstractions that IS vendors and solutions or products have created then they are IS centric but when you look at the abstractions that have been created in the cloud data space like within Kubernetes, they are application centric, right? And so, we are talking about infrastructure artifacts versus application artifacts and they end up meeting but they are coming at this from two different very different perspectives. [0:51:18.5] DC: Yeah. [0:51:19.4] NL: Yeah, I agree. [0:51:21.2] DC: All right, well that was a great discussion. I imagine that we are probably get into – at least I have a couple of different networking discussions that I wanted to dig into and this conversation I hope that we’ve helped draw some parallels back and forth between the way – I mean there is both some empathy to spend here, right? I mean the people who are providing the service of networking to you in your cloud environments and your data centers are solving almost exactly the same sorts of availability problems and capabilities that you are trying to solve with your own software. And I think in itself is a really interesting takeaway. Another one is that again there is nothing new under the sun. The problems that we are trying to solve in networking are not different than the problems that you are trying to solve in applications. We have far fewer tools and we generally network engineers are focused on specific changes that happen in the industry rather than looking at a breathe of industries like I mean as Josh pointed out, you could break open a Java book. And see 8,000 patterns for how to do Java and this is true, every programming language that I am aware of I mean if you look at Go and see a bunch of different patterns there and we have talked about different patterns for just developing cloud native aware applications as well, right? I mean there is so many options in the software versus what we can do and what are available to us within networks. And so I think I am rambling a little bit but I think that is the takeaway from this session. Is that there is a lot of overlap and there is a lot of really great stuff out there. So, this is Duffie, thank you for tuning in and I look forward to the next episode. [0:52:49.9] NL: Yep and I think we can all agree that Token Ring should have won. [0:52:53.4] DC: Thank you Josh and thank you Scott. [0:52:55.8] JS: Thanks. [0:52:57.0] SL: Thanks guys, this was a blast. [END OF EPISODE] [0:52:59.4] ANNOUNCER: Thank you for listening to The Podlets Cloud Native Podcast. Find us on Twitter at https://twitter.com/ThePodlets and on the http://thepodlets.io/ website, where you'll find transcripts and show notes. We'll be back next week. Stay tuned by subscribing. [END]See omnystudio.com/listener for privacy information.