Podcasts about Copeland

"AEW Dynamite" tomorrow night in Montreal, Quebec, Canada, their first show in the city, is shaping up to be a big one, with three more Continental Classic matches scheduled, as well as MJF and Samoa Joe taking on two of the mysterious "devil's" henchmen, and Toni Storm defending the AEW Women's World Championship against Skye Blue. But all those bouts arguably pale in comparison to Adam Copeland vs. Christian Cage, a match that will see the two friends and two Canadians wrestle for the first time in 13 years, with Cage's TNT Championship on the line. Given the magnitude of the match, as well as the history between Copeland and Cage that stretches back decades, many were surprised that the bout wound up on TV, instead of taking place at AEW Worlds End later this month. In an interview with Sports Illustrated promoting the match, however, Copeland made no bones about how Montreal was the perfect place for him and Christian to wrestle for the first time in over a decade. Source: Wrestling Inc. WE HAVE SOME GREAT MERCH ON TEE PUBLIC

Hall of Famer Bully Ray breaks down everything from AEW Dynamite including the main event between Adam Copeland and Christian Cage and he gets into the questions surrounding the devil. 

Content warning: In this episode, we discuss suicide, online harassment, and death threats.Today we share two unsettling stories with the common themes of living secret lives and doing things that others would be shocked to discover.You'll hear about the tragic story of Alabama Pastor and Mayor, Fred 'Bubba' Copeland, who, forced to live his life in the closet, used private social media accounts to present himself as a transgender woman and encourage transgender people to come out and go on hormone replacement therapy. After his secret life was exposed by a conservative news website and he was subsequently subjected to relentless online bullying, he took his life. We discuss the complex issues involved in cases like this and the ways that pressure to suppress one's identity can lead to dire outcomes.You'll also hear about a story published in the San Francisco Chronicle, in which a financially successful and apparently mentally stable man made several death threats to an operator from a Mental Health Hotline for LGBTQ+ youth in California. The name and address of this man, who lives in San Francisco, have been identified, but he will not likely face any consequences due to his power and wealth.In This Episode, You Will Learn:Pastor Fred 'Bubba' Copeland's tragic story (1:30)The effects of being forced to live a life in the closet (13:20)Online harassment shouldn't remain unpunished (16:00)People who spread hate online and showcase a "normal" life on a different platform (17:00)Resources Mentioned:Hotline for California's LGBTQ kids got a death threat.Connect with Jackie and Bridget:Transgender Support: Becoming a True Ally Video Course on VimeoTransgender School Patreon Membership with all exclusive contentTransgender School on MediumInstagramWebsite FacebookCommunity Facebook GroupYouTube Hosted on Acast. See acast.com/privacy for more information.

12/03/2023 - Sunday Morning Scriptures Used (In Order of Occurrence):Matthew 4:12-17Romans 5:12Romans 8:8Acts 17:30James 2:19Proverbs 28:13Acts 2:37-38II Corinthians 7:10-11

  «Por tanto, es necesario que prestemos más atención a lo que hemos oído, no sea que nos extraviemos» (Hebreos 2:1) A todos nos ha sucedido. Ponemos un poco de la Palabra de Dios en nuestros cinturones espirituales. Obtenemos algunas victorias. Por primera vez en muchos años nos va muy bien en la vida. Pero, de pronto, nos desviamos del camino y nuestro mundo se derrumba, y tenemos que comenzar otra vez. Eso fue lo que le sucedió a los creyentes de quienes se habla en la carta a los Hebreos. Habían avanzado tanto en la vida espiritual que ya podían ser maestros. Pero con el tiempo se desviaron tanto del camino que fue necesario volver a alimentarlos como a bebés de pecho (lee Hebreos 5:12). ¿Qué fue lo que los hizo tropezar de esa manera? Ellos dejaron que otros asuntos se interpusieran en el camino de la fe. Dejaron que se les olvidaran las promesas de Dios. Por esa razón se desviaron. Esto mismo le ha sucedido a multitud de creyentes en los últimos años. “Bueno, hermano Copeland —dicen algunos—, estamos cansados de este asunto de la fe. La verdad es que no tenemos tanto tiempo para permanecer en la Palabra”. Esos creyentes se han olvidado de las promesas de Dios. No es que hayan dejado de creer en ellas; están más interesados en otras cosas. Han bajado mucho su nivel de conocimiento de la Palabra, y ya que un nivel bajo de Palabra equivale a niveles bajos de fe, pronto empezaron a sufrir derrotas en áreas de su vida donde antes habían triunfado. No dejes que eso te suceda. Cuando las cosas vayan bien, no sólo disfrutes las bendiciones de Dios, sino que también profundiza en lo que Él tiene para ti. Presta más atención a las promesas de Dios, concéntrate en seguir adelante y en fortalecerte espiritualmente, no sólo para que te sea suplido lo que necesitas, sino también para ayudar a los demás en sus necesidades. Recuerda: Un nivel bajo de la Palabra = un nivel bajo de fe = tropiezo. No te distraigas tanto disfrutando las victorias presentes, para que mañana no termines en derrota. Examina las cosas que has aprendido. Presta más atención a la Palabra―no menos. Mantente avanzando de fe en fe y así Satanás y sus secuaces, en vez de tratar de hacerte tropezar, se lamentarán: “¡Oh, no, ahí viene otra vez ese hombre de fe tras nosotros!”. Lectura bíblica: Hebreos 5:11-14, 6:1-12   © 1997 – 2019 Eagle Mountain International Church Inc., también conocida como Ministerios Kenneth Copeland / Kenneth Copeland Ministries. Todos los derechos reservados.

NAIA Full Review of last nights Top 25 action and upcoming weekend games - PLUS - Jamon Copeland, Head Men's Basketball Coach, Ave Maria Gyrenes * Season 5 Episode 41 * Music: Hard Sell Hotel by  Shane Ivers https://www.silvermansound.com

We have a newspalooza for you today. Kara and Scott discuss Elon Musk's decision to put advertisers on blast, Henry Kissinger's death, Nikki Haley's next steps, those Mark Cuban political rumors, and Microsoft's non-voting seat at OpenAI. Then, guest Rob Copeland joins to discuss his new book, “The Fund: Ray Dalio, Bridgewater Associates, and The Unraveling of a Wall Street Legend.” You can find Rob on X at @realrobcopeland. Follow us on Instagram and Threads at @pivotpodcastofficial. Follow us on TikTok at @pivotpodcast. Send us your questions by calling us at 855-51-PIVOT, or at nymag.com/pivot. Learn more about your ad choices. Visit podcastchoices.com/adchoices

PWTorch editor Wade Keller presents the Thursday Flagship edition of the Wade Keller Pro Wrestling Podcast with guest co-host PWTorch VIP analyst Todd Martin. They discuss these topics:A review of last weekend's AEW Rampage and AEW Collision including more Continental Classic tournament matches.A review of last night's AEW Dynamite including the MJF-Samoa Joe segment, Adam Copeland-Christian Cage, and more Continental Classic matches.A review of Tuesday's NXT episode.A review of last week's Smackdown on the eve of Survivor Series including Becky Lynch-Charlotte Flair bickering. Also, reaction to the very big dropoff in viewership with Smackdown on FS1 last Friday compared to typical FS1 dropoffs and compared to a typical Smackdown.A review of Monday's episode of Raw beginning with thoughts on the placement of, the build to, and the content of C.M. Punk's return promo. What was the strategy and did it achieve that effectively and was it a sound strategy? Then a walk through Raw including the ebullient Randy Orton, Cody Rhodes addressing War Games and Punk, the Seth Rollins-Drew McIntyre segment, and more.Reaction to the PFL purchase of Bellator and what it means for MMA landscape.A review of UFC Fight Night from two weekends ago. MAILBAG TOPICS:Is WarGames a good gimmick match for WWE?If Eddie Kingston or Swerve Strickland win the Continental Classic, does it elevate either of them? Or would it define the whole tournament down as a mid-carder tournament? Or is it just too hard to tell until it plays out?How does the Full Gear story with MJF, Adam Cole, and Jay White make any sense? Is AEW looking more and more like a promotion doomed to fail?Did AEW fail to capitalize on Swerve's win over Hangman Page?Would AEW have been better off if the Young Bucks and Kenny Omega weren't every part of AEW? Is it time for Omega to step back with the pain he's in?How did the Young Bucks manage to keep their EVP titles after instigating a confrontation backstage that led to a brawl?Why was AEW vilified for the angle substituting Adam Cole (temporarily) for MJF at Full Gear while WWE got a pass for the tease of Randy Orton not showing up for WarGames?Is the ring style Wade advocated for on the PPV Roundtable after Full Gear superior or would matches look too similar to each other like in WWE?This show is part of the Spreaker Prime Network, if you are interested in advertising on this podcast, contact us at https://www.spreaker.com/show/3076978/advertisement

This week's edition of Copeland's Corner, with featured Headliners  Don Reed, Lauren Mayer & Kate Robards.Tune is as Brian and his guests talk about the latest hot talk topics, current events, and life in general. For more from Lauren, check out her website: LaurenMayer.comFor more from Kate, visit her website: KateRobards.comCheck out Don's "East 14th" at The Marsh Berkeley, head to TheMarsh.org for more info. --For more from Brian...Visit his website: www.BrianCopeland.comFollow on Social Media:  Twitter & Instagram - @BrianCopieEmail: BrianCopelandShow@Gmail.com--Copeland's Corner is Created, Hosted, & Executive Produced by Brian Copeland. This Show is Recorded & Mixed by Charlene Goto with Go-To Productions. Visit Go-To Productions for all your  Podcast & Media needs.

Christian Cage will address Adam Copeland's challenge on this week's episode of AEW Dynamite. AEW announced on Monday that Cage will respond to Copeland's challenge to face him next week on Wednesday's show. The updated card for the episode, which airs Wednesday night on TBS, is: * AEW Continental Classic Match: Swerve Strickland (3) vs. Jay White (3) * AEW Continental Classic Match: Mark Briscoe (0) vs. RUSH (0) * AEW Continental Classic Match: Jon Moxley (3) vs. Jay Lethal (0) * Christian Cage responds to Adam Copeland * Bryan Danielson serves as a guest commentator Source: 411 Mania WE HAVE SOME GREAT MERCH ON TEE PUBLIC

PWTorch editor Wade Keller is joined by Zack Heydorn from SEScoops to discuss AEW Dynamite including analysis of the Continental Classic's second week. They also discuss Toni Storm, MJF-Samoa Joe-Devil Storyline, Christian-Adam Copeland segment, and more with live callers and emails. They are also joined by an on-site correspondent who details a Sting-Ric Flair-Tony Schiavone segment after Dynamite ended for the live crowd, Rampage results, and other in arena observations.This show is part of the Spreaker Prime Network, if you are interested in advertising on this podcast, contact us at https://www.spreaker.com/show/3275545/advertisement

No one could have imagined the house of horrors that was the farm owned by elderly couple, Faye and Ray Copeland. Thank you to Delly Mozingo for her work in researching and writing this story! Learn more about your ad choices. Visit megaphone.fm/adchoices

This week, journalist and author, Rob Copeland joins to discuss his explosive best-selling book: The Fund: Ray Dalio, Bridgewater Associates and the unravelling of a Wall St Legend. Long seen as the paragon of systematic trading, Bridgewater grew to the largest hedge fund in history. Alongside that, its founder, Ray Dalio - a one-time commodities trader - a business legend with his best-selling books and his devotion to his “Principles”. Rob's book exposes a very different fund and leader. We dive into the unique culture and management style Ray created which includes 24hr surveillance, inquisitions over bagels and very public take downs. And also how exactly the fund invested. Rob is a finance reporter for the New York Times.

Explore the minds of pro wrestlers as we engage in thought-provoking conversations about their wrestling styles, character development, and the artistry behind their performances. #3countpodcast #3count #reddawg #chazthedon #nowenteringthering #chazandfriends #ProWrestling #WrestlingInterviews #WrestlingLegends #BehindTheRing #WrestlingCommunity #WrestlingFans #WrestlingTalk #WrestlingInsider #InsideTheSquaredCircle #WrestlingLifestyle --- Support this podcast: https://podcasters.spotify.com/pod/show/the3count/support

Stewart Copeland is a Rock and Roll Hall of Fame inducted musician and the drummer for the British rock band The Police. He is also the author of the new book "Stewart Copeland's Police Diaries."During this podcast, Copeland takes listeners back to the late 1970s and recounts stories of the early days of The Police including meeting and recruiting Sting and Andy Summers to form the band. He also talks about his process as a musician, and his view on whether The Police will ever play together again.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

There are things in life in which one's opinion is very important - eternal salvation, however, is not one of these. It is imperative that we know exactly what the Bible tells us is required for salvation. God's plan for how we are to be saved is clearly laid out in His Word, but only divine revelation can allow us to truly see what we must do to be saved. 11/26/2023 - Sunday MorningScriptures Used (In Order of Occurrence):Exodus 25:8-9, 40Hebrews 8:5Romans 10:9John 12:25Acts 10:1-2, 44-47Acts 2:37-38

