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 and an integer k.
For each index i where 0 <= i < nums.length, change nums[i] to be either nums[i] + k or nums[i] - k.
The score of nums is the difference between the maximum and minimum elements in nums.
Return the minimum score of nums after changing the values at each index.
Example 1:
Input: nums = [1], k = 0 Output: 0 Explanation: The score is max(nums) - min(nums) = 1 - 1 = 0.
Example 2:
Input: nums = [0,10], k = 2 Output: 6 Explanation: Change nums to be [2, 8]. The score is max(nums) - min(nums) = 8 - 2 = 6.
Example 3:
Input: nums = [1,3,6], k = 3 Output: 3 Explanation: Change nums to be [4, 6, 3]. The score is max(nums) - min(nums) = 6 - 3 = 3.
Constraints:
1 <= nums.length <= 1040 <= nums[i] <= 1040 <= k <= 104Problem summary: You are given an integer array nums and an integer k. For each index i where 0 <= i < nums.length, change nums[i] to be either nums[i] + k or nums[i] - k. The score of nums is the difference between the maximum and minimum elements in nums. Return the minimum score of nums after changing the values at each index.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array · Math · Greedy
[1] 0
[0,10] 2
[1,3,6] 3
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #910: Smallest Range II
class Solution {
public int smallestRangeII(int[] nums, int k) {
Arrays.sort(nums);
int n = nums.length;
int ans = nums[n - 1] - nums[0];
for (int i = 1; i < n; ++i) {
int mi = Math.min(nums[0] + k, nums[i] - k);
int mx = Math.max(nums[i - 1] + k, nums[n - 1] - k);
ans = Math.min(ans, mx - mi);
}
return ans;
}
}
// Accepted solution for LeetCode #910: Smallest Range II
func smallestRangeII(nums []int, k int) int {
sort.Ints(nums)
n := len(nums)
ans := nums[n-1] - nums[0]
for i := 1; i < n; i++ {
mi := min(nums[0]+k, nums[i]-k)
mx := max(nums[i-1]+k, nums[n-1]-k)
ans = min(ans, mx-mi)
}
return ans
}
# Accepted solution for LeetCode #910: Smallest Range II
class Solution:
def smallestRangeII(self, nums: List[int], k: int) -> int:
nums.sort()
ans = nums[-1] - nums[0]
for i in range(1, len(nums)):
mi = min(nums[0] + k, nums[i] - k)
mx = max(nums[i - 1] + k, nums[-1] - k)
ans = min(ans, mx - mi)
return ans
// Accepted solution for LeetCode #910: Smallest Range II
struct Solution;
impl Solution {
fn smallest_range_ii(mut a: Vec<i32>, k: i32) -> i32 {
let n = a.len();
a.sort_unstable();
let mut max = a[n - 1];
let mut min = a[0];
let mut res = max - min;
for i in 0..n - 1 {
max = max.max(a[i] + 2 * k);
min = a[i + 1].min(a[0] + 2 * k);
res = res.min(max - min);
}
res
}
}
#[test]
fn test() {
let a = vec![1];
let k = 0;
let res = 0;
assert_eq!(Solution::smallest_range_ii(a, k), res);
let a = vec![0, 10];
let k = 2;
let res = 6;
assert_eq!(Solution::smallest_range_ii(a, k), res);
let a = vec![1, 3, 6];
let k = 3;
let res = 3;
assert_eq!(Solution::smallest_range_ii(a, k), res);
let a = vec![2, 7, 2];
let k = 1;
let res = 3;
assert_eq!(Solution::smallest_range_ii(a, k), res);
}
// Accepted solution for LeetCode #910: Smallest Range II
function smallestRangeII(nums: number[], k: number): number {
nums.sort((a, b) => a - b);
let ans = nums.at(-1)! - nums[0];
for (let i = 1; i < nums.length; ++i) {
const mi = Math.min(nums[0] + k, nums[i] - k);
const mx = Math.max(nums.at(-1)! - k, nums[i - 1] + k);
ans = Math.min(ans, mx - mi);
}
return ans;
}
Use this to step through a reusable interview workflow for this problem.
Try every possible combination of choices. With n items each having two states (include/exclude), the search space is 2ⁿ. Evaluating each combination takes O(n), giving O(n × 2ⁿ). The recursion stack or subset storage uses O(n) space.
Greedy algorithms typically sort the input (O(n log n)) then make a single pass (O(n)). The sort dominates. If the input is already sorted or the greedy choice can be computed without sorting, time drops to O(n). Proving greedy correctness (exchange argument) is harder than the implementation.
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.
Wrong move: Locally optimal choices may fail globally.
Usually fails on: Counterexamples appear on crafted input orderings.
Fix: Verify with exchange argument or monotonic objective before committing.