|
I hate Windows/Visual Studio/MSXML today ...
I'd rather be phishing!
|
|
|
|
|
I take it the upgrade to 5.0 didn't go well?
I've got a 2nd generation Nexus 7, and the update seemed to work okay.
Software Zen: delete this;
|
|
|
|
|
OriginalGriff wrote: Everything has been difficult: the cabling (short fast-charge cable that comes with Nexus 7 pulls too much power from USB, and disables my PC keyboard,
Trying to use a hub? I know a lot of cheap ones assume you'll never plug enough high current devices in to theoretically max out all the ports at once and gleefully agree to all "I can haz moar powar" requests without actually making sure they can provide it.
If you're running directly plugged into a PC though; that's more worrying. A desktop shouldn't have any problem providing as much power as it negotiates to an arbitrary number of devices at once. It's not like anything else on your mobo is drawing power from any of the five +5V wires in the atx cable (or that much of anything is drawing on the ~100W of +5V your PSU can provide for that matter). It might be worth putting the tablet in a separate pair of ports though; I'm not sure if anything is shared between a pair of ports, but the way they're always bundled together makes it slightly possible I guess.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
The President's coming to inspect our secret project and we spent all the funding on vodka and video games. We better come up with something quick[^]
It was broke, so I fixed it.
|
|
|
|
|
What about a secret project of "drinking vodka and playing videos game". It is a secret afterall, so expose it in anyway you want it to be.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
One can not simply satisfy the president...
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
This is not the droid I'm looking for.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
No threat to Sarah Connor yet. They should call it terminater.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
As part of my future article, I would like to put forth the question, just to gauge the understanding
Can you please describe in a line for the meaning of Requirments and Specification from your personl experience?
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Requirements are the "what" and Specification is the "how".
|
|
|
|
|
Precisely.
/ravi
|
|
|
|
|
I agree
NKS
|
|
|
|
|
Requirements are the "WHY" and Specification is the "WHERE".
|
|
|
|
|
Are you talking about hiding the body?
|
|
|
|
|
While the first answer is a precise and a great summation of the difference I would like to add, that requirements come from the client. Specification however is created by the developer while developing the solution according to the requirements.
|
|
|
|
|
"requirements come from the client" - sounds like you have a great client, sometimes you have to guess at what they want
|
|
|
|
|
Ha, yes you are right, I should have added - if you are lucky or perhaps requirements are made up by the project manager/director. The latter is true if you are not so lucky.
|
|
|
|
|
Requirements = Hilarity.
Specification = Impossibility.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
super wrote: personl
He asked, he told ...
"If you're about to post something you wouldn't want your kid sister to read then don't post it."
|
|
|
|
|
|
For the Dilbert question: the answer is yes.
|
|
|
|
|
To me, requirements are the wish list. Specifications are what is going to be delivered.
www.davidmkelly.net
Character-based SF and more...
|
|
|
|
|
The requirements is what the software ought to do. The specification is the documented misunderstanding of the requirements.
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
|
|
|
|
|
What and how?
Requirements have 2 attributes:
1. They are statements of form, fit, and/or function.
2. They are testable (by inspection, test, etc.)
Specifications are documents. They collect the known and derived requirements. In a formal environment, there may be documents addressing software requirements, hardware requirements, and / or operation requirements. Specifications contribute (as a precursor) to test plans, procedures, and reports.
As a former system's engineer, I have not seen a 'specification' that describes 'how'.
|
|
|
|
|
Actually, they're one in the same thing:
DELUSIONS
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "As far as we know, our computer has never had an undetected error." - Weisert | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|