Nerd Journey

When does a body of work reach completion? One answer is to end it by choice. This week in episode 356 you’ll hear the reasons behind our intentional ending of the Nerd Journey Podcast. We’ll rewind the clock and focus on the show’s trajectory and inflection points over time just like we’ve done for guests, share what we learned over the course of an 8-year journey from idea to consistently released show, and discuss our favorite moments. All of our content will remain online and accessible for listeners like you to go back and enjoy. Don’t miss our final call to action in this episode. Just because this body of work is complete, there is still work for all of us to do for our careers. Original Recording Date: 12-20-2025 Topics – A Purposeful Ending, Where We Started, Interview Format and Getting to Launch, The Why Behind the Ending, The Lessons We Learned, Our Favorite Moments, What to Expect from Us Moving Forward, There’s More to Be Done for All of Us. 1:01 – A Purposeful Ending We’ll give you the bottom line up front: this is the last episode of the Nerd Journey podcast. We still love the mission, but the time has come for us to complete this body of work. When we have interviewed guests on the show, we’ve talked through their career timeline and pulled out the lessons learned. Today, we’re going to do it for the show itself. 1:38 – Where We Started John was working as a sales engineer at VMware and was the co-host of the VMware Community Roundtable Podcast. He loved listening to podcasts, enjoyed the medium, and wanted to find a topic for a show. At the same time Nick was in the process of joining VMware, John and Nick were discussing all the things Nick needed to know to transition into sales engineering for a technology vendor. “In that conversation, I said ‘maybe we should start a podcast.’” – John White As Nick remembers it, this happened the weekend before Nick started at VMware in December 2017 (almost exactly 8 years before this episode’s recording). Nick wasn’t sure what he would talk about on a podcast. This suggestion from John started the ideation period, and our launch of the show was in July 2018. John talks about some of the initial ideas for the focus of the show. At that time, VMware podcasts and blogs were a great way to interact with the greater community. Doing something like this was also a way to become what John calls “nerd famous.” By the way, no one else can use that term now (trademarked by John). We initially considered talking about VMware news and our opinions on it since we both were going to be working at VMware. Both John and Nick came from small-to-medium business IT operations and eventually became sales engineers at a technology vendor. One of the things the show could be for is to talk about that journey and help others understand it was a possibility for them as well. John and Nick recorded about 10 episodes before launching to help hit the release cadence. Nick doesn’t remember why they chose a weekly release cadence but remembers the show launched while he was on vacation. John and Nick even recorded a podcast episode while Nick was on that vacation, which started a habit of Nick doing podcast work while on vacation. Because they had recorded so many episodes in advance, they were not going to be timely or points of authority on VMware technology. Both Nick and John’s roles were as technical generalists on the VMware side. “The only evergreen stuff that we had was the career stuff, so that became a little bit more the focus. I think that we were still thinking…we’ll just record more maybe VMware specific stuff later on…as that happens. For right now, here it is.” – John White Early episodes were very prescriptive about resumes and job interview processes at larger tech companies, for example. Nick points out that John had to carry the conversation in these early episodes because he was just learning to think about career focused topics (sort of like being new to lifting weights). But, Nick picked up a lot just from the conversations on the show. 7:50 – Interview Format and Getting to Launch Nick couldn’t remember what made them bring in guests originally, but Episode 13 with Tom Delicati was our very first guest interview on the show. John feels bringing in guests was always back of mind for him, and it was what he saw happen on the VMware Community Roundtable Podcast. “We’re just 2 people and we have our experience. But we can’t represent that as the full breadth of all of experience. That just doesn’t make any sense. So, we need to start exploring what other people’s career journeys have looked like and see if we can extract some knowledge and recommendations from that.” – John White Nick doesn’t remember having a prescriptive plan for interviewing guests but feels like they settled into long-form interviews as a style pretty quickly. John says this was a structure they hit upon in the beginning (talking through someone’s job history). The lessons learned from career inflection points like job transitions emerged from conversations with guests. John and Nick did not know this was going to happen when they began. Nick likes being able to highlight more of one specific guest’s story than otherwise could have been done if each interview was only 30 minutes with a guest. But we fully acknowledge people like different lengths of podcasts. “We wanted to tell interesting stories that had an arc: a beginning and an end and a journey in between. And we were able to find those even chopping people’s long 2-hour conversations up into 2 or even 3 episodes. I think that worked for us. I don’t know if it worked for everybody.” – John White “We probably spent the same time interviewing people as we would have. We just didn’t interview as many as if it had been 1 episode per person.” – Nick Korte We also didn’t want to release a 2-hour interview as one episode. That’s a lot of editing for just one episode release. People might not realize how much time goes into editing and production even after recording an interview. At the beginning, John had to give Nick advice on the kind of microphone to get. Nick started recording with a headset and then bought the same mic as John. They would each later invest in nicer microphones as the show progressed. “I knew nothing about editing and really not that much about how to make a podcast.” – Nick Korte, on beginning as a podcaster There were a lot of things we had to figure out just to make the podcast publicly available. John had researched some of the administrative things. He knew there was a WordPress plugin that could be used to turn MP3 files of released episodes into publicly available audio feed that would be the podcast. John says there were some mental blocks and hurdles he had to get through before launching the show, highlighting the fact that it took 6 months to go from idea to publishing. He was getting overwhelmed trying to figure out the back-end production and publishing process. John thinks it was Nick who kept asking what needed to happen for us to launch, and we went with WordPress and the plugin mentioned but never changed anything…because we had no time to go back. Nick and John learned that once you start a show and get it going, you will never run out of ideas. 13:58 – The Why Behind the Ending We never ran out of ideas. In fact, we still have ideas. So why are we stopping the podcast? We ran out of time. Nick has run out of time to work on editing and production. This has been a weekly show (up until the last couple months of our run), and it takes a large time commitment each week. For guest interview episodes, the intro and outro were not recorded at the same time the interview took place. These had to be recorded before the episode was released. The show notes are not AI-generated. Nick enjoyed writing them and adding in important links and references, feeling like it allowed him to remember the episodes better and internalize the lessons within them. Nick has a teenager now with many extracurricular activities and has had a workload increase at his job. “Probably for the last year I think I’ve been fooling myself at how much of a toll it’s been to just get an episode out each week.” – Nick Korte We even tried changing the release schedule to bi-weekly and have missed that cadence a couple of times. John ran out of time about 4 years ago and hasn’t had much time since to handle podcast related tasks. John experienced a job change and new baby at that time and couldn’t add anything else. He also moved at some point. John and Nick have been advancing in their own careers over time as well, which has added responsibility. John and his wife recently had a second child. He also left his job in June 2025 and has been doing a job search at the same time. Before Nick and John made this decision, Nick listened back to some previous episodes to get advice and perspective. Some of the advice that echoed the loudest came from Amy Lewis in Episode 302 – Ending with Intention: Once a Geek Whisperer with Amy Lewis (2/2). The idea of ending with intention stood out. “Rather than being spotty on our releases and not keeping our promise of how often we say we’re going to get the show out, we wanted to end it with intention and say, ‘ok, this is it.’” – Nick Korte “We haven’t lost the love of this task. We both want this to continue. But realistically, we can’t do it. And rather than sputter and peter out and never be heard from again, we just thought we’ll follow the lessons that we’ve learned from our bettors and do what they did. Let’s be intentional about the end.” – John White 18:02 – The Lessons We Learned John learned how much we can learn from the experience of others. He had ideas and biases about how we should h