From: Larry McVoy <lm@mcvoy.com>
To: tuhs@tuhs.org
Subject: [TUHS] Interview question
Date: Mon, 2 Jan 2023 12:36:46 -0800 [thread overview]
Message-ID: <20230102203646.GT25547@mcvoy.com> (raw)
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?
next reply other threads:[~2023-01-02 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 20:36 Larry McVoy [this message]
2023-01-02 20:38 ` [TUHS] " arnold
2023-01-02 20:51 ` Larry McVoy
2023-01-03 4:44 ` Ori Idan
2023-01-03 5:15 ` Rich Morin
2023-01-03 5:32 ` Ajay Shah
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230102203646.GT25547@mcvoy.com \
--to=lm@mcvoy.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).