Podcasts about finagle

The key to raising anti fragile children or becoming anti fragile adults is not found in Murphy's Law nor Finagle's law but in living in discovery mode...Let's try it and see what happens. Life lived is life learned.  Every experience has facts, concepts and applications.  These are stories from the eclectic life of Lonnie Jones, Licensed Professional Counselor, Minister, SWAT Team Chaplain, Outdoor Enthusiast and Quixotic Jedi.   Support this podcast at https://anchor.fm/lonnie-jones/support --- Support this podcast: https://podcasters.spotify.com/pod/show/lonnie-jones/support     Please subscribe and share.   Want lonnie to speak at your event?  Contact:  lonjones@bellsouth.net   Check out YouTube for the live eye view while the episode was being recorded.  Also look for archived lessons, Skits, and videos showing/explaining some of the rope stuff we talk about.  YouTube.com/@LonnieJones   Visit www.lonniejones.org  to find links to original art, swag, 550guys and the following books: "Cognitive Spiritual Development: A Christ Centered Approach to Spiritual Self Esteem"; "Grappling With Life. Controlling Your Inside Space"; "Pedagogue" The Youth Ministry Book by Lonnie Jones; "If I Were a Mouse" a children's story written and illustrated by Lonnie Jones; "The Selfish Rill, a story about a decision" A fantasy parable by Lonnie Jones.      T-shirts, stickers, prints and other art at www.teespring.com/stores/lonnie-jones-art   https://lonnie-jones-art.creator-spring.com/listing/buy-podcast-swag?products=46     #www.worldchristian.org #tkminc2001@twlakes.net #www.hcu.edu #hpcitizensfoundation.org Faulkner.edu/kgst  graduateenrollment@faulkner.edu --- Support this podcast: https://podcasters.spotify.com/pod/show/lonnie-jones/support

A casi todo el mundo le suenan las Leyes de Murphy y seguramente se saben alguna de memoria. Pero lo que no conocerán son las Leyes de Finagle, que podrían ser parecidas pero no lo son. Eso si, ambas coinciden en que el universo es hostil y caprichoso. Vamos a descubrir su origen, su misterio, su rigor científico y su historia. Las leyes de Murphy y de Finagle son dos formas de expresar el pesimismo o la ironía sobre las cosas que pueden salir mal en la vida. Ambas leyes tienen orígenes y formulaciones diferentes, pero comparten una idea común: el universo es hostil y caprichoso. La ley de Murphy se atribuye al ingeniero aeroespacial Edward A. Murphy Jr., quien en 1949 realizó un experimento con un mono y un cohete para medir la aceleración humana. Debido a un error de cableado, el experimento falló y Murphy pronunció su famosa frase: «Si algo puede salir mal, saldrá mal». Desde entonces, la ley de Murphy se ha popularizado como una forma de explicar los fracasos, las desgracias y las coincidencias negativas. La ley de Finagle es anterior a la de Murphy, y se debe al escritor de ciencia ficción John W. Campbell Jr., quien la usaba frecuentemente en sus editoriales de la revista Astounding Science Fiction. La ley de Finagle se enunciaba originalmente como: «Cualquier cosa que pueda salir mal, saldrá mal. En el peor momento posible». Sin embargo, esta formulación se confundía con la de Murphy, por lo que se adoptó una variante más conocida como el corolario de Finagle: «La perversidad del universo siempre tiende hacia un máximo». La ley de Finagle también fue difundida por el autor Larry Niven, quien la incorporó en sus historias del Espacio conocido como una religión ficticia de los mineros del cinturón de asteroides. En resumen, las leyes de Murphy y de Finagle son dos formas de expresar el mismo concepto, pero con diferentes matices y orígenes. Ambas leyes reflejan una visión humorística y fatalista de la realidad, que puede servir para consolarse o para reírse de las adversidades. ¿Qué te parecen estas leyes? ¿Crees que se cumplen en tu vida? Otros temas en el programa: 35:13 Homo Antecessor 52:18 Ulises de Joyce 1:03:46 La perversión de las Redes Sociales No soy un serial killer - Capítulo 13 Puedes leer más y comentar en mi web, en el enlace directo: https://luisbermejo.com/murphy-vs-finagle-zz-podcast-05x26/ Puedes encontrarme y comentar o enviar tu mensaje o preguntar en: WhatsApp: +34 613031122 Paypal: https://paypal.me/Bermejo Bizum: +34613031122 Web: https://luisbermejo.com Facebook: https://www.facebook.com/ZZPodcast/ X (twitters): https://x.com/LuisBermejo y https://x.com/zz_podcast Instagrams: https://www.instagram.com/luisbermejo/ y https://www.instagram.com/zz_podcast/ Canal Telegram: https://t.me/ZZ_Podcast Canal WhatsApp: https://whatsapp.com/channel/0029Va89ttE6buMPHIIure1H Grupo Signal: https://signal.group/#CjQKIHTVyCK430A0dRu_O55cdjRQzmE1qIk36tCdsHHXgYveEhCuPeJhP3PoAqEpKurq_mAc Grupo Whatsapp: https://chat.whatsapp.com/FQadHkgRn00BzSbZzhNviThttps://chat.whatsapp.com/BNHYlv0p0XX7K4YOrOLei0

Alistair Bruce-Ball, Chris Sutton and Statman Dave are joined by Natalie Pike.Following Haaland's performance in double gameweek 25, Natalie Pike joins the podcast to talk about how her season is going as she aims for promotion from Division 2.They discuss whether it's time to wildcard – plus all the advice on which players are must-haves ahead of blank gameweek 26. Plus Natalie takes on Ali in a television-themed game of Sutton Death.

in what seems like a daily occurence at this point, JP Morgan and the USVI are trading barbs and denials once again. This time, JP Morgan has decided to go nuclear, and have alleged that Cecile de Jongh, who was the wife of the governor at the time, attempted to massage the sex offender laws that were being drawn up so that they would be more lax where Epstein was concerned.This latest allegation is just one of many that has been filed in Judge Rakoff's courtroom as the banking giant looks to switch things up on the USVI and put them on the defense.(commercial at 10:19)to contact me:bobbycapucci@protonmail.comsource:Jeffrey Epstein consulted on Virgin Islands sex offender law (lawandcrime.com)This show is part of the Spreaker Prime Network, if you are interested in advertising on this podcast, contact us at https://www.spreaker.com/show/5003294/advertisement

Title Word of the Week: Finagle - To get or achieve something by guile, trickery, or manipulation.to get or achieve something by guile, trickery, or manipulation. -- See the live video playback ON Facebook, YouTube or Twitch. Listen to the show on Amazon, Spotify, Google or anywhere podcasts are available. Just Follow Us For More  --- Subscribe to see more of what we do!! -- Link with us: https://linktr.ee/ExpertsAboutNothingPodcast  

