|
Quote: Your password should contain at least 6 characters
If you're going to require it; don't say "should", say "must". 
|
|
|
|
|
I should be home after 3 pints....
|
|
|
|
|
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.
|
|
|
|
|
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...
|
|
|
|
|
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?
|
|
|
|
|
No, but if you do, would you pick one up for me as well?
hatfok
King Yiddum's Castle
Pegasus Galaxy
|
|
|
|
|
WiganLatics wrote: Do I need to buy a sarcasm sign?
Yes, you really should
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Teal'c says "Indeed"!
hatfok
King Yiddum's Castle
Pegasus Galaxy
|
|
|
|
|
Dang they done must it up!
New version: WinHeist Version Tequila, the nigh time, snuffly, sneezing, how the hell did I end up on the bathroom floor medicine.
|
|
|
|
|
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. 
|
|
|
|
|
Exactly. That's why I loved my Atari 800XL. I didn't even know about passwords at that time. 
|
|
|
|
|
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...
|
|
|
|
|
If it says "should" then it is not optional, like in "could".
You should be "this tall" to ride this ride.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
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.
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.
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.
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..
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
No assigngment must be finished.
|
|
|
|
|
|
It must be finished as a prerequisite for getting top marks. But if you don't desire top marks then it needn't be finished.
|
|
|
|
|
In most cases, 'should' gives you some wiggle room. For DOD purposes, 'shall' means absolutely must be, required to be.
|
|
|
|
|
James Lonero wrote: In most cases, 'should' gives you some wiggle room. So, more a very strong recommendation. Something like "all variable names should have a meaningfull name", and "code comments should be not stating the obvious".
James Lonero wrote: For DOD purposes, 'shall' means absolutely must be, required to be. Good thing I don't work there then. We shall die, the rest is uncertain and open to discussion
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
When I was in MoSCoW[^], they said:
Must: Absolutely necessary,
Should: Important but not necessary,
Could: Desirable but not necessary,
Won't: Not appropriate for now.
|
|
|
|
|
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
|
|
|
|