> ...let the developers choose the work...
This is much better advice than the whole article.
The article seems to be conveying vaguely that developers want advancement, interesting problems, etc. The problem with this phrasing is that it makes a manager think about placation strategies.
The root cause of the above is just poor tasking. If a senior developer says things need attention and keeps getting ignored, then how senior is the developer, really?
The advancement, engagement, product ownership, etc. all grow from a culture where strategic technical priorities aren't ultimately valued.
This looks like boredom or angst about "career progression" but you don't solve the problem by adding whiz-bang tech (gratuitous ML) or meaningless job titles.