I was thinking that this is actually not as dumb an interview question as it at first appears to be. You could potentially learn something about your candidate's approach from how they solve it. Consider some of the things they might do:
- Write a naive solution (without even the %15 trick) very quickly. Tells you this person is good at whipping out simple code.
- Write a golfish solution. Tells you this person knows perl well, but may be too eager to show off. (An interview is probably the wrong place for golf...)
- Write an efficient solution that minimizes the number of comparisons. Tells you this person thinks about performance. Could be a danger sign for such a small program, but it is an interview.
- Write a very easy-to-read solution, with clear variable names and no tricks. Tells you this person thinks about maintenance.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||