I tend to disagree with the title anyway
. This list seems suited more for someone who wants to know enough to understand white papers and attend conferences. If you want to be a cryptographer and actually design or break algorithms you would need to know a great deal more about mathematics and computer science than what is present on that list.
Additionally if you are or work for a cryptography company the 53rd thing you should know is not to post crypto challenges on forums
, and then assume your algorithm is secure when no one attempts it. (Sorry couldn’t resist)