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

280. Learn How To Make Your Ideas Matter

Oct 16, 202512 minAudio
ShareXLinkedInFacebookWhatsAppEmail

How do I make my ideas matter? How do I turn my ideas into finished projects? I had the idea for a successful product before someone else did. Why don't people listen to my ideas? 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_01When Google first came out, I remember having multiple conversations where people said, I could have done that. If you've ever played Wordle, you probably looked at it and said, I could have done that. In fact, there are probably examples of software out there today that you had thought about building. You might have even been working on a version of the software when someone else released theirs. As software developers, we can have great ideas and the ability to turn those ideas into reality. So why is it that we don't?

SPEAKER_01How you take those ideas that you have and make them matter? How you turn your concepts into successful businesses. That's what we'll talk about 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 making your ideas matter. I remember having a conversation with two Microsoft MVPs when I was just getting started with teaching C. I was telling them that I had started selling courses and that it was going well. I was able to supplement my income by creating paid courses. Their reactions were both along the lines of, oh, I've been made to do something like that. Both of them were skilled communicators.

SPEAKER_01Both were skilled developers. Both had the ability to make good courses. Both knew exactly which courses they would make. Neither did. I see that type of scenario over and over. Skilled people with great ideas that don't go anywhere. So let's talk about the steps you need to make your ideas matter. Number one, have a clear, achievable goal.

SPEAKER_01This is one that people often get wrong because they have these grand ideas. And when I start asking questions, they don't really know the answer. It's more hand wavy. So they say, you know, I'm going to build a search engine. Okay. Where are you going to host that? Oh, I don't know. What kind of coding I use for that? Well, I'm going to use C Sharp. Okay, great. Have you ever built anything like that? Uh no. Do you know what it's going to take?

SPEAKER_01No. What database are you going to use? I don't know. Okay. All of a sudden what you have is a vague notion of a thought, of an idea. That's not the same thing as having a clear, achievable goal. Building a search engine? Probably not your first out-of-the-do. That's a lot of work. But maybe having a clear achievable goal is saying, I'm going to build this specific app. Here's how, here are the things I'm going to do, and here are the steps I'm going to take to do it.

SPEAKER_01Having ideas that you're throwing all these things into it, not an achievable goal. Okay. So maybe having the first goal be something very, very simple. That's really important. Okay. And then with that, make sure that it solves a real problem. Usually these things solve problems, but if you're not careful, when you start dreaming and start thinking up through how this app might work, you lose the thread of why does it matter?

SPEAKER_01Why does it matter that you have this app? Why does it matter that you're building this solution? What's the goal here? What's it going to do to help people? Because if it doesn't really solve a problem, then why are we doing this? Okay, so have a clear, achievable goal. That's step one. Number two, put in the hard work. It's very easy to do file new project. File new project is so rewarding because things happen right away.

SPEAKER_01And you can work on that over and over. And you can do, you know, get the starting steps in. And this is why if if you ever talk to people who are starting a business, you'll see that they have business cards, they have pens with their names on them, they have maybe even shirts or golf shirts with their name on them. They have the domain name, they have all these things around the business, but that's the easy stuff, right?

SPEAKER_01That's the stuff that is quick to do, and you can, as a result, have something in hand. But it's not really the business, right? It's the easy work, not the hard work. With software development, the hard work isn't file a project. It's getting through to the end goal. It's putting in authentication. It's making sure you check all your edge cases. It's making sure that you have a complete process in place and you have a logging in.

SPEAKER_01You have all these things in place that sometimes that last 5% is the longest 5%. Well, that's the hard work. Pushing through and getting the hard work done is what's going to separate you from a lot of people. Because a lot of people will get to the point where they start banging their head against the desk and go, ooh, there's a new idea I have. Finally, project. And they're going to drop off. Where you want to be different is you want to put in the hard work.

SPEAKER_01Now, this helps if you have a clear achievable goal. Because if your goal is a bit vague, if you're not quite sure, well then it's even harder to actually implement that. And so it's that hard work becomes impossible work. So step one, clear achievable goal, is the foundation for step two, putting in the hard work. Number three, finish it before you're ready. Projects are never completed, they're abandoned.

