I don't think the bar needs to be that high. Just write a decent API for your magic algorithm, choose decent names and types, tune the inner loops and grok the

I don't think the bar needs to be that high. Just write a decent API for your magic algorithm, choose decent names and types, tune the inner loops and grok the performance edge cases, write a few unit tests, and I think the 80/20 rule applies for anything much after that. A much better scenario for a handoff to another engineer than "here is my .m file, enjoy porting it to C++." They can refactor it up more and introduce interfaces, etc, from there.