Podcasts about luke you

Selling your business can feel lonely and emotional. You are parting with the thing you have devoted a significant portion of your life to, and that can feel hard. But beyond that is an opportunity to re-invent yourself. In this episode I speak with Luke Winter, a creative director who recently sold his shares in the video agency Wallbreaker. Luke shares with great honesty the emotional toll the sale has had on him. From the moment of knowing it was time to try something new to a final week full of doubt, Luke experienced it all. Now, with the opportunity to explore his next steps, Luke emphasis the need for support and understanding during this transformative time.   "It was a lonely experience." – Luke   You'll hear about:  The emotional toll of selling is often underestimated. It's important to have support during the selling process. Many entrepreneurs feel lonely when selling their business. Routine changes can impact mental health during transitions. Navigating the sale requires clear communication between parties. Connect with Luke Winters:   LinkedIn - https://www.linkedin.com/in/luke-winter-75a2885a/   Connect With Julie Wilkinson   LinkedIn - https://www.linkedin.com/in/juliewilkinson-accounting/ Tik Tok – https://www.tiktok.com/@wasolutions YouTube - https://www.youtube.com/channel/UCUvq6gfNoP_4dfIJulL6C6A Facebook - https://www.facebook.com/wilkinsonaccountingsolutions Website - https://wilkinsonaccountingsolutions.co.uk/   Find out more about our brilliant sponsor Acquisition Masters here - https://www.acquisitionmasters.co.uk/   Before you go, don't forget to leave a comment and review if you got something out of this episode!

Here is the full - AND VERY FRANK - conversation between Alex Andreou and More In Common's chief Luke Tryl on all four Conservative leadership hopefuls. And if you think “why should I care?” - this is why: our entire political system, for good or ill, is adversarial in nature. The quality of the opposition to the government shapes policy. Ideas that have had their tyres properly kicked, will always be better ideas.  Luke: "What we hear from our focus groups is that Kemi is refreshing." Alex: "So is an enema." Luke: "You're being mean." Want some more? You can track us down on Facebook and Twitter as @quietriotpod, or hop over to Bluesky for our starter pack action. If email is your thang, our address is quietriotpod@gmail.com. And we even have a website, www.quietriotpod.com. We make all our content available free to everyone, regardless of ability to pay. But we depend on those who can afford to support us with a few pounds doing so. You can do so on Ko-Fi by clicking HERE. Oh, we are Naomi Smith, Alex Andreou and Kenny Campbell, in cahoots with SandStone Global. But you knew that. x Learn more about your ad choices. Visit podcastchoices.com/adchoices

Rachel and Luke (see episode #28 Keto Vegan Kickstart: Two Weeks with Luke and Kingsley - Unveiling Challenges, Tips, and Laughter!) meet for a drinks eve and decide to record for a podcast too! This is before Rachel launched the podcast but was recording as much as she could for future episodes.   Rachel has waited until she retired from teaching before allowing this one to go ‘out there'. Definitely not acceptable to show students a tipsy teacher!   She'd had a G&T before she started! She wasn't using measures. She makes a mess She swears She's gets it wrong more than once   Best Moments “I can feel it getting colder, as I'm shaking. Coffee is still going everywhere!” “Let's just taste that to see what it is like and see how cold it is.” Luke: “When does the sugar-syrup go in?” “And it helps to put the sugar syrup in as well!!!!” “hmmm, that was too much sugar syrup, I don't like things too sweet.” “This could be one of the bloopers reels!” “Hey, it's Rach, the vegan martini!” Luke: “You can be a vegan martini, you can identify as whatever you want!”   Frangelico – carb count in 1oz of Frangelico there are 11g of carbs!!!!!!! Sugar free syrups: Amazon do a selection. Frangelico link – I'm not giving a link because it's almost pure sugar!  

This week, our hosts welcome a man (gasp!) into the studio to discuss the pod's most-requested film, How to Lose a Guy in 10 Days (2003). Starring Kate Hudson and Matthew McConaughey (and an exciting Kathryn Hahn cameo), this approach to "the Bet" trope has our hosts and special guest Luke questioning which behaviors constitute poor dating etiquette specifically vs. generally unhinged human conduct. (Talking during a movie is just bad manners, whether or not you're on a date!) A huge thank you again to Luke: You're a shining example to all men who dream of speaking into microphones—we owe you one (a kidney)! Connect With Us Instagram: https://www.instagram.com/loveatfirstscreening/ Email: loveatfirstscreening@gmail.com Production Hosts: Chelsea Ciccone and Madison Hill Guest Extraordinaire: Senator Tori Green, South Carolina Music: Good Steph Artwork: Chelsea Ciccone Social Media: Marissa Ciccone About the Show An examination of classic tropes and iconic characters pits connoisseur against cynic—one romantic comedy at a time. The cinematic world of love and laughter had rom-com enthusiast Madison head over heels from the time Harry met Sally. For genre skeptic Chelsea, however, it's been a grueling enemies-to-lovers plot. In Love at First Screening, Madison introduces Chelsea to all the fan-favorite love stories she's never wanted to watch. One friend's passion might be the other's displeasure, but doesn't love conquer all? Tune in every Wednesday to find out. --- Send in a voice message: https://podcasters.spotify.com/pod/show/loveatfirstscreening/message

Carmen and Brendan present a collection of poems from around Melbourne, including recent listener contributions.This episode contains pieces by:Luke You and the Zine MistakesStephanie PowellSteven AtkinsonCorinne PhillipsBrad EvansIf you would like to contribute a poem or story to the show, please click here. 

If you've been listening to Stay Paid for a while, then you've heard me mention my brother Stephen. He's a broker-agent and, at the end of 2021, four of his best agents walked out on him. Kudos to his courage, because Stephen shares why things went wrong and how easy it would be for other broker-agents to make the same mistake; how he got himself out of a full-blown pity fest; the marketing strategies he used to complete 320 transactions in spite of what happened; and the easy script he uses to get cold calls to give him the information he needs. - Luke   You can get more in-depth information and added details not included in the episode from our show notes. Visit www.staypaidpodcast.com.    Connect | Resources Email: stephen@acreebrothersrealty.com Instagram: @acreebrothers Phone: 434-607-2976 Free webinar + resources: The #1 Lead-Generating Facebook Ad to Run in 2022 - https://bit.ly/3M6FCc8   0:00     Introduction 2:41     Stephen's business bio 3:05     What happened that you lost 4 agents? 5:12     How did you get over that? [Golden Nugget] 7:28     Where in the business did you focus to recover? 9:51     What is the vision now? 10:41   What is your marketing strategy now? 12:35   How are you growing awareness among the people in your farm? 13:45   The Halo Effect: Benefit of reaching out to farm 15:25   What have you seen from running Facebook ads? 17:39   What is your script for following up on Facebook ads? 23:33   How do you find out a lead's motivation level? 25:23   Dissecting the value proposition in the script 26:18   Tip for following up: Don't show all your cards [Golden Nugget] 28:18   How do you overcome the reluctance of calling internet leads? 32:07   Advice Stephen would give to an agent looking for success 35:59   Action Item   To learn how to generate more referrals and repeat business, visit: www.remindermedia.com

Pre-gaming topics Gomer: Neighbors are so freaking frustrating right now with their drugs and cussing in front of my kids, with their VH1 and rap music and fast cars! Luke: You know, Gomer, there is a Rent Crisis going on in a America and you just demonized renters. (war ensues) Luke's real pre-game topic: The Multiverse of Madness: we're hair-metal and grunge is on its way. Main Topic When our economy corrupts our souls

Being an educator is always hard work. As we enter the third school year impacted by Covid, being an educator is harder than ever. Before the start of the 2021-22 school year, we sat down with a veteran high school history teacher to discuss the upcoming school year. Filled with equal parts optimism and concern for the year ahead, Elizabeth Rasmussen shares the importance of taking charge, engaging in advocacy and being the change she wants to see. Episode 9 Show Notes: Guests Show Resources Transcript Guest Elizabeth Rasmussen, History teacher Polk County Resources Polk Schools have more than 400 openings (Lakeland Ledger) FL Grapples with Record COVID Surge (NBC News) FEA's Safe Schools Report Florida Has A Critical Shortage Of Teachers. Here's Why. (WFME, NPR) featuring FEA VP Carole Gauronskas. Why is FL DOE behind on getting billions of federal dollars to schools recovering from COVID pandemic? Transcript [00:00:00] Announcer: Sharon: You're listening to “Educating from the Heart.” Thank you for joining our lively conversations with teachers, support professionals, parents, and students, as they share issues that matter most in our public schools. Here are your hosts, Tina Dunbar and Luke Flynt. [00:00:27] Tina Dunbar, Host: Welcome back to “Educating from the Heart,” the Florida Education Association podcast for teachers, support professionals, parents, community leaders and students. Together, we engage in monthly conversations, exploring all aspects of education and the impacts of policy decisions on our students and their schools. I'm Tina Dunbar, and with me is my co-host, Luke Flynt. Hey, Luke! [00:00:53] Luke Flynt, Host: Hey, Tina. [00:00:54] Tina: Good to see you again. [00:00:55] Luke: You too. [00:00:56] Tina: Well, after our brief summer break, we're back to kickoff season two of “Educating from the Heart.” I am so excited, and I know you are too, because we've got a lot planned for this season. [00:01:07] Luke: Absolutely, Tina. This season, we're going to talk about everything from teaching accurate history and civics in today's K-12 classrooms, to the attack on academic freedom at Florida's colleges and universities. And, of course, during the legislative session, we will keep everybody updated on what's happening in the State Capitol. But let's back up a bit and talk about this month's episode. [00:01:31] Tina: Well, Luke, as you know, back in July FEA held its annual professional development gathering called Summer Academy. It's our largest training for teachers and support professionals from across the state. And it was held in-person and, you know, everybody was looking forward to that. So, we decided to take the podcast on the road. Well, educators generally take advantage of this event and network with their colleagues, and one of the top conversations dealt with the new school year and the unknowns surrounding the virus. Luke, all school employees, regardless of where they work, had been looking forward to a fresh start this year and a return as close as possible to normal for this school year. [00:02:16] Luke: We open season two with a high school history teacher from Polk County who has been in the classroom for 14 years and seen a lot of change during that time. Elizabeth Rasmussen shared her hopes for her students, as well as her fears for what this school year could bring. “Raz” as she is affectionately known, spoke about the importance of unionism and legislative advocacy, but she begins by sharing what inspired her to become a teacher and how her students motivate her to remain in the profession, despite its many challenges. [00:02:50] Elizabeth R.: When I look back at the reason why I do what I do: It's my kids. It's kids like, and these are pseudonyms, because like Veronica and Juan that I've written about that really inspired me to keep educating, and I'm actually getting a PhD right now. So,

MLOps community meetup #52! Last Wednesday we talked to Luke Feeney and Gavin Mendel-Gleason, TerminusDB. // Abstract: A look at the open-source 'Git for Data' landscape with a focus on how the various tools fit into the pipeline. Following that scene-setting, we will delve into how and why TerminusDB builds a revision control database from the ground up. // Takeaways - Understanding the 'git for data' offering and landscape - See how to technically approach a revision control database implementation - Dream of a better tomorrow // Bio: Luke Feeney Operations Lead, TerminusDB Luke Feeney is Operations Director at TerminusDB. Prior to joining TerminusDB, Luke worked in the Irish Foreign Ministry for a number of years. He served in Ireland’s Permanent Mission to the UN in New York and the Embassies in South Africa and Greece. He was Ireland’s acting Ambassador to Greece for 2016 and 2017. Luke was also the Head of the Government of Ireland’s Brexit Communications Team and the Government Brexit Spokesperson from 2017 to 2018. Gavin Mendel-Gleason Chief Technology Officer, TerminusDB Dr Gavin Mendel-Gleason is CTO of TerminusDB. He is a former research fellow at Trinity College Dublin in the School of Statistics and Computer Science. His research focuses on databases, logic and verification in software engineering. His work includes contributing to the Seshat global historical databank, an ambitious project to record and analyse patterns in human history. He is the inventor of the Web Object Query Language and the primary architect of TerminusDB. He is interested in improving the best practices of the software development community and a strong believer in formal methods and the use of mathematics and logic as disciplines to increase the quality and robustness of software. // Final thoughts Please feel free to drop some questions you may have beforehand into our slack channel (https://go.mlops.community/slack) Watch some old meetups on our youtube channel: https://www.youtube.com/channel/UCG6qpjVnBTTT8wLGBygANOQ ----------- Connect With Us ✌️------------- Join our Slack community: https://go.mlops.community/slack Follow us on Twitter: @mlopscommunity Sign up for the next meetup: https://go.mlops.community/register Connect with Demetrios on LinkedIn: https://www.linkedin.com/in/dpbrinkm/ Connect with Luke on LinkedIn: https://www.linkedin.com/in/luke-feeney/ Connect with Gavin on LinkedIn: https://www.linkedin.com/in/gavinmendelgleason/ Timestamps: [00:00] MLOps Announcements [00:17] Slack Community [00:59] Luke and Gavin's Presentation Style [01:34] MLOps Community Twitter, LinkedIn and Youtube [01:45] Introduction to Luke Feeney and Gavin Mendel-Gleason [04:35] Luke: You wanted Git for Data? [05:17] Deep Breath || Is there a Git for Data? [06:30] What is Git for Data? [08:55] Four Big Buckets [28:43] Jupiter Notebook [30:20] Gavin: Collaboration for Structured Data [31:28] What about gitdifs with gitlfs? [31:40] Outline: Motivation, Challenges, Solution [35:35] Motivation: Why Structured Data? [36:08] Data is Core [37:34] Challenges: Data is Still in the Dark Ages [37:40] Structured or Unstructured, we're doing it wrong [40:15] Managing Data means Collaborating [45:09] Discoverability and Schema: Structured data requires a real database - not just GIT. [46:27] Revision Control [47:00] Collaboration [48:38] "Git for data, data is the new oil." [49:01] Why merging is so difficult? [49:25] "If you have a schema, you can do much more intelligent things." [52:36] Machine Learning and Revision Control

