I say there are problems that cost more to fix in code and there are problems that are cheap to fix in code. There are problems not worth fixing with telling p

I say there are problems that cost more to fix in code and there are problems that are cheap to fix in code. There are problems not worth fixing with telling people - if they fall in such ways we get support ticket and someone will explain to the user what just happens. If this happens too often only then we know it is becoming worth fixing. So for me article is wrong because author assumes there should be answer or solution for each and every problem. So 1st type of dev might be right a lot of times because how often does it happen that people deploy at the specific time? If it never happens in reality you just waste time solving it. On the other hand if it happens you will have to solve it then you might need action plan for it but … most likely you can just let people make mistakes and fix them on the spot.