Podcast appearances and mentions of ed yes

The braille community is buzzing about the next generation of braille display: multi-line devices which can show anything from tables to tactile graphics at the press of a button are now a reality, and enthusiastic early adopters around the world are putting the technology through its paces. These multi-line braille displays will, sooner or later, undoubtedly disrupt all our experiences of refreshable braille in many places, but perhaps most notably in education. What does this mean for teachers, and what does this mean for students in the classroom, doing their homework and progressing to further and higher education? We'll be digging into the detail in two parts: Firstly, we will hear from HumanWare, Bristol Braille Technology CIC, Dot Inc and Orbit Research, all of whom are developing multi-line braille displays, and each of whom will give a ten minute presentation on how they see their products working in the classroom. Secondly, we'll hear from a panel of education professionals. They will share their reactions to the presentations, discuss how current practice might evolve to take advantage of emerging braille technologies, and engage with the manufacturers to find answers to some of their most pressing questions. This episode is presented in collaboration with the Professional Association for the Vision Impairment Education Workforce (VIEW). Manufacturers, their Products and Representatives HumanWare, promoting the Monarch: Andrew Flatres, Braille Product Manager, and Peter Tucic, Director of Strategic Partnerships Bristol Braille Technology CIC, promoting Canute 360 (£2495.00) and Canute Console (£3995 or £1650 for existing Canute 360 owners): Ed Rogers, Managing Director Dot Inc, promoting the Dot Pad (£11995): Mazi Zarrehparvar Orbit Research, promoting the Orbit Slate 520 ($3495 USD) and the Orbit Slate 340 ($3995 USD): Venkatesh Chari, CEO Panellists Jane Sharp, Education Specialist QTVI at RNIB and Chair of the Visual Impairment Education Workforce (VIEW) Jonathan Fogg, Strategic Lead for IT at New College Worcester Jackie Brown, Technology For Life Co-Ordinator for Northern Ireland at RNIB The event was hosted by Dave Williams and produced by Matthew Horspool. Extracts from the Chat What are the dimentions of the Dot Pad please? Participant: 273.2 mm × 228.1 mm Mazi: 20 braille cells per line and 10 lines on the large screen. 20 cells on single line below graphics area. Dot Pad pricing is not fixed but our goals is to make the Dotpad economically accessible. Can you send information from the dot pad back to an iPad? Mazi: We are working on two way interaction between the Dot Pad and connected devices. At this time, the Dot Pad is a printer. It receives content from the iPad, iPhone, PC, or Mac. It is interactive in the sense that you can scroll up and down pages and make selections. You can also scroll across icons showing on your iPhone or iPad. If you would like more information, please be comfortable contacting me. We are rapidly innovating and all ideas and advice is welcome. Do the graphical devices allow a tactile diagram and a braille label on the same page? Ed: Yes. You can mix them up. We typically use a lot of Braille to make sense of the diagrams. For the Canute Console, that was. Andrew: For Monarch, Yes, it can display both graphics and braille on the same array. I'd be very interested to know if manufacturers were intending to (or have) produce progression charts/teaching ideas for supporting student development of skills in using these products? We can't afford to have one for us to learn on as well as one for the student, so any help on how to use them effectively and to think about skills progression is really helpful! Andrew: HumanWare appreciates there is a lot to learn when it comes to these types of new technology, therefore before Monarch will be released we will be conducting in-person teachers training across the UK. The objective will be to show how a Monarch could be used in a classroom along with getting a better understanding on this new ebraille file format. Please register your interest so you can stay updated on when these days become available. Participant: I am familiar with human wear products and they have a fantastic set of training videos for all of their devices. These are easily accessible for LSAs and BSAs as well as teachers. Would the Dot Pad be useful for a student taking physics at advanced level (up to university)? Rendering the visual data effectively has been a constant struggle/ongoing question. Mazi: Dot would love to work with you on your content and progression idea. YES, physics is an ideal subject matter for the Dot Pad. Participant: That's great to hear. I have a student applying for Physics at university this year, and this might be helpful for his Disabled Students Allowance application. Mazi: Wonderful. Exciting to know your student is going for it. Let's connect and set up a call to figure out how to help your student. What is a simple device for early years children instead of Perkins Brailler? Matthew (Braillists): The Perkins is still the best device for the job in our experience. Ed: Using the Canute Console in the basic text editing mode I demonstrated would be closest equivalent experience for our display. However as Matthew says the Perkins hasn't been superceded by any of these devices and they aren't meant as replacements for it. Participant: Unfortunately, for a 4 year old with small hands and not have the strength may impact their development Ed: In that case, pairing a multiline display with a Hable One or an Orbit Writer, be that a Canute Console or any multiline display that supports external keyboards, would be something to experiment with. Venkatesh: The Orbit single-line and multiline displays include an ergonomic Perkins-style braille keypad. The keys require very little force and would be suitable for a young child. Participant: Thank Venkatesh, I need to view this to understand if its suitable for my CYPVI Venkatesh: You are welcome. Please feel free to email me and we can work out a demo. Louise Johnson: The Annie Brailler is especially for young children. We will be purchasing two and I am happy to let you know how we get on. How do you distinguish colour? Textures? We need to teach students to read diagrams the way they will be presented in exams. Ed: Explaining our solution is a bit much to fit into the chat box but happy to tell you about the solutions we use and are experimenting with by email. In short though, with a display 40 cells wide you have space for a key along side every image if you need it and the image can include information about colour and other style information. That is one solution suitable for some circumstances. Participant: In terms of development of these products, it's worth remembering that there are a significant number of learners who are not braillists but still need tactile diagrams. Is it easy to create a table? Ed: Very easy to create a table for the Canute Console. You can use a spreadsheet or a text editor or generate a tables using conversion software. Will Monarch run on an up to date Android system? BNT+ is Oreo which no longer receives security patches. (Happy to hear if this is not the case!) Monarch will be based on Android, but will not have access to the play store, therefore it would be more capable of updating security. It should not be the case of being stuck. Does the Monarch come with Windows applications (Word, PowerPoint) and email? The Monarch will include KeySoft core application including word processor, email client and many more.

Today I'll be covering a topic that's often left in the shadows: Erectile Dysfunction. It can be a sensitive subject for many, But it is one I feel the need to shed some light on because of how much ED affects the world of dating and relationships. So much so that it's not uncommon for me to get dm's (mostly from women), Describing all the ways their partners lack the ability to get “it” up in the bedroom, is hurting their relationship. I asked the men on an Instagram poll this question: “If you struggled with Erectile Dysfunction, would you seek help?” And I asked the ladies: “If he told you early on that he had ED, would you continue to date him?” In today's quick podcast I reveal the answers to the above poll questions, Some of the potential causes and fixes of ED (Yes don't worry, there is hope), And so much more! GET IN MY NETWORK AND ON EMAIL LIST: https://datingwithkaty.com/pages/work-with-me 14 DAYS TO DATING SUCCESS : 14 Day short video course https://datingwithkaty.com/products/14-days-to-dating-success STYLE YOURSELF CONFIDENT FOR MEN: https://datingwithkaty.com/products/style-yourself-sexy-for-men 7 STEPS TO SEXY: Video Course for Women https://datingwithkaty.com/products/live-masterclass-7-steps-to-sexy-for-women Confidence 101: Video Course for Men https://datingwithkaty.com/products/confidence-101-master-class-workbook-included Get my Amazon “Hot Date Night Outfits” and “Man Pad” list's! https://www.amazon.com/shop/datingwithkaty My Instagram: https://www.instagram.com/datingwithkaty/ Learn more about my and my company Cinqe Matchmaking https://cinqe.com/personnel/katy-clark/ --- Support this podcast: https://podcasters.spotify.com/pod/show/dating-with-katy/support

In this episode we continue our Pediatric Emergency Medicine Assembly(PEM23) series with the evidence and growth of contract enhanced ultrasound in the emergency department. In this episode, we talk about the FAST and eFAST exams as well as some of the "how does it work" of contrasted imaging. Use the code EMPOWER to save $100 on registration for ACEP's Leadership & Advocacy Conference - Register Now LAC...https://www.acep.org/lac/