The Sporting Tribune's Arash Markazi is joined by Adrian Hernanez, who interviews WWE hall of famer and wrestling legend Adam "Edge" Copeland as well as WNBA champion Alsyha Clark on this special Thanksgiving edition of the show. Host: Arash Markazi Producer: Ji Hae Wiley Subscribe: Spotify / Apple Podcasts / Stitcher/ RSS And do not forget to follow or subscribe to The Arash Markazi Show on Spotify, Google Podcasts, Stitcher, TuneIn, & I Heart Radio. Also check out his daily columns on themorningcolumn.com and The Sporting Tribune. Music Credit: Alright by Kendrick Lamar Humble by Kendrick Lamar I Get Around by 2Pac To Live and Die in L.A. by 2Pac Social Media: Instagram & Twitter: @thesportingtrib

Have you ever wondered how a creatively branded service vehicle can create a massive impact on your small business's visibility and growth? In the current age of digital marketing dominance, we're shifting our focus to a traditional yet remarkably effective marketing method that can generate immense recognition for skilled trades businesses, HVAC companies, and the plumbing industry. CJ Stratte, the brilliant and dynamic CEO of On The Move Trucks, a nationwide truck leasing company, joins us in today's episode of the Service Business Mastery Podcast, to teach us more! CJ, an expert in brand marketing, oversees a company that helps primarily HVAC and plumbing businesses, transforms ordinary service vans into eye-catching moving billboards for their brands. This episode is packed with exciting insights into the power of physical mobile advertising, and how even a single leased van could significantly boost your brand's visibility. Key actionable takeaways for skilled trades businesses include:  Firstly, not underestimating the value of traditional marketing methods such as branded service vehicles. Second, the importance of creating engaging, telling visuals on service trucks. The potential of truck fleets as moving billboards and driving brand recognition. Lastly, to explore On The Move Trucks' services, from leasing to custom wraps, as ain important resource for your business. So buckle up and prepare for an intriguing ride into the world of truck leasing and unique marketing strategies–the road to enhanced brand visibility starts here!    SHOW NOTES [00:04] Intro + Tersh's Experience with Sign Branding Promo for Service Emperor [03:21] Sponsor Details [07:24] Who is “On the Move Trucks”? [08:00]  CJ's Business Experience [11:37] Business Impressions Per Mile [11: 53] “Old School” Word of Mouth Marketing [15:40] On The Move's Truck Leasing Program [21:02] “New School” QR Code Marketing  [24:11] Display Your Trucks! [26:09] Best Practices for Truck Promo [29:40] Various truck options. Contact Them for inventory. Resources And People Mentioned: Connect With Spencer on LinkedIn Here! Or check out his book's website: entreprenumbers.com.  This episode is kindly sponsored by: - Sera (visit their website) - UpFrog (visit their website) - Copeland (visit their website). - CompanyCam (visit their website) Visit www.companycam.com/SBM and use code SBM for a free 2-week trial, 1:1 training and account setup, and 50% off your first two months! - Interplay Learning (visit their website) - Join the Service Business Mastery Facebook group Affiliate Links: - Castmagic - https://get.castmagic.io/SBM  - StreamYard - https://streamyard.com/pal/c/4524595769507840 - CallRail - https://partners.callrail.com/relentless-digital  - IfTTT- 10 Percent off!  - https://ifttt.com/join?referral_code=BoERPHYVbCFE-C7okWNiClo3ygLafRze 

Rob Copeland worked at Microsoft for almost 23 years as an Engineering Manager Executive. He worked on the developer tools from Microsoft including Visual Basic and Visual Studio; he then shifted to working on tablet first features for Windows including the tablet PCs back in 2006 and Windows 8. Rob has used the iPad since it was first released in 2010. It is from this very interesting background that we have this discussion about computing and how he uses the iPad as his primary computer. This episode of iPad Pros is sponsored by Agenda, the award winning app that seamlessly integrates calendar events into your note taking. Learn more at www.agenda.com. Agenda 18 is now available as a free download for macOS, iPadOS, and iOS.Bonus content and early episodes of both iPad Pros and Vision Pros with chapter markers are available by supporting the podcast at www.patreon.com/ipadpros. Bonus content and early episodes are also now available in Apple Podcasts! Subscribe today to get instant access to iPad Possibilities, iPad Ponderings, and iPad Historia!Show notes are available at www.iPadPros.net. Feedback is welcomed at iPadProsPodcast@gmail.com.Links:Rob's Mastodon: https://mastodon.social/@coperobWords from Rob: https://wordsfromrob.comRob's Tech Talk: https://robstechtalk.comSpencerian Cursive Copybook Set and Theory Books: https://www.amazon.com/dp/088062096XChapter Markers:00:00:00: Opening00:01:36: Support the Podcast00:02:11: Rob Copeland00:07:21: Apple Pencil00:09:43: Rob's Time at Microsoft00:15:05: Favorite iPads00:17:14: Your first computers00:22:25: The Future of Computing00:29:17: 11 vs 12.900:32:19: What can't you do on iPad?00:36:12: Learning to Code00:39:39: Sponsor: Agenda00:42:08: Writing on iPad00:48:53: Journaling00:55:06: Spencerian Handwriting Books00:58:00: Apple's Journal app01:00:25: Reading01:03:14: Email01:05:28: Task Management01:07:15: Web Browsing01:09:44: Researching01:12:06: Finance and Expense Tracking01:15:58: Photo and Video Editing01:22:15: Music01:26:41: Anything else?01:27:12: General online talk about iPad01:32:59: Versatility01:36:24: Where can people follow you online?01:36:58: Closing Hosted on Acast. See acast.com/privacy for more information.

See omnystudio.com/listener for privacy information.

Join us on Got Clutter? Get Organized! with guest Shante Copeland, a seasoned personal and financial coach, advisor, and consultant. As the proud owner of Copeland Consulting LLC, located in the heart of Delaware, Shante has dedicated her career to guiding thousands of individuals and small businesses toward the realization of their personal and professional financial aspirations. With over two decades of certification and hands-on experience in an array of financial domains such as tax preparation and advising, credit education and repair, small business startup, budgeting, business management and administration, fundraising, real estate investing, and more, Shante brings a wealth of knowledge to the table. Shante's lifetime of expertise empowers her to craft tailored financial plans for her clients, enabling them to build wealth through strategic investments and effective money management. She is passionate about teaching her clients how to make their money work for them, offering programs that transform "side hustles" into thriving businesses while maintaining a disciplined budget. In this episode, Shante delves into the world of personal finance and entrepreneurship, tackling pressing questions like, "What made you decide to become a financial coach?" and offering invaluable insights for the holiday season, including what to avoid if you're prone to overspending. Plus, she shares practical tips for anyone looking to transform their spending habits and take control of their financial future. Shante Copeland's wisdom will inspire and empower you to take charge of your financial destiny. Don't miss out on this transformative journey! Website: https://www.copelandconsulting.org/ Instagram: https://www.instagram.com/smcopelandconsulting/ Connect with Janet: Schedule a FREE 15 Minute consultation: https://janetmtaylor.trafft.com/services/15-minute-session-with-janet      Facebook Group: https://www.facebook.com/groups/livinglifetotallyorganized    YouTube video: https://www.youtube.com/janetmtaylor Instagram: https://www.instagram.com/janettheorganizer/ Pinterest: https://www.pinterest.com/janetmtaylor/ TikTok: https://www.tiktok.com/@janettheorganizer?lang=en   Organizing Resources: Janet's Amazon Shop: https://www.amazon.com/shop/organizerjanet e-Course-Clear Your Desk, Clear Your Mind: https://www.udemy.com/course/clear-your-desk-clear-your-mind/?referralCode=0DD419607B4412066F49   Ways You Can Support Our Podcast: Individuals: https://www.buymeacoffee.com/GCGOwithJanet    Businesses: https://www.shoutparty.com/shop/p/got-clutter-get-organized-with-janet

To support the ministry of The Avenue Community Church visit https://www.theavecc.org/give

Have you ever considered the interplay between philanthropy and social entrepreneurship and its power in shaping  Black communities globally? Brace yourself for an eye-opening journey into the heart of the Black philanthropy movement, guided by none other than Dr. Jackie Bouvier Copeland, the brilliant founder of Black Philanthropy Month. We explore her inspiring journey from her roots in a Black community of the '60s and '70s to her groundbreaking initiatives that are now transforming lives in over 60 countries.Discover how passion, resilience, and an unshakeable belief in human potential led to the creation of the Women Invested to Save Earth (WISE) Fund. Dr. Copeland highlights the myriad forms of social finance and how the WISE Fund is championing change by supporting businesses and nonprofits in Black and Indigenous communities. But that's not all. We delve into the nuances of the multi-trillion-dollar social finance industry and how the People's Impact Fund aims to democratize investing, making it accessible to the average person. In the spirit of this year's Black Philanthropy Month, we also immerse ourselves in the deeper currents of love and collective giving. Learn from Dr. Copeland as she elucidates on the transformative power of giving back, creating sustainable change, and investing in our own institutions. As we celebrate Black Philanthropy, we also acknowledge its role in fostering social entrepreneurship and community empowerment. So tune in, get inspired, and discover how to participate in this remarkable movement.Support the show

Join us on Got Clutter? Get Organized! with guest Shante Copeland, a seasoned personal and financial coach, advisor, and consultant. As the proud owner of Copeland Consulting LLC, located in the heart of Delaware, Shante has dedicated her career to guiding thousands of individuals and small businesses toward the realization of their personal and professional financial aspirations. With over two decades of certification and hands-on experience in an array of financial domains such as tax preparation and advising, credit education and repair, small business startup, budgeting, business management and administration, fundraising, real estate investing, and more, Shante brings a wealth of knowledge to the table. Shante's lifetime of expertise empowers her to craft tailored financial plans for her clients, enabling them to build wealth through strategic investments and effective money management. She is passionate about teaching her clients how to make their money work for them, offering programs that transform "side hustles" into thriving businesses while maintaining a disciplined budget. In this episode, Shante delves into the world of personal finance and entrepreneurship, tackling pressing questions like, "What made you decide to become a financial coach?" and offering invaluable insights for the holiday season, including what to avoid if you're prone to overspending. Plus, she shares practical tips for anyone looking to transform their spending habits and take control of their financial future. Shante Copeland's wisdom will inspire and empower you to take charge of your financial destiny. Don't miss out on this transformative journey! Website: https://www.copelandconsulting.org/ Email: scopeland@copelandconsulting.org Phone : 570-517-1265 Instagram: https://www.instagram.com/smcopelandconsulting/ Connect with Janet: Schedule a FREE 15 Minute consultation: https://janetmtaylor.trafft.com/services/15-minute-session-with-janet      Facebook Group: https://www.facebook.com/groups/livinglifetotallyorganized    YouTube video: https://www.youtube.com/janetmtaylor Instagram: https://www.instagram.com/janettheorganizer/ Pinterest: https://www.pinterest.com/janetmtaylor/ TikTok: https://www.tiktok.com/@janettheorganizer?lang=en   Organizing Resources: Janet's Amazon Shop: https://www.amazon.com/shop/organizerjanet e-Course-Clear Your Desk, Clear Your Mind: https://www.udemy.com/course/clear-your-desk-clear-your-mind/?referralCode=0DD419607B4412066F49   Ways You Can Support Our Podcast: Individuals: https://www.buymeacoffee.com/GCGOwithJanet    Businesses: https://www.shoutparty.com/shop/p/got-clutter-get-organized-with-janet   --- Send in a voice message: https://podcasters.spotify.com/pod/show/janetmtaylor/message

  «Y Jesús le preguntó: «¿Qué quieres que haga por ti?» El ciego le respondió: «Maestro, quiero recobrar la vista» (Marcos 10:51) Todos sabemos lo que es estar dando vueltas, sin llegar a ninguna parte; sabemos lo que es salir de un aprieto económico por medio de la oración, para meternos en otro; y lo que es ser sanado de una enfermedad para que otra distinta nos ataque. Sí, claro, nos esforzamos. Oramos y ejercitamos nuestra fe. Pero seguimos cayendo una y otra vez en los mismos problemas. ¿Por qué? Porque en realidad casi nunca sabemos qué pedir. Ahora mismo puedo imaginarme tu reacción: “Créame, hermano Copeland, yo no tengo ese problema. Yo sé muy bien lo que necesito. Pero lo que hace que mi cabeza de vueltas es saber cómo vendrá esa provisión para lo que necesito”. Eso es lo que la mayoría de la gente también cree. Muchos desperdician su tiempo orando por obtener cosas que en realidad no necesitan y pidiendo cosas que no quieren; y así, no logran conseguir nada. Mira conmigo Marcos 10, y verás lo que quiero decir. Bartimeo el ciego estaba sentado junto al camino mendigando cuando Jesús pasaba: «Cuando éste supo que quien venía era Jesús de Nazaret, comenzó a gritar y a decir: «Jesús, Hijo de David, ¡ten misericordia de mí!»… Arrojando su capa, el ciego dio un salto y se acercó a Jesús, y Jesús le preguntó: «¿Qué quieres que haga por ti?» El ciego le respondió: «Maestro, quiero recobrar la vista.» Jesús le dijo: «Vete, tu fe te ha salvado.» Y enseguida el ciego recobró la vista, y siguió a Jesús en el camino» (versículos 47, 50-52). Ahora, quiero que pienses en algo por unos instantes. A la luz de lo que las Escrituras nos revelan, ¿cuántas necesidades tenía Bartimeo? ¿Sólo una? ¡No! Bartimeo no sólo era ciego, sino también mendigo. Probablemente él tenía más problemas de los que tú puedas imaginarte, y cada uno de ellos era una necesidad tangible en la vida de Bartimeo. Pero lo que él necesitaba era la vista. De recuperarla, todo lo demás se arreglaría por sí solo. Bartimeo lo sabía. Entonces, cuando Jesús le preguntó: “Bartimeo, «¿Qué quieres que haga por ti?»”, él sabía exactamente lo que iba a pedir, y lo recibió. Hoy Jesús desea socorrerte como lo hizo con Bartimeo y proveerte de lo que necesitas. Pero ¿sabes qué pedir? Piénsalo bien. Ora. Deja que el Señor Jesús sea quien abra tus ojos y te muestre lo que en realidad necesitas. Al hacerlo, tus oraciones adquirirán una nueva dimensión, un nuevo poder: en vez de tocar de manera superficial tus problemas, irás directamente al grano y los resolverás, y no tendrás que desperdiciar más tu vida dando vueltas sin sentido. Lectura bíblica: Marcos 10:46-52   © 1997 – 2019 Eagle Mountain International Church Inc., también conocida como Ministerios Kenneth Copeland / Kenneth Copeland Ministries. Todos los derechos reservados.

David was the chief software architect and director of engineering at Stitch Fix. He's also the author of a number of books including Sustainable Web Development with Ruby on Rails and most recently Ruby on Rails Background Jobs with Sidekiq. He talks about how he made decisions while working with a medium sized team (~200 developers) at Stitch Fix. The audio quality for the first 19 minutes is not great but the correct microphones turn on right after that. Recorded at RubyConf 2023 in San Diego. A few topics covered: Ruby's origins at Stitch Fix Thoughts on Go Choosing technology and cloud services Moving off heroku Building a platform team Where Ruby and Rails fit in today The role of books and how different people learn Large Language Model's effects on technical content Related Links David's Blog Mastodon Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today. I want to share another conversation from RubyConf San Diego. This time it's with David Copeland. He was a chief software architect and director of engineering at stitch fix. And at the start of the conversation, you're going to hear about why he decided to write the book, sustainable web development with Ruby on rails. Unfortunately, you're also going to notice the sound quality isn't too good. We had some technical difficulties. But once you hit the 20 minute mark of the recording, the mics are going to kick in. It's going to sound way better. So I hope you stick with it. Enjoy. Ruby at Stitch Fix [00:00:35] David: Stitch Fix was a Rails shop. I had done a lot of Rails and learned a lot of things that worked and didn't work, at least in that situation. And so I started writing them down and I was like, I should probably make this more than just a document that I keep, you know, privately on my computer. Uh, so that's, you know, kind of, kind of where the genesis of that came from and just tried to, write everything down that I thought what worked, what didn't work. Uh, if you're in a situation like me. Working on a product, with a medium sized, uh, team, then I think the lessons in there will be useful, at least some of them. Um, and I've been trying to keep it up over, over the years. I think the first version came out a couple years ago, so I've been trying to make sure it's always up to date with the latest stuff and, and Rails and based on my experience and all that. [00:01:20] Jeremy: So it's interesting that you mention, medium sized team because, during the, the keynote, just a few moments ago, Matz the creator of Ruby was talking about how like, Oh, Rails is really suitable for this, this one person team, right? Small, small team. And, uh, he was like, you're not Google. So like, don't worry about, right. Can you scale to that level? Yeah. Um, and, and I wonder like when you talk about medium size or medium scale, like what are, what are we talking? [00:01:49] David: I think probably under 200 developers, I would say. because when I left Stitch Fix, it was closing in on that number of developers. And so it becomes, you know, hard to... You can kind of know who everybody is, or at least the names sound familiar of everybody. But beyond that, it's just, it's just really hard. But a lot of it was like, I don't have experience at like a thousand developer company. I have no idea what that's like, but I definitely know that Rails can work for like... 200 ish people how you can make it work basically. yeah. [00:02:21] Jeremy: The decision to use Rails, I'm assuming that was made before you joined? [00:02:26] David: Yeah, the, um, the CTO of Stitch Fix, he had come in to clean up a mess made by contractors, as often happens. They had used Django, which is like the Python version of Rails. And he, the CTO, he was more familiar with Rails. So the first two developers he hired, also familiar with Rails. There wasn't a lot to maintain with the Django app, so they were like, let's just start fresh, fresh with Rails. yeah, but it's funny because a lot of the code in that Rails app was, like, transliterated from Python. So you could, it would, it looked like the strangest Ruby code in the world because it was basically, there was no test. So they were like, let's just write the Ruby version of this Python just so we know it works. but obviously that didn't, didn't last forever, so. [00:03:07] Jeremy: So, so what's an example of a, of a tell? Where you're looking at the code and you're like, oh, this is clearly, it came from Python. [00:03:15] David: You'd see like, very, very explicit, right? Like Python, there's a lot of like single line things. very like, this sounds like a dig, but it's very simple looking code. Like, like I don't know Python, but I was able to change this Django app. And I had to, I could look at it and you can figure out immediately how it works. Cause there's. Not much to it. There's nothing fancy. So, like, this, this Ruby code, there was nothing fancy. You'd be like, well, maybe they should have memoized that, or maybe they should have taken that into another class, or you could have done this with a hash or something like that. So there was, like, none of that. It was just, like, really basic, plain code like you would see in any beginning programming language kind of thing. Which is at least nice. You can understand it. but you probably wouldn't have written it that way at first in Ruby. Thoughts on Go [00:04:05] Jeremy: Yeah, that's, that's interesting because, uh, people sometimes talk about the Go programming language and how it looks, I don't know if simple is the right word, but it's something where you look at the code and even if you don't necessarily understand Go, it's relatively straightforward. Yeah. I wonder what your thoughts are on that being a strength versus that being, like, [00:04:25] David: Yeah, so at Stitch Fix at one point we had a pro, we were moving off of Heroku and we were going to, basically build a deployment platform using ECS on AWS. And so the deployment platform was a Rails app and we built a command line tool using Ruby. And it was fine, but it was a very complicated command line tool and it was very slow. And so one of the developers was like, I'm going to rewrite it in Go. I was like, ugh, you know, because I just was not a big fan. So he rewrote it in Go. It was a bazillion times faster. And then I was like, okay, I'm going to add, I'll add a feature to it. It was extremely easy. Like, it's just like what you said. I looked at it, like, I don't know anything about Go. I know what is happening here. I can copy and paste this and change things and make it work for what I want to do. And it did work. And it was, it was pretty easy. so there's that, I mean, aesthetically it's pretty ugly and it's, I, I. I can't really defend that as a real reason to not use it, but it is kind of gross. I did do Go, I did a small project in Go after Stitch Fix, and there's this vibe in Go about like, don't create abstractions. I don't know where I got that from, but every Go I look at, I'm like we should make an abstraction for this, but it's just not the vibe. They just don't like doing that. They like it all written out. And I see the value because you can look at the code and know what it does and you don't have to chase abstractions anywhere. But. I felt like I was copying and pasting a lot of, a lot of things. Um, so I don't know. I mean, the, the team at Stitch Fix that did this like command line app in go, they're the platform team. And so their job isn't to write like web apps all day, every day. There's kind of in and out of all kinds of things. They have to try to figure out something that they don't understand quickly to debug a problem. And so I can see the value of something like go if that's your job, right? You want to go in and see what the issue is. Figure it out and be done and you're not going to necessarily develop deep expertise and whatever that thing is that you're kind of jumping into. Day to day though, I don't know. I think it would make me kind of sad. (laughs) [00:06:18] Jeremy: So, so when you say it would make you kind of sad, I mean, what, what about it? Is it, I mean, you mentioned that there's a lot of copy and pasting, so maybe there's code duplication, but are there specific things where you're like, oh, I just don't? [00:06:31] David: Yeah, so I had done a lot of Java in my past life and it felt very much like that. Where like, like the Go library for making an HTTP call for like, I want to call some web service. It's got every feature you could ever want. Everything is tweakable. You can really, you can see why it's designed that way. To dial in some performance issue or solve some really esoteric thing. It's there. But the problem is if you just want to get an JSON, it's just like huge production. And I felt like that's all I really want to do and it's just not making it very easy. And it just felt very, very cumbersome. I think that having to declare types also is a little bit of a weird mindset because, I mean, I like to make types in Ruby, I like to make classes, but I also like to just use hashes and stuff to figure it out. And then maybe I'll make a class if I figure it out, but Go, you can't. You have to have a class, you have to have a type, you have to think all that ahead of time, and it just, I'm not used to working that way, so it felt, I mean, I guess I could get used to it, but I just didn't warm up to that sort of style of working, so it just felt like I was just kind of fighting with the vibe of the language, kind of. Yeah, [00:07:40] Jeremy: so it's more of the vibe or the feel where you're writing it and you're like this seems a little too... Explicit. I feel like I have to be too verbose. It just doesn't feel natural for me to write this. [00:07:53] David: Right, it's not optimized for what in my mind is the obvious case. And maybe that's not the obvious case for the people that write Go programs. But for me, like, I just want to like get this endpoint and get the JSON back as a map. Not any easier than any other case, right? Whereas like in Ruby, right? And you can, I think if you include net HTTP, you can just type get. And it will just return whatever that is. Like, that's amazing. It's optimized for what I think is a very common use case. So it makes me feel really productive. It makes me feel pretty good. And if that doesn't work out long term, I can always use something more complicated. But I'm not required to dig into the NetHttp library just to do what in my mind is something very simple. [00:08:37] Jeremy: Yeah, I think that's something I've noticed myself in working with Ruby. I mean, you have the standard library that's very... Comprehensive and the API surface is such that, like you said there, when you're trying to do common tasks, a lot of times they have a call you make and it kind of does the thing you expected or hoped for. [00:08:56] David: Yeah, yeah. It's kind of, I mean, it's that whole optimized for programmer happiness thing. Like it does. That is the vibe of Ruby and it seems like that is still the way things are. And, you know, I, I suppose if I had a different mindset, I mean, because I work with developers who did not like using Ruby or Rails. They loved using Go or Java. And I, I guess there's probably some psychological analysis we could do about their background and history and mindset that makes that make sense. But, to me, I don't know. It's, it's nice when it's pleasant. And Ruby seems pleasant. (laughs) Choosing Technology [00:09:27] Jeremy: as a... Software Architect, or as a CTO, when, when you're choosing technology, what are some of the things you look at in terms of, you know? [00:09:38] David: Yeah, I mean, I think, like, it's a weird criteria, but I think what is something that the team is capable of executing with? Because, like, most, right, most programming languages all kind of do the same thing. Like, you can kind of get most stuff done in most common popular programming languages. So, it's probably not... It's not true that if you pick the wrong language, you can't build the app. Like, that's probably not really the case. At least for like a web app or something. so it's more like, what is the team that's here to do it? What are they comfortable and capable of doing? I worked on a project with... It was a mix of like junior engineers who knew JavaScript, and then some senior engineers from Google. And for whatever reason someone had chosen a Rails app and none of them were comfortable or really yet competent with doing Ruby on Rails and they just all hated it and like it didn't work very well. Um, and so even though, yes, Rails is a good choice for doing stuff for that team at that moment. Not a good choice. Right. So I think you have to go in and like, what, what are we going to be able to execute on so that when the business wants us to do something, we just do it. And we don't complain and we don't say, Oh, well we can't because this technology that we chose, blah, blah, blah. Like you don't ever want to say that if possible. So I think that's. That's kind of the, the top thing. I think second would be how widely supported is it? Like you don't want to be the cutting edge user that's finding all the bugs in something really. Like you want to use something that's stable. Postgres, MySQL, like those work, those are fine. The bugs have been sorted out for most common use cases. Some super fancy edge database, I don't know if I'd want to be doing, doing that you know? Choosing cloud services [00:11:15] Jeremy: How do you feel about the cloud specific services and databases? Like are you comfortable saying like, oh, I'm going to use... Google Cloud, BigQuery. Yeah. [00:11:27] David: That sort of thing. I think it would kind of fall under the same criteria that I was just, just saying like, so with AWS it's interesting 'cause when we moved from Heroku to AWS by EC2 RDS, their database thing, uh, S3, those have been around for years, probably those are gonna work, but they always introduce new things. Like we, we use RabbitMQ and AWS came out with. Some, I forget what it was, it was a queuing service similar to Rabbit. We were like, Oh, maybe we should switch to that. But it was clear that they weren't really ready to support it. So. Yeah, so we didn't, we didn't switch to that. So I, you gotta try to read the tea leaves of the provider to see are they committed to, to supporting this thing or is this there to get some enterprise client to move into the cloud. And then the idea is to move off of that transitional thing into what they do support. And it's hard to get a clear answer from them too. So it takes a little bit of research to figure out, Are they going to support this or not? Because that's what you don't want. To move everything into some very proprietary cloud system and have them sunset it and say, Oh yeah, now you've got to switch again. Uh, that kind of sucks. So, it's a little trickier. [00:12:41] Jeremy: And what kind of questions or research do you do? Is it purely a function of this thing has existed for X number of years so I feel okay? [00:12:52] David: I mean, it's kind of similar to looking at like some gem you're going to add to your project, right? So you'll, you'll look at how often does it change? Is it being updated? Uh, what is the documentation? Does it look like someone really cared about the documentation? Does the documentation look updated? Are there issues with it that are being addressed or, or not? Um, so those are good signals. I think, talking to other practitioners too can be good. Like if you've got someone who's experienced. You can say, hey, do you know anybody back channeling through, like, everybody knows somebody that works at AWS, you can probably try to get something there. at Stitch Fix, we had an enterprise support contract, and so your account manager will sometimes give you good information if you ask. Again, it's a, they're not going to come out and say, don't use this product that we have, but they might communicate that in a subtle way. So you have to triangulate from all these sources to try to. to try to figure out what, what you want to do. [00:13:50] Jeremy: Yeah, it kind of makes me wish that there was a, a site like, maybe not quite like, can I use, right? Can I use, you can see like, oh, can I use this in my browser? Is there, uh, like an AWS or a Google Cloud? Can I trust this? Can I trust this? Yeah. Is this, is this solid or not? [00:14:04] David: Right, totally. It's like, there's that, that site where you, it has all the Apple products and it says whether or not you should buy it because one may or may not be coming out or they may be getting rid of it. Like, yeah, that would... For cloud services, that would be, that would be nice. [00:14:16] Jeremy: Yeah, yeah. That's like the Mac Buyer's Guide. And then we, we need the, uh, the technology. Yeah. Maybe not buyers. Cloud Provider Buyer's Guide, yeah. I guess we are buyers. [00:14:25] David: Yeah, yeah, totally, totally. [00:14:27] Jeremy: it's interesting that you, you mentioned how you want to see that, okay, this thing is mature. I think it's going to stick around because, I, interviewed, someone who worked on, I believe it was the CloudWatch team. Okay. Daniel Vassalo, yeah. so he left AWS, uh, after I think about 10 years, and then he wrote a book called, uh, The Good Parts of AWS. Oh! And, if you read his book, most of the services he says to use are the ones that are, like, old. Yeah. He's, he's basically saying, like, S3, you know you're good. Yeah. Right? but then all these, if you look at the AWS webpage, they have who knows, I don't know how many hundreds of services. Yeah. He's, he's kind of like I worked there and I would not use, you know, all these new services. 'cause I myself, I don't trust [00:15:14] David: it yet. Right. And so, and they're working there? Yeah, they're working there. Yeah. No. One of the VPs at Stitch Fix had worked on Google Cloud and so when we were doing this transition from Heroku, he was like, we are not using Google Cloud. I was like, really? He's like AWS is far ahead of the game. Do not use Google Cloud. I was like, all right, I don't need any more info. You work there. You said don't. I'm gonna believe you. So [00:15:36] Jeremy: what, what was his did he have like a core point? [00:15:39] David: Um, so he never really had anything bad to say about Google per se. Like I think he enjoyed his time there and I think he thought highly of who he worked with and what he worked on and that sort of thing. But his, where he was coming from was like AWS was so far ahead. of Google on anything that we would use, he was like, there's, there's really no advantage to, to doing it. AWS is a known quantity, right? it's probably still the case. It's like, you know, you've heard the nobody ever got fired for using IBM or using Microsoft or whatever the thing is. Like, I think that's, that was kind of the vibe. And he was like, moving all of our infrastructure right before we're going to go public. This is a serious business. We should just use something that we know will work. And he was like, I know this will work. I'm not confident about. Google, uh, for our use case. So we shouldn't, we shouldn't risk it. So I was like, okay, I trust you because I didn't know anything about any of that stuff at the time. I knew Heroku and that was it. So, yeah. [00:16:34] Jeremy: I don't know if it's good or bad, but like you said, AWS seems to be the default choice. Yeah. And I mean, there's people who use Azure. I assume it's mostly primarily Microsoft. Yeah. And then there's Google Cloud. It's not really clear why you would pick it, unless there was a specific service or something that only they had. [00:16:55] David: Yeah, yeah. Or you're invested in Google, you know, you want to keep everything there. I mean, I don't know. I haven't really been at that level to make that kind of decision, and I would probably choose AWS for the reasons discussed, but, yeah. Moving off Heroku [00:17:10] Jeremy: And then, so at Stitch Fix, you said you moved off of Heroku [00:17:16] David: yeah. Yeah, so we were heavy into Heroku. I think that we were told that at one point we had the biggest Heroku Postgres database on their platform. Not a good place to be, right? You never want to be the biggest customer person, usually. but the problem we were facing was essentially we were going to go public. And to do that, you're under all the scrutiny. about many things, including the IT systems and the security around there. So, like, by default, a Postgres, a Heroku Postgres database is, like, on the internet. It's only secured by the password. all their services are on the internet. So, not, not ideal. they were developing their private cloud service at that time. And so that would have given us, in theory, on paper, it would have solved all of our problems. And we liked Heroku and we liked the developer experience. It was great. but... Heroku private spaces, it was still early. There's a lot of limitations that when they explained why those limitations, they were reasonable. And if we had. started from scratch on Heroku Private Spaces. It probably would have worked great, but we hadn't. So we just couldn't make it work. So we were like, okay, we're going to have to move to AWS so that everything can be basically off the internet. Like our public website needs to be on the internet and that's kind of it. So we need to, so that's basically was the, was the impetus for that. but it's too bad because I love Heroku. It was great. I mean, they were, they were a great partner. They were great. I think if Stitch Fix had started life a year later, Private Spaces. Now it's, it's, it's way different than it was then. Cause it's been, it's a mature product now, so we could have easily done that, but you know, the timing didn't work out, unfortunately. [00:18:50] Jeremy: And that was a compliance thing to, [00:18:53] David: Yeah. And compliance is weird cause they don't tell you what to do, but they give you some parameters that you need to meet. And so one of them is like how you control access. So, so going public, the compliance is around the financial data and. Ensuring that the financial data is accurate. So a lot of the systems at Stichfix were storing the financial data. We, you know, the warehouse management system was custom made. Uh, all the credit card processing was all done, like it was all in some databases that we had running in Heroku. And so those needed to be subject to stricter security than we could achieve with just a single password that we just had to remember to rotate when someone like left the team. So that was, you know, the kind of, the kind of impetus for, for all of that. [00:19:35] Jeremy: when you were using Heroku, Salesforce would have already owned it then. Did you, did you get any sense that you weren't really sure about the future of the platform while you're on it or, [00:19:45] David: At that time, no, it seemed like they were still innovating. So like, Heroku has a Redis product now. They didn't at the time we wish that they did. They told us they're working on it, but it wasn't ready. We didn't like using the third parties. Kafka was not a thing. We very much were interested in that. We would have totally used it if it was there. So they were still. Like doing bigger innovations then, then it seems like they are now. I don't know. It's weird. Like they're still there. They still make money, I assume for Salesforce. So it doesn't feel like they're going away, but they're not innovating at the pace that they were kind of back in the day. [00:20:20] Jeremy: it used to feel like when somebody's asking, I want to host a Rails app. Then you would say like, well, use Heroku because it's basically the easiest to get started. It's a known quantity and it's, it's expensive, but, it seemed for, for most people, it was worth it. and then now if I talk to people, it's like. Not what people suggest anymore. [00:20:40] David: Yeah, because there's, there's actual competitors. It's crazy to me that there was no competitors for years, and now there's like, Render and Fly. io seem to be the two popular alternatives. Um, I doubt they're any cheaper, honestly, but... You get a sense, right, that they're still innovating, still building those platforms, and they can build with, you know, all of the knowledge of what has come before them, and do things differently that might, that might help. So, I still use Heroku for personal things just because I know it, and I, you know, sometimes you don't feel like learning a new thing when you just want to get something done, but, yeah, I, I don't know if we were starting again, I don't know, maybe I'd look into those things. They, they seem like they're getting pretty mature and. Heroku's resting on its laurels, still. [00:21:26] Jeremy: I guess I never quite the mindset, right? Where you You have a platform that's doing really well and people really like it and you acquire it and then it just It seems like you would want to keep it rolling, right? (laughs) [00:21:38] David: Yeah, it's, it is wild, I mean, I guess... Why did you, what was Salesforce thinking they were going to get? Uh, who knows maybe the person at Salesforce that really wanted to purchase it isn't there. And so no one at Salesforce cares about it. I mean, there's all these weird company politics that like, who knows what's going on and you could speculate. all day. What's interesting is like, there's definitely some people in the Ruby community who work there and still are working there. And that's like a little bit of a canary for me. I'm like, all right, well, if that person's still working there, that person seems like they're on the level and, and, and, and seems pretty good. They're still working there. It, it's gotta be still a cool place to be or still doing something, something good. But, yeah, I don't know. I would, I would love to know what was going on in all the Salesforce meetings about acquiring that, how to manage it. What are their plans for it? I would love to know that stuff. [00:22:29] Jeremy: maybe you had some experience with this at Stitch Fix But I've heard with Heroku some of their support staff at least in the past they would, to some extent, actually help you troubleshoot, like, what's going on with your app. Like, if your app is, like, using a whole bunch of memory, and you're out of memory, um, they would actually kind of look into that, for you, which is interesting, because it's like, that's almost like a services thing than it is just a platform. [00:22:50] David: Yeah. I mean, they, their support, you would get, you would get escalated to like an engineer sometimes, like who worked on that stuff and they would help figure out what the problem was. Like you got the sense that everybody there really wanted the platform to be good and that they were all sort of motivated to make sure that everybody. You know, did well and used the platform. And they also were good at, like a thing that trips everybody up about Heroku is that your app restarts every day. And if you don't know anything about anything, you might think that is stupid. Why, why would I want that? That's annoying. And I definitely went through that and I complained to them a lot. And I'm like, if you only could not restart. And they very patiently and politely explained to me why that it needed to do that, they weren't going to remove that, and how to think about my app given that reality, right? Which is great because like, what company does that, right? From the engineers that are working on it, like No, nobody does that. So, yeah, no, I haven't escalated anything to support at Heroku in quite some time, so I don't know if it's still like that. I hope it is, but I'm not really, not really sure. Building a platform team [00:23:55] Jeremy: Yeah, that, uh, that reminds me a little bit of, I think it's Rackspace? There's, there's, like, another hosting provider that was pretty popular before, and they... Used to be famous for that type of support, where like your, your app's having issues and somebody's actually, uh, SSHing into your box and trying to figure out like, okay, what's going on? which if, if that's happening, then I, I can totally see where the, the price is justified. But if the support is kind of like dropping off to where it's just, they don't do that kind of thing, then yeah, I can see why it's not so much of a, yeah, [00:24:27] David: We used to think of Heroku as like they were the platform team before we had our own platform team and they, they acted like it, which was great. [00:24:35] Jeremy: Yeah, I don't have, um, experience with, render, but I, I, I did, talk to someone from there, and it does seem like they're, they're trying to fill that role, um, so, yeah, hopefully, they and, and other companies, I guess like Vercel and things like that, um, they're, they're all trying to fill that space, [00:24:55] David: Yeah, cause, cause building our own internal platform, I mean it was the right thing to do, but it's, it's a, you can't just, you have to have a team on it, it's complicated, getting all the stuff in AWS to work the way you want it to work, to have it be kind of like Heroku, like it's not trivial. if I'm a one person company, I don't want to be messing around with that particularly. I want to just have it, you know, push it up and have it go and I'm willing to pay for that. So it seems logical that there would be competitors in that space. I'm glad there are. Hopefully that'll light a fire under, under everybody. [00:25:26] Jeremy: so in your case, it sounds like you moved to having your own platform team and stuff like that, uh, partly because of the compliance thing where you're like, we need our, we need to be isolated from the internet. We're going to go to AWS. If you didn't have that requirement, do you still think like that would have been the time to, to have your own platform team and manage that all yourself? [00:25:46] David: I don't know. We, we were thinking an issue that we were running into when we got bigger, um, was that, I mean, Heroku, it, It's obviously not as flexible as AWS, but it is still very flexible. And so we had a lot of internal documentation about this is how you use Heroku to do X, Y, and Z. This is how you set up a Stitch Fix app for Heroku. Like there was just the way that we wanted it to be used to sort of. Just make it all manageable. And so we were considering having a team spun up to sort of add some tooling around that to sort of make that a little bit easier for everybody. So I think there may have been something around there. I don't know if it would have been called a platform team. Maybe we call, we thought about calling it like developer happiness or because you got developer experience or something. We, we probably would have had something there, but. I do wonder how easy it would have been to fund that team with developers if we hadn't had these sort of business constraints around there. yeah, um, I don't know. You get to a certain size, you need some kind of manageability and consistency no matter what you're using underneath. So you've got to have, somebody has to own it to make sure that it's, that it's happening. [00:26:50] Jeremy: So even at your, your architect level, you still think it would have been a challenge to, to. Come to the executive team and go like, I need funding to build this team. [00:27:00] David: You know, certainly it's a challenge because everybody, you know, right? Nobody wants to put developers in anything, right? There are, there are a commodity and I mean, that is kind of the job of like, you know, the staff engineer or the architect at a company is you don't have, you don't have the power to put anybody on anything you, you have the power to Schedule a meeting with a VP or the CTO and they will listen to you. And that's basically, you've got to use that power to convince them of what you want done. And they're all reasonable people, but they're balancing 20 other priorities. So it would, I would have had to, it would have been a harder case to make that, Hey, I want to take three engineers. And have them write tooling to make Heroku easier to use. What? Heroku is not easy to use. Why aren't, you know, so you really, I would, it would be a little bit more of a stretch to walk them through it. I think a case could be made, but, definitely would take some more, more convincing than, than what was needed in our case. [00:27:53] Jeremy: Yeah. And I guess if you're able to contrast that with, you were saying, Oh, I need three people to help me make Heroku easier. Your actual platform team on AWS, I imagine was much larger, right? [00:28:03] David: Initially it was, there was, it was three people did the initial move over. And so by the time we went public, we'd been on this new system for, I don't know, six to nine months. I can't remember exactly. And so at that time the platform team was four or five people, and I, I mean, so percentage wise, right, the engineering team was maybe almost 200, 150, 200. So percentage wise, maybe a little small, I don't know. but it kind of gets back to the power of like the rails and the one person framework. Like everything we did was very much the same And so the Rails app that managed the deployment was very simple. The, the command line app, even the Go one with all of its verbosity was very, very simple. so it was pretty easy for that small team to manage. but, Yeah, so it was sort of like for redundancy, we probably needed more than three or four people because you know, somebody goes out sick or takes a vacation. That's a significant part of the team. But in terms of like just managing the complexity and building it and maintaining it, like it worked pretty well with, you know, four or five people. Where Rails fits in vs other technology [00:29:09] Jeremy: So during the Keynote today, they were talking about how companies like GitHub and Shopify and so on, they're, they're using Rails and they're, they're successful and they're fairly large. but I think the thing that was sort of unsaid was the fact that. These companies, while they use Rails, they use a lot of other, technology as well. And, and, and kind of increasing amounts as well. So, I wonder from your perspective, either from your experience at StitchFix or maybe going forward, what is the role that, that Ruby and Rails plays? Like, where does it make sense for that to be used versus like, Okay, we need to go and build something in Java or, you know, or Go, that sort of thing? [00:29:51] David: right. I mean, I think for like your standard database backed web app, it's obviously great. especially if your sort of mindset bought into server side rendering, it's going to be great at that. so like internal tools, like the customer service dashboard or... You know, something for like somebody who works at a company to use. Like, it's really great because you can go super fast. You're not going to be under a lot of performance constraints. So you kind of don't even have to think about it. Don't even have to solve it. You can, but you don't have to, where it wouldn't work, I guess, you know, if you have really strict performance. Requirements, you know, like a, a Go version of some API server is going to use like percentages of what, of what Rails would use. If that's meaningful, if what you're spending on memory or compute is, is meaningful, then, then yeah. That, that becomes worthy of consideration. I guess if you're, you know, if you're making a mobile app, you probably need to make a mobile app and use those platforms. I mean, I guess you can wrap a Rails app sort of, but you're still making, you still need to make a mobile app, that does something. yeah. And then, you know, interestingly, the data science part of Stitch Fix was not part of the engineering team. They were kind of a separate org. I think Ruby and Rails was probably the only thing they didn't use over there. Like all the ML stuff, everything is either Java or Scala or Python. They use all that stuff. And so, yeah, if you want to do AI and ML with Ruby, you, it's, it's hard cause there's just not a lot there. You really probably should use Python. It'll make your life easier. so yeah, those would be some of the considerations, I guess. [00:31:31] Jeremy: Yeah, so I guess in the case of, ML, Python, certainly, just because of the, the ecosystem, for maybe making a command line application, maybe Go, um, Go or Rust, perhaps, [00:31:44] David: Right. Cause you just get a single binary. Like the problem, I mean, I wrote this book on Ruby command line apps and the biggest problem is like, how do I get the Ruby VM to be anywhere so that it can then run my like awesome scripts? Like that's kind of a huge pain. (laughs) So [00:31:59] Jeremy: and then you said, like, if it's Very performance sensitive, which I am kind of curious in, in your experience with the companies you've worked at, when you're taking on a project like that, do you know up front where you're like, Oh, the CPU and memory usage is going to be a problem, or is it's like you build it and you're like, Oh, this isn't working. So now I know. [00:32:18] David: yeah, I mean, I, I don't have a ton of great experience there at Stitch Fix. The biggest expense the company had was the inventory. So like the, the cost of AWS was just de minimis compared to all that. So nobody ever came and said, Hey, you've got to like really save costs on, on that stuff. Cause it just didn't really matter. at the, the mental health startup I was at, it was too early. But again, the labor costs were just far, far exceeded the amount of money I was spending on, on, um, you know, compute and infrastructure and stuff like that. So, Not knowing anything, I would probably just sort of wait and see if it's a problem. But I suppose you always take into account, like, what am I actually building? And like, what does this business have to scale to, to make it worthwhile? And therefore you can kind of do a little bit of planning ahead there. But, I dunno, I think it would kind of have to depend. [00:33:07] Jeremy: There's a sort of, I guess you could call it a meme, where people say like, Oh, it's, it's not, it's not Rails that's slow, it's the, the database that's slow. And, uh, I wonder, is that, is that accurate in your experience, or, [00:33:20] David: I mean, most of the stuff that we had that was slow was the database, because like, it's really easy to write a crappy query in Rails if you're not, if you're not careful, and then it's really easy to design a database that doesn't have any indexes if you're not careful. Like, you, you kind of need to know that, But of course, those are easy to fix too, because you just add the index, especially if it's before the database gets too big where we're adding indexes is problematic. But, I think those are just easy performance mistakes to make. Uh, especially with Rails because you're not, I mean, a lot of the Rails developers at Citrix did not know SQL at all. I mean, they had to learn it eventually, but they didn't know it at all. So they're not even knowing that what they're writing could possibly be problematic. It's just, you're writing it the Rails way and it just kind of works. And at a small scale, it does. And it doesn't matter until, until one day it does. [00:34:06] Jeremy: And then in, in the context of, let's say, using ActiveRecord and instantiating the objects, or, uh, the time it takes to render templates, that kinds of things, to, at least in your experience, that wasn't such of an issue. [00:34:20] David: No, and it was always, I mean, whenever we looked at why something was slow, it was always the database and like, you know, you're iterating over some active records and then, and then, you know, you're going into there and you're just following this object graph. I've got a lot of the, a lot of the software at Stitch Fix was like internal stuff and it was visualizing complicated data out of the database. And so if you didn't think about it, you would just start dereferencing and following those relationships and you have this just massive view and like the HTML is fine. It's just that to render this div, you're. Digging into some active record super deep. and so, you know, that was usually the, the, the problems that we would see and they're usually easy enough to fix by making an index or. Sometimes you do some caching or something like that. and that solved most of the, most of the issues [00:35:09] Jeremy: The different ways people learn [00:35:09] Jeremy: so you're also the author of the book, Sustainable Web Development with Ruby on Rails. And when you talk to people about like how they learn things, a lot of them are going on YouTube, they're going on, uh, you know, looking for blogs and things like that. And so as an author, what do you think the role is of, of books now? Yeah, [00:35:29] David: I have thought about this a lot, because I, when I first got started, I'm pretty old, so books were all you had, really. Um, so they seem very normal and natural to me, but... does someone want to sit down and read a 400 page technical book? I don't know. so Dave Thomas who runs Pragmatic Bookshelf, he was on a podcast and was asked the same question and basically his answer, which is my answer, is like a long form book is where you can really lay out your thinking, really clarify what you mean, really take the time to develop sometimes nuanced, examples or nuanced takes on something that are Pretty hard to do in a short form video or in a blog post. Because the expectation is, you know, someone sends you an hour long YouTube video, you're probably not going to watch that. Two minute YouTube video is sure, but you can't, you can't get into so much, kind of nuanced detail. And so I thought that was, was right. And that was kind of my motivation for writing. I've got some thoughts. They're too detailed. It's, it's too much set up for a blog post. There's too much of a nuanced element to like, really get across. So I need to like, write more. And that means that someone's going to have to read more to kind of get to it. But hopefully it'll be, it'll be valuable. one of the sessions that we're doing later today is Ruby content creators, where it's going to be me and Noel Rappin and Dave Thomas representing the old school dudes that write books and probably a bunch of other people that do, you know, podcasts videos. It'd be interesting to see, I really want to know how do people learn stuff? Because if no one reads books to learn things, then there's not a lot of point in doing it. But if there is value, then, you know. It should be good and should be accessible to people. So, that's why I do it. But I definitely recognize maybe I'm too old and, uh, I'm not hip with the kids or, or whatever, whatever the case is. I don't know. [00:37:20] Jeremy: it's tricky because, I think it depends on where you are in the process of learning that thing. Because, let's say, you know a fair amount about the technology already. And you look at a book, in a lot of cases it's, it's sort of like taking you from nothing to something. And so you're like, well, maybe half of this isn't relevant to me, but then if I don't read it, then I'm probably missing a lot still. And so you're in this weird in be in between zone. Another thing is that a lot of times when people are trying to learn something, they have a specific problem. And, um, I guess with, with books, it's, you kind of don't know for sure if the thing you're looking for is going to be in the book. [00:38:13] David: I mean, so my, so my book, I would not say as a beginner, it's not a book to learn how to do Rails. It's like you already kind of know Rails and you want to like learn some comprehensive practices. That's what my book is for. And so sometimes people will ask me, I don't know Rails, should I get your book? And I'm like, no, you should not. but then you have the opposite thing where like the agile web development with Rails is like the beginner version. And some people are like, Oh, it's being updated for Rails 7. Should I get it? I'm like, probably not because How to go from zero to rails hasn't changed a lot in years. There's not that much that's going to be new. but, how do you know that, right? Hopefully the Table of Contents tells you. I mean, the first book I wrote with Pragmatic, they basically were like, The Table of Contents is the only thing the reader, potential reader is going to have to have any idea what's in the book. So, You need to write the table of contents with that in mind, which may not be how you'd write the subsections of a book, but since you know that it's going to serve these dual purposes of organizing the book, but also being promotional material that people can read, you've got to keep that in mind, because otherwise, how does anybody, like you said, how does anybody know what's, what's going to be in there? And they're not cheap, I mean, these books are 50 bucks sometimes, and That's a lot of money for people in the U. S. People outside the U. S. That's a ton of money. So you want to make sure that they know what they're getting and don't feel ripped off. [00:39:33] Jeremy: Yeah, I think the other challenge is, at least what I've heard, is that... When people see a video course, for whatever reason, they, they set, like, a higher value to it. They go, like, oh, this video course is, 200 dollars and it's, like, seems like a lot of money, but for some people it's, like, okay, I can do that. But then if you say, like, oh, this, this book I've been researching for five years, uh, I want to sell it for a hundred bucks, people are going to be, like no. No way., [00:40:00] David: Yeah. Right. A hundred bucks for a book. There's no way. That's a, that's a lot. Yeah. I mean, producing video, I've thought about doing video content, but it seems so labor intensive. Um, and it's kind of like, It's sort of like a performance. Like I was mentioning before we started that I used to play in bands and like, there's a lot to go into making an even mediocre performance. And so I feel like, you know, video content is the same way. So I get that it like, it does cost more to produce, but, are you getting more information out of it? I, that, I don't know, like maybe not, but who knows? I mean, people learn things in different ways. So, [00:40:35] Jeremy: It's just like this perception thing, I think. And, uh, I'm not sure why that is. Um, [00:40:40] David: Yeah, maybe it's newer, right? Maybe books feel older so they're easier to make and video seems newer. I mean, I don't know. I would love to talk to engineers who are like... young out of college, a few years into their career to see what their perception of this stuff is. Cause I mean, there was no, I mean, like I said, I read books cause that's all there was. There was no, no videos. You, you go to a conference and you read a book and that was, that was all you had. so I get it. It seems a whole video. It's fancier. It's newer. yeah, I don't know. I would love to hear a wide variety of takes on it to see what's actually the, the future, you know? [00:41:15] Jeremy: sure, yeah. I mean, I think it probably can't just be one or the other, right? Like, I think there are... Benefits of each way. Like, if you have the book, you can read it at your own pace without having to, like, scroll through the video, and you can easily copy and paste the, the code segments, [00:41:35] David: Search it. Go back and forth. [00:41:36] Jeremy: yeah, search it. So, I think there's a place for it, but yeah, I think it would be very interesting, like you said, to, to see, like, how are people learning, [00:41:45] David: Right. Right. Yeah. Well, it's the same with blogs and podcasts. Like I, a lot of podcasters I think used to be bloggers and they realized that like they can get out what they need by doing a podcast. And it's way easier because it's more conversational. You don't have to do a bunch of research. You don't have to do a bunch of editing. As long as you're semi coherent, you can just have a conversation with somebody and sort of get at some sort of thing that you want to talk about or have an opinion about. And. So you, you, you see a lot more podcasts and a lot less blogs out there because of that. So it's, that's kind of like the creators I think are kind of driving that a little bit. yeah. So I don't know. [00:42:22] Jeremy: Yeah, I mean, I can, I can say for myself, the thing about podcasts is that it's something that I can listen to while I'm doing something else. And so you sort of passively can hopefully pick something up out of that conversation, but... Like, I think it's maybe not so good at the details, right? Like, if you're talking code, you can talk about it over voice, but can you really visualize it? Yeah, yeah, yeah. I think if you sit down and you try to implement something somebody talked about, you're gonna be like, I don't know what's happening. [00:42:51] David: Yeah. [00:42:52] Jeremy: So, uh, so, so I think there's like these, these different roles I think almost for so like maybe you know the podcast is for you to Maybe get some ideas or get some familiarity with a thing and then when you're ready to go deeper You can go look at a blog post or read a book I think video kind of straddles those two where sometimes video is good if you want to just see, the general concept of a thing, and have somebody explain it to you, maybe do some visuals. that's really good. but then it can also be kind of detailed, where, especially like the people who stream their process, right, you can see them, Oh, let's, let's build this thing together. You can ask me questions, you can see how I think. I think that can be really powerful. at the same time, like you said, it can be hard to say, like, you know, I look at some of the streams and it's like, oh, this is a three hour stream and like, well, I mean, I'm interested. I'm interested, but yeah, it's hard enough for me to sit through a, uh, a three hour movie, [00:43:52] David: Well, then that, and that gets into like, I mean, we're, you know, we're at a conference and they, they're doing something a little, like, there are conference talks at this conference, but there's also like. sort of less defined activities that aren't a conference talk. And I think that could be a reaction to some of this too. It's like I could watch a conference talk on, on video. How different is that going to be than being there in person? maybe it's not that different. Maybe, maybe I don't need to like travel across the country to go. Do something that I could see on video. So there's gotta be something here that, that, that meets that need that I can't meet any other way. So it's all these different, like, I would like to think that's how it is, right? All this media all is a part to play and it's all going to kind of continue and thrive and it's not going to be like, Oh, remember books? Like maybe, but hopefully not. Hopefully it's like, like what you're saying. Like it's all kind of serving different purposes that all kind of work together. Yeah. [00:44:43] Jeremy: I hope that's the case, because, um, I don't want to have to scroll through too many videos. [00:44:48] David: Yeah. The video's not for me. Large Language Models [00:44:50] Jeremy: I, I like, I actually do find it helpful, like, like I said, for the high level thing, or just to see someone's thought process, but it's like, if you want to know a thing, and you have a short amount of time, maybe not the best, um, of course, now you have all the large language model stuff where you like, you feed the video in like, Hey, tell, tell, tell me, uh, what this video is about and give me the code snippets and all that stuff. I don't know how well it works, but it seems [00:45:14] David: It's gotta get better. Cause you go to a support site and they're like, here's how to fix your problem, and it's a video. And I'm like, can you just tell me? But I'd never thought about asking the AI to just look at the video and tell me. So yeah, it's not bad. [00:45:25] Jeremy: I think, that's probably where we're going. So it's, uh, it's a little weird to think about, but, [00:45:29] David: yeah, yeah. I was just updating, uh, you know, like I said, I try to keep the book updated when new versions of Rails come out, so I'm getting ready to update it for Rails 7. 1 and in Amazon's, Kindle Direct Publishing as their sort of backend for where you, you know, publish like a Kindle book and stuff, and so they added a new question, was AI used in the production of this thing or not? And if you answer yes, they want you to say how much, And I don't know what they're gonna do with that exactly, but I thought it was pretty interesting, cause I would be very disappointed to pay 50 for a book that the AI wrote, right? So it's good that they're asking that? Yeah. [00:46:02] Jeremy: I think the problem Amazon is facing is where people wholesale have the AI write the book, and the person either doesn't review it at all, or maybe looks at a little, a little bit. And, I mean, the, the large language model stuff is very impressive, but If you have it generate a technical book for you, it's not going to be good. [00:46:22] David: yeah. And I guess, cause cause like Amazon, I mean, think about like Amazon scale, like they're not looking at the book at all. Like I, I can go click a button and have my book available and no person's going to look at it. they might scan it or something maybe with looking for bad words. I don't know, but there's no curation process there. So I could, yeah. I could see where they could have that, that kind of problem. And like you as the, as the buyer, you don't necessarily, if you want to book on something really esoteric, there are a lot of topics I wish there was a book on that there isn't. And as someone generally want to put it on Amazon, I could see a lot of people buying it, not realizing what they're getting and feeling ripped off when it was not good. [00:47:00] Jeremy: Yeah, I mean, I, I don't know, if it's an issue with the, the technical stuff. It probably is. But I, I know they've definitely had problems where, fiction, they have people just generating hundreds, thousands of books, submitting them all, just flooding it. [00:47:13] David: Seeing what happens. [00:47:14] Jeremy: And, um, I think that's probably... That's probably the main reason why they ask you, cause they want you to say like, uh, yeah, you said it wasn't. And so now we can remove your book. [00:47:24] David: right. Right. Yeah. Yeah. [00:47:26] Jeremy: I mean, it's, it's not quite the same, but it's similar to, I don't know what Stack Overflow's policy is now, but, when the large language model stuff started getting big, they had a lot of people answering the questions that were just. Pasting the question into the model [00:47:41] David: Which because they got it from [00:47:42] Jeremy: and then [00:47:43] David: The Got model got it from Stack Overflow. [00:47:45] Jeremy: and then pasting the answer into Stack Overflow and the person is not checking it. Right. So it's like, could be right, could not be right. Um, cause, cause to me, it's like, if, if you generate it, if you generate the answer and the answer is right, and you checked it, I'm okay with that. [00:48:00] David: Yeah. Yeah. [00:48:01] Jeremy: but if you're just like, I, I need some karma, so I'm gonna, I'm gonna answer these questions with, with this bot, I mean, then maybe [00:48:08] David: I could have done that. You're not adding anything. Yeah, yeah. [00:48:11] Jeremy: it's gonna be a weird, weird world, I think. [00:48:12] David: Yeah, no kidding. No kidding. [00:48:15] Jeremy: that's a, a good place to end it on, but is there anything else you want to mention, [00:48:19] David: No, I think we covered it all just yeah, you could find me online. I'm Davetron5000 on Ruby. social Mastodon, I occasionally post on Twitter, but not that much anymore. So Mastodon's a place to go. [00:48:31] Jeremy: David, thank you so much [00:48:32] David: All right. Well, thanks for having me.

