Go One Layer Deeper
One ordinary line of code, expanded downward. Every layer names what it hides for you, how it fails, and where to learn it properly. Descend as far as the problem requires — and stop.
await fetch('/api/users')SELECT * FROM users WHERE email = 'alice@exaawait userRepository.save(user)$ git push # …and it is liveagent.run("refund the duplicate charge for oawait auth.signIn(email, password)await stripe.charges.create({ amount: 4990 }open('out.txt', 'w').write(data)items.sort((a, b) => a.score - b.score)
One library call, all the way down
Depth
The most-used abstraction in programming. What the library chose for you decides the complexity, the memory behaviour, and whether equal elements keep their order.
1items.sort((a, b) => a.score - b.score)- 1
1/5 layers · Enough to build
Why should an application engineer care?
Not so you can write your own sort. So you can recognise the day the input is nearly sorted, or the keys are small integers, or stability matters — cases where the general answer is not the right one.
The question this ladder asks
What is the library doing for you?
Related descents:One SELECT, all the way down