[chris11]

> I suspect a lot of your issues could be solved by talking to someone before you start coding to make sure your approach is valid.

I'm not sure what kind of incorrect assumptions you are getting. But one thing that could signal you should ask about your approach is working in another team's codebase. Some of your problem could be making a technically valid choice that doesn't align with the codebase. Working on unfamiliar code can cause this.

Personally I had a previous job where I got into a few longer discussion about my approach after submitting a couple PRs with another team's tech lead. I was able to be more productive by talking with that lead about my task before starting the coding.