But it doesn't have to end here! Sign up for the 7-day coding interview crash course and you'll get a free Interview Cake problem every week.
I want to learn some big words so people think I'm smart.
I opened up a dictionary to a page in the middle and started flipping through, looking for words I didn't know. I put each word I didn't know at increasing indices in a huge array I created in memory. When I reached the end of the dictionary, I started from the beginning and did the same thing until I reached the page I started at.
Now I have an array of words that are mostly alphabetical, except they start somewhere in the middle of the alphabet, reach the end, and then start from the beginning of the alphabet. In other words, this is an alphabetically ordered array that has been "rotated." For example:
Write a method for finding the index of the "rotation point," which is where I started working from the beginning of the dictionary. This array is huge (there are lots of words I don't know) so we want to be efficient here.
We can get time.
The array is mostly ordered. We should exploit that fact.
What's a common algorithm that takes advantage of the fact that an array is sorted to find an item efficiently?
Binary search! We can write an adapted version of binary search for this.
In each iteration of our binary search, how do we know if the rotation point is to our left or to our right?
Try drawing out an example array!
If our "current guess" is the middle item, which is 'c' in this case, is the rotation point to the left or to the right? How do we know?
Notice that every item to the right of our rotation point is always alphabetically before the first item in the array.
So the rotation point is to our left if the current item is less than the first item. Else it's to our right.
This is a modified version of binary search. At each iteration, we go right if the item we're looking at is greater than the first item and we go left if the item we're looking at is less than the first item.
We keep track of the lower and upper bounds on the rotation point, calling them floorIndex and ceilingIndex (initially we called them "floor" and "ceiling," but because we didn't imply the type in the name we got confused and created bugs). When floorIndex and ceilingIndex are directly next to each other, we know the floor is the last item we added before starting from the beginning of the dictionary, and the ceiling is the first item we added after.
Each time we go through the while loop, we cut our range of indices in half, just like binary search. So we have loop iterations.
In each loop iteration, we do some arithmetic and a string comparison. The arithmetic is constant time, but the string comparison requires looking at characters in both words—every character in the worst case. Here, we'll assume our word lengths are bounded by some constant so we'll say the string comparison takes constant time.
The longest word in English is pneumonoultramicroscopicsilicovolcanoconiosis, a medical term. It's 45 letters long.
Putting everything together, we do iterations, and each iteration is time. So our time complexity is .
Some languages—like German, Russian, and Dutch—can have arbitrarily long words, so we might want to factor the length of the words into our runtime. We could say the length of the words is \ell, each string comparison takes time, and the whole algorithm takes time.
We use space to store the first word and the floor and ceiling indices.
This method assumes that the array is rotated. If it isn't, what index will it return? How can we fix our method to return 0 for an unrotated array?
The answer was a modified version of binary search.
This is a great example of the difference between "knowing" something and knowing something. You might have seen binary search before, but that doesn't help you much unless you've learned the lessons of binary search.
Binary search teaches us that when an array is sorted or mostly sorted:
So whenever you know an array is sorted or almost sorted, think about these lessons from binary search and see if they apply.
Powered by qualified.io