in reply to Re: What training do YOU need?
in thread What training do YOU need?
Pick on a common example of code that can easily be improved using idiomatic constructs. Something like changing C-style for(;;)'s to foreach(@array) or map{..}@array. Make the first change manually explaining the reasons and benefits,
I realize you probably just quickly chose a
this construct as an example. But your
choice is unfortunate.
Changing C-style loops to foreach loops is not as trivial as you would have it appear. The presentation would be impressive, but misleading.
I might point out the advantages of foreach loops. And how the C-style loop is more cumbersome but more adaptable. These folk are probably very comfortable with this C phrasing. Saying this is how to improve the code is unnecessary optimization and quibbling over style at the risk of breakage.
I like presentations that include workload and mental state, to wit:
"It took me two hours to decipher this code."
"Thirty minutes to get this rewrite, that has
these problems. Notice how I used ..."
"A hour of exploratory
testing and minor tweaks. At this point I felt like
I had a good understanding of ..."
To the original post:
If these are not fairly simple scripts and requirements are vague I'd first want my crew to instrument the old stuff to tee off both I and O on demand. Assuming this is reasonable.
I cannot imagine the function-free java code these people are writing.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: Re: What training do YOU need?
by demerphq (Chancellor) on Oct 22, 2002 at 09:33 UTC | |
by Aristotle (Chancellor) on Oct 22, 2002 at 13:30 UTC | |
by demerphq (Chancellor) on Oct 22, 2002 at 13:47 UTC | |
by Aristotle (Chancellor) on Oct 22, 2002 at 15:30 UTC | |
by rir (Vicar) on Oct 22, 2002 at 14:57 UTC |