From: Larry McVoy <email@example.com>
Subject: [TUHS] Re: Interview question
Date: Mon, 2 Jan 2023 12:51:50 -0800 [thread overview]
Message-ID: <20230102205150.GW25547@mcvoy.com> (raw)
On Mon, Jan 02, 2023 at 01:38:30PM -0700, firstname.lastname@example.org wrote:
> Larry McVoy <email@example.com> wrote:
> > The /bin/sh stuff made me think of an interview question I had for engineers,
> > that a surprisingly few could pass:
> > "Tell me about something you wrote that was entirely you, the docs, the
> > tests, the source, the installer, everything. It doesn't have to be a
> > big thing, but it has to have been successfully used by at least 10
> > people who had no contact with you (other than to say thanks)."
> > Most people fail this. I think the people who pass might look
> > positively on the v7 sh stuff. But who knows?
> How many people who failed this question did you hire anyway?
None that I kept. Miss-hired some who didn't pass and let them go eventually.
Whether that question actually is that good of an indicator in general, I
couldn't say. It was a pretty solid one for what we did.
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2023-01-02 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 20:36 [TUHS] " Larry McVoy
2023-01-02 20:38 ` [TUHS] " arnold
2023-01-02 20:51 ` Larry McVoy [this message]
2023-01-03 4:44 ` Ori Idan
2023-01-03 5:15 ` Rich Morin
2023-01-03 5:32 ` Ajay Shah
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).