POPULARITY
Hosted by David Farley
4 episodes with David Farley
2 episodes with David Farley
3 episodes with David Farley
3 episodes with David Farley
2 episodes with David Farley
2 episodes with David Farley
It's the return of a special video podcast series: Food Writers Talking About Food Writing. It's available on the TASTE YouTube channel, so make sure to subscribe and check out the video version of this podcast. Every couple of weeks, cohost Matt Rodbard invites a journalist to talk about some favorite recent food writing as well as their thoughts on the industry as a whole. On today's episode we have an amazing conversation with David Farley. Farley's a longtime food and travel writer with stories in the New York Times, Wall Street Journal, Afar, and many other publications. He's the author of An Irreverent Curiosity: In Search of the Church's Strangest Relic in Italy's Oddest Town and we talk about some recent food writing and David's many travels. We also played “What would you pitch 1997 Graydon Carter?” That is, David considers his dream no-budget reporting assignment. Featured on this episode:This Is the Secret Michelin-Star Capital of the World [Afar]Is This the New Cocktail Capital of Europe? [NYT]The Dish Worth Traveling to Vietnam For (and It Isn't Pho) [Afar]Welcome to Reno, the Mighty Mecca of All-You-Can-Eat Sushi [NYT]Lucien Smith Gets a Job [NY Mag]Everyone Who Invented the Everything Bagel [TASTE]See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
A contributor to the New York Times, National Geographic, BBC Travel, and Lonely Planet (to name a few), David Farley is living the travel writing dream. When his career was just starting, though, he didn't have a direct line to any editors; he had to prove himself. In this episode of the Travel Writing Podcast, he maps his rise from amateur to regular contributor to the biggest publications. This is your chance to learn how to get your foot in the door. Before you know it, you could be sent around the world to cover stories that will be read by thousands.
This Week on True Crime News The Podcast: Over 200 woman and minors have accused Oregon OB/GYN Dr. David Farley of sexual misconduct, alleging he assaulted and touched them inappropriately during appointments. In this exclusive interview, victims Katie Medley, Lisa Pratt, Nicole Snow, and Sarah Adams recount their experiences with Dr. Farley. Representing the victims, attorney Courtney Thom addresses the miscarriage of justice in the lack of criminal charges brought against Dr. Farley, but she offers hope as victims filed a landmark lawsuit against the disgraced doctor. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices
Mormon Church Hit With 91 Lawsuits https://floodlit.org/100-lawsuits-california/ Mormon Doctor Accused Of Sexual Abuse Patients https://www.cnn.com/2024/09/15/us/oregon-doctor-survivors-abuse-claims/index.html Member of the Bishopric Charged with Sexual Abuse of Boys https://www.idahostatejournal.com/freeaccess/police-local-church-youth-leader-arrested-for-sexually-abusing-five-teenage-boys/article_2a1eea3e-75dc-11ef-bf55-ebb2e0cec904.html https://www.eastidahonews.com/2024/09/church-leader-charged-with-sexual-abuse-after-allegedly-giving-naked-massages-to-multiple-boys/ Join our squad! Kristi and Katie share true crime stories and give you actionable things you can do to help, all with a wicked sense of humor. Want to Support our work and get extra perks? https://buymeacoffee.com/truecrimesquad Looking for extra content? https://www.patreon.com/truecrimesquad *Social Media Links* Facebook: www.facebook.com/truecrimesquad Facebook Discussion Group: https://www.facebook.com/groups/215774426330767 Website: https://www.truecrimesquad.com TikTok: https://www.tiktok.com/@truecrimesquad True Crime Squad on Spotify https://open.spotify.com/show/5gIPqBHJLftbXdRgs1Bqm1 --- Support this podcast: https://podcasters.spotify.com/pod/show/truecrimetps/support
Joining Etienne this week on the podcast is Sean Nam, the CTO of Ivy Energy. Etienne engages in a multifaceted conversation with Sean, and they touch upon the intricacies of supporting founders during fundraising to reflections on technology giants like Apple and Uber.Sean provides insights into IV Energy's mission to revolutionize shared energy usage through solar platforms, shedding light on the challenges and innovations in the field, and as the conversation delves deeper, Sean and Etienne explore the dynamics of team management, fundraising endeavors, and the evolving role of a CTO. Sean's reflections on American democracy, viewed through the lens of a South African and a Korean immigrant, also add a thought-provoking layer to the discussion.Sean also offers a candid exploration of the challenges of participating in a democracy amidst distractions and complexities, resonating with both disappointment and a call for collective action. Tune in for a compelling dialogue that blends technical expertise with societal insights, offering a glimpse into the complexities of modern leadership and civic engagement.Time Stamps:[1:25] - What are Sean's thoughts on Apple Vision Pro?[4:35] - Sean describes Ivy Energy's mission.[7:30] - Learn about Sean's team dynamics.[9:21] - Sean finds David Farley's insights refreshing, bridging software engineering with other technical disciplines.[10:42] - Learn how Sean's journey to leadership at Ivy Energy stemmed from seizing unexpected opportunities and challenges.[12:16] - Sean reflects on some of the lessons that he has been learning.[13:24] - Reflecting on venture capital dynamics through media like "Super Pumped" informs Sean's approach.[16:38] - Sean argues that effective collaboration between visionaries and their teams, like Steve Jobs with engineers, shapes success.[18:04] - Sean touches upon the significance of risk assessment.[20:01] - Balancing sales and marketing with product development ensures delivering on the promised vision.[22:51] - Transitioning from software engineer to CTO, Sean has honed communication skills and adapted to delayed feedback in leadership.[24:49] - Sean explains how giving feedback in a PR setting versus individually has a significant impact on individuals.[26:01] - Sean recently saw a news story involving a lack of attention leading to bribery in West Virginia.[28:30] - Etienne discusses how participating in democracy is challenging due to complexities; simpler systems are desired for all.[30:02] - The flaw in the US voting system lies in its historical complexity and lack of modernization.[33:10] - Sean asserts that politics becoming a show has led to exhaustion and disengagement and that systemic change requires collective effort.[36:02] - Sean feels that restricting information and education perpetuates autocracy.Resources and Links Mentioned:David Farley - Modern Software Engineering: Doing What Works to Build Better Software FasterWe have 200+ CTOs in peer groups: Quick Testimonials VideoContact Etienne: Website / YouTube / LinkedIn / X / Instagram / The CTO Podcast WebsiteContact Sean: LinkedInSchedule a meeting with Etienne on CalendlySee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Durante siglos, la reliquia del Santo Prepucio fue considerada por los creyentes la única pieza de la carne de Jesús que permanecía en la tierra después de ascender al cielo y por lo tanto fue una de las reliquias más sagrados de la cristiandad. Luego, el día de Año Nuevo 1983, en un pequeño pueblo en el campo italiano, el padre Don Darío anunció de que su amada reliquia había sido robada. En la búsqueda del Santo Prepucio vamos a seguir el escritor David Farley en su misión para averiguar qué pasó con el Santo Prepucio. Se le ha ofrecido un prepucio Santo certificado por un distribuidor reliquias italiano. Podría ser esta la reliquia que desapareció de Calcata? Con la reliquia en su poder, Farley tratará de averiguar si podría ser el verdadero prepucio de Jesucristo. Visitará laboratorios de ADN en Alemania y se infiltrará en el Vaticano en su búsqueda de respuestas. Farley también descubrirá la leyenda del Santo Prepucio y el papel crucial que desempeñó en la historia europea. En última instancia viaja a Calcata para encontrarse con el cura Don Darío y revelar la verdad de una vez por todas.
P. Brendon Lundberg, a previous chronic pain suffer, along with David Farley, MD, a Harvard-MIT trained physician, set out with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain. Combining a mission to change the way chronic pain is understood, treated with deep experience in healthcare management, marketing, business development and sales, Brendon and Dr. David Farley opened Radiant Pain Relief Centres in Portland, Oregon, USA, in February 2014. Following the success of the first center, they are laying out a plan for expansion to open new centers in new markets nationally and internationally. Their story and vision for the future of pain management can be understood by reading their Amazon Bestselling book, Radiant Relief – A Case For A Better Solution To Chronic Pain. Inc. Magazine called the book, “A Manifesto” and “an epic example of how to create a movement”. Previous to founding Radiant, Brendon played key operational and business development roles for two Portland-Area Portland Business Journal and Inc. Magazine Growth Award winning companies, and was the Director of Sales and Marketing for another Portland-based medical device start-up. Brendon holds a BS in business marketing and an MBA. Connect with Jon Dwoskin: Twitter: @jdwoskin Facebook: https://www.facebook.com/jonathan.dwoskin Instagram: https://www.instagram.com/thejondwoskinexperience/ Website: https://jondwoskin.com/LinkedIn: https://www.linkedin.com/in/jondwoskin/ Email: jon@jondwoskin.com Get Jon's Book: The Think Big Movement: Grow your business big. Very Big! Connect with P. Brendon Lundberg,: Website: www.radiantrelief.com Twitter: www.twiter.com/@radiantrelief
This week David Farley describes his career path and current role as Principal at William Hough High School. We discuss: His educational background Why he wanted to go into teaching The typical steps to becoming a high school principal His main roles and responsibilities What a typical day is like for him What he likes about the role and finds challenging Advice for those who want to follow his path
David Farley, guitar instructor at MasterBooksAcademy.com, joins the podcast to talk about both of his courses. In Beginning Guitar Lessons and Guitar Level 2, students learn hymns and worship songs as they learn to play the guitar. These courses are excellent for children and adults who want to learn to play the guitar and desire to connect with God through worship. We are giving away access to one of the courses in the Master Books app and in the Moms of Master Books FB group. Links: Beginning Guitar Lessons Guitar Level 2 Show Highlights 1:47 - David Farley shares his musical background and what led him to become an instructor. 3:20 - David Farley shares his heart for worship and how King David's worship has inspired him. 5:31 - Students will learn from David Farley how to welcome God's presence through worship. 7:02 - Students also learn leadership skills in this course. 7:56 - David shares about the two guitar courses: what students will learn and how the two levels differ. 9:20 - Students will have opportunities to perform for their parents to reveal what they are learning and retaining. 9:54 - David shares a list of songs the students learn in Beginner Guitar - Level 1. 12:57 - "We have the freedom to fail and we need to recognize that failure is a good thing." 14:58 - MasterBooksAcademy.com is our online learning portal where we have video instruction to supplement curriculum or stand alone courses like the Guitar courses. 15:26 - D. Farley explains what is needed to fulfill the requirements of the course: a playable guitar, tuner, capo, 17:32 - Jennifer and David discuss the benefits of using this course as opposed to typical in person lessons. 19:03 - David Farley discusses his new Guitar level 2 course . 22:10 - David discussed what a student is prepared to do once they have completed level 2. 23:41 - David ends with a prayer for students.
Australia's oldest working textile mill: Waverley Mills in Tasmania, is expanding! Hear from agribusiness veteran and Waverley executive director David Farley about his plans for not only the growth of this important piece of wool history but his optimism for a much larger domestic processing industry in Australia.
Get in a festive mood as Rick invites a few of his friends to compare the beer styles of Europe, and the cultures that go with them. Also, writer David Farley tells us about an eccentric hill town not far from Rome. It's home to a generation of bohemian residents, and one of the strangest mysteries in Italy — a centuries-old relic the Vatican would rather not talk about. For more information on Travel with Rick Steves - including episode descriptions, program archives and related details - visit www.ricksteves.com.
Join us for a taste of the latest Blackthorn Key middle grade adventure from Kevin Sands. Kevin spent time with teachers David Farley and Pam Jones and their students at Connaught Public School and Fisher Park Middle School / Summit Alternative School. Christopher's homecoming takes a sinister turn when a murderous conspiracy is uncovered in The Traitor's Blade, the fifth novel of the award-winning Blackthorn Key series. Christopher, Tom, and Sally are back in London at last. Everyone is relieved at their return—the plague has ended, and the king, pleased with their service, offers a surprising reward. But trouble has followed them home... First, an old friend is ambushed and left for dead. Then an anonymous letter arrives at Blackthorn—a mysterious warning hidden inside a riddle and secret code. As Christopher and his friends begin to investigate, they soon discover they've stumbled upon a plot to kill the king...and anyone else who dares stand in the traitors' way. Books are available from our friends at Perfect Books. The Ottawa International Writers Festival is supported by generous individuals like you. Please consider subscribing to our newsletter and making a donation to support our programming and children's literacy initiatives .
"I love taking a spark of an idea and being able to formulate a new instrument or changes to an existing one!" In 'Talking Flutes Extra' this week, Jean-Paul speaks with David Farley technical director at TJ flutes in London (U.K) about his last 30 years of working with musical instruments, and his dedication and commitment to learning from the great makers before us. David also speaks about the wonderful new 'Voce' headjoint, the new wooden flute that he's designed and his drive to get the Open G# flute back in to circulation at an affordable price. 'Talking Flutes' and 'Talking Flutes Extra' are podcast productions by the TJ flute company. For more information visit www.trevorjamesflutes.com
As a bonus follow-up to the Feast of the Holy Prepuce episode we talk with David Farley the author of the definitive book about Jesus’ Foreskin An Irreverent Curiosity. So if you have an irreverent curiosity, listen in and learn … Continued The post Bonus: A Conversation With David Farley The Author Of An Irreverent Curiosity appeared first on Dirty Talk Podcast.
Join me for the first of a series of interviews with podcast listeners on how they are coping with the pandemic. In this episode, David Farley, a travel and food writer who lives in New York City, joins me for a conversation. David wrote a blog post where he mused about our seeming missing future. He wrote: We can't envision what life is going to be like in, say, a year or what we'll be doing.... It's seriously anxiety-producing for many of us.... The only way we can maneuver, even survive without eventually imploding, is to change our outlook on life and the world. And reality. Listen for more of this thoughtful conversation with David where he shares his understanding of Buddhist teachings and his refuge in them. And listen for how you can share what you've learned as an upcoming podcast guest!
Celebrity memorabilia is big business these days, but nothing quite compares to the Holy Foreskin, a portion of Jesus' most intimate anatomy revered by Christians since the Middle Ages. David Farley, author of An Irreverent Curiosity and star of a National Geographic TV special, The Quest for the Holy Foreskin, is the world's leading expert on the sacred prepuce and its mysterious fate. The relic was stolen from a church in an Italian hill town in 1983. Was it by Satanists, neo-Nazis... or the Vatican?
Brendon Lundberg, a previous chronic pain suffer, co-founded Radiant Pain Relief Centres, along with David Farley, MD, a Harvard-MIT trained physician, with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain. Combining a mission to change the way chronic pain is understood treated with deep experience in healthcare management, marketing, business development and sales, Brendon and Dr. David Farley opened Radiant Pain Relief Centres in Portland, Oregon, USA, in February 2014. Following the success of the first center, they are laying out a plan for expansion to open new centers in new markets nationally and internationally. Their story and vision for the future of pain management can be understood by reading their Amazon Bestselling book, Radiant Relief – A Case For A Better Solution To Chronic Pain. Inc. Magazine called the book, “A Manifesto” and “an epic example of how to create a movement”. Previous to founding Radiant, Brendon played key operational and business development roles for two Portland-Area Portland Business Journal and Inc. Magazine Growth Award winning companies, and was the Director of Sales and Marketing for another Portland-based medical device start-up. Brendon holds a BS in business marketing and an MBA. Connect with P. Brendon LundbergWebsite: www.radiantrelief.com Twitter: @radiantrelief Facebook: https://www.facebook.com/RadiantPainReliefCentres/ Instagram: https://www.instagram.com/radiantpainreliefcentres/ Connect with Jon Dwoskin: Website: http://jondwoskin.com/ Twitter: @jdwoskin Facebook: https://www.facebook.com/jonathan.dwoskin Instagram: https://www.instagram.com/Thejondwoskinexperience/ LinkedIn: https://www.linkedin.com/in/jondwoskin/ Email: jon@jondwoskin.com
A warm welcome to John Harris who will be joining us for his first time on the show today to discuss our exciting topic, CI and CD in cloud native! CI and CD are two terms that usually get spoken about together but are actually two different things entirely if you think about them. We begin by getting into exactly what these differences are, highlighting the regulatory aspects of CD in contrast to the future-focussed nature of CI. We then move on to a deep exploration of their benefits in optimizing processes in cloud native space through automation and surveillance from development to production environments. You’ll hear about the benefits of automatic building in container orchestration, the value of make files and local test commands, and the evolution of CI from its ‘rubber chicken’ days with Martin Fowler and Jez Humble. We take a deep dive into the many ways that containers differ from regular binary as far as deployment methods, build speed, automation, run targets, realtime reflections of changes, and regulation. Moreover, we talk to the challenges of transitioning between testing and production environments, getting past human error through automation, and using sealed secrets to manage clusters. We also discuss the benefits and drawbacks of different CI tools such as Kubebuilder, Argo, Jenkins X, and Tekton. Our conversation gets wrapped up by looking at some of the exciting developments on the horizon of CI and CD, so make sure to tune in! Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: Bryan Liles Nicholas Lane Key Points From This Episode: • The difference between CI and CD.• Understanding the meaning of CD: ‘continuous delivery’ and ‘continuous deployment’.• Building an artifact that can be deployed in the future is termed ‘continuous integration’.• The benefits of continuous integration for container orchestration: automatic building.• What to do before starting a project regarding make files and local test commands.• Kubebuilder is a tool that scaffolds out the creation of controllers and web hooks.• Where CI has got to as far as location since its ‘rubber chicken’ co-located days.• The prescience of Martin Fowler and Jez Humble regarding continuous integration.• The value of running tests in a CI process for quality maintenance purposes.• What makes containers great as far as architecture, output, deployment, and speed.• The benefits of CD regarding deployment automation, reflection, and regulation.• Transitioning between testing and production environments using targets, clusters, pipelines.• Getting past human error through automation via continuous deployment.• What containers mean for the traditional idea of environments.• How labeling factors into the simplicity of transitioning from development to production.• What GitOps means for keeping track of changes in environments using tags.• How sealed secrets stop the need to change an app when managing clusters.• The tools around CD and what a good CD system should look like.• Using Argo and Spinnaker to take better advantage of hardware.• How JenkinsX helps mediate YAML when installing into clusters.• Why the customizable nature of CI tools can be seen as negative.• The benefits of using cloud native-built tools like Tekton.• Perspectives on what is missing in the cloud native space.• A definition of blue-green deployments and how they operate in service meshes.• The business abstraction elements of CI tools that are lacking.• Testing and data storage-related aspects of CI/CD that need to be developed. Quotes: “With the advent of containers, now it’s as simple as identifying the images you want and basically running that image in that environment.” — @bryanl [0:18:32] “The whole goal whenever you’re thinking about continuous delivery or continuous deployment is that any human intervention on the actual moving of code is a liability and is going to break.” — @bryanl [0:21:27] “Any time you’re in developer tooling, everyone wants to do something slightly differently. All of these tools are so tweak-able that they become so general.” — @johnharris85 [0:34:23] Links Mentioned in Today’s Episode: John Harris — https://www.linkedin.com/in/johnharris85/Jenkins — https://jenkins.io/CircleCI — https://circleci.com/Drone — https://drone.io/Travis — https://travis-ci.org/GitLab — https://about.gitlab.com/Docker — https://www.docker.com/Go — https://golang.org/Rust — https://www.rust-lang.org/Kubebuilder — https://github.com/kubernetes-sigs/kubebuilderMartin Fowler — https://martinfowler.com/Jez Humble — https://continuousdelivery.com/about/David Farley — https://dfarley.com/index.htmlAMD — https://www.amd.com/enIntel — https://www.intel.com/content/www/us/en/homepage.htmlWindows — https://www.microsoft.com/en-za/windowsLinux — https://www.linux.org/Intel 386 — http://www.computinghistory.org.uk/det/6192/Introduction-of-Intel-386/386SX — https://www.computerworld.com/article/2475341/flashback--remembering-the-386sx.html386DX — https://en.wikipedia.org/wiki/Intel_80386Pentium — https://www.intel.com/content/www/us/en/products/processors/pentium.htmlAMD64 — https://www.webopedia.com/TERM/A/AMD64.htmlARM — https://en.wikipedia.org/wiki/ARM_architectureTomcat — http://tomcat.apache.org/Netflix — https://www.netflix.com/za/GitOps — https://www.weave.works/technologies/gitops/Weave — https://www.weave.works/Argo — https://www.intuit.com/blog/technology/introducing-argo-flux/Spinnaker — https://www.spinnaker.io/Google X — https://x.company/Jenkins X — https://jenkins.io/projects/jenkins-x/YAML — https://yaml.org/Tekton — https://github.com/tektonCouncourse CI — https://concourse-ci.org/ Transcript: EPISODE 11 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically-minded decision maker, this podcast is for you. [EPISODE] [00:00:41] BL: Back to the Kubelets Podcast, episode 11. I’m Bryan Liles, and today we have Nicholas Lane. [00:00:50] NL: Hello! [00:00:51] BL: And joining us for the first time, we have John Harris. [00:00:55] JH: Hey everyone. How is it going? [00:00:56] BL: All right! So today we’re going to talk about CI and CD in cloud native. I want to start this off with this whole term CI and CD. We talk about them together, that are two different things almost entirely if you think about them. But CI stands for continuous integration, and then we have CD. What does CD stand for? [00:01:19] NL: Compact disk. [00:01:20] BL: Right. True, and actually I’ve used that term before. I actually do agree. But what else does CD stand for? [00:01:28] NL: It’s continuous deployment right? [00:01:30] BL: Yeah, and? [00:01:31] JH: Continuous delivery. [00:01:32] NL: Oh! I forgot about that one. [00:01:35] BL: Yeah, that’s the interesting thing, is that as we talk about tech and we give things acronyms, CD is just a great one. Change in directories, compact disk, continuous delivery and continuous deployment. Here’s the bonus question, does anyone here know the difference between continuous delivery and continuous deployment? [00:01:58] NL: Now that’s interesting. [00:01:59] JH: I would go ahead and say continuous delivery is the ability to move changes through the pipeline, but you still have the ability to do human intervention at any stage, and usually deployments production and continuous delivery would be a business decision, whereas continuous deployment is no gating and everything just go straight to product. [00:02:18] BL: Oh, John! Gold start for you, because that is one of the common ones. I just like to bring that up because we always talk about CI and CD as they are just one thing, but they’re actually way bigger topics and we’ve already introduced three things here. Let’s start at the beginning and let’s talk about continuous integration, a.k.a CI. I’ll start off. We have CI, and what is the goal of CI? I think that we always get boggled down with tech terms and all these technology and all these packages from all these companies. But I’d like to boil CI down to one simple thing. The process of continuous integration is to build an artifact that can be deployed somewhere at some future date at some future time by some future person, process. Everything else is a detail of the system you choose to use. Whether you use Jenkins, or CircleCI, or Drone, or you built your own thing, or you’re using Travis, or any of the other online CI tools. At the end of the day, you’re building either – If you’re doing web development. Maybe you’re building out Docker files, because we’re in cloud native. I mean docker images, because we’re in cloud native. But if you’re not, maybe you’re just building JARs, WARs, or EARs, or a ZIP file, or a binary, or something. I’d just like to start off, start this off with there. Any more thoughts on continuous integration? [00:03:48] NL: Yeah. I think the only times that I’ve ever used something that’s like continuous integration is when I’ve been doing like more container orchestration, like development, things on top of like things like Kubernetes, for instance. The thing I really like about it is like the concept of being able to like, from my computer, save and do an automatic save and push to a local repo and have all of the pieces get built for me automatically somewhere else, and I just love that so much because it saves so much brain thinky juice to run every command to make the binary you need. [00:04:28] BL: So did you actually create those scripts yourself? [00:04:30] NL: Some of them. When I’ve used things like GitLab, I use the pipeline that exists there and just fiddled around with like a little bit of code, like some bash there, but like not too much because GitLab has a pretty robust pipeline. Travis — I don’t think I needed to actually. Travis had a pretty good just go make Docker build, scripts already templated out for you. [00:04:53] JH: Yeah. I’d like to tell people whenever you start any project, whether it’s big or small, especially if it’s on – Not on Windows. I’ll tell you something different if it’s on Windows. But if you’re developing on a Mac or developing on Linux, the first thing you should do in your project is create a make file or your programming language equivalent of a make file, and then in that make file what you should do is write a command that will build your software that runs its tests locally, and also builds – whatever the process is. I mean, if you’re running in Go, you do a Go build. If you’re using Rust, build with Rust, or C++, or whatever before you even write any code. The reason why is because the hardest part is making your code build, and if you leave that to the end, you’re actually making it harder on yourself. If your code build works from the beginning, all you have to do is change it to fit what you’re doing rather than thinking about it when it’s crunch time. [00:05:57] NL: I actually ran into that exact scenario recently, because I’ve been building some tooling around some Kubernetes stuff, and the first one I did, I built it all manually by hand. Then at the end I was like – I gave it to the person who wanted it and they’re like, “So, where’s the make file?” I’m like, “Where’s the what?” So I had go in and like fill in the make file, and that was a huge pain in the butt. Then recently the other thing I’ve been using is Kubebuilder. John, you and I have been talking about Kubebuilder quite a bit, but using Kubebuilder, and one of the things it does for you is it scaffolds out and a make file for you, and that was like going from me doing it by myself to having it already exist for you or just having it at the beginning was so much better. I totally agree with you, Brian. [00:06:42] BL: So quick point of order here. For those of us who don’t know what Kubebuilder is. What is Kubebuilder? [00:06:48] NL: Kubebuilder is a tool that was created by members of the Kubernetes Community to scaffold out the creation of controllers and web hooks. What a controller is in Kubernetes is a piece of software that waits, sort of watches a specific object or many specific objects and reconciles them. If they noticed that something has changed and you want to make an action based on that change, the controller does that for you. [00:07:17] JH: Okay. So it actually makes the action of working with CRDs and Kubernetes much easier than creating it all yourself. [00:07:26] NL: Correct. Yeah. So, for instance, the one that I made for myself was a tool that watched, updated and watched a specific CRD, but it wasn’t necessarily a controller. It was just like flagging on whether or not a change occurred, and I used the dynamic client, and that was a huge headache on of itself. Kubebuilder has like the ability to watch not just CRDs, but any object in Kubernetes and then reconcile them based on changes. [00:07:53] NL: It’s pretty great. [00:07:54] BL: All right. So back to CI. John, do you have any opinions on CI or anecdotes or anything like that? [00:07:59] JH: Yeah. I think one of the interesting things about the original kind of philosophy of CI outside of tooling was like trunk-based development that every develop changes get integrated into trunk as soon as possible. You don’t get into integration hell and rebasing. I guess it’s kind of interesting when you apply that to a cloud native landscape where like when that stuff came out with like Martin Fowler or Jez Humble probably 10, 15 years ago almost now, a lot of dev teams were co-located. You could do CI. I think there was a rubber chicken method where you didn’t use a tool. It was just whoever had the chicken that’s responsible for the build. Just to pull everyone else’s changes. But now it seems like everything is branch-based. When you look at a project like Kubernetes, there’s a huge number of contributors all geographically displaced, different time zones, lots of different branches and features going on at the same time. It’s interesting how these original principles of continuous integration from the beginning now apply to these huge projects in the cloud native landscape. [00:08:56] BL: Yeah, that’s actually a great point of how prescient Martin Fowler has been for many, many years, and even with Jez Humble being able to see these problems 10, 15 years ago and be able to describe them. I believe Jez Humble wrote the CD book, the continuous delivery book. [00:09:15] JH: Yeah, with David Farley, I think. [00:09:18] NL: Yeah. Yeah, he did. So, John, you brought up some good things about CI. I try to simplify everything. I think the mark of someone who really knows what they’re talking about is being able to explain everything in the simplest words possible, and then you can work backwards when people understand. I started off by saying that CI produces an artifact. I didn’t talk about branches or anything like that, or even the integration piece. But now let’s go into that a little bit. There are a lot of misconceptions about CI in general, but one of the things that we talk about is that you have to run test. No, you don’t have to run test, but should you? Yes, 100% of the time. Your CI process, your integration process should actually build your software and run the test, because running the test on this dedicated service or hardware wherever it is ensures that the quality of your software is there at least as much as your developers have insured the quality in the test. It’s very important those run, and a lot of bugs of course can be spotted by running a CI. I mean, we are all sorts of developers here, and I tell you what, sometimes I forget to run the test locally and CI catches me before a commit makes it into master and it has a huge typo or a whole bunch of print lines in there. Moving on here, thinking about CI and cloud native. Whenever you’re creating a cloud native app, have you ever thought about the differences between let’s say creating just a regular binary that maybe runs on a server, but not in a container on somebody’s cloud native stack, i.e. Kubernetes? Have you ever thought about the differences of things to think about? [00:11:04] BL: Yeah. So part of it is – I would imagine or I believe it’s like things like resource, like what resources you need or what architecture you’re deploying into. You need the binary to make like run in this – With containerization, it’s easy because you’re like, “I know that the container is going to be this architecture,” but you can’t necessarily guarantee that outside of a containerized world. I mean, I suppose you can being like with the right tooling setup you can be like, “I only want to run on this.” But that isn’t necessarily guaranteed, because any computer that runs on could be just whatever architecture that happens to land on, right? Also, something to – I think of is like how do you start processes on disparate computers in a controlled fashion? Something like, again, with containers, you can trust that the container runtime will run it for you. But without that, it seems like a much harder task. [00:12:01] NL: Yeah, I would agree. Then I said that containers in general just help us out, because most of our workloads go on some AMD or Intel 64 bit and it’s Linux. We know what our output is going to be. So it’s not like in the old days where you had to actually figure out what your run target was. I mean, that’s even on Intel stacks. I mean, I’m updating myself here where you had like – When the 386 was out and then you had the 386SX and the 386DX, there were different things there, and you actually compile your code different. Then when the 46 came out and then when we had introduction of Pentium chips, things were different. But now we can pretty much all target AMD64, and in some cases, I mean, there are some chip things like the bigger encryption things that are in the newer chips. But for the most part, we know what our deployed target is going to be. But the cool thing is also that we don’t have to have Intel or AMD64. It could be ARM32 or ARM64, and with the addition to a lot of the work that has been going on in Windows land lately, we can have Windows images. I don’t know so many people were doing that yet. I’m not out and part of the field, but I like that the opportunity is there. [00:13:25] JH: Oh! I think one of the interesting things is the deployment method as well. Now with containers, everything is kind of an immutable rip and replace. Like if we develop an application, we know that the old container is going to stop when I deploy a new one. I think Netflix were doing a little bit of this before containers and some other folks with like baking AMIs and using that immutable method. But I think before that it was if we had a WAR file, we had to throw it back into Tomcat, let Tomcat pick it up or whatever. Everything was a little bit more flaky in terms of deployment. We had to do a lot of checks around deployment rather than just bring something out, bring something back in blue/green, whatever. [00:13:59] BL: Well, I actually like that you brought that up, because that’s actually one of the greatest parts of this whole cloud native thing, is that when we’re using containers and we’re deploying with containers, we know what our file system is going to look like, because we created it. There would not be some rogue file or another configuration there that will trip up our deployment, because at build time, we’ve created the environment. It’s much better than that facility that Netflix was doing with baking AMIs. In a previous life, I actually ran the facility for baking AMIs at a large company where we had thousands of developers on more than a thousand dev teams, and we had a lot of spyware. Whenever you had to build an image, it was fine in one account, but if you had let’s say a thousand accounts with the way that AWS works and encrypted images, you actually had to copy all the images to all the accounts. It couldn’t actually boot it from your account. That process would literally take all night to get it done across all of our accounts. If you made a mistake, guess what? You get to do it again. So I am glad that we actually have this thing called a container and all these things based on CRI, the container runtime, that we are able to quickly build containers. I don’t want to just limit this conversation to continuous integration. Let’s get into the other parts too with deployment and delivery. What is so novel about CD and the cloud native world? [00:15:35] NL: I think to me it’s the ability to have your code or your artifact or whatever it is, whatever you’re working on. When you make a change, you can see the change reflected in reality, whatever your reality looks like, without your intervention. I mean, you might have had to set up all the pipelines and all that jargon, but when you press save in VS code and it creates a branch and runs all your tests and then deploys it for you or delivers it for you into what you’d define as reality, that’s just so nice, because it really kind of sucks having to do the like, “Okay, I’ve got a new deployment. Destroy the old deployment. Put in the new one or like rev the new image tag or whatever in the deployment you’re doing.” All these manual steps, again, thinky-brain juice, it takes pieces of your attention away, and having these pieces like added for you is just so nice. [00:16:30] BL: Yeah, what do you think, John? [00:16:32] JH: Yeah. I think just something in the state of DevOps we’ve bought one of the best predictors for a company’s success is like cycle time of feature from ideation to production. I think like the faster we can get that cycle – It kind of gets me interested. How long does an application take to build? If it takes two hours, how good are you at getting features out there quickly? Maybe one of the drivers with microservices, smaller pieces independently deployed, we can get features out to production quicker, because I think the name of the game is just about enabling developers to put the decision in the hands of the business to decide when the customer should see that feature. I think the tighter we can make that cycle, the better for everyone. [00:17:14] BL: Oh, no! I agree. I love and hate web services, but what I do like is the idea of making these abstractions smaller, and if the abstractions are smaller, it’s less code. A lot of the languages we use now are faster compiling, let’s say, a large C++ project. That could take literally two hours to compile. But now when we have languages like Go, and Rust is not as fast, but it’s not slow as well. Then we have all of our interpret languages, whether it’d be Python, or JavaScript, or TypeScript, where we can actually go from an idea, run the test in a few minutes and build this image that we can actually run and see it almost in real-time. Now with the complexity of the tools, I mean, the features that are built in the tools, we can now easily manage multiple deployment environments, because think about before, you would have a dev environment, and that would be the Wild West. That would be literally where it would be awful. You might have to rebuild it every couple of months. Then you would have staging, and then maybe you would have some kind of pre-prod environment just as like your final smoke test, and then you would have your production. Maintaining all the software on all those was extremely hard. But now with the advent of containers, now it’s as simple as identifying the images you want and basically running that image in that environment. I like where we’ve ended up. But with all power comes new problems, and just because we can deploy quicker means we just run into a lot of different problems we didn’t run into before. The first one that I’ll bring up is the complexity. Auto conversion between environments, so moving code between test staging and production. How do we do that? Any ideas before I throw some out there? [00:19:11] NL: I guess you would have different, or maybe the same pipeline but different targets for like if say you’re using something like Kubernetes. You could have one part of your pipeline deploy initially to this Kubernetes context, which points to like one cluster. It’s building up clusters by environment type and then deploying into those, running your tests, see if it runs properly and then switch over to the next context to apply that image tag and that information and then just go down the chain until you go to production. [00:19:44] BL: Well, that’s interesting. One thing I’d like to throw out there, and I’m not advocating any particular product. But the idea of having pipelines for continuous integration and your CD process is great, where you can now have gates and you can basically automate the whole thing. Code goes into CI and we built an artifact, and a message can go out automatically to an approver or not, and that message could say, “Hey! This code is going to be integrated into our trunk or our master branch.” They can either do it themselves manually as a lot of people do or they can actually maybe click on a link or check a checkbox and this gets integrated in. Then what automatically could happen at this point is, and I’ve seen a lot of companies doing this, is now we take that software and we spin up a new whole environment and we just install that software. For that one particular feature that you worked on, you can actually get an automatic environment for that. Then what we can do is we can take that environment itself and we can now merge this maybe into a staging branch or tag it with a staging label, and that automatically gets moved to staging. Depending on how complicated you are, how advanced you are, now you can actually have it go out to your product people or people who make decisions, maybe your executives, and they can view the software in whatever context it happens to be in. Then they can say, “Okay.” Now that’s when we’re talking about now we can hit okay and the software just keeps on moving to the pipeline and it gets into production. The whole goal here, and this is actually where your goal should be just in general whenever you’re thinking about continuous delivery or continuous deployment is that any human intervention on the actual moving of code is a liability and is going to break, and it’s going to break because on Friday afternoon at 5:25 PM, someone’s thinking about the weekend and they’re not thinking about code, and they’re going to break your build. Our goal is to build these delivery systems that are Friday afternoon proof. We can push code anytime. It doesn’t matter. We trust our process. [00:22:03] JH: I think it’s a great point about environments. I think back in the day, an environment used to be a set of machines, and then test used to be – staging was where there were kind of more stable versions of APIs and folks were more coordinated pushing things into them. What really is an environment? Like you said, when we push micro services or whatever service, we can spin up an entire Kubernetes cluster just for that service. We can set it up. We can run whatever tests we want. We could tear it down. With the advent of Elastic compute, and now containers, they really enabled this world where like the traditional idea of an environment and what constitutes an environment is starting to get a bit kind of sloppy and blend into each other. [00:22:42] BL: I like it though. I think it’s progress. [00:22:45] NL: I totally agree. The one that scares me but I also find like really interesting, is the idea of having all of your environments in one set of machines. So clusters. Having a multi-tenanted set of machines for like dev staging and production, they’re all running in the same place and they’re all just separated by like what configuration of like connectivity from different networking and things like that set up. When a user hits your website, bryanliles.com, they should go to the production images, but those are binaries, and those binaries should be running in the same space essentially as the development ones. It’s scary, but it’s also like allows for like some really fast testing and integration. I find it to be very fascinating. [00:23:33] BL: I mean that’s where we want to be. I find more often than not that people have separate clusters for dev and staging and production. But using the Kubernetes API, you don’t have to do that, because what we can do is we can force deployment or workload to a set of machines based on their label. That’s actually one of the very strong positives for Kubernetes. Forget all the complexity. One of the things that makes it easy is to say that I want this particular deployment to only live on my development machines. Well, which development machine? I don’t care. What if we increase our development pool size? We just re-label nodes. It doesn’t matter. Now we can just control that. When it comes down to controlling cost and complexity, this is actually one idea that Kubernetes is leading and just making it easier to actually use more of your hardware. [00:24:31] NL: Yeah. Absolutely. That’s so great because if you think about it from a CI/CD standpoint, at that point all you have to do is just change the label to where you’re applying this piece of code. So you’re like, “Node selector, label equals dev. Okay, now it’s staging. Okay, now it’s prod.” [00:24:47] BL: So this brings me into the next part of what I want to talk about or introduce to you all today. We’re on a journey as you probably can tell. Now whenever we have our CI process and we’re building and we’re deploying, where do we store our configurations? [00:25:04] NL: [inaudible 00:25:04]. [00:25:06] BL: Ever thought about that? [00:25:08] NL: Okay. I mean, in a Kubernetes perspective, you might be using something like etcd to sort of – But like everything else, what if you’re using Travis? [inaudible 00:25:16] store everything. Everything should be versioned, right? Everything should be – [00:25:20] BL: Yeah, 100%. [00:25:24] NL: I would store everything these as much as possible. Now, do I do that all the time? God, no! Absolutely not. I’m a human being after all. [00:25:32] BL: I mean, that’s what I actually want to bring up, is this concept of GitOps. GitOps was a coined term by my friend, Alexis, who works at Weave. I think Weave created this. Really what it’s about is instead of having – basically, Kubernetes is declarative, and our configurations can be declarative too, because what we can do is make sure is we can have tech space configurations, and for one reason it’s because tech space means it can be versioned. It can be diffs. We take those text versions and we put them in our same repository we put our code in. How do we know what’s in production at any given time or any given time in the past? We just look at the tags of what we did. We had a push at 5:15 on August 13th. Of course, this is 5:15, you could see time, because any other time doesn’t exist in the computer land. So what we could do is we could just basically tag that particular version as like 2019-08-13. If I said 5-17-55, and we call 01 just so we could have 100 deploys in a day. If we started doing that, now not only can we control what we have, but we can also know what was on in any given environment at any given time. Because with Git and with Mercurial and any other of these – Well, only the popular ones, with Git and Mercurial, you can definitely do this. Any given commit can have multiple tags. You could actually have a tag that hit dev and then a tag that, let’s say, hits staging, and then a tag that hit production, the exact same code but three different tags. So you know at any given time what happened. [00:27:18] JH: Yeah, the config thing is so important. I think that was another Jez Humble quote where it was like, “Give me three hours access to your code and I’ll break it. But give me 5 minutes with your configurations and I’ll break it.” Almost like every big bug is, right, someone was accidentally pointing the prod server to the staging database like, “Oops! Their API was pointing to the wrong port, and everything came down,” or we changed the wrong versions or whatever. I think that’s one of the intersections of developers and operations folks. We kind of talked about like Dev Ops and things like that. I really love the idea of everything being kept in Git and using GitOps, but then we’ve got things like secrets and configuration that shouldn’t be seen or being able to be edited by developers, but need to be for ops folks. But we still want to keep the single point of truth. Things like sealed secrets have really enabled us to move along in this area where we can keep everything in text-based version. [00:28:08] BL: All right. Quick point of order here. Sealed secrets is a controller/CRD created by Bitnami. What it allows you do is, John – [00:28:23] JH: It allows you – It creates a CRD, which is sealed secret, which is a special resource type in your cluster and also creates a key, which is only available to that operator running in your cluster. You can submit a sealed secret in plain text or you can submit a secret in plain text and it will throw it back out as an encrypted secret with that key and then you can check that into version control. Then when you go to deploy your software, you can deploy that encrypted secret into the cluster. The operator will pick it up, decrypt it using only the key that it has access to and then put it back in the cluster as a regular secret. Your application just interacts with regular Kubernetes secrets. You don’t need to change your app. They deal with all the encryption outside of the user intervention. [00:29:03] BL: I think the most important part of what you said is that this allows us to have no excuses about what we can store in our repositories for our configuration, because someone is going to make the argument, “No, we can’t store secrets, because someone’s going to be able to see them.” Well, guess what? We never even stored an unencrypted secret in our repository. They’re all encrypted, and it’s still secrets. It’s [inaudible 00:29:25]. I don’t know if anyone’s cracked yet. I’m sure maybe a state level actor has thought of it. But for us regular people, even our companies, like even at VMware, or even at Google, they have not done it yet. So it’s still pretty safe. Thinking even further now, and really what I’m trying to paint the picture of is not just how do you do CD, but really what CD could look like and how it can actually make you happy rather than sad. The next item I wanted to think about was tools around CD and creating tools and what does a good continuous delivery system look like. I kind of hinted about this earlier whenever I was talking about pipelines. The ability to take advantage of your hardware, so we’re deploying to let’s say 100 servers. We’re pulling 5 or 6 services to 100 node cluster. We can do those all at once, and what we can do is you want to have a system that can actually run like this. I could think of a couple. From Intuit, there is Argo, and they have Argo CD. There is the tool created by Google and maybe Netflix. I want to have to look that one up. It’s funny, because they quoted – [00:30:40] JH: Spinnaker? [00:30:42] BL: Spinnaker. They quoted me in their book, and I don’t remember their name. I’m sorry anyone from Spinnaker product listening. Once again, not advocating any products, but they have the concept of doing pipelines. Then you also have other things for your projects, like if you’re using open source, Drone. Another X Google – I think it was X-Googler that made this. Basically, they have ways you can do more than one thing at a time. The most important piece about this is not only can you do more than one thing at a time, is that you have a programmatic check that it’ll make sure that you can verify that whatever you did was successful. We deployed to staging or we deployed to our smoke test servers for our smoke test, and that requires our testing people and an executive signoff. They can actually just wait until they get their signoff or maybe if it goes over a day or so, they can actually – It just fails, and now the build is done. But that part is pretty neat. Any other topics over here before I start throwing out more? [00:31:45] NL: I think I just have thoughts on some of the tools that we’ve used. Everyone Jenkins. Jenkins can do anything that you want it to do, but you really have to tighten the screws on it. It is super powerful. It’s kind of like Bash, like Bash scripting. It’s super powerful, but you have to know precisely what you’re doing, otherwise it can really hurt you. Actually, I have used Spinnaker in the past, and I’ve really liked it. It has a good UI, very good pipelines. Easy blue/green or canary deployment mechanism, I thought that was great. I’ve looked at Drone, believe it or not, but Drone is actually pretty cool. Check out Drone. I really liked it. [00:32:25] BL: Well, since we’re throwing out products, Jenkins, does have JenkinsX. I have not given it the full rundown yet. But what I do like about it, and I think everyone should pay attention to this if you’re doing a product in this space, is that when you install JenkinsX, you install it locally to your machine. You basically get this binary called JX, and you then tell JX to install it into your cluster. Instead of just doing kubectl apply-f a whole bunch of YAML, it actually ask you questions and it sets up GitHub repositories or wherever you need these repositories. It sets up [inaudible 00:33:01] spaces for you. There’s no just [inaudible 00:33:05] kubectl apply-f HTTPS: I just owned your system, because that’s actually a problem. Then it solves the YAML sprawl, because YAML and Kubernetes is something that is complained about a lot, but it’s how it’s configured. But it’s also just a detail what we’re supposed to be doing, and we actually work with Joe Beda and I could talk about this all the time, is that the YAML is the implementation, but it’s not the idea. The idea is that we build tools on top of that that create YAML so users have to see less YAML. I think that’s a problem with Jenkins, is that it’s so powerful and they’re like, “Well, we want powerful people or smart people to be able to do smart things. So here you go.” The problem with that is that where do I start? It’s a little daunting. So I do think that they definitely came with the much stronger game with this JX command. Just as a little sidebar, we do it as well with our Valero project, and I think that just speaks, should be like the bar for anything. If you’re installing something into a cluster, you should come up with a command line tool that helps you manage the lifecycle of whatever you’re installing to the operator, YAML, whatever. [00:34:18] JH: I think what’s interesting about the options, this is definitely one area where there’s so much nuance. Any time you’re in developer tooling, everyone wants to do something slightly differently. All of these tools are so tweak-able that they become so general. I think it’s probably one of the criticisms that could be leveraged against Jenkins is that you can do everything, and that’s actually a negative as well as a positive. Sometimes it’s too overwhelming. There are too many ways of doing things. I’m a fan of some of the more kind opinionated tools in that space. [00:34:45] BL: Yeah. I like opinionated tools as well, but the problem that we’re having in this cloud native space is that, yeah, Kubernetes is five-years-old now. We are just getting to the point where we actually understand what a good decision is, because there was a lot of guesses before and we’ve done a lot of things, and some of these have been good ideas, but in some cases they have not been great ideas. Even I ran the project case on it. Great idea on paper, but implementation, it required people to know too many things. We’d learned a lot of lessons from that. That’s what I think we’re going to find out in this space is that we’re going to learn little lessons. I say this project from my last project that I was going to bring up is something that I think has learned some of the lessons. Google sponsors a project called Tekton, and if you go to – It’s like I believe, and they have some continuous delivery stuff in there and they implement pipelines. But the neat part is, and this is actually the best part, it’s actually a cloud native built service. So every step of your delivery process, from creating images, to actually putting them on clusters, is backed by a Docker image or a container, and I think that part is pretty neat. So now you can define your steps. What is your step? Well, you can use one of their pre-baked, run this command, or if you have something special, like the example before I was giving out where you would say that you need an approval, maybe it’s a Slack approval. You send something with Slack and it has a checkbox, check yes if you like me. What we can do now is we can actually control that and it’s easy to write something a little Docker image that can actually make that call and then get the request and then it can move it on. If you’re looking at more of a toolkit full of good ideas, I do think that Tekton has definitely has some lots of industry. People are looking at it and it’s probably the best example of getting it right in the cloud native way. Because a lot of the products we have now are not cloud native. We’re talking about Jenkins. We’re talking about Spinnaker and we talk about Drone and Travis, which is totally a SaaS product. They’re not cloud native. Actually, the neat part about Tekton is that it actually comes with its own controllers and its own CRDs. So you can actually build these things up using your familiar Kubernetes tooling, which means in theory we could actually use the tooling that we are deploying. We can actually control it in the same way as our applications, because it’s just yet another object that goes in our cluster. [00:37:21] NL: That does sound pretty cool. One other that I meant to bring up was Concourse. Have you check out Concourse yet? [00:37:27] BL: CouncourseCI. I have not. I have used it, but never in a way where I would have a big opinion on it. [00:37:34] NL: I’m kind of in the same place. I think it’s a good idea. It seems really neat, but I need to kick the tires a little more. I will say that I really like the UI. The structure of the UI is really nice. Everything makes sense, and anything you can click on like drills into something a bit deeper. I think that’s pretty cool, but it is one of the shout that I went out to as well as like another tool that I’m aware of. [00:37:52] BL: Yeah, that’s pretty interesting. So we’ve gone about 40 minutes now. Let’s actually start winding this down, and the way that I’m going to suggest that we wind this down is thinking about where we are now. What’s missing in this space and what else could we actually be doing in the cloud native space to make this work out better? [00:38:12] NL: I think I’d like to see better structured or better examples of blue-green or canary deployments with tests associated, and that might just be like me not looking hard enough at this problem. But anytime I began looking at blue-green, I get the idea of what someone’s done, but I would love to see some implementation details, or any of these opinionated tools having opinions around blue-green and what they specifically do to test it. I feel like I’m just not seeing that. [00:38:41] BL: With blue-green, blue-green is hard to do in Kubernetes without an external tool, because for everyone, a blue-green deployment is, I have a software deployment and we’ll give it a color. We’ll call it blue, and I have the next version, and we’ll call it green. Really what I can do is I basically have two versions of my application deployed and I can use my load balancer, or in this case, my service to just change the label or the selector in my service and now I can point at at my green from my blue. Then I want to deploy again, I can just deploy another blue and then change my label selector again. The problem with this is that you can do it in Kubernetes, just fine. But out of the box with Kubernetes, you will drop traffic, because guess what? What happens to a connection that was initiated or a session that was initiated on the blue cluster when you went to green? Actually, this is a whole conversation in itself about service meshes and this is actually one of the reasons service mesh is a big topic, because you can do this blue-green, or another example would be Netflix and Redblack, or you get the creative people who are like rainbow deployments, because just having two is not good enough for them. So they want to have any number of deployments going at one time. I agree with that 100%. [00:39:57] JH: I think, yeah, integrating tools like launch. [inaudible 00:40:01] and I think there are more which enable – I think we’re missing the business abstractions on this stuff so far. Like you said, it’s kind of hard to do if you need to go into the gritty of it right now, but I think the business abstractions of if we deploy a different version to a certain subset of customers, can we get all of those metrics? Can we get those traces back in? Will you automate it, roll it out? Can we increase the percentage of customers that are seeing those things? Have that all controlled in a Kubernetes native way, but having roll it up to a business and more of an abstraction. I think that stuff is currently missing. I think the underpinning kind of technologies are coming up, stuff like service mesh, but I think it’s the abstraction that’s really going to make it useful, which doesn’t exist today. [00:40:39] BL: Yeah. Actually, that’s pretty close to what I was going to say. We built all these tooling that helps us basically as technologists, but really what it comes down to is the business. A lot of the things we’re talking about where we’re talking about CD is important to the business, but when we’re talking about metrics or trace collection, that’s not important to the business, because they only care about the SLA. This is on the SLO side. What we really need to do is mature our processes enough that we can actually marry our outputs to something that other people can understand that has no jargon and it’s sales going up, sales going down. Everything else is just a detail. So, anything else? [00:41:20] NL: Something I think I’d like to see is in our testing, if there was a good way to accurately show the effect of something at load in a CI/CD component. Because one of the things that I’ve run into is like I’ve got this great idea for how this code should work and when I deploy it, it works great. The like a thousand people touch it all at once and it doesn’t work right anymore. I’d love to have some tool along the way that can test things out of load and like show me something that I could fix before all those people touch it. [00:41:57] BL: Yes, that would be a good tool to have. So John, anything else for you? [00:42:02] JH: I’ll open a can of worms right at the end and say the biggest problem here is probably going to be data when we have a lot of systems we need to talk to each other and we need the data to align between those systems and we have now proliferation of environments and clusters. Like how do we get that data reliably into the place that it needs to be to make up testing robust enough to get things out there? It’s probably an episode on some – [00:42:23] BL: Yeah, that’s a big conversation that if we could answer it, we wouldn’t working at VMware. We would have our own companies doing all these great things. But we can definitely iterate on it. So with that, I think we’re going to wrap it up. Thanks for listening to the Kubelets. I’m Bryan Liles, and with me today was Nicholas Lane and John – Yeah, and John Harris. [00:42:47] JH: Thanks everyone. [00:42:47] BL: All right, we’ll see you next time. [END OF EPISODE] [00:42:50] ANNOUNCER: Thank you for listening to The Podlets Cloud Native Podcast. Find us on Twitter at https://twitter.com/ThePodlets and on the http://thepodlets.io/ website, where you'll find transcripts and show notes. We'll be back next week. Stay tuned by subscribing. [END]See omnystudio.com/listener for privacy information.
David Farley, Executive Chairman at Matrix Commodities , has been around agriculture his whole life. He started off his career in agriculture as a jackaroo, which is a young man working on a sheep or cattle station to gain experience to become an owner one day. Then, David went on to work as a farm manager at Colly Cotton. Seven years later, he worked his way up to managing director then CEO growing the company to over 600 people. Not too long… Continue Reading ›› The post Grain Markets in 2020, Building a Successful Culture, and the Importance of Family appeared first on Farmtank.
Guest: David R. Farley, M.D. Host: Darryl S. Chutka, M.D. (@ChutkaMD) What should you be looking for in your physical exam? How do you differentiate a femoral hernia from a swollen lymph node? Dr. David Farley breaks down common hernias, the importance of the history and the exam, when imaging studies like a CT scan may be needed, the impact of smoking, weight gain, and life style on incision healing, and when someone should be referred for surgery. Connect with the Mayo Clinic’s School of Continuous Professional Development online at https://ce.mayo.edu/ or on Twitter @MayoMedEd.
P. Brendon Lundberg, a previous chronic pain suffer, co-founded Radiant Pain Relief Centres, along with David Farley, MD, a Harvard-MIT trained physician, with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain. Combining a mission to change the way chronic pain is understood treated with deep experience in healthcare management, marketing, business development and sales, Brendon opened Radiant Pain Relief Centres in Portland, Oregon, USA, in February 2014. Following the success of the first center, they are laying out a plan for expansion to open new centers in new markets nationally and internationally to help millions find relief without drugs, needles, surgery or side effects. Learn more about your ad choices. Visit megaphone.fm/adchoices
Hi friends! I’m thrilled to welcome P. Bredon Lundberg to the show today to talk about something extremely prevalent and sometimes misunderstood: pain. How big is the chronic pain problem? What’s the difference between acute and chronic pain? Doesn't pain mean something is wrong? And the brain’s incredible ability to change its perception of pain in the body. Here’s a little bit about Brendon: P. Brendon Lundberg, a previous chronic pain suffer, co-founded Radiant Pain Relief Centres, along with David Farley, MD, a Harvard-MIT trained physician, with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain. Combining a mission to change the way chronic pain is understood treated with deep experience in healthcare management, marketing, business development and sales, Brendon and Dr. David Farley opened Radiant Pain Relief Centres in Portland, Oregon, USA, in February 2014. Following the success of the first center, they are laying out a plan for expansion to open new centers in new markets nationally and internationally. Their story and vision for the future of pain management can be understood by reading their book, Radiant Relief – A Case For A Better Solution To Chronic Pain. Previous to founding Radiant, Brendon played key operational and business development roles for two Portland-Area Portland Business Journal and Inc. Magazine Growth Award winning companies, and was the Director of Sales and Marketing for another Portland-based medical device start-up. Brendon holds a BS in business marketing and an MBA. Some of the things we discuss in this episode: What is the latest scientific understanding of pain and why more doctors or therapies aren't utilizing this recent science Neuroplasticity and the brain’s potential to learn and change How Radiant's Scrambler Therapy works Does changing the brain's perception of pain create more risk? Brendon also gives some incredible insight on cultivating happiness, improving productivity, and his entrepreneurial journey Resources from this episode: Radiant Relief The Radiant Relief book Connect with Brendon on Instagram Brendon Burchard high performance academy If you’re working out at home this summer or traveling, click here to get 21 days FREE of Les Mills On Demand. Thank you so much for listening and for all of your support with the podcast! Please leave a rating or review if you enjoyed this episode. If you leave a rating, head to this page and you’ll get a little “thank you” gift from me to you. You can listen and subscribe to the podcast on iTunes, Stitcher, and Google Play.
This week Cindy is joined by P. Brendon Lundberg to discuss pain management and treatment for Lyme Disease and other chronic health issues. P. Brendon Lundberg, a previous chronic pain suffer, co-founded Radiant Pain Relief Centres, along with David Farley, MD, a Harvard-MIT trained physician, with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain.
P. Brendon Lundberg, a previous chronic pain suffer, co-founded Radiant Pain Relief Centres, along with David Farley, MD, a Harvard-MIT trained physician, with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain. Their story and vision for the future of pain management can be understood by reading their Amazon Bestselling book, Radiant Relief - A Case For A Better Solution To Chronic Pain. Inc. Magazine called the book, “A Manifesto” and “an epic example of how to create a movement”. “get in action. There is never a perfect time, there is never a perfect amount of money or circumstance and there is never going to be anybody that believes in the way that you believe in it. So if you have in your heart or in your minds some idea do it, start it, put it in action. You might not have total clarity as to how it's going to unfold or what is going to do what it can become but that's okay. That clarity comes through the activity. I say just getting action, make it happen and you will be glad you did”…[Listen for More] Click Here for Show Notes To Listen or to Get the Show Notes go to https://wp.me/p6Tf4b-6Xv
P. Brendon Lundberg, a previous chronic pain suffer, co-founded Radiant Pain Relief Centers, along with David Farley, MD, a Harvard-MIT trained physician, with a vision to build the safest, most consistently effective and appealing solution to the epidemic of chronic pain. We discuss: What combination of factors would support a pain sufferer to become a co-founder [1:26] The safest, most consistently effective solution to chronic pain [3:30] What the physical location of a treatment center has to do with the solution it offers [5:47] How to become an expert at clinical delivery and bring back joy into people’s lives [8:30] Changing industry: It sounds too good to be true [11:32] An epic example of how to create a movement [13:17] The apple’s seed has the same potential to become an apple tree as an apple tree does [18:00] The snowball effect of investing locally [22:58] Combining a mission to change the way chronic pain is understood treated with deep experience in healthcare management, marketing, business development and sales, Brendon and Dr. David Farley opened Radiant Pain Relief Centers in Portland, Oregon, USA, in February 2014. Following the success of the first center, they are laying out a plan for expansion to open new centers in new markets nationally and internationally. Their story and vision for the future of pain management can be understood by reading their Amazon Bestselling book, Radiant Relief – A Case For A Better Solution To Chronic Pain. Inc. Magazine called the book, “A Manifesto” and “an epic example of how to create a movement”. Learn more about P. Brendon Lundberg at Facebook (https://www.facebook.com/RadiantPainReliefCentres/) . Brief Description of Gift Free digital download of my book: Radiant Relief, A Case For A Better Solution to Chronic Pain URL for Free Gift https://radiantpainrelief.com/smashing (https://radiantpainrelief.com/smashing) Facebook Twitter LinkedIn 31Shares
P. Brendon Lundberg discusses new technology that treats chronic pain.Finding proper treatment for chronic pain sufferers is a challenge. The recent opioid crisis has proven that pharmaceuticals aren’t an option for long-term pain management and there are few therapies that prove successful. P. Brendon Lundberg, a former chronic pain sufferer, has taken a technology-driven approach to treating chronic pain. While many in the pain management industry treat the tissues surrounding the pain, he understands that pain is a phenomenon of the brain and has started treatment there. He along with David Farley, MD, a Harvard-MIT trained physician, has developed technology that acts as an artificial nerve, sending signals to the brain to relax. The result is pain relief that lasts several weeks, months, and sometimes, indefinitely. Listen as P. Brendon Lundberg joins Dr. Holly Lucille to discuss how to use this new technology to treat chronic pain.
P. Brendon Lundberg discusses new technology that treats chronic pain.Finding proper treatment for chronic pain sufferers is a challenge. The recent opioid crisis has proven that pharmaceuticals aren’t an option for long-term pain management and there are few therapies that prove successful. P. Brendon Lundberg, a former chronic pain sufferer, has taken a technology-driven approach to treating chronic pain. While many in the pain management industry treat the tissues surrounding the pain, he understands that pain is a phenomenon of the brain and has started treatment there. He along with David Farley, MD, a Harvard-MIT trained physician, has developed technology that acts as an artificial nerve, sending signals to the brain to relax. The result is pain relief that lasts several weeks, months, and sometimes, indefinitely. Listen as P. Brendon Lundberg joins Dr. Holly Lucille to discuss how to use this new technology to treat chronic pain.
In this Happier After Hours Bonus Episode you'll learn about travel through the lens of the destination with travel public relations consultant Jessica Parker. How does a place become a “brand” and how does one get to the essence of a destination? This is a follow up episode to #031 with travel writer David Farley about travel and transformation and the lessons of philosopher George Santayana. #thehappierhour
This episode kicks of The Happier Hour Season 2 as well as our conversations on DISCOVERY. You'll learn how travel writer David Farley and the philosopher George Santayana can help us find more meaning in our lives by looking at how and why we travel. You'll also hear unconventional advice about travel writing and the ways in which travel has the ability to transform us. #thehappierhour Show notes: thehappierhour.org Patreon: patreon.com/thehappierhour Facebook: @thehappierhour Twitter/IG: @MissMMcCarthy
Suffering from chronic pain? P. Brendon Lundberg and Dr. David Farley, founders of Radiant Pain Relief Centres, have developed a new approach to chronic pain. Learn more in this short interview and visit https://radiantpainrelief.com/ for more information.
Beautiful Irish flute music and why open G# mechanism could be making a comeback! Welcome to Talking Flutes 'Extra'. Following the response from the interview with William Dowdall two weeks ago, we indugle ourselves for a little with some beautiful flute music from Ireland along with an interview with the technical director of TJ flutes David Farley. David speaks about his love for historic flutes and why he has designed and built a new affordable flute with open G# mechanism, his enthusiasm for looking back in to history, as well as forward on instrument design, and gives some advice on questions which have been sent in on Care & Mantenance of the instrument. Thank you for your lovely emails with comments and suggestions for future podcasts. Please keep them coming to flutepodcasts@gmail.com Talking Flutes and Talking Flutes 'Extra' are flute podcast productions by Trevor James flutes. For more information www.trevorjamesflutes.com
This week on TF Extra I'm talking to L.A based flute player and extremely popular flute social media influencer Gina Luciani about how she started on the flute and also her latest flute and entrepreneurial projects. We also have a 'Joke of the week' from "Graeme in London Town" and some listener responses from last weeks podcast. This is the last 'Inbetweeny' podcast from me as next week I hand the reigns back to the lovely Clare Southworth for her 'Talking Flutes' Series 2. TF Extra pods return on Monday 11th June, where I'll be in dialogue with William Dowdall (Professor of flute at the Royal Irish Academy of Music in Dublin) about all things flutey, the wonderful Russian flute player Ivan Alexhin, I'll have a discussion with flute technical director for TJ flutes David Farley about flute design, and following the demand from last week's podcast, I'll be speaking again to the 'ball of energy' that is José Valentino. All links to Gina Luciani's social media and music can be found by visiting www.ginaluciani.com Thank you for putting up with me for the last few weeks and I look forward to speaking to you again soon. Jean-Paul 'Talking Flutes' and 'TF Extra' are podcast productions by Trevor James flutes. For more information visit www.trevorjamesflutes.com
04/29/2018, Rev. David Farley, Scripture: 1 John 3:16-24; John 15:1-8
Brendon Lundberg is co-founder of Radiant Pain Relief Centres whose vision is to build the safest, most consistently effective, and appealing solution to the epidemic of chronic pain. Combining a mission to change the way chronic pain is treated, Brendon and Dr. David Farley opened Radiant Pain Relief Centres in February 2014 and have plans to open centres in new markets, both nationally and internationally. Previous to founding Radiant Pain Centre, Brendon played key operational and business development roles for two other businesses and was the Director of Sales and Marketing for a medical device start-up. What you will learn in this episode: Why a Regulation A-Plus Offering might apply to your business How to learn more about the Regulation A-Plus Offering process The importance of having the right mindset The benefits of setting your day with intention How having ambition without the right discipline can lead to being unfocused The importance of building relationships and connecting with people Daily strategy: knowing and applying the key performance measurements that matter Why you should “live into who you want to be” When starting a new venture, don’t wait for it to be perfect, just jump in The importance of surrounding yourself with people who can help you How to contact Brendon: Website: radiantpainrelief.com Twitter: @radiantrelief
In episode 5 of Troubleshooting Agile we discuss the Third Agile Principle: 'Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.' Evolution in our thinking, since the Agile Manifesto was written back in 2001, makes what was once considered 'shorter timescales' seem laughable now, but, when retrospecting, 'working software frequently' remains one of the core agile disciplines. But, as Squirrel and Jeffrey highlight through various client stories, it is far from easy to implement continuously. We hear where, why and how so many companies fail to fully employ this principle, and Squirrel and Jeffrey discuss some interesting techniques to overcome common problems - from slicing up elephant carpaccio to employing continuous integration with nothing more than a rubber chicken. *We apologise for a few sound difficulties at the start of the episode with Jeffrey's mic. Stick with it and they soon pass.* *** Squirrel and Jeffrey have told us which common obstacles they regularly witness that prevent organisations from delivering working software frequently. Now we want to hear from you guys on the matter. You can leave your answers in the comments below, you can email us at agile@troubleshootingagile.com, or you can find a poll on our Twitter feed @TShootingAgile. What are the obstacle for your organisation to delivering working software frequently? 1. The tech team aren't offering to do this, or don't know how. 2. Customers (external or internal or both) don't know it's possible or how to use it if offered. 3. Both 1. and 2. 4. Neither - we already deliver frequently! *** SHOWNOTES: -Agile Manifesto Principles - http://agilemanifesto.org/principles.html -Continuous Delivery, by Jez Humble and David Farley - https://martinfowler.com/books/continuousDelivery.html -Continuous Delivery - https://continuousdelivery.com -CITCON - https://citconf.com -James Shore's blog: "Continuous Integration on a Dollar a Day - http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html -Alistair Cockburn's blog: "Elephant Carpaccio" - http://alistair.cockburn.us/Elephant+carpaccio *** We'd love to hear any thoughts, ideas or feedback you have regarding the episode (or regarding anything else for that matter). You can email us, here: agile@troubleshootingagile.com Or send us a tweet, here: twitter.com/TShootingAgile Or you can find our website, here: troubleshootingagile.com/ Also, here is a link to our iTunes: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2 If you feel like liking, Sharing and/or Subscribing, we'd really appreciate it.
Episode 31: Dr. David Farley Dr. Kohler speaks with surgical educator and Wisconsin Alum, Dr. David Farley. Dr. Farley has been a surgical educator at the Mayo Clinic for nearly two decades. His innovative approach to surgical education uses games and challenges to help students deepen their understanding of the core material. In addition, he’s also been extremely crafty when it comes to building surgical simulators. This is an episode you won’t want to miss! Recorded 6/7/2017
In the third episode of our new podcast we hear from Flood's Designer, David Farley, about the challenges of staging a play on water as well as continuing the story from Part2. Abundance.
Shannon Farley, Director of Marketing and Co-Founder Shannon Farley started her career with a progressive agency in the Bay area, developing creative for clients such as Nike, Toyota, Microsoft, Warner Brothers and MGM. She learned how to build great brands from some of the best in the industry. She then dove head first into a startup, helping nurture the design, marketing and branding of a fledgling company into a 600-person SaaS leader. She’s freelanced, led corporate teams, and rolled up her sleeves when things need to get done. She realized that to truly impact a business, ideas must generate results that engage consumers and drive sales. As businesses continue to shift away from traditional marketing, Shannon brings a unique and creative approach to the marketing mix with both sides of the brain. A process that blends insightful research, innovative strategic thinking, and conceptually driven executions. Full Bio on LinkedIn - https://ca.linkedin.com/in/shannonmfarley David Farley, CEO and Co-Founder David Farley previously founded Anatomic Global, formerly Anatomic Concepts, in 1989 as a supplier of foam support devices and mattresses to the medical industry. Re-named in 2007, Anatomic Global is the world’s number one original equipment manufacturer and supplier of memory foam products on the Internet, fulfilling an average of 850,000 orders each year directly with U.S. Consumers. In 2008, the company launched Ecomfort Mattress, an environmentally friendly sleep line, which has fueled record sales growth for the company. In 2009 he was appointed chairman of the “Green Initiative” of the Specialty Sleep Association. The Green Initiative is a process designed to identify, define and standardize how mattress manufacturers and retailers label “green” and natural sleep products. Farley has more than 25 years of experience in the foam industry and holds 27 patents on the anatomic uses of foam. Farley graduated from California State Polytechnic University with a degree in Manufacturing Engineering. He holds a MBA from Pepperdine University. Full Bio on LinkedIn - https://www.linkedin.com/in/david-farley-0667035b https://www.luxisleep.com/ https://www.facebook.com/LuxiSleep https://twitter.com/LuxiSleep
Mattress industry veteran David Farley and daughter Shannon Farley have teamed up to introduce a customizable mattress, Luxi by SmartSleep Inc. The new mattress is sold direct to consumers at LuxiSleep.com. It has four layers, consisting of polyurethane foam, memory foam, latex and base foam. The zip-off mattress cover allows owners to rearrange the top comfort layers to suit personal preferences.As sleep experts, we’ve been designing and manufacturing specialty foam mattresses since before Tempurpedic landed in America. Our innovation has earned us over thirty (30) international and domestic patents, and we’re proud to own every decision along the supply and production chain. From innovative design and sourcing raw materials to packaging and shipping, we are as manufacturer-direct as it gets, from our home to yours.
Mattress industry veteran David Farley and daughter Shannon Farley have teamed up to introduce a customizable mattress, Luxi by SmartSleep Inc. The new mattress is sold direct to consumers at LuxiSleep.com. It has four layers, consisting of polyurethane foam, memory foam, latex and base foam. The zip-off mattress cover allows owners to rearrange the top comfort layers to suit personal preferences.As sleep experts, we’ve been designing and manufacturing specialty foam mattresses since before Tempurpedic landed in America. Our innovation has earned us over thirty (30) international and domestic patents, and we’re proud to own every decision along the supply and production chain. From innovative design and sourcing raw materials to packaging and shipping, we are as manufacturer-direct as it gets, from our home to yours.
This week we visit with another designer from across the pond, it's Tony nominated Scenic and Costume Designer, David Farley! David was in town finally bringing 'Daddy Long Legs' to New York after playing around the globe for 6 years. He tells us about the evolution of the design and the process of modifying the set to fit different theatres. David and Cory dig into the artistic, practical and economical differences of being a designer in the US vs the UK and they chat about David's award winning work on 'Sunday in the Park...', why designing Josh Groban's tour was more difficult than you would think, designing in the Festival Theatre at Stratford and the qualities he loves in his frequent collaborators John Caird, Trevor Nunn, and John Doyle. But David isn't all work…he also shares insight into being a designer on the road with an infant back home and why he's passionate about his garden. It's a great show, but mainly because of how adorably he pronounces ‘aluminum.' Grab a seat in the stalls, raise the gauze and enjoy this week's panto!
Before we begin... have you gone to iTunes or Stitcher to give us a review? It takes so little time and would sure help us a lot. Thanks! New: Agile Coach Camp US West, April 10-12, 2015 - AgileGathering.com for more info Visit our brand new forums on the AgileCoffee website For this episode, Vic and Jon are joined by Larry Lawhead (lawhead5@hotmail.com), Dale Ellis (@thedigitaldale) and Brett Palmer (@brett_palmer) for peaceful morning of Agile and coffee. Today our heroes discuss the following topics: Why is IT Ops the next big thing? We discussed Jez Humble and David Farley's Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation Coach Crisis Corner - Jon wants to build a databank of shared coaching problems (not necessarily the "solutions"). To help him, we've started a Coach Crisis topic in our new forums area. Stop by to submit your problem scenario. Larry's promise to his CEO - Jeff Sutherland's new book (Scrum: The Art of Doing Twice the Work in Half the Time) has inspired Larry promise his CEO that as sales goes up, the cost of production will go down because the team will be better at what they do. Kanban Standup meeting formats - What techniques (beyond "walking the board") can be used for kanban teams? Reach out to Vic (@AgileCoffee) and Jon (@WaterScrumBan) on Twitter – and use the hashtags #askAgileCoffee or #tellAgileCoffee to interact with us on an upcoming episode.
This Week in Travel - Travel News Podcast. Regular hosts Jen Leo and Chris Christensen are joined by this week's guest: David Farley, author of An Irreverent Curiosity: In Search of the Church's Strangest Relic in Italy's Oddest Town
A few years back, David Farley wrote a book called “An Irreverent Curiosity”. The book details the history and disappearance of the foreskin of Jesus Christ. Farley spent years doing research for this book and it is amazing. In 2014, there will be a documentary about the Holy Foreskin brought to you by National Geographic, … Continue reading →
Today I have the great pleasure of interviewing one of my dearest friends in the business. He's a major fixture in the NY travel-writing world, he hosts a popular monthly reading series called Restless Legs, he's a speaker at most large travel events around the area, & he teaches a travel-writing course at New York University. Let's see, what else... He's also a contributor to Afar magazine & The New York Times, & is the author of "An Irreverent Curiosity" that is currently being made into a documentary by National Geographic International. But he's also one of the most humble guys you'll ever meet. So who is this character with the wild hair & thick glasses? He's known simply as Farley. Make sure to keep an eye out for his documentary in 2014, follow him online at www.dfarley.com & on Twitter @davidfarley, & you can find the next date for his Restless Legs Reading Series by searching for the group on Facebook. Who knows, you may even stumble into me there!
Rick invites some of his European friends to compare the beers of Europe and discuss the cultures that go with them, and travel writer David Farley talks about an eccentric hill town, not far from Rome, where a generation of bohemians share residency with a centuries-old mystery relic the Vatican would rather not talk about. For more information on Travel with Rick Steves - including episode descriptions, program archives and related details - visit www.ricksteves.com.
Enregistré le 17 novembre 2011 Telechargement de l’episode LesCastCodeurs-Episode–49.mp3 Flattr-ez nous (dons) sur http://lescastcodeurs.com/ Invités Nicolas Martignol http://www.touilleur-express.fr/a-propos-de-lauteur/ Zouheir Cadi http://twitter.com/ZouheirCadi News RHoK http://www.rhok.org/ En Belgique le 3 et 4 décembre http://www.rhok.be/ Devoxx 2011 Infinispan http://www.jboss.org/infinispan/ Cloud Foundry http://www.cloudfoundry.com/ Gerrit http://www.devoxx.com/display/DV11/Code+Review+with+Git+and+Gerrit Android http://www.android.com/developers/ JavaFX http://javafx.com/ Play Framework http://www.playframework.org/2.0 David Farley http://www.devoxx.com/display/DV11/David+Farley Cassandra http://cassandra.apache.org/ Redis http://redis.io/ MongoDB http://www.mongodb.org/ Joe Nuxoll http://joeracer.blogspot.com/ Code story http://www.code-story.net/ Langages Scala http://www.scala-lang.org/ Groovy http://groovy.codehaus.org/ Ceylon http://ceylon-lang.org/ Fantom http://fantom.org/ Kotlin http://confluence.jetbrains.net/display/Kotlin/Welcome Devoxx France Devoxx France du 18 au 20 avril 2012 a Paris http://www.devoxx.fr/ http://www.touilleur-express.fr/2011/11/16/lhistoire-de-devoxx-france-2012/ Startup weekend http://startupweekend.org/ Enregistrement live du 50eme episode au ParisJUG Le 13 decembre, on enregistra le 50eme épisode en direct au ParisJUG. Venez nombreux! http://parisjug.org/xwiki/bin/view/Meeting/20111213. Note pour les habitués, ça ne sera pas a l’ISEP, donc faites gaffe :) Nous contacter Contactez-nous via twitter http://twitter.com/lescastcodeurs sur le groupe Google http://groups.google.com/group/lescastcodeurs ou sur le site web http://lescastcodeurs.com/ Flattr-ez nous (dons) sur http://lescastcodeurs.com/
This week’s guest are:David Farley, author of An Irreverent CuriosityRobert Reid of the BBC (Lonely Planet) and ReidOnTravel.com
What appears gross to one person, is sometimes a gourmet delicacy for another. Rick puts our appetites to the test as an entrée to understanding a culture while two guides who specialize in gourmet travels from their home base in Tuscany describe the comfort foods of Western Europe and travel writer David Farley tells us about his recent foodie trip to Saigon. For more information on Travel with Rick Steves - including episode descriptions, program archives and related details - visit www.ricksteves.com.
Appreciate beer like a European along with Rick in a session comparing the beers and cultures of Europe. Travel writer David Farley also tells us about an eccentric hill town, not far from Rome. It's where a generation of Bohemian residents share space with a centuries-old mystery about a relic the Vatican would rather not talk about. For more information on Travel with Rick Steves - including episode descriptions, program archives and related details - visit www.ricksteves.com.
With a return appearance special guest David Farley (@davidfarley) from http://www.dfarley.com/Delta Air Lines charges extra fees for passengers who use travel agentshttp://www.consumertraveler.com/today/delta-air-lines-charges-extra-fees-for-passengers-who-use-travel-agents/Gadling TV's "Travel Talk," 001: Carnival, flight cancellations, Somaliland, airfare blunders, and more! | Gadling.comhttp://www.gadling.com/2010/02/17/gadling-tv-001-carnival-flight-cancellations-somaliland-ai/
© 2020-2025 Ivy Podcast Discovery LLC
