I constantly find myself battling between getting it done taking the time to design reusable code my big struggle is ready in 10 times as much code to get something done to make it reusable but if I just make a specific code to get the task done. it’s a game of predicted volume volume and objects being reused or something being specific. The catch is we don’t always know when something that we think a specific will end up being reused over and over again in many different locations
where is the human sign take a work order for work order has a status whenever the status is Marc done certain checks should be perform. but not in all cases cases can be defined as situations or in human trans screens. For example a certain user even Adman will use certain screens to do different tasks quality assurance take tests in the screens they use won’t be the same screen said end-user would use. for example a certain user even admin will use certain screens to do different tests quality assurance take tests in the screens they use won’t be the same screen said end user reviews One could say that hey this is robust and there an admin it doesn’t matter what screen the run will let certain privileges for requirements slide based on rolls. One could say that hey this is robust and there an admin it doesn’t matter what screen they’re on will let certain privileges or requirements slide based on roles but sometimes it is a functional thing meaning when I change status to dispatched from a work order details screen it’s important that a pop-up shows a form or we can notify the dispatcher. But if I’m in resource management if you watch is a bulk editing tool is no way we ever want to see a pop up when we change the status to dispatched unless nothing to do with the role but rather the screen or the purpose of the screen at the rack. So to make dry code in that situation instead of it being role-based it’s almost purpose-based meeting with Passant another parameter to the validator that is the screen. so to make dry code and that situation instead of it being rolled based it’s almost purpose based meeting with Passant another perimeter to the validator is the screen
