Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Tue, 17 Nov 2020 13:22:33 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AHLDZLY005419; Tue, 17 Nov 2020 16:13:47 -0500 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AHLDYOm005416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 17 Nov 2020 16:13:34 -0500 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 0AHLDVJe022703 for ; Tue, 17 Nov 2020 16:13:34 -0500 Received: from oc11expo6.exchange.mit.edu (18.9.4.11) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 17 Nov 2020 16:13:08 -0500 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo6.exchange.mit.edu (18.9.4.11) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 17 Nov 2020 16:13:19 -0500 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.173) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 17 Nov 2020 16:13:19 -0500 Received: from DM3PR12CA0102.namprd12.prod.outlook.com (2603:10b6:0:55::22) by CY1PR01MB2106.prod.exchangelabs.com (2a01:111:e400:c63a::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28; Tue, 17 Nov 2020 21:13:18 +0000 Received: from DM6NAM11FT031.eop-nam11.prod.protection.outlook.com (2603:10b6:0:55:cafe::a8) by DM3PR12CA0102.outlook.office365.com (2603:10b6:0:55::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3589.20 via Frontend Transport; Tue, 17 Nov 2020 21:13:18 +0000 Received: from mail-ej1-f51.google.com (209.85.218.51) by DM6NAM11FT031.mail.protection.outlook.com (10.13.172.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28 via Frontend Transport; Tue, 17 Nov 2020 21:13:18 +0000 Received: by mail-ej1-f51.google.com with SMTP id a16so3685577ejj.5 for ; Tue, 17 Nov 2020 13:13:18 -0800 (PST) From: Ryan O'Connor To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 17 Nov 2020 13:12:58 -0800 Subject: Re: [EE]: How to find & hire firmware people Thread-Topic: [EE]: How to find & hire firmware people Thread-Index: Ada9J8Qj/pJB9al8QLeGmM2+Nw7jEg== Message-ID: References: <5FB358FA.5040207@narwani.org> <70249b66-1d70-0428-fc9d-a4332ebf0eae@linuxha.com> <20201117204949.GE20895@laptop.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20201117204949.GE20895@laptop.org> Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: TempError X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.218.51 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.51; helo=mail-ej1-f51.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=IaVwEVRafMlnUJvLC1ol65undUP9Z5+g0zfJxb0HcdE=; b=gKgw91KMQH3k+SJ03hZVNvPabUfUwzfyRCGGYDKWNqCmpOKirWbzJlTVZPeuPwiUlO aos1FdBKyc/ZIPWDJ7AXDEtxLuobBlF7HO6Zuo2hQ0M9mM71aWbwP6u9e5bq1Dcc9MLL bBg8N5KM4q/v4e360qIMR6ffjhEcHh6vKlHjA8bH+Ekv0V3nUJm3Pi+2nti2aBsuHGvw Kls3FQihzVkWLeHmxIAIY/tqmEhVR6Pk8QfCVRJrvGxQQy3GMT+gjdkySuZ7+Tr24Fb0 9zJsp+4ElPjmtong0t/hYm5OBCZNLG4UCmmLkfybhLafqge7g+OAxhwLLblk3eDxtMRC 9pRQ== authentication-results: spf=pass (sender IP is 209.85.218.51) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a17:906:1159:: with SMTP id i25mr19921501eja.398.1605647596908; Tue, 17 Nov 2020 13:13:16 -0800 (PST) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Thanks James that's a really generous comment; much appreciated. In regards to web developers, in the very least we need to be constantly learning and adapting since the web is moving so fast. But I definitely recognise firmware is it's own beast and skillset in very much the same way. It does take experience and some training. What I didn't mention was when I was working on the graphics demos there was an engineer there who worked for AMD who were really breaking into the market as a big player at the time. His stuff was super next level, he was able to write all kinds of 3d raytracing demos within code size limitations which performed well and were just damn cool and interesting. His level of understanding of instructions and mathematics was incomprehensible to most of us. For anyone interested, this scene has (ironically) shifted to the web now, with opengl shaders being supported in browsers. Googling "shadertoy" will find the most popular active demo archive where all code is available and many study examples are available. I hate to admit it but many of the demos now are even more impressive with less shader code than back in those days. But that's also the evolution of GPU architecture for you. And that's not even mentioning that very soon 3D games will be enhanced with real-time ray tracing as a norm (hardware is already affordable and not a gimmick: https://www.windowscentral.com/10-graphics-cards-support-ray-tracing) On Wed, 18 Nov 2020 at 09:51, James Cameron wrote: > Thanks Ryan, a great read. > > I'm also reminded that applicants for a role experience the > Dunning-Kruger effect combined with a simple confirmation bias. > > Web developers are a cut above the average dish washer; they > understand procedural languages, computer networking, software > layering, and standards. What they don't know for a firmware role can > be learned, but an employer may want to pay for that training to occur > before hiring rather than after. > > p.s. my web development skills have atrophied, as has my COBOL, but my > firmware skills are worth testing. Hire me. ;-) > > -- > James Cameron > http://quozl.netrek.org/ > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .