Engineer/Dev will come to me on a regular basis to "use framework X", that code is module Y is shit because and there is a more optimal version of the algorithm

Engineer/Dev will come to me on a regular basis to "use framework X", that code is module Y is shit because and there is a more optimal version of the algorithm. Most of the time, there is not objective reason other than "I have used that before and I liked it", "micro-benchmark say so, but I have not looked in this case if there is any interest for us". Client want our application to produce an incorrect file, having forgotten that some bloke in their department is correcting by hand all the incorrect file of the old application. Manager want you to do a daily timesheet to properly track client billing despite the fact that your team is working full time for a single client. Client/Manager/Other Developer regularly ask for rubbish reason all the time, why would the Designer be any different ? They may have a good reason this time, just spend 2 min to explain them.