Hardware Is Cheap, Programmers Are Expensive 465
Sportsqs points out a story at Coding Horror which begins:
"Given the rapid advance of Moore's Law, when does it make sense to throw hardware at a programming problem? As a general rule, I'd say almost always. Consider the average programmer salary here in the US. You probably have several of these programmer guys or gals on staff. I can't speak to how much your servers may cost, or how many of them you may need. Or, maybe you don't need any — perhaps all your code executes on your users' hardware, which is an entirely different scenario. Obviously, situations vary. But even the most rudimentary math will tell you that it'd take a massive hardware outlay to equal the yearly costs of even a modest five person programming team."
Re:But who's going to fly it? (Score:5, Funny)
Typical Management Response:
"You bet I could!, I'm not such a bad programmer myself!"
Re:Timing is everything (Score:3, Funny)
Re:Timing is everything (Score:3, Funny)
Yeh but you have to appreciate where all this enormous amount of hardware, enormous amount of hardware goes. It doesnt just come on a truck you can dump things on, it has to come via a series of tubes. Oh... Wait.
Re:Frist? (Score:5, Funny)
"Natalie Portman can't act for shit and she has the tits of an 11-year old girl. Grits are bland and best served to the inbred, down-syndrome-afflicted inhabitants of the Southern United States."
OK, OK, ya got me horny, hungry, and nostalgic for the folks back home, but what was your point?
This only works with LAMP/FOSS (Score:3, Funny)
If your performance problem is in an Oracle or SQL Server database, throwing more hardware at the problem probably has a license fee attached to it, and that can easily be measured in multiple developer salaries. This also causes people to scale using bigger boxes, rather than more boxes, and that gets you out of the range of commodity hardware and into the land of $$$$$.
Which is why I don't care to deliver on Oracle, but my employer hasn't figured out that Postgres and MySQL will work for a lot of problems, and is still fellating the Oracle and IBM reps.
Re:I agree. (Score:3, Funny)
Engineers are billed at about $90 an hour. That includes wages, health benefits, rental for the cubicle space, and heating.
Re:Assuming of course hardware is the bottleneck (Score:4, Funny)
I remember being subject to a class called Data Structures & Algorithms ...
Yes, I believe Nicholas Wirth taught that one. Supposedly when you've added the Data Structures to the Algorithms, you get Programs or something.
Re:But first: Profile, Analyze, Understand (Score:2, Funny)
Of course, in my line of work the goal is to go from "a million years" to "realtime" so all the hardware in the world isn't really going to help much.
Here's a free pro-tip for you: Just find and use some really small years, and you should be able to solve your problem.
First Java Post? (Score:5, Funny)
Who will be the first to post "ICodeInJavaWithClassesWithReallyReallyReallyLongNames.youIgnorantClod();" ?
Re:Another u.s. specific problem. cost of living (Score:3, Funny)
extremism is bad at EVERYthing.
See? You used the shift key. That wasn't so hard, now, was it?
Re:Recalculate for the crisis (Score:3, Funny)
I will send you $20 bucks if you post a photo of yourself holding a sign that says "A non-white immigrant paid me $20 to hold this sign."
Re:Timing is everything (Score:3, Funny)
Re:programmers save lifetimes (Score:5, Funny)
Someone evil (like me) may ponder the other side of that. If I can *put* another 5 seconds on the boot time then I can effectively kill 50 people and get away with it. But then I'm a bastard.
Re:First Java Post? (Score:5, Funny)
std::i_code_in_cpp_with_crptc_cls_names::you_insns_clod();
Re:Timing is everything (Score:2, Funny)
But if he's blind he might crash and not finish at all :(
Re:I agree. (Score:3, Funny)
Uhh, you can't "throw hardware" at a hardware design. In the HW manufacturing case, you WANT to spend money on the upfront design to reduce the parts cost.
If your design forced to use 1% resistors instead of 2%, you'd better have been building a medical device or something else with tightly regulated specifications. Otherwise, when your boss says to use 2% or 5%, tell him to loosen the specs. Otherwise you're just over-engineering.