Hot100: Linked List Cycle II Floyd Detection + Entry Localization ACERS Guide

Subtitle / Summary LeetCode 142 upgrades cycle detection into cycle entry localization. The robust template is Floyd: first detect a meeting inside the cycle, then reset one pointer to head and move both by one step; the next meeting node is the cycle entry. Reading time: 12-16 min Tags: Hot100, linked list, fast slow pointers, Floyd SEO keywords: Linked List Cycle II, cycle entry, Floyd, fast slow pointers, O(1) space, LeetCode 142, Hot100 Meta description: Floyd cycle detection + entry localization with proof intuition, engineering mapping, and runnable multi-language implementations in O(n) time and O(1) extra space. Target Readers Hot100 learners who want to fully internalize the 141 -> 142 linked-list template family Developers who need to locate where a pointer chain becomes cyclic Interview candidates who want to explain why “reset to head” works Background / Motivation In real systems, cycle corruption in chain structures can cause: ...

February 10, 2026 · 9 min · map[name:Jeanphilo]

Hot100: Merge Two Sorted Lists Sentinel Two-Pointer Merge ACERS Guide

Subtitle / Summary This problem is the linked-list version of merge-sort’s merge step. Use a sentinel node plus two pointers to splice nodes in ascending order in O(m+n), without rebuilding the list. Reading time: 10-12 min Tags: Hot100, linked list, merge, two pointers SEO keywords: Merge Two Sorted Lists, sentinel node, linked list merge, LeetCode 21, Hot100 Meta description: A complete ACERS guide for LeetCode 21 with derivation, correctness invariants, pitfalls, and runnable multi-language code. Target Readers Hot100 learners preparing linked-list interview templates Developers who often lose nodes while rewiring next Engineers who need stable O(1)-extra-space merge patterns Background / Motivation This is a small problem with large transfer value: ...

February 10, 2026 · 10 min · map[name:Jeanphilo]

Hot100: First Missing Positive In-Place Index Placement ACERS Guide

Subtitle / Summary First Missing Positive is a classic in-place indexing problem. Place each valid value x into slot x-1, then scan for the first mismatch. This ACERS guide explains the derivation, invariant, pitfalls, and production-style transfer. Reading time: 12-15 min Tags: Hot100, array, in-place hashing SEO keywords: First Missing Positive, in-place hashing, index mapping, O(n), Hot100, LeetCode 41 Meta description: O(n)/O(1) solution for First Missing Positive using in-place index placement, with complexity analysis, engineering scenarios, and runnable multi-language code. Target Readers Hot100 learners building stable array templates Intermediate developers who want to master in-place indexing techniques Engineers who need linear-time, constant-space array normalization Background / Motivation “Find the smallest missing positive” is fundamentally a placement problem. ...

February 10, 2026 · 10 min · map[name:Jeanphilo]

Hot100: Reverse Nodes in k-Group Group-Wise In-Place ACERS Guide

Subtitle / Summary LeetCode 25 is the upgrade path from 206 (full reversal) and 92 (interval reversal): split by groups, reverse inside each full group, reconnect safely, and keep the last incomplete group unchanged. Reading time: 14-18 min Tags: Hot100, linked list, group reversal, dummy node SEO keywords: Reverse Nodes in k-Group, group reversal, LeetCode 25, Hot100 Meta description: In-place k-group linked-list reversal with dummy-node anchoring and safe reconnection, including pitfalls, complexity, and runnable multi-language implementations. Target Readers Hot100 learners who already finished 206/92 and want the next linked-list jump Developers who often fail at boundary handling and reconnection in pointer-heavy tasks Engineers building reusable templates for chunk-based list transformation Background / Motivation In real systems, chain structures are often processed in batches: ...

February 10, 2026 · 11 min · map[name:Jeanphilo]

Hot100: Reorder List In-Place Split-Reverse-Merge ACERS Guide

Subtitle / Summary Reorder List is a classic pointer choreography problem: find middle, reverse second half, then merge alternately. This guide derives the in-place O(n)/O(1) method from naive ideas and turns it into a reusable Hot100 template. Reading time: 12-15 min Tags: Hot100, linked list, in-place SEO keywords: Reorder List, split reverse merge, LeetCode 143, O(1) space Meta description: A full ACERS explanation of Reorder List with correctness intuition, boundary handling, engineering mapping, and runnable code in Python/C/C++/Go/Rust/JS. Target Readers Hot100 learners who want a stable linked-list rewire template Developers who can reverse lists but still fail on alternating merge details Engineers preparing for interviews where O(1) extra space is required Background / Motivation At first glance, this looks like simple reordering. In reality, it tests whether you can safely perform three dependent pointer operations in one workflow: ...

February 10, 2026 · 10 min · map[name:Jeanphilo]

Hot100: Reverse Linked List II Dummy Node + Head-Insertion ACERS Guide