Listen to Part 1Listen to Part 2Listen to Part 3Listen to Part 4FamilyLife Today® Radio TranscriptReferences to conferences, resources, or other special promotions may be obsolete. Out of the Depths Day 4 of 4 Guest:                            Ed Harrell From the Series:         Ducks on the Pond: Rescued at Last________________________________________________________________ Bob:                Sixty years ago this week, Ed Harrell and a number of other sailors were pulled from the Pacific.  They had survived four-and-a-half days afloat after the sinking of the USS Indianapolis.  It's four days that, as you might imagine, Ed Harrell has never been able to forget. Ed:                  I have not had nightmares.  I've had many times that I've awakened and have a vivid scene of the happenings, and yet I think my counteraction to that is "Thank you, Lord, for sparing my life and for bringing me through all of this." Bob:                This is FamilyLife Today for Thursday, August 4th.  Our host is the president of FamilyLife, Dennis Rainey, and I'm Bob Lepine.  We'll hear how God spared Ed Harrell's life today, and we'll hear a remarkable story about a rescue in the middle of the Pacific.                         And welcome to FamilyLife Today, thanks for joining us.  You know, Hollywood has told some tales of castaways left on a desert island, folks surviving in the middle of nowhere, and I've seen some of those movies, and you watch them, and they're interesting.  They have never come close to telling the story that we've heard this week. Dennis:          No, I agree, Bob.  Ed Harrell has been with us all this week and has told a story, a compelling story of how God enabled him to survive an ordeal at sea after being a crew member on the USS Indianapolis, which was sunk on the night of July 30, 1945, by a Japanese submarine, and, Ed, I want to thank you again for your service as a veteran, but also for writing this book and for taking us there and giving us a greater appreciation not just for veterans and what they've done to protect our freedom as Americans but also for taking us there and showing us what tough-minded faith in Almighty God looks like.  Because time and time again you've taken us to vivid scenes where you've been at a fork in the road where you've had to trust God, and you'd been at sea for four days in a life jacket.  You'd only had a few tablespoons of water.  You had some rotten potatoes that had come after you'd prayed for some food; been separated from your buddies, and on the fourth day you are virtually alone. Ed:                  No question.  Even with my buddy at the time and, in fact, there were three of us at the tail end there that fourth day and the one then dropped his head in the water, and he's gone, and then it's just McKissock and myself.  And my mind, by now, is beginning to fail me somewhat in that – McKissock, I know, would say to me, "Hey, Marine, you ever been to the Philippines?"  And, "No, I've never been there."  Well, he had, and he promised to kind of take me under his wing when we got there.                          And yet I knew him.  I knew who he was.  I'd served under him, and he was a peach of a guy, and yet, to me, he was Uncle Edwin, and I called him Uncle Edwin.  I had an uncle two years older than me.  I guess I was thinking of the good times in my mind with someone back home, and yet McKissock was Uncle Edwin to me.                                                And then it was sometime then that afternoon, you know, we had seen the planes, heard them at 30,000 feet, and I say to McKissock, "I hear a plane."  And he said, "I hear one, too," and if you can imagine somewhat that you hear a plane, and you know that it's somewhere coming closer, and yet you don't know which direction it is.  And we began to look all around and, finally, we could detect that it's coming from that direction. Dennis:          Was it coming toward you? Ed:                  It was coming toward us, and it was flying about 8,000 feet and, well, what do you do?  I tell you what you do.  You scream, you splash water, you make all kinds of contortions there in the water, hoping and praying that he can see you.  But here he is flying over us, and had he come any further, he would have gone over us, but when he got, like a quarter of a mile or so out here, flying at 8,000 feet, he headed it straight down toward us as if he knew we were there.  But he didn't know we were there – impossible for him to see us.  If we'd had on deer-hunter orange, and he knew we were there, he could not have seen us.                         In fact, the pilot that later picked us up, he said the possibility of him seeing you would be the equivalent of taking the cross-section of a human hair and looking at the end of that human hair at 20 feet.  He said impossible for him to see us. Dennis:          So why did he go into the dive? Ed:                  Why did he go into the dive – that's the miracle of the angel coming for us, and that is the end of the fourth day.  Well, I've talked to Lieutenant Guinn [ph] at different times, and … Bob:                He was the pilot? Ed:                  He was the pilot, and he was flying out of Pulau, and he was flying a land-based plane, something like a B-20, a twin-engine plane, and as he was flying, he had left out that morning, and he had a problem with his antenna that kind of trails at the back of that aircraft.  And the stabilizer on that antenna had come off, and they had put something on, and he went out and tried it, and it didn't work.  They came back in, and then they put something on, and here they go again.                         So as he is flying over us, and here, as I mentioned, here he's coming just at a point that he could nearly dive right down to us, at that point he had gone back to the bomb bay door, and he'd opened the bomb bay door, and he was reeling in the antenna, and while he had that bomb bay door open, he looks down at a split-second there in the late afternoon of the fourth day, when the sun was setting on us late in the afternoon, and he saw the little mirror, so to speak, of the sun hitting on the oil on our clothing, and when he saw that, he thought it was a submarine down there. So immediately he rushes back to take over the controls, and the boys in the aircraft, they yelled back at him, with all that noise, you know, with the motors still revving up, you know, "What is it?  What is it?"  And he said, "Look down there."  And they looked down, and they could see the oil slick.  Well, my story is this – that we see him coming, and as if God had planned it for us, you know, here, when he gets to about a quarter of a mile from us, he heads down, and he comes down, and he circles us.  And as he circles us, then he tilts his wings a few times, you know, and then he leaves us.  He goes back up, and he circles us again up here. And we wondered, "Well, what in the world is he doing up there?"  Well, he can't land on the water, we knew that, but what he did, he came down, and he saw that there was someone down here.  He goes up, and he breaks radio silence to declare, "ducks on the pond."  He didn't know whether we were Japanese or American boys, but he broke radio silence to declare ducks on the pond.  And then he comes back down, then, and he circles us again.  He tilts his wings a time or two to give us assurance, you know, that we know you're there.  We don't know who you are, but we know you're there. And then he drops a life raft in, and in the meantime, then, he has radioed back into Pulau, and the next pilot, then, gets into a PBY that could land in the water, and Adrian March [ph], then, he's on his way, you know, to come and to pick us up.  And sometime later, then, he arrives, and in the meantime the raft that Guinn had dropped – I know, my friend McKissock, had made his way to the raft.  Then he's leaving it, and I wonder what's wrong.  And I get to the raft then, and it was bottom side up.  I try to get it turned over, managed to get it halfway turned over, but the CO2 on it was torn off, so I couldn't inflate it – no food, no water, no nothing – kind of a torn place in it, so it wouldn't even hold me just to stand on that, so to speak, hole in that pile of rubber. In the meantime, then McKissock had gotten far enough away from me that the PBY landed and had picked him up, and then I wondered, well, will he tell them that there's a Marine out there with him?  Well, he did, but it was a period of time that the plane seemingly – I couldn't see it, but he was running the swells – they were, like, 20-foot swells, and he'd run the swells back and forth trying to make his way over to me, and it took a period of time for him to run those to where he could get across, because if he had turned those props into the water, it would have flipped his plane.  And he pulled a no-no when he landed.  It was against all regulations for him to land his plane in the open sea, and yet he did, because as he landed he said he could see more sharks than he saw boys.  And we were scattered over, like, a 75-mile area, and he took reconnaissance of that and could see that there are boys in life rafts, there are boys on floater nets, and there are stragglers.  Then he actually saw shark attack on several boys, and he was determined that he was going to land, and he cleared it with the rest of the crew.  They all voted somewhat that they could take the punishment, but we've got to land. So they landed then and then finally then they came over me and through out a little life ring and picked me up.  I recall that as they got me out of the water, I blacked out or nearly blacked out.  I had no control over myself, and then they got me aboard the plane, then, and they would take me like a sack of feed and set the guy here, and the next guy just stack him against him, and they kept stacking us in there, and then finally it wouldn't hold anymore, and there were still some boys, stragglers out there, and it was getting dusk dark, and they picked up all that they could, all that they could find, and they actually fashioned them out on the wings, and then finally then sometime later in the night, the seas calmed down after night somewhat, and they shut off the motors, and we sat there and waiting until 12 or 1:00 or so in the morning when the little destroyer, Doyle, came in, and they picked us up. When I got aboard the plane, after a moment to board the plane, then I could look across at a Marine, and I could see that it was a blond-haired guy.  I could see he had the eyeballs that were just big red sores, and I knew it was Spooner, and I saw what he was doing.  He had a can of green beans, and he was feeling down on the deck of the ship, and he finally found a stud bolt or something down there, and he took that can of green beans, and he kept hacking away until he knocked a hole in the can of green beans and then he was turning that juice up and drinking it.  I recall saying to him, "Hey, Marine, how about some of your bean juice?" Well, you'd have to know Spooner, but he kind of told me where I could go, and … Dennis:          This is the guy that you saved his life by grabbing him by the life jackets on day 2, right? Ed:                  Yes.  Then I said to him, "Spooner, you don't know who this is.  This is Harrell."  Well, I didn't have to say any more.  He just kind of fell across the plane there toward me and kind of spilled some of his bean juice as he shared that with me.                         I was transferred, then, aboard the Doyle, and sometime that night, 1:00 or so that night. Dennis:          Ed, when he lunged across the floor of that plane to give you the bean juice, was that kind of an emotional – I can't even imagine.  I mean, he's alive, you're alive, it's what you'd said two days earlier.  You said, "You and I are going to get out of here." Ed:                  It was emotional for me as much as, I'm sure, for him – just to see that he made it, you know, because I didn't know anytime that fourth day – I knew not where Spooner might be.  And then to be able to see him there and see that he was alive, and I recognized him as soon as I looked across the plane and saw those eyes, I knew it was Spooner. Bob:                When you first heard that plane, when it started to dive and was tilting its wings at you, you thought, "We're going to be rescued?" Ed:                  Yes. Bob:                I would think you'd just weep. Ed:                  Well, you know, there's times when you weep, and there's times when you weep for joy.  I look back on this, and when I look at the – well, the first day that I had every assurance that somehow, some way, the Lord is going to see me through.  I felt that from the very moment that I went into the water.  And then the second day, when He provided the water for me … Bob:                … the rain shower … Ed:                  … you know, you have to just say "Thank you, Lord, I know that you are speaking to my heart and that somehow, some way, you're going to see me through."  And then on the third day, then, when the little raft came into the group, and you know that your life jacket no longer is holding your head out of the water, and now you have a spare life jacket that He provided for you, and you have to thank Him again.  And then sometime, then, the third afternoon, likewise, when you're starving still for water and for some food, and then for Him to provide half-rotten potatoes, you know, I have to thank, you know, He's still with me. And as I look back on that, you know, I think of the water of life.  You know, if you drink of this water, you're going to thirst again.  If you drink of that salt water, you're not going to make it at all.  But if you drink of the water that I give you, you'll never thirst again.  And then the bread of life, the potatoes that I had – and then when I get to the last day, the plane that came in, well, you know, it's like the Lord says, "Let not your hearts be troubled.  If you believe in God believe also in Me.  In My Father's house are many dwelling places.  I go to prepare a place for you, and since I go to prepare a place for you, I'm going to come again, and I'll receive you unto myself that where I am there you may be also."                         And so here He's coming, for me, at that time, He came for me in the person of Lieutenant Guinn as he came.  So I look back on the whole experience, and I think I have to say that it's a wonderful experience to have lived through, and I just praise and thank the Lord all the time for His mercy and and for His grace – unworthy as I am and yet He saw fit to spare my life through this ordeal. Bob:                You know, you mentioned that it was two years before you shared anything with your father.  We got a letter – you may remember this, Dennis, from a woman whose husband had passed on, and she said it wasn't until the last years of his life, some – almost 50 years after the battle had occurred – that she knew he'd been on Iwo Jima.  They'd gone their whole married life; she had never known that he was in that battle until near the end of his life.                         And I thought to myself as I read that, it was another way that he was protecting and defending by not sharing his story, and yet she wrote, and she said, "Knowing that sure explained some of the nights when he would wake up in terror."  Have you had that experience?  Have you had the nightmares and the terror of remembering some of that? Ed:                  I have not had nightmares.  I have had, many times that I've awakened and have a vivid scene of the happenings, and yet I think my counteraction to that is that "Thank you, Lord, for sparing my life and for bringing me through all of this," and I think maybe – I like to look at it, say that the Lord reminds me even today of those incidents.  And as He reminds me of those, then they help to strengthen my faith and my resolve to live a life for him today. Dennis:          You mentioned that pilot ended up finding 56 survivors on that fourth day.   Ed:                  Right. Dennis:          In total, there were 317 survivors.  How did the rest of them all get picked up? Ed:                  Well, as soon as they picked us up and found out that it was the Indianapolis, then all word went out.  They broke radio silence everywhere, and any ship within a couple of hundred miles or so; that is, a destroyer or something that could move fast, they came to the scene.  And when the USS Doyle, the ship that picked me up, when it got closer and closer, what did he do, Commander Claytor, he turned on his powerful spotlights up on the under part of the clouds, and you can imagine what that did to that whole area.  It was just like a mushroom with lights underneath the clouds.  And for the boys that were out there, they knew that rescue was there, and that gave them the hope that they needed.  And some of those had to go through another night.  It would be dangerous, you know, as dark as it was, to try to take some kind of a craft out there and maneuver around without hitting someone.  But that gave them hope through the night until the next morning.                         Now, I was picked up aboard the Doyle off the PBY.  I know, as they took me aboard, there was a couple of sailors that there's no qualms about them getting dirty or anything, and, of course, we were grease monkeys, really, with all that oil and all on us.  And I recall that they took my arms and put them around their neck, and they drug my feet, and they took me down below deck, and then they began to – they stripped off my clothing, and then they began to take something like a diesel fuel or kerosene, and they began to wash that oil off of me.  And then they had to be so careful with all of the saltwater ulcers that I had, and then they put me in – a Marine being put in Navy skivvies.  So they put their Navy underwear on me, and then … Bob:                You were okay with that, at that point? Ed:                  I was okay.  In fact, may I just say that I met the guy, after 57 years, I met the guy aboard the Doyle that actually cleaned me up, and he took me, then, to his bunk and gave me his bed, and then the corpsmen then came, and they had a cup of sugared water, warm sugared water, and they gave me a couple of tablespoons full or so of warm sugared water to kind of rehydrate me, I guess. Bob:                Did it taste pretty good? Ed:                  It tasted wonderful, it tasted wonderful. Bob:                Sixty years after this happened, how many of the survivors are still alive? Ed:                  A week or so ago, I got a report.  I think there was 97 of us still alive. Bob:                Spooner? Ed:                  Spooner's gone.  There's five of we Marines.  Nine of we marines survived out of – there were 39 of us aboard, and nine of us survived, and of the nine there are five of us still living today. Bob:                How about McKissock? Ed:                  No, McKissock's gone.  And, by the way, McKissock was not a believer at the time, and McKissock told me later, he said, "Harrell, I went home, and I got to look at all that the Lord had brought me through there," and he said, "I was a churchgoer.  I went to church all the time, but I was really not a believer."  And he said, "Finally, I just had to get down on my knees and thank the Lord and tell Him that I trusted Him as my Savior because I know that He had a purpose for my life."  And he became a real Christian friend of mine as long as he lived.  He passed away four years ago, maybe. Dennis:          Well, Ed, wow.  I'm exhausted from treading water here with you.  But I have to say, what a great story.  What a great story of faith and redemption, God's providential care, and how you have faithfully given Him the credit and the honor for doing that.  I'm grateful for your book and just pray that God will give you many great years of health and many more great-grandchildren, and I appreciate you being with us here on FamilyLife Today. Ed:                  Thank you so much, my delight, my pleasure to be with you. Bob:                And, you know, if any of our listeners this week have missed portions of this story, we've got our interview with Ed available on CD.  In fact, it's on two CDs, and we've been able to include on the CDs material that we weren't able to fit on the radio because of time constraints.                           We also have the book that you've written, Ed, which is called "Out of the Depths."  It tells the story of the sinking of the Indianapolis and of your rescue along with the rescue of the other sailors and Marines who were in the water 60 years ago this week.  Go to our website at FamilyLife.com if you're interested in getting a copy of Ed's book or the CDs of our discussion.                          At the bottom of your screen when you're on our website, FamilyLife.com, you'll see a little button that says "Go."  Click on that button, and it will take you to a page where there is more information on Ed's book, on other resources that we're recommending this week.  You can order online at FamilyLife.com, if you'd like, or you can call 1-800-FLTODAY and someone on our team can answer any questions you might have about these resources, or you can order over the phone as well.                         1-800-FLTODAY is the number.  The website, again, is FamilyLife.com, and let me encourage you, especially if you weren't able to hear the complete story, to contact us and get a copy of the book and the CDs as well.                         And then let me also ask you consider this month making a donation to FamilyLife Today.  We're a listener-supported program.  Your donations are what keep us on the air.  We are asking folks if, during the month of August, you could make a donation to help with our financial needs.  We'd like to send you a thank you gift.  A few months ago we had Shaunti Feldhahn in our studios, and we visited with her on a book that she's written called "For Women Only."  It's based on research that she has done with more than 1,000 men all across the country asking them about what they need most from their wives.                         This month we're going to make those available to you as a thank you gift when you make a donation of any amount to FamilyLife Today.  You can donate online at FamilyLife.com or you can call 1-800-F-as-in-family, L-as-in-life, and then the word TODAY to make your donation.  When you do, be sure to request the CDs for women, or if you're online, when the keycode box comes up, type in the two letters "CD," and we'll know that you'd like to have the Shaunti Feldhahn CDs sent to you.  And let me say thanks in advance for your support of this ministry.  It is much needed, and it is appreciated.                         Well, tomorrow we're going to talk about some very profound theological ideas that even a three-year-old can begin to catch onto.  We'll explain what we mean tomorrow.  I hope you can be back with us for that.                         I want to thank our engineer today, Keith Lynch, and our entire broadcast production team.  On behalf of our host, Dennis Rainey, I'm Bob Lepine.  We'll see you tomorrow for another edition of FamilyLife Today.                          FamilyLife Today is a production of FamilyLife of Little Rock, Arkansas, a ministry of Campus Crusade for Christ.  ________________________________________________________________ We are so happy to provide these transcripts to you.  However, there is a cost to transcribe, create, and produce them for our website.  If you've benefited from the broadcast transcripts, would   you consider donating today to help defray the costs?         Copyright © FamilyLife.  All rights reserved.       www.FamilyLife.com                             

