327. How Do I Evaluate a Third Party Tool or Library in the Age of AI?

It seems like everyone has vibe coding It seems like everyone has vibe coding apps and tools these days. With code apps and tools these days. With code apps and tools these days. With code being so easy to write with AI, it's being so easy to write with AI, it's being so easy to write with AI, it's easier than ever to turn an idea into a easier than ever to turn an idea into a easier than ever to turn an idea into a product. Unfortunately, building that product. Unfortunately, building that product. Unfortunately, building that product was almost never the hardest product was almost never the hardest product was almost never the hardest part. Building a secure, performant part. Building a secure, performant part. Building a secure, performant product is much harder, and then product is much harder, and then product is much harder, and then supporting it long-term is even harder supporting it long-term is even harder supporting it long-term is even harder still. These are the areas where a lot still. These are the areas where a lot still. These are the areas where a lot of apps and libraries are already of apps and libraries are already of apps and libraries are already failing. So, how do you know what tools failing. So, how do you know what tools failing. So, how do you know what tools and libraries to depend on when you're and libraries to depend on when you're and libraries to depend on when you're building your own app? Should you build building your own app? Should you build building your own app? Should you build everything yourself, or should you only everything yourself, or should you only everything yourself, or should you only depend on tools from reputable sources? depend on tools from reputable sources? depend on tools from reputable sources? Let's talk about it in today's episode Let's talk about it in today's episode Let's talk about it in today's episode of Dev Questions. Software development is more than just Software development is more than just writing code. So, let's talk about the writing code. So, let's talk about the writing code. So, let's talk about the rest of it. Specifically, let's talk rest of it. Specifically, let's talk rest of it. Specifically, let's talk about how to evaluate thirdparty tools about how to evaluate thirdparty tools about how to evaluate thirdparty tools and libraries in the age of AI. Now, I and libraries in the age of AI. Now, I and libraries in the age of AI. Now, I don't know about you, but I get nervous don't know about you, but I get nervous don't know about you, but I get nervous anytime I see an app that was clearly anytime I see an app that was clearly anytime I see an app that was clearly vibe coded. I have seen too many vibe coded. I have seen too many vibe coded. I have seen too many instances of apps that seem to work only instances of apps that seem to work only instances of apps that seem to work only to discover later they leaked all their to discover later they leaked all their to discover later they leaked all their sensitive data or that they'd failed the sensitive data or that they'd failed the sensitive data or that they'd failed the worst moment or just abandoned. If you worst moment or just abandoned. If you worst moment or just abandoned. If you are building an app, you probably are are building an app, you probably are are building an app, you probably are going to depend on thirdparty resources going to depend on thirdparty resources going to depend on thirdparty resources like emailers, PDF tools, data access like emailers, PDF tools, data access like emailers, PDF tools, data access libraries, and more. So, how do you know libraries, and more. So, how do you know libraries, and more. So, how do you know what's a good app to depend on and

