Kutad Gubilik's Listen Later: Recent Episodes
Kutad Gubilik / Listen Notes
Podcast: Rapid Response RN (LS 49 · TOP 0.5% what is this?)
Episode: 98: "Broken Heart Syndrome" aka Takotsubo Cardiomyopathy
Pub date: 2024-03-29
Get Podcast Transcript →
powered by Listen411 - fast audio-to-text and summarization
Takotsubo cardiomyopathy, also known as “broken heart syndrome,” is hard to diagnose because its symptoms mimic more common conditions like acute coronary syndrome. This stress-induced cardiomyopathy presents a mysterious challenge to nurses, as you’ll hear in today’s patient story.
Host Sarah Lorenzini shares the case of a patient who went from experiencing shortness of breath and nausea to a serious cardiac emergency. She breaks down the patient’s initial presentation, their quick decline featuring hypoxia and flash pulmonary edema, and ultimate diagnosis of takotsubo cardiomyopathy.
In this episode, Sarah dives into the pathophysiology of takotsubo cardiomyopathy, covering how emotional or physical stress leads to the condition. She goes over its symptoms and treatment, as well as the role of nurses in managing the condition.
Tune in now to find out how you should be handling similar cardiac emergencies!
Topics discussed in this episode:
- Takotsubo cardiomyopathy: a patient case study
- The pathophysiology of takotsubo cardiomyopathy
- Diagnosing takotsubo cardiomyopathy
- How to effectively treat takotsubo cardiomyopathy
- Final takeaways for nurses
Listen to Episode 82: Sympathetic Crashing Acute Pulmonary Edema: That Time My Patient Went From Stable A-Fib RVR to Intubated in 30 Minutes! https://podcasts.apple.com/ca/podcast/82-sympathetic-crashing-acute-pulmonary-edema-that/id1535997752?i=1000637926574
Mentioned in this episode:
Rapid Response Academy Link
Wanna check out Rapid Response Academy: The Heart and Science of Caring for the Sick?click this link to learn more:https://www.rapidresponseandrescue.com/community
Rapid Response and Rescue Intro Course
CONNECT📸 Connect on Instagram: https://www.instagram.com/therapidresponsern/🫶 Check out my membership: https://www.rapidresponseandrescue.com/community📚 Check out my course: https://www.rapidresponseandrescue.com/learnmore🧑💻Check out my website: https://www.rapidresponseandrescue.com/📬 Subscribe to my newsletter: https://www.rapidresponseandrescue.com/login🎁 Affiliation and discounts: https://hoo.be/therapidresponsernSAY THANKS💜Leave a review on Apple Podcasts: https://podcasts.apple.com/ca/podcast/rapid-response-rn/id1535997752💚Leave a rating on Spotify: https://open.spotify.com/show/55LQqeDg6XFeixvZLEp4xETo get the FREE Rapid Response RN Assessment Guide and the coupon code for $10 off the cost of the course, message Sarah on Instagram @TheRapidResponseRN and type the word PODCAST!This episode was produced by Podcast Boutique https://www.podcastboutique.com
The podcast and artwork embedded on this page are from Sarah Lorenzini, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Revolutionary Left Radio (LS 65 · TOP 0.05% what is this?)
Episode: Fyodor Dostoevsky: The Great Russian Novelist and Proto-Existentialist
Pub date: 2022-01-15
Get Podcast Transcript →
powered by Listen411 - fast audio-to-text and summarization
In this episode, Corey Mohler (from Existential Comics) returns to the show, this time to discuss the life, religion, politics, art, and psychology of the 19th century Russian literary giant Fyodor Dostoevsky - one of the greatest novelists of all time and the author of Crime and Punishment, The Brother Karamazov, The Idiot, Notes from the Underground, and many more!
Check out Kung Fu Chess here: https://kungfuchess.org/ Outro Music: "Lotus Flower" by Radiohead
Support Rev Left Radio: https://www.patreon.com/RevLeftRadio
or make a one time donation: PayPal.me/revleft
LEARN MORE ABOUT REV LEFT RADIO: www.revolutionaryleftradio.com
The podcast and artwork embedded on this page are from Revolutionary Left Radio, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: HARDtalk (LS 54 · TOP 0.5% what is this?)
Episode: Jens Stoltenberg: Is Russia really preparing for a war with Nato?
Pub date: 2024-02-26
Sarah Montague is at Nato’s headquarters in Brussels to speak to its outgoing Secretary General Jens Stoltenberg. Two years after Russia’s full scale invasion of Ukraine, is Vladimir Putin now preparing for a war with Nato?
The podcast and artwork embedded on this page are from BBC World Service, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Newscast (LS 68 · TOP 0.05% what is this?)
Episode: NATO at 75: Can it stand up to Russia?
Pub date: 2024-04-03
Today, foreign ministers are gathering at NATO HQ in Brussels to mark 75 years of the military alliance and discuss how the member states will continue to support Ukraine and deter Russia.
James Cook is joined by the Polish Foreign Minister Radosław Sikorski to discuss efforts to support Ukraine, whether NATO members need to step up their spending and what he thinks about a potential return of President Trump.
And BBC diplomatic correspondent James Landale and head of foreign policy at Policy Exchange Sophia Gaston discuss the global challenges facing NATO, as well as its role in ending the conflict in Ukraine.
You can join our Newscast online community here: https://tinyurl.com/newscastcommunityhere
Newscast brings you daily analysis of the latest political news stories from the BBC. It was presented by James Cook. It was made by Miranda Slade with Gemma Roper, Joe Wilkinson and Hanna Ward. The technical producer was Michael Regaard. The assistant editor is Chris Gray. The senior news editor is Sam Bonham.
The podcast and artwork embedded on this page are from BBC News, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Best of the Spectator (LS 54 · TOP 0.5% what is this?)
Episode: The Edition: Is Nato ready for war with Russia?
Pub date: 2024-02-15
Welcome to a slightly new format for the Edition podcast! Each week we will be talking about the magazine – as per usual – but trying to give a little more insight into the process behind putting The Spectator to bed each week.
On the podcast: The Spectator’s assistant foreign editor Max Jeffery writes our cover story this week, asking if Nato is ready to defend itself against a possible Russian invasion. Max joined Nato troops as they carried out drills on the Estonian border. Max joins us on the podcast along with historian Mark Galeotti, author of Putin's Wars. (00:55)
Then: Lionel Shriver talks to us about the sad case of Jennifer Crumbley, the mum who's just been convicted of manslaughter – for her son carrying out a school shooting. Does this set a dangerous moral precedent? (16:05)
And finally: would you stay in a haunted hotel? The travel writer Sean Thomas speaks to us from one in Cambodia, having written for the magazine about the places with grisly pasts that he has stayed in over the course of his career. We're also joined by Judith Blincow, owner of the Mermaid Inn in Rye, one of the most haunted hotels in the country. (26:10)
Hosted by William Moore and Lara Prendergast.
Produced by Cindy Yu.
If there are any areas of the magazine that you are particularly interested in or any questions you have for Will and Lara, please email: podcast@spectator.co.uk. We will try and answer as many as we can in next week’s episode.
The podcast and artwork embedded on this page are from The Spectator, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Frugal Living (LS 35 · TOP 3% what is this?)
Episode: Is real estate really an easy way to make money?
Pub date: 2022-08-30
Jim talks with Pedro Meneses, realtor and investor, about what it takes to make money with real estate. Want to join the Frugal Living podcast community? You can find us on social media: TikTok, Instagram, Facebook, and Linkedin.
Find the full show notes, including a transcript of the show, at Frugal.fm. This episode's sponsor is Highlights.
The podcast and artwork embedded on this page are from Jim Markus, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Frugal Living (LS 35 · TOP 3% what is this?)
Episode: Frugal Food: Cheap Healthy Meals with Lynne Bowman
Pub date: 2022-10-18
Lynne Bowman, author of Brownies for Breakfast: A Cookbook for Diabetics and the People Who Love Them, talks with Jim about the frugal joy of cooking at home. Recipes included!
Want to join the Frugal Living podcast community? You can find us on social media @frugallivingpod on TikTok, Instagram, Facebook, and Linkedin. Find the full show notes, including a transcript of the show, at Frugal.fm. Frugal Living is brought to you by Brad's Deals.
Looking for more frugal tips and tricks? We recently discussed how supply chain disruptions could result in much better Black Friday deals and the best Prime Day deals we expect every year.
The podcast and artwork embedded on this page are from Jim Markus, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Kaldıraç Dergi
Episode: Taşdevrinden yeni binyıla; insanlık tarihi - Bölüm 1 - Bülent Bilgin
Pub date: 2024-03-05
Bülent Bilgin'in sunumuyla 6 hafta süren ve sınıflı toplumların oluşumundan başlayarak ‘Taş devrinden yeni binyıla, insanlık tarihi’ dersi "antik dünya", "orta çağlar", "büyük dönüşüm", "altüst olan dünya" alt başlıklarını da içeren dersliğin tamamını bu oynatma listesinden izleyebilirsiniz. Son ders kaydı ilerleyen günlerde buraya eklenecektir.
Kaldıraç Akademi'nin derslerine kayıt olmak için kaldiracdergi@gmail.com'a mail atabilirsiniz
The podcast and artwork embedded on this page are from Kaldıraç Dergi, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Empires Podcast the Ottomans (LS 36 · TOP 2.5% what is this?)
Episode: Sultan Mehmed I “The Restorer” & Post Interregnum Headache: Episode 14
Pub date: 2021-11-25
Sultan Mehmed I “The Restorer” & Post Interregnum Headache: Episode 14Show Synopsis: It is the year 1413 and Prince Mehmed has defeated his three brothers in battle and claimed the Ottoman throne for himself. In certain circles the hope of peace and stability for the Empire grows as the dark days of the Civil War recedes. In other quarters Mehmed’s ascension is greeted with hate, fear, and foreboding as the Christian leaders of Wallachia, Byzantine, and Venice array themselves to take advantage of Ottoman weakness.Across the straits Anatolia is awash in poverty, banditry, and rebellion where all hope has sank in the pits of despair of the past 11 years. The far off Karamanids break off again and the terrible specter of an invasion from the successor state to Timur’s Empire looms large. Amidst the chaos a religious leader arises, Sheikh Bedreddin, who’s movement will change the face of Ottoman policy for the next century.A strategic overview of these challenges are detailed by Frank as the stage is set for Mehmed I to set off and claim his place in history as “The Restorer” of the Ottoman Empire.Thanks for listening! Your host and creator Frank would be thrilled to hear from you the listener anytime. Email: empiresofhistorypodcast@gmail.comRespectful and constructive criticism of my pronunciations of persons, places, and things are greatly appreciated and will receive a special shoutout in the next episodes. Any and all feed back (good and bad) are welcome and will be responded to in kind.Follow Frank on Twitter: @EmpiresPodcast
The podcast and artwork embedded on this page are from Frank Schumpert- Host/Creator, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Empires Podcast the Ottomans (LS 36 · TOP 2.5% what is this?)
Episode: Sultan Mehmed I- Wallachia & Crushing Bedreddin: Episode 16
Pub date: 2022-01-11
Synopsis: Sultan Mehmed I deals with a rebellious pretender to the throne, Prince Mustafa and his confederate Cuneyd, the governor of Nikopol (ref: Episode 15). After settling accounts in Rumelia, the Sultan is forced to contend with a massive rebellion in both the Balkans and Anatolia under the philosophical banner of Sheikh Bedreddin.An overall picture of Sheikh Bedreddin, his philosophy, social and economic context of the Rebellion is explored. Bedreddin’s ultimate opponent, the redoubtable Bayezid Pasha, companion of and now Vizier to Sultan Mehmed I, is profiled. The Wallachian ever present threat of invasion is stopped and forced into tributary status.Episode 16 concludes with an overall strategic assessment of the Ottoman Empire in 1420 and the stage is set for the death of the Sultan and subsequent events in up-coming Episode 17.Thanks for listening! Your host and creator Frank would be thrilled to hear from you the listener anytime. Email: empiresofhistorypodcast@gmail.comFollow Frank on Twitter: @EmpiresPodcastSpecial Mention: 'As the Money Burns', hosted/created by Nicki Woodard. Please take a minute and check her podcast out “[a] deep dive into what happens during the Great Depression to America’s richest & famous heirs & heiresses. Scandals, greed, lust, envy.”Here is her link: Episode Guide – As the Money BurnsEmpires Podcast the OttomansListen and SHARE with a friend, subscribe and leave a review please :)Apple: Listen on Apple Podcasts Spotify: Listen on Spotify Anchor: Listen on Anchor
The podcast and artwork embedded on this page are from Frank Schumpert- Host/Creator, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Kıraathane
Episode: Nejat Yavaşoğulları, Hakan Kurşun - Bedreddin: Destandan Rock Operasına
Pub date: 2022-05-07
Bulutsuzluk Özlemi 10. albümünde benzersiz bir çalışma sundu dinleyicilere. Nâzım Hikmet’in 1936 yılında yayımlanan destansı şiiri Simavne Kadısı Oğlu Şeyh Bedreddin’in hikâyesi, Nejat Yavaşoğulları'nın bestesiyle yeni bir forma bürünüyor. Mehmed Çelebi‘ye karşı ayaklanma hazırladıkları gerekçesiyle asılan Şeyh Bedreddin, Börklüce Mustafa ve Torlak Kemal‘i ölümsüzleştiren bu manzum eserin müzikal dönüşümünü konuşmak için 17 Ocak 2022 akşamı Kıraathane'de buluştuk. Nejat Yavaşoğulları'ndan, Hakan Kurşun’un moderatörlüğünde Bedreddin'i dinledik.
The podcast and artwork embedded on this page are from Kiraathane24, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Whiskey Web and Whatnot: Web Development, Neat (LS 37 · TOP 2.5% what is this?)
Episode: Chris Coyier on Embracing Technology and the Future of Web Development
Pub date: 2024-02-15
Hosts Robbie Wagner and Charles William Carpenter III welcome special guest, Chris Coyier the co-founder of CodePen and an avid web enthusiast, to share his insights on the latest trends and happenings in the tech world.
Pondering over the pros and cons of GitHub desktop, discussing React's influence on teams and efficiency, grappling with the hot topics around CSS and Tailwind, and airing their thoughts on Apple's latest Vision Pro, the conversation bounces around delightfully.
All along, they’re savoring a pour from Barrell Craft Spirits and enjoying the occasional detour into pop culture, fitness, and more. Join them as they navigate through this tech-infused whirlwind with a dash of web nostalgia.
Key Takeaways
- [00:48] - Discussing Movies and Pop Culture
- [02:32] - Introducing the Guest: Chris Coyier
- [03:05] - Chris's Journey with CodePen
- [03:56] - Chris's Other Projects and Interests
- [07:13] - Whiskey Tasting Begins
- [07:57] - Discussing the Whiskey: Barrel Bourbon
- [09:39] - Diving into Pop Culture: Movies and Celebrities
- [11:02] - Back to Whiskey: Rating the Barrel Bourbon
- [11:59] - Discussing Tech and Coding
- [25:58] - Hot Takes: Tech Debates
- [32:27] - Discussing the Evolution of Package Managers
- [33:16] - Exploring the Transition from Node to Bun
- [34:33] - The Impact of Vite on Development
- [34:46] - The Quirks of Tech Terminology
- [36:24] - The Shift from Global to Personalized Package Management
- [36:41] - The Influence of Microsoft in the Tech World
- [39:04] - The Evolution of Web Development and the Role of Abstractions
- [57:12] - The Future of Web Development: AR, VR, and AI
- [01:03:27] - The Impact of Tech on Everyday Life
- [01:03:43] - The Future of CodePen and the Tech Industry
Links
- Chris Coyier Twitter
- Chris Coyier LinkedIn
- CodePen
Connect with our hosts
- Robbie Wagner
- Chuck Carpenter
Subscribe and stay in touch
- Apple Podcasts
- Spotify
- Google Podcasts
- Whiskey Web and Whatnot
Whiskey Web and Whatnot MerchEnjoying the podcast and want us to make more? Help support us by picking up some of our fresh merch at https://whiskey.fund/.
--- Send in a voice message: https://podcasters.spotify.com/pod/show/whiskey-web-and-whatnot/message
The podcast and artwork embedded on this page are from RobbieTheWagner and Charles William Carpenter III, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: RHLSTP with Richard Herring (LS 67 · TOP 0.05% what is this?)
Episode: RHLSTP 9 - Armando Iannucci and Graham Linehan
Pub date: 2012-06-26
It's the last in the series, but what a way to end with the creators of Ted & Ralph, Father Ted, Malcolm Tucker and Alan Partridge on stage together (but who created which?). There's talk of tax evasion, OBEs, fantastic new plots for Last of the Summer Wine, Goodfellows and a surprising departure for the Birmingham Six. Find out how many people on stage have been wanked by a ventriloquist dummy operated by Stewart Lee. It goes on for AGES, but I don't think it's hyperbole to say that this is better than the hyper-bowl. The only way it could have been improved is if we'd put a Shrek in it. Back in October for more. In the meantime there will be 25 or so RHEFP in August to keep you busy. Be lovely to see you in the audience of one of those!
SUPPORT THE SHOW!
Check out our website and become a badger and see extra content http://rhlstp.co.uk
See details of the RHLSTP tour dates http://richardherring.com/gigs
Buy DVDs and Books at http://gofasterstripe.com
Become a member at https://plus.acast.com/s/rhlstp.
Hosted on Acast. See acast.com/privacy for more information.
The podcast and artwork embedded on this page are from Sky Potato, Go Faster Stripe and Fuzz Productions, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: RHLSTP with Richard Herring (LS 67 · TOP 0.05% what is this?)
Episode: RHLSTP 379 - Armando Iannucci
Pub date: 2022-05-11
#379 M&M Apocalypse - Richard’s son continues to come up with better material than his dad, without even trying. His guest is the unparalleled comedy genius Armando Iannucci. They chat about how Armando once again predicted the future with his hilarious new sitcom Avenue 5, the lows and deeper lows of lockdown, what inspired him to write the mock-heroic poem, Pandemonium https://www.amazon.co.uk/Pandemonium-Some-verses-Current-Predicament/dp/1408715082/, whether he’d make a good PM, why Richard is upset about the casting of David Copperfield, the smell of an angel’s fart, the precipice the world finds itself on the edge of and whether there is any hope for us and the most astonishing story of what a supporting actor chose to say to Armando on the set of Veep (which is the highlight of the series so far).
Live RHLSTPs coming up. Guest and ticket link info here https://richardherring.com/rhlstpt/tour
SUPPORT THE SHOW!
Watch our TWITCH CHANNEL
Become a badger and see extra content at our WEBSITE
See details of the RHLSTP TOUR DATES
Buy DVDs and Books from GO FASTER STRIPE
Become a member at https://plus.acast.com/s/rhlstp.
Hosted on Acast. See acast.com/privacy for more information.
The podcast and artwork embedded on this page are from Sky Potato, Go Faster Stripe and Fuzz Productions, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Ottoman History Podcast (LS 48 · TOP 0.5% what is this?)
Episode: The Circassian Diaspora
Pub date: 2021-09-16
with Şölen Şanlı Vasquez hosted by Brittany White | Over the course its final decades, millions of Muslim immigrants, many of them refugees of war and Russian conquest, settled in the Ottoman Empire. Between a quarter and a third of people in Turkey today have ancestors who arrived with those migrations. Yet their history often stops short of capturing the personal experiences of such people, what was erased, and what they have sought to preserve. In this episode, we speak with sociologist Şölen Şanlı Vasquez about how to write a more empathetic history of migration in Turkey through the lens of the Circassian diaspora. For her, this history is not just the story of how people from the North Caucasus were expelled from one empire and settled in an another. It is also a personal story about continuity, rupture, and recovery within the families of immigrants across generations and continents. Through a conversation about her ongoing research project called "The Home Within," we explore the themes of family, gender, ethnicity, race, and erasure --- not only in Turkey --- but across contexts of migration and displacement in the US and elsewhere. And we also reflect on the importance of public history that makes these issues relevant and relatable to a wider audience. « Click for More »
The podcast and artwork embedded on this page are from Ottoman History Podcast, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Owen Jones Podcast (LS 55 · TOP 0.5% what is this?)
Episode: How Capitalism Wastes Billions: Mariana Mazzucato's Tour De Force
Pub date: 2023-04-19
Professor Mariana Mazzucato is one of the world's most exciting economic thinkers, and her new book - THE BIG CON - exposes how consultancy firms are eating up billions upon billions of pounds. You won't think of our economic system the same way again.
Support this show http://supporter.acast.com/the-owen-jones-podcast.
Hosted on Acast. See acast.com/privacy for more information.
The podcast and artwork embedded on this page are from Owen Jones, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: THE ADAM BUXTON PODCAST (LS 78 · TOP 0.01% what is this?)
Episode: EP.185 - MARIANA MAZZUCATO
Pub date: 2022-08-12
Adam meets Mariana Mazzucato, 'one of the worlds most influential economists'* about how capitalism fails and how it can be made to work better by 'reimagining the state'.
(* see WIRED article link below)
This episode was recorded face to face in London on 10th March 2022
Thanks to Séamus Murphy-Mitchell for production support.
Podcast artwork by Helen Green
RELATED LINKS
MARIANA MAZZUCATO WEBSITE
THIS ECONOMIST HAS A PLAN TO FIX CAPITALISM - IT'S TIME WE LISTENED by João Medeiros - 2019 (WIRED MAGAZINE)
MISSION ECONOMY: A MOONSHOT GUIDE TO CHANGING CAPITALISM- 2021 (WORLD OF BOOKS)
MISSION ECONOMY: MARIANA MAZZUCATO IN CONVERSATION WITH GILLIAN TETT - 2021 (YOUTUBE)
MARIANA MAZZUCATO - NEW ECONOMICS LECTURE- 2016 (YOUTUBE)
MOONDOGGLE: THE FORGOTTEN OPPOSITION TO THE APOLLO PROGRAMby Alexis C. Madrigal - 2012 (THE ATLANTIC)
GIL SCOTT-HERON - WHITEY ON THE MOON - 1970 (YOUTUBE)
WHY EXPLORE SPACE? A 1970 LETTER TO A NUN IN AFRICA (by Dr Ernst Stuhlinger) (ROGER LAUNIUS' BLOG - 2012)
Hosted on Acast. See acast.com/privacy for more information.
The podcast and artwork embedded on this page are from ADAM BUXTON, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Full Story (LS 57 · TOP 0.5% what is this?)
Episode: Campaign catchup: will increasing the minimum wage lead to higher inflation?
Pub date: 2022-05-11
The PM calls the opposition leader a ‘loose unit’ for supporting a rise in the minimum wage. Anthony Albanese responds that Scott Morrison is ‘loose with the truth’. Paul Karp talks to Jane Lee about what this all means for wages and the campaign
The podcast and artwork embedded on this page are from The Guardian, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Edge of Fame (LS 45 · TOP 1% what is this?)
Episode: PREVIEW: Norm Macdonald Doesn’t Like Endings
Pub date: 2018-01-24
Preview episode: Geoff Edgers follows comedian and former SNL star Norm Macdonald on his road to reinvention. Join them as they hang out backstage, talk about the original “fake news,” and lose a few grand on the Portland Trailblazers.
The podcast and artwork embedded on this page are from WBUR & The Washington Post, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Natural Seduction - The Natural Lifestyles Podcast with James Marshall (LS 39 · TOP 2% what is this?)
Episode: Why Women Flake & When To Move On
Pub date: 2022-08-26
Alex explains a mindset that helps to deal with self-doubt caused by flaky contacts
Podcast: Natural Seduction - The Natural Lifestyles Podcast with James Marshall (LS 39 · TOP 2% what is this?)
Episode: The Reality Of A Hot Girl’s Life
Pub date: 2021-11-26
James explains why so many young women are tempted to start OnlyFans accounts, and what it has to do with late-stage capitalism and the decentralization of sex work
Podcast: Recode Daily (LS 59 · TOP 0.1% what is this?)
Episode: OnlyFans blurs the line between influencing and sex work
Pub date: 2021-12-15
On platforms like OnlyFans, people with big followings online can earn money. Rebecca Jennings explains why celebrities and influencers are joining the platform, and what their arrival means for the sex workers who were there first.
Read Rebecca’’s story:https://www.vox.com/the-goods/22749123/onlyfans-influencers-sex-work-instagram-pornography
Today’s episode was produced by Vox audio fellow Tori Dominguez, engineered by Melissa Pons (Hemlock Creek Productions), and hosted by Adam Clark Estes.
Support Recode Daily by making a financial contribution to Vox! bit.ly/givepodcasts
Learn more about your ad choices. Visit podcastchoices.com/adchoices
The podcast and artwork embedded on this page are from Recode, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Theory & Philosophy (LS 50 · TOP 0.5% what is this?)
Episode: Jordan Peterson
Pub date: 2022-01-21
In this episode, I present my first publication, "Jordan Peterson and the (F)law of Scientific Inquiry."
You can find it here, if you'd like :) https://politikon.iapss.org/index.php/politikon/article/view/11
If you want to support me, you can do that with these links:
Patreon: https://www.patreon.com/theoryandphilosophy paypal.me/theoryphilosophy
Twitter: @DavidGuignion IG: @theory_and_philosophy
The podcast and artwork embedded on this page are from David Guignion, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Vox Conversations (LS 75 · TOP 0.05% what is this?)
Episode: Nicholas Carr on deep reading and digital thinking
Pub date: 2020-06-29
In 1964, the Canadian philosopher Marshall McLuhan wrote his opus Understanding Media: The Extensions of Man. In it, he writes, “In the long run, a medium's content matters less than the medium itself in influencing how we think and act." Or, put more simply: "Media work their magic, or their mischief, on the nervous system itself."
This idea — that the media technologies we rely on reshape us on a fundamental, cognitive level — sits at the center of Nicholas Carr's 2010 book The Shallows: What the Internet Is Doing to Our Brains. A world defined by oral traditions is more social, unstructured, and multi-sensory; a world defined by the written written word is more individualistic, disciplined, and hyper-visual. A world defined by texting, scrolling and social feedback is addicted to stimulus, constantly forming and affirming expressions of identity, accustomed to waves of information.
Back in 2010, Carr argued that the internet was changing how we thought, and not necessarily for the better. “"My brain, I realized, wasn't just drifting,” he wrote. “It was hungry. It was demanding to be fed the same way the net fed it — and the more it was fed, the hungrier it became.” His book was a finalist for the Pulitzer that year, but dismissed by many, including me. Ten years on, I regret that dismissal. Reading it now, it is outrageously prescient, offering a framework and language for ideas and experiences I’ve been struggling to define for a decade.
Carr saw where we were going, and now I wanted to ask him where we are. In this conversation, Carr and I discuss how speaking, reading, and now the Internet have each changed our brains in different ways, why "paying attention" doesn't come naturally to us, why we’re still reading Marshall McLuhan, how human memory actually works, why having your phone in sight makes you less creative, what separates "deep reading” from simply reading, why deep reading is getting harder, why building connections is more important than absorbing information, the benefits to collapsing the world into a connected digital community, and much more.
The point of this conversation is not that the internet is bad, nor that it is good. It’s that it is changing us, just as every medium before it has. We need to see those changes clearly in order to take control of them ourselves.
Book recommendations:
The Control Revolution by James R. Beniger
The Four-Dimensional Human by Laurence Scott
A Visit from the Goon Squad by Jennifer Egan
Want to contact the show? Reach out at ezrakleinshow@vox.com
Please consider making a contribution to Vox to support this show: bit.ly/givepodcasts Your support will help us keep having ambitious conversations about big ideas.
New to the show? Want to check out Ezra’s favorite episodes? Check out the Ezra Klein Show beginner’s guide (http://bit.ly/EKSbeginhere)
Credits:
Producer/Editer - Jeff Geld
Research Czar - Roge Karma
Learn more about your ad choices. Visit podcastchoices.com/adchoices
The podcast and artwork embedded on this page are from Vox, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Beyond the Headlines (LS 32 · TOP 5% what is this?)
Episode: How Covid-19 mRNA research could cure HIV and cancer
Pub date: 2021-05-06
Within months of the emergence of coronavirus in late 2019 drug companies around the world were racing for a vaccine. Within a year, shots were being delivered into people’s arms. The speed at which the world developed not one but several different Covid-19 vaccines in seemingly record time has thrown into sharp relief other vaccine programmes that have toiled for years with no final breakthrough.
HIV, the virus that causes Aids, kills nearly 700,000 every year, but has outwitted vaccine developers for more than three decades. Even regular influenzas can be deadly and our tools to stop it are very limited. But now, there is renewed hope that this could change – and that may be thanks to the work on Covid-19 vaccines.
On this week's Beyond the Headlines, host James Haines-Young delves into how Covid-19 vaccines have already shaken up the drug industry and how what we are learning now could one day lead to tailor-made treatment for almost any ailment.
The podcast and artwork embedded on this page are from The National UAE, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Views on Vue (LS 36 · TOP 3% what is this?)
Episode: Episode 147: VUE 142: From Nuxt to React - Catching up with Debbie O'Brien
Pub date: 2021-03-23
Lindsay and Steve talk with Debbie O'Brien, Head Developer Advocate at Bit and former Head of Learning at Nuxt about her new position. We talk about what Bit is, and how they are bringing a new approach to component development. We also talk about how Debbie is having to learn React, what that looks like for an experienced Vue developer, and ways we learn new frameworks and libraries.
Panel * Lindsay Wardell * Steve Edwards
Guest * Debbie O'Brien
Sponsors * Dev Heroes Accelerator
Links * Devchat.tv | VoV 118: Nuxtify Everything with Debbie O’Brien * React.js Learning Path - Be Productive with React.js, Today's Most Popular Framework * Epic React by Kent C. Dodds * The Beginner's Guide to React * Vueconf.US 2021 * Twitter: Debbie O'Brien ( @debs_obrien )
Picks * Debbie- Just-In-Time: The Next Generation of Tailwind CSS * Lindsay- Juralen * Lindsay- Introduction to Vite - Next Generation Frontend Tooling * Lindsay- SpaceTraders API * Steve- Instagram: The wholly pun bible ( @pun_bible ) * Steve- Instagram: Tyrannosaurus Rex ( @standup.trex )
Contact Lindsay
- Twitter: Lindsay Wardell ( @lindsaykwardell )
Contact Steve
- Twitter: Steve Edwards ( @wonder95 )
Special Guest: Debbie O'Brien.
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Views on Vue (LS 36 · TOP 3% what is this?)
Episode: Deep Dive into Nuxt with Mike Gallagher - VUE 164
Pub date: 2021-09-14
Lindsay and Steve talk to Mike Gallagher, Software Architect at Hip eCommerce, about his blog post exploring server-side rendering and how Nuxt functions under the hood. They explore Mike's specific use case of needing to manage routing on the client, rather than the server, and how he was able to find a solution.
They also discuss how Mike approaches difficult problems like this, and how he determines the next steps to find a solution. They explore some of the intricate details of Nuxt, including how Mike's company handles caching with Nuxt and other production use cases.
Panel * Lindsay Wardell * Steve Edwards
Guest * Mike Gallagher
Sponsors * Dev Influencers Accelerator * Level Up | Devchat.tv * PodcastBootcamp.io
Links * Server-side rendering and the journey to the center of Nuxt.js * GitHub | mikeapr4/vue-backbone * Awesome Nuxt Modules * Plugins directory - NUXTJS * Tracing or Debugging Vue.js Reactivity: The computed tree * GitHub | GoogleChrome/rendertron * GitHub | lindsaykwardell/nuxt-github-api * Agility CMS * Hip eCommerce * Michael Gallagher - Medium * LinkedIn: Michael Gallagher * GitHub: Michael Gallagher ( mikeapr4 )
Picks * Lindsay- GitHub | nuxt-community/module-template * Lindsay- vitejs/awesome-vite * Lindsay- Nuxt Nation Conference * Mike- AST Explorer * Steve- standup.trex - Instagram * Steve- dadjokesallday - Instragram * Steve- Failed Comedian Becomes Pastor
Contact Lindsay:
- Twitter: Lindsay Wardell ( @lindsaykwardell )
Contact Steve:
- Twitter: Steve Edwards ( @wonder95 )
- GitHub: Steve Edwards ( wonder95 )
- LinkedIn: Steve Edwards
Special Guest: Mike Gallagher.
Sponsored By:
- Podcast Bootcamp: Launch an Amazing Sounding Podcast in just 4 WEEKS! Work with a 13 year podcasting veteran to get your podcast started off on the right foot!
- Top End Devs Coaching: If you have questions about how to grow your skills or take your career to the next level, join us on our next weekly coaching call. It's completely free.
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Backend Engineering Show with Hussein Nasser (LS 38 · TOP 2.5% what is this?)
Episode: When is NodeJS Single Threaded and when is it multi-Threaded?
Pub date: 2021-03-24
Node JS Is single-threaded asynchronous non-blocking javascript runtime, but it's not always single-threaded there are occasions where nodejs uses multi-threading, so the questions we will try to answer in this video, when is nodejs single-threaded and when does it use multi-threading and how will that affect my app?
- Event Loop single thread, that really just loops for callbacks 0:00
- Threading in Node jS (libuv) 4:00
- used for
- IO/intensive
- DNS queries
- file system reads
- CPU intensive
- crypto
- compression
- process.env.UV_THREADPOOL_SIZE=1
Examples 8:00
Cluster Nodejs 16:00
Example 1
HTTP server return 1
HTTP server while 1
HTTP server with file system read async
HTTP server with file system read sync
HTTP server with fetch call to server (dns)
Support my work on PayPal
https://bit.ly/33ENps4
Become a Member on YouTube
https://www.youtube.com/channel/UC_ML5xP23TOWKUcc-oAE_Eg/join
🧑🏫Courses I Teach
https://husseinnasser.com/courses
Support this podcast: https://anchor.fm/hnasr/support
The podcast and artwork embedded on this page are from Hussein Nasser, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: JavaScript Jabber (LS 43 · TOP 1.5% what is this?)
Episode: JSJ 449: The Things Every JavaScript Developer Must Know
Pub date: 2020-09-15
In this episode the panel discusses various programming topics, and whether or not they are required knowledge for JavaScript programmers. This includes topics such as scopes and hoisting, closures, the event-loop, and the behavior of this. For each such topic, the panel discusses whether or not JavaScript devs are required to know and understand them in order to write better code, or pass job interviews, or to understand existing codebases. Alternatively, if these are topics that JavaScript developers don’t need to know, and maybe should even avoid.
Sponsors * Audible.com * The Complete Software Developer’s Career Guide – Grab a Copy Today * CacheFly
Panel * AJ ONeal * Charles Max Wood * Dan Shappir * Steve Edwards
Links * 10 Interview Questions Every JavaScript Developer Should Know – AKA: The Keys to JavaScript Mastery * https://kentcdodds.com/blog/newspaper-code-structure * https://developer.mozilla.org/en-US/docs/Web/JavaScript/Closures * Your Coffee Shop Doesn’t Use Two-Phase Commit
Picks AJ * Crock on JS
Follow JavaScript Jabber on Twitter: @JSJabber
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Ladybug Podcast (LS 49 · TOP 1% what is this?)
Episode: Level up with JavaScript
Pub date: 2020-05-11
JavaScript is notorious for being one of the most popular, yet also one of the most despised programming languages to learn, so today we’re covering some of the intermediate and advanced JavaScript concepts! We’ll discuss convoluted topics like generators, prototypal inheritance, and the rendering engine.
Knowing intermediate JavaScript concepts like the call stack, context, scope, the prototype chain, higher order functions, async programming, and the event loop is invaluable and will help with learning frameworks. The fundamentals won't change even if the ecosystem does.
Show notes 03:24 - Functional Programming vs OOP 06:28 - Prototypal inheritance 20:34 - Higher order functions 25:54 - Callback functions 27:10 - Closures 27:46 - Scope + Context 31:12 - Iterators & Generators 34:26 - Rendering engine 37:54 - Call Stack 40:33 - Event loop 43:39 - Throttle and debounce 46:21 - Asynchronous programming 52:09 - Hoisting 54:44 - Primitive vs reference 56:59 - Debugging 58:48 - Shoutouts
Resources * Functional Programming vs OOP * Lydia Halle’s blog post on the prototype chain * Practical Object Oriented Design in Ruby * Ali's What is Functional Programming? * What Tamagotchis Can Teach You About ES6 Generators - Jenn Creighton * CodeNewbie: How do Browsers Work? * What the heck is the event loop anyway? - Philip Roberts * Throttling and debouncing * Debugging Episode
The podcast and artwork embedded on this page are from Emma Bostian, Sidney Buckner, Kelly Vaughn, and Ali Spittel, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Code Chefs - Hungry Web Developer Podcast
Episode: The Javascript Event Loop
Pub date: 2020-08-22
How does Javascript handle concurrency? When you execute asynchronous code in Javascript, it goes through something called an Event Loop. It describes in what order your code will run by using a call stack and a callback queue. This is important to understand so you don't run into race conditions in your codebase. In this episode, we deep dive into how it all works!
Shownotes * 01:30 - Basics and why it matters
+ Javascript is single threaded
+ The event loop gives it Javascript the ability to handle concurrency and async code
+ It's useful for describing animation states
-
07:30 - The mechanics
- Browser initializes with v8 engine
- The event loop runs, and code executes top to bottom
- Two concepts - callstack and heap
- Callstack is FIFO (Last in first out) - like a stack of pancakes
- It describes when callbacks will occur when things are finished in that execution
- When nothing is left over in the callback queue, everything has been executed
- 12:30 Examples:
console.log("hello");
setTimeout(() => {
console.log("resolve timeout");
},5000)
console.log("last line");
Hello is logged, then resolve timeout is placed into a callback queue. last line is then logged. 5 seconds later, the callback queue is checked, and resolve timeout is logged.
What if you had a long list of executable code, and a setTimeout with a very short duration called in the middle?
console.log(1);
console.log(2);
console.log(3);
setTimeout(()=> {
console.log("set time out function")
}, 100);
//.....
console.log(1000);
The setTimeout function will still execute after all other code runs.
-
16:50 - Additional notes
- For async await, understand the order in which your promises are resolving.
- If two HTTP calls can be executed in parallel, use
Promise.all() - Stack vs Heap in Event Loops
-
22:00 - Dessert Time
-
22:40 - Swimming with Vincent
- 24:00 - Linux OS and GPUs with German
Social Media * German's Twitter * Vincent's Twitter * Vincent's Instagram * Tweet us your thoughts on @codechefsdev
Links * The event loop playground * Overview of Event Loops
The podcast and artwork embedded on this page are from Vincent Tang & German Gamboa, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 81. More Books
Pub date: 2018-09-25
Welcome back to another episode of The Rabbit Hole. Today on the show we are continuing our conversation on the books we’ve read within the last couple of months. This episode of books is a little different, because none of the books that we’ve currently read were programming books!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 87. Developer vs Engineer
Pub date: 2018-11-06
On today’s show we discuss whether we can call developers engineers! For a long time, the term software engineer has been thrown around but there has also been some debate about its accuracy and whether it is appropriate to use these titles so interchangeably.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 95. The Shackles of Frameworks
Pub date: 2019-01-01
In this episode of The Rabbit Hole we welcome our friend Jacob O’Donnell to help us talk about the shackles of frameworks.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 76. Stop talking about Tech Debt with Dane O'Connor
Pub date: 2019-01-10
This is a special throwback Thursday re-release of one of our favorite past episodes, as we lead up to our 100th episode!
On today’s show, we welcome our friend Dane O’Connor, who is here to tell us why we need to stop using the term ‘tech debt’. As a commonly used phrase in today’s developer community and in so much business, there can be a lot of sensitivity and potential issues that are connected to the term.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 97. Mocks vs Classical with Jacob O’Donnell
Pub date: 2019-01-29
On the show today we are welcoming back our friend Jacob O’Donnell to talk about some different approaches to testing.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 102. Digging Into JavaScript w/ Jonathan Wexler
Pub date: 2019-03-26
On today’s episode, we are joined by Jonathan Wexler, a software engineer who specializes in web development and teaching concepts related to development.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 105. BDD
Pub date: 2019-04-16
On today's episode, our host Dave Anderson and producer William Jeffries discuss end to end testing.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 123. Pragmatic Folks Part 3 - The Dogmatic Developer
Pub date: 2019-08-20
On the final episode of our three-part series with Dave Thomas and Andy Hunt, we discuss the nuanced nature of programming and why the idea of a “best practice” is often idealistic and not equally relevant to everyone.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 122. Pragmatic Folks Part 2 - Own Your Environment
Pub date: 2019-08-13
Today's episode is the second of a three-part Pragmatic Folks series and we are joined again by Dave Thomas and Andy Hunt, authors of The Pragmatic Programmer, to talk more in-depth about how you are in control of your own destiny even when it seems like you’re not.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 121. Pragmatic Folks Part 1 - Feedback Loops
Pub date: 2019-08-06
Today's episode is the first of a three-part Pragmatic Folks series and we are joined by Dave Thomas and Andy Hunt to talk about the 20th anniversary edition of The Pragmatic Programmer. This new edition was not only an opportunity for them to revise the material but also to revisit their thinking and see how ideas have changed over the course of twenty years.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 135. Stronger Strong Types
Pub date: 2019-11-12
Today on The Rabbit Hole we are talking about strongly typed and loosely typed languages. There is very little industry consensus about what these terms mean and it is not uncommon to find often contradictory definitions, so we take it upon ourselves to uncover the truth and what we find is rather surprising! Languages that we initially thought of as strong proved not to be as iron-clad as we thought and our previous thinking about loosely typed language also had some holes.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 138. User Stories: Why "gathering requirements" is not a gorram story
Pub date: 2019-12-03
As much as we hate breaking bad news to you, we have no choice today. If you think gathering requirements is a user story, you are wrong and we’ll tell you why. William, who is especially fired up about the topic, gets us started by explaining that usually gathering requirements is conflated with other components, such as a spike, task or research and there are also often delusions about what stories are.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: Remix: The DRY Principle is Misunderstood with Steven Solomon
Pub date: 2020-01-21
Today on The Rabbit Hole, we are doing another remix, this time going back to an episode with Steven Solomon on how the DRY principle is misunderstood. Steven has been a programmer since 2007 and has been fortunate to work in many contexts. In this episode, Steven unpacks what the DRY principle is and clears up some common misconceptions about it. Commonly when developers see two lines of the same code, they are tempted to extract that into a method based on their understanding of DRY-ing.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 147. Client Side Caching
Pub date: 2020-03-03
Caching is notoriously difficult. In fact, according to Dave, it might be one of the two (or three) hardest problems in computer science. In this episode, dedicated to all the cache money millionaires, we are talking about client-side caching. We look at how it’s different from server-side caching and why, if you want to improve user experience, it’s the way to go. While client-side caching only helps the client currently using the machine, there are some definite benefits that we walk through, particularly on larger websites.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 151. Interfaces + Design Patterns
Pub date: 2020-04-07
Dave recently used Golang for a project he was working on, and today he shares his experience of interfaces and design patterns in the language. We kick off the show by talking about the Gang of Four, where Mike reveals what we have long suspected – he’s not a real developer after all! We then talk about how Go is different from other languages in that you have to explicitly define the interface and then you have a file with an interface in it. This means that when you write the code that implements the interface, you don’t explicitly say what it’s doing. It's all a big secret!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 155. "I don't know anything" -- It's OK to not know, It's what you do after you know you don't know
Pub date: 2020-05-12
Admitting that you don’t know something can often be a bitter pill to swallow. Rather than beating yourself up about it, why not see it as an opportunity to learn something new? So rather than saying, “I don’t know,” choose to say, “I don’t know YET.” This way you can remain open to delving deeper into a subject, no matter how experienced you are.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 157. Vue - New Hotness or New Hype
Pub date: 2020-05-26
We know with JavaScript, there’s a new framework basically every week, so it can be hard to separate the hotness from the hype. If you're ready to move on from jQuery, then Vue is a worthy candidate. Since its inception in 2013, Vue has steadily been gaining popularity, and today we dive in to see what all the fuss is about. We kick the episode off by learning more about the origins of Vue and how it took all the best parts of Angular but made it more lightweight.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 162. SOLID - Single Responsibility Principle
Pub date: 2020-06-30
Do you know how you can feel overwhelmed when you have too much on your plate? Well, your code can feel the same way. This is why it’s important to follow the Single Responsibility Principle, SRP, which is what the ‘s’ in SOLID stands for. Today we do a deep dive into the SRP and how you can ensure that your class or object only does one thing at a time. We take a look at some of the benefits of following the SRP, such as ease of testing and greater flexibility with making changes. When there is more than one responsibility designated to a class, it can quickly become confusing when you need to alter a piece of code. We also look into why you should try to keep classes as small as you can, how to know if a class or object has more than one responsibility, and why you should always be ready to refactor.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 163. SOLID - Open-Closed Principle
Pub date: 2020-07-08
As part two of our series that explores the SOLID software design principles, this episode dives straight into the topic of the open-closed principle — that’s the ‘O’ of SOLID for those who are counting. As a software principle created in 1988, back in the days of C++, the essence of this principle states that you should create code that’s “open for extension but closed for modification.” Using the example of needing to create a calculator that measures the areas of rectangles, we talk about how the open-closed principle makes it easier to create an extension to your area calculator if you suddenly need to calculate the area of a circle. While this principle makes it easier for developers to add features to your software, we discuss how needing to perform “shotgun surgery” on your code may be a sign that you haven’t adhered to the open-closed principle. For a real-world example, we share how we’ve implemented the open-closed principle into an intranet project that we’re developing. Near the end of the episode, we talk about how following the open-closed principle helps ensure that you’re following the other SOLID principles. Listen to this episode and learn how important the open-closed principle is to writing good code.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 166. SOLID - Liskov Substitution Principle
Pub date: 2020-07-28
For those of you who have been waiting for the next letter of the SOLID series, we are happy to finally discuss the 'L' in SOLID, which is the Liskov substitution principle, or as we like to call it, the LSP. If you’re like us and the LSP conjures up an image of a long-gone mathematician, think again. It is actually a principle developed by Barbara Liskov, an American computer scientist. In this episode, we get into a simple definition of the LSP, which is that objects should be replaceable with their sub-types, and this should not alter the functioning of the program. To clarify, we use an example of shapes in a program and how the principle would be applied. We also look at how the LSP relates to inheritance, and why inheritance should only be used in certain circumstances. Along with this, we touch on our feelings about interfaces and learn more about William’s experience with TypeScript. Tune in today!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 168. SOLID - Interface specificity principle
Pub date: 2020-08-11
We’re back on SOLID ground. Today we explore the ‘I’ in SOLID, A.K.A the interface segregation principle or ISP. After debating how inappropriately the principle is named, we dive into what it means, that “no client should be forced to depend on methods it does not use.” We drill even further into what this means by using the metaphor of a Swiss Army knife and what it would take to code an athlete in Java. We discuss why you should apply the ISP and later share experiences where we’ve abandoned the principle, intentionally or not.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 172. Accessibility 2
Pub date: 2020-09-08
Imagine you’re browsing a web page using only a keyboard. A loud and looping video pops up that’s impossible to close without a mouse. Now you’re trapped there. Forever. This horror story is commonly experienced on websites that haven’t been designed with accessibility in mind. This episode continues our discussion on what you should do to improve your accessibility. After talking about using tools like voice-over commands to understand what’s needed from the user’s perspective, we touch on the challenge of learning the right commands to navigate the web with your eyes closed. We then tackle the rest of UC Berkeley’s list on making accessible websites, highlighting key considerations including color choice, how you should design forms, not using tables in place of styling, ensuring that everything can be accessed through a keyboard, and making dynamic content accessible. We also chat about ARIA roles and landmarks and why creating accessible websites leads to a better experience for able-bodied users. Tune in for more insights on making great and accessible websites. Not only will it expand your user-base but it’ll help ensure that no one ends up within the dreaded carousel of modals.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 171. Accessibility
Pub date: 2020-09-01
We’ve all been there. You’re trying to close an ad on your browser, but the button is too small and you’ve accidentally opened it instead. Poor web design can easily frustrate even the most agile-fingered, able-bodied techies. Imagine what it’s like for users with challenges that can range from visual impairment to limited motor function. On today’s episode, we explore how and why you should build accessible websites. We start by talking about alt text and how the show’s hosts have, to their shame, often neglected to create informative alt text. We then touch on the work that W3C is doing to establish guidelines on making accessible websites.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 176. Kubernetes VS Serverless
Pub date: 2020-10-13
Kubernetes versus serverless – the battle of the decade! Both deserve their status as exciting and powerful platforms that offer organizations tremendous boosts in agility, scalability, and computing performance, but it is easy to forget that Kubernetes offers advantages that serverless alternatives don’t — and vice versa. In this episode, Michael Nunez, Dave Anderson, and William Jeffries discuss the pros and cons of each platform, what it is like working with Kubernetes versus serverless on a project, and compare the complexity, load, function call and time cost, as well as comparing different cloud hosting services. Tune in today for all this and so much more!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 190. CSS Animation
Pub date: 2021-01-19
With Flash set to discontinue from January 12th and the HTML blink tag obsolete, how will we animate our websites from now on? With this issue in mind, we decided to dedicate today’s show to the wonderful topic of animation! We discuss how best to tame this powerful and often misused beast as well as get into the tools at our disposal for doing so in CSS, JavaScript, and by using prebuilt libraries too. Animation definitely has a place in UI, but can easily look tacky and overdone, so we start our chat off exploring some best practices for keeping things tasteful and useful. From there, we get into a few of the technicalities of building animations in CSS, highlighting the power of keyframes as well as some of the kinks in this new feature that still need to be worked out. Toward the end of our chat, we speak about the great functionality provided by animation frameworks like React’s Spring library, animate.style, and the Web Animations API. So even though Flash is a thing of the past, there is no need to cry, because there are plenty of tools in CSS and JavaScript that will keep us building beautiful animations on our websites well into the foreseeable future. Tune in to learn more!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 194. Continuous Integration
Pub date: 2021-02-16
Continuous integration is the peanut butter to the jelly of continuous delivery, and it’s also the topic of today’s episode. We are talking all things CI, including some of the benefits and downsides and a whole lot more. We kick off with a definition of CI, where we discuss how it helps reduce bugs.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 195. Continuous Delivery
Pub date: 2021-02-23
Building on last week's episode about continuous integration, today we explore the idea of continuous delivery and whether it is the best way forward. We start off with some basics, defining continuous delivery and what can truly fall into this category. From there we weigh the value of a deployment button and the difference that this single step in the process can make. William makes a strong case for why full automation and real continuous delivery is a better approach and how this philosophy will force developers to take up more responsibility and acquire better tools for their part in the process.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 203. Definition of Done
Pub date: 2021-04-27
Today we are speaking about getting things done! What does it mean when we say something is done and how can you and your team get a better handle on the concept for better products? At times, as developers, we might feel like we are done as soon as the code is written and passed, but in reality, there are more steps in the process, and to get to a real state of being finished we need to formulate a proper framework or checklist for being done! This is one of the issues with working with different teams, as responsibility can sometimes get a bit lost, and so putting some time in, to develop an appropriate way to measure completion can lead to fewer issues and confusion down the road. In today's episode, we also look at the important aspects of feedback and corrections, and how 'done' might be a relative term, especially as your products gets increasingly complex. So for all this and a few more thoughts on how you can move things into that beautiful 'done' column, come with us, down the Rabbit Hole!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 228. When to Pair Program
Pub date: 2021-11-02
In today’s episode of The Rabbit Hole, Dave Anderson and Sophie Creutz attempt to answer the question: when should you pair program and what should you pair on? We apply the basic principles of pair programming to a non-programming task like reading documentation, using an article about learning organizations as an example. Hate pair programming? Well, we also touch on how you can reframe it as deep collaboration and view it as a skill that you can work on. Stay tuned for practical advice and helpful resources, plus so much more!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 229. Agile Manifesto
Pub date: 2021-11-09
In today's episode of the Rabbit Hole, we are joined by our friends Sophie Creutz and Raymond Lam to take a shot at unpacking the Agile Manifesto! We often speak about the Agile approach and thought we would take it down to the foundational level, speaking about the components of this essential tool for developers and teams.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 230. Progressive Performance
Pub date: 2021-11-16
In some respects, we have moved on from the trend to overload web pages with too many features, but it is still worth emphasizing why performance should be at the top of your list of priorities. Today we talk about progressive performance and some interesting ways to approach and think about creating the most user-friendly websites possible. To do this, we break down why this is necessary and how to go about it; from tools and tricks to the studies that have shown how users react to load times, and buggy pages. So to hear about how you can get away with slightly slower speeds, and why learning about the tools that you will be using to tackle these issues is so important, make sure you come down the Rabbit Hole with us, today!
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Rabbit Hole: The Definitive Developer's Podcast (LS 39 · TOP 2% what is this?)
Episode: 169. SOLID - Dependency inversion principle
Pub date: 2020-08-18
Today’s show marks our reaching of the final letter in our discussion of SOLID, the D, which stands for the Dependency Inversion principle! We kick things off with a bit of research on exactly what the Dependency Inversion principle states, and from there we unpack what implementing it in the real world might look like. Our conversation is all about the idea that pieces of your code should be decoupled and you can do this using interfaces. We discuss how the Dependency Inversion principle might be applied when you are connecting to databases, how it relates to inversion of control and ways of implementing it other than dependency injection.
The podcast and artwork embedded on this page are from Stride NYC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: mikrofonika \m/
Episode: 32. Olacak O Kadar
Pub date: 2021-09-18
Komedyen Emrecan Odabaş'la dediğişen mizah anlayışı üzerine nezih bir sohbet...
The podcast and artwork embedded on this page are from Podfresh: Ege Kayacan, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: mikrofonika \m/
Episode: 31. Göç Yolları
Pub date: 2021-09-10
Cem Vardar'la tersine beyin göçü hakkında nezih bir sohbet...
The podcast and artwork embedded on this page are from Podfresh: Ege Kayacan, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Shortsighted Podcast (LS 32 · TOP 5% what is this?)
Episode: 70% Better Eyesight, In 18 Months?! (Dan: -5.25 To -1.50)
Pub date: 2021-08-06
Another episode of awesome 20/20 gains. Dan asks lots of questions so if you're on the fast gains track and want to know how it will derail, this episode is for you.
The podcast and artwork embedded on this page are from Jake Steiner / Endmyopia, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Shortsighted Podcast (LS 32 · TOP 5% what is this?)
Episode: Dr. Morris Waxler: LASIK & Permanent Dry Eye Risks
Pub date: 2021-09-23
Dr. Morris Waxler is the former Chief of Surgical and Diagnostics Branch, Division of Opthalmic Devices at the FDA. He explains in great and lurid detail how you are entirely on your own, taking changes on LASIK. This is stuff none of the surgeons will tell you, and you probably really want to know before going in for this procedure.
The podcast and artwork embedded on this page are from Jake Steiner / Endmyopia, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Shortsighted Podcast (LS 32 · TOP 5% what is this?)
Episode: Josh: -4.50 To -1.75 (2 Year Progress)
Pub date: 2021-08-20
Another day, another episode another bunch of diopters untangled.
The podcast and artwork embedded on this page are from Jake Steiner / Endmyopia, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Shortsighted Podcast (LS 32 · TOP 5% what is this?)
Episode: Erik: -3.00 To -0.50 D Progress
Pub date: 2021-08-29
Well, this feat took Erik a little while, but all worth it in the end. Check out this progress episode!
The podcast and artwork embedded on this page are from Jake Steiner / Endmyopia, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Burn it Nutrition Podcast (LS 50 · TOP 0.5% what is this?)
Episode: Ep103: Get Your Vision to 20/20 and Ditch the Glasses with Jake Steiner of EndMyopia | The science of better vision
Pub date: 2021-04-13
- Jake Steiner and how he improved his vision back to 20/20
- What Myopia is and how it develops
- How wearing glasses impacts all aspects of life
- Ways our habits lead to poor eyesight
- Whats wrong with the 100 Billion dollar eyeglass industry
- How you can begin improving your eyesight
- How our diet impacts our vision
.
Links mentioned in this episode! .
Discounts mentioned on this show at https://burnitnutrition.com/podcast103/ .
.
.
Dry Farm Wines 1 Penny Bottle Here www.DryFarmWines.com/Burnit/ .
.
.
Ned Mello Magnesium Sleep Blend - 15% off your first order —WITH FREE SHIPPING: www.helloned.com/BURNIT and use code “BURNIT” .
.
.
Tonal Home Fitness System at www.TONAL.com promo code "BURNIT" for $100 OFF smart accessories .
.
Elysium Health Matter - Long term brain health, Use Promo code BURNIT for discount - get yours here www.ExploreMatter.com
.
.
.
Podcast Shop Page for 5th Stage Keto Body Transformation & Vitamin C Powder at https://burnitnutrition.com/shop
.
Learn more about Jake Steiner:
Website: https://endmyopia.org/
Facebook: https://www.facebook.com/groups/560893680770705
. Leave me a rating & review on Apple Podcasts: https://itunes.apple.com/us/podcast/burn-it-nutrition-podcast/id1195955730?mt=2 .
Follow Joseph Navarro on Instagram under @BurnitNutrition .
Follow Joseph Navarro on Facebook under @BurnitNutrition
.
Thank You for Listening!!
Please share this episode! Be the one who helps spark a transformation in your family!
Feedback to share? Send email to info@BurnitNutrition.com
Subscribe! Don’t miss another episode!
Some Music tracks were from:
Composer: Whitesand (Martynas Lau) Year: 2018 Title: Shadows Title: Emotional Piano Title: Redemption Mystery by GoSoundtrack, Reloaded by Savfk, Deep Blue by Pold, Ross Bugden Music all of the Mountain King" Kevin MacLeod Philae by Olivaw Creative Commons — http://creativecommons.org/licenses/b Notice of Sponsorship Affiliate Disclosure with Ned, Dry Farm Wines, Amazon, Tonal, Elysium
.
Please read the full medical disclaimer burnitnutrition.com/medical-disclaimer/
The podcast and artwork embedded on this page are from Joseph Navarro Fitness, Nutrition, Ketogenic, Paleo, Keto, Diet Coach, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Views on Vue (LS 36 · TOP 3% what is this?)
Episode: Episode 75: VoV 076: Typescript Tell All with Jack Koppa
Pub date: 2019-08-27
Sponsors * The Freelancers Show * Sentry– use the code “devchat” for two months free on Sentry’s small plan * GitLab | Get 30% off tickets with the promo code: DEVCHATCOMMIT * CacheFly
Panel * Chris Fritz * Ben Hong * Ari Clark
Joined by Special Guest: Jack Koppa
Summary Jack Koppa, a frontend developer at Politico, joins the panel to discuss the adoption of Typescript at Politico. Having a background in Angular, React and Vue, Jack compares the onboarding process for all 3 frameworks. Jack Koppa explains why Politico decided to switch to Typescript and shares his experiences during the change. The panel discusses the reactions of the other developers at Politico and Jack explains the learning curve and eventual acceptance of Typescript among the Politico developers.
Typescript can solve many problems and the panel expounds on those while also addressing the drawbacks of using Typescript. While Typescript has a learning curve, can take up time to write and the need to be meticulous is very high, Typescript also adds type security, finding typos and mistakes, and provides clarity to the team and consistency for the front and back ends. Ari expresses her desire to use Typescript in a current project at Liquid and the panel gives her advice on the best way of bringing in Typescript late into a project. At the end of this episode, Chris Fritz explains what it means for Vue developers since Vue 3.0 will be written in Typescript.
Links * https://www.politico.com/ * https://twitter.com/jackpkoppa?lang=en * https://github.com/jackkoppa * https://www.facebook.com/ViewsonVue * https://twitter.com/viewsonvue
Picks Ben Hong:
- Comic Con
- Stardew Valley
- Educated: A Memoir
Ari Clark:
- https://softskills.audio/
Chris Fritz:
- In Vue, When Do I Actually Need the :key Attribute and Why?
- https://beatsaber.com
- https://beatsaver.com/
Jack Koppa:
- https://overreacted.io/react-as-a-ui-runtime/
- Aurora
Special Guest: Jack Koppa.
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Full Stack Radio (LS 52 · TOP 0.5% what is this?)
Episode: 144: Gary Bernhardt - TypeScript and Testing
Pub date: 2020-08-05
Topics include:* Why Gary decided to write Execute Program as a full-stack TypeScript application instead of using a Ruby or Python backend like he may have traditionally * Do you actually have to write less tests if you have a good type system? * What does a good type system give you that tests can't give you? * Using io-ts to type check incoming data * How to think about structuring your code to best take advantage of the benefits your type system gives you and minimize the need to write tests * Pushing conditional logic to the core of your system to reduce the number of tests you need to write at the edges * The correlation between type errors and behavioral bugs, and how a type system can help you catch mistakes you don't think to test for * Do type errors signal that you're missing a test? * Structural vs. nominal type systems, and the benefits of structural type systems like used by TypeScript and Go * Best practices for type-checking within a function in a structural type system like TypeScript * The power of supporting literal types like true or "active" in addition to traditional types
Links:* Destroy All Software * Execute Program * TypeScript * "Are tests necessary in TypeScript?" * io-ts * TypeScript course on Execute Program * Gary's tweet about unions with literal types
Supporting the show:
I decided to stop taking sponsors for the show because I think advertisements are annoying and no one wants to listen to them.If you do want to support the show, the best way to do it is to purchase one of my products:* Tailwind UI, a collection of professionally designed, fully responsive HTML components built with Tailwind CSS.
* Refactoring UI, a book and video series I put together with Steve Schoger on designing beautiful user interfaces, without relying on a designer.
* Advanced Vue Component Design, a course on designing simpler, more flexible Vue components that are both more powerful and easier to maintain.
* Test-Driven Laravel, a massive video course on designing robust Laravel applications with TDD. Learn how to build a real-world application from scratch without writing a single line of untested code.
* Refactoring to Collections, a book and video course that teaches you how to apply functional programming principles to break down ugly, complex code into simple transformations — free of loops, complex conditionals, and temporary variables.
The podcast and artwork embedded on this page are from Adam Wathan, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: COMPRESSEDfm (LS 30 · TOP 10% what is this?)
Episode: 32 | Getting Started with TypeScript
Pub date: 2021-10-25
In this episode, James and Amy discuss everything you need to know to get up and running with TypeScript: what is TypeScript, why use TypeScript, the basic types, and how and where to go to get started.
SponsorsVercelVercel combines the best developer experience with an obsessive focus on end-user performance. Their platform enables frontend teams to do their best work. It is the best place to deploy any frontend app. Start by deploying with zero configuration to their global edge network. Scale dynamically to millions of pages without breaking a sweat.
For more information, visit Vercel.com
ZEAL is hiring!ZEAL is a computer software agency that delivers “the world’s most zealous” and custom solutions. The company plans and develops web and mobile applications that consistently help clients draw in customers, foster engagement, scale technologies, and ensure delivery.
ZEAL believes that a business is “only as strong as” its team and cares about culture, values, a transparent process, leveling up, giving back, and providing excellent equipment. The company has staffers distributed throughout the United States, and as it continues to grow, ZEAL looks for collaborative, object-oriented, and organized individuals to apply for open roles.
For more information visit softwareresidency.com/careers
DatoCMSDatoCMS is a complete and performant headless CMS built to offer the best developer experience and user-friendliness in the market. It features a rich, CDN-powered GraphQL API (with real-time updates!), a super-flexible way to handle dynamic layouts and structured content, and best-in-class image/video support, with progressive/LQIP image loading out-of-the-box."
For more information, visit datocms.com
Show Notes 0:00 Introduction
+ Episode #13 - No Code
* 3:27 What is TypeScript?
* 8:08 Sponsor - ZEAL
* 9:40 TypeScript and Bugs
+ Kent C Dodds
+ Testing JavaScript
+ No Sweat ES Lint
+ Introduction to Testing on YouTube
* 17:08 Sponsor - Vercel
* 18:15 Typescript within VS Code
* 19:49 How to Get Started?
+ Linter
+ Number Blocks on Netflix
* 23:03 Different Types
+ String
+ Number
+ Boolean
+ Enums enum roles {
Admin = "ADMIN",
User = "USER",
Member = "MEMBER",
}
// or
enum roles {
Admin = 1,
User = 2,
Member = 3
}
+ Tuples
let x: [string, number];
x = ["hello", 10]; // OK
x = [10, "hello"]; // Error
+ Any
* 28:45 Taking it to the Next Level: Types vs. Interfaces
+ Types type person = {
firstName: 'Amy',
lastName: 'Dutton'
}
+ Interfaces
interface person {
firstName: 'Amy';
lastName: 'Dutton';
}
* 30:38 Sponsor: DatoCMS
* 31:32 Resources to get Started Learning TypeScript
+ React and TypeScript, Getting Started
+ Level Up Tutorials
- Level 1 TypeScript
- React and TypeScript for Everyone
+ TypeScript in 50 Lessons
+ When Should I use TypeScript (Feed Code Camp)
* 33:13 Grab Bag Questions
* 33:24 Types vs Interfaces
* 33:36 When is it appropriate to use TypeScript?
* 36:21 When is it a good idea to migrate a React project to TypeScript?
* 38:22 Which would you recommend? Going deeper on TypeScript or going deeper in React?
* 40:40 TypeScript vs JS Docs
* 42:32 Picks and Plugs
* 42:44 James's Pick - AirPods Pro
* 43:58 James's Plug - Code Connector Group in Slack
* 44:29 James's Plug - Virtual Coffee in Slack
* 44:50 Amy's Pick - Pock App
* 45:39* Amy's Plug - Advent of JavaScript and Advent of CSS
The podcast and artwork embedded on this page are from James Q. Quick, Amy Dutton, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Clean Architecture – Components and Component Cohesion
Pub date: 2017-12-11
Joe is down with OCP, Michael argues DRY, and Allen deletes our show notes as we dig into Components and Component Cohesion from Robert C. Martin's (aka Uncle Bob) Clean Architecture.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Clean Architecture – How to Quantify Component Coupling
Pub date: 2018-01-08
Joe baits Michael, Michael takes the bait, and Allen lets it happen, as Uncle Bob explains how we can quantify the coupling between our components from his latest book, Clean Architecture.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Google’s Engineering Practices – What to Look for in a Code Review
Pub date: 2020-05-26
We learn what to look for in a code review while reviewing Google's engineering practices documentation as Michael relates patterns to choo-choos, Joe has a "weird voice", and Allen has a new favorite portion of the show.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Google’s Engineering Practices – Code Review Standards
Pub date: 2020-05-11
We dig into Google's engineering practices documentation as we learn how to code review while Michael, er, Fives is done with proper nouns, Allen can't get his pull request approved, and Joe prefers to take the average of his code reviews.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Specialize or Bounce Around?
Pub date: 2021-03-01
It's been a minute since we last gathered around the water cooler, as Allen starts an impression contest, Joe wins said contest, and Michael earned a participation award.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Clean Architecture – What is the Humble Object Pattern?
Pub date: 2018-03-07
It's time for another deep dive into Robert C. Martin's Clean Architecture as Joe puts us on the spot, Allen has a new mission, and Michael shares his Easter eggs.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Full Stack Radio (LS 52 · TOP 0.5% what is this?)
Episode: 135: Lessons Learned Building Tailwind UI
Pub date: 2020-03-04
Topics include:* What Tailwind UI is and why we decided to build it * How odd numbers can wreak havoc on a user interface, and how to avoid them * Crafting the perfect form control * Unexpected benefits of working with CSS Grid * Abusing single column grids just to use gap, and why we desperately need gap support in Flexbox
Links:* Tailwind UI
Supporting the show:
I decided to stop taking sponsors for the show because I think advertisements are annoying and no one wants to listen to them.If you do want to support the show, the best way to do it is to purchase one of my products:* Tailwind UI, a collection of professionally designed, fully responsive HTML components built with Tailwind CSS
* Refactoring UI, a book and video series I put together with Steve Schoger on designing beautiful user interfaces, without relying on a designer.
* Advanced Vue Component Design, a course on designing simpler, more flexible Vue components that are both more powerful and easier to maintain.
* Test-Driven Laravel, a massive video course on designing robust Laravel applications with TDD. Learn how to build a real-world application from scratch without writing a single line of untested code.
* Refactoring to Collections, a book and video course that teaches you how to apply functional programming principles to break down ugly, complex code into simple transformations — free of loops, complex conditionals, and temporary variables.
The podcast and artwork embedded on this page are from Adam Wathan, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Two's Complement (LS 31 · TOP 5% what is this?)
Episode: Semi-Solid Principles
Pub date: 2021-03-24
Matt and Ben join an argument on the Internet, which is always a productive and rewarding use of one's time. They discuss the SOLID principles from two different perspectives, and judge them. Listen in for the verdict. Then, Ben ponders how programmers learn, and whether sailors are happy. Matt gets a new puppy.
The podcast and artwork embedded on this page are from Ben Rady and Matt Godbolt, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Ruby Rogues (LS 32 · TOP 5% what is this?)
Episode: Episode 503: RUBY 489: Demystifying Webpack and Webpacker with Paweł Dąbrowski
Pub date: 2021-03-09
Paweł Dąbrowski wrote a Deep Dive into Webpacker on his blog. He joins the Rogues to help the understand more of the ins and outs of Webpack and Webpacker for Ruby on Rails developers.
He and the Rogues break down how to manage your JavaScript assets, how Webpacker thinks about them, and how to pull together a cohesive strategy for how to make JavaScript work in your Rails application.
Panel * Charles Max Wood * John Epperson * Luke Stutters
Guest * Paweł Dąbrowski
Sponsors * Forest Admin * Dev Heroes Accelerator
Links * GitHub | kirillian/shiplane
Picks * Charles- 16th Wedding Anniversary * Charles- Gmelius * Charles- Upper Deck Legendary: A Marvel Deck Building Game * Charles- Logitech ERGO K860 Wireless Split Keyboard * John- Baby Delight Snuggle Nest Dream Portable Infant Sleeper * Luke- Waveshare * Paweł- Rails 6 and Stimulus.js - a quick launch
Special Guest: Paweł Dąbrowski.
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: JS Party: JavaScript, CSS, Web Development (LS 44 · TOP 1.5% what is this?)
Episode: What even is a micro frontend?
Pub date: 2020-04-03
Jerod and KBall are joined by Micro Frontends in Action author Michael Geers to discuss (you guessed it) micro frontend architecture. We ask: what is the concept? How is it similar/different to micro services? Who is it best fitted for? How do you put it in practice? And much more.
Discuss on Changelog News
Changelog++ members support our work, get closer to the metal, and make the ads disappear. Join today!
Sponsors
- Rollbar – We move fast and fix things because of Rollbar. Resolve errors in minutes. Deploy with confidence. Learn more at rollbar.com/changelog.
- DigitalOcean – DigitalOcean’s developer cloud makes it simple to launch in the cloud and scale up as you grow. They have an intuitive control panel, predictable pricing, team accounts, worldwide availability with a 99.99% uptime SLA, and 24/7/365 world-class support to back that up. Get your $100 credit at do.co/changelog.
- Pluralsight – Stay home. Skill up. Pluralsight is totally free for the entire month of April! With over 7,000 courses from experts in software development, security, cloud and data there’s never been a better time to skill up. Learn more and get started at pluralsight.com
Featuring
- Michael Geers – Twitter, GitHub, Website
- Jerod Santo – Twitter, GitHub
- Kevin Ball – Twitter, GitHub, LinkedIn, Website
Notes and Links
Comment on this episode for a chance to win a FREE copy of the eBook version of Micro Frontends in Action. Tell us what you think of micro frontends. Our 3 favorite comments will be selected 30 days from the date of publish for this episode.
ALSO be sure to use discount code podjsparty20 to save 40% on Manning’s entire catalog. Whether you want the print edition of Michael’s book or are interested in learning something else from their amazing library of books, we got the hook up. ✊
- KBall’s Microfrontends: the good, the bad, and the ugly
- The Book: Micro Frontends in Action
- micro-frontends.org
Something missing or broken? PRs welcome!
The podcast and artwork embedded on this page are from Changelog Media, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Ctrl Alt Delete (LS 61 · TOP 0.5% what is this?)
Episode: #172: Joanne McNally: On Comedy, Political Correctness & Storytelling
Pub date: 2019-01-01
The comedian Joanne McNally is one of my favourite new discoveries from the 2018 Edinburgh Fringe Festival. She burst onto the Irish comedy scene in 2014 and in less than a year became the co-host on RTÉ 2’s flagship comedy show Republic of Telly, co-wrote and starred in the stage show Separated At Birth a comedy about her adoption and performed sold out solo stand up shows all over Dublin. She's been nominated for multiple Dublin Fringe Festival awards including Best Performer and Best Production and been a guest on many late night TV shows.
Now, she's signed with famous comedy management Off The Kerb, and moved to London! We sat down in her offices to have a chat about everything, from how she got into comedy, how she finds inspiration for her shows, how to handle tough crowds, and her struggles from body image to break ups.
I love this episode and hope you do to!
Quotes:
"i don't want to be very PC. I'm not a worthy comic. I'm not trying to make a massive point about anything. I just want to have a good time, and I want my audience to have a good time."
"I have earnest fatigue."
"i don't want to be one of those tragedy tourists who are just constantly rolling out their sad stories to get likes."
See acast.com/privacy for privacy and opt-out information.
The podcast and artwork embedded on this page are from Emma Gannon, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Mentally Yours (LS 48 · TOP 1% what is this?)
Episode: Dopamine Nation
Pub date: 2021-10-18
We're in an age of over-consumption... That's how Dr Anna Lembke, Author of the book, Dopamine Nation, sees it. She jumps onto Mentally Yours to talk about how addiction works, how the brain works, and how society maybe isn't working so well...
Join our private Facebook group... www.facebook.com/groups/135088803805742
The podcast and artwork embedded on this page are from Metro.co.uk, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Daily Comedy News Podcast: a podcast about comedians (LS 40 · TOP 2% what is this?)
Episode: Chappelle Chills with the Transgender Jokes
Pub date: 2021-11-09
Audiences in San Francisco said Dave Chappelle did not do any transgender material.
Chris Rock took a shot at Kyrie Irving. Kyrie Irving took no shot.
Bill Burr's Immoral Compass lands on Roku (free!)
Neal Brennan loves Grand Theft Auto
T.J. Miller loves Spokane
Mo Amer is getting a Netflix special on November 30th and a new series with Ramy Yousef.
Kim Catrall joins the cast of How I Met Your Father
Facebook group: www.facebook.com/groups/dcnpod
Instagram is @dailycomedynews
Buy Me A Coffee: www.buymeacoffee.com/dailycomedynews
Goodpods: https://goodpods.app.link/2OUMliguTkb
The podcast and artwork embedded on this page are from Daily Comedy News / The Shark Deck, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Dr Justin Coulson's Happy Families (LS 54 · TOP 0.5% what is this?)
Episode: #263 A Transgender Question
Pub date: 2021-05-10
Warning - Content involves mature themes
Topics discussed in this episode:
- Justin responds to an email from a listener who is struggling with how to help their child
- Gender dysphoria
- 100% affirmation model within the medical field
- Gender fluidity
Purchase The Do's & Don'ts of Discipline or find it in our Happy Families Membership. Because a happy family doesn't just happen.
Find us on Facebook at Dr Justin Coulson's Happy Families
Email us your questions and comments at podcasts@happyfamilies.com.au
The podcast and artwork embedded on this page are from Dr Justin Coulson, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Vox Conversations (LS 75 · TOP 0.05% what is this?)
Episode: Rutger Bregman’s utopias, and mine
Pub date: 2019-07-22
Universal basic income. A 15-hour work week. Open borders.
These ideas may strike you as crazy, fantastical, maybe even utopian... but that’s exactly the point.
My guest today is Dutch historian Rutger Bregman, whose book Utopia for Realists is not only about utopian visions but about the importance of utopian thinking. Imagining utopia, he writes, “isn’t an attempt to predict the future. It’s an attempt to unlock the future. To fling open the windows of our minds.”
He’s right. And so this isn’t just a conversation about his utopia, or mine. It’s a conversation about how to think like a utopian, and why doing so matter most when the days feel particularly dystopic.
Citations:
The Lost Boys by Gina Perry
"Socially Useless Jobs" by Robert Dur and Max van Lent
"Economic Possibilities for our Grandchildren" by John Maynard Keynes
"I was a fast-food worker. Let me tell you about burnout." by Emily Guendelsberger
Book Recommendations:
Bullshit Jobs and Debt by David Graeber
A Paradise Built in Hell by Rebecca Solnit
The Entrepreneurial State by Mariana Mazzucato
The Ezra Klein Show has been nominated for best Society- culture podcast in this year’s People’s Choice Podcast Awards! Cast your vote for The Ezra Klein Show at https://www.podcastawards.com/app/signup before July 31st. One vote per category.
Please send guest suggestions for our upcoming series on climate change to ezrakleinshow@vox.com
Learn more about your ad choices. Visit podcastchoices.com/adchoices
The podcast and artwork embedded on this page are from Vox, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Capitalisn't (LS 52 · TOP 0.5% what is this?)
Episode: Is Discrimination Still Causing The Gender Pay Gap With Claudia Goldin
Pub date: 2021-10-07
If Claudia Goldin, Professor of Economics at Harvard University, wins the Nobel Prize in Economics next week, no-one will be surprised. Her work studying the intersection of gender and labor has been vital, both to the world and the field.
But there's a curious argument in her newest book "Career and Family: Women’s Century-Long Journey Toward Equity". Goldin says that though the gender pay gap persists, it's not clear that gender discrimination is the cause. She thinks that job design may be the real culprit, and that we need to rethink the flexibility and substitutability of work.
She joins us to discuss her book on this episode! Plus, in light of leaked internal research showing Facebook has known their products are harmful to kids and teenagers, we discuss whistleblowers and data-blackboxes for this week's capital is/isn't.
The podcast and artwork embedded on this page are from University of Chicago Podcast Network, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Verb (LS 43 · TOP 1.5% what is this?)
Episode: The Society of the Spectacle
Pub date: 2017-10-20
It's fifty years since the publication of 'The Society of the Spectacle' by the French writer and situationist Guy Debord. It's a book which continues to inspire artists and writers. Novelist Will Self argues that 'Never before has Debord's work seemed quite as relevant as it does now, in the permanent present that he so accurately foretold'. In this programme Will joins Ian McMillan, along with artist Paul Harfleet and writer Nick Harkaway to consider the idea of 'the spectacle', and, in the first of a new Verb series, Hollie McNish introduces new poetry from Keisha Thompson.
The podcast and artwork embedded on this page are from BBC Radio 3, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Revisionist History (LS 89 · TOP 0.01% what is this?)
Episode: The Powerball Revolution
Pub date: 2020-07-02
In Bolivia, a political activist radically reforms the voting process for... student council elections. Who else does he convince? Revisionist History. And maybe a fancy private school in New Jersey. Get Revisionist History updates first by signing up for our newsletter at pushkin.fm.
Learn more about your ad-choices at https://www.iheartpodcastnetwork.comSee omnystudio.com/listener for privacy information.
The podcast and artwork embedded on this page are from Pushkin Industries, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Psychology Podcast (LS 66 · TOP 0.05% what is this?)
Episode: Stoya || Foucault, Heteronormativity, and Good Porn
Pub date: 2019-06-06
Today it’s great to have Stoya on the podcast. Stoya has been working with sexuality for over a decade. Her writing credits include the New York Times, The Guardian, and Playboy. Her first book of essays, Philosophy, Pussycats, & Porn is available through Not A Cult Media, and her experimental porn project lives at ZeroSpaces.com. (Note: This episode is very explicit, so if that’s not your thing, please enjoy one of the other other 167 episodes of The Psychology Podcast. If you do listen to this episode, please stick around all the way to the end, as we really enjoyed tying it all together at the end of the episode!)
In this episode we discuss a wide range of topics, including:
- What is porn?
- What is good porn?
- Can there be feminism under capitalism?
- Stoya’s critique of “liberal feminists”
- The importance of values that transcend sexual preferences
- How our collective conception of “normal sex” leaves out a whole lot of sexual preferences that “normal” people have
- Focault on how preventing the discussion of sex is making us even more obsessed with sex
- The science of sexual fantasies
- Are there any sexual fantasies that are damaging to normalize?
- What we can learn about privacy from pornstars
- The benefits/disadvantages of choosing a porn career
- Comparing/contrasting BDSM with monogamy
- Why BDSM is too wide a category to be considered a sexual orientation
- Why Stoya has to be physically aroused in order to be creative in a porn scene
- How Scott and Stoya know each other
- Which author – from anytime thru history – would Stoya like to go out partying with? And what would her drink of choice be for such an occasion?
- The link between ADHD and creativity
Support this podcast: https://anchor.fm/the-psychology-podcast/support
The podcast and artwork embedded on this page are from Stitcher & Scott Barry Kaufman, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Psychiatry & Psychotherapy Podcast (LS 57 · TOP 0.5% what is this?)
Episode: The Big Five: Agreeableness
Pub date: 2020-10-22
In this episode, we continue our discussion on the Big Five. We will do a deep dive into agreeableness discussing it's sub facets: trust, straightforwardness, altruism, compliance, modesty, and tender-mindedness. We will also discuss the strengths and weaknesses of having high trait agreeableness.
Link to Blog.
Link to Resource Library.
The podcast and artwork embedded on this page are from David Puder, M.D., which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Hidden Brain (LS 85 · TOP 0.01% what is this?)
Episode: BS Jobs
Pub date: 2019-10-28
Have you ever had a job where you had to stop and ask yourself: what am I doing here? If I quit tomorrow, would anyone even notice? This week on Hidden Brain, we revisit our 2018 conversation with anthropologist David Graeber about the rise of what he calls "bullsh*t jobs," and how these positions affect the people who hold them.
The podcast and artwork embedded on this page are from Hidden Brain, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Rethink (LS 39 · TOP 2% what is this?)
Episode: David Graeber: Rethinking Jobs
Pub date: 2020-07-14
Author Graeber questions the purpose of our work.
The podcast and artwork embedded on this page are from BBC Radio, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Lie, Cheat, & Steal (LS 47 · TOP 1% what is this?)
Episode: Episode 39: Alan Sokal w/ Ben Cholok
Pub date: 2018-04-13
Ben Cholok comes by to talk to Pat about Alan Sokal and the Sokal Hoax.
The podcast and artwork embedded on this page are from Pat Sirois, Kath Barbadoro, Body Tape Intl. , which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Dr. Ruscio Radio: Health, Nutrition and Functional Medicine (LS 55 · TOP 0.5% what is this?)
Episode: Straight Talk On Weight Gain & Weight Loss
Pub date: 2019-12-04
Notes from Kutad Gubilik's Listen Later:
Hasn't proven to be effective diyir
Conventional weight loss advice often revolves around counting calories. However, although caloric intake does have a high correlation with weight gain—or loss—the counting approach hasn’t proven effective for most people. Neuroscientist Dr. Stephan Guyenet shares what is more likely to work: shifting your food quality and food environment. By understanding common craving triggers and how your brain causes you to feel full, you can painlessly lower your caloric intake. Get his tips for best results in this episode. https://drruscio.com/?p=47207
My book Healthy Gut, Healthy You is available at https://drruscio.com/getgutbook/
Looking for more? Check out https://drruscio.com/resources
The podcast and artwork embedded on this page are from Dr. Michael Ruscio, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The SAP - Comedians Talk Motivation, Dating and Relationships (LS 50 · TOP 1% what is this?)
Episode: #297 Learning To Be Less Agreeable
Pub date: 2018-08-13
Shannon Dee joins Dave Neal in studio. We talk about the birds and the bees, failed first kiss attempts, and knowing how to pick up on someone's vibes. Also, from breakup to makeup, how Shannon improved her relationship through communication.
The SAP is a place for comedians and other free thinkers to talk about their dating lives in a fun and open way. We discuss The Five Love Languages, The Superior Man, Codependency and how we are working to improve our relationships in this world. Hope you enjoy!
tags: bill burr, jordan peterson, agreeable, consent, feminism, codependency, five love languages, birds and the bees, sex talk, joe rogan,
The podcast and artwork embedded on this page are from Dave Neal and Tasha Courtney, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coach Corey Wayne (LS 53 · TOP 0.5% what is this?)
Episode: Mindsets, Monogamy, Marriage & MGTOW
Pub date: 2019-03-12
The importance of success mindsets, modern forms of monogamy in relationships and marriage and why some men are choosing to forgo relationships altogether and join groups of men who are going their own way or MGTOW.
In this video coaching newsletter, I discuss two different emails from two different viewers. The first email is from a guy who is so focused on blaming other people for his lack of success with women, that he is unable to see how his game is not working and what he needs to do instead to achieve the success he really wants and deserves. He has become stuck and frozen his ability to become any better with women because of the limiting story he has created about himself and how women feel about him. The second email is from a guy who asks my opinion on the movement MGTOW, or Men Going Their Own Way, who have given up on dating and participating with women in any kind of romantic way. The have exiled themselves from the land of women.
If you have not read my book, “How To Be A 3% Man” yet, that would be a good starting place for you. It is available in Kindle, iBook, Paperback, Hardcover or Audio Book format. If you don't have a Kindle device, you can download a free eReader app from Amazon so you can read my book on any laptop, desktop, smartphone or tablet device. Kindle $9.99, iBook $9.99, Paperback $29.99 or Hardcover 49.99. Audio Book is Free $0.00 with an Audible membership trial or buy it for $19.95. Here is the link to Audible to get the audiobook version:
http://bit.ly/CCW3Man
Here is the link to Amazon to purchase Kindle, Paperback or Hardcover version:
http://amzn.to/1XKRtxd
Here is the link to the iBookstore to purchase iBook version:
https://geo.itunes.apple.com/us/book/how-to-be-3-man-winning-heart/id948035350?mt=11&uo=6&at=1l3vuUo
Here is the link to the iTunes store to purchase the iTunes audio book version:
https://geo.itunes.apple.com/us/audiobook/how-to-be-a-3-man-unabridged/id1106013146?at=1l3vuUo&mt=3
You can get my second book, “Mastering Yourself, How To Align Your Life With Your True Calling & Reach Your Full Potential” which is also available in Kindle $9,99, iBook $9.99, Paperback $49.99, Hardcover $99.99 and Audio Book format $24.95. Audio Book is Free $0.00 with an Audible membership trial. Here is the link to Audible to get the audiobook version:
http://bit.ly/CCWMY
Here is the link to Amazon to purchase Kindle, Paperback or Hardcover version:
https://amzn.to/2TQV2Xo
Here is the link to the iBookstore to purchase iBook version:
https://geo.itunes.apple.com/us/book/mastering-yourself-how-to-align-your-life-your-true/id1353139487?mt=11&at=1l3vuUo
Here is the link to the iTunes store to purchase the iTunes audio book version:
https://geo.itunes.apple.com/us/audiobook/mastering-yourself-how-to-align-your-life-your-true/id1353594955?mt=3&at=1l3vuUo
Here is the link to purchase Official Coach Corey Wayne branded merchandise (T-Shirts, Mugs, etc.):
https://teespring.com/stores/coach-corey-wayne
Click the link below to book phone/Skype (audio only) coaching with me personally:
http://www.understandingrelationships.com/products
Click the link below to make a donation via PayPal to support my work:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LKGTSSLYJ93J6
Click the link below to read my FREE self-help articles:
http://www.understandingrelationships.com/
From my heart to yours,
Corey Wayne
The podcast and artwork embedded on this page are from Coach Corey Wayne, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Reader's Journey (LS 46 · TOP 1% what is this?)
Episode: 8. Alan Jacobs: How to Get More Pleasure Out of Your Reading
Pub date: 2020-08-18
My guest today is Alan Jacobs, the author of The Pleasures of Reading in an Age of Distraction. Jacobs is a scholar of English literature, writer, and literary critic. He is a distinguished professor of the humanities at Baylor University.
In his book, Jacobs offers an insightful and playfully guide on how to make reading pleasurable and enjoyable. You'll learn why you probably don't want to read only Great books, the benefits of writing in your books, the truth about speed reading, and many more wonderful reading tips.
TIMESTAMPS:
- [00:39] About Prof. Alan Jacobs & growing up a reader
- [02:56] Thoughts on How To Read A Book by Mortimer Alder
- [06:26] The truth about giving book recommendations
- [09:53] The difference between liking to read & liking to have read
- [11:26] Why you probably don’t want to read only Great books
- [14:35] Great books require a lot of your time, attention, and reflection
- [17:24] Niccolo Machiavelli’s relationship with books
- [21:26] The benefits of writing in your books
- [24:51] Pros and cons of reading on a Kindle
- [32:24] The truth about speed reading & why you may be reading too fast already
- [36:06] The benefits of rereading books
- [42:40] Two books that changed Alan's life
Learn more about the author:
- Website: ayjay.org
If you enjoy this podcast, please subscribe & leave a positive review.
Connect with Alex & Books:
- Twitter: @alexandbooks_
- Instagram: @alexandbooks_
- YouTube: Alex and Books
The podcast and artwork embedded on this page are from Alex & Books, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Audible Anarchism (LS 45 · TOP 1% what is this?)
Episode: Socialism from Below by George Woodcock, Chapter 3 - What is Anarchism
Pub date: 2020-07-25
Read the full text: https://zabalazabooks.files.wordpress...
George Woodcock (1912-1995) was a historian, political biographer, essayist, poet, and anarchist. He wrote biographies of such anarchist thinkers as Pierre-Joseph Proudhon, William Godwin, Oscar Wilde, and Peter Kropotkin. Throughout his life, Woodcock was given numerous awards for his work, but he refused several awards from the government of Canada on the grounds that he only accepted awards granted by his peers.
In this chapter, Woodcock dispels many of the common myths about anarchism, and he addresses the fundamental flaws of government, the state, and bourgeois democracy. He argues that if one is committed to both freedom and justice, the social philosophy of anarchism is the only tenable option.
The podcast and artwork embedded on this page are from audibleanarchism, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Stuff You Should Know (LS 90 · TOP 0.01% what is this?)
Episode: Can Anarchism Work?
Pub date: 2018-06-26
Teenage punks going through a phase probably come to mind when you think of anarchists, but anarchism is a legitimate political philosophy based on the idea that governments are unnecessary and do more harm than good. Could we actually live without them?
Learn more about your ad-choices at https://www.iheartpodcastnetwork.comSee omnystudio.com/listener for privacy information.
The podcast and artwork embedded on this page are from iHeartPodcasts, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: TED Radio Hour (LS 81 · TOP 0.01% what is this?)
Episode: Wired For Altruism
Pub date: 2019-01-25
(Original broadcast date: May 26, 2017). Helping others feels good, but why do some go farther than others? This hour, TED speakers explore ideas about altruism — what motivates us to be altruistic, what limits us and do we ever go too far. TED speakers include psychologist Abigail Marsh, clinical psychologist Cheryl Steed, philosopher Peter Singer, and writer Larissa MacFarquhar.
The podcast and artwork embedded on this page are from NPR, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Angular Air (LS 31 · TOP 5% what is this?)
Episode: ngAir 168 - Predictive Prefetching Using Machine Learning and Guess.js with Minko Gechev
Pub date: 2018-07-10
Support this podcast: https://anchor.fm/angularair/support
The podcast and artwork embedded on this page are from Angular Air, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: All Songs Considered (LS 67 · TOP 0.05% what is this?)
Episode: All Songs Considered: The Year In Music 2019
Pub date: 2019-12-09
Lizzo, Billie Eilish and Lil Nas X dominated the headlines this year, but 2019 was much more than that. We look back at the music we'll remember most and the marks it left on our cultural landscape.
As we listened back to the past year in music we heard a lot of the cultural and political angst you'd expect in a turbulent (and relentless) news cycle. But the albums that seemed to resonate the most in 2019 were more personal and inward looking, overflowing with love and defiant optimism. Sharon Van Etten reflected on motherhood, Amanda Palmer shared stories of survival and David Bazan, back as Pedro the Lion for the first time in 15 years, returned to his childhood, making the personal universal. Brittany Howard wrote songs of healing on an album she named after and dedicated to her sister who died at the age of 13, while the members of the Rwandan group The Good Ones sang songs of forgiveness in the wake of unspeakable genocide.
For other artists, 2019 was a year of renewal. Angel Olsen, Michael Kiwanuka, Sleater-Kinney, Raphael Saadiq and more all reinvented their sound, pushing themselves in dramatic new directions as a testament to the resilience and restlessness of the creative spirit.
The podcast and artwork embedded on this page are from NPR, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: A Little About A Lot (LS 56 · TOP 0.5% what is this?)
Episode: Is Monogamy The Only Answer?
Pub date: 2019-02-04
In this week's episode, we talk all about our pet peeves and some interesting unpopular opinions we have.
The podcast and artwork embedded on this page are from The Sorry Girls, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Turkey Book Talk (LS 39 · TOP 2% what is this?)
Episode: Caner Yelbaşı on the Circassians in Turkey and the Ottoman Empire
Pub date: 2019-12-02
Caner Yelbaşı on “The Circassians in Turkey: War, Violence and Nationalism from the Ottomans to Atatürk” (IB Tauris/Bloomsbury). The book describes the course of Circassians in the Ottoman Empire and Turkey after they were driven from their north Caucasus homeland by the Russian Empire in the 19th century.
Become a Turkey Book Talk member to support the podcast and get English and Turkish transcripts of every interview, transcripts of the archive, access to a 35% discount on over 400 Turkey/Ottoman history books published by IB Tauris, and an archive of over 200 reviews covering Turkish and international fiction, history, journalism and politics.
The podcast and artwork embedded on this page are from William Armstrong, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Frontside Podcast (LS 28 · TOP 10% what is this?)
Episode: 109: What Do You Need in a JavaScript Framework?
Pub date: 2018-08-23
Guests:
- Brandon Hays: @tehviking | Blog
- Chris Freeman: @15lettermax
In this episode, former Fronsiders, Brandon Hays and Chris Freeman join Charles and Taras to talk about the difference between a framework and a library, whether or not React + Redux a framework in itself, red flags to signal that you’re actually building a framework, attributes of a good framework, how can you tell if you created a bad framework, and how you can make a bad framework better.
Resources:
- Test Sizes by Simon Stewart
This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC.
Transcript:
CHARLES: Hello everybody and welcome to The Frontside Podcast. My name is Charles. I'm a developer here at Frontside and today, we're going to be talking about the things that go into making a JavaScript framework. Because, hey, there's not enough of those in the world today, so we're going to talk about that and with me is Taras.
TARAS: Hello, hello.
CHARLES: And we've got two very special guests, who have a lot of experience with this topic. Mr Chris Freeman and Brandon Hays. Hey, guys.
CHRIS: Hi, there.
BRANDON: Hi, there. We're talking about the poofberry framework, right?
CHARLES: What's a poofberry?
BRANDON: There's a tweet that's going around right now that one of them says, "I don't know what I should be doing," and the next person says, "Oh, just use poofberry." What is that? It's like fluffnuts but the [inaudible]. Hey, dot, dot, dot. Then, it integrates with log bungler.
CHARLES: There's a reason that I'm dying laughing.
BRANDON: It's so true.
CHARLES: It's so true, laugh, cry, laugh, cry. Let's start with kind of a very basic assessment here. Because there's a lot of different things that you can use to compose the applications that you build but for some reason, some of these things are grouped and considered as libraries and some of them are considered frameworks. I don't know that the boundary is very clear like I'll know it when I see it type thing. Maybe, we can start with what is the difference between a framework and a library?
CHRIS: I have some thoughts of these. I feel like this is one of those questions that could easily just turn into an infinite bike-shed but I remember reading something a while ago that stuck with me for a long time. I'm pretty sure it's related to Java but that makes sense because if anyone is going to talking about frameworks, it's Java developers. But it was saying that the difference between a library and a framework is inversion of control and the idea is a thing that's a library is a thing where you are in control. You bring the library code into your code and it's up to you what you do with it.
In a framework, the framework code calls you as I think what it said. It's like, you call the library code, the framework code calls you and --
CHARLES: In Soviet framework.
CHRIS: Yeah, exactly. A framework says, "Here are a bunch of open spaces for you to put your code in and I will take care of the rest," versus a library is just like... I don't know, "Here's some things that you can use. It's up to you. What do you want to do with them?"
CHARLES: Right, so in kind of like [inaudible], that would be basically, a framework would be the thing that's got the main method. I think the same thing in JavaScript and when you call it, does it actually implement the main method. In JavaScript, it'll probably like in node. Under that definition, it would be like, "Are you the main scripts when you invoke node? Do you control the main script?"
If you were doing your own command line parsing, for example, you're looking at the process.rb and pulling off the command lines and doing all the things but even if you're using something like Yargs or option parser in Ruby, that's more of like a framework. I guess Yargs is a library because you're still implementing the script. You're instantiating the Yargs thing.
TARAS: React calls render to figure out what to convert to DOM. Does that make React the framework?
CHARLES: I think React as a library. That's a good question. What's the equivalent of the main method on the web?
CHRIS: I think there's a very clear distinction, especially if you look at React versus something like Ember and I'm sure Angular does this as well. In React, by default, to build a React thing, you're going to pull in React, you may write some components, you may import them elsewhere but the main method is that you have an index.html with some div in it and you are the one that has to call ReactDOM.render and you pass it like document.query selector or whatever and then, your top level component and that can be as simple as complicated as you like or you can have a webpack plugin do it or whatever else. But the onus is on you to actually take that React app and get it starting up on the page versus Ember, it's like, "There's an index.html. It's fully wired up." There is one point where you sit down and say, "Start my program here," like Ember abstracted all that away. To me, that's the main method for a frontend application.
CHARLES: Right and if you actually look at something that Ember generates, then look at index.html, they generate a script tag for you that instantiate your application and mounts it on an element. If you want to change that element, that's actually a configuration option that you can change but it still a configuration option that's consumed by the framework. In that sense, there is that inversion of control. I see what you mean like in React, you're the one who flicks off the first domino, like who's the prime mover. Is it you or is it the framework that knocks over the first domino?
BRANDON: I like Chris's explanation and I think it's elegant to say because I was thinking in terms of structure. If it imposes a structure on you but really, the structure is there, it's like one of those Ikea shelf systems for you to put stuff into. If you're trying to solve a problem, here's a shelving system for you to put stuff into, whereas a library is just the tool that you might get out to put something together. Something that's multi-purpose but doesn't impose any structure on you or a ton of structure on you. My question is what's the usefulness of distinguishing between the two?
TARAS: I think what's interesting and I had experienced this in a last couple of projects is that people, especially React when they kind of assume, because a lot of people entering to React not understanding the context within which React emerged and so, they're getting into React assuming that it has everything you need to build application that you need to build. A lot of them haven't necessarily built a single page application from scratch before and so, the jump into building something with React and then, it takes about a year for them to realize the full scope of all of the features that their application actually has and then, they kind of take a retroactive look and look like, "Okay, what do I have now?" and what emerges is that they've actually over the last year, they may be creating a framework without realizing that this is actually happening.
CHARLES: They've imposed the structure of saying, "Here's the shelving system. Books about geography go here. Books on English literature go there and so on and so forth."
BRANDON: But when you rolled your own framework, that's not how it goes. It's like, "You have to launch this balloon into the stratosphere to put a book on the shelf from geology." Taras, to your point, it sounds like the importance is setting expectations properly for people, so that they know what they're in for because kind of calling back to Ryan Florence's post a few years ago, you can't not have a framework. At some point, you will have a framework in order to ship something.
I would actually take it one step further. My friend, Kyle talks about this that library is the smallest unit that you're working within a framework but that still doesn't take your code to production and put it in a debugable state. You need a platform. It's arguable, if you're handling deployment tasks and debugging tasks and operating software in production, you now have a platform and it's fair to say that Rails crossed that threshold at one point. It's fair to say that Ember has probably crossed that threshold, if you combine Ember with CLI deploy and the CLI tooling and all of that stuff. This almost like acts as a platform if you're owning and maintaining the software in production.
CHARLES: Now, can I play devil's advocate here and say, the platform, is that necessarily predicated on a framework? Is there a pyramid where it goes library, framework, platform and one is built on top of the other? Why couldn't I have a library? Because what I'm hearing is the scope of concerns is just rendering HTML based on a state is a very small chunk. The actual scope of things that you need to do to get that code in production and have it be reliable and do all of the features that you want to do is just massive but why is that predicated on a framework?
For example, one thing you have is a bunch of libraries out there, like routing for managing the title tag, managing all these things that you have to do for managing deployment, for building your application, for compressing it. There's all these different libraries out there. What if there was one massive library that just picked a bunch of other libraries but I was still in control?
TARAS: I've actually seen this happen in the last of the projects. When people jump into building, they will eventually realize that they're building a platform but what happens before that is that they take user's requirements and they break those up by sections and then they assign them to a bunch of development teams who go and actually start to build. On one platform, they end up building five or six or 10 of siloed, packaged applications that have, in some cases, have their own dependencies, they have similar architecture, might not have similar architecture.
Each team kind of implements thing differently and there's an expectation that once you package these things as npm and then you install them into one package, to one application when you run build, it's just going to work together. That's where I think, with the framework, it does create a foundation for these verticals to be implemented using kind of common foundation. This is what a lot of times that as if you don't realize that what you're trying to set out to build, the way that the projects get managed quite often, especially for big applications, for big platforms is that, it creates this period of about two years, where there's a lot of confusion and there's a lot of duplication and then, you end up seeing code that it's hard to put in production.
CHARLES: Yeah, I agree. I'm curious then, because we'd started out talking about library and framework and talked about it takes two years to recognize that you're building a framework or you're building not a framework but a platform. Brandon, you said something very interesting. Rails for example, crossed the threshold of being more than a framework and actually, being a platform. What are the concerns of a platform that are beyond a framework? We talked about and using the kind of loose definition of a framework as being something where the framework create spaces for your code, to run your code so you can just take little dollops of code and they have one concern but the framework manages the coordination of the concerns but what's the next level?
BRANDON: For the purposes of this conversation, I may have muddied the waters a little bit because I think it's more interesting to talk about the transition and the level of which you've crossed the threshold from being a library or using libraries or collecting libraries, into maintaining a framework because it's where you're going to experience more pain more than likely, than to me, the idea from works on my machine, to deployed and supported across a lot of users, it sounds like it's more interesting but it's not where we experience most of our pain actually. From my experience, maintaining frontend single page applications most of the pain is actually getting the damn thing to work on your machine and getting the libraries to collectively work together and then, getting that to production, it kind of enters back into an area of more known unknowns.
I think that's a surprisingly a more mature ecosystem, still getting from this thing works on my machine to getting it out the door. That wasn't true when Rails was invented and so, Rails had to invent a lot of its own ecosystem around this stuff. Like I said, I don't want to muddy the waters too much.
I think to me, the interesting question is how do you know you've crossed this threshold? What pain points are exposed when you start crossing that threshold or when you're pushing the boundaries of that threshold? Because you should not be using a framework if you're using React to do a select dropdown. I think of it as, if you're using it the way to replace something you might do with a jQuery plugin five or 10 years ago, you're using React like it's a library. One of the questions that you brought up was is the combination of React and Redux is a framework and I would argue that it is but I kind of want to throw that out --
CHRIS: Oh, interesting.
CHARLES: I would say, it's two libraries stuck together to make a bigger library. It's like a monolithic library.
BRANDON: But by the time you're actually using that to do anything, maybe the third thing in there is like transitioning states when you transition routes. At what point is that threshold crossed? I didn't build most of the software that led me to some of the opinions that I have about this. This was actually Chris Freeman's, though. I may defer to you on this.
CHRIS: I think React + Redux constitutes if you look at what it does. You have like this view layer and this state layer. There's a set of opinions on there that is useful and there is the foundation for doing quite a bit but in my experience, you've already kind of alluded to this a little bit. I don't think it's a framework because as soon as you start using those two things, suddenly the next thing you hit is, "Wait. How do I handle asynchronous things?" There's a lot of different options for that. "Oh, now, I need to do routing. How do I incorporate routing into my React app but also in a way, that is amenable to state transitions in Redux but also, that is aware of the async stuff that I'm doing, that is going to possibly be triggered by my routes and by my Redux actions or by some other side of things?"
Suddenly, you are very quickly pulling out a bunch of other libraries but also, probably starting to build abstractions on top of them because you're already finding a lot of common patterns that you're repeating over and over as you incorporate more and more pieces of the stack and then, you're writing a lot of glue code. I think that's the point where suddenly, you look back and behind you is the footsteps of this framework that's been walking alongside you the whole time.
BRANDON: That is where I carried you, then dropped you, then sort of drowned you.
CHRIS: Yeah.
CHARLES: And then, kicked your core.
TARAS: I'd like to suggest a way to think about this. As you guys are talking about, it kind of occurred to me is that it seems to me that libraries concentrate on how and frameworks focus on the 'what.'
CHRIS: Oh, I love that.
TARAS: Because if you think about for example, React is how geostack efficiently update DOM, then Redux is how do you wire together state across multiple components that might be in different parts of state tree and if you look at, for example, a React router or a kind of a routing component is how do you choose which components you want to render when you navigates specific URL. Because those things by themselves are not a complete solution but when you combine them together, what you get is you have a way of saying, "When I navigate to specific URL, I'm going to load specific data, provide that data to components and then, I would have a way to navigate through a different URL when you click on a link."
From that, I think what happens when you get to the framework level is you actually have a kind of a bigger umbrella and under that umbrella, you have ways to address problems that you did not have previously. I think that's what framework does it is over time, it's a way of addressing concerns that cannot be addressed with a solution. They have to address with a collection of solutions and then, they provide a specific solution. I don't know if that's --
CHARLES: That actually sparked off a train of thought in my mind that perhaps what you really want to do is say, "I'm going to go a little bit like Lisp on you all," in the sense of every code at some point is data, that maybe every library, at some point is a framework. It's just that you can look and say, "What is the scope of the 'what' that I'm tackling." For some point, you can say like React is a framework. It creates this space where I can put my JSx, AKA the render function and I'm basically inverting control and so, what it is, it is a framework for efficiently rendering HTML or efficiently mapping an object to a fragment of DOM and then the DOM that gets generated from your render function, patching that into the HTML. You don't have to worry about that. There's that inversion of control. It creates that space but that's the only space that it creates.
From that perspective, React is a framework for generating HTML but that's all it is but it is a library for constructing applications. Does that make any sense? I think as you layer on concerns, your framework create spaces for you. You use your library code to put stuff in and so, in the same way, I think one of the key realizations, I'm going to call up like BigTest and I'm not going to take credit for this, which is actually a blog post that I read at Google. I can't remember what it is but we'll link to it in the show notes where he said, "There are no such thing as unit tests. There are no such thing as acceptance tests. There are just tests of varying scope." They're all acceptance tests. To use that one thing, they're all experiments. It's just what is the scope of the test that you're trying to accomplish and his argument was we want to make that scope as big as possible by default and then, where appropriate, you narrow down. Maybe, the framework library distinction is a little bit constructed, kind of a construction of our own minds and what really is there, there's just frameworks of varying scope.
BRANDON: Agreeing on a shared scope is actually probably the most important part of this conversation. We're referring to building end-to-end an application from data access to rendering to testing --
CHARLES: To deployment to routing.
BRANDON: Yeah.
CHARLES: To one day accessibility.
BRANDON: Yeah. Adding that into the discussion is like a baseline of what constitutes an application. It's the percentage of people that are able to actually use it, the people that are locked out from using it by ability. That's a very useful frame for the discussion. Let's agree on the scope of what an application is and then, coming back to what Taras was saying is basically, when you're talking about the 'how,' that's a decision point.
You hear a lot of people talk about decision fatigue in JavaScript and it's almost a played out trope at this point but it hasn't gone away as a problem, so what frameworks are doing is they're making a series of decisions for you that allow you to basically connect the pieces from end to end. Basically, somebody threw a rope bridge across the canyon and it doesn't have to be the best solution to get end to end but we have to solve the problem end to end.
If we agree on the places end to end and the problem is when you're building your own series of libraries, you're like, "I'm going to choose best in class of A, best in class of B, best in class of C," and that sounds really good but if you're trying to build a bridge across a canyon and you're building in 10 best of class sections, for the type of connection we're trying to make here in the middle, we're going to use the best in class here. The weak point is in the connections, so you had better be the world's foremost engineer if you're going to be the person connecting all these disparate pieces that are each best in class, in order to bridge this canyon.
That's the thing that's interesting to me and it's not even agreed in our industry that JavaScript-based web applications are a good thing or that the browser is web application runtime, those are things that are up for debate. But I think if we make that assumption, this is sort of the founding principle of where Ember came from and it executed to the best of its ability at the time and that philosophy is, I think you can prove it out in terms of results based on if you have two different applications, one of them is built by somebody trying to jam together best in class components and the other person is starting with an end to end solution with a community of people rallied around that solution. It's been interesting to watch those approaches play out over time. I know Chris has a very specific hands-on experience of having done both of these. I'm curious to get your hot take.
CHRIS: There's actually a concept that I think about a lot in relation to this question. It's something that I actually heard come up again recently so the timing was great but it's called hypocognition. The idea is hypocognition is when you either just like can't see or can't understand some kind of cognitive representation of something because you don't have the words for it. An example is in Western cultures, especially like in English speaking cultures, there are not that many words for the color blue but in a lot of other cultures, they have many, many words for the color blue. After doing a big study they found that these English speakers actually have a harder time recognizing different shades of blue, like more of them just look the same versus other cultures where their brains are actually wired to see all this variety because they actually have the linguistic representations for these ideas already.
When you were talking about maybe a library is a framework at some point, I think that's right on. I think one of the things that I think about a lot when talking about frameworks and seeing these debates happen on the internet about, "What is a framework?" but also like, "Do you even need a framework?" is obviously, there's a lot of people who absolutely... Like Ryan Florence. Ryan Florence clearly knows what a framework is. He knows what it takes to build a web application and he does not lack the words to define a framework versus a library. He's just made that choice and it's a very informed choice but I wonder if there's also a lot of people who are getting into web development for the first time and they look at something like a framework and it seems just absurd to anyone would want all of the things that like in Ember or in Angular is talking about, when they can make a basic UI with React and it's easy and fun and really cool.
But then this two-year path happens and they look back and they've learned a whole bunch and now it's like, "Ooh, you couldn't even have explained this to me before," because all of the words would have fallen on deaf ears but now suddenly, it makes a staggering amount of sense.
CHARLES: Right. I love that.
BRANDON: You have to make a bad one.
CHARLES: Just so that you can inherit the vocabulary to understand why you made a bad one. Now, you guys actually have some experience with this. Brandon, you gave a talk about it, which I think you should give more widely because it's fantastic but for those folks who may or may not be aware that they are walking this to your path, I want to talk first about what are the signs that you're walking along this path and then two, what are the consequences in terms of the cost you're paying for walking this path. Let's start with that first thing. What are the signs? How can you tell that I am building a framework?
CHRIS: I think one of the telltale signs and one of the biggest red flags that caused me and Brandon to have a very serious heart to heart about our own personal framework was when we hit the point where you could look at a set of tickets for features and all you saw was 'framework features' that you needed to write before you could build the feature itself. You know like, "Oh, we have basic routing setting and we have it set up so that if you have a route transition and you would like a data request to happen when a certain route transition happens, that will happen," but then someone would like infinite scroll and we want to use a query param. When a query param changes, I want to update the query and fetch more records, except that the glue code that we wrote to tie our router to our redux async stuff is not aware of query params. It has no concept of what a query param is or what to do when it changes. Also, it has no concept of refetching the data without a full route transition, so what do we do, this person wants infinite scroll but I first have to implement several layers of framework code before I build the UI feature that you want?
CHARLES: The basic heuristic there is ratio of direct feature code to code that supports the direct feature code and code that supports the code that supports direct feature code. It's anytime you're anywhere above that first layer on the stack.
CHRIS: Yeah, I think Taras nailed it like what's the 'what' versus the 'how.' If you're asked a question that is concerned with the 'what' and you spend more time focused on the 'how,' then you might have a framework.
BRANDON: I think people will think of building an application like a recipe. If you think of it in those terms, people think of frameworks as very restrictive but I'm a big fan of Blue Apron, a sponsor of this podcast. Thank you.
They pre-select the ingredients and they give you the instructions and you know what to do, you still have to do the effort but you know if you connect these pieces together properly that you're going to wind up having a good experience and then, it gives you a lot of freedom to experiment and be creative beyond that, should you choose to. I think one of the signs that you've done a crummy job is that you're staring down, like Chris Freeman said, you actually starting to restrict your choices like, "I can't actually build you that feature because we don't have time to take on the amount of work necessary to build the support structure, to build you that feature," or if you find yourself writing a test framework.
CHRIS: Oh, yeah we did that too.
BRANDON: You know, we were real deep in this. There are developers that are like, "I really want to feel like I'm walking into a grocery store and selecting all the things necessary for my recipe," and so it really depends on what the problem actually is. If you're working at a giant megacorp and you have a two-year timeline to deliver something and their goals are not about delivering stuff on a tight turnaround, that's usually a recipe for a software failure anyway but let's say, that you're in the 5% of those types of projects that's going to succeed, that might be a good place where you can say, "What we're trying to do here is so custom and we have such a long lead time and a long leash and such a high level of internal expertise here that we should be shopping in the grocery store and we should be selecting all these things and we should be solving these problems."
Basically, when is it time to use a framework? Well, when you don't have 10 times the time you think you do, when you don't have the ability to spend 80% to 90% of your time in the first three to four months of your project, maybe six months, debugging you're glue code in between the different libraries that you're gluing together and then coming back and realizing that you've painted yourself into a corner and you have to re-architect your whole framework, then you could be so proud of this baby, 18 months to two years from now, when you actually have delivered both a framework that took about 70% of your time and an application that took 25% or 30% of your time.
CHARLES: Yeah. I think it's important to realize that people think we'll do it and we'll build it as we go but I want to call out right there, you will be spending 80% of your time and you have to be upfront about it. Of this two years, 18 months of it is going to be spent building this framework and six months of it is going to be spent actually writing the feature code and you have to be 75% of your tickets or your issues, whoever track the work, 75% of that has to be dedicated to the framework.
BRANDON: If you're going to bake in that kind of overhead purely for the satisfaction of a single or one or two developers that like inventing things, that is literally the worst possible reason you could do that. That is almost like a guaranteed recipe for failure. It has to be for some other business reason like, "We want to be the company that owns this." There has to be business value attached in making that kind of investment. If you can't justify that at the outset, then you should probably just go ahead and lean on an existing framework and join a community of people.
CHARLES: Yeah and I think one good litmus test for that is, "Is this a 'what' for which there is currently no 'how?' One of the reasons we're writing BigTest is because for the general JavaScript community, there are a number of acceptance test frameworks out there but the market is very, very limited. When we look to actually acceptance tests, our React application, this thing does not exist. Now, we had experience with something that was very like Ember specific and so, we kind of knew what the 'what' was, we experienced the 'what' but there was no 'how' for our current situation. That's like a place where you might be called upon where makes business sense to actually invest in a framework.
I'll tell you another thing too is if you have made the decision to kind of follow the beaten path on the other areas, then when a framework is called for, you have the bandwidth. You've allowed for the buffer, for the margin, for you to write in with that framework, whereas if you're already just by default, maintaining all the glue code in every single thing, then if some unique 'what' comes along, for which there is no 'how,' you're not going to have a bandwidth to tackle it.
BRANDON: Yeah. That's a real bad situation to be in.
TARAS: There's something else that I find interesting is because there's a certain point, like this two-year mark where everyone's like, "We want to fix this now." I think what is interesting what comes next which is the three years of undoing all the stuff that you made because the biggest challenge, especially in really big projects. When your projects has to borderline into platforms and a platform threshold is when you have a multiple teams working separately to write separate modules that run, maybe in a separate Git repo and maybe, packaged in separate npm package and assembled together.
Then what happens at that point, the question arises like how do you actually make this changes in this environment. Answering that question is actually really difficult. I think if you look at frameworks like Ember, Ember has made it their business to figure out exactly how to make this happen and I think they've done it really well but it's a really challenging endeavor, especially in incorporate environments where they don't have an update. You have like upgrades are like a curse. It's like a thing that you don't really want to ever do and because most quite often, they don't have the right testing habits in place to be able to support the change if necessary.
I think what a lot of times happens is that the team that made the framework in the first place, they end up trying to maintain a fort but you won't have like 10 people and they only have machetes, you know? All you can do is run around and try to chop down little twigs but at the end of day, the trees is still going to keep growing. I think that's the really challenging part of being two years into a project, where you realize that you actually need something much more comprehensive than initially thought you needed.
CHARLES: On that, assuming that you have decided that you are going to make a framework, it's a good business decision for you. Based on the criteria of this discussion, how can you assess whether it's good? Chris, you talked about needing to integrate query params with routing and asynchronous data loading and making sure all of that coordination happened and worked together easily. What's the difference between your framework just missing features kind of having holes in it that can be filled in, versus something that's not good and it's going to cost you lots of money down the road.
CHRIS: Yeah.
TARAS: One thing, if you look at what makes a good library of any kind, it tends to be like how effectively and how much words to take the address the use cases that you need. The problem is that to build a good framework, you need to understand the use cases. This is what usually happens over time. Two years in, you've actually understood the use cases and now, it's time to change and so, I think if you want to build a good framework, you actually need to understand those use cases quite early on or account for understanding use cases over time and that's a big question -- how do you figure out how to know what you don't know.
CHRIS: Yeah, I think that's exactly right. I think about what you were just saying Charles and Taras like one of the things that I think has a big impact on and what this process looks like is the completeness of vision for what's your project actually is. If you have a very, very clear idea of what the entire product you're building is going to be or, at least what the key money-making feature is going to be and you can understand the ins and outs of that, then I think that's the point where you can look at what you have and say, "Have I created a good or bad framework? Does this framework have the ability to solve this one very important thing that I have to be able to do? If the framework doesn't do it, then I need to build my own but I now know what very important features I need to front load my framework with."
I kind of think of it as imagine that you're like Jeremiah Johnson, the Reverend Jeremiah Johnson and you're going to go trekking through the woods for some unknown amount of time and you have no idea yet. You don't actually know where you're going. You don't know what you're going to see. You don't even know what's out there because you haven't done the research or whatever and you need to be prepared for anything, so you bring just a hodgepodge of stuff.
If that's you at the beginning of your company or the beginning of your product and yours is kind of like... I don't know, we got to get product market fit and that means that we may have to kind of pivot once or twice or we need to be very flexible, then I would think long and hard before you commit to writing your own framework because you don't even know what framework to build and you might as well take a broad array of tools and use what you need.
There will be times where that's frustrating and there won't be exactly the right tool for the job but 80% of the time, it's going to do just fine but if you know you have to do this one very special thing and you know that a framework is going to give you a lot of stuff that you won't need and it doesn't really excel at the one thing you do need, then don't force the framework. There may be time to build your own but just know that you need to go in with a very clear idea of what you're doing before you start building the abstractions that constitute a framework, rather than just like a constellation of libraries.
CHARLES: I have a question on that then. Going back to one of the things we were talking about like React plus Redux. Your opinion, Chris that it is not a framework, so the question is does a framework actually exist for React?
CHRIS: My guess is that many frameworks exist for React.
CHARLES: Is there a public framework?
TARAS: There is one called Fusion but it's [inaudible] what you would have imagine. It is essentially Redux and React together conventionalized. They addressed a bunch of concerns around service rendering and such but it does exist.
CHRIS: How about Next? Next.js?
TARAS: I'm not familiar with its features from a single page application perspective.
CHARLES: I think it does have a router. It does bundle with Redux and this is one of the things that when you first started using Redux, it's like, "How do I even get my store to my components?" Yes, I can connect them but there's actually a lot of stuff that you have to do. First, you have to say, "I'm going to put my reducers here and then when I create my store, I'm going to fold all my reducers. If I've got a whole bunch of reducers in my application, I've got to fold them all together. I've got to pass them off to the store. When I create the store, I have to inject the middleware and then, everybody else just imports my store and then, I have to put in a provider and then, I can connect my components."
That's actually a lot of stuff that you have to do and I think that, for example, Fusion just says, "Put your reducers here and we'll take care of all that process," and so it makes that decision for you, right? It says, "For state management, you're going to use Redux. For your reducers, they're going to go here. For your actions, they're going to go here." I don't know exactly how it's laid out but I remember reading the ReadMe, it was basically layering conventions over that. That's definitely going into framework territory but that's the only one that I know of, which is really, really odd.
TARAS: There's something interesting that's happening also and this goes to what Brandon was saying earlier is that choosing the best in class, there's this 10 things but then, what if one of the best in class stops being the best in class. The fact that the creators of Redux was essentially saying that we needed to basically provide a way to do Flux that was better than 10 different options that were available, so here's Redux. We've created Redux but we don't really think it's ultimately the solution. We need to have something else in React that provides a foundation for us to be able to deliver a better state management than what Redux is, so what happens when one of the best in class is no longer the best in class? The bridge is already standing. There's people walking across the bridge already. How do you replace one of the chains in it?
CHRIS: Over the course of six months while you figure out the differences in API between Flux and Redux and all the custom route transition data loading stuff you did with your Ajax library in your state management software that you put in a case statement inside there that you now have to change over. It's easy. It's no big deal. Don't worry about it.
BRANDON: Just a simple matter of programming.
TARAS: At least 25 years of collective frontend development experience is laughing like hyenas about the simplicity of building a --
BRANDON: Yeah, I'm actually looking at some of the old code that Chris wrote for trying to glue together, Redux Saga. I've been out of the game long enough to not know whether that's been superseded by some new or best in class piece of technology and even then, it was really challenging. This is true for frameworks too, is they don't really optimize for best in class. They optimize, hopefully for best fit for purpose but the world has moved on since Ember launched obviously. A lot of things have changed and it's, at least as difficult to try to keep that up to date with evolving trends and technologies and updates for a core team at a framework level as it is for you, as an engineer on the team. The difference is you get to outsource that work to a core team for a framework.
Ember has not done a fantastic job in keeping up with. They've done a good job and they've tried their best but if there were more people working on it or if there was more effort applied to it or if it was a higher priority, you would see Ember being a more up-to-date framework using more modern tools. As a framework author, if you stay too close to the bleeding edge, all you're going to do is change out your build system. You're going to replace a Broccoli with webpack, with Rollup, whatever's after that. What's new in Packer?
CHRIS: Parcel?
CHARLES: Parcel.
BRANDON: Parcel. You should immediately go build your framework with that and have fun. I am excited by the new and interesting stuff that's happening in these ecosystems and I think it's important not to get lulled into the siren song if your goal is to actually ship a piece of software on a timetable or a budget.
TARAS: One thing, if it's a red flag, if you think this is easy, if you think your decisions can be made in this isolation without talking to somebody else and actually kind of flashing it out, then you're probably doing something wrong because a lot of these things are not trivial. There's a lot of thought, there's a lot of considerations used to go into decisions that you make, especially when you're creating something that is going to be used by more than a few people. I think that's really one of those things where it's hard to know what you don't know but if you think you know and you haven't done this before, you haven't done this a few times before, you're probably missing some pieces.
BRANDON: Yeah, I agree with that.
CHRIS: I think one of the things that's really enticing about React and Taras, you just hit on it but I've never felt as clever as when I was writing a React app. If I'm clever, I mean, clever in the same way that I felt really clever when I wrote some unbelievably convoluted Scala one-liner that six months later, neither me nor anyone else could decipher what it meant but at that time, I felt like a god of programming. That's how it felt like, "Well, a lot of the React stuff is addicting." It felt so much fun. It was so much fun until I really had to do something and it mattered for my job and there was a deadline and people were depending on me and I've realized that the clever thing I had done a month later was not the right clever thing but I can see how, if you're like what Taras was saying, where you are at the point where these decisions are easy. These decisions make sense. We're going to be fine and you haven't done it enough to kind of like know where all of the pitfalls are. That cleverness that you feel is fantastic and I can see why it takes two years before you look back and if the cleverness was finally worn off and then, you're just mortified at what you've done.
CHARLES: Pride cometh before the fall.
CHRIS: Yeah.
BRANDON: It's like being a dungeon master in Dungeons and Dragons, where you're like, "Oh, look at this fiendish world." All right, cool. Now, you actually live there though. I have to move into an apartment on Mordor.
TARAS: You know what's the funny flipside to that is that coming from Ember world where it's so normal to leverage the work of other clever people, like really smart people who've invested a lot of time to solve a particular problem, is that there's no stronger sense of being dumb than having to write it from scratch in React. That first feeling of like, "I've actually never had to implement this from scratch," and I feel like a bunch of applications before but because I've leaned on for accessibility, I've leaned on something that someone else has done and it worked really well for me and it was perfect. But now, I need to implement autocomplete from scratch in React and I have no support. I'm basically learning as I'm going on this and it's that sense of discomfort that you get from having to do it from scratch and then, comes the euphoria of having to figure it out. But if you figured it out, you figured it out in the last month. You've written it for the first time in the last month and you now understand what all the things that the Ember implementation does for you. It's an interesting psychology of doing this --
CHARLES: Yeah, it gives you a lot of perspective but you have to ask as a business owner, who may or may not be technical and this is the hardest thing for technical people who are business owners is to be able to not see things through a tactical lens. Is what you really want to pay for is to basically give your programmers this kind of a-ha moment of their own shortcomings because that what you want to be buying.
BRANDON: Yeah, you want to maximize leverage. Your goal with technology is to maximize leverage. It's like being hired as a chef and you walk in and then you're like, "I'm a terrific chef. I worked in these fancy kitchens in New York and I'm known as a great chef," and they're like, "Okay, cool. Here's some flint and steel and a spear."
CHARLES: Go hunt.
BRANDON: You're like, "Wait, what?" Yeah, yeah, yeah. Show me what you can do.
TARAS: We had a conversation in one of the previous podcast with Michael Jackson and we asked him, "What is the one thing you wish like React community would do more of?" and he's like, "I really wish React community have more conventions." All of this is to kind of say as like, there is a place for frameworks in React world. There's a very strong place for it. The question is how and what it said and how do you actually build it and when do you --?
BRANDON: So we need a framework for making framework.
TARAS: Getting really meta here.
BRANDON: I totally agree with that and that's a great observation and that was actually the point of my talk as well, which is if I could convince people just to use Ember and improve Ember, that would be great because I think it's a really great starting point. But the React community is much larger because it had such a great adoption story. The adoption of Ember was very difficult and the adoption of React was very easy and it expanded to include the scope of full end to end applications in terms of what people thought the problem spaces they were thinking of with React.
Ember was built to solve that but it was hard to get into. React was really easy to get into but it's actually hard to build applications with. I would love to see a dedicated subset of the React community, except the idea of shared solutions and the philosophies that made Ember into sort of a powerhouse of value delivery but built out of tools that satisfy the React community and a little more modular and a little more available for people to customize and built in that ecosystem.
I'd really love to see that that included all of the main components of what we accept as, "This is an application framework. It handles testing. It handles accessibility. It handles data loading," and it doesn't have to be best in class in every scenario but it does have to be a reasonable bridge across that chasm and have a group of people look at this the same way. I would love to see a collective subset of the React community dedicate themselves to this idea. I don't know if that's too culturally opposed or even orthogonal to what the value system inside the React community. I haven't been able to fish that out but I would really love to see that emerge.
this is something I would love to push for and I'd love to see other people jump in and push for as like, "What if 20 of us got together and decided we're all building our applications in similar ways, instead of one person saying, 'I'm going to use --'" Even create React app is kind of a Band-Aid on that, it isn't useful past a certain stage of life. I would love to see a group of people, though, get together that are sort of like-minded like that, the Michael Jacksons and maybe even Dan Abramov or a group of people that shared that set of values or came into React from the Ember community.
That’s actually one piece of advice I would give to people. You said, "How do you convince this engineer that they've built a bad framework?" Use a decent one. That's the biggest guide. Use a decent one. Build something in Ember and ship it to production and go, "Oh, I get it." If you've used a good framework, you can't go back to rolling a crappy one. Your standards have been ratcheted up.
CHRIS: I wholeheartedly agree that you should try something else and Ember is a great option but I don't want to dismiss just like, "React is cool as hell," and there's a lot of stuff in React that's really, really awesome and things that I wish that will show up in Ember and they are starting to show up in Ember but they're taking a while and it'll be nice in there but who knows when that will be but I would encourage even more so is both sides, like Ember folks who are listening to this podcast, if you have never messed around with React because you feel some kind of tribal affiliation that you can't betray, please set that aside and go do something in React because you will learn a lot about why Ember does what it does and you will see a lot of really interesting things that will probably jostle some ideas loose in your brain.
The same thing goes for React developers. You, 100% should spend a weekend building something in Ember and nothing about that means that you have to switch or it's going to change the path that you're going on at work but I guarantee you, you will go back to your React application with some new and fair useful perspective that you didn't have before and that's okay. That's great. There's no identity crisis that will come about as a result of that.
CHARLES: That is a fantastic advice, Chris. It will only stretch you.
CHRIS: Yeah.
BRANDON: I think developers have been sold this idea of a competitive landscape by authors of these frameworks because it helps sell the framework. You can build and strengthen a community by leaning into the tribalism that can surround the usage of a tool. The older I've gotten as a person who was deeply tribalistic about Ruby on Rails when I got into it and Ember when I got into it, because I love tribes, I think tribes are awesome and it's a way to make friends but when you really lean into that, the costs are too high and experimenting with other technologies and noticing flaws in your own technology is not only not a betrayal, it's actually critical to your growth as a developer. The more people that do that, like Chris was saying, the better both of those ecosystems will get.
CHARLES: Absolutely because having spent as much time in React as I have, I really appreciate the precious things about Ember. It will make you appreciate the things that you hold dear. It will make you appreciate the really, really, really special things about the tool that you're using and at the same time, it will highlight the weaknesses which you can immediately use to feedback and make your tool better. It really is a win-win situation.
TARAS: I just want to do a little plug before we close up. I think the feels of working with Ember is actually gone into microstates and we're still getting our things together to make microstates look accessible and usable by everyone but that feeling of pleasure that you get from working with Ember and just things just being there for you, like we really want to reproduce that and make that available in React community and the stuff that we do in microstates is actually really designed for that.
CHRIS: Yeah, I see that in BigTest too as well. That's definitely another place where it's like, "These people definitely used to spend time in Ember and they're now in React-land." It's cool to see that stuff getting ported over.
CHARLES: Absolutely because it fundamentally changes your taste. Working with an application that doesn't have like a bolted on testing framework is like eating water soup. You just can't enjoy your life. It really is flavored everything that we do. On that note, we can go ahead and wrap up. There actually is some pretty exciting news. We're actually going to be launching a BigTest launcher. Up until this point, you kind of had to roll your own using BigTest for your assertions but using something like Karma to actually launch the browsers and we're actually launching our own launcher. I guess we've written our own launcher and we're going to be pushing it to NDM, not to overload the word launch.
You can look for that in the next couple of weeks. There's going to be a CLI that ships with BigTest to help you do even more set up, to make it so that you can just drop BigTest right into your application, whether it's jQuery, React, Ember, you name it. That should be really, really fun. Be looking for that and with that, if anybody has any other remarks...
BRANDON: If people are coming through RubyConf this year, I'll be there talking about management stuff. That's my only near-future conference stuff coming up. Hope to see some of the more Ruby-flavored folks out there.
CHARLES: All right-y. Definitely, go to every single talk that Brandon ever gives. You won't regret it. I can base that on very dear personal experience. You won't be disappointed. You know, not to put the pressure on or anything like that but you could never put any more pressure on Brandon than he puts on himself. With that, we will say good bye. Bye Chris, bye Brandon. Thank you so much. This is a great conversation. It certainly clarified a lot in my mind --
TARAS: Yes, same here.
CHARLES: -- About these problems. With that, we will say goodbye. Thank you for listening The Frontside Podcast. Please get in touch with us at @TheFrontside on Twitter or contact at Frontside.io on email. We do a range of custom services from full stack project development to JavaScript mentoring, to as you go JavaScript help desks kind of stuff. If you need to reach out to an expert, please get in touch. Our podcast as always is produced by the inimitable, Mandy Moore. Thank you very much and we'll see you all next time.
The podcast and artwork embedded on this page are from Charles Lowell & the Frontside Team, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: The Simple Sophisticate - Intelligent Living Paired with Signature Style (LS 57 · TOP 0.5% what is this?)
Episode: 252: The Characteristics of Being a Late Bloomer, and How Embracing This Gift Could Change the World for Everyone
Pub date: 2019-05-20
"By necessity, we late bloomers are on a different, more challenging trajectory. As we travel through life, we encounter obstacles like the push for conformity, the oppression of groupthink, and the pains of self-doubt. But . . . in all these challenges, we find our hidden treasure. We unearth our individuality. We see that a path to excellence, to reaching our true potential, is available to all of us. Within these challenges lies our true power, our covert talents and secret advantages as late bloomers." —Rich Karlgaard, author of Late Bloomers: The Power of Patience in a World Obsesses with Early Achievement.
Unsurprisingly, the new book by Rich Karlgaard spoke to me and offered an abundance of reassurance and exhilaration. If the comments on IG a few weeks ago when I posted an excerpt from the book are any indication, you are or will be as well.
Especially as Americans we greatly celebrate, strive for, and thus put pressure upon ourselves, and either unconsciously or consciously, to figure out our path early, to achieve success quickly and when we don't we make faulty assumptions about what we can contribute which can erode our self-confidence and potentially prevent the gem that resides within us all to be discovered and then shared with the world enabling us to find deep, lasting inner contentment.
Karlgaard's new book is worth reading in-depth, from cover to cover as he delineates the obstacles that our culture currently needs to address with historical details, new studies, multiple anecdotal examples of how indeed the "late bloomer" simply needs time, patience and awareness to blossom at their own time, as well as the most difficult support to refute findings - neurology.
So while I will encourage you to read the entire book, in today's episode/post, I wanted to share with you the characteristics that you might find yourself identifying with when it comes to being a Late Bloomer and not realizing the gift of opportunity you have given yourself to enjoy the rest of your life.
15 Characteristics of a Late Bloomer
1.Curiosity is the late bloomer's fuel
"By its very nature, curiosity demonstrates an independence of mind."
To keep on blooming throughout the entirity of our lives, forever remain curious.
- We are predisposed to be compassionate
"In facing the ups and downs of life, many late bloomers gain a greater sense of compassion. They show greater reflective thinking, diminished ego-centeredness, and a deeper appreciation of others' challenges."
Because late bloomers have faced struggles along the way, have refrained from conforming at the expense of our social connections and acceptance into "the group", we can more easily put ourselves into the shoes of others, we are more empathetic.
3.Better leadership skills are developed
Due to elevated compassion, workers view leaders more favorably, and combined with "authenticity and integrity", this trifecta of skills "improves retention and employee performance".
- Resilience is developed and strengthened
"When it comes to developing resilience, the regulation of emotions gives mature people an advantange over the young: 'There is a naturally learnable set of behaviors that contribute to resilience. Those are the behaviors that we gravitate to more and more as we age'."
- Emotion regulation is easier which cultivates a calmer demeanor which leads to more effectiveness and better relationships
"Our brains are driven to seek calmness as we age. Columnbia University social psychologist Heidi Grant Halvorson claims that calmness is central to happiness . . . research has long established that calm leaders are more effective".
Late bloomers naturally develop the skills necessary to find calmness if we choose to keep exploring, learning, listening and observing what works and what does not. This is where our curiosity helps tremendously leading us to the blooming stage of our lives that is authentic and unique to each of us.
- Extensive insight
"Our insights are the result of us drawing on our full mental library of experience, patterns, and context, yielding an idea of extraordinary value."
Karlgaard explains that "the right hemisphere [of the brain] matures in childhood; the development of the left is consistent with the development of the prefrontal cortex, which is not fully mature until the mid-twenties". Due to the left-side's difference in development compared to the right, it takes time for us to see the connection of the awesome or unique events, sights and experiences of our lives and make sense of how we can utilize them in our unique way.
- Navigation of life's ambiguity becomes easier
"Perhaps this is the perfection defintion of wisdom: reasoning and cognition based on knowledge and experience".
In other words, we are not born wise, but so long as we choose to be curious, continue to be life-long learners, we begin to build it. "Wisdom is the ability to see the layers of light that were harder to see when one was younger". And consequently, we have the opportunity to hone our intuition as to how to best navigate our journey even with the unknowns that are presented.
- More easily determine what's important versus what's trivial
To piggy-back onto #7, because we have acquired knowledge about the world over time and have made the conscious choice to continue to learn, we are then better at discern patterns faster and jump to logical solutions more quickly.
- A desire to cut the apron strings with your parents
"To fully bloom, we must declare our independence from our family. That doesn't mean we must reject their love . . . it means only that we must reach our own conclusions about what does and doesn't support our blooming."
Creating a healthy culture in which to bloom is analogous to the proper soil and conditions for a plant to flourish. Each plant will need different types of soil, different amounts of sunshine and shade, varying temperatures - some extreme, some moderate, and it all depends on the plant. Unlike the saying, "bloom where you are planted", we should instead get out of the soil we have been planted in and explore to discover where we truly thrive.
- Adult peer pressure is real, and if you've felt it and tried successfully or not to not succumb, you may be a late bloomer
"Some of this [peer group] influence can be healthy and positive, as when we join a hiking club or sign up for a program to quit smoking. But not every peer push leads us to a better version of ourselves; not all communities support growth and positive change."
To break free from our peer group, even when we don't know why it feels uncomfortable or wrong (but we know it does), is not easy and it takes great inner strength to do so. However, it does become easier because we eventually begin to feel more in tune with our true selves, we feel a burden lift, we feel our energy surge because we are no longer trying to be or do something that isn't truly in line with what we can offer the world.
- Societal pressure to conform is limiting to our true potential
"[Today's media] also promote cultural, racial or gender biases, either through stereotyping roles and behaviors, or under- or overrepresentation of minorities. And repeated exposure to media content can lead viewers to begin to accept media portrayals as representations of reality."
From the media's portrayal of how to socially engage, what dating should look like, what children should be doing at certain ages based on their gender, the values are repeatedly shared and included in endless amounts of media such as video games, movies, television, newspapers, magazines, books and radio, and since it is a passive medium, unless we are critical thinkers questioning everything we receive, it is easy to accept what is applauded as normal and what we should adhere to regarding our life's journey.
- Letting go of comparisons
"Mass media ask us to compare our body shape, sex life, marriage, house, car, family and community to unattainable television versions of perfection. Social media ask us to compare our own commonplace or even boring reality against the curated accounts of how absoutely wonderful someone else's life is — people we know!"
When we stop comparing and start celebrating, we liberate ourselves and enable the opportunity to observe our own awesomeness without the outside world's close-minded criticism or limited acceptance.
The author shared something that I think is worth sharing here as a reminder that there are many paths to success, to reaching a goal, to attaining contentment. He writes, "There are always many ways to achieve a goal, gain expertise, or find success. In sports or music, they are easy to see . . . But it's not as easy to see multiple paths for success in most endeavors . . . [which leads to confusion. As a result,] we default to following norms and take the road everyone else is taking". And these paths to success have as much to do with professional "success" as well as personal "success". Your definition of a life of contentment, as I have said many times before on the blog and in my books, will most likely be very different than mine, but that doesn't mean we both cannot feel the contentment that is spoken about and written about that provides deep satisfaction and peace.
It is important that we all recognize that each of us will bloom at a different time.
"Each of us deserves the opportunity to bloom in our own way."
When we do this there are many invaluable benefits:
1.We protect ourselves, and others we encourage to bloom, in our own time from the consequences of disappoitnment or failure. (this doesn't mean there won't be bumps along the way, but it reminds us that it takes time to understand where we are headed and why)
2.We learn how to work with self-doubt and let it be our superpower.
"To bloom, we all must learn not to fear self-doubt but to embrace it as a normally occurring opportunity for growth and improved performance . . . The key to harnessesing self-doubt starts at the very core of our individual beliefs about ourselves . . . self-efficacy".
- We strengthen our self-efficacy
Self-efficacy is an individual's confidence in their ability to accomplish what they set out to do.
- Obstacles begin to be seen as opportunities to grow rather than road-blocks
"While you may feel a general sense of self-doubt . . . [you] proceed anyway".
- Improved positive self-talk
"Positive self-talk can improve our performance by helping us regulate our emotions, thoughts and energy".
When we begin to see skill-sets that render positive results, we are more likely to invest in them. For example, positive self talk leads to more confidence, a strengthening our self-efficacy and thus improved performance with whatever task is in front of us. And so we continue to practice positive self-talk and it becomes stronger with this skill rendering more positive outcomes.
- Stronger, healthier relationships
When you bloom, gravitate toward those who celebrate your blooming, and for those who initially are not, give them a moment to understand why your blooming makes them uncomfortable. Depending upon the person, they may not realize that their discomfort with your growth is a reflection of their disappointment in what they feel they could have achieved but didn't. This is all about them. Some will grow from this and remain in your life, others will not, and you will need to move on. But all of the skills you have acquired and applied will help lead you toward building not only healthier relationships with others, but a healthier, less critical relationship with yourself.
- Excellence will arrive when you let your curiosity take over
"When [curiosity takes over], a sense of exploration also takes over. I get in the zone, and I go for it. I feel pulled, not pushed — pulled by a beautiful power I cannot explain."
- The courage to repot when necessary
"When it comes to repotting, late bloomers have a distinct advatnage over early bloomers. We're naturally curious and resilient. We're not afraid to follow a different path or break free of convention. We genuinely want to see what's around the corner or over the hill. These late bloomer strengths enable —even propel— the change we need to find the right people and the right place to help us thrive."
Once you have a clearer understanding of who you are and what cultures and communities are best suited for you to bloom, you will have strengthened, as was mentioned above in the first list, an awesome skill set. This skill set will be your bedrock for being able to repot when and if it is necessary.
"We need to give ourselves a break. We need to recognize and celebrate the fact that we're all different, with different skill sets, developmental profiles and backgrounds and that each of us will forge a different path toward blooming."
Being a late bloomer is most certainly something to celebrate, and when we "change our story, we can change our behavior and even our life".
Let me leave you with this lasting thought from the book that resonately powerfully with me:
"If we're not forced to conform to standard timetables for success, we can —and will—bloom on our own schedules. And we can do it with a deeper sense of mission and a greater feeling of contentment. What we accomplish in the marathon of life depends on our persistence, our patience, and an ability to see ourselves as we really are. Our cultural obsession with youthful talent, with early achievement, distracts us from this simple truth. . . . our late bloomer power is different. It is the power to renounce what's supposed to happen in life and intead embrace what actually happens in life, with its ups and downs, twists and turns. It's the power to explore and experience, to be an individual. It's the power that comes with knowing and valuing ourselves."
Petit Plaisir
~The Gown: A Novel of the Royal Wedding by Jennifer Robson
~read my review and reason for recommendation here.
TSLL BRITISH WEEK 2019 Posts:
Sunday May 19th
- A Giveaway for Anglophiles: A Year’s Subscription to The English Home magazine and more!
- TSLL’s First Annual British Week Begins!
~Do you enjoy reading TSLL blog and visit regularly, but would prefer to read the blog without ads? I have some good news for you. For a limited time, during British Week, the price for a monthly or yearly ad-free subscription has been reduced. Simply use the following promo codes below when you subscribe (or learn how to subscribe) here. The discount runs through Sunday May 26, 2019.
- Yearly $69.99 – Now $60/year – use promo code YEAR60Ad
- Monthly $6.99 – Now $5/month – use promo code BRITWK5Ad.
- Learn more and subscribe here.
The podcast and artwork embedded on this page are from Shannon Ables, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Code[ish] (LS 34 · TOP 5% what is this?)
Episode: 68. Performance Tuning Critical Rendering Path
Pub date: 2020-05-05
Charlie Gleason, a designer and developer at Heroku, is in conversation with Ben Harding, a developer at Raygun. Their conversation centers around a website's "critical render path," which are the steps in which HTML, CSS, and JavaScript are converted into pixels which a user actually interacts with in their browser. The fast these pixels are rendered, the better the experience which a user receives. Delays in website rendering can lead to an impact on one's business, as users are likely to leave slow sites; more often, it's an issue of accessibility, where users with slower connections should be able to visit any page they want to.
Ben outlines four metrics that can be key to gathering information about how your website is performing. There's "time to first paint," which is the time it takes for a browser to render anything; there's "time to first contentful paint," which is the time it takes for the browser to render any content, like an image or text; there's load time, which is the time it takes for all of your assets--CSS, JavaScript, and fonts--to download; and there's "time to interactive," which is when a user can start engaging with a website, such as by clicking buttons or filling out a form. It's important to measure all of these stats first so that you can approach performance optimizations from a baseline of where you are, and where you want to be.
There's plenty of low-hanging fruit when it comes to improving website rendering performance. You could try minifying and compressing your CSS, JavaScript, and images, so that the user's browser doesn't need to fetch large files. You can also implement techniques such as code splitting, which ensures that CSS and JavaScript is only loaded for the pages those styles or functions are needed on, rather than every single page on your site. You can load your assets asynchronously, so that the browser is not blocked on any one task. The important thing is to take a look at your starting metrics, and focus on tackling one of your problems until the load times are down to an acceptable range.
Fine-tuning website performance is an iterative cycle: as more features are added, performance will degrade. Sometimes you can't optimize a website any further than you've already done, and that's okay. As long as you keep your user's perceived performance in mind, you can still get away with having spinners and splash screens, so long as they are receiving feedback and are aware that something is happening.
Links from this epiode * Critical rendering path * DOM and CSSOM * Lighthouse * Webpack * Parcel * Uglify * ImageOptim * TinyPNG * SVGO * Media attributes for CSS files * Async / defer for JavaScript * Preloading / prefetching assets * Heroku’sMalibu icon library * SVG and sprite sheets * Code splitting * React Lazy and Suspense * Visualising bundle sizes * Tree shaking * Raygun
The podcast and artwork embedded on this page are from Heroku, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Podnews podcasting news (LS 43 · TOP 1.5% what is this?)
Episode: Spotify launches targeted podcast advertising
Pub date: 2020-01-09
Visit https://podnews.net/update/spotify-targeted-advertising for all the links, and to subscribe.
This update has been archived. Visit the URL above.
The podcast and artwork embedded on this page are from Podnews LLC, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Ask the Health Expert (LS 55 · TOP 0.5% what is this?)
Episode: Meat: To Eat or Not to Eat? with Angela Mavridis
Pub date: 2018-12-12
Angela Mavridis grew up in the heart of the Mediterranean, eating fresh, whole foods. After moving to the United States, Angela became a vegetarian for many years, only to realize that the vegetarian diet was taking a toll on her health. Following a Paleo lifestyle once again, Angela is now the owner of Tribali Foods, a company that sources organic, high-quality meats. In today's podcast episode, she talks with JJ about whether or not you should eat meat and why the quality of your protein is key. Listen as Angela shares what you need to look for when choosing protein and how to understand nutrition labels, including the difference between terms like organic, grass-fed, and pasture-raised. Find out how to change your plate – one bite at a time!
Freebies From Today’s Episode
Get 15% off at Tribali Foods by going to JJVirgin.com/tribali
Main Points From Today’s Episode
- Meat isn’t evil! What matters is how it’s raised, how it’s prepared, and what it’s eaten.
- Organic, grass-fed and grass-finished beef means that it’s free of antibiotics, pesticides, and hormones. It also has a better profile of fatty acids and is higher in certain vitamins and minerals.
- When it comes to protein, Angela eats from the rainbow. That includes high-quality sources of protein like salmon, lamb, venison, beef, and poultry.
Episode Play-By-Play
[2:10] Angela’s career briefing
[2:55] Listener’s review on iTunes
[4:33] Angela’s journey from Paleo to confusion to back again
[6:55] Over time, a vegan and vegetarian diet took a toll on Angela’s health.
[8:06] How Angela handles conflicting messages about nutrition
[9:41] It’s important to figure out what works for you
[11:37] Understanding food labels
[13:05] It’s key to eat as whole and as real as you can.
[13:22] Sources of protein: what organic, grass-fed, and grass-finished means, and why it matters
[14:41] The difference between pasture-raised and free-range chicken
[15:22] What to look for when buying seafood
[17:09] What made Angela decide to start her own food business
[20:34] Products available at Tribali Foods
[22:50] The importance of choosing quality over quantity
[24:40] If you want to lose weight even faster, here’s the two-word secret: Extra Fiber!
[26:16] Listener’s question: How much protein should I be eating?
[28:50] You also need to be sure that you’re digesting your protein well.
[29:45] Factors that can shift your protein requirements
Mentioned in this episode:
EWG's Seafood Guide
Vital Choice
Extra Fiber
Metabolic Digestive Balance
The Virgin Diet
7-Day Stop, Drop & Swap Challenge
Jjvirgin.com
JJ Virgin Official Facebook page
JJ Virgin on Instagram
JJ Virgin on YouTube
The podcast and artwork embedded on this page are from JJ Virgin, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: The Pragmatic Programmer – The Evils of Duplication
Pub date: 2019-05-13
We take a deep dive into the various forms of duplication and jump aboard the complain train as Allen complains about Confluent's documentation, Michael complains about Docker's documentation, and Joe complains about curl.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: The Pragmatic Programmer – How to Generate Code
Pub date: 2019-08-05
We continue our dive into The Pragmatic Programmer and debate when is it text manipulation vs code generation as Joe can't read his bill, Michael makes a painful recommendation, and Allen's gaming lives up to Southern expectations.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: The Pragmatic Programmer – How to use Exceptions
Pub date: 2019-08-20
After 112 episodes, Michael can't introduce the show, Allen pronounces it "ma-meee", and don't make Joe run your janky tests as The Pragmatic Programmer teaches us how we should use exceptions and program deliberately.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: The Pragmatic Programmer – How to Estimate
Pub date: 2019-06-24
Joe is distracted by all of the announcements from E3, Allen is on the run from the Feebs, and Michael counts debugging as coding. All this and more as we continue discussing The Pragmatic Programmer.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: The Pragmatic Programmer – Know Thy Tools
Pub date: 2019-07-08
We dig into the details of the basic tools while continuing our journey into The Pragmatic Programmer while Joe programs by coincidence, Michael can't pronounce numbers, and Allen makes a point.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: The Pragmatic Programmer – How to Debug
Pub date: 2019-07-23
It's about time we finally learn how to debug by taking take a page from The Pragmatic Programmer playbook, while Michael replaces a developer's cheat sheet, Joe judges the H-O-R-S-E competition for VI, and Allen stabs you in the front.
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: JavaScript Jabber (LS 43 · TOP 1.5% what is this?)
Episode: Episode 348: JSJ 344: Inclusive Components with Heydon Pickering
Pub date: 2018-12-18
Panel:
- Charles Max Wood
- Aimee Knight
- Chris Ferdinandi
- Joe Eames
Special Guest:Heydon Pickering
In this episode, the panel talks with Heydon Pickering who is a designer and writer. The panel and the guest talk about his new book, which is centered on the topic of today’s show: inclusive components. Check out Heydon’s Twitter, Website, GitHub, and Mastodon social accounts to learn more about him. To purchase the book – go here!
Show Topics:
0:00 – Advertisement: KENDO UI
0:38 – Chuck: Aimee, Chris, Joe, and myself – we are today’s panel. My show the DevRev is available online to check it out.
1:30 – Guest: Plain ice cream would be frozen milk and that would be terrible. So I am lemon and candy JavaScript!
2:13 – Chuck: We are talking today about...?
2:22 – Chris: He’s talking about “inclusive components” today!
2:41 – Guest: Traveling is very stressful and I wanted something to do on the plane. I’ve done this book, “Inclusive Design Patterns.”
If you don’t want to buy the book you can go to the blog. I have been talking with Smashing Magazine.
5:40 – Panel.
5:47 – Guest: I approached Smashing Magazine initially. They didn’t think there was a market for this content at the time. They were very supportive but we will do it as an eBook so our costs our down. At the time, the editor came back and said that: “it was quite good!” We skimmed it but came back to it now and now the content was more relevant in their eyes. I didn’t want to do the same book but I wanted to do it around “patterns.” Rewriting components is what I do all the time. I use Vanilla JavaScript. Backbone.js is the trendy one.
9:52 – Panel: The hard book did it get published?
10:02 – Guest: We are in the works and it’s all in the final stages right now. It has to go through a different process for the print version.
11:54 – Panel.
11:58 – (Guest continues about the editorial process.)
12:09 – Panel: They probably switched to TFS – it’s Microsoft’s.
12:23 – Guest: There was this argument on Twitter about the different processors.
13:35 – Chris: What are the ways that people are breaking accessibility with their code through JavaScript?
13:59 – Guest: The whole premise is that there aren’t a ton of different components that we use. Generally, speaking. Most things we do through JavaScript – it’s just different ways of doing this/that, and hiding things. I am discounting things with Node or other stuff. Most of what we are doing, with interactive design, is showing and hiding.
18:37 – Chris: I have some specialty friends where they tell me where I’ve screwed up my code. For example Eric Bailey and Scott O’Hara but, of course, in very kind ways. What are some things that I can make sure that my code is going to work for many different people.
19:18 – Guest: You have accessibility and inclusive design. People think of accessibility as a check-list and that’s okay but there could be problems with this.
26:00 – Panel: That’s a great guideline.
26:05 – Chris: You talked about ARIA roles and it can be confusing. One side is: I don’t know when to use these and the other side is: I don’t know when NOT to use these so I’m going to use them for EVERYTHING! I guess both can be detrimental. What’s your advice on this topic?
27:00 – Guest: Scott is great and I would trust him to the end of the Earth about what he says.
Guest mentions Léonie Watson and her talks about this topic.
29:26 – (Guest continues.)
29:36 – Advertisement – Sentry.io
30:31 – Chris.
30:40 – Guest: There is a lot of pressure, though, right? People wouldn’t blog about this if it wasn’t worthwhile. It doesn’t matter what the style is or what the syntax is.
The guest talks about not throwing ARIA onto everything.
36:34 – Aimee: Is this something that was mentioned in the book: people with disabilities and accessibility.
37:28 – Guest: Yes, of course. I think it’s important to make your interfaces flexible and robust to think and include people with disabilities.
39:00 – Guest mentions larger buttons.
40:52 – Panelists and Guest talk back-and-forth.
42:22 – Chris: It’s an accessibility and inclusivity element. I saw a dropdown menu and worked great on certain devices but not others. I could beat this horse all day long but the whole: what happens of the JavaScript file doesn’t load or just accordion options?
43:50 – Guest: It’s the progressive enhancement element.
44:05 – Guest: I think it’s worth noting. I think these things dovetail really nicely.
46:29 – Chris: Did you do a video interview, Aimee, talking about CSS? Is CSS better than JavaScript in some ways I don’t know if this is related or not?
47:03 – Aimee: When I talk about JavaScript vs. CSS...the browser optimizes those.
47:27 – Aimee: But as someone who loves JavaScript...and then some very talented people taught me that you have to find the right tool for the job.
47:29 – Guest: I am the other way around – interesting.
52:50 – Chuck: Picks!
52:55 – Advertisement – Get A Coder Job!
END – Advertisement: CacheFly!
Links:
- JavaScript
- Backbone.js
- Microsoft’s TFS
- Léonie Watson
- React
- Elixir
- Ember.js
- Vue
- GO
- jQuery
- Node.js
- Puppeteer
- Cypress
- Heydon’s GitHub
- Heydon’s Mastodon
- Heydon’s Book
- Medium Article on Heydon
- Heydon’s Website
- Heydon’s Twitter
Sponsors:
- DevLifts
- Kendo UI
- Sentry
- CacheFly
Picks:
Joe
- Chris Ferdinandi's Blog
- Luxur board game
- Cypress.io
Aimee
- Blog about interviewing
- Birthday Cake Quest Bar
Chris
- Web Dev Career Guide: https://gomakethings.com/career-guide/
- Use FREECAREER at checkout to get it for free
- Neapolitan Ice Cream
- Netflix Web Performance case study
Charles
- Disney Heroes Battle Mode
- MFCEO Project Podcast
- Gary Lee Audio Experience
- Suggestions for JavaScript Jabber
Heydon
- Bruck
- What is Mastodon and why should I use it?
Special Guest: Heydon Pickering.
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Node University (LS 28 · TOP 10% what is this?)
Episode: SL 37: Callbacks vs. Promises vs. Generators vs. Async Functions in Node and JavaScript
Pub date: 2018-05-02
Resources
- Top 10 ES6 Features Every Busy JavaScript Developer Must Know
- You Don't Know Node:
- Node Advanced
About the Channel
Node University and its creator Azat Mardan tells you about advantages of using Node.js and why its such an absolutely, positively, amazingly awesome technology.
Who is Azat? ¯_(ツ)_/¯
Well, he is the founder of Node University and...
- ⌨ Azat is in Top 1000 GitHub contributors list where Azat is number
239 right next to Paul Irish, Addy Osmani, Todd Motto and other
famous developers: https://gist.github.com/paulmillr/2657075. * 📚 Azat wrote 14 books on Node and JavaScript; the book which was #1
on Amazon when you search for "node.js" and now this book is free on
GitHub, Practical Node.js: https://github.com/azat-co/practicalnode. * 🎤 Azat spoke at 20+ conferences world-wide: http://azat.co. * 🏢 Azat taught engineers at companies such as Starbucks, Cisco,
Walmart, Intuit, Capital One, Macy’s, OnDeck, HubSpot, Fox Studios,
Northwestern Mutual, Salesforce, DocuSign,, Microsoft, VMWare and
other big companies. * 🎓 Azat has free and paid courses on Node University:
https://node.university * 👨💻 Azat wrote 200+ blog posts on Webapplog: https://webapplog.com
If you want to learn Node 🚀 and liked Node University Short Lectures 🎧, then subscribe to watch on YouTube and Node University and to listen on iTunes, Stitcher and Google Play: 👉 https://nodeuniversity.simplecast.fm and https://node.university. 👈
The podcast and artwork embedded on this page are from Azat Mardan, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Thoughts on Functional Programming Podcast by Eric Normand (LS 38 · TOP 2.5% what is this?)
Episode: Why do promises make async JavaScript better than callbacks?
Pub date: 2019-03-28
For audio, video, and text transcripts: https://lispcast.com/why-do-promises-make-async-javascript-better-than-callbacks/
The podcast and artwork embedded on this page are from Eric Normand, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: JavaScript Jabber (LS 43 · TOP 1.5% what is this?)
Episode: Episode 333: JSJ 329: Promises, Promise.finally(), and Async/await with Valeri Karpov
Pub date: 2018-09-04
Panel:
- Charles Max Wood
- AJ O’Neal
- Aimee Knight
Special Guests: Valeri Karpov
In this episode, the panel talks with programmer, Valerie Karpov from Miami, Florida. He is quite knowledgeable with many different programs, but today’s episode they talk specifically about Async/Await and Promise Generators. Val is constantly busy through his different endeavors and recently finished his e-book, “Mastering Async/Await.” Check-out Val’s social media profiles through LinkedIn, GitHub, Twitter, and more.
Show Topics:
1:20 – Val has been on previous episodes back in 2013 & 2016.
1:37 – Val’s background. He is very involved with multiple companies. Go checkout his new book!
2:39 – Promises generators. Understand Promises and how things sync with Promises. Val suggests that listeners have an integrated understanding of issues like error handling.
3:57 – Chuck asks a question.
6:25 – Aimee’s asks a question: “Can you speak to why someone would want to use Async/Await?”
8:53 – AJ makes comments.
10:09 – “What makes an Async/Await not functional?” – Val
10:59 – “What’s wrong with Promises or Async/Await that people don’t like it?” - AJ
11:25 – Val states that he doesn’t think there really is anything wrong with these programs it just depends on what you need it for. He thinks that having both gives the user great power.
12:21 – AJ’s background is with Node and the Python among other programs.
12:55 – Implementing Complex Business Logic.
15:50 – Val discusses his new e-book.
17:08 – Question from Aimee.
17:16 – AJ answers question. Promises should have been primitive when it was designed or somewhat event handling.
17:46 – The panel agrees that anything is better than Call Backs.
18:18 – Aimee makes comments about Async/Await.
20:08 – “What are the core principles of your new e-book?” – Chuck
20:17 – There are 4 chapters and Val discusses, in detail, what’s in each chapter.
22:40 – There could be some confusion from JavaScript for someone where this is their first language. Does Async/Await have any affect on the way you program or does anything make it less or more confusing in the background changes?
24:30 – Val answers the before-mentioned question. Async/Await does not have anyway to help with this (data changes in the background).
25:36 – “My procedural code, I know that things won’t change on me because it is procedural code. Is it hard to adjust to that?” – AJ
26:01 – Val answers the question.
26:32 – Building a webserver with Python.
27:31 – Aimee asks a question: “Do you think that there are cases in code base, where I would want to use Promises? Not from a user’s perspective, but what our preferences are, but actual performance. Is there a reason why I would want to use both or be consistent across the board?”
28:17 – Val asks for some clarification to Aimee’s question.
29:14 – Aimee: “My own personal preference is consistency. Would I want to use Promises in ‘x’ scenario and/or use Async/Await in another situation?”
32:28 – Val and AJ are discussing and problem solving different situations that these programs
33:05 – “When would you not want to use Async/Await?” – AJ
33:25 – Val goes through the different situations when he would not use Async/Await.
33:44 – Chuck is curious about other features of Async/Await and asks Val.
36:40 – Facebook’s Regenerator
37:11 – AJ: “Back in the day, people would be really concerned with JavaScript’s performance even with Chrome.” He continues his thoughts on this topic.
38:11 – Val answers the AJ’s question.
39:10 – Duck JS probably won’t include generators.
41:18 – Val: “Have anyone used Engine Script before?” The rest of the panel had never heard of this before.
42:09 – Windows Scripting Host
42:56 – Val used Rhino in the past.
43:40 – Val: “Going back to the web performance question...”
47:08 – “Where do you see using Async/Await the most?” – Chuck
47:55 – Val uses Async/Await for everything on the backend because it has made everything so easy for him.
48:23 – “So this is why you really haven’t used Web Pack?” – AJ
49:20 – Let’s go to Aimee’s Picks!
50:18 – AJ’s story, first, before we get to Promises.
54:44 – Let’s transition to Promises Finally.
54:53 – Val talks about Promises Finally.
59:20 – Picks
Links:
- JavaScript
- Valeri Karpov’s GitHub
- Valeri Karpov’s Twitter
- Valeri Karpov’s LinkedIn
- New E-Book: Mastering Async/Await
- Node
- Python
- Windows Scripting Host
- Facebook’s Regenerator
- Rhino
Sponsors:
- Kendo UI
- Sentry
- Digital Ocean
Picks:
Charles
- YouTube Video “IKEA” by Coulton
- Conference
- Amazon Prime Day
Aimee
- Blog Post Article
AJ
- IKEA
- https://ppl.family
Val
- https://www.npmjs.com/package/serve
- http://bit.ly/ultimate-skiing
- http://asyncawait.net/jsjabber
- New E-Book: Mastering Async/Await
The podcast and artwork embedded on this page are from Top End Devs, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Coding Blocks (LS 61 · TOP 0.5% what is this?)
Episode: Javascript Promises and Beyond
Pub date: 2015-08-22
In this episode we dive into Javascript Promises. If you’re used to the olden way of doing an async call with a callback, you’ll definitely want to give this episode a listen […]
The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
Podcast: Nerdette (LS 62 · TOP 0.1% what is this?)
Episode: Popular vs. Cool With Derek Thompson
Pub date: 2017-02-24
Derek Thompson, senior editor of The Atlantic, tells Nerdette's Tricia Bobeda about his new book Hit Makers: The Science of Popularity in an Age of Distraction. He explains what makes Adele’s "Hello" and Drake’s "Hotline Bling" top hits and how Star Wars was almost totally unknown.
The podcast and artwork embedded on this page are from Greta Johnsen, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.