BANG! @southernvangard #radio Ep379! First and foremost, y'all wish Meeks a big Happy Birthday if you haven't already. We weren't able to celebrate last week on the show, so we're making up for it in every way this week. When we say making up for it - we mean it - how about THREE, count ‘em THREE WORLD EXCLUSIVES from EDDIE MEEKS & DJ POCKET'S upcoming project, “TOXIC MASCULINITY”. Throw a few glasses of 130.2 proof courtesy of Old Forrester and you got yourself a show for the ages. Oh, and that bday gift for Meeks - just head to SOUTHERNVANGARD.BANDCAMP.COM and cop our new book for a cool twenty spot. THAAAAANK YA and YOU WAAAAALCOME!!!!! #SmithsonianGrade #WeAreTheGard #YouWaaaaalcome // southernvangard.com // @southernvangard on all platforms #undergroundhiphop #boombap #DJ #mixshow #interview #podcast #ATL #WORLDWIDE #RIPCOMBATJACK Recorded live October 29, 2023 @ Dirty Blanket Studios, Marietta, GA southernvangard.com @southernvangard on all platforms #SmithsonianGrade #WeAreTheGard twitter/IG: @southernvangard @jondoeatl @cappuccinomeeks Pre-Game Beats - Jansport J Talk Break Inst. - "Longdale Dr." - Nottz "Be Better" - Eddie Meeks (prod. DJ Pocket) ** WORLD EXCLUSIVE ** "Halfprice" - Domo Genesis & Graymatter "Forever" - Eddie Kaine & BP Infinite "Globe Holders" - P.U.R.E. ft. Inspectah Deck "Close the Market" - Freddie Black ft. Tash (prod Spliftout, cuts Tone Spliff) "Better Days (MiLKCRATE Remix)" - JRoberts x IMPERETIV x L-Biz x Rasheed Chappell "Y'all Clowns" - Stu Bangas ft. Psycho Les & Celph Titled Talk Break Inst. - "The Gardener's" - Nottz "Bet You Wont Say That Shit (In My Face)" - Eddie Meeks (prod. DJ Pocket) ** WORLD EXCLUSIVE ** "The Tale Of 2 Cities" - Kxng Crooked & Joell Ortiz (prod. Hesami) "Fupa" - AG Da Coroner & Doza The Drum Dealer ft. OSVN, D. Goynz, Mo BUks, William Bostick, Kaeson Skrilla, & Cargo Qell "Inhumans" - Stu Bangas ft. Apathy "Very Superstitious" - Verb T & Vic Grimes "Luxurious Apartheid (MiLKCRATE Remix)" - Napoleon Da Legend x J Scienide x DJ Jon Doe "Nothing Is Freestyle" - The Alchemist Talk Break Inst. - "W. Tanners Creek Rd." - Nottz "Neuschwanstein" - Crimeapple (prod. Bohemia Lynch) "Halloween Havoc" - Creasy x Uncle Fester "Fendi In The Night (Hypebeast Edition)" - RU$h & Mike Shabb "No More" - Kxng Crooked & Joell Ortiz (prod. Heatmakerz) "Finagle" - Al.Divino "Jerkin" - Frog Brothers ft. Bobby Craves & Fazeonerok (prod. Montega Mateos) "Baltimore Protest Joint" - Eddie Meeks (prod. DJ Pocket) ** WORLD EXCLUSIVE ** Talk Break Inst. - "Cedarwood Ct / Rosemont Middle" - Nottz

Jessica discusses Drake getting the key to the city, talks about Xavier Tilman Sr's option being picked up by the team, shares what she is watching on TV and more.start Jessica's island vacation preview:12 Drake gets keys to the city of Memphis:20 Xavier Tilman, Sr. option picked up:38 REPORTED news from around the NBA:45 Dame Lillard's saga:57 LSU wins men's CWS1:01 Non- NCAA National Champions1:13 TV Tuesday1:17 Nobody wants to be on 'Hard Knocks'1;21 'The Idol' moves up season finale1:24 What we're watching

Check out our new website: campcounselorspodcast.com  Bonus Content: patreon.com/campcounselors Submit your advice needed, juicy gossip, confessions, and horror stories at campcounselorspodcast.com Camp Songs Spotify Playlist: https://spoti.fi/3qyK0ri Camp Songs YouTube Playlist: https://youtube.com/playlist?list=PLg9-jhcwB2oYDvLR8zGn8t8rS0q_umm8J Camp Counselors TikTok: https://www.tiktok.com/@campcounselorspod Camp Counselors Instagram: https://www.instagram.com/campcounselorspod/ Camp Counselors Twitter: https://twitter.com/_campcounselors

Check out our new website: campcounselorspodcast.com  Bonus Content: patreon.com/campcounselors Submit your advice needed, juicy gossip, confessions, and horror stories at campcounselorspodcast.com Camp Songs Spotify Playlist: https://spoti.fi/3qyK0ri Camp Songs YouTube Playlist: https://youtube.com/playlist?list=PLg9-jhcwB2oYDvLR8zGn8t8rS0q_umm8J Camp Counselors TikTok: https://www.tiktok.com/@campcounselorspod Camp Counselors Instagram: https://www.instagram.com/campcounselorspod/ Camp Counselors Twitter: https://twitter.com/_campcounselors