what's a good app to depend on and what's a good app to depend on and what's not a good app to depend on? So, what's not a good app to depend on? So, what's not a good app to depend on? So, let's talk about what not to look at or let's talk about what not to look at or let's talk about what not to look at or not to depend on when validating a a not to depend on when validating a a not to depend on when validating a a third party library app. Number one, third party library app. Number one, third party library app. Number one, open source. Just because something is open source. Just because something is open source. Just because something is open source doesn't make it good. The open source doesn't make it good. The open source doesn't make it good. The the kind of the misconception is, well, the kind of the misconception is, well, the kind of the misconception is, well, if it was ever a problem, I can just if it was ever a problem, I can just if it was ever a problem, I can just fork it and build my own. Really? fork it and build my own. Really? fork it and build my own. Really? Really? Have you ever tried that? Have Really? Have you ever tried that? Have Really? Have you ever tried that? Have you ever actually done the the work of you ever actually done the the work of you ever actually done the the work of saying, hey, let's test out what would saying, hey, let's test out what would saying, hey, let's test out what would happen if this library suddenly stopped happen if this library suddenly stopped happen if this library suddenly stopped supporting the latest version of.NET. supporting the latest version of.NET. supporting the latest version of.NET. Could we upgrade to the latest version Could we upgrade to the latest version Could we upgrade to the latest version ofnet? Have you tried? Because more than ofnet? Have you tried? Because more than ofnet? Have you tried? Because more than likely it's not nearly as easy as you likely it's not nearly as easy as you likely it's not nearly as easy as you think it is. And even if you say, "Well, think it is. And even if you say, "Well, think it is. And even if you say, "Well, we're gonna use AI and just have AI do we're gonna use AI and just have AI do we're gonna use AI and just have AI do it." It that's even harder because now it." It that's even harder because now it." It that's even harder because now you have an app that AI is not going to you have an app that AI is not going to you have an app that AI is not going to fully read through that third party fully read through that third party fully read through that third party system. And so it's going to make some system. And so it's going to make some system. And so it's going to make some guesses and it's going to create more guesses and it's going to create more guesses and it's going to create more and more spaghetti code until you re it and more spaghetti code until you re it and more spaghetti code until you re it in. And you won't because you don't know in. And you won't because you don't know in. And you won't because you don't know the code itself. And so it just creates the code itself. And so it just creates the code itself. And so it just creates a bigger ball of mess to deal with. So a bigger ball of mess to deal with. So a bigger ball of mess to deal with. So just because something is open- source just because something is open- source just because something is open- source doesn't mean it's a good system to doesn't mean it's a good system to doesn't mean it's a good system to depend on. Now being open source can be depend on. Now being open source can be depend on. Now being open source can be a valuable thing and it can be a point a valuable thing and it can be a point a valuable thing and it can be a point in its favor but don't look at something in its favor but don't look at something in its favor but don't look at something and say oh what's open source that must and say oh what's open source that must and say oh what's open source that must be good. So don't look at open source as be good. So don't look at open source as be good. So don't look at open source as the qualifier for something to be good.

the qualifier for something to be good. the qualifier for something to be good. There's other things to look at. Number There's other things to look at. Number There's other things to look at. Number two don't look at it just because it's a two don't look at it just because it's a two don't look at it just because it's a product from a big company. There is a product from a big company. There is a product from a big company. There is a whole Twitter account dedicated to apps whole Twitter account dedicated to apps whole Twitter account dedicated to apps killed by Google because Google is killed by Google because Google is killed by Google because Google is notorious. In fact, I've told my team, I notorious. In fact, I've told my team, I notorious. In fact, I've told my team, I said, "We will not rely on products from said, "We will not rely on products from said, "We will not rely on products from Google because they're just notorious Google because they're just notorious Google because they're just notorious for shutting down good working products. for shutting down good working products. for shutting down good working products. So, not going to trust it." even So, not going to trust it." even So, not going to trust it." even Microsoft and Microsoft is better, but Microsoft and Microsoft is better, but Microsoft and Microsoft is better, but they still have a number of dead they still have a number of dead they still have a number of dead products in their wake. And you might products in their wake. And you might products in their wake. And you might say, well, no, there's they're as bad as say, well, no, there's they're as bad as say, well, no, there's they're as bad as everybody else. To be fair, Windforms, everybody else. To be fair, Windforms, everybody else. To be fair, Windforms, WindForms has been supported since Net 1 WindForms has been supported since Net 1 WindForms has been supported since Net 1 back in 2001 2002 time frame. That's 24 back in 2001 2002 time frame. That's 24 back in 2001 2002 time frame. That's 24 years we've had.net Windforms and that's years we've had.net Windforms and that's years we've had.net Windforms and that's been supported that entire time. So they been supported that entire time. So they been supported that entire time. So they do have a long track record of do have a long track record of do have a long track record of supporting certain things, not supporting certain things, not supporting certain things, not everything. Web forms, it needed to die, everything. Web forms, it needed to die, everything. Web forms, it needed to die, but it did die. Okay. And then there is but it did die. Okay. And then there is but it did die. Okay. And then there is the WCF and there's, you know, Silver the WCF and there's, you know, Silver the WCF and there's, you know, Silver Light always gets thrown in there, but Light always gets thrown in there, but Light always gets thrown in there, but that's not really their problem. But at that's not really their problem. But at that's not really their problem. But at the same time, yeah, it's another app the same time, yeah, it's another app the same time, yeah, it's another app that died because a different big that died because a different big that died because a different big company killed it. So just because it company killed it. So just because it company killed it. So just because it comes from a big company doesn't mean comes from a big company doesn't mean comes from a big company doesn't mean it's going to be around forever. It it's going to be around forever. It it's going to be around forever. It might last a year or two or it might might last a year or two or it might might last a year or two or it might last for 20 years. You just don't know.

