But making those kinds of rookie mistakes after doing hundreds of episodes, it's embarrassing, but it happens. It's one of those unexpected things that happens, just like in software. But I don't know what I'm trying to say, but those things happen and you make mistakes no matter who you are. Hey, everyone, and welcome to Developer Team. My name is Jonathan Cottrell, and in today's episode, we pick up where we left off with Dave Rail. Dave is the host of Developer on Fire. He's interviewed incredible people like Sandy Metz, Uncle Bob, that's Robert Martin, David Hennemeyer Hansen, Ward Cunningham, and a whole list of others. He has 175 episodes as of this recording. Go and check it out at developeronfire.com. Of course, that link can be found in the show notes. We're going to pick right up. We're going to pick right up where we left off in the last episode. If you missed out on that first one, you may end up feeling a little bit discombobulated or like you're jumping in the middle of the conversation because you are. We cut the conversation basically right in half. So go and listen to that episode. I'm going to stop talking so we can get to the interview with Dave Rail. So another thing that I've learned from podcasting, I want to see if you've kind of felt the same thing. You kind of alluded to it a few minutes ago. But it's this idea that really kind of the buck stops with me, right? If I don't push this forward, if I don't stand in front of the mic, if I don't contact guests or if I don't, you know, ultimately create this content, then no one else is going to do it for me. No one else can can jump in front of the mic and take over unless, of course, I tell them to. Right. But ultimately, the buck stops with me if I don't get an episode done in time. Right. Right. Right. If I don't get an episode done in time, it's not going to go out. That's right. People are not going to listen to this podcast because it just simply won't exist. Yeah. That's really appealing to me that there is no excuse. There's nobody to blame. There's, you know, that's it. If it doesn't happen, it's because I didn't make it happen. Now, there are a lot of circumstances around things and, you know, finding guests and getting them to commit to a schedule. And I had, you know, I had one guest who when. You know, I contacted him the morning of, you know, of the show and said, you know, hey, we're still good for today. And he was like, well, I thought, you know, I planned something else. I was like, really? Well, OK. You know, I mean, and so those things happen. I mean, there are a lot of those kinds of circumstances. But yeah. I've been stood up quite a few times, actually. Yeah. It's a very frustrating feeling. And that's that's actually a lesson that I learned. It's one of those, you know, you learn how not to be kind of lessons. Don't stand people up, by the way. Yeah. If you're going to an interview or if somebody has asked you to meet them and you don't tell them that you're not going to be there and then they show up and you're not there. That's one of the biggest, most disrespectful things that you can do to someone. Obviously, I don't like to throw people under the bus. I don't think that's a professional thing to do. But but certainly don't don't go out of your way to hurt someone else in their career and don't go out of your way to not be somewhere. Right. Just don't make the plan in the first place. Yeah, absolutely. Yeah. Anyway, that's that's just a complete aside, a momentary rant to a fellow podcaster who has experienced the frustration of sitting in front of the mic with the headphones on, waiting for somebody to sign on to Skype. Indeed. Yeah. Great. So so this this idea of podcasting or or really it's it's more about content publishing. Right. You said you spoke with John Sommers and he was actually on Developer Tea as well at one point. Very early on. Yeah. And he's the one in the episode list. You can find John Sommers. But we talked about that idea of of branding. I want to kind of open that discussion back up with you and and really ask, you know, what role does publishing play for you in that self branding process? Well, I think sticking to a schedule, I think, is the first thing that comes to mind that you give a message of being reliable to an audience. And, you know, as that audience grows from dozens of people to hundreds to thousands. And, you know, we'll see, you know, ultimately where that goes. You know, it's it's really ultimately saying here is someone who is reliable and is going to do the things that that, you know, that I say I'm going to do. So I think that's that's, you know, bar none stop. You know, that that's that's the start and end of it. And then beyond that, there is that quality aspect. Right. You know, I think, you know, both Developer on Fire and Developer Tea. We are delivering useful things that people can get something from with every single publish. And that is something that sends a message as well. So, you know, that branding, you know, John Sonmez is, you know, really emphasizes that, you know, being consistent and that that's how you build a following and that you build a name for yourself. And, you know, I'll add that, you know, John's his how to market yourself as a software developer package. Was. And I think that was instrumental in in my, you know, deciding that this was something that I wanted to do. And I told that story on that interview with John. And I can tell you more about that if you want to. But or, you know, can just direct people to that interview that I did with with John Sonmez where we talked about that. But there was there was one of the interviews that he had in that package with Pinal Dave, who is an Indian programmer. And, you know, he he has SQL authority dot com is his blog. And he he posts to his blog. Every day. So, you know, he writes a blog post every day. And I had him on the show. And, you know, that was that was an epic episode with with Pinal and, you know, talking about, you know, his his dedication to blogging and what that has done for his career is, you know, it's it's really inspiring to hear about how he has he called his blog his master. He serves his his master. And it has really benefited him to do that. Wow. That's that's really strong language. And it's really interesting to hear that that people see this really. It's not it's not something that you do on the side or do it because, you know, you're bored. Right. That's not what this stuff is about. You can't commit to something because of boredom. Yeah, that's not going to happen. You're not going to do well with that. You also can't commit to something just because of the excitement that you get over the course of a weekend. Right. Really committing. To a publishing schedule or even if you're not going to commit to a publishing schedule like Dave or Pinal or myself, building that brand for yourself, building the idea of dependability or developing your authority. You know, that's that's one of my main reasons for creating developer T is because I want to develop authority legitimately. Right. I want to actually explore these subjects and develop authority legitimately. And I believe that sharing this content, teaching other people. Helping other people find success. That's the best way to actually develop authority. Absolutely. Yeah, I think that totally. I would say, though, that you need to do it for yourself. Right. To start with, because when you begin publishing content and, you know, kind of going back, I guess, to that, you know, the context of talking to the person who is embarking on this journey. Right. Whether it's publishing content or just getting into the career and those kind of things. You know, if you are doing this because of the huge. Audience that you're going to build, that's probably not a good initial focus because it's going to be a long time. Right. I got I'm on an email list for Jonathan Stark, who is he's the hourly billing is nuts software consulting guy and, you know, value based pricing and all that kind of stuff. And he was on developer on fire as well. And he just launched his podcast and he sent out a mailing saying that, you know, on in the first 24 hours, he had 700 downloads. Of his podcast or 700 and some. Right. And, you know, I thought, wow, that's that's pretty awesome. He's got an existing audience and all of that. And I remember, you know, the first day that I released my first episode with John Sonmez, by the way, you know, I got 22 downloads. Right. And so, you know, it's it's humble beginnings and it takes time to build an audience. And so, you know, I mean, if you've got your eyes on the big audience, it's that's not going to be. Well, yeah. I mean, unless you. Are a really exceptionally patient person, that's not going to be the motivation that's going to get you through that, you know, up over the hill to get you into that promised land. It's going to take that you are getting something from this beyond just, you know, trying to build authority and some of those things. So, you know, I mean, by all means, you know, yes, you want to build an audience. You want to gain authority. You want to have all of that kind of stuff. But there's got to be some intrinsic. You know, some something that you enjoy about whether it's writing or speaking or some of those things. And there's got to be something there. Absolutely. I think it's kind of the the idea of a fad diet. Yeah. You you have this energy because you see the end goal. Right. You want to jump to that end goal the fastest way possible. And that's really not the best way to look at it. This is more like a long term investment. Yes. That's what this is. That's that's the way you have to look at this kind of thing. Day one is going to be equally effective as day two and day two will be equally effective as day one. But neither of them are going to get you to day 10,000. Right. Or well, I guess a more realistic a realistic number would be something like day 500. Right. You're not going to jump straight into even success at any level. There's no guarantee for any success. The process of publishing is going to reflect. Fine. You though. Right. The process of figuring out the things that you actually want to contribute and create value in the world. Not because you see the return on that value necessarily, but because you actually believe in doing something, creating value in the world as a function of just your life. Right. That's kind of the core idea. Yeah. Building something that is valuable as a function of your life. Right. Even to actually, you know, do something with your life or not. And it sounds very it sounds like we're kind of minifying this concept all the way down to are you are you a good person or not? But really, it's more than that. It's it's about actually taking the things that you believe about yourself and doing something with them. Yeah. Turning those turning those beliefs into actions. Yeah. You know, that that's that really speaks to my heart because, you know, there was for years, you know, I felt like I really had something to offer. And that there were big. Things in my future. And I wasn't really taking action. Right. I was expecting that it was just going to happen because because I had something to offer. Right. But it's it's not until you actually take action on that thing, you know, that you actually do something that that somebody can realize that you that you do, in fact, have something to offer. And, you know, that, you know, as developers, marketing often gets a bad name. Right. But it heads with marketing departments a lot of times. And I've always thought that they were kind of bad people, which was, of course, ludicrous. But, you know, marketing really at its core isn't all about manipulating people into buying something that they don't want. Right. Marketing done right is having something worth having and letting other people know that here's something that will benefit them. Yeah, absolutely. I believe it's John Sama's actually that also says that if you have something of value, then you really should like it's it's like a moral imperative. To sell it. Right. Yeah. You you need to be able to sell this thing because it is actually going to make someone's life better or it's actually going to help them, you know, further their career or whatever that particular thing does. Yeah. If John wasn't selling a package for a couple hundred dollars and I didn't buy that and I didn't get that interview that he did with Pinal and I hadn't done the blog commenting challenge that Pinal talked about in there, which I tell that story on the episode with Pinal. And also in that. Interview with John. So, you know, I don't know if you want me to repeat that here, but, you know, I've commented on Pinal's blog and on John's blog and on the dot net rocks podcast show notes, you know, just day after day after day after day. And that was kind of the, you know, Pinal having giving that challenge was was the was the genesis of me getting involved. And if it wasn't for that, you know, if it wasn't for John trying to make a buck, then, you know, I would. Well, I don't know what I would be doing right now. Yeah, sure. Sure. Incredible stuff. Dave actually has a whole list of his episodes, by the way. We've referenced so many of them. I'm not going to list them one by one in the show notes because it'd be easier. One nineteen is the episode with Pinal and then episode one actually is zero zero one, which is June 13th, 2015 was was John Sonmez. Thinking back that long is is a long journey. And I know I started developer T in 2015 as well back in January. And there's so many things that I've learned on that path. And it's it's really refreshing to talk to another person who is who has gone down a similar path in the podcasting world. So thank you very much for talking to me about the podcasting, the effect of podcasting on your career. Yeah. Yeah. I thank you very much, too. You know, you're welcome. And thank you. And yeah, it's a it's a it's a it's a great pleasure. And yeah, it's definitely nice to talk to a like mind. Today's episode is sponsored by Chartio. Chartio is built on the premise that your data is in multiple places. If you're like most businesses, you may already be using multiple sources of analytics or charging data for your customer charges, maybe even keeping sales reports in a local Excel file or CSV. This is a very common thing, and you shouldn't feel bad for not having your data all in one place. The reality is trying to keep all of your data together in one place is really a very tedious process. It takes a ton of developer energy and the value is not really commensurate to the amount of energy that you're going to spend. This is what Chartio does for you. It takes all of these data sources and it creates a single source for you to be able to analyze all of those key metrics that you want to analyze. Whether you are a business person or a developer, it is friendly for both. If you've had to struggle with bringing all of that data in yourself, then you know what I'm saying. Trying to wrangle a bunch of different APIs and bring them into a unified way of looking at that data that can really eat up a lot of resources. Chartio will solve this problem for you. Go and check it out. Spec.fm. Chartio. You can get a free trial so you really don't have anything to lose. Spec.fm. Chartio. Thank you again to Chartio for sponsoring today's episode. I'm going to switch gears again on you Dave. I'm going to ask you a totally different question. I guess it's somewhat related. We've talked about committing to a schedule. We've talked about some of those things. I'd like to hear a little bit about your normal routine. This is the kind of stuff that people who are listening to this podcast, they really want to kind of learn how developers shape their lives. How successful developers shape their lives. What is your normal routine? Both for the podcast as well as your work? What is your routine? What is your routine? What is your routine? What is your routine? What is your routine? At your, just your average day, what does it look like? At your, just your average day, what does it look like? At your, just your average day, what does it look like? At your, just your average day, what does it look like? At your, just your average day, what does it look like? At your, just your average day, what does it look like? At your, just your average day, what does it look like? At your, just your average day, what does it look like? those are remote gigs where I can just work from home. Currently, I'm actually working on site. So doing back and forth between an office, which is something that I don't particularly like and something that I'm going to try to avoid in the future. But so currently, my life is a little bit different than it usually is because I am going to an office. But so when I'm not doing that, I will split my day up usually using the Pomodoro technique. So I'm sure you've probably come across that. The idea is work for a short period where you can focus intently and have no distractions and take short breaks in between those. So that's how I do my day. And rather than counting the number of hours that I work, I usually count the number of Pomodoros that I've completed. And I consider that, you know, I used to think that, you know, I'd try to do 12 to 14 Pomodoros. And when I do that, the... Wow, that's quite a bit, isn't it? Well, that's what I used to do because it was way too much, right? Chris Winfield, who has, he's been on the podcast. He's not a developer. I've had a few non-developer guests on the show. He talks about the Pomodoro technique and he recommends, you know, basically treating a Pomodoro like an hour. And he has this gigantically, stratospherically successful blog post about, you know, 16 and two-thirds hours. And he's like, you know, I'm going to do this for a week and getting more done than anybody else is doing in 40 hours a week. So I do more than that. I don't do a 40 Pomodoro work week, but, you know, a 12 Pomodoro day is way too much. So, you know, finding something in between there is my typical. So, you know, I wake up early, early in the morning. It's not necessarily that I've chosen that. That's just what my body does. It's been years since I've used an alarm clock. So I get out I usually wake up sometime between 3.30 and five o'clock in the morning. So. So you mean very, very early. Yes. Yeah. Yeah. Of course, you know, the flip side of that is that, you know, I get my kids into bed at night and I'm a zombie, you know, I'm in, I completely, so, you know, it's not like I'm, you know, up all night and then, you know, so I do get my sleep. So, but yeah, I wake up extremely early and, you know, I, I like to listen to podcasts. I usually lay in bed just listening to podcasts. I like to listen to podcasts. I like to listen to podcasts. I like to listen to podcasts for a few minutes before I get up and then, you know, make my bulletproof coffee. So, you know, I, this, this, this fat bomb that I have in the morning that gives me my energy during the day that involves butter and oil and coffee. And, and then just, you know, hop to it. Well, I like to meditate and I don't always do it, but I like to meditate before I, before I start digging into doing stuff. And then, you know, if I have some interviews on the calendar and, you know, I, I usually, you know, two, on, on a given day, I, I, I used to try to batch them and do, you know, like four interviews in a day. I have learned that if I do two interviews in a day and then I try to do more than that, the quality suffers. So, you know, just like you were talking about. Brain can't handle it. Yeah, definitely. I mean, it takes a lot out of me to, to do these interviews. So it's fun and rewarding and wonderful as they are to talk to people. I, I am tired and I need a break afterwards. And so, you know, I can line them up back to back and I, I usually do that because I could do really like that. But, you know, I can, I can get those things done and then move on to doing something else and, and, you know, that kind of stuff. But it, it really does, it takes a toll on me. So, you know, when, when I do the interviews, that's, you know, that's what I do. And then I, you know, I do the editing still with audacity. And so, you know, I do that. Very nice. And, you know, save, save those files. And then I wrote some code to where I have a folder in my Dropbox that once I put edited files into my Dropbox, my code sees that there's new files there and it will append my intro and outro onto the thing. And it will then, it sends me emails saying, upload the, the, the, the headshot for, for the guest for this episode. And so, you know, I've got a webpage that I, you know, I click on the link there and upload the photo and it sends me another email that says, come here to do the show notes for, for this thing. And so then, you know, I, I click that link and it starts playing the audio in my browser and I've got some keyboard, uh, controls to where, you know, I can do timestamps and, and, you know, add links into the show notes and, and book recommendations. So, you know, I've got some code that queries Amazon for the books and some of that stuff. And so that's how I do my, my editing and show notes for the stuff. And then once, once I submit both the, the headshot and the, uh, and the show notes, then, um, that uploads my, uh, my, uh, it does the tagging of the audio file. It uploads the audio file to hosting, and then it schedules my blog post for creation as well. So that's, that's kind of my process of how I go through that. So I think I might've lost track of the question you were asking kind of both about my routine and daily life. And I think kind of about how I do the podcasting. So I've, I've rambled on. Does that answer the question? No, it does for, yeah, for the most part, really, I was asking about, you know, normal routine, what your habits look like. It's a big one that people are looking, looking to answer for themselves usually is what does my morning look like? What is a typical morning for me? What, should I be doing? And really, I think the interesting answer that's emerging from you is, um, that, that may not necessarily be the same for everyone, right? A lot of people say that, uh, oh, you know, waking up really early is, is the only way to be productive. Some people say that's ridiculous. That's, that's crazy. Uh, so it's interesting to hear that you actually naturally do that. It's not something that you've chosen to do, but rather that your body is just kind of wired that way. Yeah. You know, my, my friend, Ari Mizell, who is a productivity expert and another one of these non-programmers that I've had on the podcast, he's got this app that he created called, uh, the, it's the less doing peak time app, I think is the name of it. And, uh, you know, it's, it's available for iOS and Android, and you can, you can put this app on your phone and it's basically just a tap test, right? So it's just, you know, uh, the timer starts and you just start tapping away on your phone and it counts how many taps you can do. And if you do that test during, different times of the day, his theory, his, his, you know, assertion with this thing is that at that time of day where you are at your peak and you're at your best, that's when you can tap the fastest on the phone. And you know how true that is. I'm, I'm not completely sure, but I think it stands to reason that when you're at your best, you can probably perform that kind of motor activity pretty well. And so, um, that's one way that I would recommend to, you know, uh, figure out what is your, your peak time of day and do those, those activities that require your maximum focus during that time. Yeah. I think that's, that's really interesting. I actually downloaded the app, uh, as you were continuing to talk about it there because it's, well, first of all, it's very relatively simple app. So I assume it's pretty small, uh, downloaded very quickly. Yeah. I'm interested to try it out now. Um, I mean, you know, I've never really even thought about that kind of motor skill translating to my mental energy, but, uh, but they really are burning the same kind of thing inside of me, right? Like, uh, my, my, my brain is telling my finger to do something. And so, um, it stands to reason, like you said, that, that, that could be connected. Obviously the, the, I'm sure the jury's still out on that one, but, um, I would be interested to see, you know, I, I like that concept though, the idea that, Hey, you know, work during the times where you're going to work well. Right. And for some people working well as in the morning, there is some science to support that. Uh, obviously, uh, you know, the science about decision, fatigue is something we've talked about quite a bit on this show, but, you know, there's a lot of science that, that kind of underlines the idea of doing the most important things earlier in the day, uh, before you have reached that point of decision fatigue. But some people also have at least anecdotal experience with, uh, the night being their kind of their muse time, the time that they can really tap into that creative energy, whatever is causing that. I'm not really sure. Um, maybe they actually do. Yeah. It's interesting too. Tim Ferris talks about that. He writes best in, in the late nights and with wine. And, uh, you know, I think there is something different about the creativity of putting words out and, and, you know, that type of content versus writing code. Right. I mean, I definitely, uh, I write my best code early in the morning and that's, that's how I do things. And really, I think, you know, if, if I have some coding tasks that I want to get done today and I can finish them, I can do it. And I think that's a great way to do that. Before my kids get out of bed, that to me is that's bliss. That is absolutely beautiful. Right. So, you know, but yeah, not everybody is the same. And, and I think that's kind of the message of the peak time app is, you know, try to figure out what that time is and, you know, maybe the tap test helps with that. Maybe it doesn't, but, uh, experiment is really the message there. Yeah, absolutely. I agree with the, with the concept of experimentation, really that's just, uh, and if you're not familiar with experimenting in general, really all you're doing is try something, take some notes about what happened, try something else, take some notes about happen, what happened and then compare them. Yeah. That's, that's really what you're trying to do. No question. So, uh, I have, I have a couple more questions for you, Dave, and then we'll wrap this thing up going along with this idea of hobbies. I'm sorry, of habits. Uh, do you have any particular goals in the short term or, or in the longterm that you'd like to share with the developer T audience? Absolutely. Yeah. So one of the things that I'm really, uh, obsessed with recently is just the, the, the degradation of the level of discourse that I'm witnessing. And I'm sure everybody knows exactly what I'm talking about, you know, especially here in the U S where, uh, you know, this, this, uh, this ridiculous election nonsense, uh, you know, has everybody hating everybody, right? It's, you know, if, if you disagree with me, then you're not my friend anymore. Uh, kind of, kind of, uh, a sense going on. And I want to try to do something about that. It is obviously an ambitious mission to try to tackle something like that. But I think, you know, uh, the, the, the business of the world of, uh, you know, that we cannot peacefully disagree that, that there needs to be animosity. And I question somebody's, you know, their, their, their intent, their competence, their, their intelligence, because of, you know, some disagreement about a political thing is driving me nuts. So I want to do something about that. And I think that something is going to be that I want to start a podcast, uh, which I've already done, but I want to do another podcast, you know, developer on fire is something that, uh, you know, it's, it's been awesome and it is awesome. And I I'm going to continue doing it. Um, but it has limitations, right? I think in the beginning, it was wonderful for me that developer on fire was a pretty rote, you know, the, the, the, the, the, the, the, the, there, there's a script, right. A set of questions and it's, um, you know, different every time, but, you know, with a common structure and, and that, and, uh, you know, I, I listened to podcasts like, um, like the Joe Rogan experience, which is, you know, just a three hour marathon of just no plan, just a conversation. And, um, I, I think I wasn't ready for that when I began developer on fire. Uh, but I think I am now, and I think I'm ready to do something beyond software. So I want to create a new podcast, uh, while continuing to do developer on fire. I, you know, don't, uh, don't panic any developer on fire listeners out there. I, I, I intend to continue this and, uh, you know, it may be not forever, but, uh, you know, forever, as far as I can see for now. Um, but I, you know, I want to do, uh, not politics, politics to me is, you know, arguing about which narcissist sits in an office, right. Uh, I want to talk about philosophy, about the ideas behind, you know, really how we relate to one another and how we can get beyond some of our disagreements and, uh, see each other as worthy of, of civil discourse. Sure. Yeah. That's, that's a, so you've heard it first, uh, on developer T that Dave, Dave rail is going to, is going to start another podcast potentially. We don't know when that's going to happen, but, uh, or do you, do you have a, do you have a date in mind? I am, I'm thinking early 2017 is going to be the launch of it. I'm working this, this current contract that I'm on through November. And I'd like to do some of the, some of the legwork for, for in December. And, uh, and then, uh, in the new year, I don't want to commit to a specific date, but early in 2017, I think we'll, we will, we will see a new podcast and it's not going to be a developer podcast. That's great. So, uh, how can people find out about it? Do they, should they follow you on Twitter? Where should they follow you? That's, that's probably the best place. Yeah. Twitter, Twitter. Although, you know, I, to an extent, I, I really, I don't want to pollute my Twitter with non-developer stuff because I think that that's, uh, you know, that's, that's what it's all about. And really, that's one of the things that's been bugging me is that, you know, developers that I'm following are, are, uh, yelling at each other. Right. Um, so, uh, you know, so I, I don't want to be that very thing that I'm complaining about. Um, but, uh, I will, uh, make some kind of announcement about it on Twitter. Uh, it might not be easy to find there. Um, you know, that's a good question. I hadn't really thought this through yet. Yeah. Let's, let's say Twitter, rail yard on Twitter is probably the best place to find out about that. Perfect. Yeah. And, and even if you don't hear about it from, from there, I'm sure, uh, that if I see it, I will retweet it or I will send out a, some kind of message on the internet. It will be somewhere I'm sure. Yeah, definitely. So I actually have experienced a similar thing. There's, um, the, there are kind of brackets, limitations on developer T because I want to create, uh, content on developer T. I really enjoy creating content for developer T. It's a very interesting channel to me. Uh, but I also have other interests, right? I'm not just this, uh, this kind of easygoing guy only. Yeah. Uh, there are other things going on. Um, so I, you know, I'm maintaining developer T the content that's on developer T and it's intentionally approachable, but there's other things that I'm interested in. I've actually considered starting other podcasts as well. So, uh, we'll see if that, if that happens down, down the road. Uh, of course, you know, um, there's tons of other developer and designer podcasts on spec. So, uh, but I don't think it's actually going to end up being a designer developer podcast if I do start one. So. Yeah. Something different I think is really appealing. And the other constraint about developer on fire too, is that, I mean, that show is about the guest, right? I mean, I am, I, when you come on developer on fire as, as a guest of the show, I am featuring you, I'm telling your story. Or I'm facilitating you to tell your story. Right. And so me interjecting my, my opinions on those things, I think is valuable when it's relevant. Uh, but at the same time, um, you know, I, I hold back on, on, uh, you know, on really expressing my views on things at least to an extent, you know, so it's, uh, I think something where I'm, it's more conversational and it's more, uh, you know, I'm free to challenge things and I'm free to, uh, really explore that, that ability to connect with people and, uh, and find areas of common ground, even when we disagree. Yeah, absolutely. Well, that's fantastic. I'm excited about it. Yes. I have a couple more questions for you. Uh, like I said, we'll wrap it up. These are the two questions that I ask all of my guests. Uh, the first question that I have for you is if you could give every developer one piece of advice walking away from this podcast, what would it be? So I've said, I have this, uh, this mantra that I, I've introduced to my life and, uh, doing the podcast is a big part of it. And the, the mantra is punch fear in the face. And so, you know, the, the, the message, the advice is get involved, get out there and do it, right. You know, give that talk, uh, you know, ask that girl for a date or that guy, you know, whatever the case may be for your particular gender, your particular preference, whatever it is, right. Uh, don't stop living in fear, right. Because living in fear is the thing that kept me from being an engaged member of the community. And now that I am doing that, it changes everything. And life is so much better when you just ask for things. The biggest lesson that I have learned from doing the podcast is, you know, in getting these guests, right? And you've talked about it, you know, I've had, you know, the Uncle Bob's and the David Heinemar Hansen's on the show, you know, and John Skeet. Wow. You know, I got to talk to John Skeet. It's absolutely astounding. You know, just ask, right? You know, those people are people too. And if you ask them to have a conversation, chances are they're going to do it. And so, you know, punch fear in the face, get out there and do it. Absolutely. I couldn't agree more with that because really that fear, those messages of fear that you're telling yourself are, well, this person is going to think that I am fill in the blank, right? That I'm not good enough to be sending them an email. And what I'm saying is, you know, I'm not going to be sending them an email. What you're doing by stepping out and sending that email is just as much as you're affirming to them that you are, in fact, you believe that you are, in fact, worthy of their time, right? You are also affirming that to yourself. And every time you take a new step like that, it's going to embolden you further to take new steps into the future. That's the only way to advance your career. You are holding the baton to advance your career and not just your career, but also just your life, your personal life. So absolutely agree with that. Punch fear in the face. I like it. Yeah. And the last question that I'm going to ask you, Dave, thank you so much again for being on the show. What do you wish more people would talk to you about? And this can be anything. It doesn't have to be developer related. That's a tough question. I hadn't thought about that. This is always the hard one. Yeah. I want more people to tell me what they really want, right? That's, you know, really along the lines of that message there, right? I've learned that telling people what I want from them is, is liberating, right? And I want other people to have that same experience, right? So with me, right, if you want something from me, please tell me. And, you know, that's not a promise that I'm going to give you whatever it is that you asked for. But, you know, knowing that you asked and, and, you know, I am not going to tell you, you know, bug off, go away, right? I'm not going to tell you, you know, bug off, go away, right? I'm not going to tell you, you know, if, if the answer is no, it's, it's going to be a compassionate no. So, you know, I think that's the thing, right? I just, I want honesty about what, what people are looking for. And, you know, that, that I think would be the thing that I'd want most. And, and beyond that, you know, I really like talking about philosophy and some of those things. And I have, I have hesitated to do that. I've, I've been fearful of the response that, that there may be. And I think rightly so. In a lot of ways. But I think I'm going to loosen those restrictions, though, in the right context, right? You know, I think, you know, I, I definitely, you know, developer on fire is going to continue to be what it has been, because I think it works that way. And it's good for people. And so, you know, I want different channels to talk to people about different things. And so that's, that's, I guess, my message there. Yeah, that's great. And I, I, that message resounds with me as well. The idea of clarity, of honesty, of breaking down that, that barrier of, you know, trying to manipulate other people, manipulation, people can, can smell that from a mile away, right? It's, it's very obvious, you know, to the average person when you're not actually being upfront, when you're not telling the truth. And so more often than not, it's going to serve you better to be just as honest as you can. Yeah. Yeah. Which sounds, it sounds antithetical to a lot of advice that people who are listening to the show, you've probably, you know, you've probably, you know, you've probably, you know, you've probably heard over the years of, you know, don't, don't show your cards or whatever that crazy advice that you've received in the past about, you know, power, power dynamics and that kind of thing. The age now, the people who are in business now, especially the millennial, the millennial generation and, and beyond that, we value transparency far more than we value power, right? We, we value transparency probably more than we value money in some, in some ways we value transparency. So, you know, and take that advice to heart and not just because Dave is a, is a guest here and we're treating him well, but because we actually want the best for you. We're talking on this show because we want the best for the people who listen to this show. Absolutely. You know, when you talk about, when you talk about manipulation, right? The, the face that comes immediately to my mind is, is Palpatine, right? You know, I, I, everything relates to Star Wars in my mind, but, uh, you know, when I, when I picture that, that Senator that is, you know, uh, jostling for position and, and ultimately, uh, becoming the emperor, right? You know, I mean, that's, that's what manipulation is, right? It, it is that, that twisted, uh, two-faced, uh, you know, conniving behind the scenes kind of a thing where, you know, you, you see that smile, uh, you know, to your face and then you see something completely different. And, uh, the, the, the interesting thing is that, uh, the Jedi are no different, right? The Jedi mind tricks are all about getting somebody to do something that they don't really want to do. It's, it's that same manipulative marketing practice. And, uh, it's, it's counterproductive and it's destructive. And, uh, the, the, the openness is, it's just a better way to live. Absolutely. I couldn't agree more. Thank you so much again, Dave, for being on Developer Tea. Yeah. Well, thank you too, Jonathan. It's, uh, it's been a great pleasure and I, I really enjoy talking. Thank you so much for listening to today's episode of Developer Tea and for joining me for my interview with Dave Riel. Thank you again to Dave for coming onto the show. Go and check out developeronfire.com to see all of the amazing content that Dave is producing. And we'll be on the lookout for Dave's new podcast in the future. Thank you again to today's sponsor, Chartio. If you want to connect all of your services, that's things like Amazon RDS, uh, Cassandra, Redshift, even CSV file uploads or, uh, data from Heroku. Go and check out what Chartio has to offer. I'm just barely scratching the surface on what Chartio does for you. Go and check it out. spec.fm slash Chartio. That's spec.fm slash C-H-A-R-T-I-O. In the next episode, we will jump back into the developer career roadmap. If you don't want to miss out on future episodes of Developer Tea, including the developer career roadmap, go and subscribe in whatever podcasting app you use. It takes just a few seconds and all of the future episodes will be delivered to your device. Thank you so much for listening. I'll see you next time. Bye. And until next time, enjoy your tea.