Podcast appearances and mentions of leon leon

说起来已经是上个月了，安妮薇看看主编 CLU 出差来到上海，JJ 和久违的「老网友」重聚了一回，饭后即兴录制了播客，重逢的兴奋让我们聊到停不下来，先放出上半部分~也是没想到在没有 Leon 在场的情况下开启了 Leon 最感兴趣的摄影的话题，包括怎么开始玩起摄影以及对摄影看法的一些演变，最后花了很长时间聊了聊免费图库 Unsplash，作为两位贡献者，我们自己也从中获得了很多成就感，留下了不少故事# 本期嘉宾CLU，正在构建极致地地图标记，产品设计师# 内容提要06:17 · 免不了要先怀旧一下老的摄影 app 们12:18 · CLU 的摄影爱好之路17:21 · JJ 也要分享一下心路历程24:59 · 在 Unsplash 上混久了，总有点儿故事49:58 · 为什么国内没有出现 Unsplash？# 参考链接# Camera+ 老版的部分 UI 非常有拟物风格 6:31iOS 上的专业向相机应用 Halide，算是 Camera+ 的精神延续 7:30Camera+ 的 UI 所用的 Bree 字体家族，来自 TypeTogether 7:45高强度使用 Camera+ 时 JJ 喜欢的滤镜风格都是这个样子的 8:16著名街头摄影师森山大道 15:04JJ 拍的吴哥窟女王宫照片 18:49被做上手机壳的 CLU 拍摄的照片 25:33做英国音乐人做成专辑封面的 CLU 的钢琴照片 27:26Unsplash 推出的 Unsplash Plus 付费照片订阅服务 29:28JJ 那张被当做「管道」的金门大桥照片 30:29CLU 的圣诞主题姜饼屋照片 31:34Unsplash 的 iOS 版本上线 App Store 时的截图 33:04CLU 的 Unsplash 页面，饱和度很低 35:09JJ 拍的富士山游客照 36:27JJ 在北海公园拍的老爷爷画画照片 36:37JJ 所有照片里访问量最高的那个墙面材质照片 37:13另一张高访问量的卷纸纹理照片 38:02CLU 拍摄的大兴机场照片 39:03出现在手机壳上的那张 CLU 拍摄的大楼照片 39:26去年的 Unsplash Awards 大奖获奖名单 42:10Unsplash Hire 是帮助联系摄影师和需求方的服务 47:40在 2021 年，Getty Images 收购了 Unsplash 48:36Unsplash 官方在 2019 年分享过每月开支明细，大概是 10 万刀 48:58JJ 在 Unsplash 上收集的亚洲人像合集 51:19国产图片处理软件泼辣修图 53:50

Justin and Peter discuss their final thoughts on HiFi Rush, Tchia, Resident Evil 4 Remake's excellent debut sales week, MultiVersus going offline, Ubisoft's new AI writing tool, Xbox killing its $1 Game Pass Ultimate deal, and more!Follow us on Twitter @HitboxPodJoin our Discord server!https://discord.gg/unmGxETX3USupport us on Patreon!https://www.patreon.com/hitboxpod@peterspittech and @JustinMatkovichMetacritic Roundup games:Have a Nice DeathMade possible by our wonderful Deluxe Podcast Patreon producers:Dave ParkerJ KnolThe intro and outro of Hitbox! is by ali_ontheguitar, check out their work right here:https://www.fiverr.com/aliontheguitar?source=gigpage

OSCAR D' LEON “EL LEON DE LA SALSA” DE VENEZUELA, CANTAUTOR, BAJISTA, ARREGLISTA, DIRECTOR MUSICAL, ACTOR. CHARLA CON GILDA MIRÓS EN SU PROGRAMA DE RADIO EN NUEVA YORK EN LOS 80s CONTIENE MÚSICA.

The start of a new mini-series, where co-host, Myla Yeomans, asks the question, ‘how can design help combat stigma?' In this first episode, we speak to Keisha Leon, Founder and Director at Leon Design. Keisha cut her teeth in magazine design before taking up a senior position at Lorna Jane. In 2018 she moved to Carbon Creative before deciding it was time to do her own thing. Being a Waanyi and Kalkadoon woman, Leon Design is a First Nations owned and operated creative consultancy, specialising in conceptual design. We get into the what, why and how in the interview. As always, a big thank you to Streamtime, our supporting partner, consistently giving back to the Australian design industry. Give them a try at www.streamtime.net ___ Links Leon: www.leondesign.co Keisha LinkedIn: https://www.linkedin.com/in/keisha-leon/ Cancer Australia: https://leondesign.co/projects/cancer-australia/ Family Planning: https://leondesign.co/projects/family-planning-nsw/ Streamtime: https://streamtime.net/ --- Send in a voice message: https://anchor.fm/australian-design-radio/message

Arguably one of the most under rated albums? We think so! Listen to us rave about Leon's self titled album and get to know why it means so much to us. 

WWE verlässt das Performance Center und schickt das eigene Produkt in den THUNDERDOME! Wir blicken auf alle anstehenden WWE Veranstaltungen voraus. Außerdem: Umstrittenes Comeback! Warum die Rückkehr des Velveteen Dreams für Unmut sorgt. Leon: Leon spricht seit vielen Monaten für den Spotfight News-Kanal die Videos und konnte schon Podcast-Erfahrung sammeln. Neben dem Wrestling begleitet ihn der Fußball in Freizeit & Beruf. https://www.twitter.com/Leon_Karasch  Tobi: Der „Toaster“ berichtet schon seit einigen Jahren auf unserem News-Kanal. Er arbeitet als Sprecher, Moderator und Bundesliga-Berichterstatter. https://twitter.com/TobiTextet  Folge auf YouTube: https://youtu.be/3hSb-T3M3Es ➜ Merchandise: https://teespring.com/stores/spotfight ➜ Sichere dir exklusive Vorteile (+Podcasts) und unterstütze das Projekt hier: https://www.patreon.com/SpotfightPodcast ➜Jetzt auf YouTube abonnieren!

Junge Menschen in der Sauna? – Mangelware. Genau deswegen wollen Leon & Leon diesen Zustand ändern. Die zwei Studenten nehmen dich mit und erzählen von ihren (natürlich Laienhaften) Eindrücken, was sie so Witziges in der Sauna erlebt haben, aber auch wie das ganze System eigentlich funktioniert und warum man sich vor einem Saunabesuch nicht scheuen muss.

In unserer ersten richtigen Episode widmen wir uns sofort einem DER Themen zum Thema Sauna. Dem Nacktsein.  Muss ich mich unbedingt ausziehen? Ist das in jeder Sauna so? Sehe ich für die Sauna überhaupt gut genug aus? Diese und weitere Fragen beantworten wir heute. Es gibt kaum ein anderes Thema was so lang und breit diskutiert wird und über welches auch ziemlich viele Unwahrheiten verbreitet sind. Doch heute ist damit Schluss. Leon & Leon räumen mit ein paar Klischees und Gerüchten auf und erzählen Dir, was Du in Sauna zu tragen hast, bzw. nicht zu tragen hast. Und so viel sei verraten: Es spielt überhaupt keine Rolle wie du aussiehst. Wir gehen schließlich in die Sauna, um eine schöne Zeit zu haben und nicht um die Cellulite des Gegenüber zu bestaunen. 

