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 th=
em
> 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 waitin=
g
> for new data. There's just nothing to be saved in that project to justify
> the time it takes to "improve" the code.
>

Writing good code takes discipline. It's about maintaining a high=20
standard. Don't let anyone talk you into being sloppy because there is no=20
benefit in doing things the right way.

Once you become a good programmer you are on your way to becoming a great=20
programmer. Don't settle for good, good programmers don't create great=20
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
.