You know what annoys me, and I'm probably alone on this, is that when I write a programme which calls and writes to multiple files/directories, I suggest that the safest and most reliable method is to have the contractor give me shell access to the box to install it. A good number get so paranoid they won't. I mean, wtf am I going to do? I just wrote file after file of code for them, where I could have slipped in a backdoor/exploit which you would never find if I really wanted access to the box. But no, oh no. They want an installer script. An installer script takes a huge amount of time as it has to take into account endless possibilites for installation fuckup.
I do the installer scripts, but it *really* pisses me off, and takes a huge amount of work (the bigger the script, the longer the installer script).
Just give your programmer access to the box - he/she know's their programme/script - they know how it should be installed.
</rant out>
--edit to clarify, this pet peave does not stem from AW in the slightest. Just thought I'd let you all aware...
__________________
For coding work - hit me up on andy // borkedcoder // com
(consider figuring out the email as test #1)
All models are wrong, but some are useful. George E.P. Box. p202
|