"Everything is awesome! Everything is cool when you're part of a team!" - so goes the impossibly catchy song from the Lego Movie. In IT, we are often expected to be caught up in that same spirit - hyped up on the adrenaline of fixing systems, catching hackers, and inventing new stuff. These expectations - which come from external sources like our boss or company or IT culture at large, or internally from assumptions we've taken on as personal truths - can fly in the face of how we're actually feeling. When our feelings turn from just being "a little tired", "a little frustrated", or "a little sad" to serious challenges like burn out, rage, or depression, it can be hard to admit, let alone seek help or ask our coworkers for support and understanding. And yet religious, moral, and ethical traditions are rich with stories of people coping with the exact same challenges. In this episode, we're going to get brutally honest about the mental health challenges we've faced and are facing today as well as what lessons from our faiths we can carry with us to provide insight, comfort, and even strength. Listen or read the transcript below. Destiny: 00:00 Welcome to our podcast where we talk about the interesting, frustrating and inspiring experiences we have as people with strongly held religious views working in corporate IT. We're not here to preach or teach you our religion. We're here to explore ways we make our career as IT professionals mesh or at least not conflict with our religious life. This is Technically Religious. Music: 00:24 "Everything is awesome! Everything is cool when you are part of a team. Everything is awesome..." Leon: 00:31 So goes the impossibly catchy song from the Lego movie and it we are often expected to be caught up in that same spirit hyped up on the adrenaline of fixing systems, catching hackers and inventing new stuff. These expectations can come from external sources like our boss or company or it culture at large. We're internally from assumptions we've taken on as personal truths and can fly in the face of how we're actually feeling Yechiel: 00:56 When our feelings turn from just being a little tired, a little frustrated or a little sad to serious challenges like burnout, grades, anxiety or depression. It can be hard to admit or let alone seek help or ask our coworkers for support and understanding. And yet religious, moral and ethical traditions are rich with stories of people coping with the exact same challenges. Josh: 01:15 In this episode we're going to get brutally honest about the mental health challenges we faced and are facing today as well as what lessons from our face we can carry with us to provide insight, comfort, and even strength. I'm Josh Biggley and the other voices you're going to hear on this episode are my partners in podcasts, crime, Leon, Adato. Leon: 01:35 Hello. Josh: 01:36 And Yechiel Kelmenson. Yechiel: 01:38 Hi again. Josh: 01:39 Hello. All right, so this is a bit of an odd episode for us. Um, I mean this, this feels a little heavy. So before things get to, you know, heavy for us, little shameless self promotion. Leon, why don't you lead us off? Leon: 01:55 Okay, so I'm Leon Adato, uh, I'm a Head Geek at SolarWinds. You can find me on Twitter @LeonAdato. I blog and pontificate on all sorts of technical things at www.adatosystems.com and identify as an Orthodox Jew. Yechiel: 02:11 I'll take a next, uh, I'm a Yechiel Kelmenson. I'm an engineer at Pivotal. Um, you can find me on social media at @YechielK, um, if you want to read what I have to say, it's on my blog at RabbiOnRails.io and like Leon, I'm an Orthodox Jew Josh: 02:26 And I'm Josh Biggley. I'm currently an enterprise monitoring engineer, but by the time this episode drops, I'll have started a new role as a senior tech ops strategy consultant at New Relic. You can find me on the Twitters, uh, at, @jbiggley. Um, I don't actually have a place where you can find me other than I would say Twitter, LinkedIn. I I've taken to, to posting a fair bit on LinkedIn. Um, and I identify as an ex Mormon, Leon: 02:52 Um, and I'm obligated to point out to everyone who might be scribbling madly to try to write that down, that we will have show notes and it will have all those links and everything else we refer to in this episode. So please don't worry, just sit back, relax and listen, just to enjoy the conversation. So I, I have to say that this entire episode was actually inspired by a comment that Josh made during one of our other podcast. It was episode 28, which is titled Release to Production. Once again, we'll have a link to that in the production notes and around the 12 and a half minute mark, Josh said this: Josh: 03:26 And then in my own family, right, I suffer from depression and my work toward getting promoted happened to coincide with a really difficult depressive episode. Leon: 03:37 So Josh, I want to start off by talking about that specific moment. Um, do you find that you're talking, you talk about your mental health often. Josh: 03:46 I mean, you know, mental health, um, I, you know, as this episode title fight, the stigma, um, says is perhaps not something that I've talked about often. Look, I've, I've dealt with mental health issues, um, at least going back into my late teens. Um, it's something that, that kind of ebbs and flows for me. It's something that I'm comfortable with talking with my family about what my immediate family. Uh, and there are a few other people in my circle of trust who I've, I've talked to my I talked to about my mental health. Leon: 04:21 Okay. So that being the case, you know, you, you're not mental health forward when you have, hi, my name's Josh and here's my depression is not how you do things then. Then I have to ask because it, you can hear in the clip. It was just something you said and it was a point that you were making as part of a larger conversation and we move, you know, and we moved on from it. But I have to imagine that that had to feel a particular way to say that on the air like that. Josh: 04:49 I think the advantage of doing a podcast is that you record it and then it's done. And then you, you almost forget that you say it at least until I do the transcriptions. And by that point, Leon: 05:01 by the way, thank you. Josh: 05:01 You're welcome. And by that point, here's the thing, when, when you're struggling with something, um, confession is good for the soul. And I honestly, I do believe that it is good to share. I mean, did I intend to share at that particular moment? No, I didn't. Do I regret sharing? No, I don't regret sharing. Leon: 05:29 Okay. Which, which takes me to the last, you know, basic question about that moment, which is have you gotten any feedback, you know, on, on social media or in, you know, on the blog that's associated with Technically Religious or anything, you know, or even just comments that you've gotten one-on-one. Josh: 05:44 Has anybody come in and said, wow, you know, you said that and X, Y,Z , you know, uh, I haven't, and, uh, honestly, listeners, I'm a little disappointed. Uh, I know that mental health is a real struggle for people. I know many, many people, and we'll talk about this a little later, who struggle with mental health, whether we're talking about full-blown depression, whether we're talking about anxiety, whether we're talking about, you know, unhealthy levels of stress, whatever it might be, and nobody reached out. Um, I think the stigma is very real. And so, you know, if, if you're struggling or if you want to talk, you know how to find me. Leon: 06:26 Right. And I think that goes for certainly all three of us. And I, I would also say that, um, the, the Technically Religious, uh, speaker cast at large, um, one of the things we've all been very open about is, is saying, look, if you have a question about anything that you are dealing with struggling with, have a question about, curious about, we're all pretty, Oh, we wouldn't be doing a podcast if we didn't want to talk about it. Josh: 06:50 That's right. And we do like to talk. I mean, we're, we're pretty good at it. Leon: 06:54 So that's on sort of the, the podcast technical social media side. Have you shared these kinds of things in religious contexts? Josh: 07:03 Um, no, no, no, I haven't. Eh, and, um, yeah. Uh, and there's a reason for that. Um, in my, my religious community, um, as I said, I'm ex-Mormon, uh, now as our listeners know, I've, I've been transitioning since this podcast started. Um, there is a very toxic culture of perfection. Admitting that you have a mental health struggle is not a minute, is not looked at. It's looked at as a weakness. All right. Um, I F my personal experience, um, included some really fantastic people, but I also met some of the most cutthroat people that I've ever encountered in my entire life. And when you showed that soft underbelly, that weakness, your fear was that they would got you. Um, and here's the thing that's not unique to Mormonism. Um, I expected that is anytime you get a group of people together, you're going to find those, those individuals. I mean, in some organizations they may be more, but there's probably one, at least one in every organization. And for me, ultimately the, the question that I, I had to ask myself was, am I, am I generally comfortable with sharing this, um, within my religious context? And the answer was no. I mean, it's not that I didn't share it with people who shared my religious beliefs. I certainly had those, those moments, but it wasn't something that I got up in the middle of a sermon. I was like, yeah, yeah, I, I suffer from depression. And those things just didn't happen. Leon: 09:01 Right? So I think it's, it's important to point out, and, and I've said it in a very particular way on this podcast a couple of times a Judaism and apparently Mormonism also have not found the cure for the common asshole. There's still gonna be, you know, individuals who are jerks regardless of their religious affiliation. And that's, you know, that's the truth. But it's got to be hard when you are talking about, uh, w when you're having conversations around ethics and charity and Goodwill and kindness to know that there is a line in the sand that you're just not comfortable crossing that by all accounts shouldn't be there. Um, so in the Orthodox community, my, my first and my visceral experience with talking about mental health, and it's not the only one, but it's the one that comes to mind every time, is that when, when mental health comes up, um, where a lot of people go is that admitting to or getting help for mental health will make it harder for, uh, children to get a shidduch or get a match for a marriage, um, either for themselves or for siblings. So a lot of families will sweep those kinds of things under the rug. And again, it's not just don't talk about it, it's also not medicating children for everything from attention deficit to, to anxiety, to oppositional defiance disorder to anything. Because the medication itself is an admission of a problem and that can get out in the community and that can be seen as a challenge. I'm not saying it is a challenge, but I think that a lot of families immediately, that's their first worry is my kid won't be able to get married because of it. Yechiel: 10:47 Yeah, I definitely seen saying as far as the Orthodox Jewish community, that's probably the biggest obstacle in terms of talking about mental health. Um, and then on a secondary, uh, you know, started saying secondary and isn't that it's not as big a problem as the shidduch problem. Um, I find also that people have a hard time sort of owning up or admitting that they have, that they have issues because there's like, there's so much stress put on, on, you know, believing in God and trusting God that everything is good, that everything that God does is good and therefore you should be happy and you should be confident and you should be. Um, the umbrella term for it in Judaism is betach baShem to have trust in God and you feel like when you don't feel that way. When you feel, when, when you do have depression or anxiety or whatever it is, you feel like there's something wrong with you. Like if I was religious enough, if I took these ideas more to heart, I wouldn't be feeling this way. I wouldn't, you know, it's a, it's a failure on my, on my part as a person, as a religious person, not realizing course that it's a health issue, like any other health issue. And just like getting the flu doesn't mean that you're trusting God is lacking. So it doesn't getting depressed me. That is a problem in your life. Leon: 12:04 And that's, and I think we'll, we'll talk more about that in a little bit about, about how things can be addressed. But yeah, it's, it's really hard when a crisis of mental health also becomes a crisis of faith because I think those two things have a really easy time of feeding upon each other to make the entire situation much, much worse. Josh: 12:24 So I'm curious, something that, that comes to mind, um, that, at least on the surface appears to be a commonality, is this idea of the gospel of prosperity. And you see it a lot in Christianity, right? It's the whole idea that, well, if I'm, if I'm obedient enough and if I give enough than if I serve enough, then God will give me. And if I'm, if I am poor, if I'm sick, if I struggle, then you know, obviously I'm not doing, or even worse, you know, if you Yechiel, you know, if he's struggling, well obviously he's not. Uh, and then we get into that judgment that is unfortunately very prevalent in Christianity. And, and for those who are, who cannot see Leon, he is, he is writhing and agony here. Leon: 13:18 I only learned about prosperity gospel a year or two ago. I never heard of it before. And the whole thing just, I can't, I still can't wrap my head around it because it's not, it is absolutely not a Jewish concept. Um, and it, that's not what this episode is about. Josh: 13:39 That's interesting though because it's, at least within Mormonism, there is a lot of veneration about leaders and you know, how do we follow those leaders? And one of the things that at least if you go to your local bookstore and cause they still exist, there are places you can actually buy books that aren't online. I know it's weird, but if you go to your local bookstore and go to the self help section, you're going to read a titles from people who are leaders in their spaces, right? And we look to those people for inspiration. Today I was on LinkedIn and uh, uh, Jeff Weiner, who was the CEO of LinkedIn, shared a post, uh, and we'll put it in the show notes, but he was asked about what his leadership values were. And I thought that these were really interesting because as, as we're talking about this stigma or the potential for a stigma around mental health, um, if I had mental health struggles, I would want to be an environment with a leader like this. Here's what he said, "Be compassionate, be authentic, be open, honest and constructive. Be of service others. Lead by example, inspire." I thought, Holy cow, that that is what I want would want in a leader. And if I had a leader like that, then I would feel comfortable opening up to them and saying, look, these are my struggles. This is what I'm dealing with. Ken, how can I help? Or how can I continue to work and work through these struggles? I dunno, uh, Yechiel, what values do you have or what attributes do you value in, in others professionally, whether fellow engineers, managers, leaders? Yechiel: 15:38 Obviously in addition to having their technical ability, I think if they can't share that tech and global, I said, I don't have the empathy to, to look back and bring back, bring people up with them, you know, um, then, uh, they're started sort of uselessly. Um, there's a whole thing going on in Twitter now about 10X engineers. And I heard someone who said it that defined it very well. 10X engineers that someone who writes 10 times more code at 10X engineers, someone who can teach 10 times 10 more, 10 other engineers who can create 10 other engineers is sort of as a force multiplier. So if you don't have this empathy of, you know, if you don't have the communication ability and being able to bring other people up behind you, then what are you worth? Josh: 16:27 Hmm. I like that. Alright. Leon? Leon: 16:28 Yeah. Um, so in terms of professional values, I think it's all the things that are unfortunately labeled soft skills, which says everything that you need to know about how an organization perhaps views them, um, which is wrong. I think that people's ability to connect on a human level is significantly more important than their ability to do any particular technical trick. Um, or I guess I should say that if I need a particular technical skill that's a consultant or a contractor that's not a colleague, a colleague is somebody that I wanna build a relationship with. And, and Josh, to go back to your point from earlier on, I want to be among people that I am, I would be comfortable sharing those parts of my experience, not saying my life. I am not saying that you have to work with people at work who you're buddy buddy with, but you have to work with people who you can be vulnerable with in a work context where I can say, I don't know, or this has me frustrated or I'm really frightened about taking on this task. I'm, you know, I'm apprehensive about this. And you have to be able to say that, not because it's important to be vulnerable or whatever, but because if you, if you can't say that, then you're going to either avoid doing things that are, uh, opportunities for you to grow in your career and your skills, or you're going to do it anyway, and you're going to sort of do it in that sort of blind haze of panic and you may not execute well. Whereas if you have a team where you can comfortably say, I'm having a really hard moment right now, can I have, can I have five minutes? Can I have half a day? Can someone sit with me while I do this? You may not have to do anything, but I just need, I need a buddy on this. You know? Um, when you have a junior engineer who comes in and says, I've actually never, you know, done this kind of coding before and can feel comfortable saying that and the team and say, not a problem. You know, I'm going to sit right here. I'm gonna do my own thing. But when you have a question, I'm right here to answer it for you. You know, that's again, that's a vulnerability in a work context that I have to be comfortable enough to say that's the things that I value are people who, who foster those kinds of conversations. Josh: 19:03 You used a, a phrase there, um, or an example where you said, I'm not comfortable doing this thing. One, that is a really tough thing to do professionally, but it reminded me of one of the very last experiences I had in Mormonism. Um, so for context and Mormonism, there are no, there is no paid clergy at the local level. Um, they do practice lay ministry. So that means that the, the leader of your congregation is, could be your accountant to, it could be, uh, he could play a plumber. In my case, um, the, the leader of the congregation I attended as, is actually a fellow it pro, um, works for the provincial government. Really nice guy. Um, but my responsibility in the congregation was as the clerk. So I, I had a chance to invite, uh, people at the direction of, um, our Bishop to, to give sermons on Sunday and we call them talks and Mormonism. But we've actually there, there are many sermons and you'd be assigned. Everyone in the congregation ultimately gets assigned. And I remember we assigned a topic to a woman who's been a member for a very, very long time, um, you know, many, many decades. And she approached me probably a week before she was supposed to give her her talk, her sermon, and she said, Josh, I, I can't do this. Like, I, I can't speak on this topic. Uh, if you're interested, the topic was the physical nature of God. Right? Um, and so, you know, Hey, it's a heavy topic, but she's like, I read this and I'm, I, I don't, I don't understand it. And my response to her was, then talk about what you're comfortable with. I mean, pick parts of, you know, the reference material that is good for you, and then deliver that. But in your, in your comments, Leon, I was struck by how rare that might be. You know, oftentimes we're told, well, you know, just, just go ahead and do that. Um, so my next question for both of you is, we've talked about these values that we, um, that we want to see in our colleagues, in our managers professionally. Are they any different than our religious observance? Yechiel: 21:16 Not necessarily. Um, and Judaism, there's, there are two kinds of commandments. Um, there's been a bein adam lamakom, which are commandments between man, between a person and God. And bein adam lechaveiro between a person and another person. So the first category would be commandments around prayer, around the holidays, things that are between you and God. Um, the second one includes things like, do not steal, be nice to each other, help each other out. And the Talmud is full of quotes that say that if someone says that I owe, you know, there's a quote about the ethics of our fathers. If a person says, I only have Torah, then he doesn't, then even Torah, he doesn't have meaning. If someone says, yeah, I'm just going to study and learn Torah all day, that's my thing. Uh, doing things and, you know, being nice to others. That's that, you know, that I'll leave that for others. Then he doesn't even have the Torah because the Torah is all about helping others and being good with others and being good to the world. So, yeah, so just like an it, having the, you know, having the, the brilliance is nothing if you're not going to share with others, if you don't have the humility to pay it forward. Leon: 22:28 Right. And, and as an example of that, um, you know, when we're talking about rabbis, you know, the, the congregational leaders, and, and we'll get to that in a little bit also. Um, well what that really means in a Jewish context, but if a rabbi isn't comfortable getting up as part of his discussions, whether it's a sermon or a class or a lecture or, uh, a conversation, um, and say, and this thing happened, and I was, I didn't even know where to go with that, or I was feeling really overwhelmed or it really scared me. You know, any of those things. Once again, same thing as we talked about with the IT people. If they're not comfortable admitting to that, you know, quote unquote weakness, then that's, um, that's problem. If they're laboring under the misguided assumption that they have to be infallible, that is not going to end well. Yechiel: 23:27 Yeah. Uh, actually reminds me of something like my teacher brought up a lot. Uh, one of the foremost commentators on the Torah Rashi, Rabbi Shlomo Itzhaki, who lived around 900 years ago in France. And he, so he's like the foremost commentator on the Torah, every pretty much every homeless you'll find at any synagogue has his commentary there. And there's actually a pretty famous, uh, one of the verses, Rashi quotes some line from the verse and says, I don't know what this is teaching us. And my teacher said, you know, why did he bother saying that? If you don't know, just leave it out. I mean, you're not, why do you have to tell us? So how many did you say that, you know, it's true. There were probably many other places where Rashi didn't know any, he didn't say anything, but he made a point to say it at least, at least once. So that we should know that it's okay to say, I don't know. Josh: 24:18 I liked that. I liked that. So what happens when we encounter in our professional, personal, religious, you know, community environments, people who look at these values that we have, that we, that we desire and others and be like, I don't care. Wait, I, I'm going to violate these values. I mean, I can tell you what happened to me that led to my transition out of Mormonism when I saw people within Mormonism, uh, specifically leaders of the church who were acting in a way that had I acted locally, my wife would have been mad at me, my fellow congregants would have been mad at me. My Bishop may have pulled me in and said, Hey, Josh, like, what the hell are you doing? Like this is not the way you behave. Um, I certainly would have been judged. And so when I saw that from others, that began my spiral down up. I don't know which direction, uh, at the time it was down, but now I feel like it was up. Uh, and, and ultimately out of Mormonism. So, I mean, Leon, Yechiel what happens, what happens when we're, we're, we're, our values are violated? Yechiel: 25:23 So I think like Leon mentioned earlier that, you know, no one found the carry out for the common asshole. Um, you realize that you know these things, you know, these people exist and they are not the people that we want to be around. If it's possible, like you did so cut them out of your life though that does come from place of privilege and how it always is that an option both in religion and in it, not always can you just leave your job or leave your congregation or leave your community. Um, but if you can do it, if you can't try to distance yourself as much as you can. Leon: 25:59 I know that Josh, your, your transition was, you know, there wasn't like, well that was the one thing, you know, there was a lot of things that led up to this, this decision. So I don't, I don't want to characterize it as well, if only you had done this one thing that you wouldn't have those problems. You know, again, it was like all real problems. It was complex and had a lot of moving parts. Um, I think that if, if anyone listening has an experience with somebody where, you know, again, they violate these values that the religion as a whole holds as fundamental or that you personally hold as fundamental. I think the thing is to remember that they're one individual, that they're, you know, that, that they don't make up the sum total of a community, IT community or, or other. If you find yourself in an environment where those values are upheld and lauded, you know, the, the so-called toxic environment, you know, bro-grammer culture in an IT department or um, you know, or, or toxic management or, uh, or just a really unhealthy congregational life or a congregation that, that espouses a value that isn't intrinsically negative, but it's not something that's helpful for you, um, to remember that you, you do usually to Yechiel's point, usually have a choice. And that choice doesn't have to hurt. It just, it might be different. And to give you a very innocuous example of that. And I've talked about this on our podcast before, I, I read Hebrew very slowly. I'm, I've been working on it for a long time. I'm getting better, but it's still slow. And so when I find myself in a congregation that values the speed with which the prayers go, "we can get morning services done in 20 minutes. It's great!" You know, when, when I'm in there like, Hey look, I found somewhere that's not my place. This is really not for me. Um, and as you know, if I'm, if I need to be in that environment for whatever, I just sort of tough it out. But I know that as soon as I can get out of that environment, I, that's, that's what I'm going to need to do. It's not helpful for me. It's not healthy for me. It doesn't do anything for me. So that's again, that's an innocuous version. If you are in an environment that is exacerbating your mental state, um, either because you know, what you're hearing in the pews is mimicking the, the mental negative self talk that you have going on in your own head or it's making you feel more anxious rather than less or you feel like you can't share anything about who you really are with the people around you. Then, you know, it may take time, but you need to know that there are other communities, there are other places to go in most cases. Again, I'm not diminishing the, the long journey that Josh, you and your family have gone through. Josh: 29:04 No. Yeah. I think that Maya Angelou really sums up something that I wish I had known before and I, I didn't know who my Angelou was before I began my faith transition. But among other notable quotes, she says, "When someone shows you who they are, believe them the first time." And I think that that's really powerful when you are, when you're looking for people who you need to trust. Um, especially when it comes to our mental health. Um, if someone tells you, I am not someone who's going to protect you, um, and you see that, don't bring them your struggles because they're there, they're not going to be healthy for you. Leon: 29:46 Can't wish people into being the person that you need them to be at that moment. Josh: 29:50 That is right Leon: 29:50 We know you can't listen to our podcast all day. So out of respect for your time, we've broken this particular conversation up. Come back next week and we'll continue our conversation. Doug: 30:00 Thanks for making time for us this week to hear more of Technically Religious, visit our website, TechnicallyReligious.com, where you can find our other episodes, leave us ideas for future discussions and connect to us on social media. Josh: 30:14 At Technically Religious, we usually have something funny to say at this point in the show, but mental health is nothing to take lightly. If you are struggling, please reach out to a family member, friend, or a healthcare professional. If you are in crisis, please seek immediate medical attention. You are not alone. Fight the stigma.

