I am interested in Soundex only as a curiosity so I read this article mostly for entertainment. That said, I think the title might have reached a broader audience as "Test twice, code once" because it's a great example of the process. I appreciate the revealed 'oops' that you didn't redact for the sake of appearing 'expert' on the subject.

I don't have much more to add on the Soundex discussion though - just wanted to say thanks for this article and encourage you to write (and release) another soon. 🙂