Podcasts about Peter Cooper

What drives someone to publish 600+ issues of a Postgres newsletter for over a decade? In Episode 28 of Talking Postgres with Claire Giordano, Peter Cooper—creator of Postgres Weekly—shares how his days of rustic programming and QBASIC fanzines on Usenet led to a newsletter empire that now reaches nearly half a million developers each week. We dig into the BBC's "big tent" editorial influence, an accidental business model that just worked, and the perils of "temporary" hacks. Plus: spam filters, a Photoshop addiction, and one very cheesy story (dairy-free).Links mentioned in this episode:Newsletter: Postgres WeeklyCooperpress: List of newslettersNewsletter: Latest issue of Postgres Weekly on Jun 19, 2025Newsletter: Postgres Weekly issue with horrible graphicNewsletter: Very first issue of Postgres Weekly on Mar 13, 2013Newsletter: Ruby Weekly, the first Cooperpress newsletterBook: Beginning Ruby Third Edition, by Peter CooperPodcast episode: How I got started as a developer (& in Postgres) with David RowleyFeed reader: FeedbinGitHub repo: feedbin/feedbinFeed reader: FeederEmail testing software: LitmusGitHub repo: MGML markup language for emailPaper: The Design of PostgresGitHub repo: PGRX for building Postgres extensions in RustPodcast news: Podnews.net for daily briefings about podcastsWikipedia page: BBC MicroWikipedia page: ZX SpectrumCal invite: LIVE recording of Ep29 of Talking Postgres to happen on Wed Jul 9, 2025

In this special live event episode recorded in Melbourne, Inside The Rope celebrates a milestone with its 176th episode, marking the second live event in honor of 175 episodes. The event features an impressive lineup of guests from the world of finance and investment, each bringing their unique insights and experiences to the table. Guest Speakers: Michael Lukin, CFA: Group Managing Partner of Roc Partners, Michael Lukin shares his journey from the management buy-out of Macquarie Group's private markets business to leading client relationships and investment activities across various markets. He provides a deep dive into his experience managing major investments, including companies like StoneAxe and Australia's Oyster Coast. Peter Cooper: The Chief Investment Officer and founder of Cooper Investors, Peter Cooper, brings over 30 years of investment management experience to the stage. He discusses the VoF investment philosophy he developed, which has been instrumental in the success of Cooper Investors across both domestic and international strategies. Samar Mcheileh: Managing Partner at Scale, Samar Mcheileh shares her passion for venture capital and her vision of transforming Scale into a fully-matured fund. Her experience in financial services, including her transformative work at JBWere and her active role in the Australian early-stage ecosystem, adds a dynamic perspective to the conversation.

Tycoons win and lose on the sharemarket just like the rest of us: This week Peter Cooper had a win with Guzman Y Gomez but then 'Hungry Jack' Cowin has watched his Domino's Pizza shares drop by a third so far in 2024. What can we learn from tycoon stock-picking? In today's episode we cover  * The stocks that paid off big time for Rich 250 players * Terrible tycoon stock picks of 2024 (so far) * The Australian who has $900m worth of Nvidia stock  * How stock splits work  John Stensholt editor of The Rich 250 joins wealth editor James Kirby in this episode See omnystudio.com/listener for privacy information.

Many places in the US are experiencing huge amounts of rainfall with flooding and other problems associated with this amount of moisture. This week on the program we'll honor them with songs about water, rain and floods. Music from Ramsey Lewis, Eva Cassidy, Gordon Lightfoot, Stan Rogers, and lots more. Come wade in the water … this week on The Sing Out! Radio Magazine.Pete Seeger / “If I Had A Hammer”(excerpt) / Songs of Hope and Struggle / Smithsonian FolkwaysRamsey Lewis Trio / “Wade in the Water” / Wade in the Water / CadetTellico / “It's Just Rain” / Woven Waters / OrganicBetse & Clarke / “Rolling River” / River Still Rise / Smiling VioletDirk Powell / “Waterbound” / The Transatlantic Sessions Series Five, Vol. 2 / WhirlieEric Brace, Peter Cooper, Thom Jutz / “Down Along the River” / Riverland / Red BeetAnnie Staninec / “Willow on the Lake” / Annie Staninec / Self-producedGordon Lightfoot / “Early Morning Rain” / Gord's Gold / Warner BrothersSquirrel Butter / “Muddy Creek” / Renderings / Self-producedEva Cassidy / “Wade in the Water” / Eva By Heart / Blix StreetMargo Murphy & John Roberts / “Sea Fever” / The Sea and the Sky / RainmakersMoira Smiley / “Bring Me Little Water Silvy” / Bring Me Little Water Silvy / Self-producedHot Tuna / “Water Song” / Burgers / GruntIncredible String Band / “The Water Song” / The Hangman's Beautiful Daughter / ElektraStan Rogers / “White Squall” / Very Best of Stan Rogers / BorealisSally Rogers / “Lovely Agnes” / The Circle of the Sun / Flying FishPete Seeger / “If I Had A Hammer”(excerpt) / Songs of Hope and Struggle / Smithsonian Folkways