Listen to Part 1Listen to Part 2Listen to Part 3Listen to Part 4FamilyLife Today® Radio TranscriptReferences to conferences, resources, or other special promotions may be obsolete. Out of the Depths Day 1 of 4 Guest:                            Ed Harrell From the Series:         The Sinking of the USS Indianapolis________________________________________________________________ Bob:                Sixty years ago this week on the night of July 30, 1945, just weeks before the end of World War II, a Japanese submarine launched torpedoes that would sink the USS Indianapolis.  Marine Ed Harrell was on board that night. Ed:                  When I actually left the ship, and there I prayed that somehow the Lord would see me through what lie ahead, and yet I had the foggiest idea that I'm going to be out there for four-and-a-half days.  There's times when you pray, and there's times when you pray, and there is a difference. Bob:                This is FamilyLife Today for Monday, August 1st.  Our host is the president of FamilyLife, Dennis Rainey, and I'm Bob Lepine.  Of the nearly 1,200 men who were onboard the Indianapolis on that night only 317 survived.  Ed Harrell was one of the survivors, and we'll hear his story today.                         And welcome to FamilyLife Today, thanks for joining us on the Monday edition.  Dennis? Dennis:          Bob, I want you to imagine with me a pretty dramatic scene.  Just consider yourself being 20 years old, you're a Marine, you're tough, you're physically fit, but you're alone, you're in the ocean, you've just lost your ship, and you and about 80 others are floating in the middle of the night in the ocean in lifejackets.  We're going to hear a story – one of the most compelling stories I think I've ever heard from a gentleman who joins us on FamilyLife Today – one of the survivors of the USS Indianapolis. Bob:                A man who doesn't have to imagine what you just described because he lived through it. Dennis:          That's exactly right.  Ed Harrell joins us on FamilyLife Today.  Welcome to the broadcast, Ed. Ed:                  Thank you so much.  It's a delight to be with you. Dennis:          Ed is not only a survivor, but he was a businessman for 38 years.  He's served as a member of the board of trustees at Moody Bible Institute, a great ministry.  He and his wife Ola, who have been married since 1947 – that's a lot of years, that's a lot of years, live in Paris, Tennessee.  They have two children, eight grandchildren, and four great-grandchildren. Ed:                  That's right. Dennis:          You've lived quite a life, Ed, but you're one of the few, one of the few survivors of that tragedy.  Take us back, first of all, to when you signed up.  Why in the world did you sign up to be a Marine?  It was 1943, is that right? Ed:                  That's right, 1943.  I don't know that I can even know why I really did at the time, but I knew that the war was getting pretty close to home, it sounded to me.  In fact, when I heard that the Japanese and the American forces were having quite a battle at Midway, I was thinking that Midway was maybe between San Francisco and Hawaii, and so I thought, you know, they're getting pretty close to America, so, actually, I had just finished my junior year in high school, and I volunteered then for the Marine Corps. Bob:                You were 17, 18 years old? Ed:                  I was 18 when I – I actually became a Marine when I was 18. Bob:                You know, Ed, my son is a junior in high school, and the thought of my son saying, "I'm going to sign up to be a Marine in the middle of this kind of conflict, as a parent, I'm not sure I'd endorse that plan.  Were your parents behind it? Ed:                  Yes, I think they pretty much agreed.  Dad pretty much agreed.  They didn't necessarily want to see me leave, but they knew, too, the little Silvertone radio that we had was telling us quite a bit what was happening in the Pacific, and I didn't have much problem convincing them that I wanted to go.  In fact, I have two grandsons in the Marine Corps today. Dennis:          Do you remember that time when you said goodbye to your dad? Ed:                  I do.  My dad was 37 or 39 years old, and I thought he was an old man then, but I told him goodbye at the bus station. Dennis:          Did you hug? Ed:                  Yes, yes, we did. Dennis:          Were there tears? Ed:                  There were some tears, there were some tears. Dennis:          What did he say to you? Ed:                  I don't know that I can remember what he said, but I'm sure that the advice that he gave me, he was a fine Christian man, and I'm sure it was some good, solid advice that he was giving me. Bob:                Why the Marines?  Why did you pick them instead of the Army or the Navy or the Air Force? Ed:                  I wondered sometimes why if I picked the wrong one, but I really don't know.  I even considered, after I got in the Marine Corps, that I would be a paratrooper.  After I got through sea school, then they said – after I got through boot camp, they said, "You're going to sea school," and I didn't know what that meant, either, but I went through sea school, and then they said, "You're going aboard a large combatant ship," and so I waited, then, until the Indianapolis was in port and caught it at San Francisco. Dennis:          Before you left to join the Marines, you made another decision that was a life-altering decision. Ed:                  Yes, I did.  Yes, I did.  On the 1st of August, 1943, already a Marine and yet hadn't shown up even for my boot camp, I went to church on that Lord's Day morning, and seeming the Lord was saying to me, "Your last chance, your last chance," and the preacher preached a message, and he gave an invitation, he pronounced the benediction, and I sat there, I knew that my heart was not right with the Lord, and knowing that I was going into combat soon that I had to get things right with the Lord.  I know the pastor came back and sat down by me there.  Everyone else had left the building except two people – one was my wife later to be, and my mother-in-law later to be, and they were back in the back of the building there praying, and the pastor turned to a Scripture, Acts 16:31, which simply says, "Believe in the Lord Jesus Christ and thou shall be saved."  He said, "Ed, do you believe that?" Well, I was brought up in a Christian home and Sunday school, church all the time, but really never trusted the Lord as my own personal Savior.  And so he goes over that a time or two, and he said, "Ed, God who cannot lie, is making you a promise, and He simply says believe on the Lord Jesus Christ, the finished work of Christ on the cross for you, and He promises to save you."  And then he would look at me and said, "Do you believe that?"  And I said, "Yes, I believe that," and he said, "But does the Lord save you?"  "No."  Well, he went over it a time or two and there, in the quietness of that little pew there in the church, I trusted the Lord Jesus Christ as my personal Savior.                         So later now, when I'm getting into the story of the actual sinking of the ship, I could really look back and rely on the faith and trust that I had in the Lord to care for me, even there in the water those days. Dennis:          Yeah, in fact, there's a line in your book, which basically says this – "The same Jesus Christ who became my Savior was now going to be the same Jesus Christ who saved my life." Ed:                  That's right.  When I actually left the ship, you know, abandoned the ship, I trusted the same Lord to take care of me there as I stepped over the railing and stepped into the water, and brought up in a Christ home and knew some Scripture.  But the Lord brought to mind there as I was about to abandon ship and seeing many of the boys actually jumping on each other in a desperate rush to get off the ship, and I hung onto that rail for a little while, and I prayed and oftentime I say when I give talks is that there's times when you pray, and there's times when you pray, and there is a difference.  And there I prayed that somehow the Lord would see me through what lie ahead, and yet I had the foggiest idea that I'm going to be out there for four-and-a-half days.                         But here from memory of His Word that he brought to mind – "Peace I give unto you not as the world give unto you, let not your heart to be troubled.  Don't be afraid."  And yet I'm scared to death.  And as I left the ship, then I left with the assurance I felt – God didn't speak to me in any audible form in any way, but just the assurance that I had from repeating His Word back to my heart, I knew that He was going to care for me. Dennis:          You did end up joining the Marines then, and you boarded the USS Indianapolis in San Francisco. Ed:                  In San Francisco. Dennis:          At that point, you had not been to war, you had not been in any battles, but that was soon to change, wasn't it? Ed:                  That's right.  Of course, to get aboard a large combatant ship like that, you know, that ship, you know, was 610 feet, 8 3/4 inches, and four or five stories high, and that's going to be my home, you know, for a time.  And then after I got aboard, then to see all those big guns that I'm going to have to learn how to fire those things, and I think I say in my book the biggest gun that I'd ever fired was a double-barreled shotgun, and yet here I'm going to be firing five-inch guns and 40 millimeter guns, so I'll be trained to do those things.                         Then I was at Saipan – actually, I was at Enewetak and Kwajalein Islands there in the Marshalls, then the first, really, combat was at Saipan then at Tinian and at Guam.  The sea battle of the Philippine Seas, that was at Palau, at Iwo Jima, at Okinawa, and later three air strikes on Tokyo and then, lastly, I was Marine guard that guarded the two atomic bomb – components of the bombs that we took over to our B-29 base on the island of Tinian. Bob:                And you didn't know, when you got on board the Indianapolis in San Francisco Harbor, you didn't know what else was on board with you.  You didn't know that you had … Ed:                  We did not know. Bob:                … the two atomic bombs that were going to be dropped on Hiroshima and Nagasaki. Ed:                  We knew it was top-secret cargo.  We understood, even, that the captain of the ship didn't know what we had; that he had been told that what he had, we needed to get it to the forward area – that every hour would save lives, and I was a guard that guarded – or, actually, I was a corporal of the guard, and I stationed guards both on the two places that we had the components of the bomb. Bob:                San Francisco to Tinian – how long a trip is that in the water? Ed:                  We made a record speed run.  We traveled those 5,400 or so miles in 10 days. Bob:                Wow. Ed:                  So, can you imagine a heavy cruiser traveling, like, 32 miles an hour across the Pacific?  So we made a record speed run to Tinian Island and got rid of our cargo. Dennis:          And you got rid of the cargo, made the turn, and you were to participate with another ship? Ed:                  We received orders at CENPAC there in Guam, the Central Pacific Command, to proceed to the Philippines, but we were to – yes, we were to join up with the USS Idaho, I think, three days later, to make a gun re-practice as we went into the Philippines, because the main invasion of Japan was to take place in November of '45. Dennis:          We're not going to go into the detail that surrounds, really, a great controversy about the USS Indianapolis, because some information was withheld about the enemy being in the waters – enemy subs – and you guys sailed into harm's way without realizing it.  But you were in the process of making your way to join up with the USS Idaho, and it was really an uneventful trip.  You weren't even going all that fast at that point, right? Ed:                  As I mentioned, we had traveled 32 knots going into Tinian, and then when we received orders then to go on to the Philippines, Captain McVay requested, or they gave him permission to travel only at 17 knots, to slow down, because we had nearly burned the motors up, you know, getting the cargo over.  So we had slowed back to 17 knots going on to the Philippines. Dennis:          You were one day away from connecting with the USS Idaho, and was it the middle of the night? Ed:                  Well, we were to have met them the next day in the daytime, but we encountered Commander Hoshimoto at about five minutes after midnight on the night of July 30, 1945. Bob:                Now, where were you when that happened?  Were you asleep in your bunk? Ed:                  No, the Indianapolis was a pretty modern ship, but we did not have air-conditioning, and in order to get any sleep at night, you went topside.  So I was on watch 'til 12:00.  At 12:00 I went to my locker, and I got my blanket, and I went topside, and I went up under the barrels of number 1 turret, and I took off my shoes and used kind of the arch of my shoe as a pillow, and I rolled up in my blanket, and it was about five minutes or so after midnight that the first explosion, we took the first torpedo.  And about as long as it would take Commander Hoshimoto to say, "Fire one, fire two," and he fired six, but two of them hit us, and the first one cut the bow of the ship off.  If you could see the picture of the ship, you could see that those barrels on number 1 turret, forward big 8-inch guns, they're about 18 feet long, and I'm sleeping right down on the deck under the barrels of those guns and looking forward of me, maybe 25, 30 feet or so, the bow of the ship is cut off – about 50 feet.  Some said 65 feet, but I don't think it was that much.  I think it was more of a 40 feet or so.  The bow of the ship was cut off, so we became a funnel, then, as we were moving through the water, and then the second explosion then was aft of me, nearly midship and close to the marine compartment, and it made a big gaping hole.                         And, of course, since we had no air conditioning, we were traveling at a – you might say, at an open condition in that all of our bulkheads down below were open, and they had to be open or else we would suffocate without air conditioning.  So that was a death blow, likewise, because as we were moving forward in the water, all of that water … Dennis:          It just poured in the front. Ed:                  It was rushing in, and even before I could get back to my emergency station, which was back at midship, the bow of the ship is already under.  I mean, the deck of the bow of the ship, like, the first 100 yards or so, is already under. Dennis:          Was there still light on the ship at this point, or had the torpedoes knocked out the electricity. Ed:                  All the electricity was knocked out. Dennis:          So you're in the middle of the night … Ed:                  But we had light in that there was an inferno below decks.  They say that number 2 turret took a hit, and the magazine in number 2 turret had exploded and came through all the way up so that it was just a big fire, a big blaze, coming up through there.  And then most other places below decks forward of midship was an inferno.  And so you get a certain amount of light, you know, from that. Dennis:          You said when the torpedoes hit, and the boat blew up, blew the front end off, that there was a huge amount of water that went up in the air, and it drenched you and ultimately kept you from burning up? Ed:                  I think two things – number one, of course, I believe in the providence of God, number one.  I had the blanket around me, and that protected me, no doubt, maybe from much of the blast of the fire at the first explosion, and then all of the water, then, from that first explosion that went up in the air, I don't know I could imagine 50 to 100 feet plus, then all of that coming back down.  Well, I was drenched, you know, with all the water, as it came back down, and that kind of protected me somewhat, I'm sure, from much of the flash burn that many were getting. Bob:                Ed, when something like that happens, it's disorienting at first.  You're thinking, "Did something explode down in the engine room," you're kind of trying to get your bearings.  How long do you think it was before you realized, "We're under attack, we've been hit," and you caught a sense of what was going on? Ed:                  I think immediately when we were hit, I wondered, "We aren't firing at anyone," and then just those three explosions, and no one now is firing back at us.  So we had to have either hit a mine or we had to have been hit by a torpedo.  And then realizing nearly immediately that forward part of the ship was cut off, and I could hear the bulkheads breaking down below and they, to me, were a death blow.  You could imagine, you know, with all that water, with the ship still moving 17 knots or so, and the funnel there coming – all of the water coming in, and the bulkheads breaking, you knew that the ship was doomed, and as I began to make my way, then, back to my emergency station, which was back to midship, and there were those that were coming from internally coming out, and that part of the ship, really, was kind of the officers' quarters up there. Many of those were in the flash burns, and as they came out, literally, flesh was hanging from their face and from their arms, and they were in panic and begging for someone to give them some help.  But, you know, that's not my responsibility, and I have to make my way to my emergency station, which was on the quarterdeck.  And, of course, when I get to the quarterdeck, then, I'm realizing that the ship is already under forward part, and there's no question that it's sinking.  So as word actually came to abandon ship, I had made my way to the port side, and there on the quarterdeck, there's a steel cable, a rail, as we call it, and I got ahold of the rail, and I hung on there and said my prayer, you know, before I actually stepped over the rail and stepped about two big, long steps and jumped into the water feet first. My kapok jacket then came up over my head.  If you could visualize that the deck of the ship now is listing so that you step over, and you walk down the keel of the ship, walk down the side of ship, and so I could have nearly walked to the water, but I walked down closer to the water, and then jumped in feet first and then began to come up and push that oil back that was on the water and then to try to get my head up above that, and then swam away from the ship about maybe 50 yards, and then we began to congregate, you know, in little groups.  The ship had still been moving, so boys had been getting off maybe for two or three or four minutes.  I actually watched the ship as she went under. Bob:                Did you think this was it for you? Ed:                  I wondered, and yet I really felt – and I don't say this in any boasting way of any kind, but I really had the assurance that somehow, some way, that I would make it. Dennis:          You felt like God … Ed:                  I felt assurance that – "Don't be afraid, don't be afraid.  I'm with you," and I think when you hear all of my story, you'll see the various times that He came to my assurance that "I'm still with you," all the way through – the different things that happened for the next three days. Bob:                Yes, and we're going to hear the rest of your story over the next couple of days.  Of course, it is told in the book that you've written called "Out of the Depths," which is a compelling story of God's faithfulness in the midst of remarkable adversity, and I want to encourage our listeners, you can get a copy of the book from us when you contact us here at FamilyLife.                           Go to our website at FamilyLife.com.  Down at the bottom of the screen there's a button there that says, "Go."  You click on that button, it will take you right to a page where you can find information about ordering Ed's book.  Again, it's called "Out of the Depths."  We also have our conversation this week with Ed Harrell available on CD.                           We also have a book that our friend, Chip Ingram, has written that is a reflection on pivotal chapters from the Psalms where David experienced the same thing that you've talked about, Ed, which is the presence of God in the midst of trial and adversity.  He's written a book called "I Am With You Always."  It's a book that reminds us that the Lord is faithful to hear the cry of our heart; that He is there for us in times of great trial like you experienced.                          In fact, any of our listeners who wanted to get your book and Chip's book together, we'd send them the CD that has our conversation with you.  We'd send it along at no additional cost.  Again, go to our website, FamilyLife.com, click the "Go" button at the bottom of the screen.  That will take you right to the page where there is more information.  Or call 1-800-FLTODAY.  That's 1-800-F-as-in-family, L-as-in-life, and then the word TODAY, and we've got folks on our team who will be happy to let you know how you can have these resources sent to you.                         You know, speaking of resources, Dennis, one of the most requested resources we've had in our FamilyLife Resource Center this year has been two CDs from a conversation you and I had with Shaunti Feldhahn.  She wrote a book called "For Women Only."  It was based on the research she had done, conversations with more than 1,000 men about the deepest needs and the deepest longing in men's hearts.  And that conversation really resonated with a number of our listeners.  This month we are making that two-CD set available to any of our listeners who would contact us in August to make a donation of any amount to the ministry of FamilyLife Today.                         It's our way of saying thank you for helping to support this ministry.  We are listener-support, and it's your donations that keep us on the air in this city and in cities all across the country.  So this month, if you can go online to make a donation or call 1-800-FLTODAY to make a donation, just mention that you'd like the CD set for women.  In fact, if you're donating online, when you get to the keycode box just type in "CD," those two letters, and we'll know that you want to have these CDs sent to you.                         Again, our website is FamilyLife.com or you can call 1-800-FLTODAY to make a donation, and we appreciate you standing with this ministry financially.                         Well, tomorrow we're going to begin to hear the story of how Ed Harrell and others survived for four days afloat in the Pacific.  I hope our listeners can be back with us for that.                         I want to thank our engineer today, Keith Lynch, and our entire broadcast production team.  On behalf of our host, Dennis Rainey, I'm Bob Lepine.  We'll see you tomorrow for another edition of FamilyLife Today.                          FamilyLife Today is a production of FamilyLife of Little Rock, Arkansas, a ministry of Campus Crusade for Christ.  ________________________________________________________________ We are so happy to provide these transcripts to you.  However, there is a cost to transcribe, create, and produce them for our website.  If you've benefited from the broadcast transcripts, would   you consider donating today to help defray the costs?         Copyright © FamilyLife.  All rights reserved.       www.FamilyLife.com

