I got a job as a junior developer for the summer, in which they gave me an actual project which I was really happy about. Basically, I've made an app for Android and iOS in C#/Xamarin for their customers who already have the desktop version (it's not a replacement, but it does about 80% of what their 10 year old desktop software does, so I'm proud haha)

I've learned a lot and want to come back next summer, so because of that I want to leave on the best terms.

I don't want to leave my code in a way that makes the next person (who will probably be the one I interviewed with and trained me) have to redo everything. It won't ever be perfect, I know that, but I want to have him take over and have him think "this could have been written to do that" (AKA understand it) instead of go "wtf what does this do?" (Not understand my code or have to really dig deep and figure it out).

If this was school I would do this by commenting every single method (that isn't blatantly obvious). However, the guys here do not comment their code, they have the philosophy of "if you had to comment it, you didn't write it readable enough to begin with".

I've coded everything with dependency injection in mind, MVVC architecture, and followed their naming premise of everything having longer names that explain what they are.

So ignoring commenting, what else do I need to do to make sure I leave my code in the best order for the next guy?