Google| Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
| From | Tony Cooper |
| Date | 04/25/2014 01:17 (04/24/2014 19:17) |
| Message-ID | <b72jl99i5lliv70m1g0crj70kdi7ev43cq@4ax.com> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Sandman |
| Followups | Tony Cooper (49m) Tony Cooper (51m) Sandman (6h & 55m) > Tony Cooper |
On 24 Apr 2014 21:35:39 GMT, Sandman <mr@sandman.net>wrote:
SandmanOf course it is. It is only a necessary condition *if* it's added as a necessary condition.
In article <tdeil95um201umu0qrn1t9vog2sblmdr32@4ax.com>, Tony Cooper wrote:SandmanTony CooperTony CooperSandman
Those requirements are put in there because you want to do whatever it is that the requirement provides.
A requirement doesn't provide anything, Andreas. It is something that is a necessary condition for something to occur.
Only once they are included. They have to be inserted as requirements for them to be a necessary condition for something to occur.
See what I mean about illiteracy? "inserted as requirements". A requirement is a necessary condition, not something you "want to do".
Try it. Plan a route to your dry cleaner. Write down the steps you need to take to arrive at that destination.
Now, add that you must stop by the pharmacy on your way. Consider it a requirement for the trip.
It's now there as a necessary requirement, but until you wanted to add it, it was not in the route. In other words, it's a requirement because you wanted it to be a requirement.
Developer? That's using someone else's system. What I was referring to, and it was clear at the time, is planning my own system of backing up my files. I may use a developer's system in that process, but I'm going to decide what files to back up and where they are to be backed up. In doing that, I'm deciding what the requirements are, and they are what I want them to be.Tony CooperSandman
I don't understand why you can't grasp that all requirements added to a system are there because someone wants them there. It's pretty simple.
And all requirements in a given system isn't always there because someone wants them there, either. The topic was backup at the time, and a developer
doesn't add the requirement of a backup disk being a requirement because he, the developer, wants a backup disk to be connected - it's just that the program can not fulfill its task without it. The developer doesn't sit around wanting backup disks to be connected. He wants to provide functionality to the user, and as it is a requirement for the user to use that functionality is to attach a backup disk.Well, let's examine your literacy.SandmanTony CooperTony CooperSandman
For example, the use of a password might be a requirement in a system of doing something. You only include that requirement if that is what you want to do.
Not at all. You want to use the system, you don't want to use a password. You don't sit down at the system with the purpose to use a password - using a password is a necessary condition you need to fulfill in order to gain access to do what you want to do.
I can't make heads or tails out of the above.
See what I mean about illiteracy?
Second sentence: "You want to use the system, you don't want to use a password." Two sentences, actually, joined incorrectly by a comma.
Third sentence, part 1: "You don't sit down at the system with the purpose to use a password..." Awkward, but one can muddle through the "with the purpose to use a password".
Third sentence, part 2: "...using a password is a necessary condition you need to fulfill in order to gain access to do what you want to do." Grammatically OK, but it's in response to a statement where putting in a password is a choice. The condition of needing a password has not been established.
So, in other words, you have not read and understood what you've responded to. That, according to you, is a sign of illiteracy.
I see what you've done. You've assumed, incorrectly, that my statement has to do with using a program that someone else has designed and I have no choice of what requirement there will be.
There are many instances where using a password is optional and making the requirement of using one is a choice.
What? Stupid claim? There are many program wherein the user decides if a password is to be use.Tony CooperSandman
What in the world does "You don't sit down at the system with the purpose to use a password" mean?
What part of it confuse you? You just made the stupid claim that you only include the requirement for a password if that's what you want to do.
No one "wants" to do that, but it's a needed step for added security. What one MAY want to do is have added security, and in most instances that adds the requirement of identification, which could be a password.Certainly is. My grandson's new laptop offered the choice. He could decide to require a password to access the system or decline to use a password. What is more of a choice of what "you want to do" than that?Tony CooperSandman
You show that you can't follow what is said when you write "a password is a necessary condition".
Ironic.Tony CooperSandman
In a system that is being planned - as I said above - the person planning the system decides if the use of a password is a necessary requirement.
No, he decides if he wants his system to have added security, and then he choose a method. He doesn't add passwords just because he wants passwords.
The developer wants to make a secure system, so he is required to add identification, and chooses password.
The user wants to use the program, and that requires to write his password. The user doesn't sit down wanting to write a password.Tony CooperSandman
It isn't about what someone else has planned. In this case, it is a requirement if you want it to be a requirement.
What it *isn't* is something "you want to do".
Only someone illiterate would say something like that.Thick as a plank. -- Tony Cooper - Orlando FL
04/14/2014-
