# Best Time to Buy and Sell Stock II

Difficulty: Easy

Problem statement:

Say you have an array for which the ith element is the price of a given stock on day i.

Design an algorithm to find the maximum profit. You may complete as many transactions as you like (i.e., buy one and sell one share of the stock multiple times).

Note: You may not engage in multiple transactions at the same time (i.e., you must sell the stock before you buy again).

Example 1:

Input: [7,1,5,3,6,4] Output: 7 Explanation: Buy on day 2 (price = 1) and sell on day 3 (price = 5), profit = 5-1 = 4. Then buy on day 4 (price = 3) and sell on day 5 (price = 6), profit = 6-3 = 3. Example 2:

Input: [1,2,3,4,5] Output: 4 Explanation: Buy on day 1 (price = 1) and sell on day 5 (price = 5), profit = 5-1 = 4. Note that you cannot buy on day 1, buy on day 2 and sell them later, as you are engaging multiple transactions at the same time. You must sell before buying again. Example 3:

Input: [7,6,4,3,1] Output: 0 Explanation: In this case, no transaction is done, i.e. max profit = 0.

Welp, here’s where shit gets real folks.

After thinking about this problem for at least an hour, I had just about nothing. I can think of no easy algorithm that could do this, so I did what a dumbfounded programmer does best - just start writing random code!

The first horrifying idea I came up with was this one:

You can kind of see where I was going with this, but it definitely didn’t work. It didn’t even pass the first test case. I knew I was doing something horribly wrong, so I decided to start completely from scratch and come up with something different. After a bit of head-braining, I came up with this:

Like my previous solution this also fucking sucked.

These weren’t anywhere near solving the problem. I looked over at Mikayla and her IDE was filled with at least a hundred lines of Python code. “Are you getting anywhere?” “No” she replied.

At this point, I had to face facts. This was an algorithmic problem. No matter how much code we crank out, unless we understand how to best approach this problem, we’re just wasting our time.

After mulling it over a bit longer, I eventually decided to cave - I was going to look at the solution. I had to know what it was, and my worst fear would be that it was just painfully simple. I clicked the solution tab, but nothing could prepare me for what I saw next…

# Un-fucking-believable

We had spent two hours trying insanely idiotic algorithms and bashing our heads against the wall to be slapped in the face by a simple O(n) loop that just checks the next element. You’ve got to be fucking kidding me. Nope, not kidding you.

We ran to the whiteboard to check some test cases and sure as shit - checks out.

Realizing that we’re fucking idiots, I decided to take this as a learning opportunity - because really that’s what this contest should be all about anyway. We never claimed to be the world’s best programmers who knew the best algorithm to solve any problem (I mean I also didn’t think we’d get stuck on day 5, but I digress). So the take away is that we learned a new algorithm to solve certain types of problems. I know I, for one, can say that I won’t forget this one.