SPEAKER_01That's really it's a quote from someone I forget who it's from, but that's the kind of thing that you need to think through is how do I finish this? Not how do I get everything done, but how do I get it to the point where it's ready to go out the door? Because too often people have these projects where they're mostly done. They're almost done. Boy, I'm close. And either they stop putting the hard work or they just aren't ready to say it's finished.

SPEAKER_01They aren't ready to put it in front of people and say, here, try it, because they know they're going to get feedback. Well, this isn't ready yet. And this isn't ready yet. Yeah, it's not. It's not ready yet. It's it's not perfect. It's got features that need to be added. It's it's got things that it doesn't do yet, but it does the one thing, and that's good enough to get it started. And then we'll keep adding those things. So finish it before you're ready. And then number four, importantly, critically, tell people about your product or solution.

SPEAKER_01People call us marketing or sales. That can be, but at the very least, you have to communicate. A company that's not great at this is Microsoft. If you look at what Microsoft offers, you'll probably be shocked. There will probably be products that Microsoft offers that you might even want to use that you have no clue even exist. They have people working on them, they've had people working on them for years. They have solutions out there that you're like, I didn't even know it was a thing.

SPEAKER_01And you find out that, yeah, it's a thing. And it's got all this really cool stuff, and you don't even know about it. Even in the.NET space, I work hard to bring things to light because people go, I didn't know that was a thing. I didn't know it existed. Right. You didn't. Because even though it exists, even though there has been communication about it, there's not been enough. And you have to figure out ways to do that. You need to figure out, you know, who am I helping? What's that real world problem solving?

SPEAKER_01And then how do I get in front of those people, the people who have that problem? So that's step four. Now, it's important to do it. It's important to spend a lot of time in step four telling people. But it's critical that you can't tell people about your project solution if you don't have it. So you had to have a clear, achievable goal, you've had to put in the hard work, and you've had to finish it, especially before it's ready. But you had to do all those things in order to get to step four, which is telling people.

SPEAKER_01Too often people skip to step four, right? They tell people about their great idea. I got this great idea. That's great. Um, doesn't matter. You know, and that's kind of harsh and that hurts to hear. But I've got hundreds of great ideas. I've got a OneNote that's that's filled with great ideas. For my company, I've got great ideas for you. I've got great ideas I want to implement to help you learn software development better. But they're sitting there.

SPEAKER_01And so they're just ideas at this point. And that's not going to help anybody. I need to work to change the idea into a finished product that's launched that I can then tell you about. Because if I get that out of order, well, then we're just dreaming and we're just wishing. And wishing doesn't really help us actually make our products matter. So doing these four steps isn't going to guarantee success. I didn't say if you do these four steps, your product will matter, that people will love it and it will be a success.

SPEAKER_01But not doing any one of those four steps almost certainly guarantees failure. So I can't guarantee success. I can't guarantee the public will love it. I can't guarantee it will be the next billion-dollar idea. But I can almost certainly guarantee that if you don't do these four steps, that your product's going to be a failure. So you can take almost certain guaranteed failure and change into has a chance for success by doing those four steps.

SPEAKER_01So turning your idea into something that works puts you into a very small group of people. Just getting to the it's launched, not even step four of telling people. Just getting into the it's launched puts you in a very small group of people. Like I said, I have fellow MVPs that say, Oh, I'd love to create a course. Great. Have you? Well, no, I, you know, you could have. And quite frankly, there's a lot of people out there that are better communicators than I am, that are smarter than I am, that know more about software development than I do, that haven't.

SPEAKER_01It's putting you into a very small group of people when you actually complete, when you actually finish something, deploy something. Most people get stopped at the idea stage. Then the next group of people get stopped at the hard work stage. The next group gets stopped at the, well, it's not quite finished stage. Okay? By turning your ideas into a working product, you give it the only possible chance it will ever have to succeed.

SPEAKER_01Make your ideas matter by actually building and launching them. Thanks for listening. 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