Episode 280 is here and in this episode Jason and Randy go downtown to Spoiler Town. If spoilers aren't your thing, this episode is not for you. If spoilers are your thing, this episode should be your thing.  The "secret" reshoots. Spoiler - The Worm in the Cave. Spoiler - Rey's new powers. Spoiler - Rey's surname.  Spoiler - The sand snake worm makes a path. Spoiler - Ochi, his tomb, his ship, and the dagger.  Spoiler - Wayfinder details. Paraphrased Rey and Luke sequence: (Rey has ditched Kylo's ship and tossed the Skywalker saber into the wreckage when Luke catches it) Luke: "What are you doing?” Rey: “You were right, you saw the dark side within me. Luke: “The force brought us together. You have to face Sidious as I faced Vader.” Rey: “I wanted to feel I was as strong as Master Leia, but I’m not.” Luke: “You won’t know how strong you are until you know how strong you have to be. Sidious will fill you with fear, with anger, he’ll use your weaknesses against you.” Rey: “What are his?” Luke: “Sidious looked into Vader’s eyes when my father saved me. He couldn’t understand my father's feelings for me. He thought love was a weakness to be used.” https://www.youtube.com/watch?v=zGTj5t8GNww&t=5s  

Luke Melia, Aaron Chambers, and Mattia Gheda john Taras and Charles to discuss all things deployment! Luke Melia: Luke has been working with Ember since it was under early development as Sproutcore 2.0. Ember.js powers a SaaS company he co-founded, Yapp, and they funded their business for a couple of years doing Ember consulting under the Yapp Labs moniker. They're full-time on product now, and his engineering team at Yapp (currently 3 people) maintains around 6 Ember apps. Luke helps to maintain a bunch of popular addons, including ember-cli-deploy, ember-modal-dialog, ember-wormhole, ember-tether, and more. He started the Ember NYC meetup in 2012 and continues to co-organize it today. Aaron Chambers: Aaron Chambers: Aaron is the co-author of EmberCLI Deploy and is currently an Engineer at Phorest Salon Software, helping them move their desktop product to the web platform. He's been using Ember for 5 years and maintains a number of plugins in the EmberCLI Deploy ecosystem. Aaron loves trying to work out how we can ship JS apps faster, more reliably and with more confidence. Mattia Gheda: Mattia is a Software Engineer, Ember hacker, Ruby lover and Elixir aficionado. Currently he works as Director of Development for Precision Nutrition where Ember, Ruby and Elixir power several applications. He loves meetups, organizes Ember.js Toronto and co-organizes Elixir Toronto. Resource: Immutable Web Apps Please join us in these conversations! If you or someone you know would be a perfect guest, please get in touch with us at contact@frontside.io. Our goal is to get people thinking on the platform level which includes tooling, internalization, state management, routing, upgrade, and the data layer. This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC. Transcript: CHARLES: Hello and welcome to The Frontside Podcast, a place where we talk about user interfaces and everything that you need to know to build them right. My name is Charles Lowell, a developer here at the Frontside. With me also co-hosting today is Taras Mankovsky. Hey, Taras. TARAS: Hello, everyone. CHARLES: Today, we have three special guests that we're going to be talking to. We have Aaron Chambers, Luke Melia, and Mattia Gheda who originally met collaborating on fantastic open source library that we, at the Frontside, have used many, many times that saved us countless hours, saved our clients hundreds of thousands of dollars, if not more. ember-cli-deploy. We're gonna be talking not about that library in particular but around the operations that happen around UI. So, welcome you all. LUKE: Thanks, it's great to be here. CHARLES: Like I said, I actually am really excited to have you all on because when we talk about the platform that you develop your UI on, something that often gets short shrift in communities outside of the Ember community is how do I actually deliver that application into users' hands. Because obviously, we don't want it to be working just on our laptop. We want it to be delivered to our users and there are myriad ways that that can happen and it's only gotten more complex since the last time we talked which must have been like three or four years ago. I kind of just have to ask, I think that what you all were talking about then was cutting edge is still cutting edge now but there must have been some pretty incredible developments like in the last three or four years. What have been kind of the new insights that you all have? LUKE: I think that what we realized as we got started with ember-cli-deploy and a project kind of came together as a combination of a few different open source efforts, something that Aaron was working on, something that our collaborator Mike was working on. We decided to come together under one umbrella, joined forces. And what we realized pretty soon is that deployment needs vary a ton between companies. And so, we are coming from this background in Ember community where we had this attitude where nobody is a special snowflake. We all kind of have the same needs for 90% of what we do. And that's true. I really believe in a lot of that Ember [ethos]. But when it comes to deployment, you know what? A lot of companies are special snowflakes or it's at least is much more fragmented than kind of our needs around on the JavaScript side. And so, what we decided to do was to try to evolve ember-cli-deploy into a platform essentially, an ecosystem that could let people mix and match plug-ins to do in their organization without locking them into an opinion that might simply be a non-starter in their org. CHARLES: It's hard enough to have opinions just around the way that your JavaScript code is structured but when it comes to rolling out your app, it really does encompass the entire scope of your application. So, it has to take account of your server. It has to take account of your user base. It has to take account of all the different processes that might be running all over, distributed around the Internet. Maybe somewhere on AWS, maybe somewhere on Legacy servers but it has to consider that in its entirety. So, it's having opinions that span that scope is particularly difficult. LUKE: Yes. And so, you mentioned a bunch of technical details which are absolutely forcing factors for a lot of words in how they do their deployments but what we found in talking to people that there are also people in political aspects to deployment in many cases. Engineers kind of own the JavaScript code that's running within their app, more or less. But when it comes to pushing the app into the world and a lot of companies, that means they're interacting with sysadmins, ops folks, people who have very strong opinions about what is an allowable and supportable way to get those deployments done and to have that stuff exist in production. And so, we needed to come up with an architecture that was going to support all these kind of varied use cases. And so, we came up with this system of essentially a deployment pipeline and plugins that can work at various stages of that pipeline. And that ecosystem has now grown quite a bit. It's actually, I don't know Aaron if you and Mattia would agree but I think it's probably the best decision that we made in this project because that ecosystem has grown and evolved without us needing to do a ton of work in maintenance. And it's been really great. I think Mattia, you pulled some of the current numbers there. MATTIA: Yeah. I pulled some numbers just yesterday and we have currently 150 different plugins attached to themselves, to different parts of the pipeline. So some of them are about how to build the assets, some of them are about how to compress them, some of them are about shipping. And they allow people to ship it with different ways like we are seeing [inaudible] with just simply Amazon APIs or Azure APIs and some of them even are about just how to visualize data about your deployments or how to give feedback to the user about what was deployed and represent the information. And then this is kind of a bit more detail, probably specific to us but we also added this idea of plugin packs. So, in order to help people define their deployment story, we created this ideal of plugin packs. Plugin packs are simply group of plugins. So, plugins grouped together. As a user, if you want to implement what we call a deploy strategy, you can simply install a plugin pack and that will give you all the plugins that allow you to deploy in a specific way. And that's kind of like an optimization that we added just to make it easier for people to share deployment strategies, share ways of deploying applications. CHARLES: Right. It's almost like an application within the framework. MATTIA: Yeah, exactly. But to stay on the community side, I think that the interesting part about what Luke was saying which was a great success for us is that all we maintain as the core team for this project is the core infrastructure, so the pipeline and a thousand of plugins. Everything else is community-based. And often, even in my day-to-day work, I end up using plugins that I didn't write and that I don't even maintain. But because the underpinning of it were designed especially by Luke and I are flexible enough. It just like has been very, very stable and very, very reliable for many years. So, I will say definitely the idea of like in the spirit of what Ember is, I guess, creating a shared ecosystem where people can add what they want and extend what was provided has been the one single biggest win of this project. CHARLES: One of the things that I'm curious about is we've talked about how you're allowing for and kind of embracing the fragmentation that happens in people's kind of the topology of their infrastructure. What do you see is the common threads that really bind every single good deployment strategy together? MATTIA: My biggest thing here, and we actually have some shared notes about this, but my biggest thing about this is the idea that building and deploying an application for me is divided into three parts. There's building part where you have to decide how to compile your JavaScript application and how to produce some sort of artifact. There is the shipping part where it's about deciding where you're going to put the artifact. And then there is the serving part which is how you show it and deliver it to your users. I think that these three are the underpinnings of any deploy strategy. What we did with this project is just acknowledging that and give each one of these a place. And so, the entirety of what we do in what Luke defined as a pipeline is simply give you a way to customize how you build, customize how you ship, and then customize how you serve. So yeah, I think that that's kind of the root. And the question that everybody that wants to deploy a modern JavaScript application have to ask themselves is how do I want to build it, how do I want to ship it, and how will I serve it to my users. And these things are completely independent one from the order in the sense that you can have something build it, something ship it and something serve it, and that's what we end up doing in most of our deployments, I find. CHARLES: It's good to think about those things as soon as you possibly can and make sure that you have all three of those bases covered really before you start adding a whole ton of features. TARAS: Sprint 0, right? LUKE: In Agile, we call Sprint 0 the phase the thing you do right in the beginning. You've got a skeleton of an app and then you get the deployment infrastructure going, you have the test infrastructure going, so that there is no task within your actual feature development where you have to do those things. And I think that can be a valuable concept to embrace. I would just add to Mattia's three points that for deployments, to me, some very simple qualities of a good deployments are repeatability. You need to be able to reliably and consistently run your deployment process. Sounds simple but there's plenty of operations that have run up way too long on manual deployments. So, we don't want to see those rollback capabilities if you have a deployment that you realize was a mistake right after it gets into production. I'm sure none of us have ever experienced that. CHARLES: That never happens to me. LUKE: You want to have a method to roll that code back. That's something that can be remarkably complex to do. And so, having some guardrails and some support mechanisms to do that like ember-cli-deploy provides can be really useful. But whatever your approach is, I think that's a necessary quality. And then I think we start to step into kind of more advanced capabilities that a good deployment architecture can provide when we start to think about things like personalization, A/B testing, feature flags, these kinds of things. And that requires more sophistication, but you cannot build that on a deployment foundation that's not solid. AARON: I think for me, one of the things I've been really thinking about a lot lately, it's a bit of a mindset shift, I think, to get to where the things Mattia was talking about separating those different parts of deployment. And so, I really start to realize the traditional mindset around deployments like I build some stuff and I ship it to the server and then the users get it. But if we can actually stop and actually split our understanding of deployment into two separate phases. One is the building and the physical shipping of the files; and the other one's actually making them available to people. You open up this whole world of our features that you wouldn't normally have. So to be able to actually physically put stuff in production but not yet have it active, as in users don't see it yet but you can preview those versions in production against production databases. And then at some point after the fact, decide, "Okay, I'm now going to route all my users to this new thing," And to be able to do that really easily is massively, massively powerful. And so, to me, the thing I've been thinking about lately is it is a small mindset shift away from packaging everything up and pushing and overwriting what's currently there to being something, again like Luke said, immutable deployments where everything we build and ship sits next to all the other versions and we just decide which one we want to use to look at it any time which leads into then, I guess, A/B testing, feature flags and things. So I guess deployment really is not so much about the physical shipping, that's one part of it. To me, deployment now is shipping of stuff, as in physical deployment and then the releasing it or enabling it or activating it to users. CHARLES: Or routing it. Sounds like what you're describing is an extraordinarily lightweight process. AARON: It is, yeah. CHARLES: To actually route traffic to those files. AARON: It is. It's incredibly lightweight. That's the amazing thing about it. When you think about it, you're building a few JavaScript files and CSS files and images and putting them on a CDN, and then you just need a tiny web server that basically decides which version of the app you want to serve to people. There's not much to it at all, really. CHARLES: I mean that's absolutely fascinating, though the capability that you have when you have the ability to have these versions, the same versions or different versions of your application sitting along next to each other and being able to route traffic. But it also seems to me like it introduces a little bit of complexity around version matching because only certain versions are going to be compatible with certain versions of your API. You have different versions of your API talking to the -- so the simplicity of having kind of mutable deployments, so to speak, is that everything is in sync and you don't have to worry about those version mismatches. Is that a problem or this could just be me worrying about nothing? But that's kind of the thing that just immediately jumps out to me is like are there any strategies to manage that complexity? LUKE: To me, what you're describing, I kind of think of as a feature not a bug. And what I mean by that is that it is very simple to have a mental model of, "Oh, I have a version of my JavaScript code that works with this version of my API." And as long as I kind of deploy those changes together, I'm good to go. The reality is that that's impossible. The JavaScript apps that we write today, people are using anywhere from two seconds at a time to two days at a time. It's not uncommon these days to have some of these dashboard apps. People literally live-in for their job eight hours a day, nine hours a day, keep the browser tab open and come in the next morning and continue. And so, obviously there are some mechanisms we could use to force them to reload that kind of thing. But at some point in most apps, you're going to have a slightly older version of your JavaScript app talking to a slightly newer version of your API for either the span of a minute or perhaps longer depending on their strategies. So to me, the process of thinking about that and at least being aware of that as an engineer thinking about how your code is going to get from your laptop into the world, I think it's an important step that we not paper over that complexity and that we kind of embrace it and say, "Hey, this is part of life." And so, we need to think about just like we need to think about how your database migrations get into production. That's not something that you can paper over and just have a process that it's going to take care of for you. It requires thought. And I think that this, in the same token, how different versions of your JavaScript app are going to interact with your API requires thought. An exact parallel also had different versions of a native mobile app that go into the app store. How did those interact with different versions of your API? So, I think you're right. There's complexity there. There's ways that we can try to mitigate... CHARLES: Keep repeating ourselves if we think that that [inaudible] actually doesn't exist even in the simple case? MATTIA: Yeah. I think that that's to reiterate what Luke is saying. That's exactly the point. You can pretend it's not there but it is and you have no way to avoid it. Once you ship something to a browser, you have no control over it anymore. And so, you have to assume that somebody is going to be using it. LUKE: Aaron, I think you too, I don't know if you can share it. But you recently told us some stories about kind of what you encountered in your work about this and of how long people were using versions and stuff. AARON: Yeah. Something that we hadn't sort of put a lot of thought into. But the last place I worked at, we had quite a long lived app and we're using feature flags and we're using launch [inaudible] something and it gives you a list of flags and when they were last requested. And there were also flags that we removed from the code and it was just a matter of waiting until all the users had the most current version of the app and weren't requesting the flag anymore. But this one flag just kept getting requested for months and we just could not work out why. It really sort of opened my eyes up to this exact problem that these long lived apps set in the browser and if you have someone that just doesn't reload the browser or restart the machine or anything, your app can live a lot longer than maybe you actually realize it is. So we're shipping bug fixes, we're shipping new features, and we're all patting ourselves in the back. We fixed this bug but have we really? If your users haven't reloaded the app and gotten the latest version, then you haven't actually fixed the bug for some number of people. And it's really hard to tell them as you think about this and put things in place, really hard to tell what versions are out in the world, how many people are using this buggy version still. CHARLES: Yeah, that's an excellent point. I haven't even thought about that. I mean, what is the countermeasure? AARON: We hadn't made it until we came across [crosstalk]. CHARLES: It's nothing quite like getting smacked in the face of the problem to make you aware of it. AARON: That's right. CHARLES: So, what's the strategy to deal with that? AARON: I guess for me, my learnings from that would be from very early on thinking about how we're going to encourage people to reload, to start with, and maybe even have the ability to force a reload and what that means but then that has gotchas as well. You don't want to just reload something when a user is in the middle of writing a big essay or something like that. But definitely thinking about it from the start is one of the things you've got to think about from the start. But I guess something that I'd like to implement and I've kind of thought through but not really explored yet, but the ability to see what versions are out there in the world and there are things I've been thinking about in terms of this little server that serves different versions. Maybe we can start having that kind of tracking what versions are out there and who's using what and being able to see because it would be great to be out to see a live chart or a dashboard or something that sort of shows what versions are out there, which ones we need to be aware of that are still there and even what users are using and what versions they can maybe even move them on, if we need to. But there's definitely a bunch of things that aren't immediately obvious. And I don't know how many people actually think about this early on, but it's critical to actually think about it early on. MATTIA: Yeah. I was going to share what we do which is very similar to what Aaron said just maybe for the listeners to have some context. The first thing you can do is basically what Gmail does, which is every time a web app sends a request, an [inaudible], it will send the version of the app with the request and the backend can check. And the backend can check if you are sending a request from the same version that is the most recent deployed version. And if it's not, this sends back a header and the same way that Gmail does, it will display a pop up that is like, "Hey, we have a new version if you want reload." And on top of that [inaudible] is that we have a dead man's switch. So if we accidentally deploy a broken version, a part of this process, the frontend application tracks in the headers. And if a special header is sent, it force reloads, which is not nice for the user but it's better and sometimes is critical to do so. CHARLES: Right. I remember that was that case where Gmail released something. They were doing something with broken service workers and the app got completely and totally borked. I remember that my Twitter blew up, I don't know, about a year ago I think, and one of the problems I don't think they had was they did not have that capability. MATTIA: I mean, you learned this the hard way sadly. But I think these two things are definitely crucial. And the third one, [inaudible]. I thought, Luke, you had the ability that Aaron was talking about like tracking versions in the world. And I think that's more useful for stats so that you know how often your users update. And then you can make the design decisions based on that and based on how much you want to support in the past. LUKE: Yeah. We haven't implemented that but it reminds me whenever there's a new iOS version, we do a bunch of mobile work in the app and we're always looking at that adoption curve that's published. A few different analytic services publish it and say, "OK. How fast is iOS 12 adoption? How fast are people leaving behind the old versions?" And that helps to inform how much time you're spending doing bug fixes on old version versus just telling people, "Hey, this is fixed in the new OS. Go get it." But if you are able to see that for your own JavaScript apps, I think that would be pretty hot. CHARLES: Yeah. Crazy thought here but it almost makes me wonder if there's something to learn from the Erlang community because this is kind of a similar problem. They solved 20 years ago where you have these very, very long running processes. Some of them there's some telephone servers in Sweden. They've been running for over a decade without the process ever coming down. And yet they're even upgrading the version of Erlang that the VM is running. And they have the capability to even upgrade a function like a recursive function as it's running. And there's just a lot of -- I don't know what the specific lessons are but I wonder if that's an area for study because if there's any community that has locked in on hot upgrade, I feel like it's that one. LUKE: That's a terrific analogy. I bet we could learn a ton. Just hearing that kind of makes me think about how kind of coursed our mental model is about updates to our JavaScript apps. We talked to Aaron, we're talking about kind of this idea of a mutable apps and you have different versions side by side. But the idea of being able to kind of hot upgrade a version with running code in a browser, now that's an ambitious idea. That's something I'd say, "Wow! That kind of thing would be a game changer." CHARLES: Yeah. AARON: Makes me feel like we got a whole bunch of work to do. CHARLES: We welcome them. I'm always happy to give people plenty more work to do. No, but how they manage even being able to do migrations on the memory that's running. I don't know if it's something that's going to be achievable but it sounds kind of like that's the direction that we're heading. LUKE: It does, as these apps get more complex and they continue to live longer. The idea, the work arounds that Mattia mentioned about kind of showing a message and having a dead man's switch, these are all certainly useful. And today, I would say even like the best practice but they were not what you would want to do if you could magically design any system. If you're taking a magical approach, the app will just be upgraded seamlessly as a user was using it. And they would be none the wiser, the bugs would be fixed. End of story. There's no interruption to their workflow. At least for me personally, I don't really think about that as a possibility but I love the Erlang story and analogy and to say maybe that is a possibility, what would it take? I would obviously take a collaboration across your JavaScript framework, perhaps even JavaScript language features and browser runtime features as well as your backend and deployment mechanism. But I think it's a great avenue for some creative thinking. CHARLES: I'm curious because when we're talking about this, I'm imagining the perfect evergreen app but there's also feels like there's maybe even a tension that arises because one of the core principles of good UI is you don't yank the rug out from underneath the user. They need to, at some point and we've all been there when the application does something of its own agency, that feels bad. It feels like, "Nope, this is my workspace. I need to be in control of it." The only way that something should move from one place to the other without me being involved is if it's part of some repeatable process that I kicked off. But obviously, things like upgrading the color of a button or fixing a layout bug, those are things that I'm just going to want to have happen automatically. I'm not going to worry about it. But there is this kind of a gradation of features and at what point do you say, "You know what? Upgrading needs to be something that the user explicitly requires," versus, "This is something that we're just going to push. We're going to make that decision for them." LUKE: Yeah, it's a great question. One of the things that I'm curious what you all think is when you think about the mental model that our users have of working in a browser app, do you think that there is a mental model of, "Oh, when I refresh, I might get a new version." Do people even think about that? Or are they just like your example about a button color changing as kind of a minor thing. I don't even know if I could endure stack. We've all been I think in situations where you do a minor redesign and all of a sudden, all hell breaks loose and users are in revolt. Take the slack icon. So, I think it's a fascinating question. CHARLES: I don't know. What's the answer? Do you always ask for an upgrade just observing? I don't have any data other than observing people around me who use web applications who don't understand how they actually work under the covers. I don't think it's the expectation that this code, this application is living and changing underneath their feet. I think the general perception is that the analogy to the desktop application where you've got the bundled binary and that's the one you're running is that's the perception. AARON: I'd say the difference there is that, and with all these new ways of deploying, we're shipping small things faster in multiple, multiple times a day or even an hour. So it's not the sort of thing you really want time to use. There has been an update, need to upgrade as well. And that's the difference between the desktop mentality. And if that's the mentality they have, it sits quite a bit of a shift, I guess. MATTIA: It makes me think that one of the tools that the users -- if you take a look at the general public, there's probably one tool that everybody can relate to which is Facebook. So, I think if there is a way to say what do people generally expect. There is a business user which I think we are often most familiar with but the general public, probably what they're most familiar with is what happens in Facebook. And I don't use Facebook almost. I haven't used it for a couple of years but I wonder how much of what people experience in Facebook actually impacts the expectations around how applications should behave. LUKE: I think that's a really good question. I do think your underlying point of you have to know your own users I think is an important one also. Obviously, some folks are going to be more technical than others or some audiences will be more technical than others. But I would even question, Charles, your suggestion that people think of it kind of as like a binary that it stays the same until you refresh. I think people have an idea that web apps improve over time or sometimes they get bugs but hopefully that they improve and change over time, and that there is a tradeoff there that means sometimes there's something new to learn but at the same time, you get new features. But I don't know that people necessarily associate that with and it happens when I hit reload or it only happens when I open a new browser, like I don't know that it's that clear for people in their head. CHARLES: Right. I can see that. But the question is if the evolution is too stark, I think people tend to get annoyed. If they're in the middle of a workflow or in the middle of a use case and something changes, then it gives it a feeling of instability and non-determinism which I think can be unsettling. LUKE: Definitely. We all value, as engineers, we value getting into that flow state so much of like, "Oh man, I'm being productive. I don't have any distractions." And you kind of owe that to your users also to be able to let them get into that state with your app and not be throwing up, "Hey, there's new stuff. Reload." "I'm in the middle of something. Sorry." CHARLES: Yeah. I definitely do the same thing. Sometimes, I let iOS be bugging me to upgrade for a month until I finally start to feel guilty about security and actually do the upgrade. LUKE: Right. CHARLES: Although once they started doing it at night, it actually made it a lot better. LUKE: That's an interesting idea, too. I think there's a natural tension between the lower integration risk that we have as the engineering teams of shipping very frequently. Aaron mentioned shipping a dozen times a day. We certainly have been there and done that as well. I would say on average, we ship a few times a day. But the reason that we do that is because we know the faster we get code into production, the faster we can trust it. So it passes all your tests, it passes your [inaudible], but you don't really know if you're being honest. You don't really know until there's thousands of people using it in production. And yet, this conversation makes me think about there is a tension between how frequently you do that versus your users' kind of comfort level and expectations. CHARLES: And maybe there is a thing where you can kind of analyze on a per user basis how often they're active in the application and try to push updates on times that are customized to them. LUKE: Like when a user has been idle for 30 minutes or something like that. CHARLES: Yep. Or even like track trends over months and see when they're most likely to be idle and schedule it for them. LUKE: Good point. CHARLES: Something like that. TARAS: I have an idea. We should introduce screen savers into web apps. And so when the user stops using the app, just turn on screen saver and do the upgrade. LUKE: I can see the VC patch. It's after dark but for the web. CHARLES: Enter install flying toaster. AARON: It does that to open up the idea as well of that automated checking that things are okay well after the fact because it's all right to sit there maybe activate something and sit there even for an hour and make sure there's no bug request coming in. But if no one's actually received your app, then of course it's not going to come in. And it's very easy to kind of move onto the next thing and forget about that. I guess it's not something that I've ever put a lot of time in and I haven't worked anywhere that's had really great automated checking to see is everything still okay. And I guess it's an interesting thing to start thinking about as well an important thing. CHARLES: Like actually bundling in diagnostics in with your application to get really fine grained information about kind of status and availability inside the actual app. AARON: I'm not exactly sure, really. I guess I maybe wasn't thinking about inside the app but I don't know what it looks like exactly. But there is that element of shipping fast and getting stuff out there. But are we really making sure it all works later on when everyone's actually using it. LUKE: Yeah. This by the way, I just wanted to say when we were talking earlier what are the essential qualities around deploying an app. And this reminds me that one thing that we didn't mention but is very simple is your app should have a version. And it should be unique and traceable back to what was the GitHub, git commit that was the origin of that code. It's just a very simple idea but if you're going to be analyzing errors in production when you have multiple different versions of your JavaScript app running, you're going to need to know what version caused this error and then how do I trace it back and make sure that the code that I'm trying to debug is actually the code that was running when this error happened. CHARLES: Do you only use just [inaudible] or do you assign like a build number or using SemVer? What's a good strategy? LUKE: In our case, we use git tags. And so, our CI deployment process for our Ember apps basically looks like this is we work on a PR, we'll merge it to master. If it builds, the master gets deployed into our QA environment automatically using ember-cli-deploy from our CI server. And then once we're happy with how things are on QA, we do git tag or actually I use an ember addon called ember release that does that tagging for me and I'll tag it either in patch minor or major, roughly [inaudible] although it doesn't matter that much in the case of apps. When there is a new tag that builds green on CI, that gets deployed automatically into production by ember-cli-deploy. And so, that's kind of a basic flow. That tagging, just to be clear, the SemVer tag is just going to be number.number.number. You can get more sophisticated than that and I think both Aaron and Mattia have a system where even in the PR stage, there's automatic deployments happening. So maybe one of you want to mention that. AARON: We're slightly different. Every time we push the pull request, that gets deployed to production. We're able to preview up pull requests in production before we even merge into master which we find super useful to send out links to stakeholders and maybe people that have raised bugs just to get them to verify things are fixed. And then at the point that it's all Google merged, the pull request to master which will automatically do another deploy which is the thing we'll ultimately activate, we activate it manually after the fact. We just do a little bit of sanity checking but we could automatically activate that on merge to master as well. But yeah, the being able to preview a pull request in production is super powerful for us. CHARLES: That is definitely a nice capability. It's hard. It's one of those certain workflows or patterns or tools that you remember life before them and then after them and it's very hard to go back to life before. I would definitely say kind of the whole concept of preview applications is one of those. AARON: Absolutely. It's a daunting concept if you're not there, previewing something that's essentially a work in progress and production. And there are some things you want to be careful with, obviously. But for the most part, it's a super valuable thing. As you say, it's a world where once you're there, it's very hard to step back and not be there again. CHARLES: So I had a question about, we talked about I think it was 162 plugins around the ember-cli-deploy community. What for you all has been the most surprising and delightful plugin to arrive that you never imagined? MATTIA: That is a good one. I'm pulling up the list. What I can tell you, for me, it's not about a specific plugin. The surprising part was the sheer amount of different strategies that people use for the shipping part. At least, I found that the build part is similar for most people, like most people want to do the things that you're supposed to do. So, you want to build your application and then you want a minify it in some way. And there's a bunch of options there from gzip to more recent technologies. But the way people deliver it to servers and the difference in the solutions, that I think for me has been the biggest thing, where people that ship [inaudible] are people that ship directly to Fastly, people that use FTP files, people that use old FTP, people that use our sync, people that do it over SSH. We have people that ship stuff directly to a database because some databases actually have great support for large files. So we even use it as a storage. We have people that do it in MySequel, people that do it in [inaudible]. CHARLES: It's actually storing the build artifacts inside of a database? MATTIA: Yes, I've seen them in that. It's kind of interesting like the solutions that people ended up using. And so for me, I think that that's been the most fascinating part. Because as we were saying at the beginning, I'm just seeing now, we even have one for ZooKeeper. I don't have an idea what this does but it's probably related to some sort of registration around the seven-day index. That, to me, I think has been the biggest surprise. Everybody ends up working in a different environment. And so, that flexibility that users need has been by far the most surprising one. AARON: I think that's also been one of the challenging things, one of the enlightening things for me. I think in the Ember ecosystem, addons and even just Ember itself, it's all about convention of configuration and doing a lot of the stuff that you do for you. I think people expect them to see a lot of point to do the same thing. But the key thing here is it just really automates all the things you would do manually and you need to understand exactly what you want your deployment strategy to be before use them to see a lot of [inaudible] could do for you. You need to decide do I want to install my assets on a CDN and do I want to install my index in Redis or in console or in S3 bucket. You need to know all these things and have decided on all these things and then ember-cli-deploy will make that really easy for you. And this is one of the educational things, I think we still haven't even nailed because there are always people that want to know why this doesn't work. But deployments are complex thing and as what you were saying Mattia, there are so many different variables and variations on doing this that there's no sensible configuration ember-cli-deploy could really provide out of the box, I guess. And so, that's why we ended up with a pipeline that gives you the tools to be flexible enough to support your strategy. LUKE: I think the closest that we come to the convention is that if any app is using ember-cli-deploy, you can run ember deployment targets or ember deploy prod and ember deploy QA and you can expect that that's going to work. What you don't know is how has it happened to be configured in this project. Charles, your question about kind of the most surprising thing that's come out of the ecosystem. For me, I would say -- Mattia mentioned plugin packs earlier which are groups of plugins that kind work together well. And so, we've seen some plugin packs like you might expect, like an AWS pack for deploying to AWS. But the more interesting ones to me that we've seen a lot of, companies open source their plugin packs. So what you naturally fall into as a company that's adopting ember-cli-deploy that has multiple ember apps is that you are going to develop your own plugin pack for internal use because generally speaking, companies follow the same deployment pattern for each of their apps. There's usually not any reason to vary that. So then the new thing that happen on top of that is people said, "Why don't I make this open source so other people can kind of see how we do it?" And that's been a really delightful part of the process to kind of get a peek into how other organizations are orchestrating their deployments. And if people are curious about kind of looking at that themselves, you can go on NPM and look for keyword ember-cli-deploy-plugin-pack and pull up all of those. And you can kind of poke around and see what different companies have open source there. CHARLES: I actually love all three of those answers because it really is for me when you have a constellation of people around a particular problem, it's the surprising solutions that emerge that are some of the most exciting that would have lain hidden otherwise. It would have been kind of buried beneath the source of company A or company B or company C but actually having it all out in the open so that you can inspect it and say, "Wow, where has this solution been all my life?" Something that you have never imagined yourself. LUKE: It's so funny that you mentioned that because that actually is the origin story way back, I'm talking like 2013 probably when we were very early Ember adopters and we were trying to figure out how do we deploy this thing. We're deploying it with our Rails app, like literally deploying the Ruby code and the JavaScript code together which took forever which is a disaster. And I heard through the grapevine, just exactly what you're saying Charles, where the good ideas are kind of hidden inside of a company. I heard through the grapevine that Square had this approach that they were using where they would deploy their JavaScript assets and then deploy their index HTML file, the contents of that file, into a database, it's Redis in their case, and serve then it out of there. And it empowered all of these interesting situations of like having multiple versions, being able to preview the release, et cetera. And so we then set out to copy that idea because there was nothing open source. So we had to create it ourselves which we did in Ruby which we made it inaccessible to many JavaScript shops in the first place. Then the evolution of that kind of over time and of Mattia and Aaron and Mike and the rest of the community kind of talking together has now moved this into the open source sphere where these ideas are more accessible and we've created an ecosystem encouraging these ideas to stay out in the open. It's so true that there's just gems of ideas that have been created by really brilliant engineers inside of companies that could be benefiting so many people, they just haven't seen the light of day yet. CHARLES: Yeah, that leads me to my next question. I would say most of the ideas that we've been talking about today really, except for the build part, how Ember specific are they? Obviously, the ember-cli is a great resource and has a lot of great opinions for actually building the JavaScript assets themselves. But the second two phases of the pipeline really can vary freely, if I understand correctly. And so, have you all ever thought about trying to maybe kind of abstract these processes and these plugins so that these same ideas don't remain not just inside of a company but inside a community that spans a set of companies so that it's available for a wider audience? How integrated is it with Ember and what kind of effort would that be? LUKE: That's a great question. Aaron or Mattia, one of you guys wanna talk a little bit about the history here? MATTIA: Yeah, sure. We've been thinking about this as well. In the past, a guy on the ember-cli-deploy team, Pepin, has actually started this effort and it kind of prototyped this very idea of separating the ember-cli-deploy part from Ember CLI itself and make it a bit more generic. And he started a project called Deploy JS which I can give you a link for the show notes later. I don't think that the project is currently maintained but definitely the start of the effort is there. And the funny thing is that it was surprisingly easy. I think that we didn't get there mostly because we just all use Ember at work. As you know, open source is mostly motivated by the needs that an individual or a group of people have. But if any of the listeners were very interested in this, I think they should definitely get in touch and we will be happy to talk to them and see what can be done here. AARON: And also if you look, there's actually a plugin called ember-cli-deploy-create-react-app and there's also ember-cli-build-view. So it can and is being used to deploy non-Ember apps which I think is super interesting because the only real Ember part of it is just using the CLI to discover the addons and plugins. And from then on, it's really out of the hands of Ember. But it sort of leads into a little bit, Luke mentioned this concept of immutable web apps. And I've been thinking a lot about this lately because a deployment strategy that ember-cli-deploy use as an example a lot and it's kind of become [inaudible] ember-cli-deploy in ways, the lightning approach which is this whole idea of splitting or putting your assets in CDN and your index HTML separately maybe in Redis and serving that. I've been trying to work out how I can talk about this to the wider JavaScript community in a non-Ember way and knowing full well that the concept of lightning deployment means nothing to anyone outside of Ember. Just by chance, I was just talking to some people and this terminology of immutable deployments kind of rose. I started searching around and I come across a website called ImmutableWebApps.org which was just scarily the same as what we've been talking about for the last three or four years with ember-cli-deploy. And a way to boil down at a framework-agnostic level, what are the key points that you need to consider when building a JavaScript web app to make it immutable. And it was just really amazing seeing it. This website was put up 3 weeks before I did my Google search coincidentally. And it's basically word for word what we have been talking about the last three or four years, So, someone else in the other side of the world's been coming up with the same ideas in their company like you were talking about earlier and we've reached out to him. I guess that, to me, is sort of the way forward that I want to sort of pursue to try and get these ideas out in a framework-agnostic way to the rest of community and say, "Hey, we thought about deployment in this way. Have you thought about building your app in this way to give you these sorts of capabilities?" CHARLES: I think the wider community could definitely benefit from that because most of the blog posts and talks I've seen that concern themselves with deployment of single page applications, it's still much more of the tutorial phase. Like, "This is how I achieve getting this deployment strategy." Not, "This is how I repeatedly encode it as a program," and leverage it that way. And so, definitely getting that message out to a wider audience, I think it's a -- what's the word? It's an underserved market. LUKE: Yeah. I really like this idea also. I think about this ImmutableWebApps.org, if you look at it. It's sort of a manifesto with conceptual description of what are the qualities that your app has to have to qualify as an immutable web app which I think is kind of a funny idea but one that people can start to get their heads around and compare that description to their own apps and say how do I hit this or fall short. And it reminds me a lot of kind of the idea of Twelve-Factor App which is an idea that I think came out of Heroku originally. And it's an idea of a backend app that is portable to be able to easily move across different hosts and easily be scalable to different instances of [inaudible] if your app obeys all of these things then it's going to do well under those circumstances, that will satisfy those needs. So, I think it's a great way of thinking and probably maybe even a better entree into the conversation with the wider community than a library, this is certainly a library called ember-cli-deploy. CHARLES: This is a fantastic discussion. It's definitely reminded me of some of the best practices that I haven't thought about in a long time and definitely opened my eyes to some new ones and some new developments. So often, we can be focused on how our apps work internally, like how the JavaScript code works that we can just kind of -- what's the saying -- lose sight of the forest through the trees or I can't remember. It's like too busy looking down the end of your nose to see past your face. I've probably mangled both of those adages, but maybe 60% of two mangled adages is at least equal to one. This is something that we need to be thinking about more, that everybody needs to be thinking about more. This is actually a very exciting, very useful problem space and I'm just really grateful that you guys came on to talk to us about it. So, thank you, Mattia. Thank you, Luke. Thank you, Aaron. MATTIA: Thank you so much. It was a great time. AARON: It was a pleasure. Thanks for having us. LUKE: Thanks so much. CHARLES: Thank you for listening. If you or someone you know has something to say about building user interfaces that simply must be heard, please get in touch with us. We can be found on Twitter at @TheFrontside or over just plain old email at contact@frontside.io. Thanks and see you next time.

