Callbacks & Callback Hell

What common asynchronous programming problem does this code illustrate?

getData(function(a) {
  getMore(a, function(b) {
    getMore(b, function(c) {
      getMore(c, function(d) {
        // Handle d
      });
    });
  });
});

Memory leak
Race condition
Callback hell
This code illustrates 'callback hell' or 'pyramid of doom' - a situation where multiple nested callbacks make code: 1) Difficult to read and maintain, 2) Hard to reason about the flow of execution, 3) Challenging to handle errors consistently, 4) Complex to modify or extend. This is a common issue in asynchronous JavaScript that led to the development of Promises and async/await as cleaner alternatives.
Stack overflow

Next Question (3/20)