smplx,
     I concur! I am an OK programmer. If I could master assembly then I=20
might consider myself to be a good to great programmer. Knowing your own=20
limitations is also very important.
GOD Bless and GOD Help us,
rich!

On 8/25/2016 6:50 PM, smplx wrote:
>
> On Thu, 25 Aug 2016, Denny Esterline wrote:
>
>> I recall spending days playing with tricks of integer math to get
>> resolution and scaling without using floating point. "Because
>> floating-point takes too long" A couple weeks ago I was walking a junior
>> (three months out of college, so green I have to water him) through a
>> recent project. I was going down the path of integer math, he declared t=
hem
>> as floats.... I was about to go into full lecture mode when we actually
>> benchmarked the code - the processor still spends 99% of it's time waiti=
ng
>> for new data. There's just nothing to be saved in that project to justif=
y
>> the time it takes to "improve" the code.
>>
> Writing good code takes discipline. It's about maintaining a high
> standard. Don't let anyone talk you into being sloppy because there is no
> benefit in doing things the right way.
>
> Once you become a good programmer you are on your way to becoming a great
> programmer. Don't settle for good, good programmers don't create great
> systems.

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.