Off-by-one on range boundaries
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.
Move from brute-force thinking to an efficient approach using array strategy.
You are given an integer array nums sorted in non-decreasing order.
Build and return an integer array result with the same length as nums such that result[i] is equal to the summation of absolute differences between nums[i] and all the other elements in the array.
In other words, result[i] is equal to sum(|nums[i]-nums[j]|) where 0 <= j < nums.length and j != i (0-indexed).
Example 1:
Input: nums = [2,3,5] Output: [4,3,5] Explanation: Assuming the arrays are 0-indexed, then result[0] = |2-2| + |2-3| + |2-5| = 0 + 1 + 3 = 4, result[1] = |3-2| + |3-3| + |3-5| = 1 + 0 + 2 = 3, result[2] = |5-2| + |5-3| + |5-5| = 3 + 2 + 0 = 5.
Example 2:
Input: nums = [1,4,6,8,10] Output: [24,15,13,15,21]
Constraints:
2 <= nums.length <= 1051 <= nums[i] <= nums[i + 1] <= 104Problem summary: You are given an integer array nums sorted in non-decreasing order. Build and return an integer array result with the same length as nums such that result[i] is equal to the summation of absolute differences between nums[i] and all the other elements in the array. In other words, result[i] is equal to sum(|nums[i]-nums[j]|) where 0 <= j < nums.length and j != i (0-indexed).
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array · Math
[2,3,5]
[1,4,6,8,10]
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1685: Sum of Absolute Differences in a Sorted Array
class Solution {
public int[] getSumAbsoluteDifferences(int[] nums) {
// int s = Arrays.stream(nums).sum();
int s = 0, t = 0;
for (int x : nums) {
s += x;
}
int n = nums.length;
int[] ans = new int[n];
for (int i = 0; i < n; ++i) {
int v = nums[i] * i - t + s - t - nums[i] * (n - i);
ans[i] = v;
t += nums[i];
}
return ans;
}
}
// Accepted solution for LeetCode #1685: Sum of Absolute Differences in a Sorted Array
func getSumAbsoluteDifferences(nums []int) (ans []int) {
var s, t int
for _, x := range nums {
s += x
}
for i, x := range nums {
v := x*i - t + s - t - x*(len(nums)-i)
ans = append(ans, v)
t += x
}
return
}
# Accepted solution for LeetCode #1685: Sum of Absolute Differences in a Sorted Array
class Solution:
def getSumAbsoluteDifferences(self, nums: List[int]) -> List[int]:
ans = []
s, t = sum(nums), 0
for i, x in enumerate(nums):
v = x * i - t + s - t - x * (len(nums) - i)
ans.append(v)
t += x
return ans
// Accepted solution for LeetCode #1685: Sum of Absolute Differences in a Sorted Array
struct Solution;
impl Solution {
fn get_sum_absolute_differences(nums: Vec<i32>) -> Vec<i32> {
let n = nums.len();
let mut prev = nums[0];
let mut prev_sum = 0;
let mut res = vec![0; n];
for i in 0..n {
let diff = nums[i] - prev;
prev_sum += diff * i as i32;
res[i] += prev_sum;
prev = nums[i];
}
prev = nums[n - 1];
prev_sum = 0;
for i in (0..n).rev() {
let diff = (nums[i] - prev).abs();
prev_sum += diff * (n - 1 - i) as i32;
res[i] += prev_sum;
prev = nums[i];
}
res
}
}
#[test]
fn test() {
let nums = vec![2, 3, 5];
let res = vec![4, 3, 5];
assert_eq!(Solution::get_sum_absolute_differences(nums), res);
let nums = vec![1, 4, 6, 8, 10];
let res = vec![24, 15, 13, 15, 21];
assert_eq!(Solution::get_sum_absolute_differences(nums), res);
}
// Accepted solution for LeetCode #1685: Sum of Absolute Differences in a Sorted Array
function getSumAbsoluteDifferences(nums: number[]): number[] {
const s = nums.reduce((a, b) => a + b);
let t = 0;
const n = nums.length;
const ans = new Array(n);
for (let i = 0; i < n; ++i) {
const v = nums[i] * i - t + s - t - nums[i] * (n - i);
ans[i] = v;
t += nums[i];
}
return ans;
}
Use this to step through a reusable interview workflow for this problem.
Two nested loops check every pair or subarray. The outer loop fixes a starting point, the inner loop extends or searches. For n elements this gives up to n²/2 operations. No extra space, but the quadratic time is prohibitive for large inputs.
Most array problems have an O(n²) brute force (nested loops) and an O(n) optimal (single pass with clever state tracking). The key is identifying what information to maintain as you scan: a running max, a prefix sum, a hash map of seen values, or two pointers.
Review these before coding to avoid predictable interview regressions.
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.