In this episode, we cover: Aaron talks about starting out as a developer and the early stages of cloud development at RBC (1:05) Aaron discusses transitioning to developer advocacy (12:25) Aaron identifies successes he had in his early days of developer advocacy (20:35) Jason asks what it looks like to assist developers in achieving completion with long term maintenance projects, or “sustainable development” (25:40)  Jason and Aaron discuss what “innersource” is and why it's valuable in an organization (29:29) Aaron answers the question “how do you keep skills and knowledge up to date?” (33:55) Aaron talks about job opportunities at RBC (38:55) Links Referenced: Royal Bank of Canada: https://www.rbcroyalbank.com Opportunities at RBC: https://jobs.rbc.com/ca/en TranscriptAaron: And I guess some PM asked my boss, “So, Aaron doesn't come to our platform status meetings, he doesn't really take tickets, and he doesn't take support rotation. What does Aaron do for the Cloud Platform Team?”Jason: [laugh].Jason: Welcome to Break Things on Purpose, a podcast about reliability, learning, and building better systems. In this episode, we talk with Aaron Clark, Director of Developer Advocacy at the Royal Bank of Canada. We chat with him about his journey from developer to advocate, the power of applying open-source principles within organizations—known as innersource—and his advice to keep learning.Jason: Welcome to the show, Aaron.Aaron: Thanks for having me, Jason. My name is Aaron Clark. I'm a developer advocate for cloud at RBC. That is the Royal Bank of Canada. And I've been at the bank for… well, since February 2010.Jason: So, when you first joined the bank, you were not a developer advocate, though?Aaron: Right. So, I have been in my current role since 2019. I've been part of the cloud program since 2017. Way back in 2010, I joined as a Java developer. So, my background in terms of being a developer is pretty much heavy on Java. Java and Spring Boot, now.I joined working on a bunch of Java applications within one of the many functions areas within the Royal Bank. The bank is gigantic. That's kind of one of the things people sometimes struggle to grasp. It's such a large organization. We're something like 100,000… yeah, 100,000 employees, around 10,000 of that is in technology, so developers, developer adjacent roles like business analysts, and QE, and operations and support, and all of those roles.It's a big organization. And that's one of the interesting things to kind of grapple with when you join the organization. So, I joined in a group called Risk IT. We built solely internal-facing applications. I worked on a bunch of stuff in there.I'm kind of a generalist, where I have interest in all the DevOps things. I set up one of the very first Hudson servers in Risk—well, in the bank, but specifically in Risk—and I admin'ed it on the side because nobody else was doing it and it needed doing. After a few years of doing that and working on a bunch of different projects, I was occasionally just, “We need this project to succeed, to have a good foundation at the start, so Aaron, you're on this project for six months and then you're doing something different.” Which was really interesting. At the same time, I always worry about the problem where if you don't stay on something for very long, you never learn the consequences of the poor decisions you may have made because you don't have to deal with it.Jason: [laugh].Aaron: And that was like the flip side of, I hope I'm making good decisions here. It seemed to be pretty good, people seemed happy with it, but I always worry about that. Like, being in a role for a few years where you build something, and then it's in production, and you're running it and you're dealing with, “Oh, I made this decision that seems like a good idea at the time. Turns out that's a bad idea. Don't do that next time.” You never learned that if you don't stay in a role.When I was overall in Risk IT for four, almost five years, so I would work with a bunch of the teams who maybe stayed on this project, they'd come ask me questions. It's like, I'm not gone gone. I'm just not working on that project for the next few months or whatever. And then I moved into another part of the organization, like, a sister group called Finance IT that runs kind of the—builds and runs the general ledger for the bank. Or at least for a part of capital markets.It gets fuzzy as the organization moves around. And groups combine and disperse and things like that. That group, I actually had some interesting stuff that was when I started working on more things like cloud, looking at cloud, the bank was starting to bring in cloud. So, I was still on the application development side, but I was interested in it. I had been to some conferences like OSCON, and started to hear about and learn about things like Docker, things like Kubernetes, things like Spring Boot, and I was like this is some really neat stuff.I was working on a Spark-based ETL system, on one of the early Hadoop clusters at the bank. So, I've been I'm like, super, super lucky that I got to do a lot of this stuff, work on all of these new things when they were really nascent within the organization. I've also had really supportive leadership. So, like, I was doing—that continuous integration server, that was totally on the side; I got involved in a bunch of reuse ideas of, we have this larger group; we're doing a lot of similar things; let's share some of the libraries and things like that. That was before being any, like, developer advocate or anything like that I was working on these.And I was actually funded for a year to promote and work on reuse activities, basically. And that was—I learned a lot, I made a lot of mistakes that I now, like, inform some of the decisions I make in my current role, but I was doing all of this, and I almost described it as I kind of taxed my existing project because I'm working on this team, but I have this side thing that I have to do. And I might need to take a morning and not work on your project because I have to, like, maintain this build machine for somebody. And I had really supportive leadership. They were great.They recognize the value of these activities, and didn't really argue about the fact that I was taking time away from whatever the budget said I was supposed to be doing, which was really good. So, I started doing that, and I was working in finance as the Cloud Team was starting to go through a revamp—the initial nascent Cloud Team at the bank—and I was doing cloud things from the app dev side, but at the same time within my group, anytime something surprising became broken, somebody had some emergency that they needed somebody to drop in and be clever and solve things, that person became me. And I was running into a lot of distractions in that sense. And it's nice to be the person who gets to work on, “Oh, this thing needs rescuing. Help us, Aaron.”That's fantastic; it feels really good, right, up until you're spending a lot of your time doing it and you can't do the things that you're really interested in. So, I actually decided to move over to the Cloud Team and work on kind of defining how we build applications for the cloud, which was really—it was a really good time. It was a really early time in the bank, so nobody really knew how we were going to build applications, how we were going to put them on the cloud, what does that structure look like? I got to do a lot of reading and research and learning from other people. One of the key things about, like, a really large organization that's a little slow-moving like the bank and is a little bit risk-averse in terms of technology choices, people always act like that's always a bad thing.And sometimes it is because we're sometimes not adopting things that we would really get a lot of benefit out of, but the other side of it is, by the time we get to a lot of these technologies and platforms, a bunch of the sharp edges have kind of been sanded off. Like, the Facebooks and the Twitters of the world, they've adopted it and they've discovered all of these problems and been, like, duct-taping them together. And they've kind of found, “Oh, we need to have actual, like, security built into this system,” or things like that, and they've dealt with it. So, by the time we get to it, some of those issues are just not there anymore. We don't have to deal with them.Which is an underrated positive of being in a more conservative organization around that. So, we were figuring there's a lot of things we could learn from. When we were looking at microservices and, kind of, Spring Boot Spring Cloud, the initial cloud parts that had been brought into the organization were mainly around Cloud Foundry. And we were helping some initial app teams build their applications, which we probably over-engineered some of those applications, in the sense that we were proving out patterns that you didn't desperately need for building those applications. Like, you could have probably just done it with a web app and relational database and it would have been fine.But we were proving out some of the patterns of how do you build something for broader scale with microservices and things like that. We learned a bunch about the complexities of doing that too early, but we also learned a bunch about how to do this so we could teach other application teams. And that's kind of the group that I became part of, where I wasn't a platform operator on the cloud, but I was working with dev teams, building things with dev teams to help them learn how to build stuff for cloud. And this was my first real exposure to that scope and scale of the bank. I'd been in the smaller groups and one of the things that you start to encounter when you start to interact with the larger parts of the bank is just, kind of, how many silos there are, how diverse the tech stacks are in an organization of that size.Like, we have areas that do things with Java, we have areas doing things with .NET Framework, we have areas doing lots of Python, we have areas doing lots of Node, especially as the organization started building more web applications. While you're building things with Angular and using npm for the front-end, so you're building stuff on the back-end with Node as well. Whether that is a good technology choice, a lot of the time you're building with what you have. Even within Java, we'd have teams building with Spring Boot, and lots of groups doing that, but someone else is interested in Google Guice, so they're building—instead of Spring, they're using Google Guice as their dependency injection framework.Or they have a… like, there's the mainframe, right? You have this huge technology stack where lots of people are building Java EE applications still and trying to evolve that from the old grungy days of Java EE to the much nicer modern ways of it. And some of the technology conversations are things like, “Well, you can use this other technology; that's fine, but if you're using that, and we're using something else over here, we can't help each other. When I solve a problem, I can't really help solve it for you as well. You have to solve it for yourself with your framework.”I talked to a team once using Vertex in Java, and I asked them, “Why are you using Vertex?” And they said, “Well, that's what our team knew.” I was like, “That's a good technology choice in the sense that we have to deliver. This is what we know, so this is the thing we know we can succeed with rather than actually learning something new on the job while trying to deliver something.” That's often a recipe for challenges if not outright failure.Jason: Yeah. So, it sounds like that's kind of where you come in; if all these teams are doing very disparate things, right—Aaron: Mm-hm.Jason: That's both good and bad, right? That's the whole point of microservices is independent teams, everyone's decoupled, more velocity. But also, there's huge advantages—especially in an org the size of RBC—to leverage some of the learnings from one team to another, and really, like, start to share these best practices. I'm guessing that's where you come into play now in your current role.Aaron: Yeah. And that's the part where how do we have the flexibility for people to make their own choices while standardizing so we don't have this enormous sprawl, so we can build on things? And this is starting to kind of where I started really getting involved in community stuff and doing developer advocacy. And part of how this actually happened—and this is another one of those cases where I've been very fortunate and I've had great leaders—I was working as part of the Cloud Platform Team, the Special Projects group that I was, a couple of people left; I was the last one left. It's like, “Well, you can't be your own department, so you're part of Cloud Platform.” But I'm not an operator. I don't take a support rotation.And I'm ostensibly building tooling, but I'm mostly doing innersource. This is where the innersource community started to spin up at RBC. I was one of the, kind of, founding members of the innersource community and getting that going. We had built a bunch of libraries for cloud, so those were some of the first projects into innersource where I was maintaining the library for Java and Spring using OIDC. And this is kind of predating Spring Security's native support for OIDC—so Open ID Connect—And I was doing a lot of that, I was supporting app teams who were trying to adopt that library, I was involved in some of the other early developer experience things around, you complain this thing is bad as the developer; why do we have to do this? You get invited to one of the VP's regular weekly meetings to discuss, and now you're busy trying to fix, kind of, parts of the developer experience. I was doing this, and I guess some PM asked my boss, “So, Aaron doesn't come to our platform status meetings, he doesn't really take tickets, and he doesn't take support rotation. What does Aaron do for the Cloud Platform Team?”Jason: [laugh].Aaron: And my boss was like, “Well, Aaron's got a lot of these other things that he's involved with that are really valuable.” One of the other things I was doing at this point was I was hosting the Tech Talk speaking series, which is kind of an internal conference-style talks where we get an expert from within the organization and we try to cross those silos where we find someone who's a machine-learning expert; come and explain how TensorFlow works. Come and explain how Spark works, why it's awesome. And we get those experts to come and do presentations internally for RBC-ers. And I was doing that and doing all of the support work for running that event series with the co-organizers that we had.And at the end of the year, when they were starting up a new initiative to really focus on how do we start promoting cloud adoption rather than just people arrive at the platform and start using it and figure it out for themselves—you can only get so far with that—my boss sits me down. He says. “So, we really like all the things that you've been doing, all of these community things and things like that, so we're going to make that your job now.” And this is how I arrived at there. It's not like I applied to be a developer advocate. I was doing all of these things on the side and all of a sudden, 75% of my time was all of these side projects, and that became my job.So, it's not really the most replicable, like, career path, but it is one of those things where, like, getting involved in stuff is a great way to find a niche that is the things that you're passionate about. So, I changed my title. You can do that in some of our systems as long as your manager approves it, so I changed my title from the very generic ‘Senior Technical Systems Analyst—which, who knows what I actually do when that's my title—and I changed that to ‘Developer Advocate.' And that was when I started doing more research learning about what do actual developer advocates do because I want to be a developer advocate. I want to say I'm a developer advocate.For the longest time in the organization, I'm the only person in the company with that title, which is interesting because then nobody knows what to do with me because I'm not like—am I, like—I'm not a director, I'm not a VP. Like… but I'm not just a regular developer, either. Where—I don't fit in the hierarchy. Which is good because then people stop getting worried about what what are titles and things like that, and they just listen to what I say. So, I do, like, design consultations with dev teams, making sure that they knew what they were doing, or were aware of a bunch of the pitfalls when they started to get onto the cloud.I would build a lot of samples, a lot of docs, do a lot of the community engagement, so going to events internally that we'd have, doing a lot of those kinds of things. A lot of the innersource stuff I was already doing—the speaking series—but now it was my job formally, and it helped me cross a lot of those silos and work very horizontally. That's one of the different parts about my job versus a regular developer, is it's my job to cover anything to do with cloud—that at least, that I find interesting, or that my boss tells me I need to work at—and anything anywhere in the organization that touches. So, a dev team doing something with Kubernetes, I can go and talk to them. If they're building something in capital markets that might be useful, I can say, “Hey, can you share this into innersource so that other people can build on this work as well?”And that was really great because I develop all of these relationships with all of these other groups. And that was, to a degree, what the cloud program needed from me as well at that beginning. I explained that this was now my job to one of my friends. And they're like, “That sounds like the perfect job for you because you are technical, but you're really good with people.” I was like, “Am I? I guess I am now that I've been doing it for this amount of time.”And the other part of it as we've gone on more and more is because I talk to all of these development teams, I am not siloed in, I'm not as tunneled on the specific thing I'm working with, and now I can talk to the platform teams and really represent the application developer perspective. Because I'm not building the platform. And they have their priorities, and they have things that they have to worry about; I don't have to deal with that. My job is to bring the perspective of an application developer. That's my background.I'm not an operator; I don't care about the support rotation, I don't care about a bunch of the niggly things and toil of the platform. It's my job, sometimes, to say, hey, this documentation is well-intentioned. I understand how you arrived at this documentation from the perspective of being the platform team and the things that you prioritize and want to explain to people, but as an application developer, none of the information that I need to build something to run on your platform is presented in a manner that I am able to consume. So, I do, like, that side as well of providing customer feedback to the platform saying, “This thing is hard,” or, “This thing that you are asking the application teams to work on, they don't want to care about that. They shouldn't have to care about this thing.” And that sort of stuff.So, I ended up being this human router are sometimes where platform teams will say, “Do you know anybody who's doing this, who's using this thing?” Or finding one app team and say, “You should talk to that group over there because they are also doing the same thing, or they're struggling with the same thing, and you should collaborate.” Or, “They have solved this problem.” Because I don't know every single programming language we use, I don't know all of the frameworks, but I know who I asked for Python questions, and I will send teams to that person. And part of that, then, as I started doing this community work was actually building community.One of the great successes was, we have a Slack channel called ‘Cloud Adoption.' And that was the place where everybody goes to ask their questions about how do I do this thing to put something on Cloud Foundry, put it on Kubernetes? How do I do this? I don't understand. And that was sometimes my whole day was just going onto that Slack channel, answering questions, and being very helpful and trying to document things, trying to get a feel for what people were doing.It was my whole day, sometimes. It took a while to get used to that was actually, like, a successful day coming from a developer background. I'm used to building things, so I feel like success because I built something I can show you, that I did this today. And then I'd have days where I talked to a bunch of people and I don't have anything I can show you. That was, like, the hard part of taking on this role.But one of the big successes was we built this community where it wasn't just me. Other people who wanted to help people, who were just developers on different dev teams, they'd see me ask questions or answer questions, and they would then know the answers and they'd chime in. And as I started being tasked with more and more other activities, I would then get to go—I'd come back to Slack and see oh, there's a bunch of questions. Oh, it turns out, people are able to help themselves. And that was—like that's success from that standpoint of building community.And now that I've done that a couple times with Tech Talks, with some of the developer experience work, some of the cloud adoption work, I get asked internally how do you build community when we're starting up new communities around things like Site Reliability Engineering. How are we going to do that? So, I get—and that feels weird, but that's one of the things that I have been doing now. And as—like, this is a gigantic role because of all of the scope. I can touch anything with anyone in cloud.One of the scope things with the role, but also with the bank is not only do we have all these tech stacks, but we also have this really, really diverse set of technical acumen, where you have people who are experts already on Kubernetes. They will succeed no matter what I do. They'll figure it out because they're that type of personality, they're going to find all the information. If anything, some of the restrictions that we put in place to manage our environments and secure them because of the risk requirements and compliance requirements of being a regulated bank, those will get in the way. Sometimes I'm explaining why those things are there. Sometimes I'm agreeing with people. “Yeah, it sucks. I don't want to have to do this.”But at the same time, you'll have people who they just want to come in, write their code, go home. They don't want to think about technology other than that. They're not going to go and learn things on their own necessarily. And that's not the end of the world. As strange as that sounds to people who are the personality to be constantly learning and constantly getting into everything and tinkering, like, that's me too, but you still need people to keep the lights on, to do all of the other work as well. And people who are happy just doing that, that's also valuable.Because if I was in that role, I would not be happy. And someone who is happy, like, this is good for the overall organization. But the things that they need to learn, the things they need explained to them, the help they need for success is different. So, that's one of the challenges is figuring out how do you address all of those customers? And sometimes even the answer for those customers is—and this is one of the things about my role—it's like the definition is customer success.If the application you're trying to put on cloud should not go on cloud, it is my job to tell you not to put it on cloud. It is not my job to put you on cloud. I want you to succeed, not just to get there. I can get your thing on the cloud in an afternoon, probably, but if I then walk away and it breaks, like, you don't know what to do. So, a lot of the things around how do we teach people to self-serve, how do we make our internal systems more self-serve, those are kind of the things that I look at now.How do I manage my own time because the scope is so big? It's like, I need to figure out where I'm not moving a thousand things forward an inch, but I'm moving things to their completion. And I am learning to, while not managing people, still delegate and work with the community, work with the broader cloud platform group around how do I let go and help other people do things?Jason: So, you mentioned something in there that I think is really interesting, right, the goal of helping people get to completion, right? And I think that's such an interesting thing because I think as—in that advocacy role, there's often a notion of just, like, I'm going to help you get unstuck and then you can keep going, without a clear idea of where they're ultimately heading. And that kind of ties back into something that you said earlier about starting out as a developer where you build things and you kind of just, like, set it free, [laugh] and you don't think about, you know, that day two, sort of, operations, the maintenance, the ongoing kind of stuff. So, I'm curious, as you've progressed in your career, as you've gotten more wisdom from helping people out, what does that look like when you're helping people get to completion, also with the mindset of this is an application that's going to be running for quite some time. Even in the short term, you know, if it's a short-term thing, but I feel like with the bank, most things probably are somewhat long-lived. How do you balance that out? How do you approach that, helping people get to done but also keeping in mind that they have to—this app has to keep living and it has to be maintained?Aaron: Yeah, a lot of it is—like, the term we use is sustainable development. And part of that is kind of removing friction, trying to get the developers to a point where they can focus on, I guess, the term that's often used in the industry is their inner loop. And it should come as no surprise, the bank often has a lot of processes that are high in friction. There's a lot of open a ticket, wait for things. This is the part that I take my conversations with dev teams, and I ask them, “What are the things that are hard? What are the things you don't like? What are the things you wish you didn't have to do or care about?”And some of this is reading between the lines when you talk to them; it's not so much interviewing them. Like, any kind of requirements gathering, usually, it's not what they say, it's what they talk about that then you look at, oh, this is the problem; how do we unstuck that problem so that people can get to where they need to be going? And this kind of informs some of my feedback to the systems we put in place, the processes we put in place around the platform, some of the tooling we look at. I really, really love the philosophy from Docker and Solomon Hykes around, “Batteries included but removable.” I want developers to have a high baseline as a starting point.And this comes partly from my experience with Cloud Foundry. Cloud Foundry has a really great out-of-the-box dev experience for lots of things where, “I just have a web app. Just run it. It's Nginx; it's some HTML pages; I don't need to know all the details. Just make it go and give me the URL.”And I want more of that for app teams where they have a high baseline of things to work with as a starting point. And kind of every organization ends up building this, where they have—like, Netflix: Netflix OSS or Twitter with Finagle—where they have, “Here's the surrounding pieces that I want to plug in that everybody gets as a starting point. And how do we provide security? How do we provide all of these pieces that are major concerns for an app team, that they have to do, we know they have to do?” Some of these are things that only start coming up when they're on the cloud and trying to provide a lot more of that for app teams so they can focus on the business stuff and only get into the weeds when they need to.Jason: As you're talking about these frameworks that, you know, having this high quality or this high baseline of tools that people can just have, right, equipping them with a nice toolbox, I'm guessing that the innersource stuff that you're working on also helps contribute to that.Aaron: Oh, immensely. And as we've gone on and as we've matured, our innersource organization, a huge part of that is other groups as well, where they're finding things that—we need this. And they'll put—it originally it was, “We built this. We'll put it into innersource.” But what you get with that is something that is very targeted and specific to their group and maybe someone else can use it, but they can't use it without bending it a little bit.And I hate bending software to fit it. That's one of the things—it's a very common thing in the corporate environment where we have our existing processes and rather than adopting the standard approach that some tool uses, we need to take it and then bend it until it fits our existing process because we don't want to change our processes. And that gets hard because you run into weird edge cases where this is doing something strange because we bent it. And it's like, well, that's not its fault at that point. As we've started doing more innersource, a lot more things have really become innersource first, where groups realize we need to solve this together.Let's start working on it together and let's design the API as a group. And API design is really, really hard. And how do we do things with shared libraries or services. And working through that as a group, we're seeing more of that, and more commonly things where, “Well, this is a thing we're going to need. We're going to start it in innersource, we'll get some people to use it and they'll be our beta customers. And we'll inform it without really specifically targeting an application and an app team's needs.”Because they're all going to have specific needs. And that's where the, like, ‘included but removable' part comes in. How do we build things extensibly where we have the general solution and you can plug in your specifics? And we're still—like, this is not an easy problem. We're still solving it, we're still working through it, we're getting better at it.A lot of it's just how can we improve day-over-day, year-over-year, to make some of these things better? Even our, like, continuous integration and delivery pipelines to our to clouds, all of these things are in constant flux and constant evolution. We're supporting multiple languages; we're supporting multiple versions of different languages; we're talking about, hey, we need to get started adopting Java 17. None of our libraries or pipelines do that yet, but we should probably get on that since it's been out for—what—almost a year? And really working on kind of decomposing some of these things where we built it for what we needed at the time, but now it feels a bit rigid. How do we pull out the pieces?One of the big pushes in the organization after the log4j CVE and things like that broad impact on the industry is we need to do a much more thorough job around software supply chain, around knowing what we have, making sure we have scans happening and everything. And that's where, like, the pipeline work comes in. I'm consulting on the pipeline stuff where I provide a lot of customer feedback; we have a team that is working on that all full time. But doing a lot of those things and trying to build for what we need, but not cut ourselves off from the broader industry, as well. Like, my nightmare situation, from a tooling standpoint, is that we restrict things, we make decisions around security, or policy or something like that, and we cut ourselves off from the broader CNCF tooling ecosystem, we can't use any of those tools. It's like, well, now we have to build something ourselves, or—which we're never going to do it as well as the external community. Or we're going to just kind of have bad processes and no one's going to be happy so figuring out all of that.Jason: Yeah. One of the things that you mentioned about staying up to speed and having those standards reminds me of, you know, similar to that previous experience that I had was, basically, I was at an org where we said that we'd like to open-source and we used open-source and that basically meant that we forked things and then made our own weird modifications to it. And that meant, like, now, it wasn't really open-source; it was like this weird, hacked thing that you had to keep maintaining and trying to keep it up to date with the latest stuff. Sounds like you're in a better spot, but I am curious, in terms of keeping up with the latest stuff, how do you do that, right? Because you mentioned that the bank, obviously a bit slower, adopting more established software, but then there's you, right, where you're out there at the forefront and you're trying to gather best practices and new technologies that you can use at the bank, how do you do that as someone that's not building with the latest, greatest stuff? How do you keep that skills and that knowledge up to date?Aaron: I try to do reading, I try to set time aside to read things like The New Stack, listen to podcasts about technologies. It's a really broad industry; there's only so much I can keep up with. This was always one of the conversations going way back where I would have the conversation with my boss around the business proposition for me going to conferences, and explaining, like, what's the cost to acquire knowledge in an organization? And while we can bring in consultants, or we can hire people in, like, when you hire new people in, they bring in their pre-existing experiences. So, if someone comes in and they know Hadoop, they can provide information and ideas around is this a good problem to solve with Hadoop? Maybe, maybe not.I don't want to bet a project on that if I don't know anything about Hadoop or Kubernetes or… like, using something like Tilt or Skaffold with my tooling. That's one of the things I got from going to conferences, and I actually need to set more time aside to watch the videos now that everything's virtual. Like, not having that dedicated week is a problem where I'm just disconnected and I'm not dealing with anything. When you're at work, even if KubeCon's going on or Microsoft Build, I'm still doing my day-to-day, I'm getting Slack messages, and I'm not feeling like I can just ignore people. I should probably block out more time, but part of how I stay up to date with it.It's really doing a lot of that reading and research, doing conversations like this, like, the DX Buzz that we invited you to where… I explained that event—it's adjacent to internal speakers—I explained that as I was had a backlog of videos from conferences I was not watching, and secretly if I make everybody else come to lunch with me to watch these videos, I have to watch the video because I'm hosting the session to discuss it, and now I will at least watch one a month. And that's turned out to be a really successful thing internally within the organization to spread knowledge, to have conversations with people. And the other part I do, especially on the tooling side, is I still build stuff. As much as, like, I don't code nearly as much as I used to, I bring an application developer perspective, but I'm not writing code every day anymore.Which I always said was going to be the thing that would make me miserable. It's not. I still think about it, and when I do get to write code, I'm always looking for how can I improve this setup? How can I use this tool? Can I try it out? Is this better? Is this smoother for me so I'm not worrying about this thing?And then spreading that information more broadly within the developer experience group, our DevOps teams, our platform teams, talking to those teams about the things that they use. Like, we use Argo CD within one group and I haven't touched it much, but I know they've got lots of expertise, so talking to them. “How do you use this? How is this good for me? How do I make this work? How can I use it, too?”Jason: I think it's been an incredible, [laugh] as you've been chatting, there are so many different tools and technologies that you've mentioned having used or being used at the bank. Which is both—it's interesting as a, like, there's so much going on in the bank; how do you manage it all? But it's also super interesting, I think, because it shows that there's a lot of interest in just finding the right solutions and finding the right tools, and not really being super-strongly married to one particular tool or one set way to do things, which I think is pretty cool. We're coming up towards the end of our time here, so I did want to ask you, before we sign off, Aaron, do you have anything that you'd like to plug, anything you want to promote?Aaron: Yeah, the Cloud Program is hiring a ton. There's lots of job openings on all of our platform teams. There's probably job openings on my Cloud Adoption Team. So, if you think the bank sounds interesting—the bank is very stable; that's always one of the nice things—but the bank… the thing about the bank, I originally joined the bank saying, “Oh, I'll be here two years, and I'll get bored and I'll leave,” and now it's been 12 years and I'm still at the bank. Because I mentioned, like, that scope and scale of the organization, there's always something interesting happening somewhere.So, if you're interested in cloud platform stuff, we've got a huge cloud platform. If you're in—like, you want to do machine-learning, we've got an entire organization. It should come as no surprise, we have lots of data at a bank, and there's a whole organization for all sorts of different things with machine-learning, deep learning, data analytics, big data, stuff like that. Like, if you think that's interesting, and even if you're not specifically in Toronto, Canada, you can probably find an interesting role within the organization if that's something that turns your crank.Jason: Awesome. We'll post links to everything that we've mentioned, which is a ton. But go check us out, gremlin.com/podcast is where you can find the show note for this episode, and we'll have links to everything. Aaron, thank you so much for joining us. It's been a pleasure to have you.Aaron: Thanks so much for having me, Jason. I'm so happy that we got to do this.Jason: For links to all the information mentioned, visit our website at gremlin.com/podcast. If you liked this episode, subscribe to the Break Things on Purpose podcast on Spotify, Apple Podcasts, or your favorite podcast platform. Our theme song is called, “Battle of Pogs” by Komiku, and it's available on loyaltyfreakmusic.com.

