When I code, I always work on one thing for 60 - 90 minutes, nothing else so all working memory is dedicated to task at hand.
When I read (fiction or technical) or watch a lecture on YouTube, this is usually a dedicated 15 - 60 minute session. Once again, all working memory is dedicated to task at hand.
Working memory might be a problem for people who multitask, but I don't like to do that.
You need to understand the scope of what you are working on. For example, right now I am "just" getting another field from an entity in a 3rd party API. That field is a reference.
Immediately I have questions like:
1. Do I get this in one call or several? If former, will this cause issues with the cache? If latter, will it decrease performance?
2. At what level do I want to do the filtering, at the query or higher level?
3. How will this affect existing calls, etc?
Breaking this down into questions is called "chunking" - grouping multi-parameter unknowns until they are simple. The problem is that if you can only keep 5 things in mind, you may outright miss questions to ask, or, at the very least, you will spend more time on a task than a person with a higher WM.
When I code, I always work on one thing for 60 - 90 minutes, nothing else so all working memory is dedicated to task at hand.
When I read (fiction or technical) or watch a lecture on YouTube, this is usually a dedicated 15 - 60 minute session. Once again, all working memory is dedicated to task at hand.
Working memory might be a problem for people who multitask, but I don't like to do that.