Keystones

It’s amazing how after a lot of careful planning and work, the final lines of code that tie together a bunch of complex systems can be so simple.

If you do your work ahead of time, it almost comes out human readable. Having just tied together several systems that were supposedly not able to work together, can you guess what I am doing:

     unless ( &authorized($user) ) {
       $rec{username} = '********';
       $rec{password} = '********';
     }

9 Responses to “Keystones”

  1. gavyn_lumier says:

    What language is that?

  2. gavyn_lumier says:

    Erg… no wonder I didn’t recognize it. They didn’t do any Perl in college. We only really did C, C#, C++, Java, Ada (that wasn’t much fun), COBOL, VB, SQL, and .NET ASP.

    As to the question you pose, I’m going to talk out of my butt and assume you’re placing a universal security method in the code of each system so the login is standardized across the board.

  3. drleo says:

    Blanking out the username and password fields from users not authorized to see them, apparently.

  4. icywolfy says:

    Ah perl, is there anything it can’t glue together?

  5. krin_o_o_ says:

    Palestine and Israel?

  6. icywolfy says:

    Just because you can use Perl to glue things to work together — doesn’t mean that the two sides will work well together.

  7. krin_o_o_ says:

    Well… as a pundit would say “For certain values of work”.

  8. icywolfy says:

    I much prefer the “2 + 2 = 5; for extremely large values of 2”

Leave a Response