For some inexplicable reason, I am going to start writing about my experiences with Geocaching puzzle caches. Fortunately, noone reads this so I am not really all the concerned about spoilers. Still, I don't intend to offer spoilers but that can imagine that there will be some .
Part of what I think I will be writing about will be puzzle construction and execution hoping to give insight as to what I think is good or a bad what to construct a puzzle. I will probably disassemble one or two of my own as examples which will certainly be spoilers.
I will be posting links to tools I created or tools I use to solve puzzles. I will describe how I used them or how they can be used. This will likely provide some hints to solving puzzles but i will probably leave the details of the specific cache out.
Only added one of my perl tools that tests a number by performing a sequential multiplication with it to see if it matches a specific set of matching criteria.
Right now that criteria is hard coded for the test number. It looks for the result of multiplying the input against an incrementing number starting at one and hard coded to end at 10000. It is very fast. It looks for any result that has both 371 and 1215 in it. If so, it prints a hit, the coordinates translated from the result and the actual result. There could be more than one hit so you have to figure out what couldbe the right one.
I will add two more fields the two matching numbers. I may add a user defined min/max range so that can limit the search.
I have several more math calculation perl apps to enable. The next one will have three buliltin procedures to calculate certain mathmatical numbers to the nth place. Like pi to the 1000th place. Doing it in perl is REALLY fast. If i have to execute it at the shell, it takes much longer. I may even try my hand at javascript!
. 
del.icio.us