You and the other dev need to sit down together and work out a development process that works for the two of you, and stick with it. And put that process in writing. That process should address the flaws in the way you are doing the work now. Management doesn't have to be involved (or even aware) of this.
Maybe start with developing the minimum requirements for a work unit to be considered "complete" and incorporated into the product. Documentation should be one of those requirements.
Basically, you're a team (of two, but a team nonetheless) and need to be on the same page. Get on that page.
Comments
No, but it's not as rare as it should be.
You and the other dev need to sit down together and work out a development process that works for the two of you, and stick with it. And put that process in writing. That process should address the flaws in the way you are doing the work now. Management doesn't have to be involved (or even aware) of this.
Maybe start with developing the minimum requirements for a work unit to be considered "complete" and incorporated into the product. Documentation should be one of those requirements.
Basically, you're a team (of two, but a team nonetheless) and need to be on the same page. Get on that page.