P
Patrick Tingen
Guest
I try to convince my fellow developers here as well that they should follow the rules Gus mentioned, but some folks simply cannot understand that I have difficulty grasping what a procedure does when it is named "orders". I do believe that a good naming convention enforces better code quality. If you have a procedure that collects orders, recalculates discounts and then exports them to whatever, how on earth are you going to come up with a decent name for that. The answer is: you don't. You end up with a name like "orders". But in fact it tells you that your code block is way too large and that you should have split it up in at least 3 subprocedures: collectOrders, recalculateDiscounts and exportOrders.
Continue reading...
Continue reading...