Subtitle / Summary Reverse Linked List II is not about full-list reversal; it is about reversing a strict middle interval while preserving both outer connections. This ACERS guide explains the dummy-node anchor, head-insertion loop, and boundary-safe implementation. Reading time: 12-15 min Tags: Hot100, linked list, sublist reversal, dummy node SEO keywords: Reverse Linked List II, sublist reversal, dummy node, head insertion, LeetCode 92, Hot100 Meta description: In-place sublist reversal with dummy node + head insertion in O(n)/O(1), with correctness intuition, pitfalls, and runnable multi-language code. Target Readers Hot100 learners who already know 206 and want the interval version Developers who often fail at linked-list boundary handling (left = 1, right = n) Engineers building reusable pointer-rewiring templates Background / Motivation LeetCode 206 reverses the whole list. LeetCode 92 asks for a stricter operation: ...

February 10, 2026 · 10 min · map[name:Jeanphilo]

Hot100: Linked List Cycle Floyd Fast/Slow Pointer ACERS Guide

Subtitle / Summary Detecting a cycle in a linked list is a pointer chasing problem, not a value comparison problem. This ACERS guide explains why Floyd’s fast/slow pointers must meet if a cycle exists, how to avoid null-pointer bugs, and how the same pattern maps to engineering checks. Reading time: 10-12 min Tags: Hot100, linked list, fast slow pointers, Floyd SEO keywords: Linked List Cycle, Floyd, fast slow pointers, LeetCode 141, Hot100 Meta description: O(n)/O(1) cycle detection in singly linked lists using Floyd fast/slow pointers, with alternatives, common mistakes, and runnable multi-language code. Target Readers Hot100 learners and interview candidates Developers building reusable linked-list two-pointer templates Engineers who need to detect loops in chain-like structures Background / Motivation Cycle bugs are common in pointer-linked structures: ...

February 10, 2026 · 8 min · map[name:Jeanphilo]

Hot100: Palindrome Linked List Fast/Slow + Reverse Second Half O(1) Space ACERS Guide

Subtitle / Summary The core of palindrome validation is symmetric comparison, but a singly linked list cannot move backward. The most stable engineering template is: find middle -> reverse second half in-place -> compare -> reverse back to restore. Reading time: 10-14 min Tags: Hot100, linked list, fast slow pointers, in-place reverse SEO keywords: Palindrome Linked List, fast slow pointers, reverse second half, O(1) space, LeetCode 234 Meta description: O(n)/O(1) palindrome check for singly linked list with middle detection, second-half reversal, comparison, and full structure restoration. Target Readers Hot100 learners who want to master the “middle + reverse” linked-list combo Developers who frequently solve palindrome/symmetry interview questions Engineers who care about low extra memory and non-destructive checks Background / Motivation For arrays, palindrome check is easy with two pointers from both ends. For singly linked lists, you can only move forward via next, so symmetric comparison is not direct. ...

February 9, 2026 · 10 min · map[name:Jeanphilo]

Hot100: Reverse Linked List Three-Pointer Iterative/Recursive ACERS Guide

Subtitle / Summary Reverse Linked List is the first serious pointer-rewiring exercise in Hot100. It looks simple, but most bugs come from broken links and wrong operation order. This ACERS guide explains the three-pointer iterative template thoroughly and compares it with recursion. Reading time: 10-12 min Tags: Hot100, linked list, pointer, iteration SEO keywords: Hot100, Reverse Linked List, three pointers, iterative, recursive, LeetCode 206 Meta description: Three-pointer iterative reversal in O(n)/O(1), with recursive contrast, common pitfalls, engineering mapping, and runnable multi-language implementations. Target Readers Hot100 learners and interview candidates Developers who often hit null-pointer or broken-chain bugs in list problems Engineers who want stable pointer manipulation patterns in C/C++/Rust/Go Background / Motivation In production code, “reverse linked list” may not appear as a LeetCode function, but the skill is highly transferable: ...

February 9, 2026 · 9 min · map[name:Jeanphilo]

Hot100: Subarray Sum Equals K Prefix Sum + Hash Map ACERS Guide

Subtitle / Summary This is Hot100 article #1 for the series: Subarray Sum Equals K. We reduce the naive O(n^2) approach to O(n) with prefix sum plus a frequency hash map, then map the same pattern to real engineering scenarios. Reading time: 12-15 min Tags: Hot100, prefix sum, hash map SEO keywords: Subarray Sum Equals K, prefix sum, hash map, O(n), Hot100 Meta description: O(n) counting of subarrays with sum k using prefix sum + hash map, with complexity analysis and runnable multi-language code. Target Readers Hot100 learners who want stable reusable templates Intermediate engineers who want to transfer counting patterns to real data pipelines Interview prep readers who want to master prefix sum + hash map Background / Motivation “Count subarrays whose sum equals k” is one of the most classic counting problems. It appears in log analytics, risk threshold hits, and transaction sequence statistics. The two-loop brute force method is straightforward, but slows down quickly as input grows. So we need an O(n) method that scales. ...

February 9, 2026 · 9 min · map[name:Jeanphilo]