S6 E9 Finagle Space Every schedule has this! JZ talks about why every schedule in your life needs this and a new concept brought to her attention. Find our the new concept and why it hit hard especially for this past weekend! BOOM – you don't want to miss this! LISTEN NOW!! #heartsup Get. Your. Dose of The Midweek Muscle Podcast! Listen Now! #heartsup * Check it out! Rate and review on Apple Podcasts, Spotify,or leave a comment on Soundcloud or Castbox or any of the SOCIALS! * What did you think of this week? Let me know -> * jz@themidweekmuscle.com - or - Facebook and Instagram: @themidweekmuscle Twitter: @midweekmuscle

Finagle is a verb that means to obtain something by devious means. Our word of the day was birthed in the 1920s, possibly related to the word ‘fiddle.' It is mostly used in informal contexts. For example: As a highly ambitious young man, Frank was determined to get what he wanted in life — ethically or otherwise. Whatever he couldn't earn, he aimed to finagle.

What is a Creative Director? What do they do?  What do they get paid for?  Where do you get the skills and training and know-how to be one?  Mike Goldberg answers these questions and more. He also talks about his campaigns for Finagle a Bagel and Mentos in Madison, WI.  A fine artist, Goldberg does paintings on pieces of wood, and uses his fingers to rub the oil paint into the wood. His character paintings were the backdrop for this ZOOM conversation and Michelle Zeitlin drew out his kernels of gold over the course of the 90 minute conversation. Here is the edited half hour with tips and tools for success that Goldberg offers with generosity of spirit and his Boston accent.  From his Manhattan Madison Avenue days with the big ad agencies, to the mid size agencies he's enjoyed on the east coast and the creative director positions he has held for start ups in San Francisco, Goldberg is totally transparent about his journey.  Visit his website for his portfolio and contact info: https://crosscutsf.com/contact Michelle Zeitlin is the host and producer of PASSION TO POWER.  http://www.passion-power.com  If you'd like to be on the show, please reach out to morezap@gmail.com.

