文字起こし 🔗
WEBVTT
00:00:04.000 --> 00:00:07.360
It seems like everyone is vibe coding apps and tools these days.
00:00:07.519 --> 00:00:12.800
With code being so easy to write with AI, it's easier than ever to turn an idea into a product.
00:00:13.039 --> 00:00:17.199
Unfortunately, building that product was almost never the hardest part.
00:00:17.519 --> 00:00:20.800
Building a secure performant product is much harder.
00:00:20.879 --> 00:00:24.239
And then supporting it long term is even harder still.
00:00:24.480 --> 00:00:29.440
These are the areas where a lot of apps and libraries are already failing.
00:00:29.760 --> 00:00:34.479
So how do you know what tools and libraries to depend on when you're building your own app?
00:00:34.719 --> 00:00:40.079
Should you build everything yourself, or should you only depend on tools from reputable sources?
00:00:40.320 --> 00:00:43.759
Let's talk about it in today's episode of DevQuestions.
00:00:51.920 --> 00:00:54.719
Software development is more than just writing code.
00:00:54.880 --> 00:00:56.320
So let's talk about the rest of it.
00:00:56.479 --> 00:01:02.799
Specifically, let's talk about how to evaluate third-party tools and libraries in the age of AI.
00:01:03.119 --> 00:01:08.560
Now, I don't know about you, but I get nervous anytime I see an app that was clearly vibe-coded.
00:01:08.719 --> 00:01:19.359
I have seen too many instances of apps that seemed to work only to discover later that they leaked all their sensitive data or that they'd failed the worst moment and were just abandoned.
00:01:19.599 --> 00:01:29.519
If you are building an app, you probably are going to depend on third-party resources like emailers, PDF tools, data access libraries, and more.
00:01:29.760 --> 00:01:36.000
So, how do you know what's a good app to depend on and what's not a good app to depend on?
00:01:36.319 --> 00:01:46.879
So let's talk about what not to look at or not to depend on when validating a third-party library app.
00:01:47.280 --> 00:01:49.599
Number one, open source.
00:01:49.920 --> 00:01:53.519
Just because something is open source doesn't make it good.
00:01:54.719 --> 00:01:59.439
The kind of misconception is, well, if it's ever a problem, I can just fork it and build my own.
00:01:59.680 --> 00:02:00.159
Really?
00:02:00.400 --> 00:02:00.799
Really?
00:02:01.040 --> 00:02:02.239
Have you ever tried that?
00:02:02.480 --> 00:02:11.840
Have you ever actually done the work of saying, hey, let's test out what would happen if this library suddenly stops supporting the latest version of.NET?
00:02:12.000 --> 00:02:14.479
Could we upgrade it to the latest version of.NET?
00:02:14.719 --> 00:02:15.919
Have you tried?
00:02:16.240 --> 00:02:20.400
Because more than likely, it's not nearly as easy as you think it is.
00:02:20.639 --> 00:02:32.159
And even if you say, well, we're going to use AI and just have AI do it, it that's even harder because now you have an app that AI is not going to fully read through that third-party system.
00:02:32.639 --> 00:02:39.919
And so it's going to make some guesses and it's going to create more and more spaghetti code until you ring it in and you won't because you don't know the code itself.
00:02:40.080 --> 00:02:44.080
And so it just creates a bigger ball of mess to deal with.
00:02:44.400 --> 00:02:49.840
So just because something is open source doesn't mean it's a good system to depend on.
00:02:50.240 --> 00:03:00.560
Now, being open source can be a valuable thing and it can be a point in its favor, but don't look at something and say, oh, well, it's open source, that must be good.
00:03:01.199 --> 00:03:04.960
So don't look at open source as the qualifier for something to be good.
00:03:05.120 --> 00:03:06.479
There's other things to look at.
00:03:06.800 --> 00:03:11.520
Number two, don't look at just because it's a product from a big company.
00:03:11.759 --> 00:03:18.800
There is a whole Twitter account dedicated to apps killed by Google, because Google is notorious.
00:03:19.039 --> 00:03:31.039
In fact, I've told my team, I said, we will not rely on products from Google because they're just notorious for shutting down good working products.
00:03:31.439 --> 00:03:33.280
So not going to trust it.
00:03:33.599 --> 00:03:42.000
Even Microsoft and Microsoft is better, but they still have a number of dead products in their wake.
00:03:42.080 --> 00:03:44.719
And you might say, well, no, there's bad as everybody else.
00:03:45.039 --> 00:03:47.599
To be fair, WinForms.
00:03:47.840 --> 00:03:54.560
WinForms has been supported since.NET 1 back in 2001, 2002 timeframe.
00:03:54.639 --> 00:03:56.319
That's 24 years.
00:03:56.639 --> 00:04:01.199
We've had.NET WinForms, and that's been supported that entire time.
00:04:01.439 --> 00:04:05.439
So they do have a long track record of supporting certain things.
00:04:05.599 --> 00:04:06.319
Not everything.
00:04:07.599 --> 00:04:09.759
It needed to die, but it did die.
00:04:09.919 --> 00:04:10.240
Okay.
00:04:10.639 --> 00:04:17.199
And then there is the WCF, and there's, you know, Silverlight always gets thrown in there, but that's not really their problem.
00:04:17.360 --> 00:04:23.120
But at the same time, yeah, it's an app that died because a different big company killed it.
00:04:23.439 --> 00:04:27.839
So just because it comes from a big company doesn't mean it's going to be around forever.
00:04:28.000 --> 00:04:31.680
It might last a year or two, or it might last for 20 years.
00:04:31.839 --> 00:04:33.040
You just don't know.
00:04:33.519 --> 00:04:36.720
And saying, well, they have mountains of money to support it.
00:04:36.959 --> 00:04:38.160
Yeah, do they though?
00:04:38.399 --> 00:04:44.639
Because every time I turn around, it seems like these big tech companies are laying people off and cutting divisions.
00:04:44.959 --> 00:04:55.360
So while it may seem like they have lots of money, typically that lots of money goes towards shareholders, not towards
Load full transcript
your particular library that you want supported.
00:04:56.319 --> 00:05:00.079
So just be careful saying, well, it's a big company.
00:05:00.399 --> 00:05:01.519
Doesn't mean anything.
00:05:01.759 --> 00:05:07.920
Number three, just because it has a lot of stars on GitHub doesn't mean pretty much anything.
00:05:08.240 --> 00:05:11.759
Stars don't pay the bills, they don't indicate quality.
00:05:12.079 --> 00:05:24.160
They don't in any way give you an indication that this is a good library, except for the fact that a number of people have said, yeah, I want to watch this, or yeah, I think this is an interesting project.
00:05:24.399 --> 00:05:28.319
Now, when a lot of people say that, it could be good.
00:05:28.720 --> 00:05:34.959
But I see a number of projects that are bad projects, but they've got great marketing.
00:05:35.120 --> 00:05:37.519
And all of a sudden they have lots of stars on GitHub.
00:05:37.759 --> 00:05:39.360
So just be careful.
00:05:39.600 --> 00:05:44.800
There is a data point, but it's not a deciding factor.
00:05:44.959 --> 00:05:47.519
Just like open source, it's a data point.
00:05:47.600 --> 00:05:49.519
It should not be a deciding factor.
00:05:49.839 --> 00:05:55.839
So what should you evaluate when it comes to a third-party library or tool?
00:05:56.079 --> 00:06:00.560
Well, number one, does it have a monetization strategy?
00:06:01.120 --> 00:06:04.000
This is something that people just don't understand.
00:06:05.040 --> 00:06:16.480
If a tool, if a library, if something you depend on does not have a way to make money, it does not matter how enthusiastic the team is.
00:06:17.279 --> 00:06:18.639
It is in danger.
00:06:18.800 --> 00:06:20.160
I'm not saying it's going to go away.
00:06:20.319 --> 00:06:22.560
It may last for life.
00:06:22.800 --> 00:06:24.399
You don't have to pay for Linux.
00:06:24.560 --> 00:06:25.759
It's been around forever.
00:06:26.000 --> 00:06:29.759
Now, yes, there's pay Linux versions or distros, but Linux.
00:06:29.920 --> 00:06:32.399
You can that Linux has been around for a long time.
00:06:32.639 --> 00:06:33.439
It's free.
00:06:33.680 --> 00:06:36.079
Git, I would expect Git to be free forever.
00:06:36.240 --> 00:06:40.639
Like there's a number of things that we depend on that, yes, they've been free forever.
00:06:40.959 --> 00:06:45.120
But that doesn't mean it's something that you should ignore.
00:06:45.439 --> 00:06:52.000
It is a big red flag when something does not have a monetization strategy.
00:06:52.800 --> 00:06:57.360
At some point, the people developing it are probably going to get tired.
00:06:57.759 --> 00:06:59.839
And at that point, the enthusiasm is gone.
00:07:00.000 --> 00:07:02.319
Maybe their employer used to pay for this.
00:07:02.480 --> 00:07:06.240
I know a number of packages right now that are starting to figure out monetization now.
00:07:06.319 --> 00:07:11.519
It's kind of too late, but they're trying, because the fact that their work used to pay for it.
00:07:11.839 --> 00:07:12.959
It used to pay for their time.
00:07:13.040 --> 00:07:15.839
It used to pay for their work on the project.
00:07:16.000 --> 00:07:17.199
Now it doesn't.
00:07:17.439 --> 00:07:18.959
So what now?
00:07:19.199 --> 00:07:24.639
Like now all of a sudden there's no money coming in and there's a lot of people saying, I have problems.
00:07:24.800 --> 00:07:26.319
Please fix my problems.
00:07:26.639 --> 00:07:31.360
So having a good monetization strategy is really important.
00:07:31.519 --> 00:07:37.920
It makes me feel good when I can look at something and say, I understand how they make money.
00:07:38.160 --> 00:07:39.439
Because here's the deal.
00:07:39.600 --> 00:07:43.360
Yes, I don't like being nickel and dimed, I don't like having a subscription for everything I do.
00:07:43.519 --> 00:07:48.399
I don't like having to pay hundreds and thousands of dollars just to maintain my life.
00:07:48.720 --> 00:08:01.600
But at the same time, if an app depends on you continuing to pay, in general, they're going to do things that keep you paying.
00:08:01.839 --> 00:08:13.199
Now, yes, there's a lot of companies, there's a lot of venture capital, other, you know, uh resources that come in and say, hey, you know what, we're going to squeeze the money out of people.
00:08:13.439 --> 00:08:14.319
I get that.
00:08:14.639 --> 00:08:23.439
But when you're looking at a library and they have a way to make money, they want you to continue using their library.
00:08:23.680 --> 00:08:27.600
So they're going to do things that maintain that library, hopefully.
00:08:27.759 --> 00:08:30.480
Now they'll also probably try and lock you in, all the rest.
00:08:31.040 --> 00:08:38.399
There is a balance, but having a good monetization strategy means they're incentivized to keep going.
00:08:38.879 --> 00:09:01.440
That's pretty important to me because when they're incentivized, they are thinking less about trying to figure out how to make ends meet and more about how to keep you going, which means better systems, means more features, it means being faster, whatever it means in order to make you keep going with their library.
00:09:01.840 --> 00:09:06.159
Number two, does the creator have a track record of support?
00:09:06.720 --> 00:09:11.360
So when you're looking at who is creating it, look at their track record.
00:09:11.519 --> 00:09:13.039
Have they killed a whole bunch of products?
00:09:13.200 --> 00:09:18.799
This is why when I look at Google's products and they call it a new product, I'm like, nope, not going to depend on it.
00:09:19.039 --> 00:09:20.639
I haven't used Google's AI.
00:09:20.799 --> 00:09:21.759
And the reason why?
00:09:22.000 --> 00:09:28.480
I don't want to depend on anything Google creates, because I have been burned too many times.
00:09:28.799 --> 00:09:30.559
I just don't trust them.
00:09:30.799 --> 00:09:37.279
So even though they might have a great app or a great library or a great system, I
go, I don't trust that.
00:09:37.519 --> 00:09:41.120
Whereas other things I've used for years, I go, you know what?
00:09:41.200 --> 00:09:46.720
Yeah, I kind of trust them because they've been around forever or because I know that they have supported other things.
00:09:46.879 --> 00:09:48.879
And this is just one more thing.
00:09:49.279 --> 00:09:50.559
Look at who they are.
00:09:50.720 --> 00:09:51.840
Look at their track record.
00:09:51.919 --> 00:10:00.559
And if possible, look for things that have a track record of success, of support, of customers that have been taken care of over time.
00:10:01.200 --> 00:10:06.720
And then you can look at their products and go, okay, I'm more likely to consider that.
00:10:07.440 --> 00:10:14.240
Number three, the question you probably should ask right the bat, but do you really need this dependency?
00:10:14.480 --> 00:10:19.679
That's a question that too often people get caught up in, oh, I need this, I need this, I need this.
00:10:19.840 --> 00:10:21.919
They never think, do I need this?
00:10:22.240 --> 00:10:25.200
Or is this just a convenience thing?
00:10:25.519 --> 00:10:30.799
And there are, I'm a big proponent of actually using third-party libraries.
00:10:30.960 --> 00:10:35.039
I'm a big proponent of using tools that make your life better.
00:10:35.360 --> 00:10:43.759
For example, almost practically without fail, if I'm going to access a SQL type database, I'm bringing in Dapper.
00:10:43.919 --> 00:10:51.759
It's just almost a given at this point because it's a lightweight tool, it's been supported for a long time, it has a monetization strategy.
00:10:52.000 --> 00:10:54.720
It's a great tool that I can depend on.
00:10:54.960 --> 00:10:56.639
And it makes my life easier.
00:10:56.720 --> 00:10:59.120
And I don't have to rebuild that every time.
00:10:59.440 --> 00:11:01.519
So I'm not going to reinvent the wheel.
00:11:01.679 --> 00:11:06.000
Even though it's open source, I could probably go and grab the code for it and you know just recompile it myself.
00:11:06.159 --> 00:11:06.960
Not going to do that.
00:11:07.200 --> 00:11:07.519
Okay.
00:11:08.080 --> 00:11:10.559
So there are tools like that that I use.
00:11:10.639 --> 00:11:14.080
And I'm a big proponent of using tools that are best for different systems.
00:11:14.240 --> 00:11:15.360
I'm going to talk to Redis.
00:11:15.440 --> 00:11:20.000
I'm going to use the Stack Overflow Redis tool or Stack Exchange Redis tool.
00:11:20.799 --> 00:11:28.159
Because it's a proven tool and it's it's optimized and it's they've done all the work that I just don't want to do.
00:11:28.639 --> 00:11:34.399
And be very careful not to confuse something works with something that's good.
00:11:40.159 --> 00:11:45.039
Both of those are great examples of they're good, not just they work.
00:11:45.600 --> 00:11:53.360
Because you know, Dapper, for example, it's practically as fast as raw ADO.NET code.
00:11:53.519 --> 00:11:53.840
Okay.
00:11:54.080 --> 00:12:00.879
But yet it's it's so much more performant for me as a developer when it comes to I just get my models out the way I want.
00:12:00.960 --> 00:12:02.639
I send models in, I get models out.
00:12:02.879 --> 00:12:07.039
That's so much more efficient than dealing with data tables and all the rest.
00:12:07.279 --> 00:12:14.559
So that efficiency, though, is really important because I could probably recreate what DAPR does, but it wouldn't be as efficient.
00:12:14.799 --> 00:12:19.519
So now I have slower code, but it's more efficient for me as a developer.
00:12:19.759 --> 00:12:21.519
And I have to maintain that code too.
00:12:21.679 --> 00:12:24.080
Like, be careful you weigh these things.
00:12:24.240 --> 00:12:30.399
However, there are times where I've seen people bring on a whole new dependency because of one little thing.
00:12:30.720 --> 00:12:32.399
Don't do that if you can help it.
00:12:32.559 --> 00:12:34.240
Try and trim that down.
00:12:34.480 --> 00:12:41.519
Instead of bringing in three different dependencies from three different sources, see if you can bring in from one that supports all three things.
00:12:41.759 --> 00:12:44.320
Like try and figure out do I need this?
00:12:44.480 --> 00:12:46.080
Do I even need to create this dependency?
00:12:46.159 --> 00:12:49.279
And if I do, what's the simplest way of doing it?
00:12:49.600 --> 00:12:54.799
Dependencies are something that can really hold you back as an application, as a development team.
00:12:54.960 --> 00:12:56.720
So be very careful what you use.
00:12:56.799 --> 00:12:59.919
But at the same time, the other side is true too.
00:13:00.080 --> 00:13:03.440
It can hold you back if you're trying to rebuild everything yourself.
00:13:04.320 --> 00:13:07.360
And don't just say that AI can do it.
00:13:07.600 --> 00:13:15.360
AI can build working things, it is not build efficient things, it is not build things that are secure by default.
00:13:15.600 --> 00:13:18.080
You've got to put the work in to make them efficient.
00:13:18.240 --> 00:13:20.000
You've got to put the work in to make them secure.
00:13:20.080 --> 00:13:27.120
You got to put the work in to make it write good code that's clean and simple and easy to read and understand, easy to maintain.
00:13:27.279 --> 00:13:31.840
Otherwise, what you get is a lot of code that's harder to maintain.
00:13:32.080 --> 00:13:35.919
And you just create more and more spaghetti that at some point it's gonna come crashing down.
00:13:36.080 --> 00:13:36.879
So be careful.
00:13:37.039 --> 00:13:37.919
There's a balance.
00:13:38.080 --> 00:13:40.639
Taking on dependencies, it's always a risk.
00:13:40.879 --> 00:13:49.600
You have to weigh the risk of taking one on against the risk of not taking one on or of taking a different one.
00:13:49.840 --> 00:13:52.240
No matter what you do, there's a risk.
00:13:52.399 --> 00:13:56.639
So you have to figure out which risk is most palatable.
00:13:57.039 --> 00:14:02.240
The better you get at honestly evaluating risk, the better your app will be.
00:14:02.480 --> 00:14:04.559
No matter what you do, you're gonna take on risk.
00:14:04.639 --> 00:14:07.519
So make sure you take on the right risk.
00:14:07.759 --> 00:14:08.639
Thanks for listening.
00:14:08.720 --> 00:14:10.799
And as always, I am Tim Corey.