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.
You're working on a secret team solving coded transmissions.
Your team is scrambling to decipher a recent message, worried it's a plot to break into a major European National Cake Vault. The message has been mostly deciphered, but all the words are backward! Your colleagues have handed off the last step to you.
Write a method reverseWords that takes a message as an array of characters and reverses the order of the words in place.
Why an array of characters instead of a string?
The goal of this question is to practice manipulating strings in place. Since we're modifying the message, we need a mutable type like an array, instead of Java's immutable strings.
When writing your method, assume the message contains only letters and spaces, and all words are separated by one space.
We can do this in space. Remember, in place.
We can do this in time.
If you're swapping individual words one at a time, consider what happens when the words are different lengths. Isn't each swap time in the worst case?
Let’s start with a simpler problem. What if we wanted to reverse all the characters in the message?
Well, we could swap the first character with the last character, then the second character with the second to last character, and so on, moving towards the middle. Can you implement this in code?
Ok, looks good. Does this help us?
Can we use the same concept but apply it to words instead of characters?
Probably. We'll have to figure out a couple things:
We could attack either of those first, but I'm already seeing a potential problem in terms of runtime. Can you guess what it is?
What happens when you swap two words that aren't the same length?
Supposing we already knew the start and end indices of 'the' and 'landed', how long would it take to swap them?
time, where n is the total length of the message!
Why? Notice that in addition to moving 'the' to the back and moving 'landed' to the front, we have to "scoot over" everything in between, since 'landed' is longer than 'the'.
So what'll be the total time cost with this approach? Assume we'll be able to learn the start and end indices of all of our words in just one pass ( time).
total time. Why? In the worst case we have almost as many words as we have characters, and we're always swapping words of different lengths. For example:
We take time to swap the first and last words (we have to move all n characters):
Then for the second swap:
We have to move all n characters except the first and last words, and a couple spaces. So we move n-5 characters in total.
For the third swap, we have another 5 characters we don't have to move. So we move n-10 in total. We'll end up with a series like this:
This is a subsection of the common triangular series. We're just skipping 4 terms between each term!
So we have the sum of "every fifth number" from that triangular series. That means our sum will be about a fifth the sum of the original series! But in big O notation dividing by 5 is a constant, so we can throw it out. The original triangular series is , and so is our series with every fifth element!
Okay, so time. That's pretty bad. It's possible that's the best we can do...but maybe we can do better?
Let's try manipulating a sample input by hand.
And remember what we did for our character-level reversal...
Look what happens when we do a character-level reversal:
What if we put it up against the desired output:
The character reversal reverses the words! It's a great first step. From there, we just have to "unscramble" each word.
More precisely, we just have to re-reverse each word!
We'll write a helper method reverseCharacters that reverses all the characters between a leftIndex and rightIndex. We use it to:
time and space!
Hmm, the team used your method to finish deciphering the message. There definitely seems to be a heist brewing, but no specifics on where. Any ideas?
How would you handle punctuation?
The naive solution of reversing the words one at a time had a worst-case runtime. That's because swapping words with different lengths required "scooting over" all the other characters to make room.
To get around this "scooting over" issue, we reversed all the characters in the message first. This put all the words in the correct spots, but with the characters in each word backward. So to get the final answer, we reversed the characters in each word. This all takes two passes through the message, so time total.
This might seem like a blind insight, but we derived it by using a clear strategy:
Solve a simpler version of the problem (in this case, reversing the characters instead of the words), and see if that gets us closer to a solution for the original problem.
We talk about this strategy in the "get unstuck" section of our coding interview tips.
Powered by qualified.io