last for 20 years. You just don't know. last for 20 years. You just don't know. And saying, "Well, they have mountains And saying, "Well, they have mountains And saying, "Well, they have mountains of money to support it." Yeah. Do they of money to support it." Yeah. Do they of money to support it." Yeah. Do they though? Because every time I turn though? Because every time I turn though? Because every time I turn around, it seems like these big tech around, it seems like these big tech around, it seems like these big tech companies are laying people off and companies are laying people off and companies are laying people off and cutting divisions. So, while it may seem cutting divisions. So, while it may seem cutting divisions. So, while it may seem like they have lots of money, typically like they have lots of money, typically like they have lots of money, typically that lots of money goes towards that lots of money goes towards that lots of money goes towards shareholders, not towards your shareholders, not towards your shareholders, not towards your particular library that you want particular library that you want particular library that you want supported. supported. supported. So, just be careful. Saying, "Well, it's So, just be careful. Saying, "Well, it's So, just be careful. Saying, "Well, it's a big company," doesn't mean anything. a big company," doesn't mean anything. a big company," doesn't mean anything. Number three, just because it has a lot Number three, just because it has a lot Number three, just because it has a lot of stars on GitHub, doesn't mean pretty of stars on GitHub, doesn't mean pretty of stars on GitHub, doesn't mean pretty much anything. Stars don't pay the much anything. Stars don't pay the much anything. Stars don't pay the bills. They don't indicate quality. They bills. They don't indicate quality. They bills. They don't indicate quality. They don't in any way give you an indication don't in any way give you an indication don't in any way give you an indication that this is a a good library except for that this is a a good library except for that this is a a good library except for the fact that a number of people have the fact that a number of people have the fact that a number of people have said, "Yeah, I want to watch this," or, said, "Yeah, I want to watch this," or, said, "Yeah, I want to watch this," or, "Yeah, I think this is an interesting "Yeah, I think this is an interesting "Yeah, I think this is an interesting project." Now, when a lot of people say project." Now, when a lot of people say project." Now, when a lot of people say that, it could be good, but I see a that, it could be good, but I see a that, it could be good, but I see a number of projects that are bad number of projects that are bad number of projects that are bad projects, but they've got great projects, but they've got great projects, but they've got great marketing and all of a sudden they have marketing and all of a sudden they have marketing and all of a sudden they have lots of stars on GitHub. So, just be lots of stars on GitHub. So, just be lots of stars on GitHub. So, just be careful. There is, it is a data point, careful. There is, it is a data point, careful. There is, it is a data point, but it's not a deciding factor. Just but it's not a deciding factor. Just but it's not a deciding factor. Just like open source, it's a data point. It like open source, it's a data point. It like open source, it's a data point. It should not be a deciding factor. So, should not be a deciding factor. So, should not be a deciding factor. So, what should you evaluate when it comes what should you evaluate when it comes what should you evaluate when it comes to a third-party library or tool? Well, to a third-party library or tool? Well, to a third-party library or tool? Well, number one, does it have a monetization number one, does it have a monetization number one, does it have a monetization strategy?