In this episode, James Cooper, Director of Peter Cooper Ltd discusses how he began within the industry full time from the age of 21, although as a second-generation remover he helped out in the family business during school holidays from 12/13. James was begrudgingly shuffled off to college followed by university (to study marketing), mainly by his mother, to gain a degree to fall back on should he not want to return to the family business, although the goal was always for James to return. But prior to James's return to the family business, he went on to learn his removal foundation skills from White & Co initially and then GB Liners. Peter Cooper Ltd was started in 1986 by James's parents, and provide domestic (predominantly), European, international & commercial relocations, secure shredding, and storage, but also offer an antique restoration and repair side of the business too, as Peter (James's father) was trained as an antique restorer. On the removals side James runs a full-time removal crew of 12, and 3 restorers on the antique side, operating a varied fleet of 11 vehicles. James has overcome several challenges, in the early days it was being the boss's son, but Covid was his biggest challenge. The one thing James would change from his moving past is to have purchased land that became available on the industrial estate they currently reside, but the land and the build costs were just astronomical. James's highpoint of being within the industry are when the guys return from their jobs with a clean job ticket, and they and the customers are happy, then it's a good day. The one thing James would like to change within the industry is people's perception of what our industry is about. The advice James would give himself just starting out within the industry again is that you can never have to many friends within the industry, to ask questions, and to listen to the views of others no matter how different they may be to your own. In the next 5 years James believes he will be doing exactly what he is doing now, enjoying life, and hopefully taking more holidays, but probably still complaining about all the things the industry normally complains about on a yearly basis. Industry wise, James doesn't see any change as it slowly gets back to pre-Covid trends. Outside of the industry James has a very long to-do list composed by Mrs C, regarding the new home they purchased 5 years ago that requires a lot of work, so DIY is his current escapism. Up until a year ago James played football on a weekly basis, and in his youth was a schoolboy player for Southampton FC. And as always, we end Moving Matters with a funny moving story regarding an overnight in Hamburg, Germany. Enjoy! Links to Peter Cooper Ltd: * Website (https://www.petercooperltd.co.uk/) * Facebook (https://www.facebook.com/petercooperltd) Special Guest: James Cooper.

Welcome back to another episode of Rock is Lit, the podcast where we dive into the powerful intersection of rock music, literature, and pop culture. Today, we're stepping outside the realm of fiction as we embark on a fascinating journey into the 1960s with acclaimed author Frye Gaillard and his nonfiction book ‘A Hard Rain: America in the 1960s', which captures the heartbeat of an era, an era that has inspired so many of the rock novels featured on the podcast. In Frye's extraordinary book he not only delves into the tragic and hopeful narratives of civil rights, black power, women's liberation, and the Vietnam War but also unveils the cultural manifestations of change. From the Brothers Kennedy to Janis Joplin, Johnny Cash to Bob Dylan, and everything in between, ‘A Hard Rain' introduces us to the influential figures who shaped this iconic American decade. Listen to Episode 14, featuring Michael Amos Cody's novel ‘Gabriel's Songbook, with special guests Frye Gaillard and Peter Cooper: https://www.christyalexanderhallberg.com/rockislitpodcast/michaelamoscodyandfryegaillardandpetercooper Listen to my bonus uncut interview with Frye Gaillard and Peter Cooper: https://www.christyalexanderhallberg.com/podcast-vault-feed/petercoopertribute Or watch it on YouTube: https://www.youtube.com/watch?v=MGYwFdmrt8c&list=PLMlm_N-Z1yVrwPKpSnVZnH_twxo78eW8A&index=38   PLAYLIST Royalty-free 60s 70s psychedelic rock n roll music and visuals: https://www.youtube.com/watch?v=sGVRph0Dj1c&t=3s Rock is Lit theme music Clip from Season 3 Announcement/'Duck Tales'/Disney Channel [Guitar Instrumental Beat] Sad Rock [Free Use Music] Punch Deck—“I Can't Stop” Royalty-free 60s 70s psychedelic rock n roll music and visuals: https://www.youtube.com/watch?v=sGVRph0Dj1c&t=3s “We Shall Overcome” by Pete Seeger “Chain Gang” by Sam Cooke “Abilene” by George Hamilton, IV “A Hard Rain's A-Gonna Fall” by Bob Dylan “Only the Lonely” by Roy Orbison “A Change is Gonna Come” by Sam Cooke “Different Drum” by The Stone Poneys (with Linda Ronstadt) “Bad Moon Rising” by Creedence Clearwater Revival “Mississippi Goddamn” by Nina Simone “Abraham, Martin, and John” by Dion “Like a Rolling Stone” by Bob Dylan “Helter Skelter” by The Beatles “The Star Spangled Banner” by Jimi Hendrix (Live at Woodstock 1969) “If I Can Dream” by Elvis Presley Rock is Lit theme music   LINKS: Leave a rating and comment for Rock is Lit on Goodpods: https://goodpods.com/podcasts/rock-is-lit-212451 Leave a rating and comment for Rock is Lit on Apple Podcasts: https://podcasts.apple.com/us/podcast/rock-is-lit/id1642987350 Frye Gaillard's website: https://fryegaillardauthor.com/ Christy Alexander Hallberg's website: https://www.christyalexanderhallberg.com/rockislit Christy Alexander Hallberg on Instagram, Twitter, YouTube: @ChristyHallberg Learn more about your ad choices. Visit megaphone.fm/adchoices

Welcome back to another episode of Rock is Lit, the podcast where we dive into the powerful intersection of rock music, literature, and pop culture. Today, we're stepping outside the realm of fiction as we embark on a fascinating journey into the 1960s with acclaimed author Frye Gaillard and his nonfiction book ‘A Hard Rain: America in the 1960s', which captures the heartbeat of an era, an era that has inspired so many of the rock novels featured on the podcast. In Frye's extraordinary book he not only delves into the tragic and hopeful narratives of civil rights, black power, women's liberation, and the Vietnam War but also unveils the cultural manifestations of change. From the Brothers Kennedy to Janis Joplin, Johnny Cash to Bob Dylan, and everything in between, ‘A Hard Rain' introduces us to the influential figures who shaped this iconic American decade. Listen to Episode 14, featuring Michael Amos Cody's novel ‘Gabriel's Songbook, with special guests Frye Gaillard and Peter Cooper: https://www.christyalexanderhallberg.com/rockislitpodcast/michaelamoscodyandfryegaillardandpetercooper Listen to my bonus uncut interview with Frye Gaillard and Peter Cooper: https://www.christyalexanderhallberg.com/podcast-vault-feed/petercoopertribute Or watch it on YouTube: https://www.youtube.com/watch?v=MGYwFdmrt8c&list=PLMlm_N-Z1yVrwPKpSnVZnH_twxo78eW8A&index=38   PLAYLIST Royalty-free 60s 70s psychedelic rock n roll music and visuals: https://www.youtube.com/watch?v=sGVRph0Dj1c&t=3s Rock is Lit theme music Clip from Season 3 Announcement/'Duck Tales'/Disney Channel [Guitar Instrumental Beat] Sad Rock [Free Use Music] Punch Deck—“I Can't Stop” Royalty-free 60s 70s psychedelic rock n roll music and visuals: https://www.youtube.com/watch?v=sGVRph0Dj1c&t=3s “We Shall Overcome” by Pete Seeger “Chain Gang” by Sam Cooke “Abilene” by George Hamilton, IV “A Hard Rain's A-Gonna Fall” by Bob Dylan “Only the Lonely” by Roy Orbison “A Change is Gonna Come” by Sam Cooke “Different Drum” by The Stone Poneys (with Linda Ronstadt) “Bad Moon Rising” by Creedence Clearwater Revival “Mississippi Goddamn” by Nina Simone “Abraham, Martin, and John” by Dion “Like a Rolling Stone” by Bob Dylan “Helter Skelter” by The Beatles “The Star Spangled Banner” by Jimi Hendrix (Live at Woodstock 1969) “If I Can Dream” by Elvis Presley Rock is Lit theme music   LINKS: Leave a rating and comment for Rock is Lit on Goodpods: https://goodpods.com/podcasts/rock-is-lit-212451 Leave a rating and comment for Rock is Lit on Apple Podcasts: https://podcasts.apple.com/us/podcast/rock-is-lit/id1642987350 Frye Gaillard's website: https://fryegaillardauthor.com/ Christy Alexander Hallberg's website: https://www.christyalexanderhallberg.com/rockislit Christy Alexander Hallberg on Instagram, Twitter, YouTube: @ChristyHallberg Learn more about your ad choices. Visit megaphone.fm/adchoices

Today's guest is the renowned investor, Peter Cooper, founder and Chief Investment Officer of Cooper Investors. A founding supporter of Hearts and Minds, Peter is a staunch advocate of our model and its philanthropic purpose, actively engaging in every facet of Hearts and Minds. He's undoubtedly a deep thinker, which was evident in this podcast, with insights extending beyond his process and stock picking approach, delving into his business management strategies in funds management.This is a Hearts & Minds Podcast, in partnership with Equity Mates MediaFor more information about HM1 and the upcoming Sohn Hearts & Minds Conference visit our website hereDisclaimer:This communication has been prepared by Hearts and Minds Investments Limited (ABN 61 628 753 220). In preparing this publication the investment objectives, financial situation or particular needs of an individual have not been considered. You should not rely on the opinions, advice, recommendations and other information contained in this publication alone. The inclusion of third-party content does not in any way imply any form of endorsement by HM1 of the products or services provided by persons or organisations who are responsible for the third-party content. This publication has been prepared to provide you with general information only. It is not intended to take the place of professional advice and you should not take action on specific issues in reliance on this information. Past performance is not a reliable indicator of future performance. Hosted on Acast. See acast.com/privacy for more information.

James and Holley meet with prior Hattiesburger, R.S. Field (AKA Bobby Field), in his new home of Nashville, Tennessee to discuss his extensive and highly impressive collective work as a musician and producer. Field has played with the likes of Webb Wilder and Omar & The Howlers, as well as countless others. He has produced many well-known artists such as Sonny Landreth, Justin Townes Earl, John Mayall, and Billy Joe Shaver to name a few. Songs for the episode include "It's Gonna Feel Good (When It Stops Hurting)" by Allison Moore (Field on drums and guitar) and "Powerful Stuff" by The Fabulous Thunderbirds (co-written by Field). To quote Peter Cooper of Mix Magazine, "...for the past quarter-century or so, Field has been Music City's most significant and intriguing roots-rock producer."

James and Holley meet with prior Hattiesburger, R.S. Field (AKA Bobby Field), in his new home of Nashville, Tennessee to discuss his extensive and highly impressive collective work as a musician and producer. Field has played with the likes of Webb Wilder and Omar & The Howlers, as well as countless others. He has produced many well-known artists such as Sonny Landreth, Justin Townes Earl, John Mayall, and Billy Joe Shaver to name a few. Songs for the episode include "It's Gonna Feel Good (When It Stops Hurting)" by Allison Moore (Field on drums and guitar) and "Powerful Stuff" by The Fabulous Thunderbirds (co-written by Field). To quote Peter Cooper of Mix Magazine, "...for the past quarter-century or so, Field has been Music City's most significant and intriguing roots-rock producer."

We are starting to wind down on these 1876 Presidential Potentials and this man? This man is why New York is the way it is when people have good things to say about New York.

Episode 14 of Rock is Lit features Michael Amos Cody's novel ‘Gabriel's Songbook', a story that follows starry-eyed Gabriel Tanner on his quest to strike it big as a singer-songwriter in Nashville in the 1980s. In the final segment of that episode, Peter Cooper and Frye Gaillard join me to talk about the real Nashville music scene in the 1980s to add real-world context to Michael's novel. Frye is an historian and author of such books as ‘A Hard Rain: America in the 1960s', ‘The Southernization of America', which he co-wrote with Pulitzer Prize-winner Cynthia Tucker, and ‘Watermelon Wine: The Spirit of Country Music'. On a sad note, the morning Episode 14 first aired, I received a message from Frye Gaillard, giving me the tragic news that Peter Cooper had passed away just two days prior—on Tues, Dec 6, 2022. Peter was the Country Music Hall of Fame and Museum's senior director, producer, and writer. As one of Nashville's most respected music journalists, he wrote for the ‘Tennessean', ‘American Songwriter', ‘Esquire' and numerous other publications His insight was deepened by his experiences as a Grammy-nominated producer, a singer, a songwriter and a touring musician. His songs were recorded by luminaries including John Prine, Todd Snider, and Country Music Hall of Fame members Bobby Bare and Mac Wiseman. Country Music Hall of Fame member Kris Kristofferson said, “Peter Cooper looks at the world with an artist's eye and a human heart and soul.” What you're about to hear is the full interview I recorded with Frye Gaillard and Peter Cooper on Tues, Oct 18, 2022, less than two months before Peter's death. I offer it to you now as a tribute to Peter—in honor of his life and in gratitude for the insight he and Frye brought to Episode 14 of Rock is Lit about Michael Amos Cody's novel ‘Gabriel's Songbook,' a book Peter so enjoyed. I wish all of Peter's friends and family peace and healing. Listen to this bonus interview, then check out Episode 14 of Rock is Lit. For more information and photos on this bonus interview, see https://www.christyalexanderhallberg.com/podcast-vault-feed/petercoopertribute You can also access the interview on YouTube. If you enjoy the podcast, please leave a rating and comment. LINKS: Michael Amos Cody's website: https://michaelamoscody.com/ Michael on Twitter, @DrMacOde Michael on Instagram, @michaelamoscody   Frye Gaillard's website: https://fryegaillardauthor.com/ Frye on Facebook, @FryeGaillard   Christy Alexander Hallberg's website: https://www.christyalexanderhallberg.com/ Christy Alexander Hallberg on Twitter, @ChristyHallberg Christy Alexander Hallberg on Instagram, @christyhallberg Christy Alexander Hallberg's YouTube channel, https://www.youtube.com/channel/UCfSnRmlL5moSQYi6EjSvqag Learn more about your ad choices. Visit megaphone.fm/adchoices

Episode 14 of Rock is Lit features Michael Amos Cody's novel ‘Gabriel's Songbook', a story that follows starry-eyed Gabriel Tanner on his quest to strike it big as a singer-songwriter in Nashville in the 1980s. In the final segment of that episode, Peter Cooper and Frye Gaillard join me to talk about the real Nashville music scene in the 1980s to add real-world context to Michael's novel. Frye is an historian and author of such books as ‘A Hard Rain: America in the 1960s', ‘The Southernization of America', which he co-wrote with Pulitzer Prize-winner Cynthia Tucker, and ‘Watermelon Wine: The Spirit of Country Music'. On a sad note, the morning Episode 14 first aired, I received a message from Frye Gaillard, giving me the tragic news that Peter Cooper had passed away just two days prior—on Tues, Dec 6, 2022. Peter was the Country Music Hall of Fame and Museum's senior director, producer, and writer. As one of Nashville's most respected music journalists, he wrote for the ‘Tennessean', ‘American Songwriter', ‘Esquire' and numerous other publications His insight was deepened by his experiences as a Grammy-nominated producer, a singer, a songwriter and a touring musician. His songs were recorded by luminaries including John Prine, Todd Snider, and Country Music Hall of Fame members Bobby Bare and Mac Wiseman. Country Music Hall of Fame member Kris Kristofferson said, “Peter Cooper looks at the world with an artist's eye and a human heart and soul.” What you're about to hear is the full interview I recorded with Frye Gaillard and Peter Cooper on Tues, Oct 18, 2022, less than two months before Peter's death. I offer it to you now as a tribute to Peter—in honor of his life and in gratitude for the insight he and Frye brought to Episode 14 of Rock is Lit about Michael Amos Cody's novel ‘Gabriel's Songbook,' a book Peter so enjoyed. I wish all of Peter's friends and family peace and healing. Listen to this bonus interview, then check out Episode 14 of Rock is Lit. For more information and photos on this bonus interview, see https://www.christyalexanderhallberg.com/podcast-vault-feed/petercoopertribute You can also access the interview on YouTube. If you enjoy the podcast, please leave a rating and comment. LINKS: Michael Amos Cody's website: https://michaelamoscody.com/ Michael on Twitter, @DrMacOde Michael on Instagram, @michaelamoscody   Frye Gaillard's website: https://fryegaillardauthor.com/ Frye on Facebook, @FryeGaillard   Christy Alexander Hallberg's website: https://www.christyalexanderhallberg.com/ Christy Alexander Hallberg on Twitter, @ChristyHallberg Christy Alexander Hallberg on Instagram, @christyhallberg Christy Alexander Hallberg's YouTube channel, https://www.youtube.com/channel/UCfSnRmlL5moSQYi6EjSvqag Learn more about your ad choices. Visit megaphone.fm/adchoices

The Sundilla Radio Hour for the week of 12/26/2022 featuring: Austin MacRae “Last of the Hollers” Better Devil (2019 Austin MacRae) 5:02 Jack Williams “If My Eyes Were Blind” A Tickle in My Soul (2022 Jack Williams) 3:26 Liz Simmons “When the Waters Rise” Poets (2021 Liz Simmons) 3:57 Joe Crookston “Darkling/BlueBird (Fear & Transcend)” Darkling & the BlueBird Jubilee (2011 Joe Crookston) 4:01 Amythyst Kiah “Firewater” Wary + Strange (2021 Rounder) 3:39 Noah Zacharin “Moon On My Side” silence Spoken Here (1998 Soffwin) 3:35 Low Lily “We Bring the Light” Single (2021 Low Lily) 3:26 Chad Elliott “Strayful and Feverfew” Tangle with the Ghost (2020 Chad Elliott) 3:08 Heather Pierson Acoustic Trio “Thunderous Voices” Singin' (2017 Heather Pierson) 3:16 Peter Cooper “Feels Like Home” Opening Day (2013 Peter Cooper) 2:42 Sunny War “A Love so True” Simple Syrup (2021 Sunny War) 3:34 Joe Jencks “Let Me Sing You a Song” Poets, Philosophers, Workers & Wanderers (2017 Joe Jencks) 4:34 Annalise Emerick “This Love Won't Break Your Heart” Starry-Eyed (2011 Annalise Emerick) 4:48

When Peter Cooper died in Nashville earlier this month, famous country singers and so many others quickly memorialized the incredible writing and musical career he created despite passing away young at the age of 52.  What Tim didn't know, he's the brother of Western Carolina University political scientist Dr. Chris Cooper.  Chris is a regular on our TV shows and has appeared on this podcast.  Despite years of knowing each other, the connection was never made, so Tim asked Chris to talk about his brother and share some unbelievable stories. It's fitting as a part of this podcast's mission to tell the stories behind the people and stories of North Carolina politics. 

Episode 230: With an instantly recognizable voice and uncommon skill for balancing melancholy with radiance, Courtney Marie Andrews has released a string of four acclaimed album since her 2016 breakout Honest Life. She's a Tucson, AZ native who hit the road on her own at the tender age of 16 and gave her life over to writing and sharing her soul with others. Her newest follows the arc of a new love affair, from ambivalent beginnings to a rapturous consummation in the final song. Its airy, sculpted sound matches the journey and assures the Nashville-based artist of another round of attention and respect. Also this hour, some archival tape with Nashville music journalist and songwriter/artist Peter Cooper, who died last week at age 52. 

In this episode we're venturing inside the complicated world of the Nashville music biz. Michael Amos Cody joins me to talk about his novel ‘Gabriel's Songbook', which follows starry-eyed Gabriel Tanner on his quest to strike it big as a singer-songwriter in the Music City in the 1980s. In the final segment, Frye Gaillard and Peter Cooper drop by to talk about the real Nashville music scene in the 1980s. Frye is an historian and author of such books as ‘A Hard Rain: America in the 1960s', ‘The Southernization of America', which he co-wrote with Pulitzer Prize-winner Cynthia Tucker, and ‘Watermelon Wine: The Spirit of Country Music'. Peter is the Country Music Hall of Fame and Museum's senior director, producer, and writer. HIGHLIGHTS:Christopher Cross's buried guitar lead on “Ride Like the Wind”Suzi Quatro's convincing argument for including Simon & Garfunkel in a rock novelThe Appalachian setting and culture for part of the novel ‘Gabriel's Songbook' and what Appalachia means to Michael and the character Gabriel: food, religion, family, community, mountain musicThe complexities and difficulties of an image-driven music business during the MTV 1980s on singer-songwriters, like Gabriel, who don't fit the moldMichael's own experience as a young musician in Nashville during this timeHow Michael's relationship with his wife, Leesa, inspired the relationship between Gabriel and Eliza in ‘Gabriel's Songbook'The passion that Michael still feels for making musicFrye and Peter talk about the differences between the ‘70s and '80s Nashville music scene and business MUSIC AND MEDIA IN THE EPISODE IN ORDER OF APPEARANCE:Free Country Instrumental Music/No Copyright Background Music“Born the Run” by Bruce Springsteen“Ride Like the Wind” by Christopher Cross“April Come She Will” by Simon & Garfunkel“Mountain Dew” by The Stanley Brothers“Lookin' for Love” by Johnny Lee“Mexican Radio” by Wall of Voodoo“Best I've Ever Seen” by Michael Amos Cody“Leesa, Listen” by Michael Amos Cody“Soulmates” by Michael Amos Cody“You've Got Something I Need” by Michael Amos Cody“The Sweetest Gift” by Dolly Parton, Linda Ronstadt, and Emmylou Harris“Better Class of Losers” by Randy Travis“Molly Dear” by Jonathan Byrd“I Came for the Gold” by Michael Amos Cody LINKS: Michael Amos Cody's website: https://michaelamoscody.com/Michael on Twitter, @DrMacOdeMichael on Instagram, @michaelamoscody Frye Gaillard's website: https://fryegaillardauthor.com/Frye on Facebook, @FryeGaillard Peter Cooper's website: https://www.petercoopermusic.com/Peter Cooper on Facebook, @PeterCooper Christy Alexander Hallberg's website: https://www.christyalexanderhallberg.com/Christy Alexander Hallberg on Twitter, @ChristyHallbergChristy Alexander Hallberg on Instagram, @christyhallbergChristy Alexander Hallberg's YouTube channel, https://www.youtube.com/channel/UCfSnRmlL5moSQYi6EjSvqag

Reposting this episode in memory of Peter Cooper, who we sadly lost today. After crouching to fit under the doorway, singer/songwriter/journalist and gentle giant Peter Cooper steps into the portable pod booth to chat with host Jeremy Dylan about a classic from one of the classiest songwriters in country music - Tom T Hall's 1971 album “In Search of a Song”. Along the way, they break down tracks including “The Year Clayton Delany Died”, “Trip to Hyden” and “A Million Miles to the City” and talk about Hall's songwriting research trips, how he broke his own songwriting rules, the difference between poetry and song lyrics and why you shouldn't waste time complaining about music you hate.

Reposting this episode in memory of Peter Cooper, who we sadly lost today. Journalist and singer-songwriter Peter Cooper of the Country Music Hall of Fame joins me to talk about Jim Lauderdale's classic ‘Pretty Close to the Truth' album and how the changes in country music in the 90s created the need for the Americana music genre, the migration of people like Jim and his friend and collaborator Buddy Miller from California to Nashville, and how Jim helped Peter propose to his wife.

In this episode we're venturing inside the complicated world of the Nashville music biz. Michael Amos Cody joins me to talk about his novel ‘Gabriel's Songbook', which follows starry-eyed Gabriel Tanner on his quest to strike it big as a singer-songwriter in the Music City in the 1980s.  In the final segment, Frye Gaillard and Peter Cooper drop by to talk about the real Nashville music scene in the 1980s. Frye is an historian and author of such books as ‘A Hard Rain: America in the 1960s', ‘The Southernization of America', which he co-wrote with Pulitzer Prize-winner Cynthia Tucker, and ‘Watermelon Wine: The Spirit of Country Music'. Peter is the Country Music Hall of Fame and Museum's senior director, producer, and writer.   HIGHLIGHTS: Christopher Cross's buried guitar lead on “Ride Like the Wind” Suzi Quatro's convincing argument for including Simon & Garfunkel in a rock novel  The Appalachian setting and culture for part of the novel ‘Gabriel's Songbook' and what Appalachia means to Michael and the character Gabriel: food, religion, family, community, mountain music The complexities and difficulties of an image-driven music business during the MTV 1980s on singer-songwriters, like Gabriel, who don't fit the mold Michael's own experience as a young musician in Nashville during this time How Michael's relationship with his wife, Leesa, inspired the relationship between Gabriel and Eliza in ‘Gabriel's Songbook' The passion that Michael still feels for making music Frye and Peter talk about the differences between the ‘70s and '80s Nashville music scene and business   MUSIC AND MEDIA IN THE EPISODE IN ORDER OF APPEARANCE: Free Country Instrumental Music/No Copyright Background Music “Born the Run” by Bruce Springsteen “Ride Like the Wind” by Christopher Cross “April Come She Will” by Simon & Garfunkel “Mountain Dew” by The Stanley Brothers “Lookin' for Love” by Johnny Lee “Mexican Radio” by Wall of Voodoo “Best I've Ever Seen” by Michael Amos Cody “Leesa, Listen” by Michael Amos Cody “Soulmates” by Michael Amos Cody “You've Got Something I Need” by Michael Amos Cody “The Sweetest Gift” by Dolly Parton, Linda Ronstadt, and Emmylou Harris “Better Class of Losers” by Randy Travis “Molly Dear” by Jonathan Byrd “I Came for the Gold” by Michael Amos Cody   LINKS:  Michael Amos Cody's website: https://michaelamoscody.com/ Michael on Twitter, @DrMacOde Michael on Instagram, @michaelamoscody   Frye Gaillard's website: https://fryegaillardauthor.com/ Frye on Facebook, @FryeGaillard   Peter Cooper's website: https://www.petercoopermusic.com/ Peter Cooper on Facebook, @PeterCooper   Christy Alexander Hallberg's website: https://www.christyalexanderhallberg.com/ Christy Alexander Hallberg on Twitter, @ChristyHallberg Christy Alexander Hallberg on Instagram, @christyhallberg Christy Alexander Hallberg's YouTube channel, https://www.youtube.com/channel/UCfSnRmlL5moSQYi6EjSvqag Learn more about your ad choices. Visit megaphone.fm/adchoices

Carlton player Chris Judd is just one of the many fans of one of Australia's most highly regarded investors, Peter Cooper from Cooper Investors.Peters CI Brunswick Fund of which he is still charged with managing directly has returned investors an annualised gain of 16.79% since inception in 2004.However, Peter's influence across the Australian investing landscape is much greater than the single performance of any of the Cooper Investors funds. Countless successful fund managers have cut their teeth learning how to invest the “Cooper's way" before going on to start high performing funds of their own, speaking volumes about the culture that Peter and his team have been able to create.As well as their flagship Australian Equities Fund, the team at CI manage Global and Asian Equities, Endowment style Funds and specialist funds.Peter has in excess of 30 years market experience and is highly regarded for his passion, integrity and purpose.It's fair to say that Peter Cooper is not your ordinary stock picker.The daily meditator, yoga devotee has almost single-handedly built a $10 billion investment powerhouse with little of the fuss and none of the media profile that comes with the territory."We are Toyota Land Cruiser people and not Range Rover types" Cooper responded in an Aus Financial Review piece about his success.It's On His own personal journey of life balance wellness and connection that he met his wife Suparna Bhasin Cooper.Suparna is a force of nature dedicated to wellness at every level facilitating Silent Retreats both in Byron Bay and India and is spearheading the new Be Well community in Melbourne - a hub of wellness warriors determined to give back and honour self care.An inspirational speaker, philanthropist and longtime meditator. Her goal is to bring ancient Vedic practices such as meditation, breath-work and yoga, to different communities around the globe. Suparna holds a Master of Arts in Organizational Psychology from Columbia University.Suparna is co-founder of the MaiTri Foundation along with her husband, Peter Cooper. The MaiTri Foundation is the private family foundation of Peter and Suparna with a focus on helping to solve the mental health crisis as well as spreading the philosophy of individual rights and freedom.In 2018, Suparna made the decision to dedicate her time and resources to making a meaningful impact and creating lasting change through her charitable activities.  Suparna is a sought-after speaker and has presented at the Deepak Chopra Summit.When I Attended their beautiful wedding in India recently it was an exemplification of everything they are.Set against the awesome landscape of The Art of Living 200 acre ashram in Bangalore, their Union was an ode to self care, spirituality mental wellness and ageing gracefully - one of the most connecting inspiring and special experiences I've been part of - the colour the music, meditation, food the people it was quite life changing culturally immersive and enlightening.Encompassing meditation yoga intuition science collaborations with global universities and fostering an incredible educational facility .. there was a strong lense of philanthropy as the nuptials refDeborah's Instagram: https://www.instagram.com/what.ive.learnt/Mind, Film and Publishing: https://www.mindfilmandpublishing.com/Apple Podcast: https://podcasts.apple.com/au/podcast/what-ive-learnt/id153556330Spotify: ...

Have you ever wondered how Jell-O came to be the summer-time staple that it is today? Well, it starts with a 27-hour process exclusive to the elite of Medieval Europe and trickles down to be a powdered packaged patent that Peter Cooper cannot seem to sell fast enough. A lot happens from there to the Cherry-flavored Jell-O shots that I took part in last weekend, so take a listen!! 

Chris came up with a mnemonic device: Fn-Delete – for when he really wants to delete something and is also thinking about password complexity requirements, which leads to an exciting discussion around security theater. Steph talks about the upcoming RailsConf and the not-in-person option for virtual attendees. She also gives a shoutout to the Ruby Weekly newsletter for being awesome. NIST Password Standards (https://specopssoft.com/blog/nist-password-standards/) 3 ActiveRecord Mistakes That Slow Down Rails Apps: Count, Where and Present (https://www.speedshop.co/2019/01/10/three-activerecord-mistakes.html) Difference between count, length and size in an association with ActiveRecord (https://bhserna.com/count-size-length-active-record.html) Ruby Weekly (https://rubyweekly.com/) Railsconf 2022 (https://railsconf.org/) Become a Sponsor (https://thoughtbot.com/sponsorship) of The Bike Shed! Transcript: STEPH: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Steph Viccari. CHRIS: And I'm Chris Toomey. STEPH: And together, we're here to share a bit of what we've learned along the way. So hey, Chris, happy Friday. You know, each time I do that, I can't resist the urge to say happy Friday, but then I realize people aren't listening on a Friday. So happy day to anyone that's listening. What's new in your world, friend? CHRIS: I'm going to be honest; you threw me for a loop there. [laughs] I think it was the most recent episode where we talked about my very specific...[laughs] it's a lovely Friday, that's true. There's sun and clouds. Those are true things. But yeah, what's new in my world? [laughs] I can do this. I can focus. I got this. Actually, I have one thing. So this is going to be, I'm going to say vaguely selfish, but I have this thing that I've been trying to commit into my brain for a long time, and I just can't get it to stick. So today, I came up with like a mnemonic device for it. And I'm going to share it on The Bike Shed because maybe it'll be useful for other people. And then hopefully, in quote, unquote, "teaching it," I will deeply learn it. So the thing that happens in my world is occasionally, I want to delete a URL from Chrome's autocomplete. To be more specific, because it's easier for people to run away with that idea, it's The Weather Channel. I do not like weather.com. I try to type weather often, and I just want Google to show me the little, very quick pop-up thing there. I don't want any ads. I don't want to deal with that. But somehow, often, weather.com ends up in my results. I somehow accidentally click on it. It just gets auto-populated, and then that's the first thing that happens whenever I type weather into the Omnibox in Chrome. And I get unhappy, and I deal with it for a while, then eventually I'm like, you know what? I'm deleting it. I'm getting it out of there. And then I try and remember whatever magical key combination it is that allows you to delete an entry from the drop-down list there. And I know it's a weird combination of like, Command-Shift-Alt-Delete, Backspace, something. And every single time, it's the same. I'm like, I know it's weird, but let me try this one. How about that one? How about that one? I feel like I try every possible combination. It's like when you try and plug in a USB drive, and you're like, well, it's this way. No, it's the other way. Well, there are only two options, and I've already tried two things. How can I not have gotten it yet? But I got it now. Okay, so on a Mac specifically, the key sequence is Shift-Function-Delete. So the way I'm going to remember this is Function is abbreviated on the keyboard as Fn. So that can be like I'm swearing, like, I'm very angry about this. And then Shift is the way to uppercase something like you're shouting. So I just really need to Fn-Delete this. So that's how I'm going to remember it. Now I've shared it with everyone else, and hopefully, some other folks can get utility out of that. But really, I hope that I remember it now that I've tried to boil it down to a memorable thing. STEPH: [laughs] It's definitely memorable. I'm now going to remember just that I need to Fn-Delete this. And I'm not going to remember what it all is tied to. [laughs] CHRIS: That is the power of a mnemonic device. Yeah. STEPH: Like, I know this is useful in some way, but I can't remember what it is. But yeah, that's wonderful. I love it. That's something that I haven't had to do in a long time, and I hadn't thought about. I need to do that more. Because you're right, especially changing projects or things like that, there are just some URLs that I don't need cached anymore; I don't want auto-completed. So yeah, okay. I just need to Fn-Delete it. I'll remember it. Here we go. I'm speaking this into the universe, so it'll be true. CHRIS: Just Fn-Delete it. STEPH: Your bit about the USB and always getting it wrong, you get it 50-50 [laughs] by getting it wrong, resonates so deeply with me and my capability with directions where I am just terrible whether I have to go right or left. My inner compass is going to get it wrong. And I've even tried to trick myself where I'm like, okay, I know I'm always wrong. So what if I do the opposite of what Stephanie would do? And it's still somehow wrong. [laughs] CHRIS: Somehow, your brain compensates and is like, oh, I know that we're going to do that. So let's...yeah, it's amazing the way these things happen. STEPH: Yep. I don't understand it. I've tried to trick the software, but I haven't figured out the right way. I should probably just learn and get better at directions. But here we are. Here we are. CHRIS: You just loosely referred to the software, but I think you're referring to the Steph software when you say that. STEPH: Yes. Oh yeah, Steph software totally. You got it. [laughs] CHRIS: Gotcha. Cool. Glad that I checked in on that because that's great. But shifting gears to something a little bit deeper in the technical space, this past week, we've been thinking about passwords within our organization at Sagewell. And we're trying to decide what we want to do. We had an initial card that came through and actually got most of the way to implemented to dial up our password strictness requirements. And as I saw that come through, I was like, oh, wait, actually, I would love to talk about this. And so we had the work that was coming through the PR that had been opened was a pretty traditional set of let's introduce some requirements on our passwords for complexity, so let's make it longer. We're going from; I think six was the default that Devise shipped with, so we're increasing that to, I think it was eight. And then let's say that it needs a number, and a special character, and an uppercase letter or something like that. I've recently read the NIST rules, so the National Institute of Standards and Technology, I think, is what they are. But they're the ones who define a set of rules around this or guidelines. But I think they are...I don't know if they are laws or what at this point. But they tell you, "This is what you should and shouldn't do." And I know that the password complexity stuff is on the don't do that list these days. So I was like, this is interesting, and then I wanted to follow through. Interestingly, right now, I've got the Trello boards up for The Bike Shed right now. But as a result, I can't look at the linked Trello card that is on the workboards because they're in different accounts. And Trello really has made my life more difficult than I wanted. But I'm going to pull this up elsewhere. So let's see. So NIST stuff, just to talk through that, we can include a link in the show notes to a nice summary. But what are the NIST password requirements? Eight character minimum, that's great. Change passwords only if there is evidence of a compromise. Screen new passwords against a list of known compromised passwords. That's a really interesting one. Skip password hints, limit the number of failed authentication attempts. These all sound great to me. The maximum password length should be at least 64 characters, so don't constrain how much someone can put in. If they want to have a very long password, let them go for it. Don't have any sort of required rotation. Allow copy and pasting or functionality that allows for password managers. And allow the use of all printable ASCII characters as well as all Unicode characters, including emojis. And that one really caught my attention. I was like, that sounds fun. I wish I could look at all the passwords in our database. I obviously can't because they're salted and encrypted, and hashed, and all those sorts of things where I'm like, I wonder if anybody's using emojis. I'm pretty sure we would just support it. But I'm kind of intrigued. STEPH: You said something in that list that caught my attention, and I just want to see if I heard it correctly. So you said only offer change password if compromised? Does that mean I can't just change my password if I want to? CHRIS: Sorry. Yeah, I think the phrasing here might be a little bit odd. So it's essentially a different way to phrase this requirement is don't require rotation of passwords every six or whatever months. Forgotten password that's still a reasonable thing to have in your application, probably a necessity in most applications. But don't auto-rotate passwords, so don't say, "Your password has expired after six months." STEPH: Got it. Okay, cool. That makes sense. Then the emojis, oh no, it's like, I mean, I use a password manager now, and thanks to several years ago where he shamed me into using one. Thank you. That was great. [laughs] CHRIS: I hope it was friendly shame, but yeah. STEPH: Yes, it was friendly; kind shame if that sounds like a weird sentence to say. But yes, it was a very positive change. And I can't go back now that I have a password manager in my life. Because yeah, now I'm thinking like, if I had emojis, I'd be like, oh great, now I have to think about how I was feeling at the time that then I introduced a new password. Was I happy? Was I angry? Is it a poop emoji? Is unicorn? What is it? [laughs] So that feels complicated and novel. You also mentioned on that list that going for more complexity in terms of you have to have uppercase; you have to have a particular symbol, things like that are not on the recommended list. And I didn't know that. I'm so accustomed to that being requirements for passwords and the idea of how we create something that is secure and less easy to guess or to essentially hack. So I'm curious about that one if you know any more details about it as to why that's not the standard anymore. CHRIS: Yeah, I think I have some ideas around it. My understanding is mostly that introducing the password complexity requirements while intended to prevent people from using very common things like names or their user name or things like that, it's like, no, no, no, you can't because we've now constrained the system in that way. It tends in practice to lead to people having a variety of passwords that they forget all the time, and then they're using the forgotten password flow more often. And it basically, for human and behavior reasons, increases the threat surface area because it means that they're not able to use...say someone has a password scheme in mind where it's like, well, my passwords are, you know, it's this common base, and then some number of things specific to the site. It's like, oh no, no, we require three special characters, so it's like they can't do their thing. And now they have to write it down on a Post-it Note because they're not going to remember it otherwise. Or there are a variety of ways in which those complexity requirements lead to behavior that's actually less useful. STEPH: Okay, so it's the Post-it Note threat vector that we have to be worried about. [laughs] CHRIS: Which is a very real threat factor. STEPH: I believe it. [laughs] Yes, I know people that keep lists of passwords on paper near their desk. [laughs] This is a thing. CHRIS: Yep, yep, yep. The other thing that's interesting is, as you think about it, password complexity requirements technically reduce the overall combinatoric space that the passwords can exist in. Because imagine that you're a password hacker, and you're like, I have no idea what this password is. All I have is an encrypted hashed salted value, and I'm trying to crack it. And so you know the algorithm, you know how many passes, you know potentially the salt because often that is available. I think it has to be available now that I think about that out loud. But so you've got all these pieces, and you're like, I don't know, now it's time to guess. So what's a good guess of a password? And so if you know the minimum number of characters is eight and, the maximum is 12 because that actually happens on a lot of systems, that's actually not a huge combinatoric space. And then if you say, oh, and it has to have a number, and it has to have an uppercase letter, and it has to have a special character, you're just reducing the number of possible options in that space. And so, although this is more like a mathematical thing, but in my mind, I'm like, yeah, wait, that actually makes things less secure because now there are fewer passwords to check because they don't meet the complexity requirements. So you don't even have to try them if you're trying to brute-force crack a password. STEPH: Yeah, you make a really good point that I hadn't really thought about because I've definitely seen those sites that, yeah, constrain you in terms of like, has to have a minimum, has to have a maximum, and I hadn't really considered the fact that they are constraining it and then reducing the values that it could be. I am curious, though, because then it doesn't feel right to have no limit in terms of, like, you don't want people then just spamming your sign up and then putting something awful in there that has a ridiculous length. So do you have any thoughts on that and providing some sort of length requirement or length maximum? CHRIS: Yeah, I think the idea is don't prevent someone who wants to put in a long passphrase, like, let them do that. But there is, the NIST guidelines specifically say 64 characters. Devise out of the box is 128, I believe. I don't think we tweaked that, and that's what we're at right now. So you can write an old-style tweet and that can be your password if that's what you want to do. But there is an upper limit to that. So there is a reasonable upper limit, but it should be very permissive to anyone who's like, I want to crank it up. STEPH: Cool. Cool. Yeah, I just wanted to validate that; yeah, having an upper bound is still important. CHRIS: Yeah, definitely. Important...it's more for implementation and our database having a reasonable size and those sorts of things. Although at the end of the day, the thing that we saw is the encrypted password. So I don't know if bcrypt would run slower on a giant body of text versus a couple of characters; that might be the impact. So it would be speed as opposed to storage space because you always end up with a fixed-length hash of the same length, as far as I understand it. But yeah, it's interesting little trade-offs like that where the complexity requirements do a good job of forcing people to not use very obvious things like password. Password does not fit nearly any complexity requirements. But we're going to try and deal with that in a different way. We don't want to try and prevent you from using password by saying you must use an uppercase letter and a special character and things that make real passwords harder as well. But it is an interesting trade-off because, technically, you're making the crackability easier. So it gets into the human and the technical and the interplay between them. Thinking about it somewhat differently as well, there's all this stuff about you should salt your passwords, then you should hash them. You should run them through a good password hashing algorithm. So we're using bcrypt right now because I believe that's the default that Devise ships with. I've heard good things about Argon2; I think is the name of the new cool kid on the block in terms of password hashing. That whole world is very interesting to me, but at the end of the day, we can just go with Devise's defaults, and I'll feel pretty good about that and have a reasonable cost factor. Those all seem like smart things. But then, as we start to think about the complexity requirements and especially as we start to interact with an audience like Sagewell's demographics where we're working with seniors who are perhaps less tech native, less familiar, we want to reduce the complexity there in terms of them thinking of and remembering their passwords. And so, rather than having those complexity requirements, which I think can do a good job but still make stuff harder, and how do you communicate the failure modes, et cetera, et cetera, we're switching it. And the things that we're introducing are we have increased the minimum length, so we're up to eight characters now, which is NIST's low-end recommended, so it's between 8 and 128 characters. We are capturing anytime a I forgot password reset attempt happens and the outcome of it. So we're storing those now in the database, and we're showing them to the admins. So our admin team can see if password reset attempts have happened and if they were successful. That feels like good information to keep around. Technically, we could get it from the logs, but that's deeply hidden away and only really accessible to the developers. So we're now surfacing that information because it feels like a particularly pertinent thing for us. We've introduced Rack::Attack. So we're throttling those attempts, and if someone tries to just brute force through that credential stuffing, as the terminology goes, we will lock them out so either based on IP address or the account that they're trying to log into. We also have Devise's lockable module enabled. So if someone tries to log in a bunch of times and fails, their account will go into a locked state, and then an admin can unlock it. But it gives us a little more control there. So a bunch of those are already in place. The new one, this is the one that I'm most excited about, is we're going to introduce Have I Been Pwned? And so, they have an API. We can hit it. It's a really interesting model as to how do we ask if a password has been compromised without giving them the password? And it turns out there's this fun sort of cryptographic handshake thing that happens. K-anonymity is apparently the mechanism or the underpinning technology or idea. Anyway, it's super cool; I'm excited to build it. It's going to be fun. But the idea there is rather than saying, "Don't use a password that might not be secure," it's, "Hey, we actually definitively know that your password has been cracked and is available in plaintext on the internet, so we're not going to let you use that one." STEPH: And that's part of the signup flow as to where you would catch that? CHRIS: So we're going to introduce on both signup and sign-in because a password can be compromised after a user signs up for our system. So we want to have it at any point. Obviously, we do not keep their plaintext password, so we can't do this retroactively. We can only do it at the point in time that they are either signing up or signing in because that's when we do have access to the password. We otherwise throw it away and keep only the hashed value. But we'll probably introduce it at both points. And the interesting thing is communicating this failure mode is really tricky. Like, "Hey, your password is cracked, not like here, not on our site, no, we're fine. Well, you should probably change your password. So here's what it means, there's actually this database that's called Have I Been Pwned? Don't worry; it's good, though. It's P-W-N-E-D. But that's fine." That's too many words to put on a page. I can't even say it here in a podcast. And so what we're likely to do initially is instrument it such that our admin team will get a notification and can see that a user's password has been compromised. At that point, we will reach out to them and then, using the magic of human conversation, try and actually communicate that and help them understand the ramifications, what they should do, et cetera. Longer-term, we may find a way to build up an FAQ page that describes it and then say, "Feel free to reach out if you have questions." But we want to start with the higher touch approach, so that's where we're at. STEPH: I love it. I love that you dove into how to explain this to people as well because I was just thinking, like, this is complicated, and you're going to freak people out in panic. But you want them to take action but not panic. Well, I don't know, maybe they should panic a little bit. [laughs] CHRIS: They should panic just the right amount. STEPH: Right.[laughs] So I like the starting with the more manual process of reaching out to people because then you can find out more, like, how did people react to this? What kind of questions did they ask? And then collect that data and then turn that into an FAQ page. Just, well done. CHRIS: We haven't quite done it yet. But I am very happy with the collection of ideas that we've come to here. We have a security firm that we're working with as well. And so I had my weekly meeting with them, and I was like, "Oh yeah, we also thought about passwords a bunch, and here's what we came up with." And I was very happy that they were like, "Yeah, that sounds like a good set." I was like, "Cool. All right, I feel good." I'm very happy that we're getting to do this. And there's an interesting sort of interplay between security theater and real security. And security theater, just to explain the phrase if anyone's unfamiliar with it, is things that look like security, so, you know, big green lock up in the top-left corner of the URL bar. That actually doesn't mean anything historically or now. But it really looks like it's very secure, right? Or password complexity requirements make you think, oh, this must be a very secure site. But for reasons, that actually doesn't necessarily prove that at all. And so we tried to find the balance of what are the things that obviously demonstrate our considerations around security to the user? At the end of the day, what are the things that actually will help protect our users? That's what I really care about. But occasionally, you got to play the security theater game. Every other financial institution on the internet kind of looks and feels a certain way in how they deal with passwords. And so will a user look at our seemingly laxer requirements or laxer approach to passwords and judge us for that and consider us less secure despite the fact that behind the scenes look at all the fun stuff we're doing for you? But it's an interesting question and interesting trade-off that we're going to have to spend time with. We may end up with the complexity requirements despite the fact that I would really rather we didn't. But it may be the sort of thing that there is not a good way to communicate the thought and decision-making process that led us to where we're at and the other things that we're doing. And so we're like, fine, we just got to put them in and try and do a great job and make that as usable of an experience as possible because usability is, I think, one of the things that suffers there. You didn't do one of the things on the list, or like, it's green for each of the ones that you did, but it's red for the one that you didn't. And your password and your password confirmation don't match, and you can't paste...it's very easy to make this wildly complex for users. STEPH: Security theater is a phrase that I don't think I've used, but the way you're describing it, I really like. And I have a solution for you: underneath the password where you have "We don't partake in security theater, and we don't have all the other fancy requirements that you may have seen floating around the internet and here's why," and then just drop a link to the episode. And, you know, people can come here and listen. It'll totally be great. It won't annoy anyone at all. [laughs] CHRIS: And it'll start, and they'll hear me yelling about Fn-Delete that weather.com URL. [laughter] STEPH: Okay, maybe fast forward then to the part about -- CHRIS: Drop them to the timestamp. That makes sense. Yep. Yep. STEPH: Mm-hmm. Mm-hmm. [laughs] CHRIS: I like it. I think that's what we should do, yeah. Most features on the app should have a link to a Bike Shed episode. That feels true. STEPH: Excellent Easter egg. I'm into it. But yeah, I like all the thoughtfulness that y'all have put into this because I haven't had to think about passwords in this level of detail. And then also, yeah, switching over to when things start to change and start to move away, you're right; there's still that we need to help people then become comfortable with this new way and let them know that this is just as secure if not more secure. But then there's already been that standard that has been set for your expectations, and then how do you help people along that path? So yeah, seems like y'all have a lot of really great thoughtfulness going into it. CHRIS: Well, thank you. Yeah, it's frankly been a lot of fun. I really like thinking in this space. It's a fun sort of almost hobby that happens to align very well with my profession sort of thing. Actually, oh, I have one other idea that we're not going to do, but this is something that I've had in the back of my mind for a long time. So when we use bcrypt or Devise uses bcrypt under the hood, one of the things that it configures is the cost factor, which I believe is just the number of times that the password plus the salts and whatnot is run through the bcrypt algorithm. The idea there is you want it to be computationally difficult, and so by doing it multiple times, you increase that difficulty. But what I'd love is instead of thinking of it in terms of an arbitrary cost factor which I think is 12, like, I don't know what 12 means. I want to know it, in terms of dollars, how much would it cost to, like dollars and cents, to crack a password. Because, in theory, you can distribute this across any number of EC2 instances that you spin up. The idea of cracking a password that's a very map-reducible type problem. So let's assume that you can infinitely scale up compute on-demand; how much would it cost in dollars to break this password? And I feel like there's an answer. Like, I want that number to be like a million dollars. But as EC2 costs go down over time, I want to hold that line. I want to be like, a million dollars is the line that we want to have. And so, as EC2 prices go down, we need to increase our bcrypt cost factor over time to adjust for that and maintain the million dollar per password cracking sort of high bar. That's the dream. Swapping out the cost factor is actually really difficult. I've looked into it, and you have to like double encrypt and do weird stuff. So for a bunch of reasons, I haven't done this, but I just like that idea. Let's pin this to $1 value. And then, from there, decisions naturally flow out of it. But it's so much more of a real thing. A million dollars, I know what that means; 12, I don't know what 12 means. STEPH: A million-dollar password, I like it. I feel like -- CHRIS: We named the episode. STEPH: I was going to say that's a perfect title, A Million-Dollar Password. [laughs] CHRIS: A Million-Dollar Password. But with that wonderful episode naming cap there, I think I'm done rambling about passwords. What's up in your world, Steph? STEPH: One of the things that I've been chatting with folks lately is RailsConf is coming up; it's May 17 through the 19th. And it's been sort of like that casual conversation of like, "Hey, are you going? Are you going? Who's going? It's going to be great." And as people have asked like, "Are you going?" And I'm always like, "No, I'm not going." But then I popped on to the RailsConf website today because I was just curious. I wanted to see the schedule and the talks that are being given. And I keep forgetting that there's the in-person version, but there's also the home edition. And I was like, oh, I could go, I could do this. [laughs] And I just forget that that is something that is just more common now for conferences where you can attend them virtually, and that is just really neat. So I started looking a little more closely at the talks. And I'm really excited because we have a number of thoughtboters that are giving a talk at RailsConf this year. So there's a talk being given by Fernando Perales that's called Open the Gate a Little: Strategies to Protect and Share Data. There's also a talk being given by Joël Quenneville: Your Test Suite is Making Too Many Database Calls. I'm very excited; just that one is near and dear to my heart, given the current client experiences that I'm having. And then there's another one from someone who just joined thoughtbot, Christopher "Aji" Slater, Your TDD Treasure Map. So we'll be sure to include a link to those for anyone that's curious. But it's a stellar lineup. I mean, I'm always impressed with RailsConf talks. But this one, in particular, has me very excited. Do you have any plans for RailsConf? Do you typically wait for them to come out later and then watch them, or what's your MO? CHRIS: Historically, I've tended to watch the conference recordings after the fact. I went one year. I actually met Christopher "Aji" Slater at that very RailsConf that I went to, and I believe Joël Quenneville was speaking at that one. So lots of everything old is new again. But yeah, I think I'll probably catch it after the fact in this case. I'd love to go back in person at some point because I really do like the in-person thing. I'm thrilled that there is the remote option as well. But for me personally, the hallway track and hanging out and meeting folks is a very exciting part. So that's probably the mode that I would go with in the future. But I think, for now, I'm probably just going to watch some talks as they come out. STEPH: Yeah, that's typically what I've done in the past, too, is I kind of wait for things to come out, and then I go through and make a list of the ones that I want to watch, and then, you know, I can make popcorn at home. It's delightful. I can just get cozy and have an evening of RailsConf talks. That's what normal people do on Friday nights, right? That's totally normal. [laughs] CHRIS: I mean, yeah, maybe not the popcorn part. STEPH: No popcorn? CHRIS: But not that I'm opposed to popcorn just —- STEPH: Brussels sprouts? What do you need? [laughs] CHRIS: Yeah, Brussels sprouts, that's what it is. Just sitting there eating handfuls of Brussels sprouts watching Ruby conference talks. STEPH: [laughs] CHRIS: I do love Brussels sprouts, just to throw it out there. I don't want it to be out in the ether that I don't like them. I got an air fryer, and so I can air fry Brussels sprouts. And they're delicious. I mean, I like them regardless. But that is a really fantastic way to cook them at home. So I'm a big fan. STEPH: All right, I'm moving you into the category of fancy friends, fancy friends with an air fryer. CHRIS: I wasn't already in your category of fancy friends? STEPH: [laughs] I didn't think you'd take it that way. I'm sorry to break it to you. [laughter] CHRIS: I'm actually a little hurt that I'm now in the category of fancy friends. It makes a lot of sense that I wasn't there before. So I'll just deal with...yeah, it's fine. I'm fine. STEPH: It's a weird rubric that I'm running over here. Pivoting away quickly, so I don't have to explain the categorization for fancy friends, I saw something in the Ruby Weekly Newsletter that had just come out. And it's one of those that I see surface every so often, and I feel like it's a nice reminder because I know it's something that even I tend to forget. And so I thought it'd be fun just to resurface it here. And then, we can also provide a link to the wonderful blog post that's written by Benito Serna. And it's the difference between count, length, and size and an association with ActiveRecord. So for folks that would love a refresher, so count, that's a method that's always going to perform a SQL count query. So even if the collection has already been loaded, then calling count is always going to execute a database query. So this is the one that's just like, watch out, avoid it. You're always going to hit your database when you use this one. And then next is length. And so, length loads the whole collection into memory and then returns that length to the number of items in that collection. If the collection has been loaded, then it's not going to issue a database call. And then it's just still going to use...it's going to delegate to that Ruby length method and let you know how many records are in that collection. So that one is a little bit better because then that way, if it's already loaded, at least you're not going to have a database call. And then next is the size method, which is just the one that's more highly recommended that you use because this one does have a nice safety net that is built-in because first, it's going to check if we need to perform a database call, if the records have been loaded or not. So if the collection has not been loaded, so we haven't executed a database query and stored the result, then size is going to perform a database query. Specifically, it's using that SQL count under the hood. And if the collection has been loaded, then a database call is not issued, and then going to use the Ruby length method to then return the number of records. So it just helps you prevent unnecessary database calls. And it's the reason that that one is recommended over using count, which is going to always issue a call. And then also to avoid length where you can because it's going to load the whole collection into memory, and we want to avoid that. So it was a nice refresher. I'll be sure to include a link in the show notes. But yeah, I find that I myself often forget about the difference in count and size. And so if I'm just in the console and I just want to know something, that I still reach for count. It is still a default for mine. But then, if I'm writing production code, then I will be more considered as to which one I'm using. CHRIS: I feel like this is one of those that I've struggled to lock into my head, but as you're describing it right now, I think I've got, again, another mnemonic device that we can lock on to. So I know that SQL uses the keyword count, so count that's SQL definitely. Length I know that because I use that on other stuff. And so it's size that is different and therefore special. That all seems good. Cool, locking that in my brain along with Fn-Delete. I have two things that are now firmly locked in. So you were just mentioning being in the console and working with this. And one of the things that I've noticed a lot with folks that are newer to ActiveRecord and the idea of relations and the fact that they're lazy, is that that concept is very hard to grasp when working in a console because at the console, they don't seem lazy. The minute you type out user.where some clause, and the minute you type that and hit enter in the console, Ruby is going to do its normal thing, which is like, okay, cool, I want to...I forget what it is that IRB or any of the REPLs are going to do, but it's either inspect or to_s or something like that. But it's looking for a representation that it can display in the console. And ActiveRecord relations will typically say like, "Oh, cool, you need the records now because you want to show it like an array because that's what inspect is doing under the hood." So at the console, it looks like ActiveRecord is eager and will evaluate the query the minute you type it, but that's not true. And this is a critical thing that if you can think about it in that way and the fact that ActiveRecord relations are lazy and then take advantage of it, you can chain queries, you can build them up, you can break that apart. You can compose them together. There's really magical stuff that falls out of that. But it's interesting because sort of like a Heisenberg where the minute you go to look at it in the REPL, it's like, oh, it is not lazy; it is eager. It evaluates it the minute I type the query. But that's not true; that's actually the REPL tricking you. I will often just throw a semicolon at the end of it because I'm like, I don't want to see all that noise. Just give me the relation. I want the relation, not the results of executing that query. So if you tack a semicolon at the end of the line, that tells Ruby not to print the thing, and then you're good to go from there. STEPH: That's a great pro-tip. Yeah, I've forgotten about the semicolon. And I haven't been using that in my workflow as much. So I'm so glad you mentioned that. Yeah, I'm sure that's part of the thing that's added to my confusion around this, too, or something that has just taken me a while to lock it in as to which approach I want to use for when I'm querying data or for when I need to get a particular count, or length, or size. And by using all three, I'm just confusing myself more. So I should really just stick to using size. There's also a fabulous article by Nate Berkopec that's titled Three ActiveRecord Mistakes That Slow Down Rails Apps. And he does a fabulous job of also talking about the differences of when to use size and then some of the benefits of when you might use count. The short version is that you can use count if you truly don't care about using any of those records. Like, you're not going to do anything with them. You don't need to load them, like; you truly just want to get a count. Then sure, because then you're issuing a database query, but then you're not going to then, in a view, very soon issue another database query to collect those records again. So he has some really great examples, and I'll be sure to include a link to his article as well. Speaking of Ruby tidbits and kind of how this particular article about count, length, and size came across my view earlier today, Ruby Weekly is a wonderful newsletter. And I feel like I don't know if I've given them a shout-out. They do a wonderful job. So if you haven't yet checked out Ruby Weekly, I highly recommend it. There are just always really great, interesting articles either about stuff that's a little bit more like cutting edge or things that are being released with newer versions, or they might be just really helpful tips around something that someone learned, like the difference between count, length, and size, and I really enjoy it. So I'll also be sure to include a link in the show notes for anyone that wants to check that out. They also do something that I really appreciate where when you go to their website, you have the option to subscribe, but I am terrible about subscribing to stuff. So you can still click and check out the latest issue, which I really appreciate because then, that way, I don't feel obligated to subscribe, but I can still see the content. CHRIS: Oh yeah. Ruby Weekly is fantastic. In fact, I think Peter Cooper is the person behind it, or Cooperpress as the company goes. And there is a whole slew of newsletters that they produce. So there's JavaScript Weekly, there's Ruby Weekly, there's Node Weekly, Golang Weekly, React Status, Postgres Weekly. There's a whole bunch of them. They're all equally fantastic, the same level of curation and intentional content and all those wonderful things. So I'm a big fan. I'm subscribed to a handful of them. And just because I can't go an episode without mentioning inbox zero, if you are the sort of person that likes to defend the pristine nature of your email inbox, I highly recommend Feedbin and their ability to set up a special email address that you can use to then turn it into an RSS feed because that's magical. Actually, these ones might already have an RSS feed under the hood. But yeah, RSS is still alive. It's still out there. I love it. It's great. And that ends my thoughts on that matter. STEPH: I have what I feel is a developer confession. I don't think I really appreciate RSS feeds. I know they're out there in the ether, and people love them. And I just have no emotion, no opinion attached to them. So one day, I think I need to enjoy the enrichment that is RSS feeds, or maybe I'll hate it. Who knows? I'm reserving judgment. Either way, I don't think I will. [laughs] But I don't want to box future Stephanie in. CHRIS: Gotta maintain that freedom. STEPH: On that note, shall we wrap up? CHRIS: Let's wrap up. The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review on iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey. STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeee!!!!!! ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Thomm Jutz is a German-born American singer, songwriter, producer and guitarist based in Nashville, Tennessee.He has worked with folk singer Nanci Griffith (as a member of her Blue Moon Orchestra), Eric Brace & Peter Cooper, Mary Gauthier, Mac Wiseman, Bobby Bare, Connie Smith, Marty Stuart, David Olney, Otis Gibbs, Kim Richey, Bill Anderson, Amy Speace,[1] Milan Miller and Marc Marshall.[2]His songs have been recorded by Nanci Griffith, John Prine, Kim Richey, Junior Sisk, Kenny and Amanda Smith, Balsam Range, Buddy Melton, Milan Miller and Terry Baucom.[3]Jutz co-wrote the top two singles of 2016 listed on the Bluegrass Today Airplay chart. Jutz signed with Mountain Home Music Company in 2019. New albums "To Live in Two Worlds – Vol 1 & 2" were released in 2020. Singles "Mill Town Blues", "I Long to Hear Them Testify", "Hartford's Bend" and "Jimmie Rodgers Rode a Train" were released in 2019. He also signed as a writer with Asheville Music Publishing in 2018.[4] "To Live In Two Worlds, Vol 1" was nominated for a 2021 Grammy Award in the Bluegrass category.[5]Awards:Grammy Nomination for Best Bluegrass Album 2020, IBMA Songwriter of the Year 2021, Recipient of two SESAC Awards, Nominated for IBMA Songwriter of the Year in 2017, 2018, 2019, Nominated for IBMA Album of the Year in 2017Teaching:Lecturer in the Songwriting Department at Belmont University in NashvilleFor more on Thomm's work: https://thommjutz.com/homeFollow him on social: @THOMMJUTZ

A controversial worldview with a Christian perspective

12 Tháng 2 Là Ngày Gì? Hôm Nay Là Ngày Sinh Của Charles Darwin SỰ KIỆN 1502 – Vasco da Gama khởi hành từ Lisbon, Bồ Đào Nha, trong chuyến đi thứ hai của ông tới Ấn Độ. 2019 – Cộng hòa Macedonia đổi tên thành Cộng hòa Bắc Macedonia 1915 - Tại Washington, DC, lễ đặt viên đá đầu tiên của Đài tưởng niệm Lincoln được diễn ra 1994 - Bốn tên trộm đột nhập Phòng trưng bày Quốc gia Na Uy và đánh cắp bức tranh mang tính biểu tượng The Scream của Edvard Munch . Ngày lễ và kỷ niệm Ngày bàn tay đỏ ( Liên hợp quốc ) hay còn gọi là Ngày Quốc tế chống sử dụng Trẻ em nhập ngũ Sinh 1948 – Vũ Đức Sao Biển, nhạc sĩ Việt Nam. 1809 – Charles Darwin, nhà sinh học Anh (m. 1882). 1791 - Peter Cooper , doanh nhân và nhà từ thiện người Mỹ, thành lập Cooper Union (mất năm 1883) 1877 - Louis Renault, kỹ sư và doanh nhân người Pháp, đồng sáng lập Renault (mất năm 1944) 1809 - Abraham Lincoln, luật sư và chính khách người Mỹ, Tổng thống thứ 16 của Hoa Kỳ (mất năm 1865) Mất 2019 – Gordon Banks, huyền thoại bóng đá người Anh Chương trình "Hôm nay ngày gì" hiện đã có mặt trên Youtube, Facebook và Spotify: Facebook: https://www.facebook.com/aweektv - Youtube: https://www.youtube.com/c/AWeekTV - Spotify: https://open.spotify.com/show/6rC4CgZNV6tJpX2RIcbK0J - Apple Podcast: https://podcasts.apple.com/.../h%C3%B4m-nay.../id1586073418 #aweektv #12thang2 #AbrahamLincoln #CharlesDarwin #Renault Các video đều thuộc quyền sở hữu của Adwell jsc (adwell.vn), mọi hành động sử dụng lại nội dung của chúng tôi đều không được phép. --- Send in a voice message: https://anchor.fm/aweek-tv/message

I conclude the mini season of interviews with a brief summary of the five interviews I conducted. A few weeks ago, my cohost had a cycling that student that broke his jaw. As a result he had to take a break from the podcast while he was recovering. In the meantime, I invited a few people to come onto the podcast and talk about their businesses, their work and themselves.The episodes:#198: Simon Bennett of SnapShooter#199: Jane Portman of UI Breakfast#200: Positioning for bootstrappers with April Dunford#201: Peter Cooper of Cooperpress#202: Bridget Harris, co-founder of YouCanBook.Me

I chat with Peter Cooper, who runs several email newsletters, including JavaScript Weekly, Ruby Weekly, React Status, and Postgres Weekly. These all live under the collective banner of Cooperpress.Links:CooperpressPeter on Twitter 

Peter Cooper Royal Agricultural Society of WA CEO See omnystudio.com/listener for privacy information.

In this episode, Peter Cooper and I discuss the publishing of Ruby Weekly and the benefits of podcasting and blogging. We also talk about cars and the Smashing Pumpkins.Ruby WeeklyPeter Cooper on Twitter

This is the sweeps week episode, the epic crossover episode, the mega episode! We have a very special episode as Chris, and Steph teamed up with the hosts of three other podcasts to bring you one giant, mega Ruby episode! In this episode, you'll hear from the hosts of Remote Ruby, Rails with Jason, and Brittany Martin, the host of the Ruby on Rails podcast. They cover the origins of their shows, their experiences as hosts, and why podcasting is so important in keeping the Ruby community thriving. Remote Ruby (https://remoteruby.transistor.fm/) Rails with Jason (https://www.codewithjason.com/rails-with-jason-podcast/) Ruby on Rails podcast (https://5by5.tv/rubyonrails) *Transcript: * STEPH: Hello and welcome to another episode of the Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. This week we have a very special episode as Chris, and I teamed up with the hosts of three other podcasts to bring you one giant, mega Ruby episode! In this episode, you'll hear from the hosts of Remote Ruby, Rails with Jason, and Brittany Martin, the host of the Ruby on Rails podcast. This episode was so much fun to record, and we have Brittany Martin to thank as she organized and moderated this special event. So without further ado, here is the mega Ruby episode. BRITTANY: Welcome, everyone. We have a whopping seven podcast hosts recording today. So, listeners, you are in for a treat. This is the sweeps week episode, the epic crossover episode, the mega episode. We're going to need our editor to insert some epic sound effects right here. Announcer: The mega episode. BRITTANY: So let's go ahead and introduce the crew today. I am Brittany Martin from the Ruby on Rails Podcast. CHRIS OLIVER: I'm Chris Oliver from Remote Ruby. JASON CHARNES: I am Jason Charnes, also from Remote Ruby. ANDREW: I am Andrew Mason, also from Remote Ruby. STEPH: And I'm Stephanie Viccari from The Bike Shed. CHRIS TOOMEY: I'm Chris Toomey from The Bike Shed. JASON SWETT: And I'm Jason Swett from Rails with Jason BRITTANY: Today, we're going to cover the origins of our shows, our experiences as hosts, and why podcasting is so important in keeping the Ruby community thriving. Now I know personally, I really enjoy the origin story behind Remote Ruby. So, Chris Oliver, could you kick us off with that? CHRIS OLIVER: Yeah, we can go back maybe to the first time that Jason and I met, which was Jason emailed me out of the blue and was like, "Hey, are you going to be at RailsConf?" And I wasn't planning on it, but it was over in Kansas City, like four hours away from me. I was like, "No, I'm not going, but I'll meet you." So we went and drove over there and met and have been friends ever since. And Jason had the idea of doing an online meetup. And I'll let him explain where that started and turned into the Remote Ruby Podcast. JASON CHARNES: I thought it would be a good idea. There weren't any online meetups. This was pre even the idea of shutting down the world for a pandemic. And maybe I was just too soon because I got Chris to speak at the first one, and we had 40, 50 people. I spoke at the next one, and there were 20. And by the third one, there were five of us. So it wasn't really a super sustainable thing for me to do. So Chris and I got together and said, "What if we tried podcasting?" Chris, you hadn't really done your own podcast at that point, had you? CHRIS OLIVER: No, I don't think so. And you and I were just having calls every week or whatever just to hang out and chat. And we were like, why don't we just record that and publish that as a podcast? And here we are. JASON CHARNES: Yeah. So we've been doing that. I think we started in 2018, so yeah, three years in June, and somehow people still keep listening to us talk but probably because we brought along our friend, Andrew. ANDREW: Wow. Okay. No, that's not true. But yes, I was a guest on Remote Ruby before I joined as a host. And not to get into the details, but I was on another podcast, and something went down, and I no longer was on that podcast anymore. And Chris and Jason were like, "Do you want to come hang out with us?" And I was like, [chuckles] "Absolutely." So I started doing that, and at the same time, I also started The Ruby Blend with Nate Hopkins and Ron Cooke. And so we were doing that for a while until that had to tragically shut down. But I'm still here with Jason and Chris. I guess I should also mention that Jason Swett gave me my start in podcasting a month or two after I started full-time as a Rails developer on a now archived show called The Ruby Testing Podcast. BRITTANY: Which is the perfect segue because Jason Swett was also my first opportunity to guest on a podcast. So I was already hosting, but I hadn't guested, which is kind of the opposite order. So, Jason, do you want to tell the origin of where Rails with Jason came from? JASON SWETT: Sure. I'd been involved with podcasting since around 2016. I somehow ended up on the Ruby Rogues Podcast and was on there for maybe a year or so. And then, somehow, I got the idea that I could start my own podcast. And as an experiment, I started a podcast that I called The Ruby Testing Podcast, which I figured was sufficiently narrow that I could get some traction. And to my surprise, guests actually said yes to coming on the show. And also, to my surprise, people actually listened to the podcast. That gave me some confidence. So maybe a year later, I broadened, and I changed from The Ruby Testing Podcast to just Rails with Jason. And I have been doing that for something like two years. BRITTANY: That's fantastic. I want to move to probably our most experienced podcast veteran, and that would be Chris Toomey. When I was learning how to code, I was listening to Giant Robots and then was excited for the transition that The Bike Shed took. Chris, I would love to hear the story of what it was like taking over a really popular podcast and really maintaining the drive behind it. CHRIS TOOMEY: So, as you mentioned, I had done a little bit of podcasting. It was about a six-month run where I was a co-host on Giant Robots, which was the original podcast of thoughtbot. And that was more in the business and sort of how do we build a software company? So at that point, I was running Upcase, which was the subscription learning platform that thoughtbot had. So I was talking about the inner details of the business, and the marketing tests, and A/B tests and things like that that I was doing. And every week, I was sharing my MRR rather transparently in that thoughtbot way that we do. I did that for, like I said, about six months and then took a while off. And in the background, thoughtbot had started up a new podcast called The Bike Shed, and that started October 31st of 2014. So The Bike Shed has been going for a long time now, and that was hosted by Derek Pryor and Sage Griffin. And they ran that for a number of years. I think it was about four years that the two of them worked collectively on that. But at some point, they both moved on from thoughtbot, and there was an opportunity for new hosts to step in. So I took over in August of 2018. So I've been doing this now for about three years. And so, for that first year, I took the opportunity to do a tour around thoughtbot and talk with many different individuals from the company and a handful of people external to thoughtbot. But I knew that there were so many great voices and ideas and points of view within thoughtbot that I really wanted to spend some time getting to know more of them personally and then sharing that as much as I could with the existing audience that The Bike Shed had. But secretly, all along, I was looking for a person to hang out with all the more so, and Steph was the person that was a perfect choice for that. And so, for the past two years, Steph and I have been chatting. And I will send it over to Steph to share a little bit of her point of view on that transition. But from my point of view, it's been fantastic. STEPH: I still remember exactly when we had the conversation. You were running The Bike Shed and doing an incredible job of just having weekly guests. And then you'd reached out to me and said, "Hey, would you be interested in doing an episode?" And I thought, "No, absolutely not. I can't podcast. I can't begin to do this." So you continued to convince me. And finally, you said something that resonated where you were like, "Well, we can just show up and record, and we don't have to publish. We can just see how it goes." I was like, that's a perfect safety net. I'm into that. So I showed up, and I think the first episode that you and I recorded ended up being titled What I Believe About Software. And it was a lot of fun. I realized I have a lot of things to say. And after that, I think it was another month or so. You continued interviewing more guests, but then you reached out to me and asked me if I wanted to be a co-host. And at that point, I was super jazzed about it, and it's been wonderful. It's been a roller coaster. I have learned a ton. BRITTANY: I'm kind of seeing a pattern here where over the last three years, it seems like Remote Ruby came into place, Bike Shed transitioned. That's when I took over as host of the 5by5 Ruby on Rails Podcast. We're going to call it the golden era of the Ruby Podcasts. But for me, I probably have the longest-running podcast. It was started back in 2009 on the 5by5 Network, but it's gone through many different hosts. And so, I took over roughly about three and a half years ago as the main host from Kyle Daigle. And then, just a couple of weeks ago, as I announced on my podcast, we took the podcast independent. We are now just The Ruby on Rails Podcast. And I'm starting to change the model where I'm bringing in more co-hosts. So that way, I can get those regular updates that I really appreciate on all these podcasts we have featured on the show today. I am curious. I want to talk about how we put together the episodes and plan out how everything's going to go down. I know for me, I'm currently a mix of interviews and co-host episodes. So I'd love to hear from Andrew. How do you plan out what Remote Ruby is going to be week to week? ANDREW: This is an easy question because we don't at all. We don't plan. We do have some guests that come on, and sometimes, they may get their Zoom link the day of; who's to say? But we really don't have a plan. We don't talk about what we're going to talk about beforehand. We all just kind of show up, and I think we have that kind of relationship and flow where it always just works. JASON CHARNES: And I think part of that came from actually how Chris and I started the show because we were trying to make it as low stress as possible because we knew if we put a lot of pressure on it, we would stop doing it. Our first episodes were YouTube live links that we just shared out. And then in our next episodes, we were like, oh, we should start using some software to do this. And then eventually, we got an editor, but that same core of let's just keep it fun for better or for worse, I think, also affects our planning. BRITTANY: I've been lucky in the sense that I have guests sit on all three of the episodes. And I do want to give a compliment to The Bike Shed because it is very well run and very well planned. So I want to kick it over to Steph as to how putting together a Bike Shed episode looks. STEPH: Oh, thank you. That's wonderful to hear, by the way. That's wonderful feedback. So we predominantly use Trello to organize our thoughts. So we will have...and as we're capturing community questions that are coming in, so we will capture those on the board. And then, we will have a ticket that represents a particular episode. Usually, on the day of, we'll share some thoughts about, hey, these are the broad topics I'm interested in. And there's usually some hot takes in there, which is fun because the other person doesn't know exactly what's coming, and we can have real honest conversations on the mic. And then, every so often, we'll grab a beer, and we'll go through that list. And we'll chat through what sparks joy. What do we want to talk about? What would we like to respond to? And that's pretty much how we organize everything that we discuss. Chris, is there anything I've left out that you want to add? CHRIS TOOMEY: I think that mostly covers it. We do occasionally have interviews just as a way to keep some variety and different things going on, but primarily it's the sort of what's new in your world? And I find that those episodes are the ones that I think are the most fun to record for Steph and I when it really feels like a sincere conversation. I've recently taken to a segment I call good idea, terrible idea where I'm like, "I'm actually considering this, Steph. What do you think?" And live on-air, I'm getting Steph's feedback, and generally, we're very aligned. But every once in a while, she's like, "That's a terrible idea. Don't do that." And I love those, and I love being able to share that because I think it's really easy to talk about, you know, here's a list of things that are true about software, but really, everything depends. And it's all the nuance. And so, being able to share some of our more pointed experiences and then share the conversation that we have over those is hopefully very valuable to the audience but definitely the thing that I enjoy the most. BRITTANY: So kicking it over to Jason Swett, I really enjoy the interviews that you do. I'm curious, how do you select guests? JASON SWETT: Well, thanks. Selecting guests is tough. I had Peter Cooper on the other day, and I was telling him that I feel like every guest that I get on the show is the last guest I'm ever going to be able to get on the show. But somehow, I keep finding more and more guests. Early on, it was relatively easy because I would just find book authors, or if somebody else does podcasting, then it's fairly obvious okay, you're the kind of person who does podcasts, so I'll invite you. But it's a little bit tough because I don't want to invite people who aren't into podcasting and would be really thrown, although sometimes that happens. But let's see, sometimes I send an email out to my email list, and I'm like, "Hey, I'm looking for guests for my show." Sometimes I just tweet that I'm looking for guests. And sometimes I get some really interesting guests from surprising places. But at least in the start, it was looking for those authors and podcasters and the people who are known in the Ruby community. BRITTANY: I know for me, I strive to have at least 50% of my interviews be with people who've never been on a podcast before. And so that usually involves the top of the episode they're dry heaving into a paper bag. And I'm explaining to them, don't worry, about halfway through the episode, you're not going to remember that you're recording anymore. It'll be fine. And you know what? It's always fine. And so, I do love hearing from a wide variety from the Ruby community just because it really proves just how big it is. So I'm curious, could you host the podcast that you are currently hosting now if you weren't actively working in Ruby? ANDREW: I could because Chris is the one that has all the clout. I could sit back and make dumb jokes and memes during it. And as long as Chris is there, I think we'll be good. JASON SWETT: Yeah, I think I could because a good majority of what we talk about on Rails with Jason actually has nothing to do with Rails, so that would probably actually work out. STEPH: I think yes is the answer. While a lot of our conversations do focus around Ruby and Rails, we often use a lot of other languages and tools, and those are a lot of fun to talk about. So I think I would just talk about whatever new tool or language that I'm using. So I think yes, it would just take a slightly different form but would still be at its core the same where we're still talking about our daily experiments and adventures in web development. BRITTANY: I agree with you, Steph. I will say that it seems like Chris Oliver and Chris Toomey have an endless well of things to talk about just based on what they do day-to-day. CHRIS TOOMEY: I try and go on adventures and then share as much as I can. But to resonate with what Steph was saying there, we try to make the show more generally about software, and it happens to be that it's grounded in Ruby on Rails because the vast majority of the work that we do is in that. And I just recently started a new project. I was given the choice of I could pick any technology I want, and it remains the technology that makes sense to me to be the foundation of an application that I want to maintain for years and years and years. So, on the one hand, I think I could definitely talk about software more generally. I think I'm doing that most of the time. But at the other end of the spectrum, but it's always going to be based on Ruby because I haven't found a thing elsewhere in the world that is better than that. CHRIS OLIVER: I completely agree with that. I probably have a little bit of a unique thing doing a screencast every week. A lot of those are based on I'm building some project, and I need to build some random feature like Stripe Checkout. And that's a good one to do a screencast on and implement in the project. And then, we can also talk about the decisions along the way on the podcast, which is kind of nice. BRITTANY: Yeah, it feels like every week, Chris Oliver is like, yeah, I've created a new open-source library, and I'm fabulous. [laughs] Let me listen to this. CHRIS OLIVER: Too many of them. I'm currently rewriting a lot of the Pay gem. And it's just one of those things where you make a bunch of decisions. And then, if you make an open-source project, people use it in all these different ways that you didn't intend yourself, and so you want to support that. But then you need to rearchitect things in it. It is a lot of learning as you go, which is always a lot of fun. So those I think are really good topics to talk about when you're building something like that. I'm always amazed by how does the Rails core team make these decisions on what should be in the framework and what shouldn't? And what do they want to maintain, and how do they keep it flexible but yet have some sort of rule with how they allow things to be implemented and whatever? It is a very hard job to have. So I get my little taste of that with some open source but not on their level. BRITTANY: I always thought that you had a good contrast to Jason Charnes because Jason works at Podia. And while you do get to work on a lot of really cool technologies, I feel like the stakes are much higher. So you can't just rip out StimulusReflex and put in something else just because it sounds cool that week. And I love how you talk through the pluses and minuses to making a big change within the Podia codebase. JASON CHARNES: Yeah. I haven't really thought about that contrast before, but it's helpful for me even just to talk it out with two other people once a week, and luckily, pretty cool about me just coming on and talking about hey, these are the steps we took to get here. Yeah, it's a cool dynamic. BRITTANY: Steph, have you ever had a client from thoughtbot say, "Hey, were you talking about me?" whenever you're talking about your current client? STEPH: That is one of my fears at times that it will happen [chuckles] although we stay very positive on the show. That's something that's very important to us. There's enough negativity in the world. So we really want to focus on our positive experiences through the week. But there have been times where I'm speaking about some of the challenges or things that we are running into that yes, the engineering team is listening to the podcast, and they're like, "Oh, I heard you talk about this feature that we're working on or this particular challenge." And that's really cool because they get that behind-the-scenes peek to see how Chris and I are chatting about that. But yet they know enough, and they know which project that I'm on that they recognize exactly the technology and the feature that I'm trying to describe. So that has certainly happened, and it can be a lot of fun when it does. BRITTANY: Andrew, how have things changed for you now that you're not working at CodeFund, which was very much like an open-source thing? People could see what you were actively working on. And now you're working for a company where it's closed source. And so, you might not be able to reveal as much as what you're working on at any given point. ANDREW: It's different, but I don't think it's been an issue per se. I'm not like, oh crap, I let that slip, and I didn't mean to. That's not really an issue. I really cherish the time I had at CodeFund. When I think back on my experiences, that was my favorite time just because I was able to do that thing that a lot of people really want to do. I was working as an open-source developer. We were spiking StimulusReflex; that's when we were building up StimulusReflex and trying to build up the community. I joined Ruby. We started the Ruby Blend, and things were going good before a dramatic turn. But in terms of the closed and open source, it hasn't been that big of a shift just because instead of talking about what I'm doing at work, like, I still talk about it, but I speak about it in more general terms. But I also then kind of freed up to talk a lot more about the dumb crap I do on the nights and weekends. BRITTANY: So the majority of our podcasts either have the word Ruby or Rails in it, but I think we've all agreed that a lot of the topics that we're talking about are not specific to that community. But in a lot of ways, I feel that having podcasts in our community is how we're going to keep our community thriving. So I'm curious if anyone has any thoughts around...is there a way to market our podcasts so that other developers will listen to it? I get really excited when I get listener feedback saying, "Hey, I used to do Rails maybe ten years ago, but I've been listening to your podcast, and I really enjoy such and such episode." How can we make our podcasts accessible to the general software community as opposed to just Ruby? CHRIS TOOMEY: One thing that stands out to me about Ruby and Rails is because it's full-stack, because of its foundations, it tends to be holistically about web development. And so, whereas I look at React projects or other JavaScript or different things that are going on, I see a more narrow focus in those frameworks. And with Ruby and Rails, what I love about it is that it's really about building software. It's about building products that are valuable, that deliver value to end-users. And so that being the core of it, that's the story that constantly brings me back to Ruby and Rails. And it's the story that I want to keep telling as much as possible. And it's the thing that keeps me engaged with this community. And so, I think podcasts are a great way to continue to literally tell those sorts of stories and really celebrate that aspect of Ruby and Rails and why it remains such a productive way to build software. CHRIS OLIVER: I think related to that, one of the things that we should talk about more is the draw of Rails was look at what you can do with one person or two people. And I feel like we went down the JavaScript route, and now you need two teams of people, and you end up building bigger stuff. And Hotwire has kind of been like, hey, here's a reminder of what you can do with a very small team. And I think that resonates a lot with a lot of people building startups and trying to build side projects and everything. And that's one that is Rails-related. But there's a ton of people building Hotwire stuff in Laravel too. And they're all very similar. So I think at a certain point, yeah, we're talking about maybe Rails specifically, but you can apply all those things to different frameworks and just different tools. STEPH: I'd like to add on and extend that because I wholeheartedly agree with what both Chris Toomey and Chris Oliver just said. And in addition, a lot of the conversations that we have on The Bike Shed are focused on Ruby and Rails, but then we will extract that particular concept to the point that it really doesn't matter which language that you're using or which framework that you're using. We're talking more about the high level. What's your process? What are you thinking as you're going through and implementing this? And based on more of our recent conversations, you'd think we're more of a Postgres podcast, how much we hype up Postgres, and the things that we can do at the database layer. So I think there are a lot of ways that we can start with a foundation of this is how we're doing it with Ruby and Rails, but then talk about it at a higher level where then it's really applicable for everybody. JASON CHARNES: If talking about one technology defined your podcast, we might as well be a Laravel podcast because we talk about that framework more than we do Rails sometimes. [chuckles] BRITTANY: So that begs the question: is there room for more Ruby and Rails podcasts outside of who's currently on this call? JASON SWETT: I think so. And I mentioned that Peter Cooper was on our podcast a little bit ago. That's something he and I actually talked about in that episode. And I shared the anecdote about how in the new America's founding, Ben Franklin's brother or something like that wanted to start a newspaper. And somebody told him what a dumb idea that was because America already had a newspaper. And people might say, oh, there are already however many Rails podcasts. There are a small handful. But I think there could be ten more Rails podcasts or even more than that potentially because I think people have an appetite for help, and camaraderie, and stuff like that. And I don't think we've nearly bottomed out in terms of satisfying people's appetite for that stuff. JASON CHARNES: Yeah, I agree with that because a lot of times, when I listen to podcasts, the more you get to know someone, that connection becomes what it's about for me. So, yeah, there's plenty of room. I mean, brand it as Ruby and tell me about your life as a developer I'll listen. CHRIS TOOMEY: I'll also throw it out there that the way you framed the question is like, is there room for it? But one of the wonderful things about podcasting as a medium is it is distributed. It's not centralized. You can start up a podcast any day. And I will say, as someone who inherited a popular podcast or a sufficiently popular podcast and just got to run with that, it has been such a wonderful way to get my voice out there and provide opportunities that I want that for everyone. I want everyone to have this ability to speak about the way they think about software and then find like-minded people and be able to build even many communities within the larger community of Ruby on Rails. So beyond the question of, Is there room?” which I definitely think there is, I so wholeheartedly support anyone pursuing this for their own reason. ANDREW: Yeah, I think to bring it all the way back, one thing that Chris, Jason, and I care a lot about is Ruby as a community. The community aspects of Ruby are very important to us. And we're actively trying to build that up and bring in new people and bringing people onto their first podcast. We say it all the time, like, hey, if you want to come on the show, let us know. We've had a few people even, you know, recognition in jobs from that. So to us, that is the payoff of doing the show. Maybe our show is the first time someone learns about Rails. And that to me is the possibility in the future. It's like, how can we market our shows that markets Ruby as well so that this meme of Ruby being dead finally goes away because it's not. I think it's growing. And I think the more and more we push as people who are public figures in this space that we want to bring more people on, that this is a space for everyone, I think that's just kind of the ethos that all of us have, and I think that's great. BRITTANY: So I'm curious, on a lighter note, has anyone had the funny experience of realizing that you're not just podcasting into the ether and that what you're saying and what you're doing matters? For me, I have definitely been at conferences where people will run up and hug me just because they heard my voice, and they are like, "I didn't know what you looked like, but I have your voice memorized," and it just blew my mind. And I was like, "Thank you so much for being such a loyal listener." And it just proves that people are out there listening. ANDREW: I tend to talk very openly about mental health. And I very often fail in public and talk about it. And I've had a lot of people message me and email me over the past three or four years and be like, "Hey, thank you for talking about this thing that's not actually about Ruby. It's not actually about coding, but it's just about being a developer." And those are the emails that make me feel the best. Like, someone who's out there like, "Yeah, I also feel like this. Thank you for speaking about it." JASON SWETT: I had a surreal experience. I went to India in 2019 through RubyConf India. And this guy wanted to take a selfie with me because apparently, he considered me famous. So that was cool and pretty surprising because I definitely didn't consider myself famous. STEPH: My favorite has been when we receive listener questions because it lets us know that people are listening and engaged in the conversation, and I essentially feel like they're part of the conversation. They will write in to us and share anecdotes, or they'll share answers to some of the questions that Chris and I will pose on the show. But every now and then, we will also get an email from someone that says, "Hey, just thanks for doing the show. I listen, and it's great," and that's all they share. And that, to me, is just the most wonderful thing that I could receive. BRITTANY: Some of my favorite episodes from all of your shows is when we get an inside peek into what people are doing, like Andrew moving. Jason Charnes, you putting together a conference was actually some of my favorite episodes of yours, which was really early on, which proves that I'm a Remote Ruby OG. But I loved hearing the inside track as to what organizing a conference is because I think we need to get more content out there about how difficult but how rewarding it is. JASON CHARNES: Yeah, I hadn't really thought about...that was around those times we hadn't done... It feels like it's been ages since we did Southeast Ruby, but Chris and I actually podcasted from the last Southeast Ruby we did. We just met in a room and recorded. But when I started that conference, I didn't have a lot to go on. So I'm more than glad to share because the reason I started is there were no Ruby conferences around me, plus I'm an open book. So for better or for worse, maybe that's good podcast material. JASON SWETT: Side note, it's one of the most enjoyable conferences I've ever been to. JASON CHARNES: Thank you. BRITTANY: I completely agree. I miss the regional conferences. JASON CHARNES: We lucked out because we were already planning on skipping 2020 because we were tired, and then COVID hit. I just sat on the couch one night and looked at Shannon (she helps me put on the conference), and I was like, "Wow, that would have been terrible. That would have come out of our own bank account, all that loss if we would have already booked somewhere." So phew, when it chills out, we'll try it again. BRITTANY: So let's talk about legacies. I know that some of us have taken over from popular podcasts. Some of us have grown podcasts from the very beginning. So I'm curious, do you ever put any thought into the legacy of your podcast, whether or not you're going to stay with it to the end? Would you eventually pass it off? Do you think about whether or not it's your responsibility to the community to make sure that it keeps going? JASON SWETT: I, for one, plan to have my consciousness uploaded to a supercomputer upon my death so that the Rails with Jason Podcast can continue on indefinitely. JASON CHARNES: Did you recently watch Upload the TV show? JASON SWETT: No, I've never heard of it. JASON CHARNES: Oh, man. That's a whole nother conversation. BRITTANY: Consider that homework, Jason. JASON CHARNES: It's an interesting question because we started ours out of nothing. I wonder, is one of us going to get tired and just quit? I'd like to think that if one of us did, it would keep going because there are plenty of cool people who could hang out and talk Ruby on it. But it's interesting, something that's casually crossed my mind, but I think we're good. I think we're still doing it unless Chris and Andrew have a surprise for me today. ANDREW: Surprise! [chuckles] I've thought about it a few times, specifically because I'm the youngest member of Remote Ruby. What if Jason and Chris just left, and they were like, "Oh, it's all yours now." Could I keep running it by myself? I think honestly, the answer is I would probably still do it just to have an excuse to talk to someone. I enjoy it. It's almost like a hobby at this point. I don't feel any obligation to create it. To me, it's really like an excuse to hang out with two friends, and other good stuff comes from that. But at the end of the day, I cherish that time just us hanging out a lot. CHRIS OLIVER: Yeah. I think that's why we sometimes joke about it being a weekly therapy session where we are just hanging out and chatting about stuff. It's nice to be able to talk about programming things at a high level with people you don't work with that have totally different perspectives and stuff. So yeah, if Jason and Andrew dropped off, I would still try to have conversations with random people I know and keep it going just because it's enjoyable. I would hope that we would be able to keep it going and have other people on there. BRITTANY: I'd love to hear from someone from The Bike Shed. STEPH: I have thought about it. I've thought about it partially from the perspective that Chris Toomey brought up earlier in regards to being on a podcast is an incredible platform. You get to share your opinions, and people listen to you. And they know you, and it's really wonderful marketing. So I have thought about it from the perspective of I want other people to have access to this really wonderful podcast that we put on each week. So part of me is very aware of that and thinking about how more people can have similar exposures. So a sort of a similar event occurred when Chris was moving on from thoughtbot and pursuing other interests. And at that moment, I just thought, oh my goodness, Chris brought me on as co-host, and now I'm here alone, and I don't know what I'm going to do. And I just panicked. I truly don't think I even considered other options. I was like, well, okay, it's over now. This was fun. And then it turned out where Chris was going to stay with the show. So things have just gone on swimmingly, and it's been wonderful. But similar to what someone was saying earlier around when you start listening to a podcast, and you really develop that relationship and you go back to that podcast because you really enjoy hearing from those people and their adventures, it's very similar for me where The Bike Shed is very much the conversations and chats with Chris. So I think if we were to move on, it would be whenever Chris and I decided to move on and give the reins over to somebody else. I don't know if Chris fully agrees, so this will be interesting to find out. [chuckles] CHRIS TOOMEY: I agree with that. Honestly, I'm honored to have continued on in the podcast after having moved on from thoughtbot because, in a very real way, the show is thoughtbot's channel to talk about things. I was at thoughtbot for seven years. I think I live and breathe that truth. And to me, that's what maybe has made sense for me to continue on. But I really do feel a responsibility to keep the show in good shape so that someday someone else gets to inherit this thing because I was so happy to get handed it. It was such a wonderful thing. And it has been such a joy to do for these past three years. But at some point, I do presume that we will move on. And at that point, I do hope that other people pick up the mantle. And thankfully, thoughtbot as an organization, there is a group of individuals that I'm sure there will be someone wonderful that gets to step in, but I'm in no hurry to do that. And, Steph, I hope you're not either. So we'll continue the conversations for now, but I definitely do want to keep this thing alive if for no other reason than I got handed it. I don't feel like I could let it drop on the floor. That doesn't feel right. BRITTANY: Well, I think on that warm, fuzzy feeling, we should wrap up. So let's go through everybody and just tell the listeners where they can listen to your podcasts and follow you. I am Brittany Martin, @BrittJMartin on Twitter. And you can listen to the Ruby on Rails Podcast at therubyonrailspodcast.com. JASON CHARNES: So I'm Jason. We are Remote Ruby. I am @jmcharnes on Twitter. And I'll let the others tell you where you can find them. ANDREW: You can find me everywhere @andrewmcodes. And if you email me, there's a really good chance you're never going to see a response because my email is a disaster. Please don't email me, but you can contact me anywhere else. CHRIS OLIVER: I'm Chris Oliver, and you can find me on Twitter @excid3 or at Go Rails, and of course, gorails.com. And you can find the Remote Ruby podcast at remoteruby.com. CHRIS TOOMEY: I am @christoomey on Twitter. The Bike Shed is @bikeshed on Twitter. We are at bikeshed.fm for a URL. I'm pretty sure www works, but I'm going to go check that real quick after because I want to make sure that's true. And yeah, that's me. And I'll send it over to Steph for her part. STEPH: I am on Twitter @SViccari, and I post programming stuff, usually pictures of cute goats, cute dogs, that kind of content if you're into that. JASON SWETT: For me, if you want to find my podcast, it's Rails with Jason. And if you search for Rails with Jason anywhere, you should be able to find it. And then my website, if you're interested in my blog and all that stuff, is codewithjason.com. BRITTANY: Fantastic. Thank you, everyone, for being on this mega episode today. It was a lot of fun. We are going to be having a podcast panel at RubyConf; we're excited to announce and some of us will be present. So stay tuned for details around that. And if you enjoyed this mega episode and want to see more mega episodes, please let us know on Twitter. All: Bye. CHRIS: The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review on iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us @bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey. STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. All: Bye. Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Welcome to Semaphore Uncut, a podcast about developers building great products. In this episode, I talk with Peter Cooper, tech publisher, author, software engineer, and of the most successful newsletter curators. Press the play button and listen to us talking about content creation, the cycles in the tech business, and how developers learn.Key TakeawaysUsing a email as the core driver for a businessGetting older in the technology industryWhy developers should be involved in content creation alsoIs it fun to be the chair of a conference?

In this episode, David speaks with Peter Cooper of Cooper Investors. Peter founded Cooper Investors in 2001. As Chief Investment Officer, Peter created and implemented the firm's VoF investment philosophy which is applied across the international, domestic and Asian equities strategies. He is responsible for mentoring investment team members and the standardisation and integration of the process across the investment teams. Peter has over 30 years of investment management experience. In 1987 he joined the NSW State Superannuation Investment and Management Corporation as a specialist industry analyst and progressed to deputy portfolio manager of the $7bn portfolio. In 1993 Peter ran the Australian equities portfolios for BNP and then joined Merrill Lynch Investment Managers (formerly Mercury Asset Management) where he worked for 7 years, culminating in his position as Head of Australian Equities and Managing Director where he oversaw a team managing $7.5bn in Australian equities.

Peter Cooper is a billionaire and global investor who is perhaps best known for the transformation of Auckland's CBD through the redevelopment of Britomart. He was also pivotal in the creation of brewing giant Lion Nathan, and some people will be familiar with The Landing, a luxury retreat, winery and heritage project in the Bay of Islands - where Barack Obama stayed while visiting New Zealand. Cooper is currently based in California, but at heart he's a proud Kaitaia boy who turned his humble beginnings into an incredible portfolio of works, donations, and assets. This week Cooper received the supreme award at the Kea World Class New Zealand Awards, which recognises people whose achievements are driving the country's prosperity, development, and international reputation.

Peter Cooper is a billionaire and global investor who is perhaps best known for the transformation of Auckland's CBD through the redevelopment of Britomart. He was also pivotal in the creation of brewing giant Lion Nathan, and some people will be familiar with The Landing, a luxury retreat, winery and heritage project in the Bay of Islands - where Barack Obama stayed while visiting New Zealand. Cooper is currently based in California, but at heart he's a proud Kaitaia boy who turned his humble beginnings into an incredible portfolio of works, donations, and assets. This week Cooper received the supreme award at the Kea World Class New Zealand Awards, which recognises people whose achievements are driving the country's prosperity, development, and international reputation.

In this episode of the Dealership HCM podcast, Bart and Jason sit down with Peter Cooper, President/CEO of Lexus of Lehigh Valley. Peter gives us a 50,000 ft view of where the industry is headed and shares best practices to navigate through the issues of today. Don’t miss this episode!Notes:Learn more about the DrivingSales Master Certification here:https://bit.ly/3qhRL2OClick here for more info about DSES 2021:https://bit.ly/3vo60FX

Peter Cooper talks with Alan Riley about the first chapter of John's Gospel, starting at the very beginning. John's Gospel is a highpoint of theological writing with deep truths embedded within it. What or who is God's word and how does God's word affect us. Pete and Alan argue that God's word bring about both creation and new creation in a way that changes everything.

I chat with Peter Cooper an expert in rewildling, What is it? Do we need it and of course a bit of beaver! Nature Reserve of the week: Dungeness © www.jackperksphotography.com

Some doomsday preachers and conspiracy theorists have dubbed the Supermoon an incredibly sinister portent of doom. Astrologers and atheists take a different view of its significance. We look at all that from a Christian Worldview point of view: what does the Bible say? Is this a #prophecy? Is it #endtimes realated? This is an extract from The Virtual Vicar show on Flame Radion 1521 M2, www.flameradio.org featuring Peter Cooper and Beryl Polden.

Peter Cooper founded Cooperpress to deliver software engineering content to a massive audience.

In Episode 59 of The String we dive deep into the Austin/Nashville dynamic captured in the new Country Music Hall of Fame and Museum special exhibit Outlaws & Armadillos: Country's Roaring 70s. Our feature interview is with Michael Martin Murphey. Best known to many for his crossover hit “Wildfire” from the summer of ‘75, Murphey's had a wide ranging career. His songs have been recorded by Johnny Cash and Lyle Lovett among others. And he's earned abundant recognition for his decades as a champion and revivalist in the field of cowboy songs and western music. But before all that, Murphey was a key player in the Austin TX phenomenon, residing there as a full time musician from 1968 to 1974. He was a regular at the Armadillo World Headquarters, the iconic venue at the heart of the live scene, where a diverse audience heard a diverse array of roots music, from hard country to traditional blues. Murphey, along with Willie Nelson, Jerry Jeff Walker (about whom he wrote the era-defining song “Cosmic Cowboy”) and others forged a country-rock hybrid that became the foundation for the progressive folk music field we now call Americana. Also, a visit with exhibit co-curator Peter Cooper. 

Peter Cooper is the founder and Chief Investment Officer of Cooper Investors, one of Australia's leading boutique investment firms. His success is probably best conveyed by the incredible performance of the CI Brunswick fund, which he manages personally. This fund has outperformed the ASX200 Accumulation Index by a cumulative 537%, or 8.3% p.a. since inception in 2004. In this week's podcast, we discuss: •Two exciting ‘clusters' of investment opportunities that have him excited today, including his ‘big idea' for the next 30 years •The two different types of value (value creators and reversionary value) and why you need to think about them differently •Two ASX small caps floats that he's participated in over the last year, and why he likes the companies so much •A personal story of some of the philanthropic work that CI have undertaken •Which ASX stock he'd want to own if the market were to close for five years.

A thought on evangelism. Daily audio podcast - a Bible thought for each day - here https://www.youtube.com/?hl=en-GB&gl=GB Buy my book for Kindle and Kindle App http://ow.ly/iHgK307FMW8 Todays thought: what was it about Jesus that caused people to believe in him and follow him? Never having met him physically, we don't know if there was anything physical about him that inspired people. However his personality shines through the words of the Bible showing that he has an attractive personality. In the film “the Greatest Story Ever Told” you know when Jesus is about to appear because of the stirring music. Before he even speaks you can hear violins in the background. Scripture is silent on this subject, but I am personally convince that violins did not actually play overtime Jesus spoke in real life. Jesus did not need it to impress people, there was something about him that drew people to him. Jesus taught as one having authority (Matthew 7:29) when talking about the things of God. JB Phillips translated the gospels and he said that he was personally struck by Jesus' personality as he did so. A very effective method of evangelism, perhaps the most effective, is to introduce your friend to Jesus. In effect saying, “I follow Jesus, come and meet with him”. Not using those words, but rather simply inviting them to worship, to join you at you cell group, to be with you as you meet with Jesus. In meeting Jesus and in seeing how much you love him, how much you life is impacted by worship and Bible study your friend will be intrigued. There was once a young salesman who was disappointed about losing a big sale and he talked his sales manager he said, “I guess it just proves that you can lead a horse to water but you can't make him drink!” The manager replied, “Look take my advice, your job is not to make them drink. Your job is to make them thirsty.” Mark and Pete podcast here http://www.markandpete.com Subscribe https://www.youtube.com/channel/UCGwC... Facebook https://www.facebook.com/goodnewsthis... Twitter https://twitter.com/goodnewsthis Pete's blog http://petertimothycooper.com Podcasts featuring Pete: Mark and Pete http://www.markandpete.com The Good News Show http://www.tgnsuk.com Daily Devotional Preaching http://www.dailydevotionalpreaching.com Good News This Morning is: Personal updates from Pete, his family and Friends. comment on interesting, moving and humorous news and articles of the day from a Christian perspective.This channel is dedicated to presenting a sideways look at breaking Christian news and and fascinating features of theology. In these Christian videos, pastor Peter Cooper takes a look at Christian issues of the day, sometimes serious and sometimes whacky: its a Christian video blog.

#RoadToAmericanaFest Journalist and singer-songwriter Peter Cooper of the Country Music Hall of Fame joins me to talk about Jim Lauderdale's classic 'Pretty Close to the Truth' album and how the changes in country music in the 90s created the need for the Americana music genre, the migration of people like Jim and Buddy Miller from California to Nashville and how Jim helped Peter propose to his wife. Subscribe to the podcast in iTunes here or in other podcasting apps by copying/pasting our RSS feed -http://myfavoritealbum.libsyn.com/rss My Favorite Album is a podcast unpacking the great works of pop music. Each episode features a different songwriter or musician discussing their favorite album of all time - their history with it, the making of the album, individual songs and the album's influence on their own music. Jeremy Dylan is a filmmaker, journalist and photographer from Sydney, Australia. He directed the music documentary Jim Lauderdale: The King of Broken Hearts and feature film Benjamin Sniddlegrass and the Cauldron of Penguins, and writes for Capital News magazine. If you've got any feedback or suggestions, drop us a line at myfavoritealbumpodcast@gmail.com.  

Summary How do you keep up with the vast amounts of web technology released daily? It can be a losing battle for some and a opportunity for others. One person in our community that comes to mind is Peter Cooper (@peterc) from Cooper Press. Join us as we learn how his work at O'Reilly has shaped some of his strategies for this as well as what Cooper Press provides and Conferences like OSCon & Fluent O'Reilly Media Partner Discounts The Web Platform Podcast is a proud O'Reilly Media Partner. As such, one of the benefits we provide our listeners are special  discounts such as 50% off ebooks and 40% in printed material. This includes but is not limited to books on the web technologies. Your discount code is PCBW so head over to http://www.oreilly.com/ right now to get all your favorite tech books at much lower prices. Your Latest O'Reilly Discounts 20% Discount to FluentConf http://conferences.oreilly.com/fluent-javascript-html-ca/ Call for proposals is done, registration is open,  and O'Reilly Fluent Conf is back in just a few months. Fluent, The Web Platform conference will be held in San Francisco, CA on March 7-10 2016. Get practical Training in JavaScript, HTML5, CSS and the latest web development technologies and frameworks. The Web Platform Podcast listeners receive a 20% discount when registering for the conference. Make sure you use the promotional code PCWPP20 to receive your discount. Free eBook: Data-Informed Product Design http://www.oreilly.com/pub/cpc/1220 Designers must understand user needs to create any product. But what type of data should you look at? In her new book, Data-Informed Product Design, Pamela Pavliscak outlines a way to use data of all kinds to understand the relationship between people and technology. Generally speaking, big data is quantitative; it gives you the what, where, and when, while “thick data” provides the qualitative perspective—the how and the why. Up until now, there hasn't been much information on how to combine quantitative big data with qualitative thick data. That's where this report can help. If you're involved in any aspect of product design, this is indispensable reading. It's useful, and we're pleased to offer it to you, for free! Get the free ebook now. Design Sprint: A fast start to creating a great digital product http://www.oreilly.com/pub/cpc/1221 October 20 | 10:00am PT | Banfield, Lombardo, & Wax The Design Sprint is the first, and for some projects the most significant, phase of a design thinking process. It gets the entire product design and development team on the same page, reduces the risk of downstream mistakes, and generates vision-lead goals for the team to measure their success. Join Richard Banfield, C. Todd Lombardo, and Trace Wax as they explain why and how Design Sprints work and how you can use Design Sprints to enhance your own design process. Resources Fluent - http://conferences.oreilly.com/fluent-javascript-html-ca Cooper Press - https://cooperpress.com/ Panelists Erik Isaksen (@eisaksen) - Front End Development Lead at Deloitte Digital & Google Developer Expert in Web Technologies Chetan Karande (@karande_c) - Senior Software Engineer at Omgeo LLC, FluentConf Speaker, & Creator of OWASP Node Goat

After crouching to fit under the doorway, singer/songwriter/journalist and gentle giant Peter Cooper steps into the portable podbooth to chat with host Jeremy Dylan about a classic from one of the classiest songwriters in country music - Tom T Hall's 1971 album "In Search of a Song". Along the way, they break down tracks including "The Year Clayton Delany Died", "Trip to Hyden" and "A Million Miles to the City" and talk about Hall's songwriting research trips, how he broke his own songwriting rules, the difference between poetry and song lyrics and why you shouldn't waste time complaining about music you hate. Listen in the player above or download the episode by clicking here. Subscribe to the podcast in iTunes here or in other podcasting apps by copying/pasting our RSS feed - http://myfavoritealbum.libsyn.com/rssMy Favorite Album is a podcast unpacking the great works of pop music. Each episode features a different songwriter or musician discussing their favorite album of all time - their history with it, the making of the album, individual songs and the album's influence on their own music.Jeremy Dylan is a filmmaker from Sydney, Australia who has worked in the music industry since 2007. He directed the the feature music documentary Jim Lauderdale: The King of Broken Hearts (out now and featuring Peter Cooper!) and the feature film Benjamin Sniddlegrass and the Cauldron of Penguins, in addition to many commercials and music videos. If you've got any feedback or suggestions, drop us a line at myfavoritealbumpodcast@gmail.com

Justin, Alex Gemmell & Peter Cooper talk about various Hacker News stories including The Unintended Effects of Driverless Cars, What really happened aboard Air France 447, More Paypal nonsense, Don't Be A Free User, Why we ditched PayPal for Stripe, 17-year-old wins 100k for creating cancer-killing nanoparticle , Zendesk CEO calls Freshdesk a freaking rip off - Freshdesk responds.

Justin and Jason discuss why staying up late can screw up your life, how Skype is almost the full realization of the magical CTU tech of the TV show 24, Peter Cooper's Javascript Weekly newsletter, the prospect of migrating Appignite to a single-page web application, the advantages of leaving a problem unfinished at the end of a work session, Justin's idea for a collective version of Groupon for websites codenamed Groupio, the high-cost of the context switch, whether AnyFu should be incorporated as an LLC and some ideas about vesting and founder death, Justin's review of Zarrella's Hierarchy of Contagiousness, using Twitter's location based search streams, the science of extreme life extension and Leslie Kean's History Channel documentary Secret Access: UFOs on The Record.

Justin, Jason and panel guests Peter Cooper and Gabriel Weinberg discuss the weaknesses of Google search and the opportunities that exist for upstart competitors, how to recognize the early signs of exponential growth, the importance of maintaining psychological resilience as a solo entrepreneur, dispelling the myth that ideas are worthless, the two primary habits of creative people, recent changes made to Pluggio's user journey, pricing and signup process, Peter's e-book project and the potential growth in e-book readers, the tools they use, the technologies they're most excited about and what they wish they knew better.

60: TZ Interview - Peter Cooper & Coder I/O by techzing