[–] 2 points 10 months ago

Omg I remember running into something like this about 12 years ago. TTY did help but did need a reboot. I had to arch-chroot off the live usb so many times that night, my first ever Linux installation and I fucked up the bootloader and initial packages so hard so many times. I felt so cool when I was able to switch to another tty without needing yet another usb boot. Thanks for that memory.

  • source
  • [–] 1 point 10 months ago

    Oh well that's depressing. I last interviewed about 3 years ago and I guess it might well have changed overall. OTOH I get to run the interviews where I'm at now and I can assure you that 'actually using your available resources' would never be a problem :)

  • source
  • parent
  • context
  • [–] 9 points 10 months ago* (last edited 10 months ago) (3 children)

    We let people use chatbots in our technical interview and don't even mark down for it, since they're a tool that exists.

    I have yet to see a candidate who uses chatbots be anywhere near as good at producing good solutions quickly as the ones who don't.

  • source
  • parent
  • context
  • [–] 0 points 10 months ago*

    In reverse order:

    • Directly mapping structs to JSON is a solved problem in userland for every major language
    • yes it does, and worse it's part of the return signature and null is super-prevalent of necessity as a result
    • even java doesn't do that any more, but fine I guess
    • cool, but access modifiers actually make a lot of sense. Go's solution to this is to use capitalisation as a marker, which has no 'inferential readability' -- public/private is obvious. Foo/foo? Considerably less so

    Further, meta programming in go sucks donkey balls. Sure, it finally got generics but also they suck. Last I checked it still didn't even support covariance.

  • source
  • parent
  • context
  • view more: ‹ prev next ›