Podcasts about alex do

Patrick discusses the roles of husbands and wives and the importance of love and submission. Patrick also provides valuable insights on determining the legitimacy of charities and religious organizations. And, of course, we take calls from listeners who share their questions and experiences.   Joseph - I don't like how you handled the divorced man. You shouldn't have talked with him about penance, instead you should have loved him. Fred - Regrading Judas: I think that Judas could have repented in the last moments. Is that something I can believe? Rafael - I think that we are all different. If someone wouldn't have told me I need to repent, I would be sinning today. I think you do great. Carrie - I think your response was with love. I think you did a great job. Linda - I thought you acted in a loving fatherly way to the person who was getting divorced. I think you did well. Alyssa - Is Yu-Gi-Oh okay for my kids to play? Karen - How do I discern which religious solicitation are legit that I get in the mail? Alex - Do you think the way they portray Judas in movies makes him seem more innocent than he was? Monica - What does it mean to be a submissive spouse and the man's role in this? Mike - What does it mean to drink too much alcohol? Where is the line?

Hoy hacemos una selección de jazz navideño un poco alejada de lo habitual con Juan Ortiz, Yellowjackets, John McLaughlin, Chick Corea, Steps Ahead, Herbie Hancock & Eliane Elias, Everette Harp, Dave Brubeck y Geri Allen para terminar estrenando un tema navideño de Matías Mingote y su banda zaragozana Ñu Grup.Temas que puedes escuchar:   01 2022 Juan Ortiz Brighter Days 05 Christmas in Bilbao Hiroshi Takase Gene Jackson (6' 37'')02 2003 Yellowjackets - Peace Round. A Christmas Celebration 05 Peace Round Bob Mintzer Russell Ferrante Jimmy Haslip Marcus Baylor (4' 42'')03 1995 John McLaughlin - O Come O Come Emmanuel (Jazz to the world) (3' 21'')04 1995 Chick Corea - What Child is This (Jazz to the world) (4' 08'')05 1995 Steps Ahead - Angels We Have Heard On High Michael Brecker Don Grolnick Mike Mainieri Eddie Gómez Peter Erskine (Jazz to the world) (5' 18'')06 1995 Herbie Hancock & Eliane Elias I'll Be Home For Christmas (Jazz to the world) (2' 51'')07 1995 Everette Harp Duke Stanley Clarke O Tannenbaum (Jazz to the world) (6' 07'')08 1996 Dave Brubeck A Dave Brubeck Christmas 12 Run, Run, Run To Bethlehem (3' 43'')09 2011 Geri Allen - A Child Is Born 04 O Come, O Come, Emmanuel I (7' 21'')10 2020 Ñu Grup - Snowflakes - Armando Miñana Alex Doñágueda Carlos Calvo Guillermo Lacámara Maribel Vistel Senda Romero Matías Mingote (3' 12'')Os recomiendo, como siempre, la web jazzaragon y el facebook juanemiliojazz.

This week's Misfit Entrepreneurs are Alex and Leila Hormozi. Alex and Leila are an entrepreneur power couple. They have scaled three companies to well over $100M in cumulative sales across 3 different industries (software, service, eCommerce) and continue to grow. Their companies include Gym Launch, a service and coaching company, Prestige Labs, a premium supplement company, and ALAN a lead management software firm. In fact, they took Gym Launch from 1 employee to over 70 and $28 million in revenue in just 3 years. Needless to say, Alex and Leila have not only figured out how to scale and grow companies quickly and effectively, but they've also found the right balance as a couple to do it well and I want to dig into all of this with them in this episode. Alex Hormozi Podcast – The Game Alex and Leila both have Youtube Channels where they give a lot of advice Alex and Leila met in 2016 through online dating. Both were very focused on their careers. But they met for the first data and found a lot of commonalities including their love of business and their backgrounds. How they saw business was similar. In fact, after Alex heard what Leila wanted to do, he told her to skip all that and come work with him. Over 3-4 weeks of them talking and her learning more about the Gym Launch concept, she saw a great opportunity to work together. She ended up leaving her business and joining him with Gym Launch. They ran the business as just them for a year and then began to build out the teams, etc. They actually were doing such a good job that some gyms could not handle the capacity they were creating for them, and it caused problems. In fact, Alex and Leila almost gave up. They re-worked the business model so they or a rep for them did not have to be present and things took off. From there, they got into supplements specifically for gyms. They also developed a lead management software and other solutions. Alex mentions that they had a logistically challenged business that they had to fix, even though they were very good at doing what they did. Alex was good at the solution side, but Leila is really good at putting the team and leadership into place. What has been your secret to working well as a couple? Leila They want to be around each other is the foundation. You have to desire to be around each other all the time. There is never anything between them – they don't allow things to go un-addressed, fixing them when they come up. Delineating each other's responsibilities is important. Making sure to drive toward the same goals. How does your dynamic work or change during tough times? Alex We are fairly even keeled. It's important to separate a circumstance from emotions. It is not a reflection of who you are, it just is.  Separating the stressor from the response is a key skill. Finding out what information each other is working with that the other doesn't have when there is a problem. Staying in each other's lanes when it comes to making decisions in the business is also very important. They trust each other to make the best decision, but seek input as needed. What are the principles you use to develop a successful business and teams? A lot of it is psychology. Really understanding people and making sure to put them in the best place to succeed. Being willing to have good, but hard conversations. Working on your emotional intelligence is very important to success. You pick the people, you assemble the people, you coach the people. “Sharp mind, kind heart, strong will.” Core values: Candor, Micro-speed/macro-patience, have humility, give credit/take blame At the 23 min mark, Alex and Leila talk about their culture… “To have a great company – marry the smarts and the hearts.” Explain your marketing and lead strategy… Fundamentally, there are 2 ways to grow a business: Get more customers or make it each customer more profitable. Fancy fails, simple scales. Paid media, earned media, owned media are the areas of marketing. Referrals are one of the best and easiest ways to grow. You should not scale other areas until the word of mouth is a significant driver of your business. Mastering an area is that it will continue to produce once you've set things up and don't have to be involved in it constantly. Give an example of a front-end offer that works well? Win-win. For Gym Launch, a customer can start using Gym Launch absolutely free and if they don't make at least $4000 in their first 30 days, you don't have to continue. Back-end? Value ladders should never stop. You solve problem one and problem two, but solving problem two creates problem 3 that needs a solution and so on. Value ladders typically stop at the level of competence of the entrepreneur selling them. Your job is to continuously grow your ability to find and solve problems building out your value ladder. Alex's book on this is called Hundred Million Dollar Offers ​ Best advice for an entrepreneur starting out today? If you are not moving at the pace you want to look at what you may be lacking. Is it a skill? Is it a belief? Is it a character trait? Identify this and go seek it. Let go of any identity that you hold – identity is habit and may not serve you in the way you need to succeed. Start with a blank slate and become the person you need to be through the habits needed to succeed at what you are doing.   Best Quote: To have a great company – marry the smarts and the hearts.   Alex and Leila's Misfit 3: Alex: Think in decades not months. ​ Leila: 99% of your thoughts are not true. Alex: Do the boring work. Leila: ​Feelings are not to be obeyed, but something to be managed. Alex: Volume begets skill. The more you do, the better you get. The better you get, the more you do. ​ Leila: ​Learning how to make smart decisions is one of the best skills you can require. Don't build up decision debt. Show Sponsors: Check Out Freshbooks' "I Make a Living Podcast" www.Freshbooks.com/podcast 5 Minute Journal:  www.MisfitEntrepreneur.com/Journal

Part II:  Alex Doñé, chief investment officer of the $225 billion NYC Pension Funds, shares with us the advantages and challenges of investing on behalf of the 4th largest pension fund in the world. Alex also provides his perspective on hedge fund opportunities and describes NYC Pension Fund’s commitment to co-investment opportunities. And in this episode, listen to what Scott Pittman, chief investment officer of Mount Sinai Health System, asks Alex in our CIO to CIO question.Check out Accelerate Investors programs and events (where you can connect with some of the chief investment officers live!) at Events. Become an Accelerate Investors Sponsor. 

Alex Doñé, chief investment officer of the $225 billion New York City pension funds, the fourth largest pension plan in the world with 730,000 beneficiaries, shares with us his career trajectory to becoming chief investment officer. He also imparts his career advice for underrepresented people in financial services and Alex discusses the importance of investment management reflecting the diversity of the NYC pensioners. (Recorded December 22, 2020)Check out Accelerate Investors programs and events (where you can connect with some of the chief investment officers live!) at Events. Become an Accelerate Investors Sponsor. 

We're slamming toilet seats on our things again, as we join Alex and the Pruitt family in 1997's Home Alone 3.Episode 18Topics Include:Alex learning to pump gas Asking parents to tell us a story from the old country Never borrow money from Alex Do child-less co-workers deserve weekends off too? Let your kids decorate their own room Cringing over "This is a very safe neighborhood" Alex's first ride with a Drunk Driver The worst way to watch a movie for the first time is at a family event. Both Alexs' find gunsAriana dismisses Alex's fan fiction about Mr. & Mrs. Pruitt Lasso - PhoenixSi Lo Quieres - La DiferenziaMy Town - Cartoon Boyfriend

更多英语知识，请关注微信公众号: VOA英语每日一听 Alex: So Maria, what are your future plans?Maria: Future plans, that's a big question. I would like to have a nice career. I'm not really sure what it would be. I would love to be a CEO of someplace, someplace big but I don't need to. I just want to have a prestigious job because I'm that kind of person and I want to have nice pay and I want, I think it's more important to me to have, it keeps on being interesting. I'm very afraid of just ending up with a job that just bores me to death or something. I do want a family. I hope I'm about to find the guy I will have a family within the next couple of years because otherwise I'll have to start looking and I'd rather have the love at first sight thing or just like having it be normal instead of just having to look for it like those desperate women you see in the TV. Have a nice house maybe in Denmark I'm not sure. I love big cities and Copenhagen is awesome but I'm not sure if it's big enough for me. I might go to Tokyo, a place I studied Japanese and I might go to or I might go to another European country. I have something with Holland. I keep getting friends from Holland or connections and I get attracted to Dutch people for some reason so Amsterdam is a choice. My parents wouldn't mind me going to Amsterdam. They want me close. I just, I don't know, I would like my future to be kind of unclear.Alex: OK.Maria: Because I have friends who've known they wouldn't want to be a doctor or a nurse or a teacher since they were five and that's just I need to be able to change whenever I can.Alex: Do you think you would change your career if you felt that it got too boring or...?Maria: I don't think I know I will change. I will just say phew.Alex: So you'd want to be able to fit your work to your life as opposed to the other way around?Maria: I might be a little self-centered because I have to be satisfied. I can't just, I have had jobs like part-time jobs or very short time jobs just because I had time and I get impatient very fast if it's not if it doesn't work for me I just hate getting up in the morning and if it's going to be my life. Studying and having a part-time job you can live with it. You can live with a bad job but having to do it every day, having to do a bad job every day just like it seems pointless to me.

更多英语知识，请关注微信公众号: VOA英语每日一听 Alex: So Maria, what are your future plans?Maria: Future plans, that's a big question. I would like to have a nice career. I'm not really sure what it would be. I would love to be a CEO of someplace, someplace big but I don't need to. I just want to have a prestigious job because I'm that kind of person and I want to have nice pay and I want, I think it's more important to me to have, it keeps on being interesting. I'm very afraid of just ending up with a job that just bores me to death or something. I do want a family. I hope I'm about to find the guy I will have a family within the next couple of years because otherwise I'll have to start looking and I'd rather have the love at first sight thing or just like having it be normal instead of just having to look for it like those desperate women you see in the TV. Have a nice house maybe in Denmark I'm not sure. I love big cities and Copenhagen is awesome but I'm not sure if it's big enough for me. I might go to Tokyo, a place I studied Japanese and I might go to or I might go to another European country. I have something with Holland. I keep getting friends from Holland or connections and I get attracted to Dutch people for some reason so Amsterdam is a choice. My parents wouldn't mind me going to Amsterdam. They want me close. I just, I don't know, I would like my future to be kind of unclear.Alex: OK.Maria: Because I have friends who've known they wouldn't want to be a doctor or a nurse or a teacher since they were five and that's just I need to be able to change whenever I can.Alex: Do you think you would change your career if you felt that it got too boring or...?Maria: I don't think I know I will change. I will just say phew.Alex: So you'd want to be able to fit your work to your life as opposed to the other way around?Maria: I might be a little self-centered because I have to be satisfied. I can't just, I have had jobs like part-time jobs or very short time jobs just because I had time and I get impatient very fast if it's not if it doesn't work for me I just hate getting up in the morning and if it's going to be my life. Studying and having a part-time job you can live with it. You can live with a bad job but having to do it every day, having to do a bad job every day just like it seems pointless to me.

Hello, and welcome back to the lead generation for financial services podcast. This week we have got an old friend, Jodie Stevenson. Almost a year ago when we had our first podcast interview and that went to be the number one downloaded episode of last year.For every enquiry, she gets the leads, CRM, check for notifications and will schedule a chat with her client. And to make sure that she's on top of everything she uses a blank sheet of paper and knows exactly the template and just writes everything and gets it organised. She does that for every client until she runs out of paper. Recently she bought a notepad by Rocket Book. It is reusable, can automatically scan, upload to dropbox, digitally file, and then wipe clean and use again. And again.And if you happen to look for something like a file created 6 months ago, Rocket Book can easily find it for you and locates it in your dropbox file.Cost is £34.99. They've done microwavable one as well where you write in it and put it in the microwave and it will erase everything. It's a huge impact environmentally and it helps save a lot of waste.Transcription:Alex: Hello there, welcome back. And we've got an old friend with us. This week, we're catching up with Jodie Stevenson and it was pretty much a year to the date that we had our first podcast interview. And it went on to be the number one downloaded episode of last year, and of all time, so people talk about her a lot, actually, when they've, I think it's one of the kind of the earlier episodes that people sort of pick up on because it's one of the first mortgage brokers that we interviewed, and they've come on to become the most popular episodes. So I really enjoyed catching up with Jodie. So let's dive straight in. Hello, and welcome back to the lead generation for financial services podcast and I can't quite believe it's been a whole year since we last caught up with the one and only Jodie Stevenson. How's it going?Jodie: Thank God it's one and only. I can hear my mom saying that, thank God.Alex: We were just saying, how was it? You were like, no, it's nobody You know, it could have been a year but it has.Jodie: But then we were talking about things like, what things have had like you're like, a quarter of a person that you were then you were last year.Alex: We haven't got a video either away. But yeah.Jodie: Now you're super skinny. Don't worry, though. I'm still fat and consistent for the world. got consistent and but yeah, no, it's, that's great. There's actually been a lot of things that have really happened. So if you actually like, pile up the achievements that both of us have had in the last year. Actually, that makes sense. It's probably like a decade's worth of achievement. So yeah.Alex: It's funny, isn't it? Because you like them day by day, week or week, month or month thing you know, I haven't really done a lot. I've really improved a lot if anyone needs to literally think about doing a 360 and see Oh, this time last year I was doing this, you know, what.Jodie: Yeah, exactly. Well, I mean, I taught a human to walk this year, which is, technically he taught himself. I'm taking the credit. And if he was walking funny, I wouldn't be taking any other credit for it. But like, yeah, like he's actually like, he's doing the real things. Like he's really doing things this year. Like he's, he's learning words. And oddly, he's learned the word jacket. It's one of his jackets, he calls me Jodie instead of mom, which is awesome. Yeah, so shouts Daddy, and Jodie, I'm like, thank you very much.Alex: Excellent, excellent show you love that. Because I remember obviously we had theWow, it's just a sad thing. Obviously, we had the dogs barking.Jodie: Oh yeah, Thrasher and Baker. Oh yeah, yeah. Oh, that happened in a bowl we got em. So they went to live with another Basset and Mum, basically, because we were part of a really good dog network. And so they went to live with this lady who's got like four others and they are just they are so happy. I don't even think the fact they're like maybe because yeah, they live on a farm now and there are loads of dogs there and they absolutely love it. And so yeah, that was a yeah, that was sad but i think i think we could be kind of at the point with you could hear how chaotic it was in the background. They were just like, they were just like, let's go for a walk. Let's go here and I was like no. And so yeah,Alex: It is. Yeah, having a child, a human is a lot I wouldn't have been able to do with pets.Jodie: Yeah, but pets that I had created my own problem with the pets because it was too small of a house, too big of dogs, and not enough boundaries between anyone you know, the dog slept in bed with me and it just wasn't, you know, it was a recipe for disaster. And luckily they've gone somewhere where they are even further mollycoddled than they were with me. So they're there, they're even better off now. I think that's really it's a really big lesson as an adult when you make a decision that's going to hurt you and only hurt you, but it's going to help someone else. So the dogs were going to be better off. I was going to be sad. And I had to make that decision and be like, Okay, well, I guess I'll just be sad then because they're gonna be happier. Real adult learning. So yeah, it was super sad like I was gutted about it, but I think it was the right thing for them.Alex: I know, absolutely. Do you know what I was just looking up while you're telling me that, so I thought I better just check because I knew yours was a very popular sewed for a while it was the second most downloaded? But you want to know something quite exciting that it was the number one downloaded episode of all time.Jodie: Really? That's amazing. That's awesome. Yeah, you know, it's my dulcet tones. It's my lovely calming accent that ASMR of mortgage advisers.Alex: Say well, I would like to say part of the credit of doing something super exciting with the title of like a mortgage broker generating their own leads doing blah, blah, blah, blah. So I'd like to take a little bit of credit for that.Jodie: That's okay. You can.Alex: I'll take 30% of the credit. Jodie: Yeah. Alex: That's the number one so you'd be there. So David Thompson. So Gary was seventh, and then you don't talk to a second, Me and Tom doing an episode were third. We should have been first you know, that's an absolute disgrace. You got ash, Ash ball and fourth. So what was interesting actually the top, the top five are not if you take out me and Tom, the top five are all brokers. Jodie: Okay, cool. Alex: So now, you know we've had a lot of marketing experts on dishing out marketing advice. One thing I've learned over this year is that actually getting people like yourself and hearing your stories is what people are interested in. Jodie: Yeah, what do you know what though it's something that I found throughout my life and we had at the bank, we have people who would come and work for us. And you were like, university graduates and they'd come in on a graduate course or something, they'd come straight into management. And the rest of the bank was just like, nope, don't I don't want to know anything this person's got to say because you haven't lived this life. You haven't come from the ground up. And this, you know, it puts there's a lot in it. There really is I can sit there and say, Look, I know how to market for mortgage advisers because I am a mortgage advisor. Alex: Yeah.Jodie: I'm marking all myself. And this works rather than someone you know, just coming in and saying, This is what and we could probably be doing exactly the same thing. Alex: Yeah., no, absolutely, absolutely. I think it's, it's being it's easy to put someone to be like, um, you know, Jodie is a broker she's doing that what you know, why can't I and then maybe they think if there's someone who's not worked in it, and it's easy for them? Yeah. It's just easier to make a connection with people that are like you. So. Yeah, that's awesome. And then you had you, as supposed you are the only one as well that we got on that was doing Google Ads themselves. I don't think I spoke to any of the brokers that have been doing Google Ads themselves so are you still on your radar? He's still doing that. Is that anything else overtaking it, or Is that still the number one.Jodie: Now, I mean, I obviously had a baby. So there was a period of time where I wound it down. And I've continued to supply leads. So I still had a handful of loyal clients who just kind of kept buying from me over that period, but I stopped taking any of my leads. And so for about six months, I kind of just backed off from it, and then came back in sort of the back end of last year, I think a little one's gone to nursery now. So yeah, I'm kind of back in it now. And, and it's, it's a blend again. So obviously the network that I'm with b2b, they provide me with leads. And, and I also have my Google AdWords, which, and they're just two very different types of leads. And they all have different conversion rates, and they all work but I don't think you should ever turn a lead source away and you know, if If you can, as long as you are meticulously recording how many times you did everything to in that lead, you know, did I pick the phone up and dial them? How many times did I literally put my hand to my phone? And because then you can figure out how much putting your hand on a phone makes you might be 74 P. But, we can take it right back to that.Alex: Absolutely. I think I saw there was someone a broker showing me their screen and it was like one of their self-employed brokers had only logged two calls. They were saying that this I've not been able to get out as person but it was like two calls a week apart both before 5 pm. And it was like they were I can't remember how long after it was the lead initially dropped. But it was they were reporting it but not doing enough. And I think there's a case of people not being as meticulous as you are with that. I'm not chasing it enough.Jodie: Wow. I would as always, I'm going to be going against the grain here. No, I don't have the needs. I didn't do it, man, I don't do it. Look, if you want a mortgage, I'm going to touch. Here's my number. I if they put in an inquiry, I mean I would the b2b, b2b have their own structure, which is you know that you make an X number of calls, and we have a system that sends them texts, etc. And those ones, you know, that's, that's James's method, and I use that. But for my own needs I when the lead lands, I try within 10 minutes and firing them it's straight off the bat. So I go straight in and I call him because speed stones and it always will and a lot of the times they answer the phone and go oh, oh, didn't expect you to ring me that fast. And I'm like, exactly. I give them a ring straight away. And the chances are they are still sat by the computer. And so they get that one call and then and then I'm never in the zone. And then if they don't answer, I send them a text and I say, Hey, it's me from this company. I'm bringing about your mortgage when good, that's all I do. That's it. I can't find them again. Nope, I bring them at the moment and then I send them a text and that's it.Alex: Do you mind sharing what percentage of contact right there is like what percentage of like, no contact is that you know.Jodie: my contact rate is I have this down the other day I've actually I'm mentoring someone at the moment. So I'm more in my own KPIs than I ever have.Alex: While you're looking at apps are gonna it's like two very different things going on because If you are buying leads or if you're marketing in a way that you're not building any rapport you've you've only got that quick window because they'll forget about you. But if you're marketing and people know you quite well and they've bought into already then you can wait. So I don't think everyone I always think older minute coders are always like you say within 10 minutes.Jodie: Oh, I love that.Alex: Yeah, well little phrase for you.Jodie: YeahAlex: While you're looking at apps are gonna it's like two very different things going on because If you are buying leads or if you're marketing in a way that you're not building any rapport you've you've only got that quick window because they'll forget about you. But if you're marketing and people know you quite well and they've bought into already then you can wait. So I don't think everyone I always think minute older minute coders are always like you say within 10 minutes so I love that. Well, little phrase for you. Yeah. It because it literally is because they'll because if they because there's a lot of things that are important to people at that moment, like mortgages, especially protection that is important at the minute and then once the laptop gets close, I will it was important 10 minutes ago it's not important now because this is happening. So you miss if you miss that window, I think you're missing out. A big one. But it just depends on a case by a case like how well are you have you? Like, do people know you for that one thing and they've already decided that only gonna deal with you.Jodie: No, my leads have no idea who I am mainly, my leads are very much advertised on an in a cold no company we are a company, we can find you the things you would like as your details to have a call and, and so yeah, just give them a ring or give them a quick call. And then I'll send them a text and send them an email. So send them a text and an email. And if they don't come back to me, you didn't want it that much.Alex: Yeah, I wonder though, I'd be so interested to see the numbers like because you're you've got personality, definitely. If people got to know you a little bit beforeJodie: I leave a voicemail, I do leave a voicemail. So maybe that's why I get a lot of callbacks and I get a lot of texts back.Alex: And I think people prefer to communicate in the text.Jodie: 100% of the day. I do.Alex: Yeah, I think my big thing for us this year is to give the end-user the person that wants the mortgage, give them as wide of options as possible to communicate. And not just say, it's only a callback, you have to have a goal, but it's like, how do you prefer to us to get back to that email? Whatsapp? Facebook Messenger? Jodie: Yeah.Alex: Text, phone, and then let them just I think there's a lot of leads being missed, because people are going through and there, and there, yeah, I need a mortgage or I need advice. I've got this situation, and then the only they'll fill all the details out, and the only option is a callback and they'll sort of agree to it and then they'll think but whereas if it's something like WhatsApp, then they don't have to set that timeout to have a call because no one wants to be sold to and the broker can go away if they've done a fact find on the website. If you've collected all that information, why maybe go back to them with something and then build-up to the call.Alex: Yeah, exactly. I something like I think it's a month ago. And I needed to do something with my energy supplier. And I logged in and there was like to write live chat or like live chat, but I always forget it's open. You know, when you open it, and then you just walk off, just forget you have live chat open.Jodie: I’m so confident. I'm terrible with it. So, it clicks on this live chat thing. And it was like, Oh, do you want to just Whatsapp? I was like, Oh, yeah. So Whatsapp. And it just opened a WhatsApp chat with my provider. And then they just kind of got back to me throughout the day. Alex: Yeah. So as a broker, like whether you've got advisors working for you or not, and some people don't want to give them Oh, by the way, you can get a prepaid SIM and you can have WhatsApp away. So you can have all your WhatsApp communications open on a browser window to the on as you and it's so much more organized than email as well when I'm doing a whole sort of project on facilitating WhatsApp Web for clients. We've been looking at WhatsApp chatbot as well, which is not as good as the Facebook Messenger stuff. But again, if people want to do it, we're on it because if we can get as much info on if someone and then the only thing is one, someone said their network won't allow WhatsApp communication despite it being the safest. And I could say I covered which network it was where they were like they ban any communication whatsoever knowing that WhatsApp is more secure than email. That's bonkers. But either way Yeah, that's definitely on our mind because I think a lot of people just don't want to have a phone call.Alex: See, very I'm sort of taking over this episode. So what so what else? So are you doing more of the commercial stuff on your ads before? Exactly it was commercial mortgages pretty much that you were doing last year my rightJodie: Yeah, yup. So my advert saw more commercials but I do get a lot of isolettes through it as well. And yeah, but mostly it's battleaxe for so it's a limited company and Alex: That does seem to be a very popular minute obviously with all the sort of tax changes and stuff. Yeah. How are you finding it like demand this from this time last year to now the B-word is kind of semi sorted is that affected anything or our market like?Jodie: I would say that pre-Christmas which normally December is my salon and the month where I don't do anything, and January is just like I'm continuing to not do much. Outrageous this December was, I mean, right up until Christmas Eve I was still dealing with clients and taking and taking upset on Christmas Eve. Crazy.Alex: We saw one on Christmas Day.Jodie: No..Alex: One every Christmas Day, there’s always one.Jodie: I don't even think I'll pick my phone up on Christmas day it's just yeahAlex: Yeah everyone's different so people get bored and they're like but yeah I mean I was cooking on Christmas Day literally in a second but yeah that that did happen.Jodie: yeah now I've been really busy and really really busy and very much and that's kind of what my year is about this year is understanding how to manage the famine and the feast know get tons of leads in and when you're very quiet and then you know talking to me building it all up and then they kind of all slowly come back in and then you end up with like if anything you end up with too many inquiries because then you've gone too many people coming back and it's kind of I'm trying to figure out what that nice even let's take this many leads a day constantly rather than taking you to know 40 leads a day for two weeks, nothing for another three weeks. So that's what my plan is this year is to find my sweet spot.Alex: of literally the number of leads per week per day. Jodie: Yeah, yeah.Alex: And what was taking the most time for you, when you're sort of dealing with inquiries? Where could it like, Is it like,Jodie: what's that? Sorry, packaging cases? And okay, so that's always the most time-consuming part. And in any mortgage, getting the leads is fine, cuz everything's automatic. And it's also CRM, and it's perfect. And the notification comes through on my phone, I click a button and get it's great. And, but then once and I have a chat with a client, and that's fine, and I don't. Do you follow me on Instagram? Alex: Yeah. Jodie: And did you see the space paper that I got delivered yesterday?Alex: Oh, God doesn't know if I've been on the last couple of days.Jodie: So whenever I get an inquiry, I have a blank sheet of paper. And I know exactly the template of my fact find a blank sheet of paper and I just write, write all and it's all organized, you know, left side for Mr Right side to miss it, and it kind of all ends up looking like a fact find. And so I do that sheet of paper for every client, and then I write on that until really, I've run out of paper and it becomes a client file. And then I take paper, clip it in, and then they become a file. And yeah, well, that is pretty, you can imagine I've got like 60 notebooks piled up next, which is crazy. And so I've actually bought a notepad by rocket book. And it's a reusable notepad. Alex: What. Jodie: Yeah, so you write in it. And then you get your phone, you get the rocket dog app, you scan it over, and it uploads it into Dropbox into a file, wherever you can put file names on it, and everything, and then just wipe the page clean and start again.Alex: Oh my God.Jodie: It's like actual paper and so yeah, that I'm hoping that's gonna save me a bunch of time because now it's got handwriting detection as well. So all my notes now get uploaded into a file. So when a client rings me back in six months time and says hey you know Mr Donovan, I can just open my rocket dog file and go Donovan and it will find that note pad that page of my notepad and go that's that client it might just say Donovan, ah avoid you know, but it will be and that'll be on the new anywhere I am. I can just click it'll be in my Dropbox and I can just search for that name anywhere I don't need my notepads anymore. And because it will all be on this. This Dropbox so I thinkAlex: Then 34.99 I'm just on the road getting a rocket book. Why not? Not mega expensive.Jodie: Yeah, and the efforts are hilarious. I mean, you'll really enjoy him. It's just two guys in there like, they're just having a blast making these books clearly they've done a microwavable one as well where you write in it and then put it in the microwave, and it just erases everything. And but that has a shelf life. And, and something I'm really conscious of at the minute is the impact that I'm having, you know, environmentally. There's a lot of paper in my job. So I'm kind of wherever I can, I'm avoiding a paper. Because everything else in my life pretty much I know I doesn't really have minimal impact with most of the things I use are usable things in most of my life but then in this just reams and reams of paper that I'm printing, I feel terrible.Alex: It's literally my desk at the minute. I've got these A3 papers where we spent sort of between Christmas and New Year like coming up with different ideas days for campaigns and what can be doing better and I've literally got a flood of these A3 bits of paper that I could have done in this. If they do an A3 version. I'm all over, I might get the small one anyway because I do use it like my notebooks.Jodie: What size is a4? So A3 is quite bigger than A4Alex: Yeah.Jodie: I think A4 is probably the biggest that they do but you could open both pages because it's 32 pages.Alex: YeahJodie: Maybe you could open both and just have it on there but you know if you do it small and then just blow it up.Alex: Yeah, well, it's my birthday coming up and the misses were like, what can I want I can kind of get you sort of you never want anything and anything you want you but I could just send you this thing.Jodie: Do it because honestly, I was saying that is such a good present for people. And it's the last one is the one I got and it when it gets delivered. It looks like a bag of space food because it comes in the old space bag. I feel very modern, very.Alex: Yeah. I love it with these things I always get annoyed that I didn't invent it myself.Jodie: Yeah, my dad, my dad has invented everything before anyone else did. And, every time a product comes out, he'll remind me of the conversation we've had four years ago where he invented that and he's right, you know, we have and I say, well, maybe it should actually do one of those.Alex: Yeah. Oh well, I used to work at an agency and this guy called Kazu came like a freelance designer and he just comes in, he sort of lives in our office. We used to work together and our old boss used to say that he invented Facebook before Facebook Like all the time.Jodie: Oh, I bet he didAlex: It’s in his head, but then never did the difference. Zuckerberg did something about it. That's the…Jodie: I think I invented iPhones and I definitely think I did. I had all the passion for an iPhone, in my mind. Alex: Yeah. Jodie: But it just was the translation that I just, you know, probably by the time they came, you know, when I'm thinking of and they were probably 10 years in development anyway. Alex: Yeah, exactly. Jodie: So though they'll be imprinted in our fingers soon.Alex: Really? Exactly. Yeah, exactly. So, other than digital notebooks, what else is new?Jodie: So yeah, my digital notebook is very new. I'm mentoring somebody.Alex: I was gonna say you mentioned it earlier. Yeah.Jodie: I believe she found me on your podcast.Alex: Well, do you know that happens a lot. This podcast doesn't cost me a lot of money. It cost me time. I don't make anything from it. But I seem to have made like other people. Like some really good so there's like, lots of like, pretty much every guest I've had on saying so and got in touch. We'd like to do this. Amazing. That's great. It's brilliant that I always find it bonkers that people actually listen. And they still listen. And people actually do stuff out of it. So that is.Jodie: I probably get one or two messages a month that say, Hey, I heard your podcast episode. And I'd love to have a chat with you about what you do. I'd love to buy some leads off. Alex: Amazing. Jodie: Yeah. One or two a month at least.Alex: Well, I was just looking at when I looked at your episode stats, I was like, Oh, this has had eight downloads in the last week. And I was like, well, that's like one at one a, obviously, more than one a day and it was over a year old. Least not being advertised. People are picking it out. So yeah, I mean, that is amazing. Amazing to hear. And then I say I didn't get anything out of it. I mean, we get inquiries all the time. I don't ask everyone where they come from. But that's cool. So how's that mentoring? Say what's in terms of the minute you mentoring them on, are they on like everything or just marketing? Just Google Or literally the whole, the whole.Jodie: So initially it was a marketing job really, that she just wanted something to learn. And as we kind of got talking, it just kind of organically became, we were both in a really similar position actually in our lives and her kind of wants to be in the same sustainable situation that I'm in where we can have our children and be the mums that we want to be and run a business that we want to run without having to sell Aloe Vera. Or, you know, these ridiculous shapes that people sell or anything like that. It's just a true Korea and true business. Alex: Yeah. Jodie: And which is lovely to see that people look at me and think, you know, that that's an aspirational and Korea, which is, you know, it's great. So she approached me and I said, Look, you know, I'd love to expand outwards and as well not just physically but potentially for my business. Well, but yeah, let's, you know, let's, let's do it and let's just kind of cobble through it together. And so that's kind of where we're at. She's taken a leap of faith on me and I have to leap of faith on her and we're just trying to figure out how that works. And so that's where we're at. I'm kind of guiding her through how I set up myself. And then we would slowly integrate her into her own being our own broker. And eventually, she's just been doing it a few months now. We've had Christmas, so it's been a little, you know, nonstarter over Christmas, but she's doing amazing, she's got 10s of thousands of pounds in the pipeline, which is crazy. And you know, not all of that is going to go anywhere. But you know, even if I think we've said like, you know, roughly she probably roughly banks to bank seven grand. And I would say, out of everything that she's had through, which is just gorgeous in it, you know, take this leap into like a totally new field and then get in a big pipeline like that. AndAlex: What I love about 99% of the brokers 99.99% brokers I know and speak to also just get as much satisfaction out of like, genuinely helping people as well and they and they and they get rewarded for it. It's like what it's like, I'm almost jealous of the rewards that you guys get from helping people as well as what you get in return. It feels quite a unique kind of job that it's kind of a must to be satisfying.Jodie: Yeah, it really is and do they want and I needed it as well. I really needed it because I started to doubt my own hipe last year and you know, when you have a kid you lose your identity completely for a period of time. And I came back and was like, right i mean obviously I have my group that was on your podcast which is still it still exists but it's just because I didn't know how to help these people and you know they were all asking me and I was like I don't know just how do I do this I'm a parent and how do I do it? How do I do it? And I know me and you know conversations about that and definitely minute old minute cold is, you know, plays on my mind with these people. And so when this really naturally just progressed into something and mentor wise, I was really happy because I was like, Okay, I can do this. And, and I can help and even if all I do is just give her the tools and then send her on her way and Alex: Yeah.Jodie: Because it is, I'm growing as a person, whilst I'm helping her grow as a person. And, and it might be that she goes off and does it without, you know without me in the future and that's, that's fine. And it's just something that I think I've, I've needed to do and it's a big learning for me as well.Alex: I think as well as you learn from teaching as well, she always won't feel giving advice to someone else to do something you sort of like, I find that when we're trying to I always feel like I'm looking at stuff more. So I'm not trying to help myself, I'm trying to help other people as well. So it gives me that extra edge so we've obviously got we've got the pressure of clients that pay us and we've got we've got to deliver for them otherwise we lose them and you know, lose house and family can't eat and things like that, but also that extra edge of wanting to help other people that what they do well or not And affect me, but it always finds, since doing the podcast and doing videos and things like that, that it gives it I've probably pushed myself to learn more to help share that kind of accent.Jodie: Yeah, exactly, exactly. I mean, I, I would have, I would have said I was very, you know, very efficient at my job. And I knew I knew exactly what to do, but actually, I just knew exactly what to not do. I knew what to avoid. I knew what I knew. And I knew I knew how to avoid the stuff I didn't know. And with this new, new starter, she's kind of expanded and been like, Oh, well, I'm looking at loads of stuff over here. And I'm like, Oh, no, I don't play in that court. But what I have to do now, so I've, you know, started doing that as well and funnily and, you know, growth, growth is, it's up and down and sideways. It's everywhere because I've had a really great opportunity as well as my father in law and my mother in law and Actually, I've started on the path to working for me as well. And right, so they're going to become mortgage brokers and buy their own rights, which is lovely. But also my dad is coming to work for me as well. And he's had a background like you had a family that had worked in. He's got some experience in it. Oh, yeah. Yeah. Right. Yes. So he was a senior financial adviser for the bank that I worked for. And my sister was an advisor as well. And she's had a baby and she's going back to work in January, self-employed as well, which is lovely. And so we're all kind of doing it self employed. But yeah, my dad's come in to work with me as well. Which is great because he's the guy who kind of coached me and made me the person that I am. And now I kind of get to give a little bit back to him, but he loves me and he's going to help me from above and you No, it's going to, it's going to go everywhere. And it's going to be really nice. And it's going to build a really nice little company.Alex: Family literally a family business literallyJodie: Literally a family business. Yeah. Yeah. I mean, my partner Matt, and he's always been like a rock in my company anyway. And when I have these, you know, packaging nightmares where I've got just, you know, reams and reams and reams of applications that I've got to fill in. He's just incredible. You just get straight on the computer and he's like, scans him in and, and does it all for me anyway, so I've always had him helping me. And even if sometimes it's just he just goes out with our thoughts. Leave Hello. Yeah.Alex: Yeah. Jodie: And so it's always been great and hands-on, but it's so nice that we're getting everyone else is kind of getting involved in it as well. And it's fantastic. Yes, it's lovely. It's quite a nice little family that we've got now. Really a family.Alex: Really Yeah. And I think just going back to what you said about Like growth being up down sideways my business mental talks about competitive with like climbing Everest is like the night before they go to sleep they climb up and then they have to climb back down again to like a climatized so it's always talking about the growth of that you're up and then you've got sometimes you've got to go back down to be able to push forwards again parallel so it's nobody can build a business with cute like continued growth will kill you.Jodie: Yeah absolutely. Isn't linear it's not you know.Alex: Yeah it's a graph, this graph should have these peaks where you drop down and then you that gives you the ability to then push back up again. So yes one thing is you always want like a month I always want growth, growth, growth, but the one thing he thought he taught me about was that it is normal and healthy to have no backs and I'm pushing on from there.Jodie: Yeah, yeah, exactly. And it's amazing what you can really beat yourself up on mean on AdWords I can, I can have a week where I look at my fingers and you know, they're costing me three times as much as they did on, you know, the month before and I will really panic. And I'll go Stop, stop the ads. And you know, it's just your instinct is to stop at that point but no, no, you need to stop because there's a reason why they're coming through at this. You know, it's because people really really want it or people you know, there's a lot of competition or whatever, but it always evens out. It always evens out over the course of a year and you always end up at the same cost per click. So there's a reason it's an average, you know, you're gonna have some weeks where it's half of your normal one that you just can't look in like that you've got to set boundaries and be like, I'm only gonna, I'm only gonna worry about it. If over the course of three months, my average cost is going up and then I'll worry andAlex: Yeah.Jodie: But even then don't leave it another three months.Alex: Yeah, exactly. Is that easy? Again, because when we do it like that with Google Ads absolute minefield in terms of like, we've got one company where the cost per click can range from like quid to four quid depending on the time of day and when other people are bidding and things like that. Jodie: Yeah.Alex: There are so many sorts of and it's difficult when if there are brokers with a small budget as well, those impacts will be felt bigger than one whether someone's spending like 50 grand a month compared some of the spending 500 pounds those ups and downs have felt much bigger with the smaller budgets definitely.Jodie: Absolutely.Alex: Have you ever kind of looked at the thought about SEO being on page one top of page one for those keywords bidding on.Jodie: You mean organically?Alex: Yeah, organically. Yeah. Is it ever like, do you have SEO remorse as in like this time last year, if there was an if you knew what to do, there was a plan in place, and you could have executed it and by now a year later, you could have been position one.Jodie: I don't know, I've never really, I've never really seen the benefit of you know what, I am the person who scrolls past the ads and goes to the organic number one result, but I feel like that's the same as buying an ad anyway now, because people just strategically do things to make themselves the number one result, but it's not. It's not really, you know when you go shopping online, and it organizes things, you know, and you can do it from price low to high or whatever, whatever the default is never price low to high, its price, whatever is gonna make me the company more money. And they do it that way. So it's, you know, I don't necessarily believe personally, that the value of being number one, organically has the value that it used to. I think it just means that you're very good at SEO.Alex: Oh, yeah. Jodie: Just means you're good at getting number one on Google. Alex: Yeah, absolutely. What we find with a lot of our clients, the reduction in the cost to acquire a new client if they're getting free traffic from Google is is is the biggest one the biggest factors inJodie: Yeah, yeah. Yeah. In that sense, yes, definitely that it would be a cheaper option. But just for me, I feel like I didn't know that my audience is ready.Alex: What you’re doing now is work and I don't want your eye off the ball. So there's a lot of things in life like, don't if you've got something that is working, that's profitable unless you're obviously like, where you were their way or now. You don't want to change it. Yeah, I was just kind of interesting. If we're, if because you're getting those leads from Google, whether that was on your mind.Jodie: It is nice to know, it would definitely be nice to know. And, and, and I certainly, I certainly would be open to looking at it and seeing But I'm still in the same position that I was in before, which I know is always your favourite thing to hear from me. I don't need any more leads at the minute. I have to turn the machine off frequently. Alex: If you if we were to talk this time next year, and you didn't have to have the machine on at all, and they were all just coming in.Jodie: Oh, yeah. Yeah. be great.Alex: Yeah. So that was my I have a question. I should have asked that beginning. But ya know, it's interesting. And that's where a lot of we have all kinds of ads running literally, bar, no bar, none. All of them but they were the ones that are getting those. We work on SEO for all of our clients because of getting that free trial. And Google's great because it's people are like, well, like we said earlier about catching them within that 10 minutes. They're in the zone. Jodie: Yeah.Alex: Like Facebook, LinkedIn once you're there when they are in the zone and it's They haven't made the decision to go out and look for something. Yes. You've got to be even quicker with the social ads to get them But yeah, I think we're finding Google gives the best quality and if you can get it free so obviously it reduced like the possibilities cray LAUGHINGJodie: You had a podcast with Joe Mani.Alex: The thing I haven't asked because it's we have your name is coming up on my thing is Joe Mani but Joe Mani is that a self-inflicted?Jodie: Yeah hundred per cent you know what? funny because it's difficult to nickname my name because it isn't really you can't really other than Steve Oh, yeah, all coffee bit. Oh calling me like, which I don't like Joe Go. Yeah, exactly. So it has to be something. So after a while, it just became, I just used to put myself on board, you know, couldn't fit Jody on it. So I'd write j and then we'll do like $1 sign. So I was. So yeah, it's definitely a self-made Monica and that does not need to stick. Nobody knew that nickname mom. But just to go back to what you said about LinkedIn, and LinkedIn, such a funny little place at the minute. And I mean, I've turned my notifications off because it's too much, people, I don't know who in their right mind thinks that anyone is going to read a near eight paragraph-long message from a brand new connection. Either like, Hey, how are you insert name here, comma, I would really like to talk to you about insert profession here. Let me tell you a little bit about what it is that I do. It was 25 paragraphs about it and I'm like Blah, blah, blah, blah, blah. I just never read it.Alex: I agreed at the no who's speaking to a guy the other day. And they're kind of like an agency that does that can't that I outreach but in a very different way. And he was like talking about getting them to strike up a conversation like asking a question or something to start a conversation rather than just doing a whole sales blurb is like running up to someone in the street and just shouting about your business for like, 10 minutes.Jodie: Yeah, exactly. And I way prefer, like, I've had a lot of impact on a lot of my favourite messages on LinkedIn, or people who've listened to your podcast, and they will message me with something. And, and I'll, it always makes me laugh. It'll always be something funny in the message. It'll be like, Hey, I heard you on the podcast. And then they'll just say something hilarious. Along the lines, I think because I give a sense of like and look for a laugh. And they'll always always have a laugh. And even if all we do is just say, uh, you know, I'll say thank you very much. And I'll see Say that I mean, uh, you know, I mean a deadly baffle for number one. So please be free to download it 400 times.Alex: As much as we've done it. Jodie: Yeah, exactly, exactly. I'll send you all your five pounds in a minute. So we're at and, but well, you know, we'll have a laugh and we'll have fun and that's what I think that's what LinkedIn should be is a place to find like-minded business people to do business with. And to Hulu, and not to get too caught up on being everyone's cup of tea. Alex: Exactly, that's Yeah, if you're vanilla, like the, someone was asking me about, Tony, have you seen Gary Vaynerchuk?Jodie: Yeah, I love Gary Vaynerchuk.Alex: Yeah, but he is Marmite, you know. That's why if he was vanilla and trying to get everyone to like him, he wouldn't have the following that he has. So Jodie: Yeah.Alex: Pretty extreme example, obviously. But yeah. Like being yourself is.Jodie: Yeah, I'm a marmite well, hundred percent a marmite. And people literally do like me or they do not like me. And it's and you know what, I used to really struggle with that but now I'm just like, that's fine. There are plenty more people in the world and I like to be alone. I like to warm people up a bit I am a little bit of a troll by nature and I do like to sort of tickle people a bit, particularly on LinkedIn. And somebody put something at Christmas. I hate the boastful nature of Christmas. And I don't think people talk about the presence that golfing kids run said. And so I was on LinkedIn at some point. And this guy was like, What do you get the guy who has everything, and I think I responded with haemorrhoid cream. And if you say you've got everything, have you got a spare tenner?Alex: Yeah, brilliant.Jodie: Yeah. You know, I like to sort of make fun of people a bit but I think Yeah, LinkedIn has got to change to become a bit more. I think you've got to be aggressive with who you let in your circle on LinkedIn.Alex: Yeah, definitely. Yeah, I've really filtered.Jodie: Yeah, remove connections, remove connections. Yeah. Are you within a geographical distance of me that we can do business if not remove connection?Alex: Absolutely. I think it is a great platform and I'm slowly being marmite like I don't I put a photo on I think was yesterday and I've got I got bought two notepads for Christmas one says the Archbishop of Canterbury and the other thought of this as a warning Bantam merchant, proper cringe but I just took a photo and said I've got a really important meeting with a top dog Fs company but which notepad I never would have done that before because it's like, oh, I should be professional or not have a but then I think I've made more a double business got more friends out of LinkedIn and connections from being myself and not worrying about not being too professional or worrying about or not worried about anything actually other than just being sad.Jodie: Just don't do it. It's, you've got to you've just got to be yourself. I mean, you really have to just be yourself. My favourite people in the financial industry are you. I can smell I can sniff out a metalhead in a crowded room. I just know him. I know the people who you know they've got like a slipknot tattoo, I just know it. And I like a Rolodex of metal you know metal aficionados who are in the financial industry, and that's one that they're my people. So I love those people. And but then also people who, who have a criminally, you know, offensive sense of humour. That's, that's Matt der max. People so if I find a particularly funny person who also listens to, you know the same sort of music as me, you know that's a relationship for us. So if you're out there and you want to be my BDM please message me on LinkedIn and if you want to talk slipknot and deals let's do it let's I'm in the market for it.Alex: I'm really looking forward to someone opening a message or connection requests or doing some sort of reference or, or something like if you get that please do a screenshot and send.Jodie: I will put it on a T-shirt. Promise. Alex: Yeah, brilliant. We have been chatting for 50 of your English minutes Wow. Wow, it was like three.Jodie: It really does. Alex: What have we not discussed?Jodie: I think pretty much it and we've done exactly what I've been taught not to do there with it. We haven't done politics or what is it politics and religion not covered? That's good.Alex: We could do that next year. Yeah. Jodie: Okay. Yeah, definitely.Alex: It's so good to catch up with you. I can't believe it's been a year. It. It's absolutely bonkers. Yeah. And it's great that people are still listening to your original one. Still getting in touch with you. I can't believe I've been involved in something that makes that happen. I find that bonkers.Jodie: It's not the first situation that's gone viral for me. And I'm sure it won't be the last. Alex: Yeah, what was, go on spill it.Jodie: I'm not going to give you my medical records. No, I'm joking. And no, I put a few in. I often go viral actually. And I did it. I did a bit of a famous post about mediums A while ago and my disdain for the role of BDM. Right. I've always said, I stand by it. I don't think it's a role that that is relevant. I don't think it's a helpful role. For mortgage advisors when it's one person I think it's unfair on the person. I used to hate BDM but now I hate whoever makes a BDM do their job. I hate them. It's and it's not sustainable. It's not sustainable. You just need a call center that deals with those. But yeah, I did them almost like an X factor of BDMs. Once I put up that I don't like BDMsms and I refuse to use them. I actually completely refuse to use them now. I did have a few people who were like, let me prove you wrong Let me prove you right like so and so and a few of them did. Yeah, pretty much funny Penny Paul. But yeah, I got I ended up with quite a few connections through that who appreciated my angle which is Look, I want to know now the answer to my question, not seven o'clock at night when you've got home from I've been 16 coffees all day when you finally Got to read your emails. Like, the deal is with someone else at that point. It's, you know, it's crazy. But yeah, that was another thing that went a bit viral as well.Alex: Fantastic. So, if people haven't heard the first episode I'm following you know, I'm following you on Instagram. Jodie: Yeah.Alex: Where? Where? Where is that? Where's the BDM slugging going on?Jodie: Oh, it's on LinkedIn. Oh yeah, LinkedIn it's a really old post now I think and what it did it did get some traction and but yeah, you can find it on LinkedIn my Instagram is not a professional arena in any capacity it's just me but maybe yeah, maybe that's what I should do. Maybe I should start an Instagram for work. ItAlex: It should be one on one in one on the same.Jodie: Do you think?Alex: I think people buy from people.Jodie: I still talk a lot as a business on my Instagram, I just it's not like a business Instagram.Alex: I do not use my company Facebook page, my company LinkedIn, my company anything is all via me. And I get more out of it.Jodie: Yeah, I think I think that's the I think it's the way to go. And I do definitely talk about I always throw, you know, one or two posts a month up on my stories. Just saying no, don't forget, don't get life insurance. Don't forget mortgages don't get addressed. And, and I always get a couple of leads off of that. And even sometimes it's just people saying, Oh, I'm really interested. And we just have a chat. And then I'll come back to me a little later and we'll talk about it but yeah, yeah, I think you're right. I think you should keep it all as one brand.Alex: Nice. Love it. Awesome. I can't believe we're with them. I think we need to do it closer than a year. We need to catch up when I need to kind of get you drunk. You belong to one of our events as well so people can meet you in real life.Jodie: Wow definitely, definitely. I would love to do that and get the winter over with so I can come out as my winter cocoon. And yeah, but definitely Yeah, just invite me along I think you went to Did you go to u printer?Alex: Yeah, yeah it didn't just go It was on the stage.Jodie: Exactly. I think I need to go.Alex: It is an amazing event.Jodie: Yeah.Alex: Really good. Jodie: I should definitely make it to some sort of physical social interaction at some point in my life and stop the piano. Avoid at the end of the phone.Alex: We've got our events in March there's gonna be a load of brokers there in the lovely Peterborough March the 26th. I will send you a link.Jodie: March is pretty clear for me. So where I could probably squeeze you in. I’ll try my best.Alex: I will. Fantastic, awesome. All right, cool. Well, let's do that let's meet properly in March.Jodie: Yeah. Alex: Let's speak again soon. And I'm loving that you get in the family involved and things are growing and I like your partner helping you out with every I was like visualizing oh no exactly what it's like having a kid ourselves. But yeah sounds like it sounds amazing and I'm glad everything's still going really well for you.Jodie: Yes Yeah it's great. It's all a learning curve and to sayAlex: Oh god yeah Jodie: We’ll see, you never know listen if you know God but this is me on record now all of you all my family members are as fireable as anyone else and I like my coffee with sugar in it.Alex: I'm going to use that clip to promote this episode.Jodie: I love it.Alex: Fantastic. What an amazing note to leave on. Thank you so much for spending your time with us again, as amazing. And let's see if you can be the number one episode of 2020 as well. That'd be pretty cool. All right, thanks very much. Bye-bye.Jodie: See you later. Bye.Alex: And there we have it. There's my chat with Jody Stevenson. It is so good. catching up with her. And it sounds like businesses growing was great that she's kind of getting people involved now it's becoming a proper family business. So that is awesome. So she's got a lot of work to do to see if we can get her as the number one download episode of 2020. We'll see we've had a lot of amazing ones. some incredible ones coming up too as well. So don't forget our event, March 26. Only a few weeks away now I literally got a couple of tickets left. It'd be great to see you there. If you need any more information, go to the lead engineer, click on the conference tab, or details, their agendas all kind of finalize all speakers are on there. We've got loads going on. I will see you next time.

This month I've got tracks by Alex Do, Charlie Thorstenson, Stefan Rein, HDN, Erhalder and some classic vinyl from Pounding Grooves. Of course, there's much more so pump up the volume, cut the mid-range, drop the bass. EVENTS: Klein Berlijn 20th of April, 21:00 - 1:00 https://www.facebook.com/events/691016687982181/ Record Store Day 13th of April, 11:00 - 17:00 https://www.facebook.com/events/2278327482407941/ Son of 8-Bits social media: https://links.sonof8bits.com Send promos to: promo@sonof8bits.com For bookings: bookme@sonof8bits.com

This month I've got tracks by Alex Do, Charlie Thorstenson, Stefan Rein, HDN, Erhalder and some classic vinyl from Pounding Grooves. Of course, there's much more so pump up the volume, cut the mid-range, drop the bass. EVENTS: Klein Berlijn 20th of April, 21:00 - 1:00 https://www.facebook.com/events/691016687982181/ Record Store Day 13th of April, 11:00 - 17:00 https://www.facebook.com/events/2278327482407941/ Son of 8-Bits social media: https://links.sonof8bits.com Send promos to: promo@sonof8bits.com For bookings: bookme@sonof8bits.com

This month I've got tracks by Alex Do, Charlie Thorstenson, Stefan Rein, HDN, Erhalder and some classic vinyl from Pounding Grooves. Of course, there's much more so pump up the volume, cut the mid-range, drop the bass. EVENTS: Klein Berlijn 20th of April, 21:00 - 1:00 https://www.facebook.com/events/691016687982181/ Record Store Day 13th of April, 11:00 - 17:00 https://www.facebook.com/events/2278327482407941/ Son of 8-Bits social media: https://links.sonof8bits.com Send promos to: promo@sonof8bits.com For bookings: bookme@sonof8bits.com

Live from her Berlin studio, Anja Schneider brings you this weeks Club Room radio show featuring music from Brame & Hamo , Marco Faraone, Eric Cloutier, Fjaak, Keith Carnel, Alex Do, Einzelkind & Christian Burkhard, NiCe7 and BMG & Derek Plaslaiko 01. Brame & Hamo - Hurt You 02. Marco Faraone - On My Way 03. Eric Cloutier - Hadal 04. Fjaak - Eether 05. Sad Girl - Oizys (Keith Carnal Mix) 06. Alex Do - Siskens 07. Brame & Hamo - Limewire 08. Einzelkind & Christian Burkhard - Seamless Pattern 09. Malandra - Take Off Your Shoes (NiCe7 Remix) 10. BMG & Derek Plaslaiko - Sonic Rendevouz

Selected a great bunch of fresh track for you this week. Expext the freshest cuts from the likes of Meeshoo, ALMA, Gabriel Lynch, Westseven, Luis Junior, Matador, Rafael Cerato, Marino Canal, Kellerkind, Super Flu, Rudy, Pete Oak, Alex Do, Yotto and Mark Alow.

NEWS [26:01] Case against two ‘drunk’ pilots arrested at Glasgow Airport collapses [31:20] Vietnam Airlines flight #VN7344 mistakenly landed on a non-operational runway [35:56] FAA Expands CFM56 Checks To Newer Blades [38:19] Wasaya DH8A at Thunder Bay on Apr 23rd 2018, knocking on cockpit's door [40:47] Runway Lights Baffled Pilots on Night of San Francisco Near-Miss [44:25] Nine Dead After An Air National Guard WC-130 Hercules Plane Crashes In Georgia [48:08] Southwest B737 near Cleveland on May 2nd 2018, cracked cabin window [51:32] Bombardier C Series Could Be Renamed Airbus A200 FEEDBACK [56:09] Southwest 1380 Feedback [1:49:39] Thomas - EA-18G: Flying blind and freezing [1:56:15] Ben - Promoting an Aviation Tour of North Korea [2:00:03] Chris - Employment Contracts [2:26:34] Liz - University of Michigan pilot’s aborted takeoff broke rules, but saved lives [2:37:09] Robert, Alex - Do you sightsee up front? [2:45:56] Texas Charlie - Why are Some Runways Hilly?? [2:51:02] Nick - Weight and Balance [2:54:03] Orson - The 717 [2:55:07] Col Jeff - St Maarten VIDEO Audible.com Trial Membership Offer - Get your free audio book today! Give me your review in iTunes! I'm "airlinepilotguy" on Facebook, and "airlinepilotguy" on Twitter. feedback@airlinepilotguy.com airlinepilotguy.com ATC audio from http://LiveATC.net Intro/outro Music, Coffee Fund theme music by Geoff Smith thegeoffsmith.com Dr. Steph's intro music by Nevil Bounds Capt Nick's intro music by Kevin from Norway (aka Kevski) Copyright © AirlinePilotGuy 2018, All Rights Reserved Airline Pilot Guy Show by Jeff Nielsen is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

In this episode, Yehuda Katz, co-founder of Tilde, OSS enthusiast, and world traveler, talks about what's in store for Ember. Yehuda Katz: @wycats | blog | GitHub Transcript: ALEX: Hey, everybody. Welcome to the Frontside Podcast, Episode 46. My name is Alex Ford, subbing in for our usual hosts, Brandon and Charles, today. We have an awesome episode. We have a really special treat for you. Co-creator of Ember, Yehuda Katz is joining us today. Hello, Yehuda. YEHUDA: Heyo! ALEX: We also have a first time Frontside podcaster, Chris Freeman. Chris, do you want to introduce yourself? CHRIS: Hey, everybody. ALEX: We've also got a podcast Frontside favorite, Robert DeLuca. ROBERT: Favorite? I don't know if you say that. Hey, everyone. How are you doing? ALEX: I'm really excited about our guest today. Yehuda was just in Austin a couple of days ago. He gave a great meet up talk and a deep dive into Ember and it looks like you're going on-tour with that talk, Yehuda. Is that what I saw from your website schedule? YEHUDA: Yeah, I'm not sure exactly. I change it up every time, largely because things happen. So if I say this thing is 'active' or 'in progress', and then it actually shifts, I have to change it up. I've been talking a little bit about what's up on what we were working on. ALEX: Do you want to give us a brief outline as to what's going on in that talk for those podcast listeners who might not be able to attend? What's going on with Ember? What's new? What is it that you're trying to get across here? YEHUDA: Sure. Actually, the talk I gave in Austin was, you're right, it was basically a deep dive. It was really focusing on a few targeted things that we're working on. I would say that at a high level, we're basically working on a couple of things. One of them is generally more integration with the ecosystem, things like ES6 modules, classes, components that look more like HTML and more graphic components and things like that, also improving EmberCLI so it's more integrated with other tools that people are using. A lot of that stuff has to do with the fact that Ember started a long time ago now, like five years ago or so. And so, I think we've actually done a pretty good job of keeping up with things. For example, we adopted ES6 modules and promises a while ago now, and I think generally speaking, we tend to keep up with the ecosystem. But because we've been around for so long, there are certain things like classes, where it took a while for that feature to catch up with the functionality that we were using in Ember. Decorators landed a little while ago as a stage 2 feature in TC39, and that lets us really take a bigger chunk of the functionality that we have in our class model. I make it work for everybody with class syntax and that's something we're pretty excited about. So that's one area just generally taking things where Ember had its own stuff and try to integrate a better ecosystem. Another big area is this mobile readiness and also, a lot of that has to do with the fact that things like service worker have just recently landed. For example, AppCache was a nice feature in some ways. Some people at Google will kill me for using the word 'nice' in AppCache in the same sentence. [Laughter] YEHUDA: But AppCache was trying to accomplish something for a long time. I think it did some version of what it was trying to do. But really, using AppCache is a default behavior for all users having - there's too many caveats to make it work well where service worker, because it's more of level one and more directly controllable is a better fit for something that we could ship with all Ember users. We basically want to use Ember and EmberCLI, you build an application, you get a good mobile experience out of the box. Some of that has to do with trimming down parts of Ember that we don't need to be using in simple applications. Some of it has to do with service workers, some of it has to do with things like Glimmer 2, just making the performance better. But generally, that's the other [inaudible] so it's basically mobile readiness on the one hand and just integrating better with the one ecosystem are both big picture things we're work on. ALEX: Something that you brought up in your talk where private Ember methods and how a lot of people use private methods and you have to keep them around, what you we're just talking about that was unifying around the conventions of programming in Ember. Whatever JavaScript people bring in to Ember, you want to try to incorporate that as the language moves forward which is, I think, a really interesting problem. Also, something you could talk about a little bit further is what you look for in the way people use Ember going forward and how you have to kind of bend the framework to allow it to be backwards compatible. I'm curious what that decision making is like. YEHUDA: What you're talking about and what I talked about yesterday is what we call 'intimate APIs' and that basically means APIs that we never intended to be public. But for some reason or the other, people got their hands on them and started using them. I gave a somewhat elaborate example of funky case yesterday. But basically, the way we approach generally dealing with compatibility is pretty similar to how the web itself does it. First off, there's a thing that we mark as a public API. We just don't break it unless we make a major version which is very rare. We have basically one of those the entire Ember, and I don't think there's anyone coming in the near future. One option is if we don't like something, we just break it. That's very uncommon. Another option, and this is way more common, is that we try to build -- it's for public APIs -- we try to build a new API and we try to nudge people away from the old one. One approach for nudging that is probably the most common is deprecation. So, deprecations themselves don't violate semantic versioning because we're allowed to say, "Please don't use this anymore." The one area that's annoying about deprecations is that if backup code that powers the old feature has to still stick around. And so something that we've been working on around that aspect, around deprecations is something we called svelte build, which is basically the idea that we'll mark every deprecation with the version, that it will start to be deprecated in and people can ask for, "Please don't include any code that was deprecated out of 2.4, or 2.5, or 2.6, or whatever." Then, we'll automatically slip it away. You could think of it sort of like as a reverse feature flag. CHRIS: Wow, that's actually super interesting. I didn't know that. YEHUDA: We haven't finished it up yet but the RFC that talked about it and actually some old guy who actually wrote the RFC along with 1.13 when I noticed that 2.0 was going to end up being a pretty painful release for a lot of users. We did a lot of things around 2.0 to make things less painful, like we made sure that 1.13 contained all of the deprecations that you could possibly need, as well as all the new features. So if you went to 1.13, you could look at all the deprecation warnings, switch to the new functionality. As long as you have no deprecations left, 2.0 was just the exact same code without any of the deprecated features. But as we're working on that, I realized that there is no real reason to give people such a heartbreak, if we could instead just slip away the code. So that's one approach and I think, more or less deprecations, and then eventually, svelte builds are the normal path. With regard to intimate APIs, those are cases where people came to rely on very specific timing or very specific API, very specific details in some internal API and for those things, if we know that a lot of people use them -- usually they get used to like a couple of add-ons. Maybe Ember Wormhole, which is really popular, we'll use it. Then it's really hard for us to remove those things. Those APIs are harder to maintain compatibility for because the exact details of what they even did was never really well-defined in the first place because they were never documented. So usually what we'll do is we'll look at the usage of the API. We'll come up with a new API that is satisfying the exact same use case, and then we'll deprecate the old API. The policy these days is that you have to go through an LTS release so we'll make sure it's deprecated. Let's say, you want to deprecate something now, make sure it's deprecated in 2.8. And you'll know that if you were actually doing the whole song and dance that deprecate what is intrinsically a private API, so it would be within our rights to say like, "Sorry guys. You used the private API. We're not going to help you." But we really think it's important that for Ember, if something feels like a breaking change, that we're not doing it willy-nilly. If somebody upgrades to 2.9 and all of the sudden, Wormhole stops working, they're not going to understand that the reason that happened was because Wormhole did a bad thing. We basically need to do a clear pass. So we'll do a deprecation in LTS release, then we'll wait a couple of releases before removing it. Then usually what happens is, in the meantime, we'll go ahead and we'll submit pull request for the big add-ons that we're responsible for, and we'll also try to talk and write down why it happened. Historically, we've done that a few times and it's worked okay. There was an example of this, which is the lookup factory API in Ember which is really a boring API but it's used by a bunch of high profile add-ons. So the reasons why we needed to deprecate it were silly. They were just a bunch of bad behavior in the old thing that was making everything super slow. We can make things faster by giving people exactly the same functionality without exactly but identical guarantees. So there were some 'guarantees' which don't even make sense for private API. But there were some things that in theory, the API did that we didn't want to support because of performance reasons. And so, we gave people a new API that is, for all intents and purposes, identical. All users will be able to use it in identical way. But it doesn't have exactly the same weirdness and that weirdness was pretty expensive. ALEX: So you've trained Ember developers to be on the 6-week release cycle? They're looking at the blog posts. They're looking to upgrade but you've been involved in a lot of open source projects where I'm sure that wasn't really the case. Say, jQuery has a huge API and obviously, some things have to be deprecated on that and you were on the jQuery core team, I should mention. YEHUDA: Rails has the same story whereas API releases every year, more or less. ALEX: So, I'm just curious. The fact that you have Ember developers, I would like to think bingeing on your word and hinging on those updates, how would you go about, say, the Rails API? Or the jQuery API? Maybe, now you're involved with Rust, and maybe the plan is to have Rust on a 6-week release cycle. I'm curious, if you don't have your developer's attention, as you do the Ember developers, how do you deprecate an API like that? YEHUDA: That's a good question. How do you deal with deprecations if you're releasing quickly? I think there's a couple of important points to make here. First of all, Rust is on the 6-week release cycle. Sometimes, as the same kind of story with intimate APIs, it's much less common with a strong-type system like Rust. I guess, important things to point out, first of all, deprecations don't intrinsically break things. When we talk about intimate APIs and deprecations happening pretty quickly, those are APIs that are large, if someone is not paying super attention to Ember, they're probably not using those APIs, like they would not have known to use them in the first place. They might be using an add-on that use those APIs and the intimate API deprecation process causes the add-ons to update relatively quickly. In terms of regular deprecations, those deprecations stick around forever so you could come back a year later. For the most part, you could make an app that was 2.2 and upgrade it to 2.9 as long as you upgrade the add-ons that you are using at the same time and everything will work. We also realized that some people can't upgrade every six weeks and that LTS release process which is basically a six-month process, more or less. It basically gives us a communications channel to people who want to pay less attention. The way that that works is that, every four release cycles, so that six times four is 24 weeks -- about half a year. Every 24 weeks, there's another release. We assume people are on that release channel. Some people operate at 2.4, 2.5, 2.6, 2.7, 2.8. Some people go directly from 2.4 to 2.8. For those users, we [inaudible] ecosystem, please make sure you support the last LTS release, which means that if your user's on 2.4, and 2.8 comes around, you know that you could have stuck to 2.4 and generally got add-on support and when 2.8 comes around, you should probably upgrade. Also, with intimate APIs, we make sure we always deprecation them one LTS release before we move into an LTS release. Now, what that means is that if we want to remove something by the 2.8 LTS, we have to have already deprecated it in 2.4. If we want to remove something by 2.12, we have to remove it at 2.8. So six months is still not quite the one-year Rails release cycle but it's starting to get to a reasonable state. Also, I would point out that the LTS releases, the support policy for them is that they're four cycles long. We do bug fix support for six cycles and security releases for 10. What that means is that we're actually supporting LTS releases. We were supporting two at a time for security patches -- two and half basically -- and we're supporting one and half at a time for critical bug fixes. The one and a half basically means that when 2.8 comes out, you have two release cycles which is basically three months to upgrade. If you're on 2.4, and 2.8 comes out, it's not like, "Oh, my God. Panic! I got to upgrade right now." You can take a few months to upgrade. Basically, 2.4 came out, you got all the deprecations you need to care about. You had six months to deal with deprecations and then another three months after that. Even in terms of intimate APIs, where in principle, like Rails and jQuery don't even care about those things for the most part -- ah, jQuery cares about it even more. But most projects will get private APIs and say, "Sorry you used the private API. Why did you do that?" Ember is a rare project in that we actually deprecate things that we know where we actually use them. We have a process for dealing with them. Even that process, like I said, it's not a six-week process. We don't deprecate something and remove it. We deprecate something and then give it a pretty long horizon before removing it. ROBERT: I'm curious. You brought up that you are the common element between jQuery, Rails, and Rust. I know that there are, at least, between Rust and Ember and from Rails to Ember, there have been a lot of commonalities and lessons learned in how the projects themselves are managed. But I'm also curious with Rails, Ember is clearly pretty heavily influenced by Rails, which you were doing before. You've been working on Rust quite a bit and I'm curious, does your usage of Rust, even though it's a very low-level language, does that influence Ember at all? Does that change how you think about the framework or JavaScript in general? YEHUDA: The number one thing that I got out of all those projects that I think used to be a thing is something like a conventional reconfiguration idea which is really not - I think the mentioned of reconfiguration is probably not even the best description of what it is. I think the idea that communities that are all working together on the same thing to build that thing bigger and better and better and better and build ecosystems around that thing, those communities are able to build much higher than communities that ask every single developer to put together a bunch of pieces themselves for profit. That's the basic idea. If you look at Rust, which is conceptually very low-level, you'll find that there are things like Cargo, which is a tool that not only builds your thing and not always package manager but it has a convention -- not only a convention -- it has a built-in support for documentation. So you're on Cargo docs, you get all your documentation for all your dependencies. You run Cargo bench. That's a built-in thing that runs your benchmark. You run Cargo test that runs your test. To mark your documentation as being Rust code, it will automatically run your tests for you when you run Cargo test. We will build your examples for you and make sure your samples keep compiling. There's all this stuff in Cargo that you would not necessarily consider, like it's basic [inaudible] helping you get your workflow the same. Then there's things like Rust format which you've been working on and there's been a huge debate in the community about exactly how much configuration we want to allow in Rust format. But the irony of it is something that most people agree with is that we should try to come up with some kind of default style for Rust that everyone agrees to, that most people can pick up and use the Rust products where it's often used. Then there's things like Futures and [inaudible], where the goal of those libraries is really to make there be a single central way that everybody does [inaudible] in Rust. These are all things that if you look at like C or C++, which are languages that are sort of in the same low-level in this space, in the same kind of area, you'll find that those languages have billions of ways in doing all of those things and there's so many different styles and so many different workflow tools, so many different things that you can make in then a million things that [inaudible]. Even the Rust is conceptually low-level, it doesn't really affecting every single environment as some sort of things that everyone doesn't need to do themselves. I think, an important thing that people don't always get about convention configuration is that it's not just that everybody doesn't have to do all of those things and it saves you some time, it's that when everyone is doing the same thing, it's a lot easier to build another level on top of that. For example, a fast food is a great example of this in Ember. The fact that everyone initializes their application using an Ember initializer, the fact that services were these global things that are sort of global- there's no better word than 'services' but global services, the different components could share the fact that those are all going in the same place. The fact that the way we manipulate DOM is always in a constraint single area. Almost things mean that when it comes out and to build something like fast food, it's pretty easy to take almost any Ember application and make it run in the fast food environment because we know what we're looking at, and that's something that isn't necessarily true about other tools. For me, Chris, the number one thing that, I think, all of those sharing, including jQuery, actually, like jQuery said, "There's so many different ways that people do DOM manipulation, why don't we unify it into one thing that I everyone can use?" You know, the 'jQuery plugin', which is something that has falling out of favor over time. The reason it was so popular was largely because people knew, "Okay, I'm dealing with jQuery object. If I just put a plug into the jQuery object, it makes sense." People understand how to use it. I think that's something that a lot of projects that I used to share and it's also something that is not close to ubiquitous. It's very uncommon, actually. So that's one thing -- the conventional configuration story. I think, another major aspect of all this, and this is something that jQuery and Rails do not share, but Rust and Ember have the RFC process, which more or less, is just a wave as a community of saying, "The way that we agree to add new features to the project is not something coming down the [inaudible] with a tablet every year." At a conferencing, we have agreed to add these features but sometimes people are core team, but sometimes they're not. Sometimes, they're actual contributors, coming with an idea, write their view down in a format that we all know how to do with. Then there's a community discussion about it. Sometimes it takes a very long time. Sometimes it's not. But then we eventually come to a conclusion about what it is that we're doing. Eventually, the core team agrees to merge the RFC. I think one of the nicest things about RFC process is that it produces an artifact that you can come back to a year, two years, three years later. If you say, "Oh, I wonder why they've made that decision. I wonder why that's the thing that they did," and the reason why this is great is that the RFCs are not gospel. They're not something that we should hold onto forever. But at the same time, we don't want to reel it again, things that we already discussed that in-depth over and over and over again. If a person comes back and they say, "Oh, why do they do that? The modification of RFC, why are these instructions directors are like that?" If they go back and look at the RFC and the thread associated with it, and the thing that they want to bring up is something that was already discussed, it's really no reason to bring it up again. But maybe someone have thought of a different idea or a different reason to dislike or to disagree with the decision that was already made. That was already discussed. That's a much better rationale for bringing up for re-litigate. In other words, re-litigating is actually good but if you re-litigating five times a day, on every decision, that's not why you move. So RFCs, by their very nature, the fact that the core team is doing things in public like anybody else and everybody else is also participating in that same process, the fact that artifact tells you, more or less, exactly what was discussed, makes it really easy to decide when is a good time to revisit some of the questions. ALEX: Do you find that poll request has the same process as an RFC and it's an artifact you can go back to, it's a place to have communication that is visible to everybody, unlike say, this micro message service such as Slack where context is just lost for the public. I'm curious if you want to see that modeled in poll requests or if an RFC is where something like that belongs. YEHUDA: I think, poll requests are great. I remember that when I was somewhat like the first user on GitHub who's not a founder of GitHub. I remember one of the things that excited me about GitHub early, although, the very beginning, didn't have poll request yet. but one thing that excite me about poll request is that before poll request, every single time I would use an issue tracker so they were like a billion issue trackers like [inaudible] whatever, and at that time I called it 'patch management'. I want something that helps me manage patches because the actual discussions are not the higher of it. The higher of it is something that submitted a request for me to merge in this patch. How do I merge it? How do I discuss with them? Those things were always really hard so I might ask people to upload patch files or whatever. It's hard to remember how bad things were but the number one thing that was just so obvious but also so terrible about the ecosystem before GitHub was patches were like old mailbox approach. Like you'll make a patch, and hopefully, get it to the right place at the right time. So I think, poll request and comments of poll request and many of the improvements that have been made for poll request are great. The reason, I think, RFC are really important in addition to poll request is that, by the time someone actually took the time to write some code and submit it, it's very easy to look at it and say, "Well, I don't necessary agree on all the things here but I don't want to give a person a hard time that will do the work," whereas somebody submit some idea early on and they say, "I have this idea --" It's actually a lot easier to sort of get into details at that point and say, "Don't do this. If we should do this or it doesn't fit that well with this other RFC or this other poll request that's already open --" But once somebody actually does start and actively working on the feature, I think, poll request are great, like most open source project these days. Ember doesn't ever committed anything to master. Everything goes to poll request, and even core team stuff. I also find that when I submitted a poll request or anybody in the core team, there are almost always people who are not in the core team that saves or fix in the poll request, for various reasons. Of course, poll request also are the usual mechanism by which people run things like CI and linting tools and things like that, called quality tools. I think, the poll request workflow is really good. In terms of other messaging services, I think, there just sometimes the need to have conversations that are faster than poll request and I don't really have any problem with check conversations. But I definitely agree that it has a deep conversation. This is something that happened in the [inaudible] a lot where we having this conversation with the core team and somebody will say like, "We should really move this out into a public discussion, or move it into RFC. If you don't agree with this thing that somebody said public, can you say [inaudible]." So I totally agree that if there's a thing that people want to say in private about something but it's just in private for convenience, it's not private or transient for any good reason, actually getting out there onto the issue or the poll request and say your opinion and letting the conversation back and forth happen there is, for the exact same reason as you said, very useful. In fact, Aaron Turon from Rust brings this point out repeatedly. We just had a conversation this past week about the fact that we have sort of a normal Rust project that, let say in the core team room and it's a technical topic, and it doesn't have anything sensitive about it, people always say like, "Hey, can you move that into Rust Internals," which is a public room. Or like moving this course, we have internals at Rust-Lang.org and I keep thinking Ember could use it. Basically, this sort of a hierarchy of private to public or transient to sort of a free-form discussion forum like this course to something like a GitHub issue, something like an RFC to something like poll request. There's like a hierarchy of how much of those artifacts are easy to search and find. But I think, you're totally right that there's no reason why, things like the core team needs to exist because at some point, the buck has to stop somewhere. Somebody has to make decisions. Somebody has to actually responsible for laying out the cross-cutting vision for the entire project. But those things are actually pretty lightweight. The core team when it's doing its job, it's just sort of making an omnibus of everything that the community is thinking at a particular point and making it more concrete. While, I think that's important that there are spaces which are core team spaces, or spaces that are transient, I think, a lot of questions that people have in the Ember slots are important that people who can just jump in and ask them. I think, getting things out into both public and more of permanent artifacts spaces is good. ALEX: Rob, you are a co-runner of Ember ATX and I was hoping you could speak on the fact that we've gotten some core team members down to Texas to come talk. It's nice that they're able to share their message with what's going on in the core team. But also, they're doing work. They're seeing how real people use Ember and then taking that back to the core team. I was wondering if have just want to comment on that and your work on bringing some really excellent people who make decisions down to Austin. ROBERT: As a meet up runner, like a co-runner, I guess. It's me, Jeff, and Lydia that run Austin Ember ATX. We really like to try and bring people that are deep into Embers core into Austin to talk about the framework that these people work in daily. It's always awesome because whenever you get them there in the flesh, you can ask questions. I guess, we can go back to where Slack is, like you have the higher bandwidth communication but it's even higher bandwidth when you're in person. Getting those people to talk to people that are actually working on the framework daily is I think, hugely important and that's why we work really hard to try and bring out people that work on the core. YEHUDA: For what it's worth, I think that Rails and Ember shares a common core value, like other projects have, more or less. Ember core team people almost exclusively actually work on Ember apps as part of their jobs so I work on skylight. Having some responsibility in the real world for apps that you are working. It's a big difference in just [inaudible]. I definitely noticed a few. Sometimes, I'll be working on a project for a while, like when I was working on Rails for 18 months and never actually used Rails. I mean, I used it but not for anything significant during that time. I, sometimes, get into a rut where I'm working on Ember a lot and I haven't had a chance to work on an app at all. Then, you go back to work on that for a day and it's like, "Oh, my God. There are so many obvious things that I can make better here." Like the kind of things that you would think about when you're working on your framework stuff is not necessarily- as quick it gets, the quickest things that you can fix. The Ember welcome page is a good example of this. I think, when someone is training, it's very easy for them to notice that it would be great if there was some kind of welcome screen for people. But it's not something that a framework author would necessarily think of on your own. Similarly, getting down to places that are not my usual haunts and hearing people bringing stuff that I just hadn't heard before. Like things, "Oh, that's a good idea. But I haven't heard that." A lot of that just come from the fact that the core team has a lot of different kinds of users in it so the people doing training, there are people doing apps or people doing consulting, there are people doing rescue projects in that kind of combos is pretty good. There's a long tale of all kinds of stuff, like people using web sockets for network people using React. People are trying to do Redux in Ember, who knows? That long tale is impossible to represent all that long tale. In a core team, we try to get as much as possible. It's impossible to represent all of them so going out there and talking to people doing weird stuff and weird doesn't meant pejoratively, just unusual stuff. Like Ember, really wants to be pretty flexible under the hood. Even though, it's a pretty conventional tool, we want it to be flexible under the hood so I kind of no way of flexibility is but sometimes, I'll talk to somebody and I'll be like, "Oh, in retrospect, that particular thing, I thought that was flexible as missing as little knob that we can add." So I really enjoy it. CHRIS: Since you've been pretty heads down on Glimmer 2 and you are actually traveling out and talking to people, I'm curious, are you noticing any common themes from the feedback that you're getting recently in terms of what users are saying? Do you have an indication of what the next move might be? Or what people are asking for? YEHUDA: For Glimmer specifically? CHRIS: For Ember in general, or Glimmer specifically. But I imagine, you're probably getting general Ember feedback. YEHUDA: Yeah. I talk about this a little before like the two big areas of interest are mobile readiness and better integration with the ecosystem. Integration is the wrong word. There's nothing wrong with Ember to that extent but people want classes. I think, those are the biggest picture things. I actually noticed a couple, somewhat interesting things when working with Ember. We ship the Glimmer Beta six weeks ago and we're doing another beta just because there's a couple of bugs that we got that were trickling and we want to make sure we get it right. I've actually noticed the people have on the one hand, the story of Glimmer is that we're pretty similar to React in the sense that you should think of what we're doing as a top down, you render the whole time and that there are some nice [inaudible] that use Ember.set or the set API, then we are able to do what people should do with component update automatically for you. For [inaudible], then we know, "Oh, this whole area, doesn't need anything to be updated." If you think about it that way, if you think about it as how can we render [inaudible] around set, I think, you'll notice that Glimmer updates are always faster than React's updates. But people have come to really rely on the sort of quasi-guarantee that if you didn't update something, it doesn't change the DOM associated with it, or even execute code associate with it. I find it sort of interesting. This is like meta problem, which is React actually got some things right about how to make this story performance. Part of that has to do with not assuming that you need as much bookkeeping as Ember always assume that you need. In exchange, you get much faster initial render and you have to do more work around updates. We actually have a pretty good story here. Ember.set is pretty nice because it lets us use API that our users are used to, say, generate [inaudible] upon updates for you and that's nice. But people get very upset when things run that they didn't expect, which of course, is not how React people think about it. The way React people thinking about it is, of course, [inaudible]. That's the whole API. It runs until you told not to. In Ember, things run at people who don't expect to get very angry. I think, you have to be one that I'm thinking about and that's a lower [inaudible]. But in terms of low-level, like thinking about how to shift the mental model of an Ember user so that we can get away with less and less bookkeeping upfront. I still do too much bookkeeping as part of initial render but in order to keep reducing the amount of bookkeeping, we need people to get into mindset of things are fast initially and the tradeoff is that your updates are slower, unless you do whatever. There are mighty things like React does this wasted time debugging tool or they basically tell you, "Hey, you didn't tell us not to render this but it never render," so you should try and do that. To be honest, I think, having to write something once your component updates, that exactly, "Do I [inaudible] is not okay. I'm not willing to do that." But there are a lot of things that approximate that were more similar to Ember existing APIs that we can find. I guess, my medium-term goal here is to make it so that we have the sweet spot so that the initial render is always very efficient. I think, we're getting closer. There's still some back problems that we can deal with so. Initial render is very efficient, fast components are fast, and more or less, you get good updates performance until you reach a certain amount of scale and then the escape valves are much nicer [inaudible] before an update. They're basically little [inaudible] where you say, "You know this thing can't change." It would be hard for me to explain. It would feel like it's [inaudible] we talk about. We've had a bunch of discussion about different escape valves, and the thing I'm most interested in is finding once that feels semantic. Should there a component update doesn't feel like you're describing anything other than React's API. I'm more interested in things that feel like you're talking about your app or your data. ALEX: Yeah. ROBERT: Keeping with the Glimmer 2 topic. Glimmer 2 is written in TypeScript, right? YEHUDA: Yep. ROBERT: Do you see that creeping its way more into the Ember community? I guess, I kind of want to get your general thoughts on TypeScript and what your experience was writing in Glimmer 2. YEHUDA: I actually really like that. But the story with TypeScript was that I was writing the Glimmer 2 originally in regular JavaScript and I came back from a long trip. I want to show Godfrey what I've done and I was having trouble explaining some of the interfaces. I happen to know that TypeScript is a lot of it is just interface so I'll just use their syntax and I think, I open the playground and I type in some TypeScript interfaces. Then I was like, "Oh, it's annoying that if I reload, I'll lose it so let me copy the interface into the ReadMe, basically and to the app." Then over time, like not very much time, I was like, "Oh, it's very annoying that now that I have this, I really wish I could just use it inside of the code." So we started doing that. It took us maybe a week of actually being to be able to use TypeScript for real. But honestly, the code base is pretty big at that point, and the actual was not so bad. A lot of the reason why it was at the time, TypeScripts like VS Code, TypeScript was still younger and it wasn't a slam dunk. For example, in today's TypeScript, you can just have JavaScript files in your directory and just tell it to [inaudible] that works. At that time, you couldn't so you have to really change all the files and there are some things like TypeScript requires you to specify in classes. It requires you to specify all your fields and I think that's fine, that's good for TypeScript. But you're not going to have already done that in JavaScript so you can't just like rename all your JS files with TS and have a nice day. So it took as a little over a week, I think, and we also have to write the Broccoli TypeScript thing during that same period of time. That was another thing we have to do. ROBERT: Yeah, that's a [inaudible]. YEHUDA: Then, with TypeScript change the compiler API a few times so we have a bunch of [inaudible] to do. But other than that initial like [inaudible] to get it working, I would say that it was every single point in time, there was always a [inaudible] win, in terms of what we had to do to make TypeScript happy and what wounds that we got out of it. You get things like, obviously, people know about code completion. I personally like code completion. I think, it's helpful. But I think, jumps to definition is actually more important feature than code completion. Just like what is this method? I want to look at it. You can jump directly to it. Also, for me, the code completion of parameters is way important the code completion of method names so when someone teaches you about code completion, they will usually show you, "Oh, look [inaudible]." It gives you the list of all method names, and you're like, "Well, that's fine. But I probably know all of those method names." But you don't necessarily know all the parameters. Especially, once you start using types, the parameter or information is actually quite rich, like it's telling you this is a component definition, this is a string or this is whatever. All that stuff, I think, I basically come to realize from using TypeScript that Microsoft has done a really good job with [inaudible] code of distilling down to just what part of ID experience is really good and just bring you that to an editor, that feels a lot like Atom or Sublime, or other than that. So if you get like a pretty good ID experience, without all of [inaudible]. ALEX: I've seen some talk on GitHub about people who want to write their Ember add-ons on TypeScript and I did not know Glimmer 2 was written in TypeScript until just now. I'm glad that was brought up. But we as Ember developers have been trained to use convention over configuration. The convention is Ember is not written in TypeScript. We're starting to see convention now where logic has crept into the template, or it's not as much as convention as people are doing it right now. I'm curious what your thoughts on that and more is treating Handlebars as a programming language and something that we're seeing now in real production Ember code, so what is the path going forward there because it is happening? YEHUDA: Yeah, I agree. I just want to say, I didn't actually answer the previous question in full. I think my expectation is we have no interest in ever making TypeScript as rudimentary part of Ember. I think Ember should always work and work nicely with regular JavaScript. I don't want to do anything that would lean to heavily on people having TypeScript around. Certainly, I don't want to do with Angular did, which they use the types as semantic markers for dependency injection and something like that. But I do anticipate things like Ember-metal for sure, Ember runtime being written in TypeScript because anything that's pretty low-level and a lot of algorithms benefits a lot from clearly delineating interfaces. I think, another thing people don't realize is that there are all these [inaudible] interfaces floating around your code in JavaScript. But like you are in a class, it's pretty easy to document what the class does. But if you have an interface, it's not really any good mechanism for describing it and it can become very [inaudible] and it's Like, "Please give me an object as these methods on it and build these methods." It's funny because you don't realize until you start using TypeScript that it's a very recursive problem. It's like, it has these three methods on it have these six parameters and these parameters have these interfaces and those have these. So you can actually start describing a very complicated thing and it's like those complicated things didn't exist before, they were just very implicit. The explicitness of the interfaces is not you can write [inaudible]. You can write the three interfaces and have the methods with all types of networks [inaudible]. I think, I expect Ember-metal, Ember runtime, other low-level parts Ember, certainly the component library now it's like directly linking in with Glimmer and Glimmer were written in TypeScript so that stuff would really benefit with TypeScript. In terms of Ember itself, using TypeScript, I think we have sort of a medium term goal of letting Ember apps use TypeScript if they want. I would say that making that story really nice, pretty much leans on ES6 modules and ES6 classes so we have some of the ES6 modules but there's still a lot of Ember [inaudible] whenever module story. In terms of classes, were still using the old-style class system and that class system is actually just really hard to get the types working in TypeScript. It's hard, period. But like React has a similar problem and there's lot of advance features that only really exists in [inaudible] express ES5 class [inaudible] and TypeScript doesn't have all the features. My expectation is that sort of along the same path as getting ES6 classes. We will also get a lot of TypeScript support in Ember and I think a lot of people are interested. A lot of people have work on Glimmer now and they're like, "I would love to use it in my app so we'll probably have that happen." Coding your templates, was the other question. I sort of have a mixed feeling about this because on the one hand, I actually do want Glimmer to be the programming language in production way. So either templating engines are just using the programming language embedded like the ERP. Or they are like Mustache or like the general templating engine -- forget what that thing is called -- but there's a bunch of template engines that use like the curly syntax and those things aren't very rigorous in terms of how they think about scope. Like lexical scope, it turns out to be a pretty important thing about how programming language work. If you have a shitty scope story, people don't have a good sense of what's going on so like the Angular 1 templating story was you basically find your scope on wherever and you attach to a part of your template and that basically means that if you're looking at just temple, you have no idea what the actual variables mean, anyway, because any part of it could be choking up the scope to be whatever. I start with Handlebars but have refined a lot overtime and I'm pretty happy with it now. The Glimmer templating engine is basically defines a programming language. It has scoping story. If you want a variable, name it. Use the as-pipes syntax and you get some variables there. Your function, your output, your components, and your helpers are functions and sometimes it's written in JavaScript, just like in Ruby cellular functions that are written in C. But ultimately, just like a C extension, it can't magically change the scope of Ruby program, helper or component in Glimmer. It can't magically change the scope of your template. With all that needs, if you look at a Glimmer template, it's actually really clear what are the names mean. That sound boring but ultimately, that's one of the things that needs to you look up at a lot templating engine and not only really know what's going on. I don't understand what's going on, without thinking of what every single one of those custom helpers is doing. I think Jinja is the name of the templating engine in Django. If you look at some of the templating engine like that or even like Handlebars before Ember 2.0, you really have to go that like 'for x and y' is a magic syntax that needs a particular thing. Because a lot of these templating engines are very flexible in the sense that they let users have or whatever, any particular piece of syntax could actually be creating random names that mean whatever. I've just found, having worked through that in the Ember community, I'm very happy that we took the time to get that stuff solid. One of the nice side effects of that is that it makes some of the usual optimizations that people do on code work very nicely. Once we know all the names mean and know all the scopes mean, things like in lining specialization from invocation. This component is invoked here. It has these parameters, but those parameters are all strings and I can see the receiving end. The receiving end just fix those strings into attributes or something. At compilation time, like to combine all into one thing. This is an optimization that we haven't done yet because we been working on compatibility. But there's a lot of normal 'programming languages standard optimizations' that we can do because we design Glimmer to be a programming language. The fact that we've done that is actually mean the root cause of people doing more programming language stuff in their templates, in older versions of Ember before, we had done such a good job of rationalizing everything. You would start doing that stuff and you would start hitting clips where the behavior didn't work the way expected for some reason, then you just use a sub-expression as something and then depending on exactly which things you put into the slots, maybe it didn't update on the inside of the template. We always consider those things as bugs so we would fix the bugs that we encountered. There's an explosion of different kinds of things in a programming language and if you don't model variables as variables basically, then it's hard to know callbacks are callbacks, variables as variables. There's a lot of doubt so they would start using the APIs as part of them [inaudible] hit someone and they would pull back. But today, the implementation of Glimmer, especially with Glimmer 2 is extremely [inaudible] standard, and what that means is that you want to do very [inaudible], parenthesized expressions with as type something and then you want to go and take that and send to the component and you have that and you put that value and put it to a service and you do all that and it works. That doesn't necessarily mean that it's a good idea for your template to be in a large program. That's generally that. I think that's main question that you asked me and it is generally, for things to get really complicated. But I think there is a reason for it and I think it's something we're doing to make it better. I think, the reason for it is that, if you think about the Glimmer core language, the main escape of what you have to get complicated expressions out of Glimmer and back into a reasonable place is helpers. Let's say you have a big bunch of [inaudible], and/or whatever people are doing inside of their Glimmer templates and it's like a multi-line thing and you want to pull that out to a more reasonable place. The natural way to do that is to make a helper. But it's also pretty common that you have a complicated piece of expression that isn't reusable. It's not being reusable for multiple places and helpers in Ember right now are global so you may have this big block. Another [inaudible] of computer's property, but computer property's don't have a nice- like I have a few internal parameters and I just do something that they always require you do something against it, the components off of this, and that is usually what's you are doing. You're usually have what is effectively a function with a bunch of parameters in it and those parameters combine some way like with 'and', 'or', maybe there's some comparisons like 'greater' or 'less than' or whatever. One of the things that comes out of module modification RFC and makes everyone pretty excited is the ability to have helpers in your templates that are local so it's a helper that is just sitting right next to your template. I think, those kind of things -- helpers that are right next to your template -- will give people who like you do not want to see so much code in your template, a much nicer story to explain to people why we're doing it, and what we should do instead. A template has a three-line, fifteen is privacy expression and you want to convince the person not to do it. The re-factor is literally just to make a local helper, put the code in there and use the local helper. I think that's the better story to explain to people than, "Hey, I don't like that. It feels bad. What should I do?" CHRIS: This brings up an interesting point that we actually encountered recently at The Frontside, we use helpers a lot and are frequently trying to get them to do all sorts of weird things. But recently, it occurred to us that one kind of blocker was that you can't compose helpers. We had an existing helper and we kind of needed to make a helper on top of it and it suddenly dawned on all of us that, "Oh, we can't go up a level." We can't build a helper and its abstraction over another one because you kind of have to hit the dump. You have to have a component or a template or something to invoke that. Is that's true? YEHUDA: I would expect that you could call the function with the arguments that looked ugly but I would suspect and I would say that you can call it and just pass the parameters and hash these [inaudible] and -- ALEX: Like a helper that invoke or something? Because to write a new helper, you would have to go back to JavaScript. YEHUDA: That array an object. I expect that to work. Do you just need a helper calling another helper? ALEX: Well, a helper composing, like composing several helpers into a bigger helper and then just calling in the template, much like how you might write some functions and that write a function that closes over them or something. YEHUDA: Are we talking about a helper that takes the helper? ALEX: I guess it could be. I guess, higher order helpers could be a thing in this case. YEHUDA: Helpers that call helpers are helpers that close over helpers really should just- helpers are more or less functions. It would just be able to use them directly. I think, what you're saying is an interesting Ember phenomenon. I actually don't know which of two categories this discussion is in. Basically, either. Either there is some good reason why this turns out to be difficult and there's like a missing API that usually fix it. Like in general, my mental model here is you're talking about a function so if you can just [inaudible] the function, it really should work and in that, it is hard. There's something weird. Basically, what I'm saying is either there are some 'gotcha' that how it was structured right now, that's like an accident. That means they're not exactly as much like functions as we think or the mental model that you have using them doesn't make you think of them like functions. So you think that there are hard to compose but actually there are functions. Basically, those two things are equally likely Ember. I think that's unfortunate. ALEX: I think that with them, you can certainly combine them in a template and you could even pass one into the other. What we ran into an issue was, similar to functions, if you are writing like an npm library, you may write five functions and only export one of them. That one function will compose the other four and call them. In some cases, you may not realize, do you want to export that composed abstracted function until much later and it's okay, because you just import the function from somewhere else, then you say like, "All right. I'm just going to consume this function from another and now I have this combination put together." Well, with a helper, if you already have a helper that does something and then you realized, "Oh, actually, I need to build an abstraction on top of this helper in a new helper," we so far have not found a good way to combine them like that. YEHUDA: So probably, it will not succeed and having this conversation through to the completion year. I'll just say for listeners, what I find surprising about this, although, I can believe that there is something that makes it true is that helpers in Ember are really just functions and increasingly they really are like helpers in Glimmer are functions. They have a weird arguments signature. They take positional parenthesis in array and named arguments as dictionary and that's a convenience basically because otherwise, you have to scrape of the last parameter and try to figure stuff out. So that's a signature issue. But generally speaking, helpers are supposed to be functions and if there's something that you could do with regular functions you can't do them with helpers, that sounds to me like something is wrong. Like I said, I can definitely believe I should talk to Chris about this and he should write a blog post about it. I can definitely believe that there is something that makes it true but it's hard for me to imagine what it is. CHRIS: Well, I'm glad to talk to you about it offline. YEHUDA: Yes. We will figured it out. ALEX: Yehuda, thank you for this deep dive into open source process into Ember. I could drill deeper into your brain and just extract as much knowledge as I can. I hope to be able to do that someday soon. We're going to wrap up for today. Thank you very much for Yehuda Katz and your time. YEHUDA: Yeah. Thank you. I apologize for people who didn't understand half the things I said. ALEX: Yeah, it's a podcast for everybody. But we have a lot of Ember developer's listening and I'm sure that they loved it and hated it all up so thank you very much.

On this show, Chef Alex will be doing his 23rd live Question and Answer show. This is going to be our last Question and Answer show before our awesome 24th question and answer celebration episode this Saturday!!!!!!  Do you have a cooking or baking question you'd like to ask chef Alex? Do you have a restaurant experience you'd like to share with Chef Alex? Do you want to know what to bake for Christmas? Do you have any Christmas questions? Well then this show is for you. Call in at 646-716-6458 dial 1 to ask those questions. I will also ask you the listeners 4 questions and you may call in to answer them! In the first hour of the show at 8 PM EST, Chef Alex is going to be accepting callers!!!! Call in to ask questions, and speak with chef Alex. Also in the 1rst hour, Chef Alex will be talking about various items. Alex will talk about how to make the best cookies for Christmas and a bit about the Creaming method, then Chef Alex will chat about the upcoming events for the weekend, then Alex will chat about his plans for the weekend, and then Alex will add some safety tips to the show! In the 2nd hour of the show at 9 PM EST, Alex will be taking callers. ALL CALLERS in the 2nd hour, will win a prize. The 2nd hour is being billed as caller interaction hour! Callers go ahead and call in to speak with Alex. Also in the 2nd hour, Chef Alex will make a MAJOR ANNOUNCEMENT for the q and a 24 live this Saturday, give out his daily tip, and more! MERRY CHRISTMAS 2013!!!! www.blogtalkradio.com/chefalexcardinale2013 www.gusandpauls.net