What you'll learn in this episode:   Which essential jewelry books you should have in your library Why books are so much more reliable than internet research when it comes to gemstones and jewelry Why the Renaissance opened up a new world of adornment An overview of the periods of jewelry and how they overlapped and influenced one another How cultural turning points, like World War II and the South African diamond rush, influenced what materials were used during different time periods   About Jo Ellen Cole Jo Ellen Cole is the owner of Cole Appraisal Services and the director of fine jewelry at Abell Auctions. She earned her Graduate Gemologist Diploma at the Gemological Institute of America in Santa Monica and successfully passed the prestigious Gemological Association of Great Britain's FGA examinations.   Additional resources: LinkedIn Gemological and Jewelry Books for a Professional Library:   GEMOLOGICAL IDENTIFICATION BOOKS Gemstones: Their Sources, Descriptions and Identification, Webster, Robert Gem Testing, Anderson, Basil Handbook of Gemstone Identification, Liddicoat Jr., Richard T. Gem and Ornamental Materials of Organic Origin, Pedersen, Maggie Campbell Gemstones of the World, Schumann, Walter Photoatlas of Inclusions in Gemstones, Vols. 1, 2 and 3, Gubelin, Edward and Koivula, John Color Encyclopedia of Gemstones, Arem, Joel The Spectroscope and Gemmology, Anderson, Basil and Payne, James, edited by Mitchell, R. Keith   GENERAL REFERENCE Gemology, An Annotated Bibliography, Sinkankas, John The Complete Handbook for Gemstone Weight Estimation, Carmona, Charles Dictionary of Gems and Gemology, Shipley, Robert The Jewelers Manual, Liddicoat Jr., Richard T. and Copeland, Lawrence L. Gemstone and Mineral Data Book, Sinkankas, John     DIAMONDS Diamonds, Bruton, Eric Diamond Cutting: Complete Guide to Cutting Diamonds, Watermeyer, Basil Famous Diamonds, Balfour, Ian Hardness 10, Vleeschdrager, Eddy Diamond Handbook, Newman, Renee Laboratory Grown Diamonds, Simic, Dusan and Deljanin, Branko Fluorescence as a Tool for Diamond Origin Identification – A Guide, Chapman, John, Deljanin, Branko and Spyromilios, George PEARLS Book of the Pearl, Kunz, George F. and Stevenson, Charles Hugh Pearls, Strack, Elizabeth Beyond Price, Donkin, R.A.   JADE Jade, A Gemmologist's Guide, Hughes, Richard Jade For You, Ng, John Y. and Root, Edmund   COLORED STONES Ruby and Sapphire, Hughes, Richard Emerald and Other Beryls, Sinkankas, John Opal Identification and Value, Downing, Paul   JEWELRY HISTORY Brilliant Effects, Pointon, Marcia Understanding Jewelry, Bennett, David, and Mascetti, Daniella Jewelry in America, Fales, Margha Gandy Victorian Jewellery, Flowers, Margaret Transcript: In appraiser Jo Ellen Cole's opinion, the best thing a jewelry lover can have is a well-stocked library. Information on gems and jewelry abounds online today, but much of that information is incorrect. For that reason, Jo Ellen—a Graduate Gemologist who also passed Gem-A's FGA examination—turns to books when she has a question about a specific piece, hallmark or stone. She joined the Jewelry Journey Podcast to share which books she recommends for every jewelry interest; how jewelry trends shifted over the years due to cultural forces; and how to quickly identify the characteristics of different jewelry periods. Read the episode transcript here.  

