Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

DevQuestions with Tim Corey

DevQuestions with Tim Corey artwork

259. The Shortcuts to Learning Software Development

May 22, 202515 minAudio

Now that I know what to avoid (the pitfalls from the last episode), are there some shortcuts to learning software development? How can I become a developer faster? These are the questions we will answer in today's episode of Dev Questions. Website: https://www.DevForge.com/ Ask Your Question: https://suggestions.iamtimcorey.com/ Sign Up to Get More Great Developer Content in Your Inbox: https://signup.iamtimcorey.com/

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_01Everyone wants to have a shortcut, especially when learning software development. The process of learning software development can be a long one, but there are ways to shorten the time between when you start learning a topic and when you feel like you're confident in your skills in that topic. In this episode of Dev Questions, we will go over the shortcuts to learning software development, whether you're just getting started or you're a seasoned professional who is picking you up a new skill. Just to be clear though, this is not a learn quick scheme or one of those one simple trick scams.

SPEAKER_01These shortcuts will make you faster, but they won't be magic. Let's talk about it in today's episode of Dev Questions.

SPEAKER_00Welcome to the Dev Questions Podcast with Tim Corey.

SPEAKER_01Software development is more than just writing code. So let's talk about the rest of it. Specifically, let's talk about the shortcuts you can take when learning software development. Now, before I get into the list, I want to prepare you. Your first instinct when you hear some of these answers will probably be to discount what I have to say because they all take effort. But that's why they're shortcuts. People tend to avoid the hard work. And so they waste time doing other things instead of just doing what they need to do.

SPEAKER_01And that's part of why these are shortcuts. Now let's get into the five shortcuts for learning software development. Number one, and if you've watched any of my other videos, you know the answer I'm going to say, but let's talk about why. So number one is practice. Yes, practice. This is by far the number one shortcut to becoming a software development. Let's put this in a different light. Let's say you're learning to drive a car. Now you could watch videos on how to drive a car.

SPEAKER_01You could learn every button, knob, and lever in the car. You could learn how to best optimize your mirror setup for your driving personality. You could know how to correctly set up everything in the car. You could even sit in the car and feel where everything is and make sure you know where everything is. That doesn't give you the skill to drive. What gives you the skill to drive is actually getting out there and doing it. I'm not saying those other things are bad things.

SPEAKER_01It's great to know what all the knobs and levers do. It's great to know how to configure your mirrors. It's great to know where everything is and how to get to it without even thinking about it. But you need practice. You need to actually drive on the road. Now, here's where software developers often go off course even when they're trying to practice. Let's take it back to driving again. Imagine I said, well, I'm going to go out there, I'm going to learn to drive, and so I'm going to practice driving by driving from city A to City B.

SPEAKER_01Well, that's not going to be terribly effective practice. Yes, it will give you some value, but let's just say that's a four-hour drive. Well, the start of that drive, you're going to have to navigate city streets, get on the highway, merge with traffic, get up to speed, maintain your lane, watch your mirrors, all great things and very, very helpful for learning to drive. But once you're up to speed, once you're in your lane, how much is there to do between city A and City B if it's a four-hour drive?

SPEAKER_01Probably not a lot. You're just maintaining your lane and watching your mirrors. Occasionally maybe passing a car or something like that. That's it. There's not a lot of value in that, even though you are driving. Now, it's still valuable, but you probably shouldn't do that every day. Driving from city A to City B and back again isn't going to give you the same experience as driving around in the city or in the country and dealing with things like merging with other traffic, making turns in a city, yielding to traffic, looking at lights and how to navigate those and right of ways and all the rest that you get with that smaller practice.

SPEAKER_01You can learn more in half an hour than in half an hour on the highway or an hour on the highway. Because the fact that what you're doing matters, the decision-making process that has to go into that driving experience is different. In the same way with learning software development, if you say, I'm going to build one app, I've got this idea for an app that I'm learning anyways, I might as well build that app. Well, you're going to spend a lot of time, kind of lost, first of all, but second of all, doing the same thing over and over and over and over again, but not really getting a whole lot of value out of it.

