https://bugzilla.wikimedia.org/show_bug.cgi?id=22018
--- Comment #10 from Martin Keckeis <keckeismar...@hotmail.com> 2010-01-06
13:35:08 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > Anyway, my point was that one has to understand where are the slow parts
> > before
> > making any claims.
> >
> This is the key point: micro-optimization is a waste of time. It's much more
> productive (in terms of performance gain per man-hour spent) to profile the
> code and figure out where the big gains are than it is to change all instances
> of "foo $bar baz" to 'foo ' . $bar . ' baz' or whatever.
I would do this, even if the "performance gain per man-hour spent" is low.
The reasons are:
* micro performance gain ( german quote: "Klein Vieh macht auch Mist" --> out
of www.dict.cc it's in english "A penny saved is a penny earned."
* code looks better (which is for me the design part not the front end ;-) )
* new developer can start faster, because they understand the code faster (IMO)
* when someone new (like me) do something like that, they gain a lot of
knowledge about the software itself in a short period of time -> because u see
much parts of the code, so u know what is the current state
if($interest==true)
mail('keckeismar...@hotmail.com', '...', '...');
else
echo 'I which u good luck for the future.';
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