The nature of technology is to continuously evolve. Each iteration draws on learnings and mistakes of the past. As we move past the cusp of change from monolithic infrastructures to cloud based microservices we are experiencing an evolution of the tooling and monitoring of our applications. We knew how to monitor our servers, network devices and our applications running on our systems, however the shift to microservices required a new infrastructure and with that new ways to automate and monitor it.In the early days at Twitter, William Morgan, worked heavily on their in house tools to monitor their transformation to a microservices infrastructure. One critical tool, called Finagle, was eventually open sourced and became the basis for Linkerd which William and co-founder Oliver Gould eventually dubbed a “Service Mesh”.Linkerd is reminiscent of a monitoring system developed at CloudFoundry leveraging some of Netflix OSS releases as well as the Spring Framework. Without out of the box tools, innovators built what they needed without knowing it was a service mesh.Now with the widespread adoption of service meshes to manage microservices infrastructures, Buoyant has watched Linkerd adoption skyrocket among organizations adopting cloud native technology such as Kubernetes. (Here is an excellent article by William explaining what every Software Engineer needs to know about service meshes.)Tune in for a brilliant discussion on the origins of service mesh, its ecosystem and why it's important for Kubernetes centric infrastructures today.

Hello there and welcome to our wonderful adventure as we invite you to join along with us in this journey as we discover ourselves and each other through silly role play and bad rolls.

