Google| Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
| From | Sandman |
| Date | 04/29/2014 14:56 (04/29/2014 14:56) |
| Message-ID | <slrnllv8gq.be5.mr@irc.sandman.net> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Eric Stevens |
| Followups | Tony Cooper (1h & 13m) > Sandman Eric Stevens (14h) |
In article <ejsul995fdqlfedkgiklohabttvlha965d@4ax.com>, Eric Stevens wrote:
EXACTLY! He *needs* to submit a password, that need is not born from desire, it is born out of a requirement.SandmanEric StevensSandmanEric StevensSandmanEric Stevens
From then on persons B, C, D etc have to that specific thing.
Yes, and a very good example that shows that Tony used the word incorrectly, which was my point. A requirement is not what you want to do, which your example clearly shows.
It is if I am person A.
In your example, there were no requirements posed for person A, he's the one who added it, not the one subject to it.
Person A will have to use a password to log in, just like everyone else.
Not in your example, but even so, it's still the same.Desire - Person A want added security Requirement - Enable measure of identificationDesire - Person A want to use the computer Requirement - Submit password"A requirement is what you want to do" - Andreas SkitsnackIf that were true - the above would read:Desire - Person A want to submit a passwordEric Stevens
No it wouldn't. It would read 'Person A needs to submit a password'.
Andreas Skitsnack told me that a "requirement is what you want to do", but as you so correctly say, a requirement is what you NEED to do in order to proceed. Not what you WANT to do.
I love it when you argue with me just because Andreas is arguing with me and then it turns out you actually agree with me, since you can't really twist the world to fit Andreas' words.
-- Sandman[.net]
04/14/2014-
