That’s why I sugest to include alternative solutions in the path description. While reviewing I also tinker in my head, to see if I can come up with something better. If the developer writes down what they already considered as an alternative and describe why they chose that particular solution from the alternatives, it makes my pondering to see if the approach is sound a lot easier.
We have a back-log of patches to review. My proposal is not aimed at making it easier to create a new patch. It is aimed at making the review process easier, more streamlined, and more straight-forward because the relevant information is proveded up-front.
I think that this is the result of having too much work for too few people. It is also one of the reasons I wrote this proposal: to make the reviewer require less brainpower to understand what the patch is about. To streamline the process by giving the relevant information in an easy-to-understand way, which I hope will help getting faster, higher quality reviews. Of course it’s not the only thing that can be improved, but I think it’s an easy one.
The focus of the development team at the Blender Institute is now 2 days per week on bugfixing, simply to get through the ever-growing pile of open bug reports. If you want to help, please jump onto the bug tracker and help fixing things. At this moment that’s much more important than to add yet another feature (note that this is not aimed at @EitanSomething in particular, just a general call for help).