FWIW, I felt the same way transitioning to working within a software development team coming from a world in which my work was done much less tracked while still in progress, however I eventually realized that 1. typically no one is watching because they are aware of the structure of the workflow and that doing so would be inefficient, and that 2. when they do, there's little reason to be shy about it since anyone paying attention understands it's a draft and all that encompasses.
Maybe consider labeling the files that are in progress as such?
I've now gone fully the other direction and will open draft pull requests as soon as I start committing code, knowing that I have nothing to lose from doing so and often end up being saved time and with a better finished product sooner when someone whose intuition probably told them to peek at this particular piece of work for a reason.
TL;DR - You can get used to this and even grow to prefer it. That said, design is not engineering and I may simply have Stockholm Syndrome.
Maybe consider labeling the files that are in progress as such?
I've now gone fully the other direction and will open draft pull requests as soon as I start committing code, knowing that I have nothing to lose from doing so and often end up being saved time and with a better finished product sooner when someone whose intuition probably told them to peek at this particular piece of work for a reason.
TL;DR - You can get used to this and even grow to prefer it. That said, design is not engineering and I may simply have Stockholm Syndrome.