Gender role subversion in the Gospel of Luke? You might be hearing this first from the Rev. Anne Thatcher. Explore what the Song of Simeon has to teach us today as we celebrate the Feast of the Presentation.

In today's episode, we help Luke grow his audience to get more consistent membership sales.  FULL TRANSCRIPT Jocelyn: Hey, y'all. On today's podcast, we help Luke take his education business to the next level. Shane: Welcome to the Flipped Lifestyle Podcast, where life always comes before work. We're your hosts, Shane and Jocelyn Sams. We're a real family that figured out how to make our entire living online. Now we help other families do the same. Are you ready to Flip Your Life? All right. Let's get started. Shane: What's going on everybody? And welcome back to the Flipped Lifestyle Podcast. It is great to be back with you again today. We are super excited to have another member of the Flip Your Life community on today's podcast, on today's show. And we're going to celebrate some big wins with them and help them take their business to the next level. Our guest today is Flip Your Life community member Luke Reed. Luke, welcome to the show. Luke: Hey. Thanks for having me. Jocelyn: It is great to have you today, Luke. And we are super excited because just a few minutes ago before the show started, I heard some gentle mooing in the background. And we determined that this is the first ever cow appearance on the Flipped Lifestyle Podcast. Shane: Yeah. [inaudible 00:01:08]. As we talk to Luke, and he is standing outside in a cow pasture apparently, right now. You're going to hear some mooing. Our dogs are in the house. They may come in and start barking at the cows mooing through the microphones. Jocelyn: And you know what, it kind of surprised it's taken us over 200 episodes to get cows on the podcast because- Shane: I know. Right? We lived out in the country. Jocelyn: Kentucky. Shane: We have a cow pasture. We should go out, Jocelyn, to the cow pasture next door. And maybe our cows could talk to Luke's cows. That would be amazing. Jocelyn: You can never have too many cows on a podcast. Right? Luke: Why don't we try it, see? Shane: Where are you and why do you have so many cows surrounding you right now? And should we be worried for your safety? Luke: No, I am perfectly safe. But I'm in the middle of a cattle ranch, so there are cows about 200 yards away from me right now. Shane: Nice. Okay. Well, if they charge, you let us know and we'll pause the recording. And we'll edit out any trampling that happens. Okay? Jocelyn: If this whole cow thing doesn't work out for you, we need to know a little bit more about what you're doing online, so tell us a little bit about you, your family, your background, and your online business. Luke: My online business started as many of your members, after listening to Pat Flynn and hearing your story on Pat Flynn's podcast. And I heard your story, and it just sounded so real. It really resonated with what I wanted to do and the freedom that I wanted to try and build for my family. I really took off after listening to that. I'm in the education business, so I was able to model a lot of what I've done after what you started with, with Elementary Librarian and US History Teachers. And it's gone pretty well. In, let's see, it's been just about exactly one year, I found a business partner to do the curriculum side of the business. And we built the website and put together the curriculum. Now we've got our first few sales already, so it's gone pretty quickly. Shane: Tell us a little bit about your family and where you're from. Where are you at? What is your background? Like you said, you're in the education field. Tell us a little bit more about that. Tell us about your wife, kids, stuff like that. Luke: Okay. I'm in Central California. I was born and raised in a little town smack dab in the middle of California. Grew up here and went to school here. Got my degree at the most recent University of California campus, which opened just as I finished my bachelor's, so I went on and got graduate degrees done. My wife is the reason that I'm now renting a house in the middle of a cattle ranch. Her father is a rancher, so she grew up raising cows, working cows. And it turns out that her dad and herself, they have a genetic mutation that causes heart failure, early onset heart failure, so part of my reason for wanting to do the online business is that. I want to be able to have freedom to spend more time as my wife goes through the health problems that she's dealing with. Luke: And we've got two little boys. Our older son is our biological son. And then our younger son is adopted, so we just recently finished that adoption process, so got two boys now. We really like the bigger family. Two kids is just so different than just one. Shane: Oh, yeah. My father-in-law always used to tell me, and I'm sure this is going to offend someone out there who only has one kid. My father-in-law used to tell me when we had our first kid. I was like, "Yeah. I'm a parent now. I'm a real grown up." Right? That's how I felt. He'd just laugh at me. And he would go, "You've got one kid. You're not a real parent until you have at least two." And I used to get so mad at him for saying that. Jocelyn: But then after we had two we're like, "Oh, he's kind of right." Shane: We were like, "You were right, bro. Pops, come on, man. You were right." It's hard. Jocelyn: It's true. Shane: I can't imagine going to three or four. I can't even fathom that. Jocelyn: I can't either. Two is good. Shane: I'm not tough enough for that. I know I'm not. I am not man enough to go. I'm running man to man coverage right now. I do not want to have to go to zone. You know what I'm saying? Jocelyn: A couple of things kind of struck me about what you were talking about. First of all, that you live in a cow pasture in the middle of California. People probably weren't expecting that. Shane: People are like, "Wait. There's cows in California?" Jocelyn: There are because I've seen those commercials about cheese. Luke: Yeah. The happy cows. Jocelyn: That's right. Happy cows in California, so Luke's cows are happy I guess. Another thing that you said that kind of struck me was that you are in California, which means that it's like 6:00 AM there. Right? Luke: Yes. Well, 6:20 now, but yeah. Shane: You're doing what it takes to get up and make this online business thing happen. That's why we love you, Luke. That's why we wanted to bring you on the show too, just because I know you're doing the work. And I know you're dedicated. And your why is so powerful because you've got this really real threat in your life to the health of the person that you love. And to be able to say, "Hey. It would be really cool not to go to work," and be able to come home, and to be able to work with your wife, around your wife, and spend more time with your wife as she deals with these health problems. That's a really, really powerful way. Jocelyn: Right now you're still working. Right? Tell us a little bit about that. Luke: Right. I have a job as a lab coordinator, instructional lab coordinator, actually at the school where I got my degree. I finished- Shane: What's your degree in? What is your degree in? Luke: My degree's in chemistry. Shane: Chemistry. That's right. Luke: I work as lab coordinator there. And it's actually a really good job. It's very flexible. Working at a university is pretty friendly towards the workers. There's not a lot of hostile environment of get more work done and make us more money. But it is still a job and you have to go there. You have to be there. You have to do what other people want you to do. If I can move on from that at some point, I would really like to. And that's the goal. Shane: Awesome. Jocelyn: Lately we have been making some changes to our podcast. And what I mean by that is that when we started the free trial in our membership, our members started growing, so we have a lot of people in the membership now. And when we first started out, it was sort of just like a perk for being a member for so long that you got to be on the podcast. But now that we have so many members, we can't really do that anymore. So what we've decided to do is, we look for people who are posting success stories regularly. And the reason that we do that is because we know that those people are doing the work. One of the ways that we know Luke is doing the work is because he is posting regularly in that success stories thread. And recently you told a success story to us that I would like for you to share with the listeners. Shane: It blew our mind when we read this because this was like the epitome of online business. Right? This is why you do it. Tell us a little bit more about that success story that you shared. Luke: Yeah. It was my first online sale. And it was for an annual subscription to the lesson plans that I've made with my business partner. And it actually happened while my wife was in the hospital recovering from a blood clot that lodged in her kidney. So we had been there. Let's see, we got there on a Thursday. And they got her in, they got her into her room. Got her pain under control. She was there for four days. And on that fourth day, I had gone to my parents to see my kids, take a little break from the hospital environment. And as I was there relaxing, I heard notification come through on my phone. I went and checked it. Thought it was just going to be another email. And I pulled it up, and it says, "You just received a payment, $397 for an annual subscription." Jocelyn: Yay. There was a celebratory moo. Shane: Instead of celebratory mood. [crosstalk 00:09:44]. The cow is happy. You're happy. We're happy. The listeners are happy. This is the best podcast we've done in weeks. Amazing. Yeah. When you saw that, did you feel like the magnitude of, I have spent the last four days taking care of my wife in the hospital, and in the background my marketing, my website, my social media, everything kept working for me? Even though I couldn't pay total attention to it, even though I could only check it here and there from the hospital room, did it hit you? Like man, if you could make your whole living like this, then all of these things, your kids getting sick, your spouse getting sick, you would be able to deal with those things instead of business. Luke: Honestly, it didn't hit me. That was the reality. But what actually hit me was pretty much complete freak out moment. This can't be right. I don't know what's going on. I think I need to contact this guy. And he probably wants- Jocelyn: Somebody accidentally typed in their credit card numbers. Luke: Yeah. Yeah. I think what I really realized instantly was that, oh my goodness, I've got a horrible problem with fear of success. And it took me another day and a half to settle down and be okay with the fact that somebody sent me money. And then it started to sink in. Oh, this works no matter what you're doing. Shane: Did you tell your wife? Did you call her immediately and like, "I just made a sale"? What was that? Luke: No, actually I waited until I was ... I processed it and I was over the initial reaction of this had to have been a mistake. And I told her a couple days later, and she was feeling a bit better. She could handle some news at that point. So it wasn't until a couple days after it happened that I told anybody. And then she just kind of looked at me like, "Okay. Well, you've been working on it, so there you go. What's the big deal?" Shane: Right. Exactly. You know? Jocelyn: I'm reading through some of the things that you wrote here. And I love what you said. It says, "Anyone who says they don't have time for online business doesn't want it badly enough. If I can use the time waiting for my wife to be out of surgery to answer questions and work on blog posts, anyone can find some time." Shane: Wow. That's deep, man. Jocelyn: That's very profound. Shane: And it's also powerful because we've had family members get sick. And their spouse had to go to work to be able to pay for their bills, to be able to do ... And they literally, someone has to go and sit with the spouse while their husband or wife had to go to work. Right? And it's just incredible to hear that I can sit in the hospital, in the room, and work on my business while taking care of my spouse. My family member can go to surgery. I can take care of my things, but be there when they wake up for surgery. And these opportunities that we have to take control of our lives are just amazing. And we have to take advantage of them because 20 years ago, people didn't have that opportunity. Right? Luke: Yeah. Yeah, it is quite an opportunity. You can do it anywhere, whatever's going on. If you can sit down and focus for a few minutes, you can get something done. It's quite an opportunity. And it would be a shame to just let it go by. Jocelyn: I totally agree. You clearly don't struggle with time. That's something that a lot of people say that they struggle with, so that is really cool. Shane: Well, first of all, congratulations for everything that's got you to this point, and on getting that first sale, especially such a big sale. I think back at our 11 cent moment. The first money we ever made online was 11 cents on an ad click, and I thought that was the greatest thing ever. And you're dropping $400 bones in your back account like nothing. Right? But I want to go back and just point out you have been an active member in the Flip Your Life community. You post your success forums. You post your action plan posts. You go in there and ask questions. You did a workshop with us. You worked with us. We worked with you one on one a little bit in coaching and call environment. And you've really put in the effort and the investment to get to that point of that first sale, because I don't want anyone out there to listen and say, "Well, he started a website, and someone found it. And he got lucky." Right? Shane: Because Luke did not get lucky. Luke put in the work. He put himself in the right place at the right time so that someone could find that product and make that purchase. You need to just look in the mirror and say, "I deserve success," because you're putting in the work. And some people get really overwhelmed when people send them that money and think, "Wow. Do I deserve this? Am I expert enough? Is this really me?" And then imposter syndrome kicks in. And we've got to kick that to the side right now because if you can get one person to give you $400, then you can find 100 people to do it. You can find 1000 people to do it because there's more people out there just like that buyer. And it's just amazing watching your journey. And when we see these success stories in the Flip Your Life community because Jocelyn and I know all the background. And I just wanted to really bring that up because the listener may not know that, that you've done the work. And you deserve this, and you deserve everything that's about to happen in your business going forward. Luke: Thank you. Yeah. It's definitely a lot of work. Everybody hears the polished side and sees the stories. But yeah, there's a lot of work that goes into it behind the scenes. Jocelyn: Definitely. For sure. All right. Well, let's talk a little bit. You've already overcome so many things to get to where you are now. But let's talk about what is going on inside your head, or maybe something else that's holding you back right now. Do you have any fears or mindset issues, maybe something else that you think is keeping you from reaching the next level? Luke: You know, I think there is some of the imposter syndrome. Every time I sit down to send an email out to the list, I struggle with that because my business partner is actually the one who does all the teaching and does all the curriculum. She's the one with the experience. And when I send the emails, it's hard because I feel like I'm saying things that aren't really from my background, so I feel that imposter syndrome. That's a challenge. Communicating to these people, I have about 300 people on the email list now. Sending emails to them, I get so nervous every time I sit down to do that. Shane: Interesting. What are you sending? And this is really good because a lot of people pick a niche where they're not necessarily an educated degreed person and you get to do this. I have a master's degree in that subject. That's not what's happening. A lot of people pick a niche because they know a little bit about it. They do research. They learn more about it and they become a teacher in it. Right? What are you sending people? Just like, hey, here's a cool resource. Are you just relaying information from your business partner? What's in these emails that's making you so nervous? Luke: It's just relaying resources for the teachers to use. And of course I've got high school teachers that are signing up for the emails. Sharing resources, sharing stories from my business partner's past and experience, sharing blog posts that we put up, just things like that. And I can't tell you why, but it just really feels like it shouldn't be me sending the email. I think that's what it is. Shane: Basically because you're not the teacher when you send the teacher stuff. Even though you're just literally relaying information from someone else, that freaks you out a little bit because you're afraid people are going to be like, "Well, the person that hit send is not the actual expert." Right? Luke: That's correct. Yeah. Shane: This reminds me. Okay. Let's say you're walking down the street. Right? And I see you. I'm new in town and I'm lost. So I pull over, I'm like, "Hey, buddy. How're you doing?" You walk over and say, "Hey, man. I'm just out walking my cows. Moo." And I'm like, "Hey. Can you tell me how to get to the next town?" And you're like, "Sure. All you've got to do is go down this road, take a right, and go this way." Right? Or maybe you don't know where it is, so you pull out your phone. And I don't have a GPS, so you pull up your map. And you're like, "Okay. Here's a map I got for you. So you go down this road, you go left, and you go straight." So you give me those directions. Right? Shane: Wouldn't it be ridiculous if I looked up at you and said, "That's great. But are you a cartographer? Did you make that map? Did you literally draw that map that you just showed me? Are you a member of the Army Corps of Engineers that built these roads that get me to the next town? Are you really an expert at that?" That would be ridiculous. Right? But that's what you're doing. You're like, "I'm not the guy that drew the map, so I can't show anyone how to use the map," and you're not even involved in the expert enough. And you can even be honest with this and be like, "Hey, this is Luke. Here's my business partner," whatever. You could even make up a persona if she doesn't want to identify herself. And be like, "She wanted me to send you this thing." You could even put a buffer zone in between. But don't ever be afraid to relay information, to curate things and give it to people because nobody cares. They just want the answers. They just want the solutions. Jocelyn: And I think probably the story that you're telling yourself is that somebody's going to ask you a question you don't know how to answer. Shane: Ooh, that's deep. Jocelyn: Or somebody is going to say, "Hey. Who are you to say this to me? You're not even a teacher. You've never even been a teacher." Is that part of it, do you think? Luke: Oh, yeah. It is. Definitely. Jocelyn: Yeah. Sometimes you have to kind of dig underneath the surface and figure out what's really going on. And I think that might be what it is. What you have to do is, you have to rewrite that story and say, "If I don't know the answer to a question, or if someone says, 'Hey, you're not a teacher,' then you're going to tell them." Hey. I don't know the answer to that question, but I'm going to find it for you. Or no, I'm not a teacher. But my partner, who works with me, is and she's an expert in this area. Shane: Yeah. That's also, we invent problems before they happen. And then our mind has to deal with them. And that's a problem, and that's something that me and Jocelyn really fight against is what ifs. What if someone sends me a question that I don't know? What if someone calls me out? They send me a reply and they're like, "You're not even a teacher. I can tell"? What if? What if? But until it happens, it's not really a problem. We can prepare for that. Like Jocelyn said, you can have the script ready. You can rewrite it in your brain. But until it's a problem, don't make it a problem because we have enough problems to deal with in online business and any kind of venture, that are real, that we have to deal with today, to invent problems that may never even exist. Jocelyn: And that's something that is really effective for me. I was just saying to go ahead and prepare for that. It's something that I've done a lot. When I was doing Elementary Librarian years ago and I was raising my prices, I was raising them from $89 for the full year, which is insane, to $400 and something for the full year. And I knew that when I did that people were going to be upset, that they weren't going to like that because they're used to paying this price. And now they're going to have to pay a new price. Jocelyn: One of the things that I did is, I wrote a response because I knew I was going to have people say, "Hey. Why did you change this price? This is bad. I don't like this." I went ahead and wrote a response to those people. I had not even increased the price yet. But I knew that I was going to have a problem with doing it because I perceived that people were going to be upset. And how many times did I have to use that script? Maybe two or three, maybe. But it made me feel better to know that I was prepared if someone had that response. Shane: Your brain kind of dealt with it. You just kind of dealt with it. So maybe you could write down the four things you think someone ... What are you afraid of that people are going to send to you? Like, hey, are you even really a teacher? What's your response to that? And then categorically like: Why should I pay for these things? You just write a response for that. Maybe if you just do two or three of those, you've got them in your back pocket, and then you can say, "Now forget about any other ghosts that I'm imagining. I'll deal with them as they come." Right? But at least you'll have a couple responses to the big one. And you can just kind of move on. Luke: That's a good idea. I like that. I had not thought of doing that. Shane: Yeah. From talking to you so much in the community and on member calls and in our workshops and stuff, I feel like you and Jocelyn are kind of on the same wavelength. You know? Jocelyn: I'm sorry, Luke. Shane: Yeah, right. Yeah. But I don't deal with things like Jocelyn does. I'm kind of just like, "I don't care. I'll just deal with it when it comes." Like that, but that's how I mentally deal with, because I have the same struggles. I worry about people doing this. I worry about people thinking that. My solution is just ignore it until it becomes a problem, and then fight it then. But I think you're more of the, hey, I want to be prepared for this. I want to dot my Is, cross my Ts. So maybe think of the four big things you are afraid of, that you think people are going to call you out for in that imposter syndrome. Go ahead and write a quick two paragraph email for each one of them and have it ready. And then forget about the rest until you move on. Luke: Okay. I will do that. Jocelyn: Okay, Luke. We talked about some fears and obstacles that you're having in your business right now. Let's talk about how we can help you grow more. What is your question for us today? Luke: I think my question kind of centers around sales. I had the first annual sale. And then there was a bit of a pause. And then a few more sales came in. Now I've got actually three annual members and five monthly members, so it's growing and it's moving. But it's not as quick as I'd like it to be. And I'm struggling with knowing what's next. What lever do I pull next to get things flowing more effectively? Do I do more ads? Do I send more emails? Do I do a bit more of everything? What should my focus be? Where should I put my efforts? Shane: What a great question from today's guest. We'll get to the answer of that in just a moment. But first, did you know that you can get the answers you need to start, build, and grow your online business too? All you have to do is join me and Jocelyn and Luke and all of our other members inside of the Flip Your Life community. You can get all the training, coaching, and support that you need to build and grow your own online business. The best part, you can get started today for free, absolutely no cost to you. Shane: All you have to do is go to flippedlifestyle.com/free, and you can start your one month free trial right away. Join hundreds of other family focused entrepreneurs from all over the world inside of the Flip Your Life community. You can learn how we started an online business, replaced our income, quit our full-time jobs, and now we get to work from home. You can build a life that you want, and you can get started today at no cost. Just go to flippedlifestyle.com/free and start your free month today. Now let's get back to our show and back to our guest's question. Shane: All right. The interesting thing about your story, Luke, is where you're at because you've been doing this now for a while. You finally made the first sale. You finally made the second, the third, the fourth sale. You're getting some traction. You're getting that monthly recurring revenue going. And even though you feel like you've been in the game for a while, and you want things to accelerate so fast, you're just at the beginning. Everybody thinks the beginning is the day that they sign up for the Flip Your Life community, or start their website, or make their first product. But all of that other stuff is just preparing you for the beginning. I kind of think of it like an athlete. An athlete start ... Our kids play sports. Anna Jo does gymnastics and cheerleading. Issac does basketball. They're both really young right now. They're just in lessons to learn how to do the flips and learn how to shoot the free throws and learn how to do the lay ups. They're just starting to play in their first games and do things like that. Shane: And then they're going to go to middle school. Then they're going to go to high school. And let's say that some day they get to go and play in college. Right? Well, really the first day of your career as an athlete starts there. All that other stuff has been leading up to that moment to get you ready for your actual career. And that's kind of where you are now. But the problem is we want it to happen now fast. You want to go straight to the NBA. Right? You're like, "I'm ready. Let's go pro, coach." But it's like, it can't happen that way. You've got to kind of look at yourself and say, "No. I'm still in ... This is the beginning. This is the true beginning, the foundation of my business." Shane: It's not like you're going to be able to pull a lever and just wow, 500 members in the next three months. What we've got to do is, we've got to figure out a progression. We've got to figure out drills, those everyday things that you do to start adding this thing brick by brick. And I say that only to get you ready for this mental shift of, I've got to be happy with being the glacier and not the forest fire. I want to be a slow moving thing that adds something every day to my membership. Maybe it's a little bit of ads. Maybe it's a little bit of promotion. Maybe it's a Facebook Live. Maybe it's an email, whatever it is. But we've got to get you mentally shifted to now growing slowly because the turtle always wins the race every time you read the book. Shane: We don't want to burn out. We don't want to get 50 members and then it dies. We want to build an everlasting, long running, stable, successful business. That's what I want you to be really focused on first is that mental shift of, it doesn't have to happen fast. It doesn't have to accelerate, especially now because this is really your first step, is getting these first few members. Next year is where you might make a 10X growth. You know what I'm saying? That's what we found. We were steady Eddie for the first year. And then month 13 is where we accelerated. Right? And I don't want you to go into this thinking, "Why do I not have 100 members? I'm a failure. Why didn't everything grow? Why didn't everything happen?" It's because this is really just the first step. Jocelyn: With that being said, there are definitely some things that you can do right now to grow this thing already. And I imagine that you're already doing some. You're clearly ... You said you have ads on Google. You have Facebook. You have Pinterest, which is great. But I think right now what you need to do is figure out a way for the people who are already at your website to kind of spread the word for you. And the way that you do that, especially in this education field, is to find a way for them to share you without, first of all, blatantly asking for it because nobody likes that. And second of all, a way for them to increase their status. Jocelyn: The way that I used to do this on Elementary Librarian is that I would offer free trainings. It would be something that they wanted. For instance, right now is back to school time, so for librarians, I made a webinar about open house, some tips for open house, things that you can do. It's very timely. It's relevant. They want to share it with another librarian. It's totally free. It's something cool. It's something that everyone needs, so right now is the perfect time to do that. I'm not saying that open house is the right answer for your audience. I'm just saying find something that they would think is really cool and they would want to tell their friends about it. Shane: We grew our history business Facebook page to almost 5000 people, not by sharing cool lesson plans, not by running ads to sell them things, but we developed a strategy about two years ago. And we just made a commitment to we are going to share a funny meme every day that only a history teacher would really get. Right? And the result wasn't, hey, I want to grow my Facebook page to 5000 teachers. It was: Hey, what can we do to get people to share this page that are probably US History teachers? You have to focus on the steps and not the result. Everybody gets so into goal setting. And everybody writes their goals and puts their post-it notes on their mirrors and all this crap. Nobody ever does anything because they say, "I want to quit my job," instead of saying, "Hey, if I did X, Y, and Z every day, I would eventually get to quit my job." Everybody says, "I want to lose 50 pounds," instead of making a commitment to working out and eating healthy every day. Right? Shane: I'm going to eat ... I'm going to only drink water every day. If you did that, a year from now, you would look very different. Right? Same thing here. If you make a commitment to two or three actions to grow your page, to grow your site, to do what Jocelyn said, to give people status. The reason we picked memes is because people love to share funny stuff because then someone says, "Hey Bob, thanks for being funny and sharing that meme with me." They get the credit for it. Right? You've got to think outside the box and quit thinking about your content. And think, "How can we share? How can we grow? How can we do what it takes to get more eyeballs?" Because more eyeballs equal more money. Right? And then put the daily things in place and say, "I'm going to share a meme every day. I'm going to do like Jocelyn said. Maybe we'll do a free training once a month." How involved is your partner? Is she doing things live, or is she just making content? She doesn't want to be on camera, or what does she want to do? Luke: Primarily she just makes content. I don't think she really wants to be on camera. Shane: Okay. Then what you want to focus on is stuff like blog posts. That could be very interesting for teachers. So instead of a live video training, maybe you get her. Say, "Hey. Would you write me a blog post? Five tips for blank." Jocelyn: Maybe it's about new standards come out all the time. I don't know for sure if there are any new science standards right now. But maybe it's a guide to new science standards, something that people need and something that they would feel good about telling their friends about. Shane: And then maybe you could have her send you funny things that she sees about teaching because I'm sure she's in teacher circles. Your business partner's around people. They're probably sharing stuff with her. Just be like, "Hey, if anyone sends you anything hilarious, send it to me." And then what you do is, you take it and you kind of fudge it to whatever your people are. What we do is, one of the big things is, I can't wait until back to school, said no teacher ever. Right? What we do is, we say, we just take that same meme and we'll change the picture of it a little bit. And then we'll put, "Said no US History teacher ever." Or we'll just kind of bend it a little bit over to our thing to kind of focus our message in, and make sure that it's history teachers [inaudible 00:32:58]. Shane: One of the things I shared this summer was we had Independence Day, July 4th. Right? People share American flags and something like that. And I put a British teacher sent me this, and it was a British flag. And it said, "Happy Traitor's Day," or something. I don't remember what it was. But it was just like something that only a history teacher would actually laugh at and share. Think of things outside the box. You've done so much content work now. And you guys are really focused on education and curriculum. Now you have to build a tribe. If you sent a thing to all these email lists, you've got 300 emails. Right? Are they all biology teachers, chemistry teachers, science teachers? What are they? Luke: High school biology teachers. Shane: Right. Send them an email that's funny. If you see one of these memes about biology teachers or something. I'm sure there's something funny about a dinosaur or something you can figure out and find. Right? Don't be afraid even to email all 300 of those people this funny picture just to brighten your day. And it says something funny. And then put, "Forward this to all of your teacher friends," because there's probably more than one science teacher in the building. Do the same thing on social media. Find a strategy that lets people want to share your stuff, and not just, hey, I have a lesson plan for tomorrow. Jocelyn: But the big key for me is to do it in a natural way. You don't want to say, "Share this with all your friends." Don't do that. Luke: Especially on social media. Jocelyn: You want it to be something that they're going to share on their own without being asked to do it. Shane: Yeah. Jocelyn: All right. I would start there. I think that is a great way to grow your audience, mostly just by serving them. Think about what they want, what they need, and what they would be willing to tell their friends about. Shane: What ideas have you guys had, have you had, to grow your audience? Forget about sales right now because if you focus on audience growth, the sales will come. Right? Forget all the ads. Forget all the promotions. And forget all the flash sales and Black Fridays and all that stuff. How have you thought to grow your audience in this space based on what you've learned about them in the last year? Luke: You know, honestly, I don't think there's been a real focus on how to grow the audience. It's been on content creation and ring ads and the technical side of the website and some blog posts, but no real focus on: How do we grow an audience of high school biology teachers? Shane: Right. And that's what you've got to figure out next because if you don't get more eyeballs, then you can't possibly have hands attached to them that can reach for their wallet. Right? Luke: Right. Shane: Ads can be a part of the strategy. There's nothing wrong sometimes with promoting stuff that's not necessarily sales related like a good blog post that only a biology teacher would care. Those are things you can promote to create awareness, to get more people on your list. And then once you get people on your list, you can sell to them. But no audience, no growth, no business. Jocelyn: Just knowing you like we do, because you've been part of our community for a while, you're willing to do the work. You just need to focus on promotion now. Shane: Yeah. I think the main thing here is, and this is the lesson to take away. What could you do every day and every week and every month? And if you just did it consistently, you would have no choice but to grow your audience. Things that we've chosen in the past, like our daily thing was a meme. Our weekly thing was a piece of content. And our monthly thing was an ad campaign or a webinar. That's something we've done in the past. And it's like if you just do that every day, every week, every month, and you just say, "Hey. This is the path. I'm just going to do this. My business can't help but grow." Six months from now it's going to look really different. You're going to have 3000 people on your list instead of 300 because you did those things. Shane: Think about: How can I get more people to like our Facebook page? How can I get more people then to click something to give me an opt in? And how can I do that every day, every week, moving forward through this year to build this audience that will create explosive growth next summer, or as we go along? Right? Luke: Okay. Consistent, steady growth of audience and a little less focus on making more courses and more material and more content. Shane: Yes. That's always. Anytime anyone says, "Should I make another course?" We usually nine times out of 10 say no because you've got tons of curriculum. And also too, she's making the curriculum, your business partner. You know what I'm saying? You don't even have to worry about that. You just need her input so that you can get creative and say, "How could I do X every day?" And maybe it's a five minute thing. Maybe if you schedule it on Sunday night and just something happens every day. But every day, your biology teacher audience has an opportunity to share something. Because if you don't give them the opportunity, they can't do it. If you're not doing something every day, they can't do it. That's why I email my list every day, because if I email my list every day, and I give them value, and then I give them a link to click and make them pitch something ... Or to pitch something, they then have an opportunity to go join the free trial or buy something from us. Shane: If I don't do it that day, I did not give anyone an opportunity to buy something from me. If we share a meme every day on our history site, well, every single day all those history teachers have the opportunity to share that. I think one of our last posts got like 1000 shares. And it's because we gave them the opportunity to. Really, you've just got to give people an opportunity to become a member of your audience. And then you can give them an opportunity to buy your product. Luke: Okay. Seems so straightforward when you put it out there for me. Shane: It usually is. People want the magic button. They want the magic tool. They want the magic whatever. But really, it's like if you just did these things consistently and prolifically every single day, your business couldn't help but grow. You couldn't help but lose the weight. You would overcome the obstacle if you just did it step by step over and over. And also, that mindset shift of be patient. It's not time yet for that growth. That growth usually happens at a tipping point. You get the snowball. You roll it down the hill. It looks like a snowball. It looks like a snowball. Whoa, it's getting bigger. Whoa. What happened? All of a sudden, now it's like 2X, 10X. It's an avalanche. That's kind of what online business has to do to run its natural course. Luke: Huh. Okay. I'll stop looking for the avalanche. Jocelyn: Exactly. Shane: Yes. Jocelyn: Well, you can look for it, just not right this second. Shane: Yeah. The avalanche isn't caused by the avalanche. The avalanche is caused by the gust of wind that blew the first snowflake into the snowball. Right? And that's how the avalanche starts. Or it's the guy that yelled, and it echoed and it rumbled. And then it all came down the mountain. That's what you're trying to do right now. Jocelyn: But keep doing what you're doing because I think sometimes people are constantly looking for something new to do. But you're doing a lot of the right things. You just need to do more of the right things. Luke: Okay. Yeah. That's been another one of the shiny object syndrome. It's like, okay. Check mark. Got that one. Sale made. What's next? Shane: Yes. And like really, that's usually where most entrepreneurs fail because what you should say is, "I got the first sale." And then you got three more. What caused those sales? Do that every day for a year. That's all you've got to do. That's why we switched our business model to this free trial thing because we were like, "Okay. What if people got in our membership? They would see how awesome it is and they would stay." Right? The answer was let's just let everyone into our membership for free for a month. And then they'll see how awesome it is, and they'll stay. And that's what happened. Shane: But now it's commitment though. You can't ... If you're going to do one thing, you've got to do one thing. We've got a sales page up, but you can go in there for free and you'll see what it's going to cost the next month. But everything's free. Everything points to the free. Everything does that. Whatever caused that thing, hey, I ran an ad that got this, that did this. I shared something that got shared that did this. Just do more of that. Find what works, find the nail and just hammer it until it stops working. And then you find something new. Shiny object syndrome says, "That thing worked. I wonder if something else will work too." [crosstalk 00:41:22]. Jocelyn: And we deal with this too. We were just talking about this the other day. Shane: All the time. Jocelyn: Shane's like, "What about these 18 things?" And I'm like, "Well, the business is not broken right now. Let's just do more of what we're already doing." He's like, "Oh, yeah." Shane: Right. I'm just passing on Jocelyn bombs. She told me that two days ago. Right? Jocelyn: Yeah. Sometimes I think we try to invent problems, even though we really don't have any problems. You're getting members. You're getting paid members. You don't have problems. You just need to keep it going, grow more. Shane: And also too, it's like a mentality of it's now or never. It always feels like that, doesn't it? In your online business, it's like, if I don't do it in August, I'll never do it. If I don't do it in July, I'll never do it. If I don't do it in September, I'll never do it. I'm getting sales now. I need more sales now, or it's going to all fail and go away. And it always feels now or never. But that's not really it. It's just like: What's the strategy this month? It might change a little next month, but it's going to be the same things with different content. Right? You've just got to get that mentality of one step at a time, baby step it, keep going forward. Okay? Luke: Okay. Jocelyn: All right, Luke. It has been a fun conversation today. I have loved the mooing especially. Before we go, we always ask our guest: What is one thing that you plan to take action on in the next day or so based on what we talked about here today? Luke: I think what I'm going to go and do is sit down and face my imposter syndrome and find out. Make some templates. Make some emails, some responses to questions that I'm afraid of having in my inbox. And just let my mind be okay with the fact that they may come, but if they do, I'm ready. Jocelyn: Exactly. I love that. I think it is a really important strategy even if no one ever asks the question. And they might not. At least you're prepared. It just makes you feel like you have a mental check box that you've checked off. Luke: Yeah. It sure does, so I like that plan. Shane: All right, man. Jocelyn: All right. Thank you for [crosstalk 00:43:14]. Shane: We've got another call. And I've got one at my door, so we're going to jet. You take care of those cows, and we'll talk to you soon, brother. Jocelyn: Bye. Luke: Thank you. Bye now. Shane: All right, guys. That was another great interview with one of our Flip Your Life community members. Before we go, Jocelyn, I always like to share a Bible verse at the end of all of our podcasts. Today's Bible verse comes from Proverbs chapter 13, verse 11. And in the Bible it says, "Wealth from get rich quick schemes quickly disappear. Wealth from hard work grows over time," so do what it takes to build a stable, successful, growing business. Put in the work. Make the investment. Don't look for the get rich quick schemes. Don't listen to all those people out there that tell you, you can do it fast. Build your business so it will be there for you and for your family in years to come. Until next time, do whatever it takes to get out there and take action. Jocelyn: Bye. I hear some gentle mooing in the background. Shane: I do hear gentle mooing. Are you near a cow pasture by any chance, Luke? Luke: I live in a cow pasture. Jocelyn: That's fantastic. Shane: I think that's a first on the Flipped Lifestyle Podcast. Mooing. We've had dogs barking. We've had kids walking in eating bags of chicken. We've never had a cow. Never had a live cow on the show. Good job, Luke. Links and resources mentioned on today's show: Luke's website Flip Your Life community 30-day trial Enjoy the podcast; we hope it inspires you to explore what's possible for your family! Get your FREE 30-DAY Membership in the Flip Your Life Community NOW! – https://flippedlifestyle.com/free You can connect with S&J on social media too! You can connect with S&J on social media too!   Thanks again for listening to the show! If you liked it, make sure you share it with your friends and family! Our goal is to help as many families as possible change their lives through online business. Help us by sharing the show! If you have comments or questions, please be sure to leave them below in the comment section of this post.

