That’s not the takeaway. The author said work on “projects” not “tickets”. In other words, volunteer to be the single responsible individual for “work streams” or “Epics”. This is actually the behavior of a mid level developer at every tech company whose leveling guidelines I have seen either internally, talked to other people about or that’s publicly available - ie Drobox

https://www.levels.fyi/blog/swe-level-framework.html

https://dropbox.tech/culture/sharing-our-engineering-career-...

A senior developer should be over guiding an implementation and mentoring and coordinating mid level and junior developers.

I made it a point ny entire career not to be a “ticket taker” and be able to say I “lead” or “designed” a major feature or implementation.