Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] funny article about Rust and technical interviews
Date: Tue, 26 May 2020 15:24:44 -0700
Message-ID: <CAC2bXD5FBVOumGyBxgWQxK6DTzkE1g=SuQvLWgT2UmGOcLppyw@mail.gmail.com> (raw)
In-Reply-To: <958561A0-F4FC-4EE1-9C1C-D75110311BC7@getmailspring.com>

On Tue, May 26, 2020, 15:03 Cole Poirier <colepoirier@gmail.com> wrote:

> On May 26 2020, at 2:25 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> > On Tuesday, May 26, 2020, Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> >> https://blog.mgattozzi.dev/oxidizing-the-technical-interview/
> >>
> >> Amazing and horrifying!
> >
> >
> > :)
> >
> > reminds me of a bare metal ADA howto i saw, when the question came up on
> > comp.arch about not using ADA runtimes that are only designed for
> GNU/Linux.
> >
> > l.
>
> It made my brain hurt. Can one of you more experienced programmers
> please explain the joke to me? Is the objective to show us mere mortals
> our assumptions of safety, etc. lie upon foundations that would scare us
> because our modern programming environments coddle us?
>

The objective is mostly to provoke laughter at the absurdity of what the
interviewee is doing, since they are going waay beyond what is necessary or
practical to run a program even if you were running it on bare metal: using
#![no_core] is like if you decided to write your own stddef.h or stdint.h
if you were writing in C, or writing your own implementation of the int or
bool classes in Python.

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 20:15 Jacob Lifshay
2020-05-26 21:25 ` Luke Kenneth Casson Leighton
2020-05-26 22:03   ` Cole Poirier
2020-05-26 22:24     ` Jacob Lifshay [this message]

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='CAC2bXD5FBVOumGyBxgWQxK6DTzkE1g=SuQvLWgT2UmGOcLppyw@mail.gmail.com' \
    --to=programmerjake@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git