SPEAKER_01And so you're not going to get that same value as if you built tiny little apps that didn't mean anything, but that allowed you to do a number of steps over and over that are more like driving the city. So what kind of practice you do matters. I always encourage you, create practice projects you can throw away. You're not trying to build something. If you try to build something, you waste too much time on things that don't give you enough value per hour. You want value per hour, and that's the shortcut.

SPEAKER_01It's get that value per hour up by how you practice. The way you practice will make a huge difference in how much value you get out of it. That's number one. Number two is be intentional about what to learn next. If you are bouncing from topic to topic to topic, even if you're learning that topic deeply, are those connecting? Or are they just entirely separate things? What's the value of that next one? What's the value to you, to your career, to your objectives?

SPEAKER_01Because learning for learning's sake is fun, but not necessarily valuable to you. So I would encourage you to have an intentional list of these are what I'm going to do next and why. Why do you want to pick that next thing up? What's it going to help you in your career? Why is it going to be valuable to you? Because there is too much to learn in the software development industry so that you cannot learn everything. You just can't. You can't pick up everything.

SPEAKER_01You cannot be the everything to everybody. So you have to figure out what you're going to focus on. So focus on things that will help you in the long run. That's why when I teach C sharp, I teach things like Git and GitHub because they link together. And SQL is a great database for C sharp, even MongoDB or our Cosmos DB, because they link well. And Azure because it links well. And all of a sudden you have these connected things that go together rather than saying, okay, let's learn Python now, or let's learn Java now, or let's learn Rust now, because those are valuable languages and they do valuable things, but they don't connect well to what you already know.

SPEAKER_01And if they don't connect well, well then they're not going to be as helpful to you as if you have connected things together. So be intentional about what to learn next. That's number two. Number three is put your training on the calendar. Too often I've heard people say, yes, I want to learn. And I say, okay, when are you training? And they say, when I get time. What that means is it's the lowest priority for me.

SPEAKER_01Because if it's a high priority, you put it on the calendar. That doesn't mean it doesn't get bumped. But when it's on the calendar, you say, this is my priority. I'm stating this is my priority. And if I have to change it, well, then maybe I'll redirect it, put it somewhere else. So you might say, well, I'm going to train on Thursday between six and eight, but something comes up. You have a, you know, your child has a recital that night, go to that. But then move that instead of six to eight, either move it from nine to eleven, or you move it to Friday from six to eight, or Saturday from 10 to 12.

SPEAKER_01You move it on the calendar rather than just saying, oh well, because you make it a priority. So when you put it on the calendar, you make it a priority. And when you make your training a priority, all of a sudden you do it more often. When you do it more often, you get better results. When you get better results, you get closer and closer to your goal. So that's number three. Number four, don't switch midstream. So when you are learning a topic, often what's going to happen is you get to a spot where you're like, ooh, kind of bogging down here.

SPEAKER_01And it will be like magic, where you will see something else pop up, whether it's in your Twitter feed or whatever social media you consume, or it's something online, or Microsoft makes an announcement, or somebody else does, and you're like, ooh, I want to learn about that. And all of a sudden you switch from the thing that you are learning that you're halfway through, but you're kind of bogged down in, to something that makes you feel better because it's quick to learn, because everything's quick to learn at the beginning. Don't do that.

SPEAKER_01It's kind of like learning to be a marathon runner. When you're learning to be a marathon runner, I am not, but when you're, I've had a number of friends that are, and when you're learning to be a marathon runner, you have to run over and over and over again. You run longer and longer distances and you varied up and all that kind of stuff. But at some point it gets really hard and it's difficult and you have to push through. Well, at that point is not the time to say, you know what? Weightlifting, that's what I'm gonna do.

SPEAKER_01I'm gonna switch to weightlifting because you know, I've seen my friends are weightlifters and I could do that. And all of a sudden you switch to weightlifting. Is that gonna be effective? No, because you're now no longer a marathon runner and you're a beginner weightlifter, and you're not really either. So don't switch midstream. When things get tough, push through. All right. You want to be able to say, you know what? I stuck with it. Because when you stick with it, that's where everybody else drops off.

SPEAKER_01Because that's that's the key here is you want to go where others don't. You want to go beyond others who get distracted, who drop off because it's hard, who switch midstream. You want to go beyond that because on the other side are fewer and fewer competitors. And when you're looking for jobs, you want fewer and fewer competitors, not more and more. So don't switch midstream. Number five, embrace the hard thing.

