Your concept feed
39 ideas
Follow the connections in this topic
A small step before this topic
Let’s picture it Let’s start with three stops.
Home. Then the park. Then the café. Just a few things in a row.
One little change Point to the middle one.
The park is second. In Python, its position is 1, because counting starts at 0.
Now it has a name That’s a list.
A list keeps things in order. An index is just a position in that list.
No pressure. Just try it.Which place is at position 0?
1 / 4 A small step before this topic
Let’s picture it Now visit each stop.
You don’t need three different instructions. “Visit the next place” works each time.
One little change One, then the next.
Finish home. Move to the park. Then do the same at the café.
Now it has a name That repeat is a loop.
One small action, repeated for each item. Three stops mean three visits.
No pressure. Just try it.Add one more stop. How many visits now?
1 / 4 A small step before this topic
Let’s picture it What if it rains?
Let’s choose the café on rainy days, and the park on sunny days.
One little change Today is sunny.
The rule stays the same. The weather changed, so we choose the other place.
Now it has a name That’s an if / else.
Raining?
Yes: café
No: park
A condition is a yes-or-no question. Its answer chooses which step happens next.
No pressure. Just try it.It’s raining. Where does our rule send us?
1 / 4 A small step before this topic
Let’s picture it Name a tiny job.
Our job is “add one.” Give it 3, and it gives back 4.
One little change Try a new input.
Give the same job 8. It gives back 9. We can reuse the instructions.
Now it has a name That job is a function.
Input goes in. An answer comes back. In Python, return sends the answer back.
No pressure. Just try it.What does add-one return for 5?
1 / 4 A small step before this topic
Let’s picture it Picture a pile of plates.
Blue goes down first. Pink goes on top.
One little change Take the top one.
Pink comes off first, even though blue arrived first.
Now it has a name That’s a stack.
Last in, first out. Paused function calls work this way too: finish the newest call, then return.
No pressure. Just try it.Add green on top. Which plate comes off next?
1 / 4 A small step before this topic
Let’s picture it Now picture a line of people.
Ana arrives first. Bo waits behind her.
One little change Ana goes first.
Bo moves to the front. New arrivals join the back.
Now it has a name That’s a queue.
First in, first out. Unlike plates, we serve the oldest waiting item first.
No pressure. Just try it.Who goes before Cy?
1 / 4 A small step before this topic
Let’s picture it Have we visited the park?
Keep a little checklist of places we’ve seen.
One little change Write park again.
We still only need one check beside park. We’re remembering whether, not how many times.
Now it has a name That’s a set.
A set keeps distinct items. “Is park in here?” becomes a quick membership check.
No pressure. Just try it.Add park twice. How many copies in a set?
1 / 4 A small step before this topic
Let’s picture it Let’s remember a little more.
The park is five minutes away. Write that beside its name.
One little change Look it up later.
Ask for “park.” The notebook gives you 5. No need to measure the walk again.
Now it has a name That’s a dictionary.
A key finds a value. Here, the place name is the key and the time is the value.
No pressure. Just try it.We now write park: 6. What does park return?
1 / 4 A small step before this topic
Let’s picture it Draw our little walk.
A dot for each place. A line where we can walk directly.
One little change Two short walks can join.
Home to park, then park to café. We can reach the café without a direct road.
Now it has a name Dots and links have names.
A dot is a node. A link is an edge. Together, they make a graph.
No pressure. Just try it.Must two places share a direct road to be reachable?
1 / 4 A small step before this topic
Let’s picture it Where did we put the book?
Try “second shelf, first box.” We need two positions, not just one.
One little change Pick a row, then a column.
Python calls the second row 1. The first column is 0. So the book is at [1][0].
Now it has a name That’s a two-dimensional table.
Two labels find one cell. A third label could tell us which cupboard contains the table.
No pressure. Just try it.Two cupboards have the same shelves. What extra label helps?
1 / 4 A small step before this topic
Let’s picture it Same door. One small difference.
You have a key. Your friend doesn’t. The door is the same, but your next move isn’t.
One little change Remember the key.
If we only write down “at the door,” we lose something important.
Now it has a name That little note is a state.
A state remembers what we need to continue. Here: where we are, and whether we have the key.
No pressure. Just try it.Is “at the door” enough to decide if we can enter?
1 / 4 A small step before this topic
Let’s picture it How many little jobs?
Visit three places. Say hello once at each. That’s three hellos.
One little change Now try every pair.
Three people each greet all three people, including themselves for this toy count. That’s nine greetings.
Now it has a name Count how the work grows.
One pass grows with n. Trying every pair grows with n × n. Code length doesn’t tell us that.
No pressure. Just try it.With 4 items, how many ordered pairs, including self-pairs?
1 / 4 A small step before this topic
Let’s picture it Find 8 in a sorted row.
Start with 2, 4, 6, 8, 10. Look at the middle: 6.
One little change Keep the side that can work.
8 is bigger than 6. Everything on the left is too small, so we can leave it behind.
Now it has a name Keep one promise.
If 8 is present, it stays in the part we keep. That repeating promise is called an invariant.
No pressure. Just try it.Would this left-or-right shortcut work on an unsorted row?
1 / 4 A small step before this topic
Let’s picture it Keep a small part of a row.
Our budget is 5. The values 2 and 3 fit together.
One little change One more makes it too much.
Add 4: the sum is 9. Remove from the left until it fits again.
Now it has a name That moving part is a window.
left edge
kept values
right edge
With nonnegative values, adding cannot lower the sum. That predictable change tells us which boundary to move.
No pressure. Just try it.Could adding a negative number make a too-large sum fit?
1 / 4 A small step before this topic
Let’s picture it Open a box.
There’s a smaller box inside. We already know how to open a box.
One little change Do the same small job again.
Open the smaller box. Keep going until there isn’t another box inside.
Now it has a name That’s the idea of recursion.
A function asks itself to handle a smaller case. The empty box is our stopping point: the base case.
No pressure. Just try it.What if every box contains another box forever?
1 / 4 A small step before this topic
Let’s picture it A question can make two more.
Climb one or two stairs at a time. Four stairs can lead to a smaller question with three or two left.
One little change Look, the same question returns.
ways(3) also asks for ways(2). We’ve reached that smaller question twice.
Now it has a name Notice the repeated work.
Draw the calls to spot repeated questions. Later, we’ll save their answers instead of solving them again.
No pressure. Just try it.Do two calls with the same input always need separate work here?
1 / 4 A small step before this topic
Let’s picture it Count a tiny family of dots.
One parent has two children. Each child says, “There’s one of me.”
One little change Let the answers travel up.
The parent adds the two answers, then counts itself: 1 + 1 + 1.
Now it has a name That works for bigger trees too.
my answer
left answer
right answer
Ask each child about its little tree. Combine the answers. You don’t need to hold the whole tree in your head.
No pressure. Just try it.Do we also count the parent itself?
1 / 4 A small step before this topic
Let’s picture it Come back to our little map.
Home, park, café. Each place is a dot; each allowed walk is a link.
One little change A dot can also mean a situation.
“At park with a key” may allow a move that “at park without a key” cannot.
Now it has a name Choose dots that tell the whole story.
situation
legal move
new situation
A graph organizes possible moves. Sometimes places are enough. Sometimes a place plus a small extra fact is needed.
No pressure. Just try it.Must graph nodes always represent physical places?
1 / 4 A small step before this topic
Let’s picture it Try the nearest places first.
From home, find everything one road away before looking two roads away.
One little change Put new places at the back.
A queue keeps the earlier discoveries in front. That lets us finish one layer before the next.
Now it has a name That’s breadth-first search: BFS.
With equal-cost roads, the first layer reaching a place uses the fewest roads. Unequal costs need more care.
No pressure. Just try it.One road costs 100 minutes; two others cost 1 each. Fewest roads means fastest?
1 / 4 A small step before this topic
A familiar idea Two oranges start rotten.
In this row, both ends are rotten at minute zero. The middle orange is fresh.
One new wrinkle Both ends spread together.
The middle turns rotten after one minute. We should not finish one source’s entire search before starting the other.
Try a tiny example Put all starts in the queue.
all starts: 0
neighbors: 1
next: 2
Give every rotten orange distance zero. Then process the next layer just as in ordinary BFS.
Notice what matters First arrival wins.
Mark a fresh orange when it enters the queue. Two nearby sources must not count it twice.
Make it reusable One search, many beginnings.
The last reached fresh orange determines the time. If any fresh orange remains unreachable, return −1.
No pressure. Just try it.One fresh orange is isolated by empty cells. What happens?
1 / 6 A small step before this topic
Let’s picture it Follow one path for a while.
Instead of finishing a whole layer, keep walking down one branch. This is depth-first search, or DFS.
One little change Remember where you’ve been.
For reachability, a seen set helps avoid walking around the same cycle forever.
Now it has a name But ask what “seen” means.
this attempt
undo mark
next attempt
For routes that cannot repeat a place, a place used in one attempt may be free in another. Clear path-only marks when returning.
No pressure. Just try it.Does “used in this path” always mean “forbidden in every path”?
1 / 4 A small step before this topic
Let’s picture it Socks before shoes.
Some jobs must wait for other jobs. Draw an arrow from the earlier job to the later one.
One little change Start with a ready job.
Do a job with nothing unfinished before it. Remove it from the waiting list and look for the next ready job.
Now it has a name That makes a dependency order.
A waits for B
B waits for A
Its name is topological order. A cycle means some jobs keep waiting on one another, so no such order exists.
No pressure. Just try it.A waits for B, and B waits for A. Can either start under these rules?
1 / 4 A small step before this topic
Let’s picture it Try a snack combination.
Pick apple first. See what can go with it. We’re exploring, not committing forever.
One little change Put it back and try again.
After exploring the apple choices, undo that pick. Now start with banana.
Now it has a name That’s backtracking.
Choose, explore, undo. Undoing keeps the next attempt from accidentally inheriting the last attempt’s choices.
No pressure. Just try it.Before a sibling attempt, what happens to path-only choices?
1 / 4 A small step before this topic
Let’s picture it We’ve answered this before.
route A
3 stairs left
route B
Two routes leave us with three stairs left. We may climb one or two at a time.
One little change Save these three little routes.
The routes are 1+1+1, 1+2, and 2+1. Count them once; both arrivals can reuse the answer.
Now it has a name That sharing is the heart of DP.
same question
reuse answer
Dynamic programming saves answers to smaller questions. Share only when the remaining question really is the same.
No pressure. Just try it.One route has a key left and the other doesn’t. Always the same remaining question?
1 / 4 A small step before this topic
Let’s picture it Two ways to fill a notebook.
One way: when a question appears, solve it if needed, then write down the answer.
One little change Or prepare the small answers first.
Fill answers in an order where each needed earlier answer is already available.
Now it has a name Same idea, different order.
Saving answers on demand is memoization. Filling them in a planned order is tabulation.
No pressure. Just try it.When filling a table, should an answer be ready before another cell uses it?
1 / 4 A small step before this topic
Let’s picture it Pick snacks, but not neighbors.
The values are 4, 5, 4. Taking the middle snack blocks both neighbors.
One little change Taking less first can win.
Take the first 4 and the last 4. Their total is 8, which beats 5.
Now it has a name Ask about the row from here.
At position i, compare taking it and moving two places, or skipping it and moving one. One position names this smaller question.
No pressure. Just try it.After taking position i, where can we continue?
1 / 4 A small step before this topic
Let’s picture it Make 3 using coins 1 and 2.
We could use 1 then 2, or 2 then 1.
One little change What are we counting?
Those are two orders, but the same combination of coins. The question decides whether to count them separately.
Now it has a name Same ingredients, different tasks.
fewest?
orders?
combinations?
Fewest coins, number of orders, and number of combinations are different questions. Decide which answer one cell is storing.
No pressure. Just try it.If order doesn’t matter, are 1+2 and 2+1 two combinations?
1 / 4 A small step before this topic
Let’s picture it Keep some numbers in order.
From 3, 1, 2, we can keep 1 then 2. We are allowed to skip 3.
One little change Ask what can end here.
For the 2, an earlier smaller number such as 1 can extend into a longer increasing sequence.
Now it has a name Gaps are allowed.
A subsequence preserves order without needing neighboring positions. That’s different from one continuous window.
No pressure. Just try it.Can we reorder 3, 1, 2 into 1, 2, 3 as a subsequence?
1 / 4 A small step before this topic
Let’s picture it Walk across four squares.
Start at the top-left. Reach the bottom-right. For now, moves only go right or down.
One little change Two tiny routes.
Right, then down. Or down, then right. Both reach the same finish.
Now it has a name A square can share its answer.
Row and column name the remaining journey. With only right/down moves, we can fill answers without moving in circles.
No pressure. Just try it.If moves can go in circles, is this simple fill order automatically safe?
1 / 4 A small step before this topic
Let’s picture it Keep letters in the same order.
Compare abc with ac. We can keep a, skip b, then keep c. The shared sequence is ac.
One little change Put a bookmark in each word.
After keeping a, we compare b with c. Skipping b moves only the first bookmark. Now c matches c.
Now it has a name Two bookmarks name one question.
position in word 1
position in word 2
Ask for the longest shared sequence remaining. Equal letters can join it; otherwise, try skipping from either string and keep the better answer.
No pressure. Just try it.May we rearrange letters to make the shared sequence longer?
1 / 4 A small step before this topic
Let’s picture it Will this snack fit?
snack: 3
room: 4 ✓
room: 2 ×
The snack weighs 3. A bag with 4 spaces can take it; a bag with 2 cannot.
One little change Remember the room left.
Seeing the same next item doesn’t mean having the same choices. The remaining capacity matters too.
Now it has a name Give the question two labels.
For 0/1 knapsack, remember which item comes next and how much capacity remains. Each item can be chosen at most once.
No pressure. Just try it.For 0/1 knapsack, after taking an item, can we take that same item again?
1 / 4 A small step before this topic
Let’s picture it Which cut should be last?
Some problems concern one stretch of items. Try choosing the final split, instead of the first action.
One little change Solve the two sides.
If that split makes the sides independent, combine their best answers and the split’s cost.
Now it has a name Name a stretch by its ends.
left boundary
right boundary
Interval DP uses a left and right boundary. Try possible split points. First check that the two sides really are independent.
No pressure. Just try it.Can we combine two independently solved sides if hidden choices still link them?
1 / 4 A small step before this topic
Let’s picture it Same square. Different tickets.
square + 1 ticket
square + 0 tickets
A wall is ahead. One traveler has a wall-removal ticket; the other has none.
One little change Keep their answers separate.
The first traveler may pass. The second may be stuck. Row and column alone lose that difference.
Now it has a name That’s a third state label.
place in row
place in column
budget
3D DP isn’t strange geometry. It means three pieces of information identify the smaller question.
No pressure. Just try it.Which label distinguishes these two travelers?
1 / 4 A small step before this topic
A familiar idea Remember the wall-removal ticket?
same grid
new movement rule
new objective
Now moves can go up, down, left, or right. We want the fewest steps, not the number of routes.
One new wrinkle Two arrivals are not always equivalent.
At the same square, one traveler has no tickets left. Another has one and can pass a wall ahead.
Try a tiny example Keep the ticket in the visited key.
Use (row, column, remaining tickets). Spending a ticket moves to a different state, even at a familiar location.
Notice what matters Choose BFS because each move costs one.
The first reached goal state has the fewest steps. The queue handles cycles; a right/down table order no longer does.
Make it reusable Extra state does not force a DP table.
what to remember
how to explore
State design and exploration order are separate choices. Here the correct combination is a three-coordinate state explored with BFS.
No pressure. Just try it.Can we reject every second arrival at the same square?
1 / 6 A small step before this topic
Let’s picture it Two travelers move down together.
Both are on the same row. One is in column 0; the other is in column 2.
One little change We don’t need two row labels.
Their row is shared. Store it once, plus one column for each traveler.
Now it has a name Three labels can describe two people.
Count independent information, not characters. If both collect from the same cell, count that cell’s reward once.
No pressure. Just try it.Do we need four position labels when both always share a row?
1 / 4 A small step before this topic
Let’s picture it Do we still need yesterday’s notes?
Suppose today’s row only reads yesterday’s row. Rows before yesterday will never be used again.
One little change Keep two rows, then swap.
Finish the new row. It becomes the previous row for the next step.
Now it has a name Less storage, same questions.
keep what is read
discard what isn’t
Space compression removes answers we won’t read again. It does not remove information the next calculation still needs.
No pressure. Just try it.Can we overwrite an old value before its last reader uses it?
1 / 4 A small step before this topic
A familiar idea Give three places their own switches.
Rightmost is A, middle is B, leftmost is C. A lit bit means that place has been visited.
One new wrinkle Visit A, then C.
Turn on A’s bit: 001. Then C’s bit: 101. The same places in another order produce the same mask.
Try a tiny example Use OR to turn a bit on.
mask
single bit
OR combines
1 << v makes a single lit bit at position v. mask | (1 << v) includes that place without switching other bits off.
Notice what matters Use AND to ask whether it is on.
membership: &
include: |
all: 111
mask & (1 << v) is nonzero exactly when v is included. All three places visited gives 111.
Make it reusable Small notation. Still many possible sets.
Three bits allow eight masks. n bits allow 2ⁿ. A compact representation does not make every subset search cheap.
No pressure. Just try it.Does 101 remember whether A or C was visited first?
1 / 6 A small step before this topic
Let’s picture it Which towns are still unvisited?
Two travelers stand at C. One has visited A; the other has visited B. Their remaining tasks differ.
One little change Keep a tiny checklist.
For A, B, C, the bits 1, 0, 1 mean A and C have been visited.
Now it has a name The chosen set can be state.
Subset DP remembers which items are included, often alongside a current position. n yes/no choices give 2ⁿ possible subsets.
No pressure. Just try it.Does a compact bitmask make the number of possible subsets small?
1 / 4 A small step before this topic
A familiar idea Visit every leaf of a little star.
A center connects three leaves. You may start anywhere and revisit nodes. Find the shortest walk covering all four.
One new wrinkle The center must be visited again.
leaf A
center
leaf B
center
leaf C
Start at one leaf: leaf → center → leaf → center → last leaf. That is four moves.
Try a tiny example Same center. More places collected.
center + {A}
center + {A,B}
At the center with only A visited, B and C remain. After visiting B, the remaining task is different.
Notice what matters Pair the node with its visited mask.
A bit per node remembers the set. Revisiting the center is allowed; rediscovering the identical node-and-mask state is unnecessary.
Make it reusable Put every starting node into BFS.
all starts
BFS states
all bits on
Each start has distance zero and its own one-bit mask. Stop at the first state whose mask contains every node.
Name the idea Graph search meets subset state.
revisit allowed
same mask possible
queue order
Unlike exactly-once subset DP, some moves add no new bit. BFS handles those cycles because every move still costs one.
No pressure. Just try it.Why not mark the center visited forever after its first arrival?
1 / 7 Keep a connection for later.
Tap the bookmark on any post to find it here.