Stop writing, start cleaning up what you've written. Then, after a while of cleaning up the solution will fall out of the sky all by itself.
What has happened is that you have lost the overview, cleaning up your code will restore that.
What has happened is that you have lost the overview, cleaning up your code will restore that.
Sometimes it's good to walk away, as in literally take a walk and utterly ignore all your problems, and sometimes it's good to chip away, as in doing one little easy thing that's within your immediate power, however meaningless it might seem. I find that such small efforts produce a sort of "compound interest" effect, where your gains start to pile up faster than you expect.
I'm going to give this a go. Thanks.
If your overall vision is too solidified in your head, there may be some minor decisions that were a good idea at the time ("well if we're already doing X, it's easy to also give them Y!"), but now that you're down in the muck they are complicating things far more than you imagined.
Sometimes you can just drop a few things you actually don't need (but have become fixed in your vision though habit), ...and dependencies start collapsing, and the whole thing takes on a new shape.
Also: don't overlook temporary solutions.
You can often fix a dependency with a cheap hack that obviously won't scale in the long run... but it gets you over the hump, and you'll be able to replace it with the real solution down the road.