God has a certain covering that is required of His people - one that was used both in the Tabernacle and in the covering of the nakedness of Adam and Eve. It is clear that man's idea of being covered is not equivalent to being covered in God's sight. Our bodies should be modestly covered so that the attention of others can be drawn to what is within us, not without. 11/16/2023 - Thursday NightScriptures Used (In Order of Occurrence):Numbers 9:15Isaiah 4:1Genesis 2:25Genesis 3:7, 10, 21Exodus 28:42Exodus 20:26Isaiah 47:2-3I Timothy 2:9John 21:7Revelation 2:20II Kings 9:30Proverbs 6:25Jeremiah 4:30Ezekiel 23:40-41Jude 1:8I Corinthians 6:19-20I Corinthians 3:16

AEW Full Gear takes place this Saturday, November 18th live at the KIA Forum in Los Angeles! CEO, GM and Head of Creative, Tony Khan, returns to break down the biggest matches on what is sure to be a history-making card. MJF faces off against Switchblade Jay White for the AEW World Championship after he defends the ROH Tag Team Title against The Gunns during Zero Hour (FREE for everyone to watch on YouTube). Hikaru Shida defends the AEW Women's World Championship against Timeless Toni Storm. Ricky Starks and Big Bill battle in a 4 Way against LFI, FTR, and The Kings of The Black Throne (Malakai Black & Brody King) for the AEW World Tag Team Title. Kris Statlander takes on Julia Hart and Skye Blue in defense of the TBS Championship, Orange Cassidy squares off against Jon Moxley for a second time over the AEW International Championship, and Swerve Strickland and Hangman Adam Page look to settle the score in a Texas Deathmatch. Plus, former tag partners Christian Cage and Adam Copeland find themselves in opposite corners of the ring as Cage's The Patriarchy (Luchasaurus & Nick Wayne) go up against Copeland, Darby Allin and Sting!See omnystudio.com/listener for privacy information.

  «Por tanto sean imitadores de Dios [cópienle y sigan Su ejemplo] como hijos amados [imiten a su Padre]» (Efesios 5:1, AMP) Crear cosas nuevas y cambiar aquellas cosas que son viejas. Debido a que tú y yo fuimos creados a la imagen de Dios, siempre estamos tratando de hacerlo. Pero si queremos tener éxito en ese ámbito, necesitamos aprender cómo es que lo hace nuestro Creador, nuestro propio Padre celestial. No fue por accidente que Dios se puso a crear cosas. Él no dijo: “Vaya, qué casualidad: ¡apareció la luz!”. Él primero vio el resultado de lo que quería hacer (primero concibió la imagen interna o la idea de lo que quería crear) y luego dijo: «Sea la luz», y fue la luz. Si vamos a imitarlo, tendremos que poner en práctica el principio de primero concebir la imagen interna de lo que queremos hacer. Quizás digas: “Pero, hermano Copeland, usted está hablando de Dios. Seguramente no espera que yo trate de ser como Él”. Por supuesto que lo espero. ¡Efesios 5:1 nos lo confirma! Sin embargo, déjame darte un consejo. No pierdas el tiempo tratando de concebir una imagen interna positiva por tu propia cuenta, porque eso no será nada más que pensar positivo, y aunque pensar de esa manera es ciertamente mejor que pensar lo opuesto (o no pensar en nada), eventualmente se desplomará. Si eres un hijo nacido de nuevo del Dios todopoderoso, Él te ha dado las bases y el poder para hacer cambios permanentes en tu vida y en tus circunstancias. Piensa una vez más en la creación. Dios quería que hubiera luz. Entonces, dijo: «Sea la luz». Las palabras que Él declaró estaban directamente relacionadas con Su imagen interna. Dios usó Sus palabras para convertir esa imagen interna en una realidad externa. La base que debes utilizar para formar tu imagen interna y las palabras que declaras es La Palabra de Dios. Ésta tiene poder sobrenatural. Si te llenas de esa Palabra de fe y la declaras, ella te dará los resultados deseados en tu vida y en tus circunstancias, así como le dio resultados a tu Padre celestial. Descubre lo que es la verdadera creatividad. Profundiza en la Palabra de Dios y empieza a reconstruir tu mundo. Lectura bíblica: 2 Corintios 4:6-13   © 1997 – 2019 Eagle Mountain International Church Inc., también conocida como Ministerios Kenneth Copeland / Kenneth Copeland Ministries. Todos los derechos reservados.

