In modern development, it is very easy and powerful to get into immediate feedback loops. Write a little bit of code, compile or equivalent, evaluate or fix errors, repeat.
But I think there is something to be said for breaking out of that loop every once in a while. To build something from start to some amount of finished without the constant helpful distractions of seeing whether the current inbetween state is even runnable. I just spent a large part of my work day adding a feature to a code base I am unfamiliar with. For most of the time, I was not even trying to run the code. I was reading, thinking about how the feature should work and where it should be, making changes and thinking about how they might interact with their surroundings.
On more familiar ground, I would have been constantly reloading, clicking around to find good data to test with, running into lots of intermediate errors, and of course spent time waiting for rebuilds getting distracted by other things.
I still got plenty distracted of course - I am still human - but I do feel I succeeded in better reasoning about my problems and the small amount of architecture involved rather than blindly trying things and running off on side tracks of premature polish. Helpful tools draw attention too, especially when they try to be helpful just because you hit save midway through a thought.