3 ms·
Yeah, we did this at a previous employer. One example, is we had them ssh, download & extract a tarball (the Linux source, but the content doesn't matter). Som
by deathanatos 4y ago
Yeah, we did this at a previous employer.
One example, is we had them ssh, download & extract a tarball (the Linux source, but the content doesn't matter). Sometimes, they'd gunzip to stdout. The reaction tells you a lot "lol whoopsie" followed by a quick fix: person knows what they're doing. "uh… what is going on? did I break it?" followed with general cluelessness… maybe not.
That did occasionally break tmux, though.
Part of it was "what are the specs of this thing you're SSH'd into?" and we had one candidate who was adamant the numbers must be wrong: 2 GiB is too little RAM, no machine is that small! Yeah we didn't spin up 128 GiB VM for your interview…
- Volundr 4y agoI never cease to be amazed at how few people really realize just how little hardware is often required for getting real work done. You'd be surprised just how much that 2GB vm with a couple cores can handle!
- sorongopowa 4y agoI started with a single 1xx MHz core and 16MB of RAM. And I'm sure some with even less, lol. Supporting your point: Hardware is awesome if you use it wisely.
- icedchai 4y agoMy first Linux box was a 20mhz 386SX laptop with 3 megs of RAM (1 meg on the motherboard, 2 in an expansion.) I could barely run Linux 0.99.x. The distro was SLS, and it came on 12 or so floppy disks. I quickly upgraded to a 486 with 8 megs RAM, then 20... which seemed incredible at the time (1994-ish.) It's amazing how bloated today's software is...