Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: Warner Losh <imp@bsdimp.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Interview question
Date: Tue, 3 Jan 2023 18:44:42 -0800	[thread overview]
Message-ID: <F93489B7-14F1-4375-B5C1-15FC0DC8EAA1@iitbombay.org> (raw)
In-Reply-To: <CANCZdfpkhq=UqJvTFYpLCRSJaSYXXDoZQjmJvyBEOG74xGt3fA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]

On Jan 3, 2023, at 7:57 AM, Warner Losh <imp@bsdimp.com> wrote:
> 
> 
> 
> On Mon, Jan 2, 2023 at 7:59 PM Larry McVoy <lm@mcvoy.com <mailto:lm@mcvoy.com>> wrote:
>> On Mon, Jan 02, 2023 at 02:13:45PM -0700, Adam Thornton wrote:
>> > Which of these, if any, do you count?
>> 
>> Any of them that are entirely done by you. 
> 
> With due respect, this seems like an impossible thing to have done. I think it's an arbitrary question.

I see the point of Larry asking this. Presumably it is *one* of the questions he asks! There are a lot of smart people who don't know or don't have experience with how to deliver a product. Product delivery is a lot more than hacking up some code. It is writing good design and user documentation, thorough testing, lots of trial and error to make the UI/GUI as intuitive as possible, making it as bug free as possible, may be even dealing with customer bug reports and requests etc. etc. At least to me it would not be a pass/fail question (IMHO there is no point in asking such questions to an interviewee).

> "No man is an Island" John Donne.
> 
> Nobody on this list can claim to have anything they did entirely by themselves. Everybody used tools built by others. Everybody used an OS built by others. Even people that did a full OS + all the tools used other tools to boostrap that were done by others. They used hardware that was designed by others, made from chips made by others from raw materials mined by others.

Right but even with a complete set of tools and detailed plans not everyone can do good carpentry. It requires care, knowing your craft, knowing what shortcuts you can take, knowing who to ask for advice etc. etc. And it is a different challenge when you have to make a dozen matching chairs as opposed to one.

When I was interviewing people my job was to assess their experience, abilities & aptitude. Nobody is perfect so you have to find where they would be a good fit in some job for which there is an opening, as well as whether it is of sufficiently interesting/challenging for them etc.

> We all "stand on the shoulders of giants"[*]. While I get the connection to looking for someone that's independent, self sufficient, etc, it seems a bit arbitrary. I've done a ton of work on the FreeBSD kernel, for example, but it isn't all 100% me. Others have contributed to it, others have reviewed my work, others have given me (or the project) bug fixes. That project, as with so many others, are so much better due to the collaboration that happened between people. In many ways that's more important than doing something 100% yourself.
> 
> Warner
> 
> [*] "If I have seen further it is by standing on the sholders[sic] of others" -- Isaac Newton in a 1675 letter to his rival Robert Hooke




[-- Attachment #2: Type: text/html, Size: 3746 bytes --]

  parent reply	other threads:[~2023-01-04  2:46 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
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 [this message]
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=F93489B7-14F1-4375-B5C1-15FC0DC8EAA1@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=coff@tuhs.org \
    --cc=imp@bsdimp.com \
    /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).