I absolutely see all the crap devs who work on 5 tasks at once create.

Basically I try to explain to them they are not paid by amount of tasks they pick up but amount of tasks that are DONE and DONE doesn't mean "yeah it kind of works, I don't have time to fix details because I have 10 other tasks".

Super annoying, yeah we can make follow up fixes - but that's more work not less and if all would be done right just now topic would be closed.

I've always worked best this way. Then again, I got my start in support, where step 2 of every ticket was "wait on the response from the user to clarify their issue." Working only a single ticket was not an option.

To this day, I still prefer Kanban to scrum-based workflows.

I wonder if people are honest to themselves whether they actually did have the ability to work on one and only one issue at once.

I mean at some point you're waiting for a build or test run, or you've submitted your work for code review. Do you sit there patiently and wait, or do you open the next ticket, a new tab, a private project, etc? (This predates AI of course)