The amazing Simone Holtznagel walks off the catwalk and straight onto Fitbet. We chat about her life as a model, the harsh world or reality TV and she enlightens us on some unique ways of keeping skin silky, smooth and soft. Enjoy. See omnystudio.com/listener for privacy information.

В 14 выпуске подкаста Javaswag поговорили с Сергеем Целовальниковым об организации митапа в своем городе, переезде в Австралию и архитектуре Canva.com 00:01:35 О себе 00:02:34 JUG.EKB 00:04:49 Как организовать митап в своем городе? 00:07:53 Проекты для джуниора, Groovy скрипты для кастомизации продукта 00:21:42 Сколько времени уходит на статью в блог? 00:22:53 Чем занимался в JetBrains? 00:23:22 Интересная связка - Java, Clojure, ClojureScript 00:26:28 Магистерская работа в РАН с JetBrains, Cloud IDE 00:28:47 Как переехать в Австралию? Где Сидней? 00:35:30 Canva.com в 2016. Что такое Canva? 00:42:19 Не нужен нам ServiceMesh - https://serce.me/posts/23-07-2020-you-dont-need-no-service-mesh/ 00:43:54 Деплоим даже если нет никаких изменений 00:44:44 Bazel. В чем выгода перехода на Bazel 00:48:42 Почему же не Грейдл? 00:51:49 Монорепа для Java и Javascript 00:52:48 Архитектура, макро-микро сервисы 00:57:36 Finagle, Protobuf-idl 01:05:08 Хранилище 01:10:18 Мониторинг, алерты 01:12:12 Что бы изменил вернувшись в прошлое? Гость - https://twitter.com/SerCeMan Телеграм канал подкаста t.me/javaswag Чат t.me/javaswag_chat

Alyssa Hall is a life coach for mom’s. She’s a single mom to her 4-year-old daughter. A couple of years ago her life was a complete mess - every part of her life felt hard; her job, her relationships, and taking care of her self. She didn’t know how much more she could take —so she took a risk. She signed up for the coach training program at iPEC (Institute for Professional Excellence in Coaching). She knew it wasn’t a good time, but that there would also never be a “perfect” time. She knew she couldn’t afford it. But also knew she was tired of being unhappy. So, she stepped into her fears of the unknown seeking a career change and left with a completely different life. Alyssa was able to see firsthand how changing herself can affect every single person in your life. When she completed the program, she had a mission. She needed to help mom’s overcome what I went through; all the overwhelm, guilt, frustration, communicating with her daughter's father, and more. She knew she wasn’t the only one who experienced life this way and was grateful to coaching tools early in her parenting journey. Segment Time Stamps/ Episode Highlights: 00:00 Discussed the biggest shift that happened when she became a mother. Initially, she thought nothing was going to change because she wasn’t a busy person. Eventually, she realized that everything she was doing was being seen and reflected and that being a parent was beyond babysitting. 03:46 Discussed how she managed guilt. Alyssa realized that her child mirrors her actions. She takes mental notes to observe her behavior and shifts it to be more conscious of her actions. 06:40 An important lesson she learned was to try not to take parenting so seriously. “Realize that we won’t be perfect at it.” 08:50 Did her perspective of her parents changed once she became a mother? Yes, and she hates to admit it. She understands her mother as a parent, especially as a single parent. 10:59 Did having a child change her relationship with her mom? It did, it made her be diligent about setting boundaries. She also started to make herself a priority. What’s her experience with mom guilt and how does she manage it? The most type of guilt she experienced was spousal guilt. She felt like she needed to be the perfect spouse, she didn’t want to burden her partner with the baby for too long. 20:03 Does she see similar challenges in other moms she coaches? She sees two different types of mothers. One type of mother is unhappy because she forgot what made her happy as a person because she is so consumed with parenting. The other type of mother knows what would make her happy but the guilt of being away from her family stops her from pursuing it. 21:54 How and when did she start her business while being a single mom? Her daughter was about a year old; she heard about coaching and knew that this was something she wanted to do. For an entire year, all she could think about was coaching while she did misc. jobs. She eventually signed up for the program and committed to it despite never thinking about having her own business prior to this. Day 3 of the program she broke up with her partner and her commitment became even more serious because she had more of a financial burden. But she knew she couldn’t go back to doing what she was doing. “It’s easier to work for someone else than it is to work for yourself and push yourself.” Daily, she reminds herself why she is coaching. 25:35 What happened just before she made the switch to the program. She was in a “perfect” yet toxic job where she worked 4, 10-hour days a week. Simultaneously she was studying to be a therapist. She took a year off to coach. Between her job, and her relationship she was at a breaking point that caused her to make a shift. 28:00 What did she learn in those two days that showed her she could do it? The beginning felt like an intervention. She thought she was going to just learn how to be a coach but the start of the program was about digging deep and learning how she was showing up in the world. How her actions lead her to the results that were currently occurring. 29:01 What did she do to realize how she was showing up in the world? The thing that they taught them was how to communicate with people. And how to communicate in a curious nonjudgmental way. Since she isn’t a mean-spirited person it was hard for her to accept those truths.) 35:46 What’s an important value you want to teach your daughter and how do you plan to teach it? She wants her to really have confidence. So, she works on it daily and tries to lead by example. 38:00 How does she deal with her body post-baby. She was never happy with her body ever. When she was pregnant, she was happy because she had a reason to have a belly. She is currently building up that confidence again. She started to buy clothes that fit, and follow body positive models on social media. 45:00 What’s the best advice she’s been given? Doing the things that you want to do and not holding yourself back. Quotes: “Children are a mirror, every action that I’m doing is being seen and reflected.” “Finagle the bagel. Which means finesse everything so you can still get everything you want done.” “It’s important to do what makes you happy not what people think you should be doing.” “Remind yourself who you are at your core and fit that into your life… like a constant refresher.” “It’s easier to work for someone else than it is to work for yourself and push yourself.” Relevant Links: http://alyssahall.com/ https://www.instagram.com/alythelifecoach/ https://www.facebook.com/alyssahallcoaching/

