From: Larry McVoy <lm@mcvoy.com>
To: Adam Thornton <athornton@gmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Interview question
Date: Mon, 2 Jan 2023 18:58:36 -0800 [thread overview]
Message-ID: <20230103025836.GZ25547@mcvoy.com> (raw)
In-Reply-To: <7AC50DD1-DAB2-443A-B275-E3FB08031167@gmail.com>
On Mon, Jan 02, 2023 at 02:13:45PM -0700, Adam Thornton wrote:
>
>
> > On Jan 2, 2023, at 1:36 PM, Larry McVoy <lm@mcvoy.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?
>
> Huh. That is a surprisingly tricky question, depending on how you want to construe "entirely you".
>
> Which of these, if any, do you count?
Any of them that are entirely done by you. Here's an example. I posted
move.c and copy.c to comp.sources.unix as an undergrad, a newbie. They
let you do stuff like
move =.c =.C++
and the = was the wild card. .* in regexp. They were a little better
than that because you could have more than one = and could expand with
something like \=2 \=1 (it's been 40 years, I might have the details
wrong, still have the source, can post). Just did
http://mcvoy.com/lm/move.shar
I know people used it because later in life it got mentioned. But
literally noone ever asked me how to use it or install or anything.
It's a tiny thing but it meets what I was looking for.
Entirely you means entirely you. If you have done that, you are in
a pretty small crowd.
--
---
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2023-01-03 2:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230102203646.GT25547@mcvoy.com>
2023-01-02 21:13 ` Adam Thornton
2023-01-03 2:58 ` Larry McVoy [this message]
2023-01-03 6:06 ` Dave Horsfall
2023-01-03 6:16 ` Adam Thornton
2023-01-03 15:57 ` Warner Losh
2023-01-03 19:53 ` segaloco via COFF
2023-01-04 2:44 ` Bakul Shah
2023-01-04 3:06 ` Larry McVoy
2023-01-04 15:42 ` Dan Cross
2023-01-04 16:00 ` Warner Losh
2023-01-04 16:52 ` Dan Cross
2023-01-04 17:51 ` Adam Thornton
2023-01-04 16:06 ` Larry McVoy
2023-01-04 16:58 ` segaloco via COFF
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=20230103025836.GZ25547@mcvoy.com \
--to=lm@mcvoy.com \
--cc=athornton@gmail.com \
--cc=coff@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).