Mike: Welcome back, server nation, to Process Server Daily, the number-one podcast for legal support professionals. I am your host, Mighty Mike, the podcast server. I'm excited about today's episode, and I look forward to knocking your socks off. Let's get right to it. Mike: Welcome back to the show, server nation. We are joined by the owner of Alaska Investigation Agency, located in Palmer, Alaska. He started out his career in the Army Reserves and transitioned into private investigation in 2001. Since then, he has owned and operated numerous investigative agencies across the country. Luke Smith, welcome to the show. Luke: Thank you, Michael. Glad to be here. Mike: Thanks. So Luke, tell us a little bit about how you got started in the industry. Luke: About 15 years ago, 16, 17 years ago, a friend of mine was a police officer in Mississippi. He invited me to go do some surveillance with him on some private cases that he was doing, and I fell in love with it. The investigations morphed into process serving, and so now I do both. Mike: That's excellent. Do you remember your first job, your first investigation job? Luke: My first investigation job, I remember it very well. It was a cheating spouse, and I lost the husband in, like, the first block of trying to follow him. Mike: But you've learned a lot since then, right? Luke: I have learned so much since then. I haven't been burned in quite a while. Knock on wood. And I like to think that I'm pretty good at what I do now. Mike: That's awesome. So we don't like to focus on the negative stuff. As humans, we get a lot out of the negative and rising out of the negative and going into the positive, like finding your path in life. And so my first question always starts out with, tell us about your worst experience working in the field. Luke: My absolute worst experience, I was working a child custody case one time, and I was part of the team that located a mother, and I helped the troopers physically take the child away from the mom. Although it was what was best for the child, it absolutely broke my heart, and I realized then that child custody was not for me. Mike: How do you deal with that, Luke? Luke: You go home, and you hug your kids a little bit tighter and a little bit longer, and you move forward. I know it was what was best for the child, but it still was just heartbreaking, and I even tear up now sometimes when I think back to that child screaming and yelling and wanting his mommy. Mike: Yeah, as a parent we always relate it to our own relationships, and you want to be able to help them. But like you said, it was probably what was best. If the mom spends a few weeks without her kid, a few months without her kid, she might turn things around. You know? Luke: Absolutely. Mike: Luke, what do you want server nation to take from your story? Luke: What I want server nation to take from that particular story is just do right by your kids. Yeah, just be good parents. Mike: That's awesome. Yeah, being good parents is a great thing, and so you can ... Being in this job, one of the beautiful things about this job is you get to see the worst of the worst and you know where things could go. I don't know. In some respects, it makes you happier. You know? Luke: It does. Mike: Let's go to the positive now, Luke. Tell me about your greatest experience working in the field. Luke: I tell you what. I did a job a couple of weeks ago, and I followed a gentleman to a restaurant, and I sat down at the bar two people away from him, and I videoed him eating lunch. And then I followed him to his hotel. Six hours later, I followed him to another restaurant, where I sat right next to him at the bar, and we had dinner together. Mike: Wow. Luke: And then I followed him back to the hotel, and I rode up the elevator with him to find out which room he was in in the hotel. In that particular job, I think I pushed it to the limits just to see how far I could go, and it was such a satisfying feeling because he never had a clue I was even there watching him. Mike: So I'm going to sound like a total new, but did you feel like a CIA agent or something? Luke: Every day. Mike: Oh, that's awesome. Luke: No, I feel that way every day. Mike: What I take most from your story is enjoy what you're doing and go after it. What do you want server nation to take from your greatest experience? Luke: Take a few risks, ask that person that you're following to hold the elevator for you, and if you're trying to find someone and serve someone, ask questions. People love to talk, and they will give you just about all the information you need if you sound like you are supposed to have that information. Mike: Interesting. So I've heard it said before that you ask a question, not a direct question, but a related question that some stranger might actually ask. Luke: Absolutely. Mike: That's a pretty cool ... Do you guys still call that sub rosa? Luke: Yes. Mike: Okay, cool. Look at me knowing all the terms. Okay. So Luke, tell me what you're working on right now that you're most excited about. Luke: I guess probably one thing that I love that I have coming up is I'm adding a canine unit to my business. Mike: That's definitely something worth being excited about. Are you getting German shepherds or ... Luke: I'm getting Belgian Malinois. And actually, I have the opportunity to hire a handler that already has two Mals that are already trained. Mike: Wow. Luke: So I'm super excited about that. Mike: So Luke, tell me, why would you need a canine unit? And I think I know the answer, but could you just tell the audience, as a private investigator, what would you use a canine unit for? Luke: There's so many different uses for a canine. Here recently, Alaska has become one of the states that marijuana is now legal. However, you have a lot of corporations up here that it's still against company policy. So we can run the dogs through the companies to ensure that the employees are not breaking policy. There's no law enforcement side to it, but we are not law enforcement officers, so that's okay. The other area is we found that there are a lot of real estate agents that will have us run the dog through a house to make sure that there's no drugs in the house or there was no meth lab in the house or anything like that, just to limit their liability. Mike: Oh, I never thought about that perspective. Just the civil service. Luke: Sure, yeah, absolutely. So we're really excited to get that up and running. We've already nailed down a few contracts, and so we're really excited about that being a part of our business. Mike: Well, that's definitely worth being excited about. I am excited to hear about how you go and serve people on a snowmobile. How does that happen? Luke: Yeah. So Alaska offers unique challenges to the lower 48. Where are you from, Michael? Mike: I'm from New Mexico, but I'm based in Chico right now, in Chico, California. Luke: We're the largest ... obviously, the largest state in the United States. Here's a good comparison. Denver, Colorado, has one and a half million people. Alaska, there's 700,000 people. So we're the largest state in America, but we have the fewest people per acre or per square mile even of any other state. And so of course, if you call me and say, "Hey, what counties do you serve?" we don't have counties. We have boroughs. And we're statewide, but let's say, for instance, I serve the Matanuska-Susitna Borough. The Matanuska-Susitna Borough is the size of West Virginia, so we have maybe 300,000 people that live in the borough. And so if you could imagine West Virginia and 300,000 people, they're pretty spread out. Mike: Wow. Luke: So there are tons, I mean, hundreds of villages across Alaska that are only accessible in the summertime via plane or boat or a four-wheeler. In the wintertime, you either take a plane or a dog sled or a snow machine. I mean, that's just part of what we do, and we have planes and snow machines and four-wheelers all at our disposal for serving papers and working cases. Mike: That's why you feel like a CIA agent when you're out there because you're in planes and ... You ever jump out of a plane to go serve someone? Luke: No. Mike: Come on! Luke: No. I did jump off of a four-wheeler once. Mike: Wow! And then I heard something about a moose chasing you. Luke: We have wildlife scattered across Alaska. And inside the city of Anchorage, there's a very large population of moose. I've been chased by moose. I've turned corners and been staring a moose face to face, and you just slowly back away. You don't need that 1,800-pound animal trying to trample you. We have bears that you have to deal with sometimes. Luke: So obviously, everywhere we go, we're armed to the teeth, ready for really the wildlife, not the people. But yeah, I've been chased by moose. I've never been chased by wolves, but I've felt them kind of breathing down my neck, if you will. That one was interesting, a little bit scary. The moose aren't really scary. You just know what to expect from them, and you respect them. This was their land first, so we're just visitors on their land anyway, and they believe that. Mike: It's the truth. Luke: Yes. I have video of moose walking down the street in Anchorage in the middle of traffic, and they just do not care. Mike: That is awesome. Server nation, Luke has been dropping some major value bombs on us today, telling us all about Alaska and the crazy private investigation stuff that he's got going on, from the canines to the planes and the quads, you name it. But prepare yourself, because we're headed into the rapid-fire round right after a word from our sponsors. Recording: Server nation, I know you're with the times, and you want to do whatever you can to have all of the resources for your client. That is why I created 123efile.com. As a process server, attorney, or even an [inaudible 00:10:59], you can visit the website and file your documents in any of the Tyler courts in California. With its easy-to-use, one-page operation, you can have your e-filing done in a matter of minutes and get back to what really matters. If your time is important to you, visit 123efile.com. Mike: Okay. Welcome back to the show. Luke, are you ready for the rapid-fire round? Luke: I am, Michael. Mike: What is your favorite skip-trace tactic? I imagine it's got to be a little bit different in Alaska. Luke: My favorite skip-trace tactic is going and asking the wildlife if they've seen my skip. Mike: You said asking the wildlife? I had to think about that for a minute. I was like, did you just say ask the wildlife? Luke: All right. You know, my favorite skip-trace tactic, I think, pretending to be a guide because there's so many fishing and hunting guides in Alaska that you can call just about anyone up and say, "Hey, I'm a guide, and I'm looking for this person. They booked a thing with me, and I'm just trying to confirm," and they will tell you where they're at, where their mom and dad are at, how to get in touch with them, what they drive, when they come home. They'll give you everything because, up here, hunting and fishing is a big business, and it's a big deal. Mike: So who do you call for that? Luke: The skip that I'm looking for. Mike: Oh, you call the person. Oh, wow! Luke: Or their family members. Mike: Oh, wow! So they're like, "Yeah. Oh, you're a guide. Yeah, let me get him over here." What's the incentive for them to help you, though? They're like ... because it's their friend or family, and they want to connect them to the guide? Luke: So many people up here need to hunt and fish just to feed their family. It's the sustenance thing. So maybe this isn't the best wording, but I prey on that a little bit, if you will. Mike: No, yeah. Yeah, that's awesome. I mean, we manipulate things all the time. People say, "Hey, what are you doing stalking that girl?" I go, "Oh, that's my job. That's what I do." What is your favorite tool for defense? I know you said you're armed to the teeth. What does that entail? Luke: You know, my favorite tool for defense depends really on where I'm going and what I'm doing. I always carry a firearm everywhere I go. I am a certified firearms instructor. But if I'm going out to some of the remote locations, I'll carry a shotgun along with my sidearm. I do carry concealed when I'm in most areas because I don't want to approach people looking like law enforcement. Mike: Yeah. Luke: And in Alaska, everybody carries a gun. It's legal to carry a gun here concealed or otherwise, and so everybody has one. So even people walking around showing their sidearms, it's not really that big of a deal. My personal preference is to keep it concealed, though. But if I'm going, like I say, out to remote locations, I'll carry a shotgun mainly for bear protection. Mike: Well, that's awesome. That's some cool defense. What kind of pistol do you carry? Luke: I carry a Glock 19-9 millimeter. Mike: Luke, what book would you recommend? Luke: What book would I recommend? Mike: From guns to books. Luke: I know a couple of different people that have written books, and one is a skip-trace queen. Her name is Valerie. She wrote a book, "Skip Trace Secrets." That's a very, very good book. And then also another friend of mine, Kimberly, wrote a book about process serving and mayhem, and she's got tons of funny stories in those. I can't remember the exact name of that book, though. Mike: That's okay. I'll look them up, and I'll link them in the show notes. Anybody who's interested can go to processserverdaily.com/Luke, and they'll see all the show notes word for word and the links and everything. Luke: Perfect. Mike: Luke, what is the greatest advice you've ever received? Luke: I think the greatest advice that I ever received was be professional, be respectful, and be ready to take care of business regardless of what that is. Mike: To close this awesome episode, can you tell me what parting piece of advice would you give the servers out there that are ... Maybe they're struggling. Maybe they're new. Maybe their business is circling the drain, and they don't know what they're doing wrong. What advice would you give them? Luke: My advice to all the servers out there across the board is be professional, do not be judgmental. We don't know what people's stories are. Do what you say you're going to do in a timely fashion, and hang in there and just keep pounding the pavement. Mike: That's awesome. So if you had to start your business over again, Luke, how would you ... What would be the first thing you would do? Luke: I would go get a job somewhere. Mike: So you would work for another company? Luke: If I had to start my business all over again, I think I would probably have made a lot of contacts prior to opening my business because, in this business, that's what is very, very important, is your contacts. Mike: That's perfect. They say your net worth is your network. Build your network, and you'll grow your business. Luke: Absolutely. Mike: Luke, what is the best way that we can connect with you? And then we can say good-bye. Luke: You can connect with me through Facebook or my website, alaskaaia.com. Mike: So Luke, I want to personally thank you for coming on this show, man. This has been really cool. I'm excited to share it with the world. Luke: Thanks for having me, Michael. Mike: Well, I'm going to have to come visit one day. Luke: You do that, buddy. Mike: All right, partner. Well, until next time, server nation, you've been served up some awesomeness by Alaska Luke and Mighty Mike, the podcast server. Server nation, I want to personally thank you for listening to today's episode and ask you a question. Do you or your staff need additional training? Can you handle more clients, but you're not sure where to get them? I've developed a solution. Psduniversity.com offers a step-by-step online training by the top legal support professionals in the industry. Visit psduniversity.com.

