…mplexity of the code, future-proofing you considered, and any optimizations you made or would make. You can also include a section explaining what you would have done if you had more time (maybe refactoring a specific section, adding more tests, or adding handling for another edge case).
This is such good advice!
This is such good advice! Like India (this may be where I learned it), I like to do a README that sums everything up, but I do leave comments within the code as well, where it makes sense. I always think of it as "don't assume the reviewers are as smart as you are! tell them where to look to see all your good work!"