better interviewing through data Quote from http://blog.interviewing.io/ http://blog.interviewing.io/ Writing Good Code is like Writing a Novel Quote from htt

better interviewing through data Quote from http://blog.interviewing.io/ http://blog.interviewing.io/ Writing Good Code is like Writing a Novel Quote from https://hackernoon.com/writing-good-code-is-like-writing-a-novel-33973645be01 https://hackernoon.com/writing-good-code-is-like-writing-a-n... When I put above two ideas together, I realized following. If you were running a publishing house and needed to a writer to publish your next book, how do you go about picking the writer? You usually look at the body of work from the writer. You read the books the author wrote in the past to decide if the writer is any good. You don't decide if the writer is good or bad from just 1) reading a page of resume and 2) asking him to write out a clever sentence on a whiteboard in the middle of the interview. That tiny slice of data is useless for deciding on anything. If you are all about deciding based on data, why would you make an employment decision based on the most tiny fraction of the actual data (resume and 30 min interview)? Programming/IT/DevOps workers now have ample ways of showing past work. Often it's personal projects in github or a blog with tutorials on how to secure servers. These are far better tools to measure a candidate. Just like reading books by an author is a far better way to predict how that author's works would turn out. And my personal experiences have shown me that majority of interviewers don't read my blog or my github. I find out in interviews that some don't know it's there. It's at the top of my resume for a reason. And no one's asked about any question what I've written about in my blog or in my github repo. And these are topics directly related to the position.