Doesn't "should" mean it's not required?
-
All the 'should haves' happened in a perfect parallel universe. Be brave, stay classy, stay true to this universe, enter less than 6 characters (also try special characters and Chinese unicode or just empty password). :-\
I always enjoyed being an OpenVMS System Manager because I could ignore all the password requirements and make my password whatever I wanted. :cool:
-
I always enjoyed being an OpenVMS System Manager because I could ignore all the password requirements and make my password whatever I wanted. :cool:
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
You should use must when you really, really want something. Or should it be: You must use must when you really, really want something. Or must it be? Should be or not should be. That should be the question. Just use the word 'should' as your password. It has six characters.
Kitty at my foot and I waAAAant to touch it...
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
When writing specifications, the customary usage is: MUST: mandatory SHOULD: highly recommended, but not mandatory MAY: optional SHOULD NOT: highly discouraged, but not prohibited MUST NOT: prohibited When speaking to non-engineers, "should" is often taken to mean "must".
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
Eddy Vluggen wrote:
You should be "this tall" to ride this ride.
In English, that's almost always written as "You must be ..." to avoid precisely this problem. ;P
Inicates that ... the speaker has some strong advice but has no authority to enforce it.
Indicates that the sentence subject is required as an imperative or directive to execute the sentence predicate.
RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels[^]:
MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Eddy Vluggen wrote:
You should be "this tall" to ride this ride.
In English, that's almost always written as "You must be ..." to avoid precisely this problem. ;P
Inicates that ... the speaker has some strong advice but has no authority to enforce it.
Indicates that the sentence subject is required as an imperative or directive to execute the sentence predicate.
RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels[^]:
MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
In English, that's almost always written as "You must be ..." to avoid precisely this problem. ;-P
It is probably not up for negotiation. Even if it says "you oughta be".
Richard Deeming wrote:
SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item
RFC or not, the word "must" will also have valid reasons to ignore a particular item. Unless we are talking about unsigned numbers, there are no absolutes. See the forum where code is "urgent" and "must" be finished by the next day. I should ignore those messages, must not redicule them. If I only could.. :rolleyes:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
Richard Deeming wrote:
In English, that's almost always written as "You must be ..." to avoid precisely this problem. ;-P
It is probably not up for negotiation. Even if it says "you oughta be".
Richard Deeming wrote:
SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item
RFC or not, the word "must" will also have valid reasons to ignore a particular item. Unless we are talking about unsigned numbers, there are no absolutes. See the forum where code is "urgent" and "must" be finished by the next day. I should ignore those messages, must not redicule them. If I only could.. :rolleyes:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
No assigngment must be finished.
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
Insanity notwithstanding ... * Should should be reserved for project stretch targets. * Must must be used only in brewing. * Shall, shall be used in the case of compulsory requirements. * Will will only be used in the case of death
-
No assigngment must be finished.
-
Your password should contain at least 6 characters, otherwise it won't be accepted. However, you CAN type a shorter password, it's just that it'll be rejected. ;P
From the requirements document: "The password entered by the user should be rejected if it does not contain at least six characters." If I received that requirement from my boss, I would make darn sure that the password is rejected. I don't think I would randomly reject some and not others. How about "You shouldn't break the speed limit"? Now, if you were being chased by a tyrannosaurus rex, I think the judge would (should?) let you off the hook.
hatfok King Yiddum's Castle Pegasus Galaxy
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
SHame + cOULD = SHOULD Could says there is a choice to be made and is an element of should. Shame on those who don't follow the implied directive is an element of should. Should is one of the most stress-inducing words in the English lexicon and absolutely... ...ought not be used in message boxes, forms or web pages. IMNSHO :)
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
From the requirements document: "The password entered by the user should be rejected if it does not contain at least six characters." If I received that requirement from my boss, I would make darn sure that the password is rejected. I don't think I would randomly reject some and not others. How about "You shouldn't break the speed limit"? Now, if you were being chased by a tyrannosaurus rex, I think the judge would (should?) let you off the hook.
hatfok King Yiddum's Castle Pegasus Galaxy
If I receive a requirement document from the boss, I just do what I want. It usually has an "optional requirements" section...
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
I think it is just local interpretation. I used to work with a guy who thought if a sentence contained the word "are" that it was then a question. "Are you going to do that?" "Where are you?" He didn't have an audible response when I said. "You are out of your mind." So maybe in the writer's local culture, saying "should" implied "have to".
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
-
If I receive a requirement document from the boss, I just do what I want. It usually has an "optional requirements" section...
Well then, what exactly do you do when they are not in the "optional" section? Please enlighten us! I'll check, but I'm sure I did not mention optional requirements.
hatfok King Yiddum's Castle Pegasus Galaxy
-
Well then, what exactly do you do when they are not in the "optional" section? Please enlighten us! I'll check, but I'm sure I did not mention optional requirements.
hatfok King Yiddum's Castle Pegasus Galaxy
Do I need to buy a sarcasm sign?
-
Do I need to buy a sarcasm sign?
No, but if you do, would you pick one up for me as well? :)
hatfok King Yiddum's Castle Pegasus Galaxy
-
Quote:
Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". :mad:
As used in many standards documents, "should" means, "This is a best practice. You're an idiot if you don't." It is the concensus advice of the standard-writers who are usually very experienced people. It is the behavior of a very junior, very unimformed person not to treat "should" advice in a standards document as "do it". But hey, knock yourself out, do a half-assed job. That's the way to impress your boss and your customers. I think there are people who are still rebelling against "should" advice in standards documents because they hated hearing their mom tell them what they "should" do. Chances are mom was right too.
