A Friday afternoon discussion in a couple of slacks today made me think about "coding tests" that companies like to implement.
While I don't often encounter them myself any more, I certainly have in the past. They're apparently loved by hiring managers, but detested by developers, and I'd like to give some feedback on why they're not helpful (and how to make them better).
Samuel Levy is a software architect, developer and consultant.
He owns and operates Determined Development,
a small web development and consulting company operating out of Brisbane, Australia.
He doesn't know why you're reading the footer. Who reads the footer?