From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18964 invoked from network); 4 Jan 2023 17:53:00 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 4 Jan 2023 17:53:00 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 5676C42561; Thu, 5 Jan 2023 03:52:28 +1000 (AEST) Received: from mail-pj1-f42.google.com (mail-pj1-f42.google.com [209.85.216.42]) by minnie.tuhs.org (Postfix) with ESMTPS id 4D88041BC4 for ; Thu, 5 Jan 2023 03:52:21 +1000 (AEST) Received: by mail-pj1-f42.google.com with SMTP id z9-20020a17090a468900b00226b6e7aeeaso2274938pjf.1 for ; Wed, 04 Jan 2023 09:52:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9ph4FXrtD2QBSEDS0Qv8mxdh+L82E9JCLa7hOKRouV0=; b=dx55Vm2btFiogJVuHt/5pfgSWJqDw8tUARsdUE8XCTdhlyFQ7nBQCgkDLdwazbxcbT MVkrP8S25g8cgrVnSbxRFcbiR9SkeNlDaHYt4Kpnqmybxh5eb6eA28E+1lcwj2lyO/WZ WRqVH7AeDeiaUbhIiAzMPDgXc5VDi0+woJqaATHv/EhjA3ecRgOczJM7c0DZS7able8E zo3b0cfd95UDc/kiO7PuzRho/ooV+mqxsx4FioPglpJTJpICRx+CK34HtXk2Th7GYmXA MMYcLqwGjqUVYXAemTNVwtUN5s9uZWZBL1rO/NJ22M5rxjVfatrd70P9PJJ6RxZzqzCX vuOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9ph4FXrtD2QBSEDS0Qv8mxdh+L82E9JCLa7hOKRouV0=; b=e6iAv60l+7j3kdMpyHU/JRdRRTxVIDoHysKI3p7icvkP9nlxR69+8b3U/dwND8oBXE ffgd7izqvNhySeEsMUxjzmBiK4RM5LgpvAWuyrpHqKvuNFcjwhaJM+Bznsrq5KO9h7bB m+tjCSahBwb89oc5OZZfvlrxgbE5FNbn2lgg6LyFUjnL7uIIRwu8gI0EcgV/s5UsNc9p VCXEUA1KjQ9kSiekgT2seoHEFJCU/RhF0lZnhB580HuvPvui5GgWbOBfQilQx5jOrXZN Ws3jwANhibjiJvVD2UsvjmR0T76WHnyMiCq1qzoxjw6urFCFjwuzwfXVxPN7FgzKNw/B eo/Q== X-Gm-Message-State: AFqh2kqsO9PUtLIqtCwviIHG5SSwcu243117ng1zCybbuLxOkhD56sy+ BD63c526pNr0jI8FWcqXUhS8iGHJaq4= X-Google-Smtp-Source: AMrXdXuBiUSijrcNl3QqRg0IJCAQZsId5c7Fa0kfbNdyc6hp+7vXXYbc5ff4GkhU0DhZ0JX1U8M/VA== X-Received: by 2002:a05:6a21:3d0a:b0:af:7939:5fed with SMTP id bi10-20020a056a213d0a00b000af79395fedmr63276634pzc.43.1672854680389; Wed, 04 Jan 2023 09:51:20 -0800 (PST) Received: from smtpclient.apple (ip98-165-124-124.ph.ph.cox.net. [98.165.124.124]) by smtp.gmail.com with ESMTPSA id b6-20020a63d306000000b0047850cecbdesm20242567pgg.69.2023.01.04.09.51.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2023 09:51:19 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\)) From: Adam Thornton In-Reply-To: Date: Wed, 4 Jan 2023 10:51:08 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <5F32EB3A-A50F-4996-84DB-6B3DC2BFA96A@gmail.com> References: <20230102203646.GT25547@mcvoy.com> <7AC50DD1-DAB2-443A-B275-E3FB08031167@gmail.com> <20230103025836.GZ25547@mcvoy.com> <20230104030610.GB25689@mcvoy.com> To: Warner Losh X-Mailer: Apple Mail (2.3731.300.101.1.3) Message-ID-Hash: ILEANU7KCUVIYTDPLDDU4YGN4HM5I6LL X-Message-ID-Hash: ILEANU7KCUVIYTDPLDDU4YGN4HM5I6LL X-MailFrom: athornton@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: COFF X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [COFF] Re: [TUHS] Interview question List-Id: Computer Old Farts Forum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > On Jan 4, 2023, at 9:00 AM, Warner Losh wrote: >=20 > The best programmers I've ever worked with understood teamwork and the = team produced something way better than what any one of us could do = (this was back in the days before egoless programming, CI, code reviews, = etc), so we invented the bits that worked for us on the fly). The thing = is, every single person on that team could (and often did) work on any = aspect of the product, be it the documentation (though the tech writers = usually did that), the code (the programmers usually did that, but the = tech writers committed fixes to the example code that was in the book), = to the printer being out of toner / paper, the soda supply in closet = running out, the snacks that we got at costco running low, stuffing = product into boxes to ship to customers, handling customer calls, = dealing with talking to customers at a technical conference in a sales = booth, presenting papers at conferences, etc. Nobody did anything = entirely by themselves. We interviewed several 'lone wolves' that had = done it all, but found the one we hired couldn't integrate into our pack = because they couldn't be part of a team and put the team first and the = group needs ahead of their own. That's the Genesis of my mistrust of = this question, or at least the premise behind it. And Dan, these 'scut = tasks' weren't about hazing, but just about doing what needed to be = done... One of the things that makes working in my team at the Rubin Observatory = the best job I've ever had is that our manager is brilliant at hiring = smart generalists who can play nice together. It's not that we can all = do everything: I'm pretty terrible at RDBM stuff, for instance (I have = learned a fair bit about time-series databases in the last year), but in = a pinch, we can step in and try and get each other unstuck, and between = all of us we have a lot of experience and our hunches have gotten pretty = good. And honestly, it's just a lot more fun to have other people to bounce = ideas off of and to make the stuff I'm writing better through thoughtful = code reviews. Sure, I have done solo projects that saw the light of = day, some very very large (that text adventure is the second-biggest = Inform 7 project I'm aware of, and it took a decade or so of free-time = screwing around, on and off; it's got a good-sized novella, anyway, of = text displayed to the player, and all the logic wrapped around that = probably doubles the size[*]), but the stuff I am most proud of = currently (which is the conversion of the JupyterHub Kubespawner to = coroutines) was a maintenance project. I didn't own the original codebase, my work went through several rounds = of internal review before we submitted it upstream, and then it went = through a couple more rounds of review with the project maintainers = before they accepted it. But accept it they did, and our spawn error = rate is less than 10% of what it was with the thread-based version. And = to get that last 10% down significantly farther we're going to have to = abandon their spawning model entirely, which is the right decision for = the Rubin Observatory but almost certainly the wrong one for the vast = majority of sites who want to run JupyterHub/Lab under K8s. Adam [*] Inform 7 is a weird language. It's fundamentally declarative, and = in some sense wants to make the experience of writing a text adventure a = lot like the experience of playing a text adventure.=