SGTW presents the media conference call with AEW CEO & GM Tony Khan ahead of Saturday's AEW Full Gear in Los Angeles. Plus Stew gives his thoughts.This show is part of the Spreaker Prime Network, if you are interested in advertising on this podcast, contact us at https://www.spreaker.com/show/3226782/advertisement

This week's edition of Copeland's Corner, with featured Headliners Ngaio Bealum, Chris Riggins & Tom Sawyer. Tune in they chime in with Brian discuss this week's hot talk topics. Follow Ngaio on Instagram: @Ngaio420Follow Chris on Instagram: @ChrisRigginsComedyCheck out more from Tom Sawyer on his website: TomSawyerVoices.com--For more from Brian...Visit his website: www.BrianCopeland.comFollow on Social Media:  Twitter & Instagram - @BrianCopieEmail: BrianCopelandShow@Gmail.com--Copeland's Corner is Created, Hosted, & Executive Produced by Brian Copeland. This Show is Recorded & Mixed by Charlene Goto with Go-To Productions. Visit Go-To Productions for all your  Podcast & Media needs.

See omnystudio.com/listener for privacy information.

What you'll learn in this episode:   Which essential jewelry books you should have in your library Why books are so much more reliable than internet research when it comes to gemstones and jewelry Why the Renaissance opened up a new world of adornment An overview of the periods of jewelry and how they overlapped and influenced one another How cultural turning points, like World War II and the South African diamond rush, influenced what materials were used during different time periods   About Jo Ellen Cole Jo Ellen Cole is the owner of Cole Appraisal Services and the director of fine jewelry at Abell Auctions. She earned her Graduate Gemologist Diploma at the Gemological Institute of America in Santa Monica and successfully passed the prestigious Gemological Association of Great Britain's FGA examinations.   Additional resources: LinkedIn Gemological and Jewelry Books for a Professional Library:   GEMOLOGICAL IDENTIFICATION BOOKS Gemstones: Their Sources, Descriptions and Identification, Webster, Robert Gem Testing, Anderson, Basil Handbook of Gemstone Identification, Liddicoat Jr., Richard T. Gem and Ornamental Materials of Organic Origin, Pedersen, Maggie Campbell Gemstones of the World, Schumann, Walter Photoatlas of Inclusions in Gemstones, Vols. 1, 2 and 3, Gubelin, Edward and Koivula, John Color Encyclopedia of Gemstones, Arem, Joel The Spectroscope and Gemmology, Anderson, Basil and Payne, James, edited by Mitchell, R. Keith   GENERAL REFERENCE Gemology, An Annotated Bibliography, Sinkankas, John The Complete Handbook for Gemstone Weight Estimation, Carmona, Charles Dictionary of Gems and Gemology, Shipley, Robert The Jewelers Manual, Liddicoat Jr., Richard T. and Copeland, Lawrence L. Gemstone and Mineral Data Book, Sinkankas, John     DIAMONDS Diamonds, Bruton, Eric Diamond Cutting: Complete Guide to Cutting Diamonds, Watermeyer, Basil Famous Diamonds, Balfour, Ian Hardness 10, Vleeschdrager, Eddy Diamond Handbook, Newman, Renee Laboratory Grown Diamonds, Simic, Dusan and Deljanin, Branko Fluorescence as a Tool for Diamond Origin Identification – A Guide, Chapman, John, Deljanin, Branko and Spyromilios, George PEARLS Book of the Pearl, Kunz, George F. and Stevenson, Charles Hugh Pearls, Strack, Elizabeth Beyond Price, Donkin, R.A.   JADE Jade, A Gemmologist's Guide, Hughes, Richard Jade For You, Ng, John Y. and Root, Edmund   COLORED STONES Ruby and Sapphire, Hughes, Richard Emerald and Other Beryls, Sinkankas, John Opal Identification and Value, Downing, Paul   JEWELRY HISTORY Brilliant Effects, Pointon, Marcia Understanding Jewelry, Bennett, David, and Mascetti, Daniella Jewelry in America, Fales, Margha Gandy Victorian Jewellery, Flowers, Margaret Transcript: In appraiser Jo Ellen Cole's opinion, the best thing a jewelry lover can have is a well-stocked library. Information on gems and jewelry abounds online today, but much of that information is incorrect. For that reason, Jo Ellen—a Graduate Gemologist who also passed Gem-A's FGA examination—turns to books when she has a question about a specific piece, hallmark or stone. She joined the Jewelry Journey Podcast to share which books she recommends for every jewelry interest; how jewelry trends shifted over the years due to cultural forces; and how to quickly identify the characteristics of different jewelry periods. Read the episode transcript here.   Sharon: Hello, everyone. Welcome to the Jewelry Journey Podcast. This is the first part of a two-part episode. Please make sure you subscribe so you can hear part two as soon as it's released later this week.   I met Jo Ellen about six or seven years ago when I was studying for the GG, or the Graduate Gemology degree. In order to pass it, I needed to identify about 18 stones and get them all right, and I only had three chances to do that. This was daunting to me because I'm not a science person; I'm not a math person or anything. I wasn't working with the stones. I wasn't working in a jewelry store, so I really didn't have the opportunity to handle the stones. I called another appraiser, Charlie Carmona, whom we've had on this podcast, and asked him for a recommendation for a tutor. I thought it was a pretty weird recommendation that I was asking for, but he immediately recommended Jo Ellen, and I never looked back. She's been a great tutor. It was a few years ago, but she helped me a lot.   She knows a lot about jewelry, and not just jewelry, but I find her extremely knowledgeable about vintage and antique pieces. I have talked to and been to enough appraisers to know that this is its own specialty. She's also been helpful when it comes to directing me to researchers for whatever I need. She pointed me in the right direction. Today, she's going to share with us the books that she thinks will help us with our jewelry journey. Jo Ellen, welcome to the program.   Jo Ellen: Thank you so much for having me. I'm happy to be here.   Sharon: I'm so glad that you deigned to be on. Now, tell us, with a GG, which is part of the GIA, you can do a lot of things. So, why did you go into appraisal as opposed to other things?   Jo Ellen: Well, I found that I was lacking in salesmanship abilities, to say the least. I'm just not a salesperson, but I love to categorize; I love to research. Appraising seemed to fit that bill very well. Plus, when I realized that I was not good at sales, I met Charles Carmona, whom you mentioned before, at American Society of Appraisers—no, it was the AGA. I can't remember what that stands for, but it was a meeting. I met him, and a couple of years later, he asked me to work with him and I jumped on it. It was a wonderful experience. He's still my mentor. He's so knowledgeable and knows so much about appraising. I always feel comfortable talking to him about any problem I might encounter. He's been very instrumental.   Sharon: And a big name in the L.A. market, I would say.   Jo Ellen: He's really gone worldwide. He has three laboratories in China and Thailand as well.   Sharon: I didn't realize that.   Jo Ellen: Yeah, he's really opened up his market. He also leads a lot of traveling groups and things. He's very well-known.   Sharon: I knew he was well-known in Los Angeles, but I didn't know he was that well-known around the world.   Jo Ellen: Having factories in Africa, he's been around doing a lot of different things.   Sharon: I've stopped purchasing books when it comes to novels or something like that. I just listen to them. Why should I purchase a book as opposed to listening online when it comes to jewelry? Why should I purchase a jewelry book?   Jo Ellen: What I've noticed is that when I go online to research prices of jewelry, which I do often, I find that a lot of the information I find is not correct. I think part of the reason for that is because it's so easy to list something online. It gets your name out there, so people do that. However, they don't always double check their information. There's a lot of misinformation out there.   Whereas in a book, it takes a lot longer to set it up, edit it, make sure everything's proper. I've been able to count on the information coming from books a lot better than I have been from online sources. However, I must say there is certainly a good reason to look online as well. Some of the information is very good. It's just that, personally, I feel more comfortable with a book form. Then, you can revisit that if you need to. It's easier to find.   Sharon: Do you have to know if it's right or wrong before you look at a book?   Jo Ellen: You have to figure that out on your own. But generally, if you have a good background in terms of knowledge of gems and gemology and antique jewelry from reading through books, a lot of times, you'll find that information is incorrect when you go online.   Sharon: I know instances where I've found incorrect information about pearls or something like that. I wouldn't say I'm any kind of expert, but I know it's incorrect.   Jo Ellen: Yeah.   Sharon: Can you tell us quickly what you do every day? What does an appraiser do every day?   Jo Ellen: If I'm not reviewing a book for a gemological publication like The Gemologist or Gems & Gemology, which doesn't do book reviews anymore—but a lot of times, I'm asked by people in the industry to review new books. So, I do that a lot, which involves going over the book line by line and figuring out what I think is proper and what isn't, or what is clear and what is not. I do that a lot.   I also work at a local auctioneer two days a week, at Abell Auctions, as their fine jewelry director. I'm constantly cataloguing things and looking for prices on things, always encountering something unusual there. You get things from all over the world, and people like to use that venue as a way to sell their items. If I'm not doing that, I'm actually going to people's localities to appraise their jewelry for them, either for insurance purposes or for estate purposes if somebody has passed or wants to set up a trust. I do that a lot, but a lot of my days are spent doing what I love, which is reading.   Sharon: You sound pretty conscientious to look at a book that closely when you're writing a book review.   Jo Ellen: For me, it's really important to get it right. Generally, most books, even if I don't particularly like them, I can at least validate that their information is correct. I did have one book about a year-and-a-half ago that was just so egregious in its information I had to give it a bad review, which I've never done before. I called up the editor the week before it was due and said, “Why are you even covering this book? It's so awful.” He asked why, and I started pointing out little things. He was like, “Oh,” but he published the review anyhow. I didn't feel great about it because I don't like to slam people for things, but it was just so awful I had to point it out.   Sharon: So, we should do our own reading, both online and with books.   Jo Ellen: Absolutely.   Sharon: Let's talk about a book or books and talk about the history. If you want to learn about the history of jewelry through the ages, what would you look at?   Jo Ellen: There are a couple of really good books. When you write a book, it seems like the best formula is always to start at the beginning and take them through the ages. That's what they do with jewelry history. Usually, they'll start with prehistoric jewelry and how jewelry first came to be—it's one of the oldest things that humans have done that marks them as humans—and then it goes through medieval times and Renaissance, and then to Georgian and Victorian and Arts and Crafts or the Aesthetic Period, and then through Art Nouveau and Art Deco and Retro and on up to modern jewelry for today. That's usually how a book on jewelry history is set up. There are couple of really good ones out there that encapsulate what you need to know in terms of jewelry history.   Sharon: Before you tell us that, I wanted to tell our listeners that we will have all this information on the website. Yes, take notes, but you don't have to write everything down; it'll be on our website.   Jo Ellen: Yeah, I created a list of things that you can look for. One of the main books I recommend for overall jewelry history is a book called “Understanding Jewelry.” It's by David Bennett and Daniela Mascetti, who were both cataloguers at Sotheby's for many years and very knowledgeable in their field. It really helps to set up all those different ages of jewelry and gives wonderful examples and photographs. It's a picture book as well as an informative book, but all the information they offer has always been spot-on. I've learned so much from that book. It's one that I would definitely recommend.   Sharon: I've probably seen it in every jewelry office that has books. I see that book.   Jo Ellen: It's a great book. It really is. Another good one that's much simpler and has more pictures is a book called “Warman's Jewelry.”   Sharon: Warman's?   Jo Ellen: Yeah, W-A-R-M-A-N. The second edition was actually written by a good friend of mine, Christie Romero, who has since passed on. She used to be on the Antiques Roadshow. You'd see her on Antiques Roadshow a lot, a very knowledgeable woman. She had started her journey by traveling down to Mexico and learning all about Mexican silver and then just expanded from there. She used to give classes on jewelry at Valley College in Los Angeles. She just knew how to present things in such a way that it was very easy to assimilate that information.   It has tons and tons of pictures. It also has a jewelry timeline. It's very thorough for being such an easily read book. There are even some prices in there, I think. It's now an older book, and I think there have been other editions that have been written since hers, but I always liked hers because I'm familiar with it. So, that's another good one that I would offer.   Sharon: What about a book if we want to be more specific, like Georgian or Victorian jewelry? It's funny that when you say prehistoric, you could take many of the prehistoric pieces and wear them today and nobody would know the difference. But it seems to jump then to Renaissance.   Jo Ellen: Because it has to do with the Dark Ages. A lot of it is about human history and civilization. During the Dark Ages, people were in such terrible shape as a civilization, they didn't have time to decorate themselves, so they usually used items from the past. There wasn't a lot of information coming out between, let's say, the 5th and 13th centuries. Then things started rolling again once society got more stabilized.   Sharon: Is there a particular book we should look at if we want to pick up where society picked up? Let's say Georgian.   Jo Ellen: There's a really good book on jewels of the Renaissance by Yvonne Hackenbroch. It's quite a tome. It's big, and it goes through the history of civilization as well as jewelry. It talks about the light occurring in the beginning of the Renaissance, when people started realizing there's more to life than just eating and sleeping and staying alive. You can decorate yourself. You can show your social status by what you wear, some of it being jewelry. That's a very good book for the Renaissance period.   There's also another Renaissance book called “Renaissance Jewels and Jeweled Objects: From the Melvin Gutman Collection” by Parker Lesley. It shows wonderful examples of Renaissance-oriented jewelry. There's one called the Hope Pearl Jewel. It's this big, baroque pearl that's decorated as the body of a man. It's very well known. It demonstrates jewels like that.   Sharon: From there, does it continue to Georgian and Victorian?   Jo Ellen: Yeah, there's a really good book, “Georgian Jewelry 1714-1830,” by Ginny Redington and Tom Dawes with Olivia Collings. It's great because I had never seen a book specifically on Georgian jewelry. It's not glamorous jewelry because the techniques weren't there. It's just that people wanted to adorn themselves to help their social status. It's very collectable today. People collect Georgian jewelry all the time. It goes through the period before Queen Victoria took the throne and clarifies a lot of things. And, again, the information is spot-on. I've never had a problem with these books. When I go to confirm that information, I've never had a problem with it.   Sharon: I don't collect Georgian jewelry, but I do know it's very hard to find.   Jo Ellen: Yeah, it is, but it shows up at different auctions, sometimes in the most unusual places. Even at Abell Auctions you'll see it. People just hold onto these things. A lot of Georgian jewelry isn't available anymore because people would melt down those items to make new items in a newer fashion, such as a Victorian fashion. They would take the stones out, melt down the metals and then either recast them or remake them in some way into a newer-looking form. That's why you don't see a lot of Georgian jewelry anymore.   Sharon: How about Victorian jewelry? There seems to be a lot of it.   Jo Ellen: There's a lot of Victorian jewelry. Even though people also did it then, where they would melt things down and make a new piece out of older pieces, there is a lot of Victorian jewelry because Queen Victoria, whom that period is named after, wore a lot of jewelry. She was a big jewelry person. She loved jewelry and she used it for sentimental reasons to give imagery, to bestow favor on people. So, there's a lot of it around because people would want to copy her. Everybody started doing that. You'll have mourning jewelry from Victorian times.   A lot of historical things happened during her reign, such as the finding of diamonds in South Africa, which changed the diamond market forever. Before then, there were diamonds from Brazil, primarily, or India, but they're very hard to come by and very, very expensive. Once they opened up the diamond fields in South Africa, you started getting a lot more diamond jewelry.   Sharon: By mourning, you mean if somebody dies?   Jo Ellen: Yeah. A lot of times, when someone would die, they would leave a certain amount of money in their will to make mourning rings or pendants for their friends and family to remember them by. So, you have this memento mori-type jewelry which has its own collecting base. People collect their little pendants, which are like little baskets with a little enamel skeleton inside, little rings that say the man or woman's name written around the inside of the band, all sorts of things like that. It's kind of sweet because, when you think about it, jewelry is one of the few art forms that's worn close to the body. It makes it more sentimental.   Sharon: And the diamonds from South Africa, were they different than the other diamonds, besides being less expensive?   Jo Ellen: The thing with Brazilian diamonds in particular is that they had what they call a lot of knots in them, where their crystals grow into crystals. You would have these harder-to-polish areas. With African diamonds, it's such a pure form that they're easier to polish. They didn't take as much time to polish, and they didn't break on the wheel the way that some of the Brazilian diamonds would break.   Sharon: They used those diamonds in Victorian jewelry?   Jo Ellen: They did.   Sharon: What books should we look at if we want to learn about Victorian jewelry?   Jo Ellen: There is a wonderful book—in fact, I used to know an antique dealer that used to give out these books to his clients because they were wonderfully organized. There's a book called “Victorian Jewelry” by Margaret Flower, and it goes through the different phases of Victorian jewelry. There's an early, a mid and a late phase. What she does is describe exactly what you can see during each of the phases, what types of jewelry. It's very interesting, and it gives you an overall picture of how things came to be during that time period. It's really nicely done.   There's a much larger book I'm still reading because it's so big. It's called “Jewelry in the Age of Queen Victoria” by Charlotte Gere and Judy Rudoe. That also has a lot of very specific information on different types of jewelry, the makers during that time. What's interesting is you'll see the same authors over and over again because these people really use it. It's their way to express themselves as a lifestyle, almost. They're wonderful authors, and they do their research and know what they're talking about. So, those are two Victorian jewelry books I would highly recommend. I think they're wonderfully done.   Then, if you want to go into French jewelry, there's another book called “French Jewelry of the Nineteenth Century” by Henri Vever. It's an enormously fat book. I'm still reading that one as well, but again, it's jewelry makers. It's huge. It gives makers' information and techniques, and it's beautifully done. That's a good book to have as well.   Sharon: First of all, it strikes me that you seem to look at the pictures a lot more. You read. Most people don't read any of the book. They look at the pictures. That's different.   Jo Ellen: They have pictures with jewelry; that's sure to entice you to continue looking.   Sharon: Then what do you go into? Edwardian and Art Nouveau?   Jo Ellen: Before that, there's actually a period called the Aesthetic Period, which is also covered in the “Jewelry in the Age of Queen Victoria” book. It was in the late 1870s through the 1900s. There were certain makers that specialized in it, like Child & Child of London. They would make these beautiful pieces that harkened back to classical times but using new techniques and materials. That was a specific period. It was a very small period, but all the jewelry that was done during that time is beautifully done. There's a book by Geoffrey Munn called “Castellani and Giuliano,” and it talks about that specific time period. For example, Castellani was known for taking antique or ancient jewelry and refiguring it for that time period around the 1900s.   Sharon: He was a goldsmith?   Jo Ellen: He was a goldsmith. It was actually two brothers who were goldsmiths. One of the brothers was very politically active and lost an arm when they were demonstrating or something. He got put in jail, but the other brother kept on, and then their children took over after them. In Giuliano's case, which was another manufacturer in Rome, he was known for his enamels. You will see jewelry specifically with black and white enamel accenting other colored enamels. The work is beautifully done, and it's very detailed.   Sharon: We may be going back a few years. What was Berlin iron, and when was that popular?   Jo Ellen: Berlin ironwork, I believe, was like 1840 through 1860. It was a result of people giving up their precious metals for the Prussian Wars that were happening at that time. They would make this Berlin ironwork, which is very delicate and lacey, but it was made out of iron because they didn't want to use precious metals for that; they wanted to use it for warfare. So, they would use ironwork as a substitute for precious metals. There are some beautifully intricate bracelets and necklaces. It looks like lace. It's really beautiful.   Sharon: Is it wearable?   Jo Ellen: It is wearable. It's kind of a Gothic look, so it's a heavier look. I don't know if you'd want to wear it every day because, again, it's kind of—I hate to say gloomy, but it is kind of a sober look because it's black and the tracery is so fine. But it's certainly wearable.   Sharon: After the Aesthetic Period, we have Edwardian and Art Deco. What do we have?   Jo Ellen: What we start with is Arts and Crafts, which is actually my favorite period. I have a lot of books on it, but there are a couple that were really good in terms of pushing forward the information I knew. One is a book called “Jewelry and Metalwork in the Arts and Crafts Tradition” by Elyse Zorn Karlin, who's a very active member of the jewelry industry. She gives lectures. It's this wonderful book on Arts and Crafts jewelry and metalwork and leads you through the making of it with the guilds.   They tried to restart jewelry guilds in England where everything was made from first to last by the same person. The metal would be drawn and shaped by the person. If enamels were used, they would make the enamels themselves and apply them themselves. The stone setting was done by the same person. That was the beginning of Arts and Crafts, the person making the piece from beginning to end. Usually they're not terribly intricate, but they're beautifully fashioned with a lot of feeling. It's a very comfortable look, and it's infinitely wearable. The first part of Arts and Crafts started around 1883 through 1900. Then there was a repeat of it between around 1920 and 1935, around the same time as Art Deco.   What I forgot to mention during the Aesthetic Period was Carl Fabergé from Russia. He did a lot of Aesthetic pieces.   Sharon: He did the eggs, right?   Jo Ellen: He did the eggs for the Russian monarchy, but he also did jewelry for everyday people. He would make little, miniature enameled eggs for the general Russian population. Those still come up today once in a while. I saw an entire necklace of Fabergé eggs, all in different enamel colors beautifully done. Everything is so beautifully fashioned. You can tell they really took time in every single aspect of the making of that jewel. That's what I love about it. It shows so much attention to detail.   Sharon: We will have photos posted on the website. Please head to the JewelryJourney.com to check them out.    