AFTERBUZZ TV — Galavant is a weekly "after show" for fans of ABC's Galavant. In this show, hosts  Megan Salinas, Jacque Borowski, Blake McIver, and Katie Cullen discuss episodes 7 and 8. Screenwriter/executive producer Dan Fogelman (“Crazy, Stupid, Love,” “Tangled,” “Cars”) teams up with Broadway and Hollywood award-winning musical team—composer Alan Menken (“The Little Mermaid,” “Aladdin,” “Beauty and the Beast”) and lyricist Glenn Slater (“The Little Mermaid,” “Tangled”)—for a musical comedy fairytale of epic proportions. Once upon a time, the dashing hero, Galavant (Joshua Sasse) lost the love of his life, Madalena (Mallory Jansen), to the evil King Richard (Timothy Omundson). Now, our fallen hero is ready to take revenge and restore his “happily ever after.” But it won’t be without a few twists and turns along the way. “Galavant” stars Joshua Sasse as Galavant, Timothy Omundson as King Richard, Vinnie Jones as Gareth, Mallory Jansen as Madalena, Karen David as Isabella and Luke You

Luke: You've heard the stories, now experience the power of these stories as we take an in depth look at the gospel according to Luke.

Luke: You've heard the stories, now experience the power of these stories as we take an in depth look at the gospel according to Luke.

