My key looked worn so i had a new one made. Why did that not fix my problem?
Hardly a day goes by that I don’t hear the following statement. “There’s nothing wrong with my key, it’s brand new.” It is a common response When I suggest that a new key, CODE cut to factory specifications might be all that is necessary to solve a lock problem. There is a world of difference between a brand new COPY of a worn out key and a brand new key. Consider for a moment a printed document. Let’s say it is a desert recipe. It is a few years old and has several stains from being splashed with liquids. A few of the quantities are smeared, making it impossible to tell if it calls for 2 teaspoons or 3 Tablespoons of grated orange peel. Will making a photocopy of the recipe solve this problem? Of course not! The copy will appear to be in better condition. A nice fresh piece of paper, no wrinkles or curled up corners, but you will not be able to read the specified amount of orange peel any better than on the original recipe. The same holds true for a duplicate copy of a worn out key. I
- Our concrete driveway has sunken near house, and water now ponds there. Is there any way to fix the problem without removing and replacing the driveway?
- Im trying to use heapify to fix the problem in the binary heap caused by decreasing a key, but there seems to be a problem?
- My key looked worn so i had a new one made. Why did that not fix my problem?