strategy? strategy? This is something that people just don't This is something that people just don't This is something that people just don't understand. understand. understand. If a tool, if a library, if something If a tool, if a library, if something If a tool, if a library, if something you depend on does not have a way to you depend on does not have a way to you depend on does not have a way to make money, it does not matter how make money, it does not matter how make money, it does not matter how enthusiastic the team is, enthusiastic the team is, enthusiastic the team is, it is in danger. I'm not saying it's it is in danger. I'm not saying it's it is in danger. I'm not saying it's going to go away. It may last for life. going to go away. It may last for life. going to go away. It may last for life. You don't have to pay for Linux. It's You don't have to pay for Linux. It's You don't have to pay for Linux. It's been around forever. Now, yes, there's been around forever. Now, yes, there's been around forever. Now, yes, there's paid Linux versions or dros, but Linux, paid Linux versions or dros, but Linux, paid Linux versions or dros, but Linux, you can that Linux been around for a you can that Linux been around for a you can that Linux been around for a long time. It's free. Git, I would long time. It's free. Git, I would long time. It's free. Git, I would expect Git to be free forever. Like, expect Git to be free forever. Like, expect Git to be free forever. Like, there's a number of things that we there's a number of things that we there's a number of things that we depend on that yes, they've been free depend on that yes, they've been free depend on that yes, they've been free forever, but that doesn't mean it's forever, but that doesn't mean it's forever, but that doesn't mean it's something that you should ignore. It is something that you should ignore. It is something that you should ignore. It is a big red flag when something does not a big red flag when something does not a big red flag when something does not have a monetization strategy. have a monetization strategy. have a monetization strategy. At some point, the people developing it At some point, the people developing it At some point, the people developing it are probably going to get tired and at are probably going to get tired and at are probably going to get tired and at that point the enthusiasm is gone. Maybe that point the enthusiasm is gone. Maybe that point the enthusiasm is gone. Maybe their employer used to pay for this. I their employer used to pay for this. I their employer used to pay for this. I know a number of packages right now that know a number of packages right now that know a number of packages right now that are starting to figure out monetization.

are starting to figure out monetization. are starting to figure out monetization. Now it's kind of too late, but they're Now it's kind of too late, but they're Now it's kind of too late, but they're trying because of the fact that their trying because of the fact that their trying because of the fact that their their work used to pay for it. It used their work used to pay for it. It used their work used to pay for it. It used to pay for their time. it used to pay to pay for their time. it used to pay to pay for their time. it used to pay for their their their work on the for their their their work on the for their their their work on the project. Now it doesn't. So what now? project. Now it doesn't. So what now? project. Now it doesn't. So what now? Like now all of a sudden there's no Like now all of a sudden there's no Like now all of a sudden there's no money coming in and there's a lot of money coming in and there's a lot of money coming in and there's a lot of people saying I have problems. Please people saying I have problems. Please people saying I have problems. Please fix my problems. So having a good fix my problems. So having a good fix my problems. So having a good monetization strategy is really monetization strategy is really monetization strategy is really important. It makes me feel good when I important. It makes me feel good when I important. It makes me feel good when I can look at something and say I can look at something and say I can look at something and say I understand how they make money. Because understand how they make money. Because understand how they make money. Because here's the deal. Yes, I don't like being here's the deal. Yes, I don't like being here's the deal. Yes, I don't like being nickel and dimed. I don't like having a nickel and dimed. I don't like having a nickel and dimed. I don't like having a subscription for everything I do. I subscription for everything I do. I subscription for everything I do. I don't like having to pay hundreds and don't like having to pay hundreds and don't like having to pay hundreds and thousands of dollars just to maintain my thousands of dollars just to maintain my thousands of dollars just to maintain my life. But at the same time, if an app life. But at the same time, if an app life. But at the same time, if an app depends on you continuing to pay depends on you continuing to pay depends on you continuing to pay in general, they're going to do things in general, they're going to do things in general, they're going to do things that keep you paying. Now, yes, there's that keep you paying. Now, yes, there's that keep you paying. Now, yes, there's a lot of companies, there's a lot of, a lot of companies, there's a lot of, a lot of companies, there's a lot of, you know, venture capital, other, you you know, venture capital, other, you you know, venture capital, other, you know, uh, resources that come in and know, uh, resources that come in and know, uh, resources that come in and say, "Hey, you know what? we're going to say, "Hey, you know what? we're going to say, "Hey, you know what? we're going to squeeze the money out of people. I get squeeze the money out of people. I get squeeze the money out of people. I get that. But when you're looking at a that. But when you're looking at a that. But when you're looking at a library and they have a way to make library and they have a way to make library and they have a way to make money, they want you to continue using money, they want you to continue using money, they want you to continue using their library. So, they're going to do their library. So, they're going to do their library. So, they're going to do things that maintain that library things that maintain that library things that maintain that library hopefully. Now, they'll also probably hopefully. Now, they'll also probably hopefully. Now, they'll also probably try and lock you in all the rest. There try and lock you in all the rest. There try and lock you in all the rest. There is a balance, but having a good is a balance, but having a good is a balance, but having a good modernization strategy means they're modernization strategy means they're modernization strategy means they're incentivized to keep going. That's