The illustrious Mr. Leon Leon Lee was nice enough to join us again for Part II to to go deeper into his incredible journey in sports, business, and life story as former pro baseball & manager Leon Lee who was the first African American Manager of a Japanese baseball team. And if you didn't listen to our very first episode with Mr. Lee in Episode 1, check that out too!

Chris Leon grew up with wine around the table via his Dad. His early love for hospitality and, eventually wine led him to Sonoma. He attended the French Culinary Institute, now the International Culinary Center after college, with a degree in restaurant management. Chris went on to open and operate restaurants in NYC and earned his Advanced WSET Certificate. He knew hospitality extended beyond the walls of a restaurant and opened Leon and Son, a highly curated wine shop in Brooklyn. It's HRN's annual summer fund drive, this is when we turn to our listeners and ask that you make a donation to help ensure a bright future for food radio. Help us keep broadcasting the most thought provoking, entertaining, and educational conversations happening in the world of food and beverage. Become a member today! To celebrate our 10th anniversary, we have brand new member gifts available. So snag your favorite new pizza - themed tee shirt or enamel pin today and show the world how much you love HRN, just go to heritageradionetwork.org/donate The Grape Nation is powered by Simplecast.

Weeks ago, the world watched helplessly as he Notre Dame Cathedral, burned. While this event was notable for many reasons, one of the things that struck us here at Technically Religious was the protocol used by emergency responders: Save the people, save the art, save the altar, save what furniture you can, then focus on the structure, in that order. We know what can be rebuilt and what can't.” In this episode, Josh and Leon compare and contrast that disaster recovery process to the ones typically used in IT. Listen or read the transcript below. Leon: 00:00 Hey everyone. It's Leon. Before we start this episode, I wanted to let you know about a book I wrote. It's called "The Four Questions Every Monitoring Engineer is Asked", and if you like this podcast, you're going to love this book. It combines 30 years of insight into the world of IT with wisdom gleaned from Torah, Talmud, and Passover. You can read more about it, including where you can get a digital or print copy over on adatosystems.com. Thanks! Leon: 00:25 Welcome to our podcast where we talk about the interesting, frustrating, and inspiring experiences we have as people with strongly held religious views working in corporate IT. We're not here to preach or teach you our religion. We're here to explore ways we make our career as IT professionals mesh - or at least not conflict - with our religious life. This is Technically Religious. Josh: 00:45 A few weeks ago, the world watched helplessly as one of the iconic buildings in Paris, the Notre Dame cathedral burned. While this event was notable for many reasons. One of the things that struck us here at Technically Religious was a response by one of the bystanders, who understood what was happening on the ground. He said, Leon: 01:04 "The fire department in Paris followed a protocol. Save the people, save the art, save the altar, save what furniture you can, then focus on the structure. In that order. They know what can be rebuilt and what can't." Josh: 01:17 Now that smacks of a disaster recovery policy to us. But I think we in IT might look at it differently. Which is what we're going to do in this episode. Joining in the discussion with me today is Leon Adato. Leon: 01:31 Hi everyone. And of course, the other voice that you're hearing is Josh Biggley. Josh: 01:35 Hello. Hello. Leon: 01:36 Okay, so I think the first thing, because we're talking about disaster recovery, is let's get our terms. Let's define our data library and differentiate between redundancy, high availability, disaster recovery, risk mitigation, all those things. So do you wanna take a crack at it? Do you want to just collaboratively? Do this? Josh: 01:58 I love redundancy. And in this world of cloud, I think redundancy is the thing that we do really well now because you know, you can set up a system that is in two regions and so if one of your regions fails here, the region will pickup, you can do a multisite region. Redundancy to me feels like a descriptor that actually bridges across HA and DR and risk mitigation. Um, yeah, redundancy feels like a catchall term, right? It's not something you can achieve. I don't know. What do you think, Leon? Leon: 02:36 All right. All right. So I think redundancy at its simplest is "there's another one of them." There's another Josh: 02:42 Oh, like RAID Leon: 02:43 Yeah. Okay. Right. There's like RAID, you know, having multiple disks - RAID 0 - which is just having two discs, one backing up the other constantly. Or RAID 5... any of the other flavors of raid. So I think redundancy means "having more than one" and yes, redundancy can fit into a high availability plan. But high availability is more nuanced. High availability means that no matter what happens, the "thing" - the service, or the the network, or whatever, is going to be available. That can also be done by doing load balancing. It can also be done by, you know, in networking terms, channel bonding, so you can have those. So redundancy by itself is just "more than one of those at a time." So if one fails, the other one is still going or can take over. But high availability I think has more flavors to it. And then you have disaster recovery. That means that all your beautiful efforts at high availability have failed and it still went down. And so now you're left trying to recover from the failure. But at that point the failure is done. It has occurred, the system has crashed, you know, the meteor has hit the data center. Whatever it is and now you're trying to rebuild or pick up the pieces or whatever it is. Then you have risk mitigation, which sounds a little bit like, "We believe that this disaster could potentially occur, and we want to see what we can put in place to completely avoid the disaster, but we're going to do that ahead of time." So in the case of the Notre Dame fire, it might've been, you know, a sprinkler system. Just something like that. Like that would have been a nice little risk mitigation idea. Josh: 04:37 You know, I wonder how many of those risk mitigation things that we do on our lives are really, uh, to make us feel better. Leon: 04:46 Okay. So like the, you know, security theater kind of stuff, Josh: 04:50 Right, right. Yeah. Like, um, you know, locking your front door. I mean, if someone really wants in your house, they're just going to kick your front door down. I mean, if the police want in, they're going to get in, you know? No deadbolt you pick up at home depot is going to keep them out. Right? Leon: 05:08 No. Um, and, and I know this is a topic that Destiny Bertucci would love to be part of because this is one of her big things. But, so the thing about the dead bolts in the house, it's first of all, they don't need to kick down the door because you have windows. And I don't mean the computer system... Josh: 05:24 Ha ha, ba dum bum! Leon: 05:26 Yeah, we'll be here all week folks. So the thing about deadbolts is that it is way of avoiding, I guess, avoiding risk. It's a deterrent. It's not a protection. I saw some statistics recently that said, unless there was something specifically in your house that that individual wants - you have a Renoir, or a priceless Monet painting, or something like that - then they're just looking for what can get quickly and easily and a deadbolt is absolutely an effective deterrent because breaking a window is too risky and too loud and too noticeable. And if the door can't be easily opened, they'll move on to the next house or structure, where the pickings are easier. Or they'll walk around the house. And I've seen the statistics in neighborhoods where I've lived, that's occurred. Where they tried the front door, they tried the side door, they went around to the back door and "oops!". That one didn't have [a deadbolt. because], "who would go to the back door?!?" Everybody who wants to get in your house would go around to the back door. YOU go around to the back door right when the front... So everyone goes around. So having a dead-bolted system on all of your doors is the most effective deterrent to that. But I think we've gotten a little off topic, you know, in terms of Notre Dame. So I think we've defined redundancy, high availability, disaster recovery, risk mitigation... but what they're talking about, what they talked about in this whole, "first save lives and then save the art, and then save the...", you know, that's different. Josh: 07:05 Yeah, it is, isn't it? Because they almost - well not almost, they gave a priority to specific items. Right? And I appreciate the fact that they said "save lives," lives are irreplaceable. So..., and there are things, there are some beautiful things in that cathedral that were also irreplaceable. Right. But you know, to their credit, human lives come first. Leon: 07:31 Right. And, and I think that that's a pretty obvious one. After that though, taking the priority of lives, then art, and then, um, sorry I'm going back and looking at it... right. "Save the people, save the art, save the altar, save the furniture, then focus on the structure." So, you know, why did the roof, you know, get so hot it melted? Because it was just not part of the protocol... They hadn't gotten to that part of the protocol yet. And also what was said later was that not only is that protocol in place for overall, but it's in place room by room. Josh: 08:06 Oh, interesting. Leon: 08:09 I think there's an order of which rooms they tried to get to first. Again, looking for people. Once they knew all the people were safe throughout the structure, then they were going to specific rooms and looking for specific things to make sure that they could get those out before they moved on to the next category or even the next room. So I find it all fascinating. But the other thing is, do we do that in IT? Do we set up a protocol for which things we save first? Josh: 08:42 You know, I'm thinking back and I don't recall ever having a, "Howell moment" and by Howell I'm referencing Gilligan's island and the Howells and the, "Oh deah save the furniture first!" you know, Leon: 08:58 Save money, save the money! Josh: 09:01 Yeah. I don't know that we've ever had one of those situations. Now, I will say though, we've taken risk mitigation efforts. Back in the days of doing tape backups, you would keep.. now if someone here isn't, you should, but you keep your backups offsite, you would move them to iron mountain and other similar facilities. Leon: 09:26 Well, and, and bringing it forward a little bit, the 3-2-1 policy for backups, which is you have to have three separate backups, physically discrete backups, on at least two different kinds of media, with one of them being offsite. And offsite can be cloud, that's okay. But you know, 3-2-1" three backups to different media, at least two different media. One that is not where you are. So I would say that there is an order, but I think it's almost so self evident that we don't bother elaborating on it, which is: Save the data first. Josh: 09:59 Oh absolutely. Leon: 10:00 Yeah. So data in... Okay, and we're not talking about a fire in the data center, which changes the nature of everything. But you know, the first thing is save the data. The data equals lives in the Notre Dame protocol. If we, if we want to say it that way. And maybe the application is, you know, art, if we want to think of it that way, like the next thing. Once we know the data is secure, then save the applications, make sure, and by save I mean make sure the application can keep running, post disaster, post outage, whatever that is. So, we're both network folks and, we'll say "the network has gone down," All right? The main circuit out to the Internet, to our customers, whatever that circuits gone down. So what's the first thing? Let's make sure the data wasn't corrupted. Now, we might make sure that that happened before the outage by making sure that the system of rights is, you know, won't get caught in the middle of something that we're doing. Whether it's the particular kind of logging on the database or what have you, that those things are taken care of. But make sure the data's fine. Then make sure the application can get out to... "the signal must flow." The signal has to keep going. So can make sure the application is okay. Maybe the next thing in an IT version of that protocol... Uh, I don't know what would it be? Josh: 11:32 So, you know, we've talked about keeping the data, we've talked about getting the application out there. Then it's, "can I get the people who need to be connected to it, connected to it." So one of the things when you have a major disaster, is you're often worried about addressing your largest customers and getting them back. But maybe you've got a remote workers and you don't have the VPN, so they're not going to be terminating in your, your new data center. Or swinging those circuits, those VPN tunnels from your original data center to your new data center. Maybe that wasn't part of your disaster recovery plan. So all of those things I think that's the, "Okay, now, now go get all the bits that make the, make your application experience comfortable. And again, I'm a remote worker, you're remote worker. So being able to connect and provide the support to the business is very important. Leon: 12:32 And I can get behind that in terms of, like, we're the furniture. Josh: 12:34 Yeah. I mean we've been sat on before. It's all right. Leon: 12:39 Right. Sat on, stepped on, brushed aside, Josh: 12:43 and knocked over. Leon: 12:43 Yeah. Right. Yeah, sure. And I think the structure is, it literally that, it's the organizational structure. Make sure... but that's last because it's the thing that can be rebuilt easiest. The other thing about the Paris, the Notre Dame issue was the other comment: They knew it could happen and by that they knew it would happen again because Notre Dame was trashed back in the French Revolution or "The Terror" as someone referred to it. But the thing that was interesting was they weren't making any meaningful changes to Notre Dame even though it had happened before, and they knew it could happen again. And again, I find this fascinating. I've talked and written before about black swans in IT. You know, that really big event where "the application crashed and we couldn't sell widgets to our customers and we lost blah, blah, thousands of dollars." And you know, all that stuff. "And now we need to make sure that never happens again!" Okay. Yeah. But it was a meteor falling on the earth. I can't... why are we spending time even talking about it? And yet businesses spend lots and lots of time trying to protect themselves from the next Black Swan, which is going to look just like the last Black Swan, even though that one is a black swan because it was unpredictable. So why would they not make meaningful changes? Josh: 14:09 So, I wonder about that, right? Like why would we not make meaningful changes when we know that something has happened? And I think you've nailed it there. These are black swan events. The chances that, the realistic chances of "The Terror" happening again, were reasonably small in the grand scheme of things. They also knew that the cathedral itself, although it is iconic, it can be rebuilt. So get the things that will go into the new building and in the new building will have new designs. So here, a tale from Mormonism. The Salt Lake Temple was one of the first buildings that was built in the Salt Lake Valley - major building that was built in the Salt Lake Valley after the Mormons moved there from Nauvoo. And when they got there, they built this temple out of stone that was quarried from the nearby quarries. That temple has stood the test of time. It's, it's been there for, uh, geez, I don't even know how many years. Well over a hundred years at this point. They are shutting the temple down in the center of Salt Lake because they are going to make some changes. They're going to redo the foundation, which at one point had cracked, and then they had to tear it out well before the temple was finished and then put it back in and then finish the temple. But they're going to protect the temple from seismic events. And not that, not that there's ever been a major earthquake in Utah, but you know, there could be, and it's hard to take such a landmark off the grid. People literally from around the world to see that that temple and downtown Salt Lake. So I imagine those changes to the Notre Dame cathedral would have been equally... uh, no, let me rephrase that. They would have been more impactful to a tourism around that facility and the worship services that go on in there. Leon: 16:21 So, yeah, not that Notre Dame doesn't undergo renovations. In fact, this all occurred during a renovation. They certainly were renovating. I just, I wonder about, why not a sprinkler system or whatever. Although, as I sit there and I say it to myself, again, working in IT, well, why don't we put sprinkler systems in our data center? Oh, that's right. That's why we don't do that. And you know, the art, the paintings, the whatever, you know, maybe Josh: 16:51 The servers Leon: 16:52 The servers. Yeah. The wiring, the electricity. A water suppression system would probably be be more damaging than not, than the fire, which I guess people feel that they can outrun. And they did, in large part. You know, they really did. And also that the next step up, a halon system is simply not possible in a structure the size of Notre Dame. Josh: 17:27 I think the key here, though, is don't make any changes because once you make changes, you introduce variables that you can't control. Like really, "no deploy Fridays"? They're a thing. I mean, they should be a thing. Leon: 17:39 So I hear that, although I think that Charity Majors, from Honeycomb.io, is on a campaign for getting rid of that. But... Josh: 17:48 I'm just going say she was the one I was thinking about when I said that, I was thinking "Charity is totally going to kill me." Leon: 17:53 But I will say also that she is presupposing that there is a vastly different architecture in place than A) the kind of structure that Notre Dame is; and B) the kind of day to day small, medium, even large size businesses, but sort of the, the monolithic businesses that we, you and I, are used to working in, I think that she's presupposing that's not the case. Josh: 18:21 Most definitely not. Right. I think if the equivalent of a of honeycomb in architecture would be something akin to.... Boy, I can't even, I I have no idea. I'm like what, what would change as often as an environment monitored by honeycomb? Leon: 18:43 Yeah. So neither one of us is architect enough to come up with a good analogy, but... Josh: 18:50 I have one!! Leon: 18:51 Oh, go ahead. Josh: 18:51 What about a 3-d printed house, one of those ones you can build in a day that like puts the concrete down? I think if you had something like that, Leon: 19:01 ...if that was the case then you wouldn't worry about you. Yeah. You'd deploy changes all the time because you just reprint your plans, right? Josh: 19:09 "Oh honey, I think we're going to put an addition on this afternoon." "Okay. Hit print." All right. There we go. So Honeycomb is like a 3-D printed house. Leon: 19:20 There we go. I'm going to tweet that and see how quickly Charity jumps on there to tell us "erm, no!" Okay. Um, Josh: 19:30 I have a question. You mentioned to me, when we were talking about this episode, about this comment about the "long now in action" and how that resonated with you. Tell me only, what was it about that phrase "the long now?" Leon: 19:45 I loved the idea - and just to put it in context from the tweet (and we'll have it in the notes from the show.) But the original comment, "They know what can be rebuilt and what can't." (I'd said that before) "...the protocol has been in place since the last time the cathedral was destroyed. Sacked during the French Revolution. The steeple and beams supporting it are 160 years old. And oaks for new beans await at Versailles, the grown replacement for oaks to rebuild after the revolution. This is the long now in action. It's what happens when you maintain civilization." So a few more pieces here about why the protocol is in place and how they do it. They actually do have a sense of disaster recovery. They're growing it! There are trees. And in the thread of the tweet that we quoted, the gentleman who tweeted it posted pictures of Versailles with the oaks that have been grown to replace pieces. Now, of course that's also meant to replace pieces that just wear out after a while, or become decayed or something like that. But the entire idea is that they have their disaster recovery. They have their replacement process in place. But the idea of calling it "the long now" - I think in American we call it the long game, right? But the long game has a whole different flavor than "the long now." The long now means that life is happening - now. We are in it - now. But I'm not just looking at this moment. I'm not living for just this moment. I'm living for this moment, and also to ensure that every other moment is able to be sustained or maintained like it. That my children will experience THIS now. They will walk into iconic structures like Notre Dame and have the same experience I'm having in in large part, if not completely. So I just like that. And from an IT perspective, I think that we would do well if we could build in awareness of the long now - and by the way, which things don't need it. Which aspects of our architecture really are momentary and shouldn't be given the "long now" treatment, like Y2K is a great example of not doing that. You're not thinking about the long now, and you're not building in obsolescence into your code to say, "No! At the end of five years, this has to go away. It has to, we have to do something else with it." So that's the opposite of it. I just, I was just enchanted with both the terminology and everything poetically that seemed to be wrapped in with it. Josh: 22:31 Yeah. And, and as I, as I've listened to you wax eloquent about that idea, I do think that that is it. That is really an enchanting idea. Maybe to make it a little more base and brutish. It's that whole argument of pets versus cattle. And I think Netflix was one of the first companies to really push that idea. Don't get so attached to your tech that you can't kill it off. Right? We've got this dog, her name is Mabel. She's a Boston terrier. She's the purebred. And she is literally the most expensive gift I have ever purchased for my wife. Not because she was expensive to buy. But in the first year of her life, she is undergone close to $4,500 in surgery because apparently Boston's have bad knees. Who would have known?? And so for my pets, for this pet in particular, we're willing to literally move heaven and earth to make sure that she's comfortable. Right. But I also enjoy eating cows and I would not move heaven and earth to save a cow. Leon: 23:47 You might spend extra for a really tasty cow, but that's a very different thing. So I have long said both in IT context and also in my home that it's not the cost of the puppy that's gonna get ya. It's the cost of feeding the puppy. Josh: 24:02 Children too, actually. Leon: 24:04 Yeah. Well that's, it's all of them. Right. Iit's like "but you know the puppy's free!" No, it's not. It's not buying the puppy, it's feeding the puppy. And I think that again in IT, we would be well served to remember which of our projects, which of our architectural choices, which of our things that we do during the day, which of our activities, are cattle and can be really sort of thoughtlessly left to the side. And which of them are pets. Cause I'm not gonna say that all of it is cattle. Not, not everything in it can be treated like cattle. We want to do a certain level of commoditization, but it's always gotta be the things that are intrinsically not valuable that, that we can change it. Another corollary in the Dev ops mindset that, since you've brought up Netflix. Netflix is named, but also, uh, other companies are referenced in a book called "The Phoenix Project." And the Phoenix project also mentions this thing called Disaster Kata. Now a kata in karate terms is simply a set of actions that you take, and you do them over and over and over again until they just become muscle memory. And so they do disaster recovery or emergency or chaos kata. So they practice being in trouble and getting themselves out of it when it's not really an actual problem. So that when there's a real problem, you have that muscle memory, you jump into the situation. And that's true of military training. That's true of true disaster responders. They do the same thing. They practice certain behaviors, so that they don't have to think really hard about them when they come. And I think that we see this in the Notre Dame cathedral experience also. Is that they had done their kata. They had figured out the protocol and practiced it or talked through it so they knew what they were doing. And this was an example of it. And again, we in IT would be well served to think about which types of failures, which types of disasters and recovery actions we would be well served to practice beforehand. You talked about backups a little bit ago, you know, practice your restores. Otherwise you have what has become affectionately known as "Schrodinger's backup." The backup is both there and possibly not there, and you won't know whether it's there until you try to restore it. And if it's at the worst possible time and the answer is "the cat in the box is dead," then you're going to have a problem. Josh: 26:42 What you have is you have a branding problem. If you don't know if your backups are there or not there, what you really have are "quantum backups!" You won't know what state they're in until you observe them. So just as long as you don't observe it, then you can assume that they're there. Right? Leon: 26:58 Um, that's, I, I'm, Josh: 27:00 I'm trademarking that too late. Leon: 27:02 That's fine. Quantum backup. It just makes it sound far more exciting and sophisticated, and also then management may want to buy more of it. "Don't check it. Don't check it! You'll let the quantum state out! That's we're paying for. Josh: 27:18 I love it. See, were gonna be millionaires. Millionaires! Leon: 27:21 We are, but we're also not going to be able to show her face in IT conferences ever. "THERE THEY ARE!! GO GET THEM!" All right. So I want to turn this around to the religious perspective and talk about you know, this idea of disaster recovery, this idea of, what we protect and what we don't protect. Now you talked about how the Mormon temple is being restructured because clearly they don't want to lose it. They can't 3-D print the temple in Salt Lake City. So yeah. So they're not gonna even try to do that. And also they know the hit to the community that it would represent if something bad happened to it. Josh: 28:03 And historically, the LDS church has been ransacked right? When they were in Kirtland, the Kirtland temple was destroyed. It was literally burned with, well, I won't say burned to the ground, but it was, it was burned and desecrated. So there's, there is a history in Mormonism, even though it's a relatively new religion from a religion perspective, you know, founded in 1830 of having, it's it's sacred objects desecrated by people who were against them. Leon: 28:35 Right? Okay. So, so in terms of disaster recovery - and again, we'll presume that every church and every synagogue and every temple of whichever stripe or flavor we're talking about, has their own structural, organizational protocol for what to do if the building is on fire - if that happens. But there's other things that had been disaster and disaster recovery. So there's two I'm thinking of, one big and one small. And the big one was the destruction of The Temple (capital letters), The Temple in Jerusalem. And not only was it the building that got destroyed, not only was it the entire organization of the priesthood that was effectively demolished with the loss of the temple and the single focal point of sacrifice, but the religion - Judaism itself - took a hit because at the time Judaism was a sacrifice based religion that, you know, when you wanted to say, "I'm sorry" or "I messed up" or "thank you", the method that you did that through was to go to The Temple, and bring a sacrifice, and the priest would sacrifice on the altar either all or in part, and you would either eat some of it in celebration or not. And there's all sorts of wonderful flavors of that. But you couldn't go do that in your backyard. That was absolutely not an okay thing to do for a variety of reasons that would take too long to go over. There's some wonderful videos that I might link to in the show notes for this episode. But what's Judaism going to do now? The Temple's gone. There's no longer away to say I'm sorry or I messed up or thank you or I'm happy. There's no longer a way to do that. So does the, does the religion just disappear? No. There was a pivot. First of all, the location moved from a Jerusalem to a town of Yavne. And also what happened was a philosophical change that instead of sacrifices on an altar, it became sacrifices of the heart. That prayer took the place of the sacrifice. First and very, very literally by reading the laws of sacrifice. It was analogous to doing the sacrifice. And so every morning in morning prayers, still to this day, Orthodox Jews will read through those laws of sacrifice and the process and the protocol to do it as a way of metaphorically or philosophically saying this is still alive. But also prayer itself. Also, everybody's home has become an altar that on Shabbat, that Sabbath offering that we bring the two loaves of bread and the wine and everything has taken the place of it. So the religion was able to pivot from a very visceral, physical experience of divinity and connecting to the divine to a very, I'm going to say, intellectual and mental connection. And that was a big change. And for the religion to be able to do that was really remarkable. Not to have people just say, "Oh, well yeah, the building's gone. Yeah, that's it. I guess I'm going to be a, you know, I dunno, a pastafarian or, you know, whatever. I'm not trying to offend any pastafarians. The giant invisible spaghetti monster is a fantastic being if or if it does not exist. So that's the big one. The little one though, the little story is actually in the middle of disaster and having this protocol and how it saves more than you expect. So a friend of mine here in Cleveland was telling me a story about his grandfather. His grandfather was a young man in Morocco and, very hilly, you know, a lot of mountains and stuff like that. And they were sort of look in the low lands I guess. And in the spring, you know, the spring melt and the water was coming in. And I guess one of the rivers overran its bed, and the grandfather could hear the water coming at the town, like a flood was coming and he could hear it. And so what do you do? He ran to the synagogue and he grabbed the Torah because you know, that's the thing like, just make sure you have the Torah. Like again, we're not going to worry about the structure. Nobody was in the building, so he grabbed the Torah. Now the thing that you need to understand is: many people have seen a Torah and they see this parchment that is rolled between two scrolls and then covered with a cloth. That is not what a Sephardic - or people from the Middle East, the Spanish country. There, it's in a box. If the scrolls are strung between two poles, but then that's all wrapped in a box itself. A wooden case. So he picks up this case and he realizes he wasn't fast enough. The water is now there. It's coming into the synagogue and it's rising really fast. And he's waiting through this water with this Torah, this huge boxy Torah in his arms trying to get out, and the water just completely sweeps him off his feet and now he's going down the street, you know, still holding onto the Torah. Which is a big wooden box. That holds air inside. And so he's holding it and now the Torah is holding him up. He's floating down the water, this, this deluge holding on for dear life, both metaphorically and physically to this Torah that is keeping him afloat. And it saved him. And on top of it there's a saying that many people say in Hebrew "etz chayim hi lamancha zikim ba" - "It's a tree of life to those who hold fast to it." And that story was passed down generation by generation that in making sure he followed this protocol, making sure he saved that thing, that one artifact, made sure that he was able to survive also. Josh: 35:11 Thanks for making time for us this week. To hear more of Technically Religious, visit our website, https://technicallyreligious.com, where you can find our other episodes, leave us ideas for future discussions, and connect with us on social media. Leon: 35:24 We didn't start the fire, Josh: 35:26 ...but you can be damn sure we're going to be asked to pull an all nighter to fight it.  

This weekend, May 17, 2019, John Wick Chapter 3: Parabellum comes to theaters everywhere and Jonathan (@berkreveiws), Corey (@coreyrstarr), and Michael (@servermonkey) couldn't be more pumped. In fact, Corey and Jon did John Wick chapter 1 & 2 Movie Club episodes a while back, and are very excited for what should be an action-packed conclusion. Though, for this episode of Top Five Movies, the trio decided to look through cinema's greatest Action Heroes and choose their favorites. They like to speak freely about the films so be warned that spoilers can happen. Check their lists below to see if you're comfortable with spoilers! Corey's List: 5. Ash Williams - Evil Dead Trilogy 4. Rocky Balboa - Rocky films 3. Furiosa - Mad Max FURY Road (2015) 2. Selene - Underworld (2003) 1. John Wick - John Wick films Michael's List: 5. Mark Gor - A Better Tomorrow (1986) 4. Jed - Red Dawn (1984) 3. Keung - Rumble in the Bronx (1995) 2. Leon - Leon the Professional (1994) 1. Ripley- Aliens Jonathan's list: 5. El Mariachi - Desperado (1995) 4. Mad Max - Mad Max Fury Road (2015) 3. Ripley - Alien Franchise 2. Ethan Hunt MI:3-6 1. Neo - The Matrix (1999) --- Support this podcast: https://anchor.fm/berkreviewscom-moviecasts/support

This week on Checkpoint Chat, Sandy revisits the spooky hallways of Raccoon City's Police Department, and tries to steer clear of Mr. X. Matty touches on his triumphs in Bloodborne before the pair buckle in for a busy week ahead filled with great game releases. Leon? LEON!? LEEEEEEOOOOON!

ビームス 六本木ヒルズのオープンを記念した1時間特番。前半のゲストはLEON編集長の石井 洋さんと、新店舗のカジュアルフロアを手掛けたビームス執行役員の豊永信一郎。ビームス 六本木ヒルズが遊び場としての六本木の新しいハブになっていくのでは？と石井さんより嬉しいお言葉。後半のゲストとして、LEON.JP編集長の前田 陽一郎さんと、新店舗のドレスフロアを手掛けたビームス クリエイティブディレクターの中村達也が出演。新店舗の魅力を語るとともに、ビームス 六本木ヒルズや六本木という街についてなど語っていただきました。