|Think about Loose Coupling|
Re: Rosetta Dispatch Tableby sundialsvc4 (Abbot)
|on Nov 24, 2017 at 00:14 UTC||Need Help??|
Since we seem to have strayed onto the topic of “interviews from the interviewer’s point of view ... which is quite refreshing, actually ... I think that we should begin by acknowledging that our profession is one of intense pressure. But, the root-cause of that pressure is, I think, novel(!). Please let me quickly explain.
I once read an e-book (I never saw it in print) called Managing the Mechanism, in which the author pointed out that “computer software is a
Furthermore, I consider it entirely-safe to assert that “the actual task has never been ‘programming-language specific.’” Not Perl, not PHP, not JOVIAL, not anything. All of us use whatever is at hand to do what needs be done, and we do it every day using an endless series of technical compromises(!), not absolutes. All of this we know. I am preaching to the choir.
And so: ENTER, STAGE LEFT: The Candidate
Well, IMHO, first of all, while it used to be that we were dealing with esoterica that no one else knew, today we are probably dealing with people who first encountered (say ...) Perl in fifth grade, if not kindergarten. Also, it is impossible, I aver, to expect to find any candidate who off-the-curb already possesses exactly the technical milieu that “our team” possesses, “right here.” If we are waiting to find any such person, IMHO we are “Waiting for Godot.”
Therefore, when interviewing, I try to look for three things in particular:
I freely admit that some of these perspectives are shaped by my career-history of striving to turn-around projects that have sunk into “failure mode.” Which, I readily admit, is (thank God ...) an edge-case. I have encountered a lot of demoralized people along the way. When I interview, I don’t want to create another one.
Even though I know that the candidate will encounter intense pressure on