|
Des Ward wrote: 95% of all code has practically zero impact on ultimate code performance
Source? 
|
|
|
|
|
30+ years of experience
Cheers, Des
P.S. All your pie are belong to us
|
|
|
|
|
Get all my patterns, objects/data structures and algorithms in place.
I then profile to see when the code is getting bogged down.
If it's bad, or particularly noticeable, I try to optimise the boggy code (although it's almost always in disk, network or database parts of the code)
|
|
|
|
|
|
I suppose I still think like a C programmer, or even an assembler programmer. My code is as small and unobtrusive as I can make it, and I use the optimisers provided before I deliver it.
~~~~~~~ <;,>< ~~~~~~~~~~~
|
|
|
|
|
There are only few obvious things to take into account from the start. E.g. when you know you need to look up instances in a collection, then provide a fast lookup function (using an std::map or std::unordered_map).
For the rest, it's just wait and see. First, make your code work. Then optimize where needed.
Enjoy life, this is not a rehearsal !!!
|
|
|
|
|
What about adding (or showing) some of the free text replies for next voters?
|
|
|
|
|
I am embeded controlers developer, in my case binary size is first concern.
--RA
|
|
|
|
|
I wait until the app is far enough along to know where optimisation will be necessary and yield measurable improvement, otherwise its Premature.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
I totally agree.
Rules of Optimization:
Rule 1: Don't do it.
Rule 2 (for experts only): Don't do it yet.
(M.A.Jackson)
|
|
|
|
|
|
Completely agree.
Enjoy life, this is not a rehearsal !!!
|
|
|
|
|
Is this bad?
Really, this pool made me stop and think about this a bit.
By "I don't care" I don't mean I waste it, or that I'm careless about optimization, I just use as much as I need/have.
I develop mainly for the web and my servers are usually powerful.
My main goal is to keep the client fast and light, and if for that I need to use more server-side memory I'll do it without hesitation...
I care about the client memory usage, but not so much about server-side.
This is some kind of introspection I'm doing here... is this bad?
Am I alone on this?
Cheers!
|
|
|
|
|
Most people optimize their 'apps' for processor temperature. Or was that meant with the 'power' option? Anyway, we 'nowadays' have plenty of verything and therefore we do not have to know about any algorithms and can waste as much processor time or memory as we want. And there are (and always have been) great ways to fill up the memory and let the processor(s) get hot enough to fry eggs on.
Nothing like a nice interpreter like good old BASIC to get things slow enough. What? That's sooo 20th century? Right. JavaScript can waste time much better than any BASIC ever could. Still not slow enough? Then we can go overboard with data binding and even get compiled code down to a crawl.
After all, in the last 20 years all young and promising developers have been taught to believe that any compiler is better than an average assembly programmer. If I may translate: At least half of you are considered to be dumber than some mindless automation.
Sent from my BatComputer via HAL 9000 and M5
modified 1-Jul-13 1:43am.
|
|
|
|
|
I used to vote every week on Monday and never did first in my CPian days! 
|
|
|
|
|
Good, but nothing to say about the poll?
|
|
|
|
|
|
Well, now you have a new objective: Be the *LAST* to vote! 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