Eric Anderson (@ericmander) and Matt Klein (@mattklein123) discuss the beginnings of Envoy Proxy, an open source project now governed by the CNCF. Matt is a software engineer at Lyft and creator of the project. During the conversation Matt mentions Finagle, NginX, Hystrix, HA Proxy and Istio. This conversation was recorded several months prior to being published.

On this first episode, we discuss:The Eagles first victory of the seasonAntonio Brown's weekend dramaProjections for Top 5 NFC and AFC teams at season's endA little Fantasy Football talk andMike's MinutesWe hope you enjoy the show...- Mike and Taylor

In this episode of THE SHENANIGANS podcast, Tristan and Drew have just a random good ole time talking about everything from rabbits, potatoes, Batman, robin, comics, Uncharted, stories, and MUCH MORE! Have fun, and enjoy the nonsense in Episode 34

In this episode of THE SHENANIGANS podcast, Tristan and Drew have just a random good ole time talking about everything from rabbits, potatoes, Batman, robin, comics, Uncharted, stories, and MUCH MORE! Have fun, and enjoy the nonsense in Episode 34! Boehm!

The boys discuss what they've been up to the past two weeks, puberty, and other sex related things.

The Envoy proxy, a universal data plane for Cloud Native, has just graduated as the third top-level project in the CNCF. Craig and Adam talk to its author, Matt Klein from Lyft, about modern load balancing for microservices and pragmatically avoiding “second system” syndrome. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod News of the week CVE-2018-1002105: proxy request handling in kube-apiserver can leave vulnerable TCP connections Gravitational write up Proof of concept More cryptocurrency mining with exploited Kubernetes clusters Microsoft Connect(); AKS virtual nodes are in preview Virtual Kubelet joins CNCF GPU support for ACI ACS to be retired in favour of AKS Cloud Native Application Bundle Microsoft and Docker introduce Cloud Native Application Bundle CNAB spec Duffle DockerCon EU 2018: Docker releases Compose operator for Kubernetes Available on GitHub Docker Desktop Enterprise Hashicorp Vault 1.0 Upbound introduce Crossplane Available on GitHub GitLab moving to GKE Rook 0.9.0 — available you-guessed-where MicroK8s from Canonical: Announc4t Project p2e Available on G5b Links from the interview Envoy Recently graduated to top-level project at the CNCF Built at Lyft Replaces libraries like Finagle and Hystrix Introduction to modern network load balancing and proxying Envoy contributors Istio, built on Envoy Turning down the VC money: Why Matt isn’t starting an Envoy company Service mesh data plane vs. control plane Matt Klein on Twitter Matt’s blog

In this episode is all over the place and pretty confusing probably as the guys talk Jay-Z and Beyonce, Generational Wealth, Azelia Banks crying on Wild 'N Out and More. West Coast Throwback Album of the Week comes from Nick: Souls of Mischief- 93' Til Infinity Question of the Week: Best Fight Songs Music: 1. PC The Real- In My Zone 2. Lah-Kid- LongxLivexOurDreams 3. Tay Gutta- Where I Come From... RIP

|00:07:05| интервью с Олегом |00:11:48| команда |00:21:08| кассандра |00:47:51| DeGoes There Can Be Only One IO Monad |00:57:54| SIP-ZZ newtypes for Scala https://docs.scala-lang.org/sips/opaque-types.html https://contributors.scala-lang.org/t/pre-sip-unboxed-wrapper-types/987 |01:15:49| ensime looking for maintainer http://ensime.org/maintainer/ https://www.reddit.com/r/scala/comments/71pphu/newmaintainerneeded_ensime/ |01:22:18| Http4s 0.17.2 Http4s. 0.17.2 |01:27:05| Streams, effects and beautiful folds, a winning trilogy by Eric Torreborre |01:32:57| Lambda Cast - подкаст про понимание FP https://soundcloud.com/lambda-cast https://itunes.apple.com/ru/podcast/lambdacast/id1133087254?l=en&mt=2 |01:36:28| high sierra, brew, sbt 1.0 |01:39:00| Finagle 7.1 |01:46:25| Scala OSS twitter - scala oss |01:47:47| http://snacktrace.com Поиск артифактов по имени класса |01:52:03| Type classes as GoF's facade and abstract factory https://github.com/typelevel/general/issues/81 https://github.com/ThoughtWorksInc/DesignPattern.scala covariant.scala Голоса выпуска: Евгений Токарев, Алексей Романчук, Вадим Челышов, Олег Нижников (o.nizhnikov@tinkoff.ru)

[00:00:46] - Вопросы - Путь в отрасль и за жизнь. [00:23:14] - Вопросы - Конференции scala matsuri, scala days, typelevel summit, scalawave. [00:39:53] - Вопросы - Аэроспайк и скала. [00:53:01] - Вопросы - Макросы [01:18:51] - Вопросы - Shapeless. [01:23:25] - Вопросы - SoftSkills, TeamWork. [01:33:32] - http4s v0.17.0-RC1 is now available, built on fs2 and cats. [01:34:35] - Gigahorse. [01:36:47] - Functional Programming in Scala is now a part of Scala Exercises [01:37:50] - Twitter announces Reasonable Scala compiler [01:42:51] - Vladimir Pavkin - Multiple faces of Scala Iterator trap [01:45:09] - cats infographics updated for cats 1.0 [01:45:48] - Finagle v7 is out: now without a Netty 3 dependency! Голоса выпуска: Марина Сигаева, Вадим Челышов, Евгений Токарев

Jean Barmash is Director of Engineering at Compass, Founder & Co-Organizer, NYC CTO School Meetup. Live in New York City. He has over 15 years of experience in software industry, and has been part of 4 startups over the last seven years, 3 as CTO / VPE and one of which he co-founded. Prior to his entrepreneurial adventures, Jean held a variety of progressively senior roles in development, integration consulting, training, and team leadership. He worked for such companies as Trilogy, Symantec, Infusion and Alfresco, consulting to Fortune 100 companies like Ford, Toyota, Microsoft, Adobe, IHG, Citi, BofA, NBC, and Booz Allen Hamilton. Jean will speak at QCon New York 2017: http://bit.ly/2nN7KKo Why listen to this podcast: - The Compass backend is mostly written in Java and Python, with Go increasingly a first class language. The main reason for Go being added was developer productivity. - The app is based on a Microservices architecture with around 40-50 services in total. - Binary RPC, originally Thrift and Finagle, is used as the communication protocol, but the company is gradually moving to gRPC still with Thrift. One advantage that gRPC offers is better Python support than Finagle. - The company has built a code generation framework which takes Thrift and converts it to a RESTful API for clients to consume. - Constraint theory is about how you manage the one constraint in a system or team that prevent you increasing throughput; for example if your software engineering team only has one front end engineer do you ask back-end engineers to pick off some front-end tasks, or bring in a contractor. Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

The Grammy's? What in tarnation?! Phoenix doesn't wanna go off on a rant, but he does. Eminem' albums don't age well, but then again neither does milk. Big Ben D.C. news causes us to try and reshape the universe. Please use the hashtag #PhoenixRevampsDC. Also our usual video game jargon, all this and less on this latest episode. Enjoy. Finagle.      Don't forget to drop us an email with any questions or comments here: PhoenixPodcast404@gmail.com   Maybe send us some harsh love or sweet hate on our voicemail: 678-753-5144   Follow the Podcast on Twitter: @PhoenixPodcast    Follow our personal Twitters:  @king_phoenix410   @Polo_Papi  @ChrisCreamster    For more from Randumb Gaming Bros please don't hesitate to like, share, & subscribe here: https://youtube.com/channel/UCrEjIIRTEnA9KvD0Yij-4mA   Follow the gaming channel Twitter: @RandumbGamingBs

