Testing — a different take
A few weeks ago I learned about an interesting technique one of my professors used when writing algorithmic code. He’d first write a very naive, straightforward implementation that wasn’t algorithmically smart but gave correct results. To create the optimal design, he’d use the naive one as a baseline to verify that the answers are correct.
Definitely interesting, gives a much larger input/output space then just doing something table driven.