Academia is divided over the wisdom of offering students extra credit on tests or projects. In this episode of the KUT podcast “Higher Ed,” KUT’s Jennifer Stayton and Southwestern University President Dr. Ed Burger discuss the utility and merit of offering extra points for extra effort. Ed says for the most part he supports extra […]

Academia is divided over the wisdom of offering students extra credit on tests or projects. In this episode of the KUT podcast “Higher Ed,” KUT’s Jennifer Stayton and Southwestern University President Dr. Ed Burger discuss the utility and merit of offering extra points for extra effort. Ed says for the most part he supports extra...

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Picks: Ed Podcast - All Things Git

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Picks: Ed Podcast - All Things Git

Sponsors: KendoUI Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the React Round Up Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the React Round Up Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Adventures in Angular panel talks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Adventures in Angular panel talks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the Adventures in Angular panel talks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that... 39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there. You are an eMac’s guy? The way I think about it is through Git right out of the box. Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it. 40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are. Chuck talks about code editor and tools.  41:28 – Ed: ... we have been pulling that out as quickly as possible. We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time. 42:02 – Chuck: Yes, sure. 42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that. 42:30 – Ed: That Chuck. 42:36 – Chuck: Where do people get news? 42:42 – Ed: Go to here! 42:54 – Chuck: Where do people find you? 43:00 – Ed: Twitter! 43:07 – Chuck: Let’s do Picks! 43:20 – Advertisement – Fresh Books! Links: GitHub Microsoft’s Azure Microsoft’s Pipeline Azure DevOps Erlang WhiteSource Chuck’s Twitter Ed Thomson’s Twitter Ed Thomson’s GitHub Ed Thomson’s Website Ed Thomson’s LinkedIn Sponsors: Angular Boot Camp Fresh Books Get a Coder Job Course Picks: Ed Podcast - All Things Git

