I've been struggling with something similar, although I think that in my case it's tunnel vision and the impostor syndrome. I often get completely lost in the

I've been struggling with something similar, although I think that in my case it's tunnel vision and the impostor syndrome. I often get completely lost in the minute details, and find it really, I mean, really hard to move on to more important things in the bigger picture. Then, just getting stuff out and sharing it with people becomes a chore as soon as I'm done with the more difficult parts of work. Things I've tried: - follow TDD and XP, Design Thinking/HCD (iterative methodologies that allow you to slice problems differently, split them into smaller chunks) - Build smaller products/tools (most of my apps are really, really tiny, an old example: http://facade.photo http://facade.photo) - Build a tool to separate writing from editing (https://sonnet.io/posts/ulysses/)-I've https://sonnet.io/posts/ulysses/)-I've been using it every day for the past 1.5y - Force taking regular breaks, even if I'm focused, to regain context (pomodoro) - therapy (I got to the point where building a calculator in JS took me a week, which made me realise that maybe there are some deeper problems at play here) I was at the point where I would run courses on having this high-level perspective: XP, pairing, workshops on Human Centred Design, and ironically, I find all of that paralysing in my solo work. So, I guess the last point from the list (therapy, taking time off) seems to be the most helpful one. I still find all of that extremely frustrating, almost destructive. Side note: either Clean Coder or Pragmatic Programmer criticises being "in the zone"/the state of flow precisely for the reason you've mentioned. I recommend reading both, although I think the approach to the craft they describe is to put it mildly, draconian.