Detailed Notes
Want your work to matter long after the last commit?
In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche revisit their classic conversation “Your Developer Journey – How to Leave a Lasting Legacy.”
Here are some of the actionable steps to create a developer legacy that stands the test of time: • Writing clean, maintainable, well-documented code • Publishing open-source projects people actually adopt • Mentoring teammates and fostering a collaborative culture
Whether you’re a junior engineer or a senior architect, you’ll learn how to build code and culture that outlives you.
👉 Subscribe for more developer career insights and practical software advice. 🎧 Full podcast feed: https://develpreneur.com/developer-legacy/
*Follow-us on:*
* [email protected] * https://develpreneur.com/ * https://www.youtube.com/@develpreneur * https://facebook.com/Develpreneur * https://x.com/develpreneur * https://www.linkedin.com/company/develpreneur/
#DeveloperLegacy #CleanCode #OpenSource #Mentorship #BuildingBetterDevelopers
Transcript Text
[Music] We got talking things, talking points. I hit record. Uh, let's see. >> We are live sort of. >> Here we go. >> It's live. All right. Um, gosh, started off. We're already off the rails. So, we've got this episode, I think, is going to be the last one of using AI with that season. I think we want I think what we want to do is just go ahead and instead of like AI on the the wrap-up, I think it'd be worth us to the next one will be then to have at least one and maybe two. We'll see how it goes. I think at least one episode that's like our wrap-up episode that's sort of like okay let's think back about what you know a little bit of like little retrospective of how did this work how did this go what did we like about AI what don't we like about AI and all the fun stuff that's out there because I think that may be um a pretty cool one I'm gonna shoot let's see I don't have the best light here I guess it's not too bad I have a little bit a glow. Let me see if I can smooth here. So, hold on. This may give me a little more natural lighting and such. I probably should drag like a lamp in here, but oh well, we'll go with this for now. Okay, so I'm just >> Yep. diving right into my postworkday drinky poo as some people would call it. >> Have you tried this yet? >> The I'm not really a Jim Beam fan. >> Uh, so this is their black label and uh I wasn't My mom was a big Jim Beam fan, but I didn't like the original mash. This is uh I really like this one. I've been drinking it for a while. I might have to try that one because yeah, dad was always that was one that he drank regularly and I've had I've had it over the years and earlier on when I was younger it was not that big a deal. I was like, "Oh, okay. It's not bad." But I've become a little more snobbish about it as I've been going through all these different things. So, I have like It's like everything I've gotten more so >> really more so what I'm drinking is about the taste and the flavors and the certain things that I want as opposed to um you know, anything else. So, I've gotten much more digging into the various flavor profiles. >> To be fair, >> yeah, to be fair, this is I I barely drink this straight, but this is a very good like mixing bourbon. >> Oldfashions and things like that. Like Eagle Rare when I can get it is like my go-to. Um, which is funny because since I do live out in the middle of nowhere, interestingly enough, a college town just 15 minutes south of me, uh, which is a dry county, you have to go to the border, uh, they sell the magnums for $89 and I can't even get the little bottles for $89 if I go to Jackson. So, it's like, wow. Okay. So, uh, I I wait till I can find those and then, um, of course it's limited to one, but still one magnum will last me about a month. So, it's pretty good. >> Let's see. Sorry, I got sidetracked by sidetracked by one of our customers sending an email. Okay. So, serious note there. Sorry. I like just got myself as I was shutting stuff down. I was like, "Oh," or actually not really. Well, I guess this is shutting stuff down. Plus, make sure I Come on. Stop. There we go. Quit. And I want to go to do not disturb. I'm just way off today. This is just one of those. Okay, we'll do it for an hour. We'll see how long we last. Um, I think we're just going to dive right. Let me move this around so I can actually This is a bonus of having my m my my screens my screens configured this way. And so, okay. So, let's see. So, we're going to do how to leave a last name legacy and then we'll see where we go from that. Um, yeah, I think that'll be sort of cool because it at the very least we'll either come back next time around and we'll be doing yet another wrap-up episode for this season or we'll maybe we'll just honestly and maybe we'll just like use chat GBT and say what would be a great conversation point. We'll just like list all of the stuff we've done and say what would be a topic for us to cover and see what happens. >> Oh, so you haven't been keeping these in like a folder? not all of the all of the seasons. >> Okay, >> I've got it. >> So, just small AI tip for those of you watching the pre-show. If you create uh Chat TPT has this new feature, even in the free one where you can now do folders, uh if you put all your chats into that group, they treat it as a project and you can have it scan all of those uh under a certain criteria. So, it's a very interesting way to quickly summarize or review what you've are kind of working on throughout your project. >> Yeah, I was thinking No, I'm actually looking at that go because I wanted to see uh I think that's what I want somewhere. I have a way to do Where did it go? I may have lost it. Um, oh, it's in categories. My bad. Okay. Um, what it was? I want to go grab all of the titles of all of the seasons that we've done. Not episodes, but actual seasons and say, "Hey, this is what the development podcast has done. What would be a cool season idea?" So, maybe we'll even do that to wrap up the next episode, but I get ahead of us a little bit. I don't know if we can what can do uh so there is a way if you install the chatgpt app I think you can have it scan a folder but I have not tried that I think because I have seen it integrate with like things like PyCharm Intelligj uh Eclipse like if I have that open it's like oh you have this open do you want me to integrate with what you're using uh and it lets me uh but I think you can do that against a file system I'm Not 100% sure though. >> Yeah, I think I can just do it actually. Okay, now I'm I'm curious. So, let's see if we do this. I want to just like cheat here in a second. Where is it? Is at. Okay, so let's go over here. Um I want to go over here. Um >> on a side note, uh when we do get to the episode at the end, let me know what you think about my new intro. I'm switching it up a little. Oh yeah, I gotta put Thank you for reminding me that. Let's see. So for the Okay, past seasons, >> we might have to keep the bonus bonus to a minimum. >> Yeah, I know. We're going to be a little bit here. So, let's see. What would be a good new season for the developer podcast? Okay, I'm going to spit that out. I'm going to come back because I want to go back over here to get the thing up that I'm working on. Let me get this document up so I can think about what I'm thinking about. Where did that go? There it is. Cool. Okay. All right. Let's get let's just get it going here. All right, do uno. Hola and welcome back. We are continuing and almost wrapping up our season where we are taking a past season, going through the topics, throwing it out to AI and saying, "What do you think? What should we have done? How could we have done it better?" Most of the time AI does give us some more things to talk about. I don't know if it's better. Uh sometimes it goes in a very different direction. We'll see where it goes today because we're going to be talking about uh this was the last one of that season which was your developer journey. How to leave a lasting legacy. Uh I can almost guarantee it's going to give us some different thoughts on this because we have keywords that it's probably going to go differently. Before we get into that, I should introduce myself and then I'm going to let him introduce himself. See, I'm not even giving his name out. My name is Rob Broadhead. I am one of the founders of developing also the founder of RB consulting where we help businesses assess and simplify their technology. From there we build clear road maps and we help you full grow fuel growth. We help you to move forward. We help you to figure out how to take where you're stuck. You know your wheels are spinning and then we find a way to put a little leverage in there and get you going. We do this by sitting down with you, understanding your business, helping you craft a special recipe, a unique recipe for your business, that roadmap so that you can move forward leveraging technology through simplification, integration, automation, innovation, all of the shuns that are out there. We help you do business better. And check us out at rb-sns.com. We also have like we've got some deals going on there. We've got some like insta assessments out there. And even you can do a self assessment. Go out to matrix.rb- rb-sns.com. Check it out. Let us know what you think. Good thing, bad thing. Uh, bad thing was, and I don't know if I'm going to tie it to a good thing yet, uh, I was I was on a call today, sitting there like deeply into this conversation, worked great, got done, and I suddenly realized it was pouring outside and I'd left a couple things out on the porch that I was like, ah, probably shouldn't have. So, I had to go throw them in the dryer and things like that. So, lesson to you kids, make sure you're keeping an eye on the weather before you like go heads down for a bit. Good thing um and this is actually I think I've I've mentioned this before is like I'm in a little bit of a a more quiet time in business. I'm not spend I've been able to extract myself from working in my business quite so often and so I'm able to work on my business and that has been awesome. It has been so good to be able to knock out some of my to-do list items. to upgrade. You can go check out the RB Consulting website. We've definitely done some upgrades there. We've been tweaking stuff. Uh added some products. We're like finishing touches here and there. And this also means it will spill over to developer soon enough. I've been already delaying with some ideas there and starting to work towards making that more uh bringing it current and also making it easier for you to utilize the huge amounts of content that we have out there. But first, you're gonna have to meet my co-host. Go ahead, introduce yourself. >> Hey everyone, my name is Michael Moash. I'm one of the co-founders of Developer, Building Better Developers. I'm also the owner of Envision QA where we help businesses take back control with customer soft with custom software that's built around their needs, not the other way around. Our focus is simple, great service, smart solutions, and a rockolid quality. We build tools that replace frustrating systems, streamline operations, and are fully tested to work right the first time. At Envision QA, we combine development and quality assurance to give you software that you can trust and support you can count on. Check us out at envisionqa.com. Good thing, bad thing. Let me start with the bad thing. Wife had to take down the pool today. Uh it was uh she's a bit depressed cuz, you know, it's finally cool enough. It it's just not worth keeping it up anymore. Uh, good thing fall is here sort of. Uh, the days are getting a little bit shorter. Uh, the trees are starting to change color and if it wasn't just on the other side of hot today, it would have been a perfect day to sit outside and work all day. Those are good days. I would not have had a perfect day because I would have been rained upon as mentioned before. Well, let's dive right into it. So, this episode we are going to go with, as I mentioned, the title was your developer journey. How to leave a lasting legacy. Uh, chat GPT, we're back to that. It came out right away and said because it loves us. Great title again. Wow, we are just knocking them out of the park. Uh, you can really connect with developers who want to think beyond just writing code and start shaping something more uh something meaningful in their careers. Here's how you could structure and enrich that episode. So, let's see how we structure and enrich this puppy. Uh, part one, introduction. What does legacy mean in software development? Legacy is more than old code. It is about lasting impact. Contrast getting tasks done versus building something that outlives you. Why developers should care about their professional legacy. Now, this honestly I don't remember us ever really getting into this before. I think we've talked a little I think it was a little bit more about mentoring and leading and passing it on to the next generation but this is actually really uh a cool direction for AI to go with it because I I think it is an area that is worth discussing. Um one of the things we've talked about a lot is building your scratching your own itch building applications to help you to help your utilities to help you other developers all those things. And it's also a great way to grow uh professionally. You can go test out new technologies and approaches and different areas of code. Maybe like maybe normally you're not a tester, but you get to do some testing. Or maybe normally you don't do UI, but you get to do UI. Uh the I have these conversations with my team on a regular basis where it's like, hey, you can go work on this project and do this thing and that's going to help you be able to actually like dip a toe into an area that you you want to understand a little bit better. I like the idea of uh and again I always like this getting tasks done versus building something that outlives you. This really goes to work ethic. This really goes to what we want to do is we want to build something that people are going to use. I don't think any of us really want to build something that somebody puts on a shelf and they're just like, "Okay, I bought the software and I never use it." It it has frustrated us because we probably have invested our time, blood, sweat, and tears into it. We want them to use what we're what we've sold them. We really I think most of us would be rather we'd rather like earn less money out of it and have them use it all the time than be able to retire on it and have them never use it. Now, I know there's a point where you're like, I'll take the retirement, thank you very much. But there's very much an idea of we don't want people that's our whole point is for so people aren't throwing their money away that they're buying something of value that we're giving the value of our time and our intelligence and our ability to problem solve and they're returning the value of you know whatever they paid for. And I think that's that's very critical to it's like our why. It's very critical to keep in mind while we're doing software development is to basically say look we're not here just to write code. We're not here just to like play around with the latest technology. We're really here to solve problems. We're really here to help other people become better. Their businesses become better through technology and through the skills that that we bring to the table. Thoughts on that? or actually other ways you may want to go just like AI that was completely in a direction we haven't been. >> So, I'm going to since I'm a gamer, I'm going to start out with think legacy. All right? If you think if you've been around more than a decade or two, especially with games, you you look at what's been around for a long time. Pac-Man, Donkey Kong, these are games that are legacy games. I mean these this is software written in the 80s that is still around today. It's still being enhanced upon. It was simple. It was great and it has withstand the test of time. The our legacy can be twofold. It can be software that we've written or it could be how we handle a situation or how we solved a problem not just for a customer but for anyone we've worked for a company we've worked for um our friends whatever as you were talking about this topic I I was thinking back to a company I worked for a couple jobs ago they're still using software I or test software I wrote and it is the only way they're able to get the job done. They have not found a solution that can replace what they're currently doing. So there are times when you're working to solve a problem when if you really have the mindset of anything I do I want to do right the first time. Now, that doesn't mean that you have to write perfect code every time, but the intent is what you're putting together is a solution that could really withstand the test of time. You write something so good that yes, it can be expanded upon, but it doesn't have to be rewritten. It doesn't have to be replaced. And if you look at the industry, you know, Windows has been around forever. It keeps reinventing itself, but it's still Windows. Linux, same thing. Um, so while code can kind of withstand the test of time, how you build this software, how you approach these things, your impact on these projects could be around for a long time. um you could be remembered as the person that hey this person put aside personal differences really put together something solid that they really did something here. Now the sad part is your legacy may not be recognized while you're at your job while you're currently working on the project. Legacy doesn't happen overnight. Legacy takes time and usually legacy doesn't happen until you're gone or have left the project. >> Yeah, that's uh sometimes a lot of times the legacy is as soon as you leave everybody blames you. It's like everything went wrong. Oh yeah, that was that guy that's gone. But there's a uh it's very heartwarming to hear that you know that something you did is still working is still being used is you know has continued on lived well beyond your time at that company. Uh, moving on. Defining your developer journey from junior coder to experienced developer. What changes? Skill building, mindset shifts, and responsibility growth. Common milestones, your first PR, leading a project, mentoring others. And I'm going to move right into the next one. Crafting a legacy in code. Writing clean, maintainable, and documented code. Importance of standards, naming conventions, and clarity. Leaving behind code that's understandable and usable years later. that I I know I sort of blew through that one point, but it's like it really is the developer journey. If we're talking legacy, let's, you know, let's talk more about the legacy side of it. I really think that that that part really nails it. Writing clean, maintainable, and documented code, which is basically goes handinand glove with leaving behind code that's understandable and usable years later. If you if you spend your time, you design it, you write it solid, you document it, you probably are not going to need, nobody's going to need to change it. Uh it is I know it's sometimes interesting to us, maybe even frustrating to be like you'll see the name of some coder, some developer from 10 years ago in comments. It's like, oh yeah, that was, you know, Bob the coder. Yeah, he used to work for us and did a lot of stuff. But think about it. If you were Bob the coder and now people are still looking at your code. Now if they're cussing at you, okay, you screwed up, but if they're like, "Oh yeah, Bob's code is great. Every time I find that, I know what I'm working with." And I literally I have I've got a guy that works with me. He has dealt with multiple projects where we have taken over stuff and and found a way to grow with it. And there's so many times that he and I have had conversations where it's like, "Oh yeah, so and so did this code. it was at the top of that file. This is going to be a pain in the butt versus oh yeah, so and so did this section and it's great that like so we're, you know, we're pretty sure it's going to work. It really is like it's the ability for you to create a relationships and and trust with somebody you never even meet. And a lot of it comes down to writing the code right the first time. Going back making sure you've done the things you need to do. You've tested it. You've documented it. You've kept it up to date. You've solved that problem. You've and especially if you do it in a concise way. If you're like, you know, you're probably your entire if you build the whole application that is not as likely to be like not touched. But if you build like libraries and utilities and certain functions and things like that and they just work, nobody's ever going to need to touch it. So where do you want to go with those? >> So it it's interesting with this one. So when I'm looking at crafting a legacy in code, I see two things here. One, leaving behind code that's understandable and usable. Um, one thing AI doesn't touch on here, which I think is a good point here, we live in an age of open source. There are so many communities out there where you can commit your code, put it out in GitHub, open it up to the world. If you do that and you want people to contribute or you think you have a solution that everyone could, you know, utilize and improve on, crafting a legacy in code, this is a great example of how to do that. You start out, hey, I've got a project. Great. Stick it in a code repository, drop it out on the web. The problem is if you do not write clean and maintainable documented code, no one's going to use that code. They're going to look at and be like, "Oh, well, this may solve my problem, but I can't understand it. It won't work." That is exactly the right way to kind of figure out, are you building a legacy? Stick your code out there. Have people review it. have people try to use it. If they can't use it, you need to refine it, tweak it, clean it up. If you can do that, chances are you might become the next Apache or the next utils that are out there that people start coming to your uh git repository and using your code more and more because it's solid. It works. They don't have to change it. Now, will it stand the test of time? That depends on the language you're in and how many iterations it goes. But if you continuously maintain it, you could be around for a long time and people will like you, understand your code, and heck, you never know. You might even be picked up for a job based on something you did. I only mentioned that last part because I actually interviewed someone that wrote an open- source code, a little training tool for IBM years ago called Robbot. And I had the opportunity to hire him and have him work on my team. He was a great coder. Uh had some personality conflicts where he was very opinionated on how things uh like contracting and management styles worked. But from a code perspective, this guy was rock solid. His code was good. It was clean. He made sure it worked. So long story short, you never know. If you want to put your code out there and want to start building a legacy, take the first step. write a utility class or take something that you're good at, drop it out in, you know, a open code repository and share it. See what people think about it. You never know. It could build that legacy or it could tell you that, hey, you have room for improvement to get to that legacy. Yeah. And I I guess that reminds me of I have done that as well. my first job that I interviewed when I came to Nashville. Uh one of the reasons that they liked me uh and then actually that they liked me and then later uh one of my fir actually the first customer that caused me to create RB consulting came from a project that I had done. My name was on the documentation along with a couple other people and when they saw that they were like oh my gosh you like you're that person you know you're one of those people that wrote it. It's just like when we talk about like writing a book or or a podcast or having a blog when your name is associated with that then certain people will just be like they give you an amazing amount of credit. You are now an automatically an authority in that area and that was how I ended up getting a couple you know landing a couple of positions is because my name was out there. I had done some work and they liked what was done and they were able to you know and it was even with as part of a team. It wasn't necessarily it wasn't definitely all of my work or anything, but it was something that I could talk to and I could say, "Well, yeah, we did this and this is how we approached it." And and now that kind of legacy was, you know, immediate. It wasn't something that came back after the fact where it was like years later people like, "Oh yeah, he was a great guy. We would have loved to hire him." It was like, "No, you're a great guy. We want to hire you now." So what you do building your legacy can also help you immediately, not only in the future. Moving on, uh, beyond code, your impact on teams, mentorship, teaching others is one of the strongest legacies, advocating for good practices, testing, design review, security, building a culture of collaboration instead of silos, stories of developers who left a mark not through genius code, but through leadership and kindness. This um, what goes around comes around, karma, and all these other things that people have heard a lot of times. Um, I have been blessed by working with people throughout my career that have led, been leaders and mentors and things like that. I've done what I can to give that back and be a leader and mentor to people all the time. I literally had a conversation with a lady just the other day that was like, "Hey, you know, my husband graduated and I want to, you know, he's a he's a tech guy and he really wants to get into it, but he's struggling to figure out like how to start his career." And that to me was the best conversation I'd had in I don't know how long because I'm like that's what we do literally building better developers. That's what we want to do. And it's about it's really not about legacy as much as it is like look I, you spend a lot of time learning the crap that we know. We spend a lot of time working on our craft. So why not pass that on to the next generation, to the next group, to the next person that's coming up and help them move that much further so we can all move that much further along. And that's what it's all about is using what we've got to help everybody do better. And that's where you're going to impact you as a leader, as a mentor and things like that, as a manager that you can help impact not only code and products, but actually teams and people. Thoughts on that one? Yes. So, I'm going to take the um I I'll take the mentorship one. So, teaching others in oneonone. Actually, I'll take a couple because a culture of collaboration kind of goes with this because if you mentor not just one person on your team, but if you foster a environment, a culture of collaboration, you essentially get to a point where you have an environment of kind of paired programming or where, hey, let's open up a Slack channel, jump in, I'm working this problem, let's all kind of jump in and just kind of circle the fences. You can create many hackathons that the only way this works is you have to leave your ego at the door. You have to go into these situations not just being I have the answer, but hey, what is the problem that we're trying to solve, get feedback from the team on ways to solve this solution, and then tackle it together and treat it like a mini hackathon. Uh, and it doesn't have always have to be hackathon-ish, but you could do this for a lot of strong problems. So, like if someone's struggling and you hear, uh, I'm working on this, but I'm kind of stuck on this. Or someone's stuck on a problem for a day or two. Open up a team chat or at the end of your standup say, hey, let's stay on for 10 15 minutes. Let's walk through this problem and walk through it as a team. Like, hey, just kind of debug it. What comes out of these which is interesting is not just better testing and design but you also get a better understanding as a team as how people understand the requirements, understand the work that needs to be done, understand the environments, the code. But the best part is you get to learn how people think and troubleshoot the problems and then you can kind of all figure out where the strengths are, where the weaknesses and how can we improve. Now, that leads me to my favorite part of saying, hey, if you ever want to like get some of that feedback or have those discussions, feel free to shoot us an email at [email protected]. But also, uh, I want to shoot shout out to Brandon, a guy that has been, uh, goes way back in some of our mentoring sessions, stuff like that at developer. Speaking of hackathons, actually was part of a winning team at a recent hackathon here in the late the local area. It was pretty cool. I was like looking at the people that were there and I'm like I know that guy. I know that name. I'm like cool. So congratulations Brandon. That stuff's always fun and uh it's really cool to be able to like it's one of those things. It's really cool to be able to build out your legacy and your skills as a professional developer. We will wrap this one up though. As always, you can shoot us an email. You can send us uh leave us comments wherever you get podcast. You can leave it out on the developer.com or the developer channel on YouTube. You can catch us at developure onx. Uh you can also check out the developer Facebook page. At some point we're going to probably have some more stuff, but we just haven't gotten there yet because we're still catching up on social media and stuff. We're we spend too much time in the business versus on the business and all that kind of goodness. But that being said, we do appreciate the heck out of you spending some time with us, hanging out with us and just being out there supporting us. We we feel your support. Trust me, we feel those vibes coming in. So, go out there and have yourself a great day, a great week, and we will talk to you next time. Uh, bonus material. Keeping it short because we've sort of like bonused it. Actually, I'm going to dive right into my bonus material. Uh because I while we were I did get a response back. So um let me see if it'll display. Here we go. Actually, it's pretty cool. So I dumped all of our past seasons, all 25 seasons um plus a couple of special topic series that we had in the uh uh blog post. Uh said, and so here's what it came for. I said like what would be a good season? So this is actually pretty cool little bonus content, I think. Look at your past developer or podcast seasons. You've covered a great mix of technical skills, AWS, Python, Django, React Native, testing, career development, developer journey, mastering your career, interviews, passive income, building better habits, and business consulting insights, lessons learned from consulting, building better businesses, frontline lessons, growth from failures. Check all of those seasons out. There's a ton of really cool stuff in there. What seems missing and could really resonate with both aspiring and experienced developers is a practical future focused season that ties together the themes of tools, habits, businesses, and technology shifts. And I went ahead and like here's a few strong candidate ideas for a new season. Future proof proofing your developer career. Uh the developers toolbox 2.0 global developer perspectives. This is actually one that I had uh some requests on. It was like doing more global developer perspectives um and getting into that from code to company developer entrepreneurs. We sort of started that but that's actually a pretty cool one. Based on your past seasons, I'd recommend starting with future proofing your developer career. It builds naturally on become a better developer, build better developers with AI and developer journey while introducing a fresh forward-looking perspective that your audience will find highly pra practical. It asked me if I wanted to draft a season outline with 10 to 12 specific episodes and I said sure. This is what it gave me. I haven't even read this part yet. Um, episode one, the only constant change in tech. Episode two, skills that never expire. Ex. Episode three, AI as your coding partner, not your replacement. Episode four, navigating the cloudnative world. Episode five, the five, the rise of low and no low code and no code. Episode six, continuous learning without burnout. Episode seven, building a resilient career network. Episode eight, futurep proof architectures. Uh, episode nine, soft skills that will matter most in 2030. Episode 10, thriving in remote and global teams. Episode 11, developer to optim entrepreneur, build expanding your options. Episode 12, your legacy as a developer, which we just covered. Again, that's actually a pretty cool series of of topics. I think Yeah. Um, do you want to take one as a season or take that or take the overall season topic because some of those are just seasons in and of themselves. >> They could be, but I think that that's like I think the whole Where is that? Go back to like future proofing your developer career. That's like a pretty cool little theme to have. And I like those episodes. There's a lot of stuff there. I mean, each of any one of those I guess could be expanded quite a bit, but um I like it. So, like AI is continuing to be like a pretty cool little uh content feeder for us, we'll say. So, before we go too far, your bonus material. >> Well, I think that sums it up. The big thing with this is we're nearing the end of or I can't remember if this was the final episode or not, but um if you want to leave a legacy at the end of the day, make sure you are doing something the work that you are working on the code that you are producing is something that you will be proud of it. You don't have to be one of those crazy crazy is the wrong word. Um, you don't have to be super critical about the work that you do. Just make sure that what you're working on is solid. It continues to move things forward and it's something people can understand, can use, and should withstand the test of time. >> Yeah. Yeah, you don't have to be like a I don't know quality Nazi or something like that on what you would think about or for your code and things, but um I do agree that it's like it's >> I was just thinking perfectionist. That that's what I was trying to >> so much better than quality Nazi. >> Well, that's what I was trying to go for because I used to draw a lot back in high school and I I liked what I did, but I would never turn in my work because it was never done. It it's one of those things you got to be careful of falling into the trap of you're not going to share it till you think it's done. You need to share it sooner so you can get feedback and then fix it and tweak it to make sure that it's done. So I think that's going to wrap this one up because we have gone a bit long. Uh so we will come back next episode and we will be wrapping this season up. Uh however we do it. It may be a multi- uh episode wrap-up. We'll see how it goes because there's a lot of stuff uh that we can dig into. So, that being said, I'm going to I'm not even going to bother you with all the marketing stuff. Uh we're going to let you guys get to it. Go out. Yeah, you can check all the links. Michael's going to take care. >> Just click the button. >> That's right. Um yeah, other stuff we'll get in future episodes. I don't want to get too far into this. Thank you so much. We appreciate your time and your attention and what you even if you've been doing something else or if you're, you know, watching this at like 1.5 speed, I still really appreciate it. Thank you so much. Have yourself a great one. We'll talk to you next time. [Music]
Transcript Segments
[Music]
We got talking things, talking points. I
hit record. Uh, let's see.
>> We are live sort of.
>> Here we go.
>> It's live. All right. Um, gosh, started
off. We're already off the rails. So,
we've got this episode, I think, is
going to be the last one of
using AI with that season. I think we
want I think what we want to do is just
go ahead and instead of like AI on the
the wrap-up, I think it'd be worth us to
the next one will be then to have at
least one
and maybe two. We'll see how it goes. I
think at least one episode that's like
our wrap-up episode that's sort of like
okay let's think back about what you
know a little bit of like little
retrospective of how did this work how
did this go what did we like about AI
what don't we like about AI and all
the fun stuff that's out there because I
think that may be um a pretty cool one
I'm gonna shoot let's see
I don't have the best light here I guess
it's not too bad I have a little bit a
glow. Let me see if I can smooth here.
So, hold on.
This may give me a little more natural
lighting and such. I probably should
drag like a lamp in here, but oh well,
we'll go with this for now.
Okay, so
I'm just
>> Yep.
diving right into my postworkday
drinky poo as some people would call it.
>> Have you tried this yet?
>> The I'm not really a Jim Beam fan.
>> Uh, so this is their black label and uh
I wasn't My mom was a big Jim Beam fan,
but I didn't like the original mash.
This is uh I really like this one. I've
been drinking it for a while. I might
have to try that one because yeah, dad
was always that was one that he drank
regularly and I've had I've had it over
the years and earlier on when I was
younger it was not that big a deal. I
was like, "Oh, okay. It's not bad." But
I've become a little more snobbish about
it as I've been going through all these
different things. So, I have like It's
like everything I've gotten more so
>> really more so what I'm drinking is
about the taste and the flavors and the
certain things that I want as opposed to
um you know, anything else. So, I've
gotten much more digging into the
various flavor profiles.
>> To be fair,
>> yeah, to be fair, this is I I barely
drink this straight, but this is a very
good like mixing bourbon.
>> Oldfashions and things like that. Like
Eagle Rare when I can get it is like my
go-to. Um, which is funny because since
I do live out in the middle of nowhere,
interestingly enough, a college town
just 15 minutes south of me, uh, which
is a dry county, you have to go to the
border, uh, they sell the magnums for
$89
and I can't even get the little bottles
for $89 if I go to Jackson. So, it's
like, wow. Okay. So, uh, I I wait till I
can find those and then, um, of course
it's limited to one, but still one
magnum will last me about a month. So,
it's pretty good.
>> Let's see.
Sorry, I got sidetracked by sidetracked
by one of our customers sending an
email.
Okay. So, serious note there.
Sorry. I like just got myself as I was
shutting stuff down. I was like, "Oh,"
or actually not really. Well, I guess
this is shutting stuff down. Plus, make
sure I Come on. Stop. There we go. Quit.
And I want to go to do not disturb.
I'm just way off today. This is just one
of those. Okay, we'll do it for an hour.
We'll see how long we last. Um, I think
we're just going to dive right. Let me
move this around so I can actually This
is a bonus of having my m my my screens
my screens configured this way.
And so, okay. So, let's see. So, we're
going to do how to leave a last name
legacy
and then we'll see where we go from
that. Um, yeah, I think that'll be sort
of cool because it at the very least
we'll either come back next time around
and we'll be doing yet another wrap-up
episode for this season or we'll maybe
we'll just honestly and maybe we'll just
like use chat GBT and say what would be
a great conversation point. We'll just
like list all of the stuff we've done
and say what would be a topic for us to
cover and see what happens.
>> Oh, so you haven't been keeping these in
like a folder?
not all of the all of the seasons.
>> Okay,
>> I've got it.
>> So, just small AI tip for those of you
watching the pre-show. If you create uh
Chat TPT has this new feature, even in
the free one where you can now do
folders, uh if you put all your chats
into that group, they treat it as a
project and you can have it scan all of
those uh under a certain criteria. So,
it's a very interesting way to quickly
summarize or review what you've are kind
of working on throughout your project.
>> Yeah, I was thinking No, I'm actually
looking at that go because I wanted to
see
uh I think that's what I want
somewhere. I have
a way to do Where did it go? I may have
lost it. Um,
oh, it's in categories. My bad. Okay.
Um,
what it was? I want to go grab all of
the titles of all of the seasons that
we've done. Not episodes, but actual
seasons
and say, "Hey, this is what the
development podcast has done. What would
be a cool season idea?" So, maybe we'll
even do that to wrap up the next
episode, but I get ahead of us a little
bit. I don't know if we can what can do
uh so there is a way if you install the
chatgpt app I think you can have it scan
a folder
but I have not tried that I think
because I have seen it integrate with
like things like PyCharm Intelligj uh
Eclipse like if I have that open it's
like oh you have this open do you want
me to integrate with what you're using
uh and it lets me uh but I think you can
do that against a file system I'm Not
100% sure though.
>> Yeah, I think I can just do it actually.
Okay, now I'm I'm curious. So, let's see
if we do this. I want to just like cheat
here in a second. Where is it? Is at.
Okay, so let's go over here.
Um I want to go over here.
Um
>> on a side note, uh when we do get to the
episode at the end, let me know what you
think about my new intro. I'm switching
it up a little.
Oh yeah, I gotta put Thank you for
reminding me that. Let's see. So for the
Okay,
past seasons,
>> we might have to keep the bonus bonus to
a minimum.
>> Yeah, I know. We're going to be a little
bit here. So, let's see. What would be a
good
new season for the developer
podcast?
Okay, I'm going to spit that out. I'm
going to come back because I want to go
back over here to get the thing up that
I'm working on. Let me get this document
up so I can think about what I'm
thinking about. Where did that go? There
it is. Cool. Okay.
All right. Let's get let's just get it
going here. All right,
do uno. Hola and welcome back. We are
continuing and almost wrapping up our
season where we are taking a past
season, going through the topics,
throwing it out to AI and saying, "What
do you think? What should we have done?
How could we have done it better?" Most
of the time AI does give us some more
things to talk about. I don't know if
it's better. Uh sometimes it goes in a
very different direction. We'll see
where it goes today because we're going
to be talking about uh this was the last
one of that season which was your
developer journey. How to leave a
lasting legacy. Uh I can almost
guarantee it's going to give us some
different thoughts on this because we
have keywords that it's probably going
to go differently. Before we get into
that, I should introduce myself and then
I'm going to let him introduce himself.
See, I'm not even giving his name out.
My name is Rob Broadhead. I am one of
the founders of developing also the
founder of RB consulting where we help
businesses assess and simplify their
technology.
From there we build clear road maps and
we help you full grow fuel growth. We
help you to move forward. We help you to
figure out how to take where you're
stuck. You know your wheels are spinning
and then we find a way to put a little
leverage in there and get you going. We
do this by sitting down with you,
understanding your business, helping you
craft a special recipe, a unique recipe
for your business, that roadmap so that
you can move forward leveraging
technology through simplification,
integration, automation, innovation, all
of the shuns that are out there. We help
you do business better. And check us out
at rb-sns.com.
We also have like we've got some deals
going on there. We've got some like
insta assessments out there. And even
you can do a self assessment. Go out to
matrix.rb- rb-sns.com.
Check it out. Let us know what you
think. Good thing, bad thing. Uh, bad
thing was, and I don't know if I'm going
to tie it to a good thing yet, uh, I was
I was on a call today, sitting there
like deeply into this conversation,
worked great, got done, and I suddenly
realized it was pouring outside and I'd
left a couple things out on the porch
that I was like, ah, probably shouldn't
have. So, I had to go throw them in the
dryer and things like that. So, lesson
to you kids, make sure you're keeping an
eye on the weather before you like go
heads down for a bit. Good thing
um and this is actually I think I've
I've mentioned this before is like I'm
in a little bit of a a more quiet time
in business. I'm not spend I've been
able to extract myself from working in
my business quite so often and so I'm
able to work on my business and that has
been awesome. It has been so good to be
able to knock out some of my to-do list
items. to upgrade. You can go check out
the RB Consulting website. We've
definitely done some upgrades there.
We've been tweaking stuff. Uh added some
products. We're like finishing touches
here and there. And this also means it
will spill over to developer soon
enough. I've been already delaying
with some ideas there and starting to
work towards making that more uh
bringing it current and also making it
easier for you to utilize the huge
amounts of content that we have out
there. But first, you're gonna have to
meet my co-host. Go ahead, introduce
yourself.
>> Hey everyone, my name is Michael Moash.
I'm one of the co-founders of Developer,
Building Better Developers. I'm also the
owner of Envision QA where we help
businesses take back control with
customer soft with custom software
that's built around their needs, not the
other way around. Our focus is simple,
great service, smart solutions, and a
rockolid quality. We build tools that
replace frustrating systems, streamline
operations, and are fully tested to work
right the first time. At Envision QA, we
combine development and quality
assurance to give you software that you
can trust and support you can count on.
Check us out at envisionqa.com.
Good thing, bad thing. Let me start with
the bad thing. Wife had to take down the
pool today. Uh it was uh she's a bit
depressed cuz, you know, it's finally
cool enough. It it's just not worth
keeping it up anymore. Uh, good thing
fall is here sort of. Uh, the days are
getting a little bit shorter. Uh, the
trees are starting to change color and
if it wasn't just on the other side of
hot today, it would have been a perfect
day to sit outside and work all day.
Those are good days. I would not have
had a perfect day because I would have
been rained upon as mentioned before.
Well, let's dive right into it. So, this
episode we are going to go with, as I
mentioned, the title was your developer
journey. How to leave a lasting legacy.
Uh, chat GPT, we're back to that. It
came out right away and said because it
loves us. Great title again. Wow, we are
just knocking them out of the park. Uh,
you can really connect with developers
who want to think beyond just writing
code and start shaping something more uh
something meaningful in their careers.
Here's how you could structure and
enrich that episode. So, let's see how
we structure and enrich this puppy. Uh,
part one, introduction. What does legacy
mean in software development? Legacy is
more than old code. It is about lasting
impact. Contrast getting tasks done
versus building something that outlives
you. Why developers should care about
their professional legacy. Now, this
honestly I don't remember us ever really
getting into this before. I think we've
talked a little I think it was a little
bit more about
mentoring and leading and passing it on
to the next generation but this is
actually really uh a cool direction for
AI to go with it because I I think it is
an area that is worth discussing.
Um one of the things we've talked about
a lot is building your scratching your
own itch building applications to help
you to help your utilities to help you
other developers all those things. And
it's also a great way to grow uh
professionally. You can go test out new
technologies and approaches and
different areas of code. Maybe like
maybe normally you're not a tester, but
you get to do some testing. Or maybe
normally you don't do UI, but you get to
do UI. Uh the I have these conversations
with my team on a regular basis where
it's like, hey, you can go work on this
project and do this thing and that's
going to help you be able to actually
like dip a toe into an area that you you
want to understand a little bit better.
I like the idea of uh and again I always
like this getting tasks done versus
building something that outlives you.
This really goes to work ethic. This
really goes to what we want to do is we
want to build something that people are
going to use. I don't think any of us
really want to build something that
somebody puts on a shelf and they're
just like, "Okay, I bought the software
and I never use it." It it has
frustrated us because we probably have
invested our time, blood, sweat, and
tears into it. We want them to use what
we're what we've sold them. We really I
think most of us would be rather we'd
rather like earn less money out of it
and have them use it all the time than
be able to retire on it and have them
never use it. Now, I know there's a
point where you're like, I'll take the
retirement, thank you very much. But
there's very much an idea of we don't
want people that's our whole point is
for so people aren't throwing their
money away that they're buying something
of value that we're giving the value of
our time and our intelligence and our
ability to problem solve and they're
returning the value of you know whatever
they paid for. And I think that's that's
very critical to it's like our why. It's
very critical to keep in mind while
we're doing software development is to
basically say look we're not here just
to write code. We're not here just to
like play around with the latest
technology. We're really here to solve
problems. We're really here to help
other people become better. Their
businesses become better through
technology and through the skills that
that we bring to the table. Thoughts on
that? or actually other ways you may
want to go just like AI that was
completely in a direction we haven't
been.
>> So, I'm going to since I'm a gamer, I'm
going to start out with think legacy.
All right? If you think if you've been
around more than a decade or two,
especially with games, you you look at
what's been around for a long time.
Pac-Man, Donkey Kong, these are games
that are legacy games. I mean these this
is software written in the 80s that is
still around today. It's still being
enhanced upon. It was simple. It was
great and it has withstand the test of
time.
The our legacy
can be twofold. It can be software that
we've written or it could be how we
handle a situation or how we solved a
problem not just for a customer but for
anyone we've worked for a company we've
worked for um our friends whatever
as you were talking about this topic I I
was thinking back to a company I worked
for a couple jobs ago they're still
using software I or test software I
wrote and it is the only way they're
able to get the job done. They have not
found a solution that can replace what
they're currently doing. So there are
times when
you're working to solve a problem when
if you really have the mindset of
anything I do I want to do right the
first time. Now, that doesn't mean that
you have to write perfect code every
time, but the intent is what you're
putting together is a solution
that could really withstand the test of
time. You write something so good that
yes, it can be expanded upon, but it
doesn't have to be rewritten. It doesn't
have to be replaced.
And if you look at the industry, you
know, Windows has been around forever.
It keeps reinventing itself, but it's
still Windows. Linux, same thing. Um, so
while code can kind of withstand the
test of time,
how you build this software, how you
approach these things, your impact on
these projects
could be around for a long time. um you
could be remembered as the person that
hey this person
put aside personal differences really
put together something solid that they
really did something here. Now the sad
part is
your legacy may not be recognized while
you're at your job while you're
currently working on the project. Legacy
doesn't happen overnight. Legacy takes
time and usually legacy doesn't happen
until you're gone or have left the
project.
>> Yeah, that's uh sometimes a lot of times
the legacy is as soon as you leave
everybody blames you. It's like
everything went wrong. Oh yeah, that was
that guy that's gone. But there's a uh
it's very heartwarming to hear that you
know that something you did is still
working is still being used is you know
has continued on lived well beyond your
time at that company. Uh, moving on.
Defining your developer journey from
junior coder to experienced developer.
What changes? Skill building, mindset
shifts, and responsibility growth.
Common milestones, your first PR,
leading a project, mentoring others. And
I'm going to move right into the next
one. Crafting a legacy in code. Writing
clean, maintainable, and documented
code. Importance of standards, naming
conventions, and clarity. Leaving behind
code that's understandable and usable
years later. that
I I know I sort of blew through that one
point, but it's like it really is the
developer journey. If we're talking
legacy, let's, you know, let's talk more
about the legacy side of it. I really
think that that that part really nails
it. Writing clean, maintainable, and
documented code, which is basically goes
handinand glove with leaving behind code
that's understandable and usable years
later.
If you if you spend your time, you
design it, you write it solid, you
document it, you probably are not going
to need, nobody's going to need to
change it. Uh it is I know it's
sometimes interesting to us, maybe even
frustrating to be like you'll see the
name of some coder, some developer from
10 years ago in comments. It's like, oh
yeah, that was, you know, Bob the coder.
Yeah, he used to work for us and did a
lot of stuff. But think about it. If you
were Bob the coder and now people are
still looking at your code. Now if
they're cussing at you, okay, you
screwed up, but if they're like, "Oh
yeah, Bob's code is great. Every time I
find that, I know what I'm working
with." And I literally I have I've got a
guy that works with me. He has dealt
with multiple projects where we have
taken over stuff and and found a way to
grow with it. And there's so many times
that he and I have had conversations
where it's like, "Oh yeah, so and so did
this code. it was at the top of that
file. This is going to be a pain in the
butt versus oh yeah, so and so did this
section and it's great that like so
we're, you know, we're pretty sure it's
going to work. It really is like it's
the ability for you to create a
relationships and and trust with
somebody you never even meet. And a lot
of it comes down to writing the code
right the first time. Going back making
sure you've done the things you need to
do. You've tested it. You've documented
it. You've kept it up to date. You've
solved that problem. You've and
especially
if you do it in a concise way. If you're
like, you know, you're probably your
entire if you build the whole
application that is not as likely to be
like not touched. But if you build like
libraries and utilities and certain
functions and things like that and they
just work, nobody's ever going to need
to touch it. So where do you want to go
with those?
>> So it it's interesting with this one. So
when I'm looking at crafting a legacy in
code, I see two things here.
One, leaving behind code that's
understandable and usable. Um, one thing
AI doesn't touch on here, which I think
is a good point here, we live in an age
of open source. There are so many
communities out there where you can
commit your code, put it out in GitHub,
open it up to the world. If you do that
and you want people to contribute or you
think you have a solution that everyone
could, you know, utilize and improve on,
crafting a legacy in code, this is a
great example of how to do that. You
start out, hey, I've got a project.
Great. Stick it in a code repository,
drop it out on the web. The problem is
if you do not write clean and
maintainable documented code, no one's
going to use that code. They're going to
look at and be like, "Oh, well, this may
solve my problem, but I can't understand
it. It won't work."
That is exactly the right way to kind of
figure out, are you building a legacy?
Stick your code out there. Have people
review it. have people try to use it. If
they can't use it, you need to refine
it, tweak it, clean it up. If you can do
that, chances are you might become the
next Apache or the next utils that are
out there that people start coming to
your uh git repository and using your
code more and more because it's solid.
It works. They don't have to change it.
Now, will it stand the test of time?
That depends on the language you're in
and how many iterations it goes. But if
you continuously maintain it, you could
be around for a long time and people
will like you, understand your code, and
heck, you never know. You might even be
picked up for a job based on something
you did. I only mentioned that last part
because I actually interviewed someone
that wrote an open- source code, a
little training tool for IBM years ago
called Robbot. And I had the opportunity
to hire him and have him work on my
team. He was a great coder. Uh had some
personality conflicts where he was very
opinionated on how things uh like
contracting and management styles
worked. But from a code perspective,
this guy was rock solid. His code was
good. It was clean. He made sure it
worked. So
long story short, you never know. If you
want to put your code out there and want
to start building a legacy, take the
first step. write a utility class or
take something that you're good at, drop
it out in, you know, a open code
repository and share it. See what people
think about it. You never know. It could
build that legacy or it could tell you
that, hey, you have room for improvement
to get to that legacy.
Yeah. And I I guess that reminds me of I
have done that as well. my first job
that I interviewed when I came to
Nashville. Uh one of the reasons that
they liked me uh and then actually that
they liked me and then later uh one of
my fir actually the first customer that
caused me to create RB consulting came
from a project that I had done. My name
was on the documentation along with a
couple other people and when they saw
that they were like oh my gosh you like
you're that person you know you're one
of those people that wrote it. It's just
like when we talk about like writing a
book or or a podcast or having a blog
when your name is associated with that
then certain people will just be like
they give you an amazing amount of
credit. You are now an automatically an
authority in that area and that was how
I ended up getting a couple you know
landing a couple of positions is because
my name was out there. I had done some
work and they liked what was done and
they were able to you know and it was
even with as part of a team. It wasn't
necessarily it wasn't definitely all of
my work or anything, but it was
something that I could talk to and I
could say, "Well, yeah, we did this and
this is how we approached it." And and
now that kind of legacy was, you know,
immediate. It wasn't something that came
back after the fact where it was like
years later people like, "Oh yeah, he
was a great guy. We would have loved to
hire him." It was like, "No, you're a
great guy. We want to hire you now." So
what you do building your legacy can
also help you immediately, not only in
the future. Moving on, uh, beyond code,
your impact on teams, mentorship,
teaching others is one of the strongest
legacies, advocating for good practices,
testing, design review, security,
building a culture of collaboration
instead of silos, stories of developers
who left a mark not through genius code,
but through leadership and kindness.
This um, what goes around comes around,
karma, and all these other things that
people have heard a lot of times. Um, I
have been blessed by working with people
throughout my career that have led, been
leaders and mentors and things like
that. I've done what I can to give that
back and be a leader and mentor to
people all the time. I literally had a
conversation with a lady just the other
day that was like, "Hey, you know, my
husband graduated and I want to, you
know, he's a he's a tech guy and he
really wants to get into it, but he's
struggling to figure out like how to
start his career." And that to me was
the best conversation I'd had in I don't
know how long because I'm like that's
what we do literally building better
developers. That's what we want to do.
And it's about it's really not about
legacy as much as it is like look I, you
spend a lot of time learning the crap
that we know. We spend a lot of time
working on our craft. So why not pass
that on to the next generation, to the
next group, to the next person that's
coming up and help them move that much
further so we can all move that much
further along. And that's what it's all
about is using what we've got to help
everybody do better. And that's where
you're going to impact you as a leader,
as a mentor and things like that, as a
manager that you can help impact not
only code and products, but actually
teams and people. Thoughts on that one?
Yes. So, I'm going to take the um I I'll
take the mentorship one. So, teaching
others in oneonone. Actually, I'll take
a couple because a culture of
collaboration kind of goes with this
because if you mentor not just one
person on your team, but if you foster a
environment, a culture of collaboration,
you essentially get to a point where you
have an environment of kind of paired
programming or where, hey, let's open up
a Slack channel, jump in, I'm working
this problem, let's all kind of jump in
and just kind of circle the fences. You
can create many hackathons that the only
way this works
is you have to leave your ego at the
door. You have to go into these
situations not just being I have the
answer, but hey, what is the problem
that we're trying to solve, get feedback
from the team on ways to solve this
solution, and then tackle it together
and treat it like a mini hackathon. Uh,
and it doesn't have always have to be
hackathon-ish, but you could do this for
a lot of strong problems. So, like if
someone's struggling and you hear, uh,
I'm working on this, but I'm kind of
stuck on this. Or someone's stuck on a
problem for a day or two. Open up a team
chat or at the end of your standup say,
hey, let's stay on for 10 15 minutes.
Let's walk through this problem and walk
through it as a team. Like, hey, just
kind of debug it. What comes out of
these which is interesting is not just
better testing and design but you also
get a better understanding as a team as
how people understand the requirements,
understand the work that needs to be
done, understand the environments, the
code. But the best part is you get to
learn how people think and troubleshoot
the problems and then you can kind of
all figure out where the strengths are,
where the weaknesses and how can we
improve.
Now, that leads me to my favorite part
of saying, hey, if you ever want to like
get some of that feedback or have those
discussions, feel free to shoot us an
email at [email protected].
But also, uh, I want to shoot shout out
to Brandon, a guy that has been, uh,
goes way back in some of our mentoring
sessions, stuff like that at developer.
Speaking of hackathons, actually was
part of a winning team at a recent
hackathon here in the late the local
area. It was pretty cool. I was like
looking at the people that were there
and I'm like I know that guy. I know
that name. I'm like cool. So
congratulations Brandon. That stuff's
always fun and uh it's really cool to be
able to like it's one of those things.
It's really cool to be able to build out
your legacy and your skills as a
professional developer.
We will wrap this one up though. As
always, you can shoot us an email. You
can send us uh leave us comments
wherever you get podcast. You can leave
it out on the developer.com or the
developer channel on YouTube. You can
catch us at developure onx. Uh you can
also check out the developer Facebook
page. At some point we're going to
probably have some more stuff, but we
just haven't gotten there yet because
we're still catching up on social media
and stuff. We're we spend too much time
in the business versus on the business
and all that kind of goodness. But that
being said, we do appreciate the heck
out of you spending some time with us,
hanging out with us and just being out
there supporting us. We we feel your
support. Trust me, we feel those vibes
coming in. So, go out there and have
yourself a great day, a great week, and
we will talk to you next time. Uh, bonus
material. Keeping it short because we've
sort of like bonused it. Actually, I'm
going to dive right into my bonus
material. Uh because I while we were I
did get a response back.
So um let me see if it'll display. Here
we go. Actually, it's pretty cool. So I
dumped all of our past seasons, all 25
seasons um plus a couple of special
topic series that we had in the uh uh
blog post. Uh said, and so here's what
it came for. I said like what would be a
good season? So this is actually pretty
cool little bonus content, I think. Look
at your past developer or podcast
seasons. You've covered a great mix of
technical skills, AWS, Python, Django,
React Native, testing, career
development, developer journey,
mastering your career, interviews,
passive income, building better habits,
and business consulting insights,
lessons learned from consulting,
building better businesses, frontline
lessons, growth from failures. Check all
of those seasons out. There's a ton of
really cool stuff in there. What seems
missing and could really resonate with
both aspiring and experienced developers
is a practical future focused season
that ties together the themes of tools,
habits, businesses, and technology
shifts. And I went ahead and like here's
a few strong candidate ideas for a new
season. Future proof proofing your
developer career. Uh the developers
toolbox 2.0 global developer
perspectives. This is actually one that
I had uh some requests on. It was like
doing more global developer perspectives
um and getting into that from code to
company developer entrepreneurs. We sort
of started that but that's actually a
pretty cool one. Based on your past
seasons, I'd recommend starting with
future proofing your developer career.
It builds naturally on become a better
developer, build better developers with
AI and developer journey while
introducing a fresh forward-looking
perspective that your audience will find
highly pra practical. It asked me if I
wanted to draft a season outline with 10
to 12 specific episodes and I said sure.
This is what it gave me. I haven't even
read this part yet. Um, episode one, the
only constant change in tech. Episode
two, skills that never expire. Ex.
Episode three, AI as your coding
partner, not your replacement. Episode
four, navigating the cloudnative world.
Episode five, the five, the rise of low
and no low code and no code. Episode
six, continuous learning without
burnout. Episode seven, building a
resilient career network. Episode eight,
futurep proof architectures.
Uh, episode nine, soft skills that will
matter most in 2030. Episode 10,
thriving in remote and global teams.
Episode 11, developer to optim
entrepreneur, build expanding your
options. Episode 12, your legacy as a
developer, which we just covered. Again,
that's actually a pretty cool series of
of topics. I think
Yeah. Um,
do you want to take one as a season or
take that or take the overall season
topic because some of those are just
seasons in and of themselves.
>> They could be, but I think that that's
like
I think the whole Where is that? Go back
to like future proofing your developer
career. That's like a pretty cool little
theme to have. And I like those
episodes. There's a lot of stuff there.
I mean, each of any one of those I guess
could be expanded quite a bit, but um I
like it. So, like AI is continuing to be
like a pretty cool little
uh content feeder for us, we'll say. So,
before we go too far, your bonus
material.
>> Well, I think that sums it up. The big
thing with this is we're nearing the end
of or I can't remember if this was the
final episode or not, but um
if you want to leave a legacy
at the end of the day, make sure you are
doing something the work that you are
working on the code that you are
producing is something that you will be
proud of it. You don't have to be one of
those
crazy crazy is the wrong word. Um,
you don't have to be
super critical about the work that you
do. Just make sure that what you're
working on is solid. It continues to
move things forward and it's something
people can understand, can use, and
should withstand the test of time.
>> Yeah. Yeah, you don't have to be like a
I don't know quality Nazi or something
like that on what you would think about
or for your code and things, but um I do
agree that it's like it's
>> I was just thinking perfectionist. That
that's what I was trying to
>> so much better than quality Nazi.
>> Well, that's what I was trying to go for
because I used to draw a lot back in
high school and I I liked what I did,
but I would never turn in my work
because it was never done. It it's one
of those things you got to be careful of
falling into the trap of you're not
going to share it till you think it's
done. You need to share it sooner so you
can get feedback and then fix it and
tweak it to make sure that it's done.
So I think that's going to wrap this one
up because we have gone a bit long. Uh
so we will come back next episode and we
will be wrapping this season up. Uh
however we do it. It may be a multi- uh
episode wrap-up. We'll see how it goes
because there's a lot of stuff uh that
we can dig into. So, that being said,
I'm going to I'm not even going to
bother you with all the marketing stuff.
Uh we're going to let you guys get to
it. Go out. Yeah, you can check all the
links. Michael's going to take care.
>> Just click the button.
>> That's right. Um
yeah, other stuff we'll get in future
episodes. I don't want to get too far
into this. Thank you so much. We
appreciate your time and your attention
and what you even if you've been doing
something else or if you're, you know,
watching this at like 1.5 speed, I still
really appreciate it. Thank you so much.
Have yourself a great one. We'll talk to
you next time.
[Music]