I came here to make exactly the same recommendation about Udi Manber's book.
When designing an algorithm, you ought to make sure that it actually works. At some point, then, you're going to have to prove it. Which for most people is hard, in part because most algorithms books present the proofs as a fait accompli. They just show up, fully formed.
But Manber argues, and demonstrates convincingly in his book, that the design and the proof both become easier if you do them together. The design guides the proof, the proof the design.
He's right. Since reading the book, I don't do it any other way.
The book, tragically, costs about $110. But if you care about this stuff, it's worth it.
When designing an algorithm, you ought to make sure that it actually works. At some point, then, you're going to have to prove it. Which for most people is hard, in part because most algorithms books present the proofs as a fait accompli. They just show up, fully formed.
But Manber argues, and demonstrates convincingly in his book, that the design and the proof both become easier if you do them together. The design guides the proof, the proof the design.
He's right. Since reading the book, I don't do it any other way.
The book, tragically, costs about $110. But if you care about this stuff, it's worth it.