Re^2: Creating a sub-list constrained by an average while maintaining maximum number of original elements

CountZero...

I am truly humbled by your reply to the OP. Your response was quick, and eerily accurate. I understood what he was asking only after you had replied.

I am dazzled by your ability to so rapidly dissect such a problem into its parts, and then provide an easy-to-understand description of the mathematical formula.

Steve

Comment on Re^2: Creating a sub-list constrained by an average while maintaining maximum number of original elements

Replies are listed 'Best First'.
Re^3: Creating a sub-list constrained by an average while maintaining maximum number of original elements by CountZero (Bishop) on Sep 01, 2010 at 10:15 UTC
Thank you for this praise, but really it is what I was trained to do. Yes, I am a lawyer (not a trained programmer) and as a lawyer we are trained to analyse a problem (most of the time based on incomplete or even wrong data), then synthesize a solution and present this solution using language (the dreaded "legalese"). It is not that different what a analyst / programmer does! CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]

Replies are listed 'Best First'.

Re^3: Creating a sub-list constrained by an average while maintaining maximum number of original elements
by CountZero (Bishop) on Sep 01, 2010 at 10:15 UTC

Yes, I am a lawyer (not a trained programmer) and as a lawyer we are trained to analyse a problem (most of the time based on incomplete or even wrong data), then synthesize a solution and present this solution using language (the dreaded "legalese").

It is not that different what a analyst / programmer does!

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]