> Really good pseudocode might be more useful than your actual code Hear hear! OP, if you go this route, treat your implementation as a practice run, and write

> Really good pseudocode might be more useful than your actual code Hear hear! OP, if you go this route, treat your implementation as a practice run, and write out exactly how it works in pseudocode. My 2 cents: I think that hiring a (good) professional for a rework/reimplementation would be productive, but it would certainly run the risk of exposing errors in your work. If that's desirable or not depends on your timeline to publish, I guess.