incentivized to keep going. That's incentivized to keep going. That's pretty important to me because when pretty important to me because when pretty important to me because when they're incentivized, they're incentivized, they're incentivized, they are thinking less about they are thinking less about they are thinking less about trying to figure out how to make ends trying to figure out how to make ends trying to figure out how to make ends meet and more about how to keep you meet and more about how to keep you meet and more about how to keep you going, which means better systems, means going, which means better systems, means going, which means better systems, means more features. It means, you know, being more features. It means, you know, being more features. It means, you know, being faster, whatever it means in order to faster, whatever it means in order to faster, whatever it means in order to make you keep going with their library. make you keep going with their library. make you keep going with their library. Number two, does the creator have a Number two, does the creator have a Number two, does the creator have a track record of support? So when you're track record of support? So when you're track record of support? So when you're looking at who is creating it, look at looking at who is creating it, look at looking at who is creating it, look at their track record. Have they killed a their track record. Have they killed a their track record. Have they killed a whole bunch of products? This is why whole bunch of products? This is why whole bunch of products? This is why when I look at Google's products, they when I look at Google's products, they when I look at Google's products, they call it a new product. I'm like, nope, call it a new product. I'm like, nope, call it a new product. I'm like, nope, not going to depend on it. I haven't not going to depend on it. I haven't not going to depend on it. I haven't used Google's AI. And the reason why I used Google's AI. And the reason why I used Google's AI. And the reason why I don't want to depend on anything Google don't want to depend on anything Google don't want to depend on anything Google creates because I have been burned too creates because I have been burned too creates because I have been burned too many times. I just don't trust them. So many times. I just don't trust them. So many times. I just don't trust them. So even though they might have a great app even though they might have a great app even though they might have a great app or a great library or a great system, I or a great library or a great system, I or a great library or a great system, I go, I don't trust that. Whereas other go, I don't trust that. Whereas other go, I don't trust that. Whereas other things I've used for years, I go, you things I've used for years, I go, you things I've used for years, I go, you know what? Yeah, I kind of trust them know what? Yeah, I kind of trust them know what? Yeah, I kind of trust them because they've been around forever or because they've been around forever or because they've been around forever or because I know that they have supported because I know that they have supported because I know that they have supported other things. And this is just one more other things. And this is just one more other things. And this is just one more thing. Look at who they are. Look at thing. Look at who they are. Look at thing. Look at who they are. Look at their track record. And if possible, their track record. And if possible, their track record. And if possible, look for things that have a track record look for things that have a track record look for things that have a track record of success, of support, of customers of success, of support, of customers of success, of support, of customers that have been taken care of over time.

