Your "shibboleths" come off as somewhat smug and self-congratulatory, IMHO.
E.g.:
> You think comments are a last resort for documenting an algorithm.
Right, would like to see you implement tf-idf weights in a vector-space model without any comments. Super helpful for devs who come in after you.
> You understand the illusion of complexity and why simplicity is always better.
Who's pro-complexity? What dev sits around and says, "Wow, this is too easy to understand, I need to make it more confusing"? Complexity is a result of many factors but intent is typically not one of them.
> You can and have extracted declarative implementations out of imperative code. You know when it’s worth it and when it’s not.
Speaking as a hiring manager I'm not sure I can think of a less applicable signal as to whether or not a candidate would be a good hire than something this specific.
What this list really should be titled is, "A List of Things I Know and Am Proud of" not potential signals for good hires.
Not saying this to cut you down, just to let you know it's written in a tone that's over-specific and (to the average reader) arrogant. If I may I suggest rewriting it sound more inclusive, exciting and positive instead of "I'm so great because I know these things and you should too."
Just my two cents.
E.g.: > You think comments are a last resort for documenting an algorithm.
Right, would like to see you implement tf-idf weights in a vector-space model without any comments. Super helpful for devs who come in after you.
> You understand the illusion of complexity and why simplicity is always better.
Who's pro-complexity? What dev sits around and says, "Wow, this is too easy to understand, I need to make it more confusing"? Complexity is a result of many factors but intent is typically not one of them.
> You can and have extracted declarative implementations out of imperative code. You know when it’s worth it and when it’s not.
Speaking as a hiring manager I'm not sure I can think of a less applicable signal as to whether or not a candidate would be a good hire than something this specific.
What this list really should be titled is, "A List of Things I Know and Am Proud of" not potential signals for good hires.
Not saying this to cut you down, just to let you know it's written in a tone that's over-specific and (to the average reader) arrogant. If I may I suggest rewriting it sound more inclusive, exciting and positive instead of "I'm so great because I know these things and you should too."
Just my two cents.