Earlier quoted context omitted.
It may be a common trait in programmers, since we're rewarded by getting to the bottom of things: "why is this function failing? who calls it? in which possible states?" Most programmers have experienced being so immersed in code that we don't notice time is passing, forgetting to eat or sleep. It's similar with immersion in social media / food / whatever. We become lost in the activity and lose our sense of self. I'…
I identify with all of this, but this: > to make pauses, take a deep breath and think about "what am I doing right now? What should I be doing instead?". this too can have its pitfalls. In my case, I always feel like I have BOTH too many things that I WANT to do and too many things HAVE to do and whenever I step back and try to look at the bigger picture, I realize that I don't feel like I'm making tangible progress…
As much as I know I should prioritize it based on urgency, highest impact, what I could delegate etc., if the willpower required to do that is more than the ramifications or not doing it, it can be a losing battle.
On days when I push through a ton of work, I'm energized at the end of the day. Compared to the feeling of guilt that I just wasted a day when there's so much to do and I achieved little. Yet knowing that still just doesn't provide the necessary motivation some days. I've yet to figure out a reliable solution for it.