Luke: You've heard the stories, now experience the power of these stories as we take an in depth look at the gospel according to Luke. Title of Message:  The Temptation (James 1:13-14) (NIV) When tempted, no one should say, “God is tempting me.” For God cannot be tempted by evil, nor does he tempt anyone; but each person is tempted when they are dragged away by their own evil desire and enticed. (James 1:15-16) (NIV) Then, after desire has conceived, it gives birth to sin; and sin, when it is full-grown, gives birth to death. Don't be deceived, my dear brothers and sisters.   (Luke 4:1-2) (NIV) Jesus, full of the Holy Spirit, left the Jordan and was led by the Spirit into the wilderness, where for forty days he was tempted by the devil. (Luke 4:2-4) (NIV) He ate nothing during those days, and at the end of them he was hungry. The devil said to him, “If you are the Son of God, tell this stone to become bread.” Jesus answered, “It is written: ‘Man shall not live on bread alone.'” (Luke 4:5-8) (NIV) The devil led him up to a high place and showed him in an instant all the kingdoms of the world. And he said to him, “I will give you all their authority and splendor; it has been given to me, and I can give it to anyone I want to.  If you worship me, it will all be yours.” Jesus answered, “It is written: ‘Worship the Lord your God and serve him only.'” (Luke 4:9-12) (NIV) The devil led him to Jerusalem and had him stand on the highest point of the temple. “If you are the Son of God,” he said, “throw yourself down from here. For it is written: “‘He will command his angels concerning you to guard you carefully; they will lift you up in their hands, so that you will not strike your foot against a stone.'” Jesus answered, “It is said: ‘Do not put the Lord your God to the test.'” (Luke 4:13-14) (NIV) When the devil had finished all this tempting, he left him until an opportune time. Jesus returned to Galilee in the power of the Spirit, and news about him spread through the whole countryside. The Top Temptations: 1.    Temptation toward something good. (Luke 4:2-4) (NIV) He ate nothing during those days, and at the end of them he was hungry. The devil said to him, “If you are the Son of God, tell this stone to become bread.” Jesus answered, “It is written: ‘Man shall not live on bread alone.'” (Luke 4:5) (NIV) The devil led him up to a high place and showed him in an instant all the kingdoms of the world. 2.    Temptation to Instant Gratification (Luke 4:12) (NIV) Jesus answered, “It is said: ‘Do not put the Lord your God to the test.'”  (1 John 2:16) (NIV) For everything in the world—the lust of the flesh, the lust of the eyes, and the pride of life—comes not from the Father but from the world. 3.    Temptation for Security (2 Corinthians 2:10-11) (NIV) I have forgiven in the sight of Christ for your sake, in order that Satan might not outwit us. For we are not unaware of his schemes.   Leaving Temptation in the Spirit 1.    When am I tempted?  2.    What is my temptation? 3.    Who is with me when I'm tempted?