The key to solving problems.

Key Takeaways

In programming, there are hundreds of ways to solve the [music] same problems. Some are objectively much better than others. So, when you're solving these types of [music] problems, you need to put that at the forefront of your brain. You need to evaluate the different ways you could go about solving this problem, analyze them, and talk about why you made the decision you did. Now, the common way to make sure you don't get this wrong is to always present the [music] brute force solution first before you move into the more optimal solution. So, for example, let's say I ask you to sort an array. You can [music] brute force this sort by using something like bubble sort or insertion sort, right? Where you're doing an n squared time complexity algorithm. This is not the most efficient way to solve it, but it is one way and it's a solution that even though you're not going to write, you need to present to the interviewer. So you would say, hey, this is the first solution that comes to mind. It's a brute force approach where I'm going to have two for loops. I'm going to loop through and I'm going to compare every element to every other element. I know that's [music] going to solve it, but that's going to be an n squ time complexity algorithm. So, I'm going to hold off on that for right now and see if I can come up with a more optimal solution that uses less