Comment Obligatory (Score 1) 145
Sorry, no one else killed their karma with this one, so I felt compelled to do so:
There was only one IP involved in the edits, apparently it was 127.0.0.1
Sorry, no one else killed their karma with this one, so I felt compelled to do so:
There was only one IP involved in the edits, apparently it was 127.0.0.1
"10,000! We could almost buy our own ship for that!" "Yeah, but who's going to fly it kid? You?"
Typical Management Response:
"You bet I could!, I'm not such a bad programmer myself!"
Or as Benjamin Franklin said, "Some people are penny-wise, but pound foolish." You try to save pennies and waste pounds/dollars instead.
The same can be true in programming, but usually the scenario describes development itself, i.e. premature optimization. If your team is experienced, the only reason for this would be people trying to do big things in small spaces.
I think it comes down to what you need, what you want and what you need to spec for your software to actually run.
If your willing to spend quite a bit of money on some really talented people, what you need as far as hardware (at least memory) can be reduced significantly.
What you want is to roll a successful project in xx months and bring it to market, so raising the hardware bar seems sensible.
Then we come down to what you can actually spec, as far as requirements for your clients who want to use your software. Microsoft ended up lowering the bar for Vista in order to appease Intel and HP
If your market is pure enterprise, go ahead and tell the programmers that 4GB/Newer dual core CPU is the minimum spec for your stuff. If your market is desktop users
I don't think there's a general rule or 'almost always' when contemplating this kind of thing.
Elvis has left the building
Elvis has left the building
And the other Elvis has left the building
There, fixed that for you.
Cheers!
Strat
Well, sort of
"For more than six months, beginning in January of this year, Wikipedia's million-dollar check book was balanced by a convicted felon. When Carolyn Bothwell Doran was hired as the Chief Operating Officer (COO) of the Florida-based Wikimedia Foundation, she had a criminal record in three other states — Virginia, Maryland, and Texas — and she was still on parole for a DUI (driving under the influence of alcohol) hit and run that resulted in a fatality. Her record also included convictions for passing bad checks, theft, petty larceny, additional DUIs, and unlawfully wounding her boyfriend with a gun shot to the chest."
The moon is made of green cheese. -- John Heywood