Re:Grace Hopper to Programmers: Mind Your Nanoseconds
by maligree on Saturday January 12, 2013 @06:07AM
(#5047445)
Rant inspired by seeing her for the 5th time this week:
It's like every time I hear about Grace Hopper, it's got to do with a piece of wire. Or tube. And any comments on it are usually strangely excited, almost awestruck. What's up, people? She did some other stuff too. Like, no big deal back then, writing a god damn compiler.
It's like people treat her like a dancing bear. Look, woman! Look, uniform! Look, she said "nano"! Take a step back and a deep breath. Chill out.
Re:Grace Hopper to Programmers: Mind Your Nanoseconds
by meaty on Saturday January 12, 2013 @09:02AM
(#5047778)
until you get to the end game and you realise you have a lemon on your hands which is going to require a rewrite because it's so slow when you throw 10,000 users at it...
"Be mindful" is probably better advice. Tradeoffs are easier to make earlier on and everything is a compromise after all.
Re:Grace Hopper to Programmers: Mind Your Nanoseconds
by DanWaterworth on Saturday January 12, 2013 @10:04AM
(#5047909)
What I said was:
> When programmers care about lack of efficiency before it's a problem, they're doing it wrong.
That doesn't mean that you shouldn't identify problems as quickly as possible, just don't try to improve performance when you haven't got a problem in front of you.
Re:Grace Hopper to Programmers: Mind Your Nanoseconds
by bennyg on Saturday January 12, 2013 @01:10AM
(#5046719)
And it's the first time I've seen it. What exactly is the point of the negativity? If it's annoying to the community as a whole, it won't be voted up. If it isn't, and you don't like it, you're wasting energy by clicking and commenting sarcastically.
It's like every time I hear about Grace Hopper, it's got to do with a piece of wire. Or tube. And any comments on it are usually strangely excited, almost awestruck. What's up, people? She did some other stuff too. Like, no big deal back then, writing a god damn compiler.
It's like people treat her like a dancing bear. Look, woman! Look, uniform! Look, she said "nano"! Take a step back and a deep breath. Chill out.
"Bike shed" comes to mind, in a weird way.
> Programs must be written for people to read, and only incidentally for machines to execute.
When programmers care about lack of efficiency before it's a problem, they're doing it wrong.
"Be mindful" is probably better advice. Tradeoffs are easier to make earlier on and everything is a compromise after all.
> When programmers care about lack of efficiency before it's a problem, they're doing it wrong.
That doesn't mean that you shouldn't identify problems as quickly as possible, just don't try to improve performance when you haven't got a problem in front of you.
I sure hope someone posts the Letterman interview with her next, so I can see that to the nth as well.