Linked List
A linked list stores values in nodes. Each node keeps the value plus a reference to the next node, so the elements do not need to live next to each other in memory.
Start with this mental model
A linked list stores values in nodes. Each node keeps the value plus a reference to the next node, so the elements do not need to live next to each other in memory.
How it works, without unnecessary jargon
The list starts at a head node. To reach an item, you follow next references one by one.
Insertion at the front is cheap because only a few references change. Random access is expensive because there is no direct index lookup.
Read the algorithm as a sequence of decisions
Keep a head reference.
Traverse with current = current.next.
For insertion/deletion, reconnect the surrounding next references carefully.
For 10 → 20 → 30, inserting 15 after 10 only changes the links around 10 and 15.
class Node {
constructor(value, next = null) {
this.value = value;
this.next = next;
}
}
class LinkedList {
head = null;
prepend(value) {
this.head = new Node(value, this.head);
}
}Do not memorize the syntax. Follow the state that changes on each line and connect it to the invariant described above.
access O(n), head insert O(1)
Do not quote this complexity mechanically. Ask which operation or input dimension it describes, then derive the cost from the loops, recursion depth, data-structure operations and any preprocessing assumptions.
Good fit
- Choose it when its dominant operations match your workload.
- Compare memory overhead as well as Big-O.
What usually goes wrong
- Memorizing complexity without understanding representation.
- Ignoring worst-case shape or resizing/rebalancing costs.
A professional answer shape
Contrast it with arrays: linked lists give flexible local insertion/deletion, but lose O(1) index access and usually have worse cache locality.
What problem does Linked List solve?
A linked list stores values in nodes. Each node keeps the value plus a reference to the next node, so the elements do not need to live next to each other in memory.
What should I mention about complexity?
Its typical cost here is access O(n), head insert O(1), but a complete answer should connect that cost to the representation, input constraints and the dominant operations.
What is the most common mistake?
Memorizing complexity without understanding representation.