If you are passionate about your skilled trades service business but struggle to see it grow, or if you're simply curious about running a successful service enterprise, this episode of the Service Business Mastery Podcast is for you! In this episode, "Accounting Doesn't Have to Suck," hosts Tersh Blisset and Joshua Crouch engage with guest Spencer Sheinin, CEO and Founder of Shift Financial Insights, in a deep dive into the world of accounting, and how as daunting as it may appear, it doesn't have to suck! They explore hiring problems often faced by small and medium-sized businesses and how hiring the wrong person for accounting can result in lost opportunities. They discuss the role of AI in bookkeeping, financial analysis, and how it may not necessarily be the ideal option for smaller businesses with unique scenarios.  Tersh, Josh, and Spencer inspire others with their personal stories of business finance, including Spencer's transformative shift in mindset towards numbers. If you've ever been overwhelmed by financial statements, Spencer's take on using data visualization techniques for better understanding and data interpretation is a game-changer. Also, make sure to look out for the invaluable advice from Sheinin's book, "Entreprenumbers," of which we are giving away copies after the interview. It's an absolute must-read for entrepreneurs looking to demystify their financials and gain the knowledge to make effective business decisions.  This episode is full of insights, practical advice, and money-saving tips for anyone in a service business. Don't miss out! SHOW NOTES 01:59 Justin hosts giveaway and offers script for success. 04:11 Copeland offers valuable compressor diagnostics training. 08:58 Struggling to keep up, correcting formulas, light bulb moment. 12:20 Not a certified accountant. HVAC career started accidentally. 14:14 Accounting department struggles due to inadequate staffing. 17:15 Financials are backwards looking, but budgets and cash flows can be forward looking. Looking backwards helps identify what's not working and the root causes. The 80 20 rule applies to most problems. Understanding the right information helps identify issues like a 3% decrease in average margin. 20:14 AI accounting benefits big companies, not small. 24:16 Increase sales, decrease costs, analyze divisions. 26:01 Forward vs. backward analysis in HVAC operations. 30:46 Managing labor is crucial in every industry, particularly this industry. Analyzing labor as a percentage of sales can indicate if it's going in the wrong direction. Our brains process information visually, so financial information should be presented in pictures instead of letters and numbers. For example, when determining the current percentage of receivables, the accounts receivable aging report is commonly used. 34:27 Book version of tips/tools for implementation. 36:38 Great ideas shared with like-minded business coaches. 39:22 Impressive intro video. Tersh's amazing shoes. Resources And People Mentioned: Connect With Spencer on LinkedIn Here! Or check out his book's website via entreprenumbers.com.  This episode is kindly sponsored by: - Sera (visit their website) - UpFrog (visit their website) - Copeland (visit their website). - CompanyCam (visit their website) Visit www.companycam.com/SBM and use code SBM for a free 2-week trial, 1:1 training and account setup, and 50% off your first two months! - Interplay Learning (visit their website) - Join the Service Business Mastery Facebook group Affiliate Links: - Castmagic - https://get.castmagic.io/SBM  - StreamYard - https://streamyard.com/pal/c/4524595769507840 - CallRail - https://partners.callrail.com/relentless-digital  - IfTTT- 10 Percent off!  - https://ifttt.com/join?referral_code=BoERPHYVbCFE-C7okWNiClo3ygLafRze

