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.
Break down a hard problem into reliable checkpoints, edge-case handling, and complexity trade-offs.
Given an m x n grid. Each cell of the grid has a sign pointing to the next cell you should visit if you are currently in this cell. The sign of grid[i][j] can be:
1 which means go to the cell to the right. (i.e go from grid[i][j] to grid[i][j + 1])2 which means go to the cell to the left. (i.e go from grid[i][j] to grid[i][j - 1])3 which means go to the lower cell. (i.e go from grid[i][j] to grid[i + 1][j])4 which means go to the upper cell. (i.e go from grid[i][j] to grid[i - 1][j])Notice that there could be some signs on the cells of the grid that point outside the grid.
You will initially start at the upper left cell (0, 0). A valid path in the grid is a path that starts from the upper left cell (0, 0) and ends at the bottom-right cell (m - 1, n - 1) following the signs on the grid. The valid path does not have to be the shortest.
You can modify the sign on a cell with cost = 1. You can modify the sign on a cell one time only.
Return the minimum cost to make the grid have at least one valid path.
Example 1:
Input: grid = [[1,1,1,1],[2,2,2,2],[1,1,1,1],[2,2,2,2]] Output: 3 Explanation: You will start at point (0, 0). The path to (3, 3) is as follows. (0, 0) --> (0, 1) --> (0, 2) --> (0, 3) change the arrow to down with cost = 1 --> (1, 3) --> (1, 2) --> (1, 1) --> (1, 0) change the arrow to down with cost = 1 --> (2, 0) --> (2, 1) --> (2, 2) --> (2, 3) change the arrow to down with cost = 1 --> (3, 3) The total cost = 3.
Example 2:
Input: grid = [[1,1,3],[3,2,2],[1,1,4]] Output: 0 Explanation: You can follow the path from (0, 0) to (2, 2).
Example 3:
Input: grid = [[1,2],[4,3]] Output: 1
Constraints:
m == grid.lengthn == grid[i].length1 <= m, n <= 1001 <= grid[i][j] <= 4Problem summary: Given an m x n grid. Each cell of the grid has a sign pointing to the next cell you should visit if you are currently in this cell. The sign of grid[i][j] can be: 1 which means go to the cell to the right. (i.e go from grid[i][j] to grid[i][j + 1]) 2 which means go to the cell to the left. (i.e go from grid[i][j] to grid[i][j - 1]) 3 which means go to the lower cell. (i.e go from grid[i][j] to grid[i + 1][j]) 4 which means go to the upper cell. (i.e go from grid[i][j] to grid[i - 1][j]) Notice that there could be some signs on the cells of the grid that point outside the grid. You will initially start at the upper left cell (0, 0). A valid path in the grid is a path that starts from the upper left cell (0, 0) and ends at the bottom-right cell (m - 1, n - 1) following the signs on the grid. The valid path does not have to be the shortest. You can modify the sign on a cell with cost = 1.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array
[[1,1,1,1],[2,2,2,2],[1,1,1,1],[2,2,2,2]]
[[1,1,3],[3,2,2],[1,1,4]]
[[1,2],[4,3]]
minimum-weighted-subgraph-with-the-required-paths)disconnect-path-in-a-binary-matrix-by-at-most-one-flip)Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1368: Minimum Cost to Make at Least One Valid Path in a Grid
class Solution {
public int minCost(int[][] grid) {
int m = grid.length, n = grid[0].length;
boolean[][] vis = new boolean[m][n];
Deque<int[]> q = new ArrayDeque<>();
q.offer(new int[] {0, 0, 0});
int[][] dirs = {{0, 0}, {0, 1}, {0, -1}, {1, 0}, {-1, 0}};
while (!q.isEmpty()) {
int[] p = q.poll();
int i = p[0], j = p[1], d = p[2];
if (i == m - 1 && j == n - 1) {
return d;
}
if (vis[i][j]) {
continue;
}
vis[i][j] = true;
for (int k = 1; k <= 4; ++k) {
int x = i + dirs[k][0], y = j + dirs[k][1];
if (x >= 0 && x < m && y >= 0 && y < n) {
if (grid[i][j] == k) {
q.offerFirst(new int[] {x, y, d});
} else {
q.offer(new int[] {x, y, d + 1});
}
}
}
}
return -1;
}
}
// Accepted solution for LeetCode #1368: Minimum Cost to Make at Least One Valid Path in a Grid
func minCost(grid [][]int) int {
m, n := len(grid), len(grid[0])
q := doublylinkedlist.New()
q.Add([]int{0, 0, 0})
dirs := [][]int{{0, 0}, {0, 1}, {0, -1}, {1, 0}, {-1, 0}}
vis := make([][]bool, m)
for i := range vis {
vis[i] = make([]bool, n)
}
for !q.Empty() {
v, _ := q.Get(0)
p := v.([]int)
q.Remove(0)
i, j, d := p[0], p[1], p[2]
if i == m-1 && j == n-1 {
return d
}
if vis[i][j] {
continue
}
vis[i][j] = true
for k := 1; k <= 4; k++ {
x, y := i+dirs[k][0], j+dirs[k][1]
if x >= 0 && x < m && y >= 0 && y < n {
if grid[i][j] == k {
q.Insert(0, []int{x, y, d})
} else {
q.Add([]int{x, y, d + 1})
}
}
}
}
return -1
}
# Accepted solution for LeetCode #1368: Minimum Cost to Make at Least One Valid Path in a Grid
class Solution:
def minCost(self, grid: List[List[int]]) -> int:
m, n = len(grid), len(grid[0])
dirs = [[0, 0], [0, 1], [0, -1], [1, 0], [-1, 0]]
q = deque([(0, 0, 0)])
vis = set()
while q:
i, j, d = q.popleft()
if (i, j) in vis:
continue
vis.add((i, j))
if i == m - 1 and j == n - 1:
return d
for k in range(1, 5):
x, y = i + dirs[k][0], j + dirs[k][1]
if 0 <= x < m and 0 <= y < n:
if grid[i][j] == k:
q.appendleft((x, y, d))
else:
q.append((x, y, d + 1))
return -1
// Accepted solution for LeetCode #1368: Minimum Cost to Make at Least One Valid Path in a Grid
struct Solution;
use std::collections::VecDeque;
impl Solution {
fn min_cost(grid: Vec<Vec<i32>>) -> i32 {
let n = grid.len();
let m = grid[0].len();
let mut dist = vec![vec![std::i32::MAX; m]; n];
let mut queue: VecDeque<(usize, usize, i32)> = VecDeque::new();
dist[0][0] = 0;
queue.push_back((0, 0, 0));
while let Some((i, j, d)) = queue.pop_front() {
let right = Self::cost(i, j, d, 1, &grid);
let left = Self::cost(i, j, d, 2, &grid);
let down = Self::cost(i, j, d, 3, &grid);
let up = Self::cost(i, j, d, 4, &grid);
if i > 0 && up < dist[i - 1][j] {
dist[i - 1][j] = up;
queue.push_back((i - 1, j, up));
}
if j > 0 && left < dist[i][j - 1] {
dist[i][j - 1] = left;
queue.push_back((i, j - 1, left));
}
if i + 1 < n && down < dist[i + 1][j] {
dist[i + 1][j] = down;
queue.push_back((i + 1, j, down));
}
if j + 1 < m && right < dist[i][j + 1] {
dist[i][j + 1] = right;
queue.push_back((i, j + 1, right));
}
}
dist[n - 1][m - 1]
}
fn cost(i: usize, j: usize, cost: i32, dir: i32, grid: &[Vec<i32>]) -> i32 {
if dir == grid[i][j] {
cost
} else {
cost + 1
}
}
}
#[test]
fn test() {
let grid = vec_vec_i32![[1, 1, 1, 1], [2, 2, 2, 2], [1, 1, 1, 1], [2, 2, 2, 2]];
let res = 3;
assert_eq!(Solution::min_cost(grid), res);
let grid = vec_vec_i32![[1, 1, 3], [3, 2, 2], [1, 1, 4]];
let res = 0;
assert_eq!(Solution::min_cost(grid), res);
let grid = vec_vec_i32![[2, 2, 2], [2, 2, 2]];
let res = 3;
assert_eq!(Solution::min_cost(grid), res);
let grid = vec_vec_i32![[4]];
let res = 0;
assert_eq!(Solution::min_cost(grid), res);
}
// Accepted solution for LeetCode #1368: Minimum Cost to Make at Least One Valid Path in a Grid
function minCost(grid: number[][]): number {
const m = grid.length,
n = grid[0].length;
let ans = Array.from({ length: m }, v => new Array(n).fill(Infinity));
ans[0][0] = 0;
let queue = [[0, 0]];
const dirs = [
[0, 1],
[0, -1],
[1, 0],
[-1, 0],
];
while (queue.length) {
let [x, y] = queue.shift();
for (let step = 1; step < 5; step++) {
let [dx, dy] = dirs[step - 1];
let [i, j] = [x + dx, y + dy];
if (i < 0 || i >= m || j < 0 || j >= n) continue;
let cost = ~~(grid[x][y] != step) + ans[x][y];
if (cost >= ans[i][j]) continue;
ans[i][j] = cost;
if (grid[x][y] == step) {
queue.unshift([i, j]);
} else {
queue.push([i, j]);
}
}
}
return ans[m - 1][n - 1];
}
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.