Peter Bourgon discusses his work at Weaveworks, discovering and imlemeting CRDTs for time-stamped events at Soundcloud, Microservices in Go with Go Kit and the state of package management in Go. Why listen to this podcast: - We’ve hit the limits of Moore’s law so when we want to scale we have to think about how we do communication across unreliable links between unreliable machines. - In an AP algorithm like Gossip you still make forward progress in case of a failure. In Paxos you stop and return failures. - CRDTs give us a rigours set of rules to accommodate failures for maps, sets etc. in communication that result in am eventually consistent system. - Go is optimised to readers/maintainers vs. making the programmers’ life easier. Go is closer to C than Java in that it allows you to layout memory very precisely, allowing you to, for example, optimise cache lines in your CPU. - Bourgon started a project called Go Kit, which is designed for building microservices in Go. It takes inspiration from Tiwtter’s Scala-based Finagle which solved a lot of Micoservice concerns. - Go has a number of community-maintained package managers but no good solution; work in ongoing to try and resolve this. Notes and links can be found on: http://bit.ly/2kaHC9k Work at Weaveworks Gossip vs. Paxos CRDTs at SoundCloud Go Go in large teams Go and Java package management Microservices in Go with Go Kit Logging and tracing in a distributed environment More on this: Quick scan our curated show notes on InfoQ. http://bit.ly/2kaHC9k You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Teve a época do Corba, do COM, passamos para webservices com SOAP, WSDL até chegar ao Rest... é muita letrinha nesse cenário de sistemas distribuídos. A bola da vez são os microserviços. Vamos conversar com Phil Calçado, que sempre esteve muito presente no GUJ e em palestras no mundo inteiro, sobre arquiteturas distribuídas e de como chegamos, vantagens, desvantagens e como adotar uma arquitetura de microserviços. Participantes: Paulo Silveira, host do hipsters, que queria ter escrito MicroSServiços para seguir a nova gramática Mauricio Linhares, o cohost que chamou o chefe para o episódio Phil Calçado, vulgo Phillip, diretor de engenharia na Digital Ocean em Nova York Links citados no episódio: Como terminamos usando microserviços? (inglês) - Phil Calçado em inglês sobre o Soundcloud Artigo do Martin Fowler sobre Microserviços (inglês) Monolitos e Microserviços, no blog da Caelum Ferramentas como Finagle, Kubernetes, Prometheus, Thrift Lançamento do Livro do Phil Calçado: Fragmentos de um Programador Curso de micro serviços com Java e Spring Curso de docker Produção e conteúdo: Alura Cursos online de Tecnologia - https://www.alura.com.br === Caelum Ensino e Inovação Edição e sonorização: Radiofobia Podcast e Multimídia

Teve a época do Corba, do COM, passamos para webservices com SOAP, WSDL até chegar ao Rest... é muita letrinha nesse cenário de sistemas distribuídos. A bola da vez são os microserviços. Vamos conversar com Phil Calçado, que sempre esteve muito presente no GUJ e em palestras no mundo inteiro, sobre arquiteturas distribuídas e de como chegamos, vantagens, desvantagens e como adotar uma arquitetura de microserviços. Participantes: Paulo Silveira, host do hipsters, que queria ter escrito MicroSServiços para seguir a nova gramática Mauricio Linhares, o cohost que chamou o chefe para o episódio Phil Calçado, vulgo Phillip, diretor de engenharia na Digital Ocean em Nova York Links citados no episódio: Como terminamos usando microserviços? (inglês) - Phil Calçado em inglês sobre o Soundcloud Artigo do Martin Fowler sobre Microserviços (inglês) Monolitos e Microserviços, no blog da Caelum Ferramentas como Finagle, Kubernetes, Prometheus, Thrift Lançamento do Livro do Phil Calçado: Fragmentos de um Programador Curso de micro serviços com Java e Spring Curso de docker Produção e conteúdo: Alura Cursos online de Tecnologia - https://www.alura.com.br === Caelum Ensino e Inovação Edição e sonorização: Radiofobia Podcast e Multimídia

Teve a época do Corba, do COM, passamos para webservices com SOAP, WSDL até chegar ao Rest... é muita letrinha nesse cenário de sistemas distribuídos. A bola da vez são os microserviços. Vamos conversar com Phil Calçado, que sempre esteve muito presente no GUJ e em palestras no mundo inteiro, sobre arquiteturas distribuídas e de como chegamos, vantagens, desvantagens e como adotar uma arquitetura de microserviços. Participantes: Paulo Silveira, host do hipsters, que queria ter escrito MicroSServiços para seguir a nova gramática Mauricio Linhares, o cohost que chamou o chefe para o episódio Phil Calçado, vulgo Phillip, diretor de engenharia na Digital Ocean em Nova York Links citados no episódio: Como terminamos usando microserviços? (inglês) - Phil Calçado em inglês sobre o Soundcloud Artigo do Martin Fowler sobre Microserviços (inglês) Monolitos e Microserviços, no blog da Caelum Ferramentas como Finagle, Kubernetes, Prometheus, Thrift Lançamento do Livro do Phil Calçado: Fragmentos de um Programador Curso de micro serviços com Java e Spring Curso de docker Produção e conteúdo: Alura Cursos online de Tecnologia - https://www.alura.com.br === Caelum Ensino e Inovação Edição e sonorização: Radiofobia Podcast e Multimídia

This week, our Indigenous current affairs roundtable unpacks recent revelations that, despite federal bureaucrats saying the cupboard for First Nations education funding was full, the Liberals deliberately chose to delay a large chunk of it until after the next election. And, we’ll share our thoughts on an alarming report out of BC that shows First Nations kids in custody suffer alarming rates of sexual abuse. Joining us once again are Colleen Simard and Conrad Prince. // Our theme is 'nesting' by birocratic.  

Rufus T. Rufus is back to hassle everyone at the Bumperpodcast – and Natty Bumpercar is a bit down – right up until Doodle Poodle shows up with a plan! Do you plan? Let us know by sending an email to bumperpodcast@nattybumpercar.com. The post Bumperpodcast #234 – The farce is a finagle! appeared first on Natty Bumpercar.

Naoya Ito さんをゲストに迎えて、Reactive System, Elixir, 技術顧問などについて話しました。 (8/19 日経カンファレンスルームにて収録) スポンサー: 日本経済新聞 電子版 Show Notes Reactive System Meetup in 西新宿 The Reactive Manifesto Build Reactive Applications on the JVM | @typesafe Akka Finagle WEB+DB PRESS Vol.88 Elixir Conf 2014 - Opening Keynote: Think Different Elixir のパターンマッチを攻略しよう Phoenix Thoughts on Elixir? : haskell Elixir, Mithril, Phoenix - in 2015, web development has become Final Fantasy Hack The NIKKEI 日経電子版インターンサイト ★ 日経電子版アプリ内製開発の舞台裏 技術顧問というお仕事 - YAPC::Asia Tokyo 2015 CTO不在で、開発組織改善に着手！ 一休のエンジニアが語る苦悩の1年

Hajime Morrita さんをゲストに迎えて、WebKit, Chrome, WebView, リファクタリング, Rx などについて話しました。 Show Notes PushBullet Rebuild channel steps to phantasien WebKit Quest Blink - The Chromium Projects WebComponents.org Shadow DOM 101 - HTML5 Rocks Service Workers A Beginner's Guide to Using the Application Cache - HTML5 Rocks Google Gears Background Pages - Google Chrome Safari Push Notifications - Apple Developer Android 4.4+ KitKat ships without browser app. OEMs have to license Chrome or build their own Lollipop unwrapped: Chromium WebView will update via Google Play WKWebView Class Reference Link Bubble - mobile browsing done right Javelin browser 書類仕事を追いかけて Inside Google's culture of relentless self-surveying リファクタリング The reactive manifesto Akka JavaScript Promises: There and back again - HTML5 Rocks Finagle Reactive Extensions ReactiveX/RxJava ReactiveX ReactiveCocoa for a better world ReactiveX/RxAndroid Netflix JavaScript Talks - Async JavaScript with Reactive Extensions #10 node.js sideshow | mozaic.fm Erik Meijer (@headinthebox) | Twitter