How did Digital Entrepreneur Courtney Copeland invest in herself to be able to run Trauma Tree House? Well, that's what your Podcast Mogul Phil Better is here to do. Join Phil as he asks about I'd love to open a healing center where entrepreneurs come for an immersive experience that includes multiple treatment modalities for total healing and better coping strategies for when things may not go as planned and how Brand awareness is currently something they are dealing with in their business! We also discuss why Get Paid for What You Know by Graham Cochrane is a book they recommend for Entrepreneurs to Read. Make sure to listen until the end for a special treat! Remember to Invest In Yourself Team Invest In Yourself

The decisions that each of us make during our time on this earth will determine where we spend our eternity. The Word tells us in Acts that Judas Iscariot went to his own place - the place to which his own actions led him. Therefore, there is a responsibility in the life of each individual to make their eternal destiny certain by choosing to follow after the commandments of God.  11/12/2023 - Sunday MorningScriptures Used (In Order of Occurrence):Acts 1:16-25I Samuel 9:21Revelation 22:11Isaiah 55:6-7 

PWTorch editor Wade Keller is joined by PWTorch's Greg Parks to discuss AEW Collision live caller and email interaction along with an on-site correspondent who attended the taping in Oakland on Friday night. They opened with a discussion on the Tony Khan announcement about the Continental Classic 12-man round-robin tournament. They went on to discuss the rest of the show from the commentary to Kris Statlander to Rush to Danny Garcia.This show is part of the Spreaker Prime Network, if you are interested in advertising on this podcast, contact us at https://www.spreaker.com/show/3275545/advertisement