3Sum

Problem Highlights

• 🔗 Leetcode Link: 3Sum
• 💡 Difficulty: Medium
• ⏰ Time to complete: 15 mins
• 🛠️ Topics: Array, Two Pointer
• 🗒️ Similar Questions: Number of Arithmetic Triplets

1: U-nderstand

Understand what the interviewer is asking for by using test cases and questions about the problem.

• Established a set (2-3) of test cases to verify their own solution later.
• Established a set (1-2) of edge cases to verify their solution handles complexities.
• Have fully understood the problem and have no clarifying questions.
• Have you verified any Time/Space Constraints for this problem?

• Can the input array be empty?

  • Yes, that is possible

• What is the space and time complexity?

  • We want O(n) time and O(1) space.

Example 1:
Input: nums = [-1,0,1,2,-1,-4]
Output: [[-1,-1,2],[-1,0,1]]

Example 2:

Input: nums = [0,1,1]
Output: []
Explanation: The only possible triplet does not sum up to 0.

Example 3:

Input: nums = [0,0,0]
Output: [[0,0,0]]
Explanation: The only possible triplet sums up to 0.

2: M-atch

Match what this problem looks like to known categories of problems, e.g. Linked List or Dynamic Programming, and strategies or patterns in those categories.

For Array problems, we want to consider the following approaches:

• Sort.
  • The arrays are already sorted.
• Two pointer solutions (left and right pointer variables).
  • We can start at index m - 1 for nums1 and index n -1 for nums2, find the larger number and start inserting at m + n - 1 index of nums1. Repeat until we reach index 0 for nums2.
• Storing the elements of the array in a HashMap or a Set.
  • A HashMap or Set just complicates our code.
• Traversing the array with a sliding window. Similar to the two pointer solution.
  • A sliding window doesn't really help us here.

⚠️ Common Mistakes

3: P-lan

Plan the solution with appropriate visualizations and pseudocode.

General Idea:

4: I-mplement

Implement the code to solve the algorithm.

5: R-eview

Review the code by running specific example(s) and recording values (watchlist) of your code's variables along the way.

• Trace through your code with an input to check for the expected output
• Catch possible edge cases and off-by-one errors

6: E-valuate

Evaluate the performance of your algorithm and state any strong/weak or future potential work.

• Time Complexity:
• Space Complexity: