Code Interviews
I won&#x27;t bother with coding interviews. I consider them to be &quot;hazing rituals&quot;; not actual qualification assessment. I am very, very fortunate, in that I don&#x27;t have to deal with them. I am not looking for work, and plan to never look for work, ever again.<p>I have a <i>giant</i> portfolio[0]. It has links to 40 or so repos, with tens of thousands of lines of code, spanning decades. Just about every project can be cloned, built, and submitted to the App Store, or SPMed into your own work, in about thirty seconds.<p>I&#x27;ve written stuff that is now a worldwide standard infrastructure, and the links to that work is in my portfolio, as is a blog entry, where I discuss the strategic thinking that informed its genesis.<p>I&#x27;ve written dozens of articles, tutorials, and blog entries, that detail the way I think, work, document my code, evaluate and implement architectures, and work with others. Links to all that is...you guessed it...in my portfolio.<p>There are years of checkins, so things like development velocity can be measured. My GH ID is solid green.<p>If you aren&#x27;t willing to even look at it, then we probably won&#x27;t get along, and we&#x27;re both better off, avoiding each other.<p>[0] <a href="https:&#x2F;&#x2F;stackoverflow.com&#x2F;story&#x2F;chrismarshall" rel="nofollow">https:&#x2F;&#x2F;stackoverflow.com&#x2F;story&#x2F;chrismarshall</a>