文字稿 🔗
WEBVTT
00:00:00.239 --> 00:00:02.799
Why are companies so far behind the times?
00:00:02.959 --> 00:00:12.480
New developers often want to learn the cutting edge technologies, but when they get their first job, they're shocked to see just how far behind the times their new company is.
00:00:12.720 --> 00:00:16.800
They might be using.NET framework or they might be using a long outdated system.
00:00:17.120 --> 00:00:18.559
So why is this?
00:00:18.719 --> 00:00:23.039
Why do companies gravitate towards boring and outdated technology?
00:00:23.280 --> 00:00:27.839
Why does it seem like the best practices never apply in the corporate environment?
00:00:28.079 --> 00:00:31.920
That's what we're going to discuss in today's episode of Dev Questions.
00:00:40.320 --> 00:00:43.759
Welcome to the Dev Questions podcast with Tim Corey.
00:00:44.399 --> 00:00:47.280
Software development is more than just writing code.
00:00:47.439 --> 00:00:48.960
So let's talk about the rest of it.
00:00:49.200 --> 00:00:54.159
Specifically, let's talk about why boring tech wins in business environments.
00:00:54.320 --> 00:00:58.640
Now there's more than one answer to this question, but I want to focus on the boring tech part.
00:00:58.799 --> 00:01:04.400
To do that, I first want to answer the other half, which is why companies don't upgrade the technology they use.
00:01:04.640 --> 00:01:07.040
And I think there's probably three major reasons.
00:01:07.280 --> 00:01:09.200
One, it's expensive.
00:01:09.439 --> 00:01:13.680
You're spending a lot of money to basically stay in place.
00:01:14.239 --> 00:01:24.640
So when you pitch an upgrade to your boss, you say, hey, we're on.NET 8, we should move it.NET 10, your boss says, well, that's an awful lot of money.
00:01:24.719 --> 00:01:25.599
How long is it going to take?
00:01:25.760 --> 00:01:28.959
Well, it's going to take two months worth of work and testing.
00:01:29.200 --> 00:01:33.680
Well, okay, if you start doing the math on that, that's just thousands and thousands of dollars.
00:01:34.319 --> 00:01:35.680
Is it worth it?
00:01:35.920 --> 00:01:43.840
And unless you have a good reason, the boss often will say, Well, no, I don't want to spend the money if there's not a great reason to do so.
00:01:44.000 --> 00:01:48.400
And just saying the version number gets bigger isn't enough of a reason.
00:01:48.560 --> 00:01:51.519
So part of this is on developers to have a really good reason.
00:01:51.680 --> 00:01:55.519
For example, I would say things like immediate performance improvements.
00:01:55.680 --> 00:01:57.439
You'll get that with an upgraded.NET.
00:01:57.599 --> 00:02:08.719
You also get the ability to be again shielded under the security blanket of updated security changes, which security is more and more of an issue, et cetera.
00:02:08.879 --> 00:02:12.800
So, but number one is it's an expense because it is expensive.
00:02:12.879 --> 00:02:15.680
And the end user doesn't see any new features.
00:02:15.840
Load full transcript
--> 00:02:18.560
They just see the same thing.
00:02:18.879 --> 00:02:26.800
So why is it that their work didn't get done, their new features didn't get added, new bugs didn't get fixed for two months while you upgrade?
00:02:26.960 --> 00:02:27.680
Is that worth it?
00:02:27.840 --> 00:02:29.439
It doesn't feel that way.
00:02:29.599 --> 00:02:31.039
So that's one reason.
00:02:31.280 --> 00:02:36.319
Now, again, I don't agree with that, but again, it comes down to how you talk about it.
00:02:36.560 --> 00:02:38.879
Number two is a lack of understanding.
00:02:39.039 --> 00:02:43.360
This kind of goes with number one, which is they don't understand why you would upgrade.
00:02:43.599 --> 00:02:44.960
It's working now.
00:02:45.199 --> 00:02:46.960
Why would we change it?
00:02:47.280 --> 00:02:50.800
So think about anything else you use in your life.
00:02:50.960 --> 00:02:52.159
Let's talk your house.
00:02:52.240 --> 00:02:57.680
I've been dealing with some house issues recently, but I have an air conditioning unit.
00:02:57.919 --> 00:03:01.120
Why would I ever change that out if it's still working?
00:03:01.360 --> 00:03:01.759
Right?
00:03:02.000 --> 00:03:03.919
I would keep it going as it is.
00:03:04.080 --> 00:03:08.639
There's no reason in my mind to say, well, yes, but it's it's been two years.
00:03:08.800 --> 00:03:10.800
It's time to get a new unit.
00:03:11.039 --> 00:03:13.199
Well, no, it's it's working now.
00:03:13.439 --> 00:03:18.800
This is the same mindset that management brings into upgrades.
00:03:19.039 --> 00:03:20.639
It's working now.
00:03:20.879 --> 00:03:22.159
Why would we spend the money?
00:03:22.319 --> 00:03:26.240
Again, expense, number one, but why would we do that when it's working?
00:03:26.400 --> 00:03:29.199
There's no reason to change just because of change sick.
00:03:29.360 --> 00:03:31.439
In fact, change is scary.
00:03:31.599 --> 00:03:33.439
Change causes problems.
00:03:33.840 --> 00:03:40.479
So it's a lack of understanding about what this change means and why it's actually more dangerous not to change.
00:03:40.560 --> 00:03:41.439
But that's number two.
00:03:41.680 --> 00:03:47.039
Number three is that users are often focused on features, not fixes.
00:03:47.360 --> 00:03:53.520
So, yes, they want bugs fixed, but they're really focused in on that new feature they want.
00:03:53.680 --> 00:03:55.439
Hey, I want the software to do this.
00:03:55.520 --> 00:04:00.719
And if you talk to a user and say, dream of me, what do you want to see in the software?
00:04:00.960 --> 00:04:06.639
They don't say things like, I would like to see new versions of.NET implemented.
00:04:06.800 --> 00:04:10.639
I would like to see those uh node packages upgraded.
00:04:10.879 --> 00:04:14.639
I would like to see the NuGet packages brought to the latest version.
00:04:14.800 --> 00:04:17.920
They don't say those things because they have no clue what those things even are.
00:04:18.160 --> 00:04:22.560
What they
say is, I would love it if the software would do X or Y.
00:04:23.040 --> 00:04:25.199
And that's what they see is progress.
00:04:25.360 --> 00:04:31.519
So if you don't start implementing new features, then they see the application as stagnant.
00:04:31.680 --> 00:04:33.439
They don't know what's going on behind the scenes.
00:04:33.519 --> 00:04:37.839
They don't know how many lines of code you took out or how many things are more efficient now.
00:04:38.079 --> 00:04:43.040
They may see performance improvements, and that's something you want to talk about a lot.
00:04:43.360 --> 00:04:46.800
But beyond that, they don't really see much change.
00:04:47.040 --> 00:04:52.720
So they're often focused on features, not on version numbers.
00:04:52.959 --> 00:05:00.800
So that's that's the one side of things about why companies don't upgrade their technology, which leads to them having old technology.
00:05:01.120 --> 00:05:08.399
But there's another side of this, and that is that companies don't tend to have the flashiest of products.
00:05:08.639 --> 00:05:11.199
Um, they tend, yeah, especially in enterprise.
00:05:11.360 --> 00:05:14.720
Um, the the software just gets the job done.
00:05:14.959 --> 00:05:19.680
It's not entertaining, it's not flashy, it just does the work.
00:05:20.000 --> 00:05:24.959
Um so and let's look beyond the the big players to the actual software that runs most companies.
00:05:25.120 --> 00:05:34.879
So I'm not talking about like, you know, Microsoft or Teams, which is, you know, we all have opinions on Teams, but let's talk about like the actual software that runs companies.
00:05:35.040 --> 00:05:36.399
Um it's boring.
00:05:36.639 --> 00:05:40.800
Battleship gray screens with standard fonts are really common.
00:05:41.040 --> 00:05:42.639
Um I used to be a consultant.
00:05:42.800 --> 00:05:49.920
I spent years going from company to company to company, working on their software, building some of these things, and then improving a lot of them.
00:05:50.160 --> 00:05:53.920
And it's pretty common that nothing looks good.
00:05:54.079 --> 00:05:55.199
It just works.
00:05:55.360 --> 00:05:58.879
Um they even have text-based data entry screens sometimes.
00:05:59.040 --> 00:06:02.639
Uh, there's a store in Dallas called Nebraska Furniture Mart.
00:06:02.720 --> 00:06:03.680
And it's a chain.
00:06:03.839 --> 00:06:05.680
Obviously, it's not from Dallas.
00:06:05.839 --> 00:06:09.040
Um, but Nebraska Furniture Mart is massive.
00:06:09.199 --> 00:06:10.560
I mean, it's a massive store.
00:06:10.639 --> 00:06:12.319
It's an event just to go there.
00:06:12.480 --> 00:06:16.000
It's it's actually not really great prices and a great selection.
00:06:16.240 --> 00:06:20.879
But their sales staff, they'll use tablets to help you check out right where you're at.
00:06:20.959 --> 00:06:23.920
So you say, I want this couch, they'll say, cool, they'll look it up.
00:06:24.000 --> 00:06:32.480
Here's the price, they'll put it on your order, and when you're ready, you give them a credit card and they can go ahead and take care of that right there, and then send your order onto the warehouse.
00:06:32.639 --> 00:06:35.199
And they use a tablet for that, which is very modern.
00:06:35.600 --> 00:06:42.319
But those tablets are running a web-based version of a text-based data entry screen.
00:06:42.639 --> 00:06:52.319
So it's the same data entry screen that I used to work on and modify back in the 90s when I was working on machine applications.
00:06:52.959 --> 00:06:53.600
Why?
00:06:53.839 --> 00:06:58.720
Why don't they have a flashy web app with images and Amazon-like shopping carts and more?
00:06:59.120 --> 00:07:05.519
Well, in my years of experience working with dozens of companies, it comes down to one of three things.
00:07:05.920 --> 00:07:07.439
Number one, it works.
00:07:07.519 --> 00:07:08.639
So don't change it.
00:07:08.879 --> 00:07:13.839
Like if you have something that works, again, it comes back to that air conditioning example.
00:07:14.079 --> 00:07:15.040
It works.
00:07:15.360 --> 00:07:21.839
So if this is the way we've done things for 30 years and it has worked all that time, why would we change it?
00:07:22.000 --> 00:07:29.839
Now, there are reasons, but that's one of the arguments is it works, so don't change it.
00:07:30.399 --> 00:07:35.759
Number two, it's heavily integrated systems that are outdated that really can't change.
00:07:35.839 --> 00:07:44.319
And this is a really common one where maybe that text-based system, all it is is just a web wrapper around the actual text entry screen.
00:07:44.399 --> 00:07:47.600
And it's even doing some really clunky stuff behind the scenes to make it work.
00:07:47.759 --> 00:07:48.879
I built those things.
00:07:49.040 --> 00:08:00.319
Um, but the reason why is because the systems and and processes that it connects to, those actual machines or other things, they don't have new upgraded software.
00:08:00.560 --> 00:08:02.959
I've worked a lot with manufacturing plants.
00:08:03.279 --> 00:08:13.519
And when you buy or install a machine in a uh in a plant, you typically don't get a new version in five years.
00:08:13.759 --> 00:08:22.319
You typically don't say, hey, that that big, very expensive uh thing, let's rip it out and put a new one in because it's a new model.
00:08:22.480 --> 00:08:23.360
That doesn't happen.
00:08:23.519 --> 00:08:27.680
So the software that runs those things, it is what it is.
00:08:28.000 --> 00:08:34.879
And you often have updates for a very long time, but at some point those updates go away and the machine is still in use.
00:08:35.279 --> 00:08:36.720
So what do you do then?
00:08:36.960 --> 00:08:42.320
Well, you keep running a machine and just have to have software that integrates with that.
00:08:42.480 --> 00:08:52.480
And that can be true for conveyor systems, or it can be true for any number of other things that might go into supporting an enterprise business.
00:08:52.799 --> 00:08:58.720
So if they're heavily integrated into systems that are outdated, you're not gonna get a whole lot of change.
00:08:58.960 --> 00:09:16.399
And then third, and this is one that I see way too often, is there were upgrades that were proposed, but those upgrades are proposed, or even they try to implement those things and they were very expensive and they were less efficient.
00:09:16.639 --> 00:09:18.159
This is one that's very common.
00:09:18.320 --> 00:09:22.399
Um people see an old system and they say, ah, I could do so much better than that.
00:09:22.720 --> 00:09:27.440
They see the Nebraska furniture more, and they say, you know what, text-based data entry, it's not where it's at.
00:09:27.600 --> 00:09:31.120
We've got a modern web, we've got a modern way of doing things.
00:09:31.360 --> 00:09:36.480
We can build a site that is so much better, so much faster, um, and so much more efficient.
00:09:36.639 --> 00:09:42.080
And then you actually start doing it and you're like, ooh, I didn't realize all these edge cases existed.
00:09:42.240 --> 00:09:46.399
And you have workarounds and systems and other things that you have to try and figure out how to make work.
00:09:46.559 --> 00:09:59.679
And before you know it, you have this clunky system that is really complicated and really fragile and it's really expensive, and it doesn't do it as efficiently as the boring system that just worked.
00:09:59.919 --> 00:10:11.679
And that's where companies, after a while, they get jaded to this and say, you know what, we're not spending millions on consultants to come in and you know, give us a flashy new product that won't work.
00:10:12.080 --> 00:10:14.720
And so they kind of stay where they're at.
00:10:15.039 --> 00:10:17.440
So it works, so don't change it.
00:10:17.600 --> 00:10:24.080
It's heavily integrated in systems that are outdated, and every proposed upgrade was actually less efficient.
00:10:24.399 --> 00:10:26.799
So where does this leave us?
00:10:27.360 --> 00:10:29.759
I think there are things to learn from all these things.
00:10:29.919 --> 00:10:35.360
I think that the my challenge to you is to make boring software.
00:10:35.600 --> 00:10:39.200
And that may feel boring.
00:10:39.440 --> 00:10:41.679
It may feel like I don't want to do that.
00:10:41.919 --> 00:10:49.679
But I think it's really important as software developers when you're thinking about how to make a mark on on what I do.
00:10:49.840 --> 00:10:53.440
How do I make sure that I am invaluable as a developer?
00:10:53.519 --> 00:10:58.480
How I make sure that if I build a product, that people actually use it.
00:10:58.720 --> 00:11:03.600
And I think one of the big things you can do is make boring software.
00:11:03.840 --> 00:11:05.679
And what do I mean by boring?
00:11:06.159 --> 00:11:09.600
Make software that is incredibly efficient.
00:11:10.159 --> 00:11:14.960
So when you're building software, too often people start with a user interface.
00:11:15.039 --> 00:11:24.000
And they start with, you know, how to make this thing look pretty and how to make it, you know, look modern, and they're focused in on colors and fonts and styles and that kind of thing.
00:11:24.799 --> 00:11:28.240
That's not where your application should shine.
00:11:28.639 --> 00:11:32.960
Now, to be clear, I do think your application should look good.
00:11:33.200 --> 00:11:37.120
I do think your application should be more than just battleship gray.
00:11:37.600 --> 00:11:44.720
But I think it's more important that you focus on making it incredibly efficient.
00:11:45.279 --> 00:11:56.559
Talk to the people who are actually going to use your application and figure out every possible place that you can take time out of the process.
00:11:56.960 --> 00:12:00.480
So it could be as simple as don't touch your mouse.
00:12:00.720 --> 00:12:10.879
So if you're building a desktop application or a web application or a mobile application, especially desktop and mobile because, or desktop and web, because mobile doesn't have a mouse necessarily.
00:12:11.120 --> 00:12:19.919
But try to figure out how do I stop the user for having to move to another device, like a mouse, to move a cursor down and click next.
00:12:20.080 --> 00:12:24.240
Maybe it's a it's you know, keystrokes and trying to figure out hotkeys and things like that.
00:12:24.399 --> 00:12:28.960
Try to figure out how do I help this user move quickly through the system.
00:12:29.200 --> 00:12:35.360
The point isn't to spend time in your application, the point is to help them get the job done.
00:12:35.600 --> 00:12:49.600
If you can change that paradigm in your mind to go from the point is to use my application to the point is to use my application as little as possible to do the job, you're gonna write a whole lot better software.
00:12:49.919 --> 00:12:56.240
Number two, focus on making your customers successful before you make it pretty.
00:12:57.919 --> 00:13:04.639
The goal of your application is not to be the next Mona Lisa of designs.
00:13:04.799 --> 00:13:09.440
Your goal is not to win awards for how pretty it looks.
00:13:09.759 --> 00:13:14.799
Your goal is to make your customer successful.
00:13:15.120 --> 00:13:19.840
Now, your customer might be internal, your customer might be your boss, whoever the case may be.
00:13:20.080 --> 00:13:23.440
Your goal is to make them successful in what you build.
00:13:23.759 --> 00:13:27.039
Spend almost all of your time there.
00:13:27.919 --> 00:13:37.039
Yes, make it look good, but that's a secondary goal compared to your primary goal of making your customer successful.
00:13:37.440 --> 00:13:41.759
Number three, make your apps rock solid.
00:13:42.240 --> 00:13:42.559
Okay.
00:13:43.519 --> 00:13:50.080
This is something that microservices really hurt this case here.
00:13:50.240 --> 00:13:54.960
Um, the whole idea behind microservices was hey, we can make things more resilient.
00:13:55.120 -->
00:13:59.519
And that can be a very good thing, especially if you're at the Amazon level.
00:13:59.759 --> 00:14:02.159
But most people aren't at the Amazon level.
00:14:02.320 --> 00:14:05.840
They're at the 100 people use this at a time level.
00:14:06.240 --> 00:14:20.879
And the problem is the more dependencies, now I don't just mean like NuGet packages, but I mean things like if you have a front-end app that's that's a web UI and it depends on API, but that API depends on a database.
00:14:21.039 --> 00:14:23.679
Okay, so there's three links in the chain there.
00:14:24.080 --> 00:14:27.120
Your front-end, you have your API, and you have your database.
00:14:27.360 --> 00:14:31.120
If one of those goes down, then your app is down.
00:14:31.279 --> 00:14:41.039
It might say, well, okay, so I'm gonna put a message bus in the middle so that I have more resiliency, like the front end can still work if the middle is down or something like that.
00:14:41.279 --> 00:14:50.879
Yes, but now you have even more dependencies and interconnectedness where if something were to happen to one of those servers, you've got a problem.
00:14:51.200 --> 00:15:00.879
And so what happens is we built more and more complex applications that, yeah, it works in the web, it works on mobile, it works all over the place.
00:15:01.200 --> 00:15:02.799
But is it rock solid?
00:15:03.039 --> 00:15:05.919
Or is it a bit messy, it's a bit muddled?
00:15:06.399 --> 00:15:17.679
Sometimes the best thing you can do is write a desktop application, a thing that installs locally, has local storage for data, and it just works.
00:15:17.919 --> 00:15:19.039
It doesn't crash.
00:15:19.360 --> 00:15:32.000
You think about it, every time your application crashes, every time it's slow, every time one of the dependencies is down and causes a slowdown in the system, you are hurting your user.
00:15:32.320 --> 00:15:35.759
Your user is waiting on the application.
00:15:36.399 --> 00:15:40.320
That makes your application less reliable.
00:15:40.720 --> 00:15:44.960
And this is where you want to be a boring system that just works.
00:15:45.200 --> 00:15:47.759
You want to be a thing that no one has to think about.
00:15:48.080 --> 00:15:50.879
No one has to wonder, is it gonna be okay today?
00:15:51.200 --> 00:15:54.080
You want to make sure that your app is rock solid.
00:15:54.559 --> 00:16:01.440
Every possible case you want to work out so it's as efficient as possible and it's as performant as possible.
00:16:01.600 --> 00:16:11.919
And part of that is making sure that you don't depend on too many things, more than you have to, especially, so that you can make sure that your application always works.
00:16:12.480 --> 00:16:16.960
And finally, define your success on performance, not features.
00:16:17.200 --> 00:16:22.639
Kind of goes back to the previous ones, but define your success on performance, not features.
00:16:24.080 --> 00:16:31.679
You've if you've listened to me at all, you've
you've probably heard me not rant, but kind of rant around Microsoft's tooling.
00:16:31.840 --> 00:16:35.919
Um let's take an example that probably everyone knows about Microsoft Word.
00:16:36.240 --> 00:16:39.120
So what's the point of Microsoft Word?
00:16:39.360 --> 00:16:43.679
Well, it's to be an editor for documents.
00:16:43.919 --> 00:16:44.399
Cool.
00:16:44.639 --> 00:16:44.960
Okay.
00:16:45.600 --> 00:16:48.639
How many features does Microsoft Word have?
00:16:49.759 --> 00:16:54.480
Could you put that into the 10, 20, 30, 50, 100?
00:16:54.639 --> 00:16:56.000
Could you even get close?
00:16:56.240 --> 00:17:00.879
Or would you not even realize just how many features are inside of Word?
00:17:01.120 --> 00:17:06.799
And then do you know how to use 50% of them, 30% of them?
00:17:07.759 --> 00:17:20.400
What happens is as software matures and grows, there's one more feature, one more feature, one more feature that keeps getting requested until your app is this bloated mess that no one knows how to use.
00:17:20.640 --> 00:17:26.240
It's slower because every little feature takes a little bit more uh effort out of it.
00:17:26.559 --> 00:17:33.839
If you've used Visual Studio, you've seen this in action because we've had Visual Studio for decades now.
00:17:34.480 --> 00:17:37.599
And we keep getting more and more cool features.
00:17:38.079 --> 00:17:41.839
But because of that, it keeps getting slower and slower.
00:17:42.079 --> 00:17:48.240
And the team has done a great job at trying to improve that, trying to bring back performance, et cetera.
00:17:48.400 --> 00:17:53.200
But that's a constant struggle because of all the stuff that's in Visual Studio.
00:17:53.359 --> 00:18:02.000
Now, VS Code came out, and all of a sudden, this is a snappy code editor that is just so fast, but it doesn't have all the features.
00:18:02.160 --> 00:18:08.559
And so they start putting the features into VS Code, and all of a sudden it starts to slow down a bit, right?
00:18:08.720 --> 00:18:09.599
This is what happens.
00:18:09.759 --> 00:18:12.000
It's the cycle of software.
00:18:12.240 --> 00:18:13.839
Be very careful about that.
00:18:14.000 --> 00:18:18.480
Be careful you define your success on performance, not features.
00:18:18.720 --> 00:18:25.920
Because it does not matter if you have 100 great features, if none of those features are very performant.
00:18:26.480 --> 00:18:30.000
Because people just aren't going to want to use it or can't use it.
00:18:30.160 --> 00:18:34.160
It's just too slow, or it crashes, or it's not reliable.
00:18:34.400 --> 00:18:44.160
But instead, if you do the one thing that you're designed to do really, really, really well, then you're just that reliable thing they always rely on.
00:18:44.319 --> 00:18:49.599
They always come back to because it's all about the fact that you get out of the way.
00:18:49.759 --> 00:18:52.559
Your application is not the star they are.
00:18:52.880 --> 00:18:58.079
You are saying, I want to get you in and out and on your way as soon as possible.
00:18:58.319 --> 00:19:01.759
Define your success on performance, not features.
00:19:02.000 --> 00:19:05.839
Again, that does not mean you can't have more features.
00:19:06.240 --> 00:19:14.640
It just means that your success is defined by the performance of your application, not on how many features you have.
00:19:14.880 --> 00:19:20.160
Okay, so boring applications are really valuable tools.
00:19:20.319 --> 00:19:25.279
And unfortunately, today, we're getting farther and farther away from those boring tools.
00:19:25.440 --> 00:19:30.880
We're getting to the point where we're focusing more on things like, hey, does it deploy everywhere?
00:19:31.039 --> 00:19:33.279
Does it have all the features?
00:19:33.599 --> 00:19:36.000
Is it quick to build?
00:19:36.240 --> 00:19:40.000
And yet that's not the right set of metrics.
00:19:40.160 --> 00:19:48.079
This is why when you open up Microsoft Word now, it's a web-based app, which quite frankly isn't as good as a desktop app.
00:19:48.319 --> 00:19:51.599
It's not as performant, it's got quirks to it.
00:19:52.400 --> 00:20:01.920
Outlook drives me nuts because of the fact it's a web app and it doesn't have some of the features that Outlook used to have that I relied on.
00:20:02.240 --> 00:20:05.599
Because, well, it's web-based now, so you can deploy it to more places.
00:20:05.759 --> 00:20:09.839
Yes, so you have a lesser product deployed to more places.
00:20:10.400 --> 00:20:16.960
I want you to focus on making better products, even if they are more tightly targeted.
00:20:17.200 --> 00:20:17.519
Okay.
00:20:17.920 --> 00:20:20.559
This is what's going to create great software.
00:20:20.799 --> 00:20:23.039
This is the thing that people keep coming back to.
00:20:23.200 --> 00:20:29.599
Instead of saying, I'm going to hold my nose and use this tool, they say, this is the tool you have to use.
00:20:29.759 --> 00:20:30.240
All right.
00:20:30.400 --> 00:20:35.359
That's what I want you to build for your software, even if it does feel a little boring.
00:20:35.519 --> 00:20:35.920
All right.
00:20:36.079 --> 00:20:36.960
Thanks for listening.
00:20:37.039 --> 00:20:39.200
And as always, I am Tim Corey.
00:20:39.839 --> 00:20:42.799
Thank you for joining us for this episode of Dev Questions.
00:20:42.960 --> 00:20:51.279
When you're ready to learn to think and code like a professional developer, head over to IamtimCorey.com and enroll in a course.