Nay Co ~ . _~ --by Gregg W. Taylor Dallas, Texas ~AKING CODE READABLE, AS understandable and main- tainable as possible has been the thrust of my efforts since becoming a consultant. T r u l y nasty code is what I try to remedy. But in t_his article I'm going to look at how to make code look as bad as possible. Any security scheme that truly works will keep out the most devious and persistent interlopers. Anticipating someone else's methods o f intruding into a secured area (or bit of code) is probably best handled by someone who is a little devious himself. Being a rather naive person, I have always shied away from such systems, feeling rather inept to do an adequate job. I was therefore somewhat amused when a client recently asked me to secure some APL code against tampering. T h e task was to do whatever I wanted to the code, so long as it still functioned the same way and was not locked. I was essentially to make the code as unreadable as possible! This turned out to be one of those fun projects that comes around every once in a
/lp/association-for-computing-machinery/nasty-code-cfEchN6kbl