SPEAKER_01This is something that has really benefited my career. It's, you know, anybody can, almost anybody can do the easy thing, right? The, oh, I'll take care of that simple task, or I'll do that simple bug fix, or I'll, you know, change these little things that anyone can do. I can I can learn the beginnings, the hello world of, you know, whatever language you want me to. But it's the hard thing. It's the, again, going back to number four, not switching midstream, the going deeper, the getting through the hard thing.

SPEAKER_01I've used this example before, but early on, mid of my middle of my career, um, before I started doing anything with social media or or sharing what I learned, I was learning log for net. And it was hard because there was not great documentation. And it confused me. Now, maybe as clear as crystal as somebody else, but for me, it was like walking through mud. I could not get my hands around what does this thing do?

SPEAKER_01How does it work? How do I configure it? What are all these different things I have to know? And there's a whole bunch of terminology that's kind of throw me for a loop. And so what I did, I sat down one Christmas break, I printed out all the documentation. They actually had good documentation, just not like connected documentation. It was like one specific feature we documented, but never like connecting it to the rest. So I printed out all the documentation and I read through and I started compiling a list. I pushed through and did the hard thing.

SPEAKER_01I created for myself a basically a cheat sheet of this is how it works, these are the terms, what they mean, this is how you set up everything. Here's examples for all these different things. And at the end of it, I had a working log4net setup. But I also had great documentation on how that worked. Now, I decided to just share that with the world. I said, hey, you know what? Maybe somebody else might need this. And turns out millions of people literally read that article because they found it helpful too, because they were in the same spot I was.

SPEAKER_01I just didn't realize it. I thought I was the only one. So by embracing the hard thing, what I found was that I actually put myself apart where I was now more of an expert in LogFournet. And people reached out to me and said, Hey, can you help me with my LogFournet? Hey, can you help me set this up because I know that you have done the hard thing that I couldn't do or that I don't want to do. And either way, I put myself forward, put myself ahead because I pushed through and did the hard thing.

SPEAKER_01And that is where you find that you provide value. When you can do the hard thing and others, again, fall away and don't do it. All of a sudden you're left standing there saying, I can do this. And the people that need that help rely on you. Shortcuts to your career. Okay? Now, these five points all come down to one word focus. If you can keep your focus when you are working towards your goal, you'll get there faster.

SPEAKER_01In a world filled with distracted people, stand out by not giving in. Thanks for listening. And as always, I am Tim Corey.

SPEAKER_00Thank you for joining us for this episode of Dev Questions. When you're ready to learn to think and code like a professional developer, head over to IamTimCorey.com and enroll in a course.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. 334. Is Entity Framework Still Relevant When AI Can Write SQL?

    Nov 5, 202614 minAudio

    Entity Framework and other ORMs write the SQL for us. But are they necessary now that AI can do that work? Is the overhead of EF on every query worth the limited benefits we now get at design time? Do ORMs still make...

    Credit the people on this episode

  2. 333. Why Boring Technology Wins

    Oct 29, 202621 minAudio

    Why don't companies use the latest frameworks and systems? Why is .NET Framework still used in companies? Why don't companies follow industry best practices in their apps? Why can't I use the latest tech at my software...

    Credit the people on this episode

  3. 332. What To Do When You Are Burned Out

    Oct 22, 202628 minAudio

    What do I do if I am burned out? How do I get through burnout? How do I get to the other side? How do I endure my job and my situation while experiencing burnout? These are the questions we will answer in today's...

    Credit the people on this episode

  4. 331. .NET 8 and .NET 9 Both Expire Next Month: Is LTS Still a Thing?

    Oct 15, 202613 minAudio

    .NET 8 is the LTS version of .NET, but it expires next month. Why? Why does .NET 9 expire at the same time as .NET 8? How does LTS work with .NET and why is it so short? Do these versions stop working next month? Why...

    Credit the people on this episode

  5. 330. What To Do When Someone Pitches You An App Idea

    Oct 8, 202621 minAudio

    What do I do if my friend wants me to build an app? How do I evaluate if an app is a good idea? Who should own an app if one person has the idea and the other builds it? How do I say no to an app idea? These are the...

    Credit the people on this episode