From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] pre-more pager?
Date: Thu, 9 Nov 2017 19:15:12 -0500 [thread overview]
Message-ID: <f60da335-60aa-a2fd-cb70-1118c2037b33@kilonet.net> (raw)
In-Reply-To: <alpine.BSF.2.21.1711100741390.4766@aneurin.horsfall.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On 11/9/2017 3:53 PM, Dave Horsfall wrote:
> If you're interviewing a new hire, see how long it takes 'em to work
> out what this does:
>
> :; </etc/motd> /dev/tty sed 1q ;: echo "Hello, world"
>
For me, there are other criteria for hiring than telling me what some
obscure string of stuff will do.
It's more important that they can take the above or something similar
and shorten/simplify it to:
head -1 /etc/motd
or
sed 1q < /etc/motd
Because I just ran the above on a few different platforms, and they all
just give the first line of /etc/motd, which I expected.
I might be missing something :P - but having them solve a problem the
shortest way possible is more in my interests.
art k.
PS: I've been in interviews where I was given something like that. A
notable one was NYNEX Science and Technology. One of the sysadmins
interviewing me asked about some obscure command or maybe an option, in
SunOS. My answer was "well, I don't remember that, having already worked
with SunOS for a few years, but see that row of manuals behind you? I
bet I can find it in there quick enough". I did, within a minute or two.
I got the consulting gig.
--
Again, no disrespect intended.
next prev parent reply other threads:[~2017-11-10 0:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 18:54 Will Senn
2017-11-08 18:59 ` Clem Cole
2017-11-08 19:06 ` Arthur Krewat
2017-11-08 19:31 ` Jeremy C. Reed
2017-11-08 22:43 ` Dave Horsfall
2017-11-08 22:47 ` Arthur Krewat
2017-11-08 23:21 ` Dave Horsfall
2017-11-09 4:38 ` Will Senn
2017-11-09 13:18 ` Dan Cross
2017-11-09 14:29 ` Will Senn
2017-11-09 20:53 ` Dave Horsfall
2017-11-10 0:15 ` Arthur Krewat [this message]
2017-11-10 2:14 ` Ralph Corderoy
2017-11-08 19:12 ` Bakul Shah
2017-11-08 19:22 ` Random832
2017-11-08 21:18 ` Will Senn
2017-11-08 21:59 ` Ron Natalie
2017-11-08 22:00 ` Clem Cole
2017-11-08 22:18 ` Will Senn
2017-11-09 2:01 ` Steve Johnson
2017-11-09 2:16 ` Lyndon Nerenberg
2017-11-08 19:29 ` Forrest, Jon
2017-11-08 19:43 ` Ron Natalie
2017-11-08 21:03 ` Mark Green
2017-11-08 19:23 Noel Chiappa
2017-11-08 20:02 Noel Chiappa
2017-11-08 20:11 ` Forrest, Jon
2017-11-10 5:26 ` Random832
2017-11-10 7:31 ` Otto Moerbeek
2017-11-08 20:18 ` Clem Cole
2017-11-08 20:28 ` Ron Natalie
2017-11-08 22:47 ` Dave Horsfall
2017-11-08 20:28 Noel Chiappa
2017-11-08 22:02 Paul Ruizendaal
2017-11-08 22:20 ` Will Senn
2017-11-08 22:58 Doug McIlroy
2017-11-09 13:33 Doug McIlroy
2017-11-09 16:19 Norman Wilson
2017-11-09 16:48 ` Arthur Krewat
2017-11-09 17:19 ` Steve Nickolas
2017-11-09 18:15 ` Don Hopkins
2017-11-09 18:26 ` Arthur Krewat
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=f60da335-60aa-a2fd-cb70-1118c2037b33@kilonet.net \
--to=krewat@kilonet.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).