I would suggest including in your PR a clear design statement that summarises (briefly) why you coded the solution the way you did. I always used to 'demand' t

I would suggest including in your PR a clear design statement that summarises (briefly) why you coded the solution the way you did. I always used to 'demand' that of my juniors otherwise there was no way of knowing if they'd just opted for the simplest and not most performant solution