coox
Jan 30th, 2001, 03:57 AM
Morning chaps.
Okay, I've written an app for the company, and now been given the fabulous task of writing a technical descripripripription (or something) of it. It's for when I win the lottery and tell the company to go to hell, and then some other schmo has to figure out what my coded ramblings are all about.
So, my question, to you, as members of the human race, is - what would you chaps like the guy before you to have included in the technical description that he did very hastily and wasn't really concentrating on that is currently making your life hell and causing you great stress at home and elsewhere? Sortafing?
In a nutshell - what should a tech. desc. contain?
Okay, I've written an app for the company, and now been given the fabulous task of writing a technical descripripripription (or something) of it. It's for when I win the lottery and tell the company to go to hell, and then some other schmo has to figure out what my coded ramblings are all about.
So, my question, to you, as members of the human race, is - what would you chaps like the guy before you to have included in the technical description that he did very hastily and wasn't really concentrating on that is currently making your life hell and causing you great stress at home and elsewhere? Sortafing?
In a nutshell - what should a tech. desc. contain?