that have been taken care of over time. that have been taken care of over time. And then you can look at their products And then you can look at their products And then you can look at their products and go, "Okay, I'm I'm more likely to and go, "Okay, I'm I'm more likely to and go, "Okay, I'm I'm more likely to consider that." consider that." consider that." Number three, Number three, Number three, the question you probably should have the question you probably should have the question you probably should have asked right off the bat, but do you asked right off the bat, but do you asked right off the bat, but do you really need this dependency? That's a really need this dependency? That's a really need this dependency? That's a question that that too often people get question that that too often people get question that that too often people get caught up in. Oh, I need this. I need caught up in. Oh, I need this. I need caught up in. Oh, I need this. I need this. I need this. They never think, do this. I need this. They never think, do this. I need this. They never think, do I need this or is this just a I need this or is this just a I need this or is this just a convenience thing? And there are I'm a convenience thing? And there are I'm a convenience thing? And there are I'm a big proponent of actually using big proponent of actually using big proponent of actually using thirdparty libraries. I'm a big thirdparty libraries. I'm a big thirdparty libraries. I'm a big proponent of using tools that make your proponent of using tools that make your proponent of using tools that make your life better. For example, almost life better. For example, almost life better. For example, almost practically without fail, if I'm going practically without fail, if I'm going practically without fail, if I'm going to access a SQL type database, I'm to access a SQL type database, I'm to access a SQL type database, I'm bringing in Dapper. It's just almost a bringing in Dapper. It's just almost a bringing in Dapper. It's just almost a given at this point because it's a given at this point because it's a given at this point because it's a lightweight tool. It's been supported lightweight tool. It's been supported lightweight tool. It's been supported for a long time. It has a monetization for a long time. It has a monetization for a long time. It has a monetization strategy. It's a great tool I can depend strategy. It's a great tool I can depend strategy. It's a great tool I can depend on and it makes my life easier. I don't on and it makes my life easier. I don't on and it makes my life easier. I don't have to rebuild that every time. So, I'm have to rebuild that every time. So, I'm have to rebuild that every time. So, I'm not going to reinvent the wheel. Even not going to reinvent the wheel. Even not going to reinvent the wheel. Even though it's open source, I could though it's open source, I could though it's open source, I could probably go and grab the code for it probably go and grab the code for it probably go and grab the code for it and, you know, just recompile it myself.

and, you know, just recompile it myself. and, you know, just recompile it myself. Not going to do that. Okay. So, there Not going to do that. Okay. So, there Not going to do that. Okay. So, there are tools like that that I use. I'm a are tools like that that I use. I'm a are tools like that that I use. I'm a big proponent of using tools that are big proponent of using tools that are big proponent of using tools that are best for different systems. I'm going to best for different systems. I'm going to best for different systems. I'm going to talk to Reddus. I'm gonna use the Stack talk to Reddus. I'm gonna use the Stack talk to Reddus. I'm gonna use the Stack Overflow Reddus tool or Stack Exchange Overflow Reddus tool or Stack Exchange Overflow Reddus tool or Stack Exchange Reddus tool um because it's a proven Reddus tool um because it's a proven Reddus tool um because it's a proven tool and it's it's optimized and it's tool and it's it's optimized and it's tool and it's it's optimized and it's they've done all the work that I just they've done all the work that I just they've done all the work that I just don't want to do. And be very careful don't want to do. And be very careful don't want to do. And be very careful not to confuse something works with not to confuse something works with not to confuse something works with something is good. the this, you know, something is good. the this, you know, something is good. the this, you know, either the the Dapper tool or the the either the the Dapper tool or the the either the the Dapper tool or the the Stack Exchange RAS tool. Both of those Stack Exchange RAS tool. Both of those Stack Exchange RAS tool. Both of those are great examples of they're good, not are great examples of they're good, not are great examples of they're good, not just they work because, you know, Dapper just they work because, you know, Dapper just they work because, you know, Dapper for example, it's practically as fast as for example, it's practically as fast as for example, it's practically as fast as raw ADO.NET code, okay? But yet it's raw ADO.NET code, okay? But yet it's raw ADO.NET code, okay? But yet it's it's so much more performant for me as a it's so much more performant for me as a it's so much more performant for me as a developer when it comes to I just get my developer when it comes to I just get my developer when it comes to I just get my models out the way I want. I send models models out the way I want. I send models models out the way I want. I send models in, I get models out. That's so much in, I get models out. That's so much in, I get models out. That's so much more efficient than dealing with data more efficient than dealing with data more efficient than dealing with data tables and and all the rest. So that tables and and all the rest. So that tables and and all the rest. So that efficiency though is really important efficiency though is really important efficiency though is really important because I could probably recreate what because I could probably recreate what because I could probably recreate what Dapper does but it wouldn't be as Dapper does but it wouldn't be as Dapper does but it wouldn't be as efficient. So now I have slower code but efficient. So now I have slower code but efficient. So now I have slower code but it's more efficient for me as a it's more efficient for me as a it's more efficient for me as a developer and I have to maintain that developer and I have to maintain that developer and I have to maintain that code too. Like be careful you weigh code too. Like be careful you weigh code too. Like be careful you weigh these things. However, there are times these things. However, there are times these things. However, there are times where I've seen people bring on a whole where I've seen people bring on a whole where I've seen people bring on a whole new dependency because of one little new dependency because of one little new dependency because of one little thing. Don't do that if you can help it.