We discuss the idea of professional reinvention and sit down with sales executive and entreprenuer Edward Nunn to hear his 33 year journey. Length: 54:08Host: Zach | AdeEdward Nunn LinkedIn: https://www.linkedin.com/in/ed-nunn-7851ba11/NunnAbove www.nunnabove.comLiving Corporate Patreon and All Major Links: https://linktr.ee/livingcorporateTRANSCRIPTAde: "It is not the strongest species that survive, nor the most intelligent, but the ones most responsive to change." The context of this apocryphal quote commonly attributed to Darwin is related to this theory of biological evolution, but I believe there's something more there. For many of us, we don't want to just survive, we want to thrive. We want to achieve as much as we can while being our best selves, or at least while striving to find out who our best selves are. So with that in mind, what does change responsiveness look like for us in our careers? How do we adapt professionally to make sure we're constantly setting ourselves up for long-term success? What does that even mean? What does that look like? This is Ade, and you're listening to Living Corporate. It's the remix. Zach: What?Ade: Thank you for joining us. [laughs] My bad. Today we're talking about reinventing yourself professionally, so I thought it was contextually appropriate. So the act of making a career change that is in-line with your long-term career goals.Zach: Oh, okay. Yes, gotcha. Yes. [laughs]Ade: Yeah. [laughs]Zach: This is really important though. Like, the concept of looking where you believe you're trending professionally and making adjustments. Sometimes they're major adjustments where appropriate. Speaking of which, Ade, would you mind talking to us about your journey to becoming an engineer?Ade: It's been a pretty rough, rough trip so far, and--I mean, some of it has been very enjoyable, and I mean that with all sincerity. I've had some amazing experience, but a lot of it has just been, you know, having to teach yourself a whole new--brand new field of knowledge. I like to describe myself as a learner, but having to teach yourself a whole new field of knowledge when you have nothing to base that field on is incredibly daunting. And I've had some, you know, technical issues, technical difficulties along the way, and I've also had some very, like, up at 2 A.M. in the morning like, "I don't think I can do this." Like, "I don't think that I am up to the task of making this switch," and that's not because I don't find this interesting or I don't find this, like, mind-meltingly awesome, it's that I just don't feel like I'm capable. And so those doubts always exist, but the fun thing about the switch is that in reinventing yourself you discover parts of yourself that you didn't know were there. And so it's difficult, it's daunting, but it's also really, really rewarding. Like, sometimes I get to a point where [inaudible] or my portfolio site comes together and I'm like, "Oh, my God. I did it. I did it, and I didn't--" I mean, yes, I used Stack Overflow more than once, but I did it, you know? You get that sense of accomplishment that you're not actually steering your life right off a cliff, and there's that duality of on the one hand "Am I even supposed to be here?" And on the other hand, on the days where, you know, you do feel like you're in the right room or you do feel like you're doing the right thing and you do feel like "I'm right where I need to be," it's this breathless wonder, I suppose is the best way of putting it, at just how dope everything can be.Zach: That's so cool. I know of a few people, right, who have made similar changes in terms of--not similar changes in terms of becoming an engineer, but similar decisions to kind of make a pivot, right, career-wise, and you know, I've seen people who have transitioned from being, like, HR managers to being fashion bloggers. I've seen--I have friends who have transitioned from being teachers to being full-time photographers. I've had friends who worked in the government and now they're, like, running intramural sports leagues. And I can't speak to the bag, like, how much money they're making, but I can say that each and every one of them seemed much more fulfilled in their day-to-day activities. And so, like, I'm really excited for you because you're going through a journey yourself, and I'm excited to see what the other side of that looks like for you.Ade: [laughs] So am I.Zach: [laughs] And I know that regardless of whatever, you know, ultimately it is, you're gonna be a better version of yourself coming out of it, so I'm really excited for you for that.Ade: Aye. And here's where we insert the celebratory Milly Rock. [laughs] But yeah, you know what? I think it would be super interesting to talk to someone who has had to professionally maybe reinvent themselves a couple times over, several times over. I'm thinking major changes, something like transitioning from education to car sales to, I don't know, stock brokering? To maybe pharmaceuticals to--hm, let's go with hospice care, and bonus points if this person was somehow related, in some form or fashion, to one of our Living Corporate hosts.Zach: Oh, you mean like our guest, my dad Ed Nunn?Ade & Zach: Whaaaaat? Zach: [imitates airhorns][Sound Man throws 'em in]Zach: Sound Man, listen, now. You gonna give me my pow-pow-pows, but then you also give me a couple pow-pow-pows 'cause it's my dad, okay? So pow-pow-pow. Give me a couple more.[Sound Man obliges]Zach: Give me some pow-pow-pows. Boy, that needs to be on a t-shirt somewhere. Anyway, keep it in. All right, so next we're gonna get into our interview with our guest, my dad Ed Nunn.Ade: We're back. Welcome to this portion of the show called the interview section. Y'all know how we go. So today we have the wonderful, wonderful, wonderful Mr. Ed Nunn with us.[Sound Man throws in cheers]Ade: Ed, welcome to the show.Ed: Thank you. Appreciate it, Ade. Ade: Most certainly. So for those of us who don't know you, do you mind sharing a bit of your background? Tell us a bit about yourself.Ed: I'm 53 years old, Midwesterner. Right now I'm married, living in--outside of St. Paul. Five children. One of them happens to be one of your colleagues, Zach Nunn.Ade: Yeah, yeah.Ed: His siblings are a bit younger. We have a dog. My mother-in-law lives with us here in the suburbs. Ade: Okay. I love dogs, so I'm not gonna, like, go down that line of inquiry 'cause I'm gonna sit up here all day talking to you about your dog. But that sounds wonderful. It sounds like you have a nice, cozy life with a nice, cozy family, which is something I definitely aspire to, but today we're talking a little bit about professional reinvention, kind of remaking your career, which is something that's near and dear to my heart, and the path to getting there. You mind walking us through your own 33-year journey to being who you are now?Ed: Mm-hmm. You know what? When you put it that way, there's a--I look back, and I think about it, and I haven't really thought about it until you put it that way. 33 years.Ade: [laughs] Right.Ed: You know, I recall when I first went to college I had an academic scholarship to Jackson State University, and I recall going to college, and honor student and all that stuff, and my mom had talked to me--you know, I remember taking these trips with my mom and dad and the family to Saint Louis and Mississippi and California, and every time we'd go some place, you know, she'd talk about these roads and these build--I'm sorry, these bridges, and she said, "You know, son, you can be an engineer. You could build these. You could design these." My mom and dad weren't--were not educated, didn't graduate high school, but their aspiration was of course for all of us to do much more, much greater things, and they poured a lot of expectations and resources, time, and love and all of that into us to do that. So I went to school and I was gonna be an engineer. Not a civil engineer, I decided I'd try my hand at being a mechanical engineer and found out that I didn't like engineering. [laughs] So instead of--'cause I went to Jackson State, transferred to Mississippi State, went back to Jackson State and finished up my math degree. So I graduated with a Bachelor of Science in Mathematics, and I said, "Okay, now I'm out. Now what do I do with that?" Thought about being a teacher, tried my hand at teaching mathematics high school for a couple of years, realized I didn't like that. Left that and went into working as a recruiter for a liberal arts college in the Midwest. Left that and became a stockbroker. Really, really changed gears there because we--at that time I was married, and we decided to leave the Quad City area. When I got out of mathematics and moved back home to the Quad Cities I started the recruitment for the liberal arts college, became a stockbroker and wanted to leave the Quad Cities just to--the idea of having a family and being able to raise a family in a more cosmopolitan, diverse--you name it. You can put anything you want, it wasn't the Quad Cities.Ade: Right. The stakes were different.Ed: Well, yeah. It was just different, right, and so we decided to go to Minneapolis, the Minneapolis area, and got up to the Minneapolis area and realized I didn't really want to start all over again building a book of business after three or four years of doing it in the Quad Cities, so I started working in the field of pharmaceutical sales. Left pharmaceutical sales, went into selling copiers and printing and multi-function devices. Left that and went into--well, previously I went to telecommunications, then to--no, I'm sorry, it was telecommunications after selling printers, and then I found myself at a point where I was just kind of burnt out, you know? I'm hopping from place to place, industry to industry, and not really finding what I'm looking for. It was okay for a little while, get bored. Literally get bored of it, and I took a break, flat out took a break. There was a place where the pharmaceutical industry dried up. A lot of reps--the companies were downsizing, and I recall--I recall talking to my wife and saying, "You know what? I'm tired of this." It really wasn't sales, it was walking in and, you know, pop-up ads all you were. You weren't having an opportunity to have a discussion with people around their needs and how to solve them.Ade: Right.Ed: So I took a break, and I just started my own little deal. I got involved with some guys that had an investment idea, and we formed a company and started--we're manufacturing, with some partners in Asia, some technology, and then we have formed a company to actually--a separate company aside from our investment. We were going to import it and start selling it to resellers, and I did that for a couple years, and it was good. I enjoyed it. We saw some growth, my partner and I did. That went awry because the original investor group kind of--they were at odds with each other, and there were some issues that came about, and so that kind of blew up on that side, which it then kind of obviously cratered the business that we had importing the product and trying to sell it to the resellers. And so there I am again thinking, "Okay, great, now what?" So as I sat there, you know, I recall a couple of weeks just saying, "Okay, what am I gonna do? What do I want to do?" I got a phone call, and this was the beginning of what I've been doing for the last few years of my life. I got a phone call from a hospice company, and they--I picked the phone up and the lady said, "Hey, you know, I'm looking for Ed Nunn." Said, "This is he." "Hey, Ed, I'm So-and-so from, you know, so-and-so hospice. Have you ever thought about hospice?" I said, "No." "Would you like to?" I said, "No." [laughs] "What I know about hospice is death. I--you know, I'm not there yet. I'm not ready to talk about it, I'm not ready to experience it, so I'm not really interested. Thank you very much." "Well, just keep my name, and if you ever change your mind please call," you know? "We got your name from So-and-so and we'd like to talk to you." "Okay, thanks. Goodbye." I hung that up, and my wife said, "Who was that?" So I told her. She says, "You know, you may want to think about that." I said, "Sheila, I thought about it. No thank you."Ade: Right.Ed: But I gave it a little more thought. I don't know what happened, but I gave it some thought. I didn't have anything else lined up necessarily. I didn't have anything in my mind I wanted to do, and, you know, after I thought about it, there's got to be more to hospice than just death. I mean, it's something we're all gonna do is what I recall thinking, and I end up wanting to find out more about it. So a couple days have passed. I pick the phone up and call the lady back, and, you know, a couple, three, four weeks later, I find myself hired by this company, which at the time was one of the largest, if not the largest home health care company. It was a large company. 60,000 employees here in the states. For what they did, they were a big company. And so I found myself in the world of--still in health care, but now in hospice, and I've been in hospice ever since. And that was 2012, I believe. So for the last six years I've been in hospice, working for three different hospice companies. The third one, you know, actually was purchased, and they decided to shut down a third of their operations in the country to kind of get control of five different platforms. It was just spread out too far, and they chose to shut down the two offices I was running here in Minnesota as well as the other 25 to 30 they shut down. And so I got tired of doing hospice for others, and I opened my own hospice company, and so right now I own part of a hospice company, and I'm still working for yet another one, doing sales and marketing for them here in the Twin Cities area. So that's me.Ade: Wow. So first of all, I want to take a break. [laughs] I want to, like, sit back and be like, "That was a whole lot," and I feel like I've earned it, but yeah, it sounds like you've gone through a process of constant reinvention and experiences that have built one upon the other. Not necessarily a 1:1 correlation there, but it does sound like you've had a wealth of experiences. Have any of them really stuck with you, or any feedback that you've gotten from the people around you, have those stuck with you to the extent that you've utilized those thoughts or you've utilized that process in other areas of your life, maybe in building your previous companies or in building this one?Ed: Yes. As a matter of fact, the very first time I stepped out into the world of commission-based earning versus, you know, an hourly salary or some hourly pay rather versus salary, just doing it on commission. The very first thing I heard was from my father, and he told me, "What are you doing? You need to get you a job that pays you a solid hourly rate and will just--" "You can pay your bills, and--what are you talking about, commission? You don't know what you're gonna make," and he didn't care that it was a--that I had just been interviewed and I was the first person of color in the Quad Cities to actually have a Series 7 to be a licensed stockbroker with the company that I was working with, and they had been there in one form or another--for 93 years been around, and he didn't care. That wasn't a focus. He was--you know, my father grew up John Deere and forging metal and grinding it and that kind of thing. He's like, "Better get you a job." [laughs] And so that experience, his objection to it, was so strong. I'll never forget it. I'm thinking, "You know what? You may be right, but I'm gonna try this," and it was the best thing I ever did, and I always go back to that thinking no--you really have to have faith in yourself and the things you do, and if you really are passionate about it and--you just have to believe in it and go for it, and I'll never forget that. As the first thing--the first time I tried to do something outside the realm of what my parents had kind of modeled for me, that was the one thing that--it stuck out, like, "Wow, okay. I'm out here by myself now." "You're on your own." But yeah, that one stuck out with me because--I kept that mindset. It was uncomfortable, Ade. It was very uncomfortable going from a known, you know, to the unknown in terms of my pay because yeah, you know, I had a house, you know? All these things you're doing and you need to pay for, and all of a sudden--*claps*--you know? You know, when they first start you out as a broker, you know--I started out, and they give you a pay, rather a salary, and wean you off of it, and the goal is to be a year, a year and a half or so, that you're 100% commission-based. Well, after the first three months, I was doing enough in commissions--my commissions far exceeded my salary, so after three months I said, "You know what? You keep your salary. I'll just go commission here on in," and it was the best thing I ever did. And so I look back and think about the fact that had I not done that, had I not gone through that, had I not weathered the storm of my father telling me not to do it and going ahead and doing it, I wouldn't have ventured out and done some of the things I've done in the last few years.Ade: Right. And you've kind of touched on it, but I do wanna backtrack and get, like, an explicit conversation about the motivation behind a few of these shifts. So you mentioned that a few of them were by necessity, but you made some jumps and you made some decisions that weren't necessarily necessities, they were just you making decisions based off of your own motivations 'cause you speak to those.Ed: Well, I've always found it odd that when someone would look at my resume, and this was--you know, I'm 53 now, so when I was in my mid-30s someone would look at my resume--'cause there was a time when, and I didn't mention this, my wife and I actually went to Japan for a couple of years and taught English. We just--we stopped it all and said, "You know what? We don't have kids. Before we go, we're just gonna go." To get started we're just gonna go to Japan, and we're gonna start and teach for a while and get an experience, but when you get back and you sit down with folks and they look at your resume, and they're looking for--you know, they're looking for [inaudible], right? Whatever that [inaudible] is, that's what they're looking for. I've got widgets over here. All I've got is widgets. Now, some of mine are yellow, some are green, but I don't have [inaudible], and I'm thinking, "Why are you looking for that? Why don't you look--and I know that you're looking for something in terms of what you're trying to do for this position. You want these qualities you want this person to fill, and they've got this list, but I--and they're trying to, you know, jam me into that, or jam anybody into it, and what I realized was that after a while--for a while [inaudible] I was frustrated because I didn't have [inaudible] and I didn't fit the mold because I didn't stay nine years here, I didn't stay five years there, and the older I got, the more experience I got, the more I realized that's fine, it just wasn't a fit. But while I was going through it it was frustrating, and so the decisions that I made to move, at first they were very uncomfortable when I was--you know, I'd move. I'd want to do something. It was intentional. I didn't like what I was doing, and my thought was "Why stay here? Just because I don't fit this mold I have to stay until I fit this mold? Who tells me--and when is it okay to move because I'm miserable here? How long do I stay here and be miserable so I can do another move here?" And I realized, "No, that's just not gonna work. If that's not a fit because of me moving, well, then that's not a fit, and I'll just keep moving." What I came to realize in the end was I wasn't going to be happy getting a job somewhere necessarily. It's gonna have to be something--and I know a lot of folks come to it on their own. It took me a while to get to it, you know, get to the fact that it was okay, it was okay to not be comfortable. It was okay to not fit the mold, and it was okay to go and make your own money your own way, and if you stumbled along the way, you didn't make all the money you thought you were gonna make, and whatever that stuff was in the middle that I was kind of, you know, letting get in my way, that was okay too because the goal was to kind of, you know, be true to myself, and I know it sounds kind of cliche, but I really was trying to find something that I didn't have, and so it was okay getting through all that to get to, you know, trying to be happy with what I was initially rather going to wind up with, which was a journey in terms of just feeling like I was accomplishing something, you know? For me and myself, because I tell my kids all the time, Ade, and I know I kinda strayed here, but I tell my kids all the time that my life is--my life, I identify myself by my family. I'm only doing what I'm doing because of them in terms of trying to provide for them, but if I'm not happy doing it then they're in trouble because I'm--[laughs] They're in trouble, so that being the case I need to be happy while I'm trying to provide and give them the things that I really want them to have just like my folks did for me.Ade: Right. Yeah, so, you know, I think a lot about the current trajectory for a lot of my friends, or for even me myself, and just thinking about how people map their three-year plan, their five-year plan, their seven-year plan, their ten-year plan, I think a lot of it is based in that community where it's [inaudible]. Ed: [inaudible]. [laughs]Ade: [inaudible], yes. It makes me think of, like, my dog chewing on my shoes or something. Now I'm scared that he's chewing on my shoes downstairs. [laughs] But anyway, I've noticed that for a lot of my cohorts, we rely on that continuity and will even, like, rewrite resumes, and we'll just, like, try to shave the edges off of the square peg to fit in a round hole. And it sounds very much that you were like, "Nope, the square peg is still the square peg," and so that process for you, do you have any advice for anybody who's navigating that current trajectory on their own, such as myself? How we should go about it, just kind of presenting your experiences and how that might--and how your experiences might help us or edify us in any way.Ed: You know what? The first thing first and foremost is get comfortable with the idea of being very uncomfortable.Ade: Yikes. [laughs]Ed: I mean, you know, you've heard the--you know, those adages, and you've heard, you know, "If you want to succeed," you know, "you're either burning the bridge or burning the boat that got you there," so you're stuck there, those kinds of things. You know, that's true. You--I'm not saying you burn your, you know, your contacts and you burn people, but in your mind you have to just get used to the fact that "Wow, I just did something that--" "Oh, okay. I let that go," and you have to be comfortable letting it go and not going back to it. You let it go for a reason, and you get--you know, sometimes you can get a--you know, you get afraid of where you're going 'cause you're not quite sure and you kind of want to hold onto some things, but I would tell you that number one, get very comfortable being uncomfortable. Number two, I would say that you're going to--even if you have that mindset, some of those personality traits--you know, the gambler type of personality.Ade: [laughs]Ed: Seriously, you know, that doesn't mean that the gambler is 100% certain of themselves, but just know that--[laughs]--when you make that call, you're gonna fall. You really are, but that doesn't mean you made the wrong call. Be comfortable, you know, with being uncomfortable. Know that you're gonna fall down along the way, but you have to stay true. You really have to have faith in what you've chosen and faith in yourself because I'm telling you this much, if you put yourself out there and you don't have this privileged mindset, you will make it happen for yourself. I can guarantee you. If you sincerely understand that--the mindset that, "You know what? I don't know what this problem--I don't know how to solve this one, but I will figure it out. I'll use my resources. I'll call some friends. I'll have these conversations." You do what you have to do. You talk to folks, and it'll come to you, but you have to know that when you put yourself out there it's gonna be challenging, but if you have serious faith in what you're doing--and if you don't panic, overly panic...Ade: So panicking a little bit is fine. [laughs]Ed: [laughs] It's fine. You're gonna panic a little bit, because, you know, there are times when I might need a good chunk of change to do something I'm working to do. I've got a few projects now I'm working on that have nothing to do with my employer, they have nothing to do with, you know, my children right now. They have a sibling band, and they have--you know, they're actually doing pretty good. They're starting to get going a little bit. They're actually featured on this season's America's Got Talent and that kind of stuff. Not featured, but they're actually gonna be on the show. I can say that because I was told I could. Ade: [laughs] I'm looking forward to rooting for them.Ed: Pardon me?Ade: I said I'm looking forward to rooting for them.Ed: Oh, I appreciate it, and I'm sure they would too, but I've got another project I'm working on that I've been working on for five years, and there are times I--you know, you have a money crunch. If you need--you know, and I'm not a rich guy, so if I need 30, 40, $50,000, or even $10,000, and I need it next week and I don't have it, you have to start being creative. "How am I getting this money up?" You know, I'm not looking to go borrow money and go into debt, and so you just have some faith that you'll figure it out. And, you know, you do. You really do if your mindset--if you condition yourself to knowing that, "Okay, I'm gonna hit some things that I don't know how to handle. I'm gonna hit some snags. Don't panic overly so. Just go ahead and--" You know, 'cause there's a process to it, and typically my process has been to put different things in play so I have different areas or different things I can go back to to help me out.Ade: Right, so basically having a backup plan.Ed: Well, not just a backup plan. I'm talking multiple things that are going on at once. You know, the idea of having just one source of income scares the snot out of me. I don't know how folks do that. They have one job, and I look at that and think, "You're one management change away from twiddling your thumbs," and I'm thinking, "How do you navigate that?" And I realize you might have your--a year worth of savings, or two years worth of savings, or whatever you've got in your savings 401K to survive and why you--but why do it that way? Well, you know what, if that's what you want to do, great. My thought is just--I don't see it that way. I just like to have a little bit more control.Ade: Sure, yeah. Yeah. So I'm definitely gonna be looking into other streams of income now because you just dragged me by my edges just then.Ed: That wasn't the intent. That wasn't the intent, but--Ade: Look, I take it with all the love and the good sentiments behind that one. [laughs]Ed: [laughs] Well, no. I mean, and it's not anything that's--there's nothing elaborate, you know? Real estate, you know? For 20 something years I've owned real estate, you know? From several houses and/or multi-unit buildings to individual, you know, houses, but that stuff, for the last 20 something years, has kept me afloat, and it gave me the opportunity to make the choices and say, "You know what? I don't want to do that." You know, right now I have a project where I'm building these--I build these quarter-scale cars, and these things are--these are, like, four feet long, and they're huge, and they're quarter-scale. I mean, these things are 50 pounds maybe. They have their functioning engines, whether the engines be eight-cylinder gasoline engines or nitromethane engines. They have working lights, doors, you name it. They're actually scale cars. These things sell for about--you know, they sell for a lot of money, so that's something I do on the side as well. Just a lot of different things going on that help as you want to make a change, and they also take up your time, but they're a part of the plan, because the plan for me has always been--I go back to what I'm doing this for. It's just to make sure I get this group of people through this to a point where they can, on their own, start navigating. That's my purpose. That's my plan. That's all I'm here to do right now. That's it, and so I'm taking everything I can with me that I'm using to do just that, period the end. Ade: That's brilliant. I think that it's important, you know, the thought you just elucidated, that it's great and it's a good idea to reinvent yourself, but you also should have something to fall back on while you do that because it's a good thing to take the leap of faith, but you should have a parachute.Ed: Oh, certainly. Well, if you don't, it's a hard, rough landing. [laughs] I've been there too.Ade: [laughs] Right. But yeah, I mean, thank goodness for, you know, parachutes because every once in a while taking that step of faith is just kind of like, "I don't know. That's a mighty long way down."Ed: But you know, you guys, you're much younger. I mean, I look at--I look at you and Zach and, you know, folks your age, and I say, "Wow, you don't have to worry about that nonsense, someone looking at your resume saying, "Gee, you know, you were only here for two years. You were only here for three years."" Ade: Right.Ed: You know, that's not a question that people are posing. That's not even a mindset anymore. Well, you know, 30 years ago it certainly was. The idea of stability was--it was different, and I look at that flexibility that you have to--you know, to shape yourselves, your careers, your destinies. I think you have--I think you have more flexibility. I think you--there's an opportunity, a greater one, a much more easy opportunity to do just that than I had. So I think that's really cool.Ade: Yeah, I really like that. I think those were all the questions that we have today. Are there any thoughts that you would like to share that we haven't gotten to? Anything that you really think would benefit us? Ed: I guess--let me ask you a question.Ade: Sure.Ed: Education-wise.Ade: Yeah.Ed: What is your education?Ade: I have a B.A. in political science and legal studies. I think I had a minor's in philosophy. I really wanted to go to law school at the time, and then I began a master's in sociology, the focus being [inaudible] science, but I never completed my master's, and I'm now working on a front-end nanodegree at Udacity. It's a Google scholarship that allows people to kind of learn programming skills, which is what I'm interested in. So I really, really, really, really, really want to become a software engineer. That's my eventual goal. I want to build my own apps, but I also want to work at--not a Google or a Facebook. I think those are way too large for my personality type. Maybe eventually. Right now, I definitely want to work at more of a mid-sized company where I get the mentorship that I'm really looking for and ownership of my products, honestly so I can be outchea. [laughs] No, I'm kidding. I mean, that is it a little bit. I think that--I think that I'm really invested in a bit of freedom, and most of the software engineers that I know and most of the jobs that I look at are like, "Oh, yeah, you can work 90% of the time remote," which to me means, you know, I can spend a solid 90% of my time coding on beaches, which I know you don't know much about me, but I'm very much a water person, so the idea of being able to do something that I enjoy in a place I enjoy really, really appeals to me. So I have that freedom, and my whole life isn't sitting behind a desk somewhere.Ed: So if I'm not mistaken, what I'm hearing you say is that this education you're pursuing, you're doing so in order to gain some freedom in life and control.Ade: Yeah.Ed: Okay. If you didn't have to work, what would you be doing?Ade: If I didn't have to work, I would own a restaurant. Ed: You don't think that's work?Ade: No. [laughs] It's funny. I actually don't know if we'll keep all of this in the conversation. I don't know. Where is this going? Ed: [laughs] I'm asking the question 'cause you asked me--I'm getting somewhere. I'm going somewhere.Ade: Okay, okay. If I didn't have to work, I would have a restaurant. I actually have a book of recipe ideas and meals that I want to cook. The idea is to have a restaurant that is diasporic, so all of the food in the restaurant would from the African diaspora, from West African, East African-inspired meals to the Caribbeans to Latin America and meals that are typically in Afro-Latino homes. Just everything that brings us together as one community. I'm very much a community-oriented person, and I think that--to me, one of the most beautiful things about the diaspora is how similar but different food is, and Anthony Bourdain, who was, like, one of the, like, biggest influences for my love of food and cooking and people, had this thing where he talked about food being the center of humanity. Like, once you talk about a people's food, you're talking about people. So culture is built on that, and I could wax poetic about this all day, but essentially I'd be cooking. I'd own a kitchen or a food truck or a series of them and just feed people, 'cause I'm African and that's what we like doing. [laughs]Ed: So here's my question to you, and I mean, it's--you know, I listen to you talk, and the last couple of minutes have been real talk from you. It's been--I can tell it in your tone. I can tell from the fact that you have this knowledge about, this breath and this passion about it. I marvel at that because I'm wondering, "Okay, so how many of these changes are you gonna take yourself through before you say, "You know what? I'm ready for that change now.""Ade: Yikes. [laugh]Ed: Because I have a couple things that I'd like to do for me, and I'm 53, and I'm working towards them. One of them I've already started, with these cars. It's a passion. I love cars, and I like the idea of control or whatever. You know, life is extremely obviously random, but however you can eliminate some of that randomness--but that's one of the things I want to do. It's just taken a long time to get here. Dealing with my family, working with my family and having my kids and my wife around, that's something that I've always wanted to and I hold dear to. So the idea of working with them with their music career right now, that's really big for me, but it's taken a long time to get there. Some of that--well, I didn't have a family, you know, 30 years ago like this, but to get to something I really love--you already knew it, or know it rather. I didn't know 'til I got here. You already have something that is really, really dear and tender, and I'm listening to you talk about this nano this and this MBA that and this wizzy-wazzy this, and it was just interesting, and then when you started talking about the food I'm thinking, "Okay, this is real for her," and I'm just wondering: What are you gonna do, and when are you gonna decide to do that?Ade: It's funny that you ask because my partner is a tax lawyer, and her thing is constantly, like, "We need to get a food truck for you,", right? [laughs] And so I think that it's definitely something I want to work towards within the next five or so ten--five to ten years because I think that for me it's the security of the job, because, for example, I kind of provide for my family as well, and it's difficult for me to take a leap of faith with, like, a mini-parachute on my back when I know that, like, there are people who are relying on me to not break my legs on the way down, you know? So that's always--that's the fear. So there's the passion behind the cooking, right? And it's like--I'm definitely not gonna die without putting at least a plate in front of somebody's face and like, anticipating the look on their face when they eat it, right? But I also know that the amount that I have to lose right now is keeping me--is what's keeping me from it. So I think that the process of reinvention for me has to start from a place of absolute commitment, not a place of one foot in the commitment and one foot in the fear ,if that makes any sense. Yeah. Fingers crossed, man. [laughs]Ed: [laughs] Well, I just--I'm looking forward to hearing your story later when both feet, you know, finally land on the commitment side, and I'm wondering if it'll be the--you know, the pain to change was less than the pain to stay the same is what they say, right? So I'm just wondering what's your motivation, what actually gets you to that point? I realize you've got other things, that your people are depending on you. I got that. Hey, I got the same thing, and it's always interesting to hear what people's story is, what their story is, because I've gone through it too. So I'll be looking to hear the end of this one.Ade: Most definitely, and I'm looking forward to, like, feeding you at some point. [laughs] Putting a plate on your table, and hopefully I've written, like, my own e-commerce platform or something of the sort, so merging those two loves.Ed: Well, I've got to tell you this. I've listened to you guys with this Living Corporate, and I was--I've got some friends who listen to it too, and we marvel at it because--Ade: Really?Ed: Yes, yes. I think it's--I think it's relevant. My wife thinks it's extremely cool, because I think you guys have hit upon something.Ade: Thank you.Ed: Well, we think you've hit upon something because, you know, the idea of this--it's one thing to acknowledge, it's another to accept. And, you know, what you're doing is not new with respect to wanting, you know, this acceptance, not just acknowledgement in Corporate America for different peoples. But you guys have been able to reach beyond walls of these companies and connect it with this technology and have this conversation. And, you know, I've been at different companies, large companies, you know? A lot of them. You know, Xerox, Lilly. Some big companies, and within the walls, yeah, there's a lot of acknowledgement of different groups of people, and these different groups are formed, and they can have a platform of some sort, but typically in the past my experience has always been it's been a pat on the head, right? "Yeah, that's nice. That's nice. You guys go over there in the corner and talk, and I'll take it back to the board, and that'll be that." [inaudible] "I'll take this report that you guys had a meeting back too. That'll be nice," but you guys have decided that "No, we're not gonna center it in one particular place. We're just gonna put it out here for everybody," and you've taken this technology and taken this conversation to a different level, and it's so relevant. It's because it's now something that isn't confined to somebody's little bitty, you know, pat on the head from the corporate leadership. No, this is real, and we get to talk about this stuff, and we need to talk about it. And so I look at Living Corporate and say, "My God, that's a really cool idea. Man, they--talk about hitting on something that makes sense," and I enjoy listening to it. I enjoy listening to you guys. Your platform, the way you guys put it together, the music, the artwork - it's cool.Ade: Thank you. I really appreciate that it's making this much of an impact, and we've certainly been getting, you know, great feedback from people, and we really appreciate all of those things. So before we close out, do you have any final thoughts, anything that you'd like to share? Any shout outs you'd like to give? Whatever. The floor is yours.Ed: A big shout out to NUNNABOVE. That's the musical group that Zach's siblings have formed. They've been together for a few years doing their music together. They're young, they're young, but I ask that you check 'em out on America's Got Talent and support 'em, and a big shout out to my wife. She doesn't know that I'm gonna shout her out here, put her out here, but, you know, I mentioned--I mentioned all that changing and all those decisions I made to do different things to support my family. Without my wife there to be the support, it wouldn't have been able to be accomplished. I couldn't have--I couldn't have made the decisions and actually made them work without her. Not someone like her, but her here taking care of the things that needed to be taken care of in--you know, within the walls necessarily when I'm out trying out to figure out and knock down--you know, figure out a new path, knock down trees and break up big rocks. It makes it easier if you've got someone that can--that can do that for you. So a big, big, big shout out to her, big shout out to you guys, and seriously, I know that I don't need to do that 'cause you guys are--it's your show, but I'm just very proud of the fact that he's part of this effort that you guys are bringing forth.Ade: Thank you. Thank you very much, and I'm definitely gonna, like, hit him up like, "Your dad is the coolest ever." I did tell him that you were dragging me though. I informed him.Ed: That I was what? I was what?Ade: That you were dragging me. Like, you spent a solid chunk of our conversation today just, like, tugging on my wig all the way through. [laughs]Ed: [laughs] Well, it wasn't intentional. I just--but I do appreciate it, and you guys--I love the website. I was telling Zach there's some things that you guys are doing, the fact you got some pictures, and the way you guys have set it up, and I love the fonts. I love just the look and appeal of it. This is a really slick--I love the sound of it. When I listen to it, it makes you--it makes you want to listen. You want to engage. Like, "Okay, what did he say? Let me back that up. What did [inaudible] say? What? Oh, that was pretty cool." Ade: [laughs] Okay, I have appreciated the full length of this conversation. I am telling Zach about how amazing all of this is and how we're probably gonna have to put this on our Patreon 'cause people can't get this one for free. Thank you for your wisdom. Thank you.Ed: Thanks, Ade.Zach: And we're back. Hey, Ade. That was a great interview. I really enjoyed that. The themes that kept popping up to me during your conversation were intentionality, comfort with being uncomfortable, and courage. It was really good.Ade: Uh... so I'm confused. Ed, why are you here? We're in the wrap session of the show. You can go now.Zach: Oh, you got jokes.Ade: Yeah, actually. Yes, I do. [laughs]Zach: [laughs]Ade: 'Cause y'all sound exactly alike. It is so weird.Zach: We do sound alike, which is why I knew we couldn't be interviewing, like, together. Like, I couldn't interview him. It would sound like I was having a conversation with myself.Ade: Facts.Zach: But eeriness of that aside, I love the fact that he was able to be on the show. He and I, we have these discussions all the time, and he's really the reason I'm so comfortable trying new things.Ade: Yeah. I mean, I definitely got that sense from him. During our interview, I was taken aback, and dragged, quite a few times at just how fearless he seemed to be. He made so many different transitions and changes and jumps and leaps of faith over the course of his professional career. It was actually kind of scary. Zach: Yeah. I know, right?Ade: But, like, at the same time, I think I learned that your plan doesn't need to make sense to anybody but you, right? 'Cause you're the one living your life, and--I mean, when he was talking about his parents discouraging his shifts and those transitions, I could definitely really--'cause, you know, you can't explain your plans to everybody. Sometimes people side-eye you like, "Sis, you sure?"Zach: Right, and it's all about like my dad said, following your passions and going for what you feel is right. I mean, we're here right now doing Living Corporate and embracing discomfort and uncertainty. High risk for sure, but great rewards.Ade: No, I definitely agree, and it's also interesting that your dad was definitely job-hopping and forging his own path way before it was trendy, like millennial trendy.Zach: Right, and, you know, he really wasn't wrong then, and he isn't wrong now. I mean, look, if you look at this 2014 article from Forbes, it says that employees who stay in companies longer than two years get paid 50% less, and I know there's more value than just your paycheck, but also there's value in being bold and taking control of what you need to get where you believe you need to be.Ade: Right. So honestly, I'm excited for us to drop the extended interview on our Patreon. By the way, Sound Man, give me some slow jams real quick while I hit them with the super ASMR voice. Guys, check out our Patreon. You want more content, right? You want exclusive stuff? You want giveaways? You want to hang out with the Living Corporate team? I know you do, so go ahead and go join our Patreon. The link will be in the show note. Thank you.Zach: Oh, my God. [laughs]Ade: [laughs]Zach: Oh, my goodness. (laughing) Anyway, major shout out to Ed, my dad, and I hope he can join us again soon. Let's get into our next segment, okay? Favorite Things, where we talk about what our favorite things are these days.Ade: Yep. My favorite things right now are--I'm really into Miguel. I have been listening to some of my favorite Miguel songs lately non-stop. Candles in the Sun is, like, top 5, top 5, top 5 of all my favorite songs. So I've been really into his entire discography, and I've also been really into hiking. So I have a puppy, and he's a husky, and he needs a lot of, like, physical activity, and I'm training for this marathon, and just being able to get out and really be active and get outside and kind of commune with nature and exercise my hippie-dippie side has been really, really fun. Hurts sometimes 'cause my knees like, "Sis, we're getting way too old for this," but it's been--it's been really great. What about you?Zach: That's really cool. So my favorite thing right now has to be my sibling's band, keeping with the family theme of the show.Ade: Right. Why didn't you tell me you have whole rock stars in, like, your family? Like, bro, what?Zach: I know, right? And so I don't know--like, by the time this episode releases if we'll already have seen them on America's Got Talent, but yeah, I'm really, really proud of them. I love them. They're great, but yeah, so they're called NUNNABOVE. They do funk, pop--Ade: Yes.Zach: Yeah. Like, my oldest sister--my oldest little sister Cadence, she's 18, and she plays the bass and she does lead vocals, and then my second-youngest sister is Maddie, and she does keys and vocals. And then my oldest little brother Bennett plays guitar, and he also does vocals, and then my littlest sibling, my little brother Wisdom, plays drum set, and they're all great. Like, they're super talented, really cute. I love 'em. They're awesome.Ade: I want you to know that this is a setup. They had no choice but to be rock stars with names like that. Cadence? Cadence?Zach: (laughing) Yeah, Cadence.Ade: Your dad knew what he was doing. See? Setup.Zach: Yeah, yeah, yeah. Strategist, strategist. And so what we'll do is we'll make sure to put their information in the show notes so you guys can check them out as well, and yeah, we'll make sure to link all that up.Ade: Awesome. And as a reminder, to see all of our Favorite Things, go to our website at living-corporate.com and click on Faves. And that's our show. Thank you for joining us on the Living Corporate podcast. Make sure to follow us on Instagram at LivingCorporate, Twitter at LivingCorp_Pod, and subscribe to our newsletter through living-corporate.com. If you have a question you'd like us to answer and read on the show, make sure you email us at livingcorporatepodcast@gmail.com. Also, don't forget to check out our Patreon at LivingCorporate as well. And that does it for us on the show. My name is Ade.Zach: And this has been Zach.Ade and Zach: Peace.Kiara: Living Corporate is a podcast by Living Corporate, LLC. Our logo was designed by David Dawkins. Our theme music was produced by Ken Brown. Additional music production by Antoine Franklin from Musical Elevation. Post-production is handled by Jeremy Jackson. Got a topic suggestion? Email us at livingcorporatepodcast@gmail.com. You can find us online on Twitter, Facebook, Instagram, and living-corporate.com. Thanks for listening. Stay tuned.