thing. Don't do that if you can help it. thing. Don't do that if you can help it. Try and trim that down. Instead of Try and trim that down. Instead of Try and trim that down. Instead of bringing in three different dependencies bringing in three different dependencies bringing in three different dependencies from three different sources, see if you from three different sources, see if you from three different sources, see if you can bring it in from one that supports can bring it in from one that supports can bring it in from one that supports all three things. Like try and figure all three things. Like try and figure all three things. Like try and figure out do I need this? Do I even need to out do I need this? Do I even need to out do I need this? Do I even need to create this dependency? And if I do, create this dependency? And if I do, create this dependency? And if I do, what's the simplest way of doing it? what's the simplest way of doing it? what's the simplest way of doing it? Dependencies are something can really Dependencies are something can really Dependencies are something can really hold you back as an application, as a hold you back as an application, as a hold you back as an application, as a development team. So be very careful development team. So be very careful development team. So be very careful what you use, but at the same time, the what you use, but at the same time, the what you use, but at the same time, the other side is true, too. It can hold you other side is true, too. It can hold you other side is true, too. It can hold you back if you're trying to rebuild back if you're trying to rebuild back if you're trying to rebuild everything yourself. everything yourself. everything yourself. And don't just say that AI can do it. AI And don't just say that AI can do it. AI And don't just say that AI can do it. AI can build working things. It does not can build working things. It does not can build working things. It does not build efficiency by default. You've got to put the work by default. You've got to put the work in to make them efficient. You got to in to make them efficient. You got to in to make them efficient. You got to put the work in to make them secure. You put the work in to make them secure. You put the work in to make them secure. You got to put the work in to make it write got to put the work in to make it write got to put the work in to make it write good code that's clean and simple and good code that's clean and simple and good code that's clean and simple and easy to read and understand, easy to easy to read and understand, easy to easy to read and understand, easy to maintain. maintain. maintain. >> [snorts] >> [snorts] >> [snorts] >> Otherwise, what you get is a lot of code >> Otherwise, what you get is a lot of code >> Otherwise, what you get is a lot of code that's harder to maintain and you just that's harder to maintain and you just that's harder to maintain and you just create more and more spaghetti that at create more and more spaghetti that at create more and more spaghetti that at some point is going to come crashing some point is going to come crashing some point is going to come crashing down. So, be careful. There's a balance.

down. So, be careful. There's a balance. down. So, be careful. There's a balance. Taking on dependencies, it's always a Taking on dependencies, it's always a Taking on dependencies, it's always a risk. You have to weigh the risk of risk. You have to weigh the risk of risk. You have to weigh the risk of taking one on against the risk of not taking one on against the risk of not taking one on against the risk of not taking one on or of taking a different taking one on or of taking a different taking one on or of taking a different one. No matter what you do, there's a one. No matter what you do, there's a one. No matter what you do, there's a risk. So, you have to figure out which risk. So, you have to figure out which risk. So, you have to figure out which risk is most palatable. risk is most palatable. risk is most palatable. The better you get at honestly The better you get at honestly The better you get at honestly evaluating risk, the better your app evaluating risk, the better your app evaluating risk, the better your app will be. No matter what you do, you're will be. No matter what you do, you're will be. No matter what you do, you're going to take on risk. So, make sure you going to take on risk. So, make sure you going to take on risk. So, make sure you take on the right risk. Thanks for take on the right risk. Thanks for take on the right risk. Thanks for listening and as always, I am Tim Corey. listening and as always, I am Tim Corey. listening and as always, I am Tim Corey. [music]