3 ms·
... can't do this in your incredibly artificial, unrealistic context Oh, then you're a non-hire (rightfully so). If you can't adjust to such a simple context,
by smikhanov 11y ago
... can't do this in your incredibly artificial, unrealistic context
Oh, then you're a non-hire (rightfully so). If you can't adjust to such a simple context, there's no way I can be sure you can handle an occasional tight deadline, urgent and critical failure in production, rewrite of stinky and hairy piece of code left by a less competent colleague, external system that mystically fails for no reason and writes no logs whatsoever, etc, ad infinium.
Programming profession is hard and full of rough edges, unfortunately.
- mquander 11y agoIf you can't adjust to such a simple context, there's no way I can be sure you can handle an occasional tight deadline, urgent and critical failure in production, rewrite of stinky and hairy piece of code left by a less competent colleague, external system that mystically fails for no reason and writes no logs whatsoever, etc, ad infinium. Citation needed.
- Tenhundfeld 11y agoAnd you think if I solve fizzbuzz in 15 minutes on a sheet of paper, you can be sure I can handle those things? That's the part I don't get. It's so arbitrary and artificial. All you can be sure of is that I can solve fizzbuzz in 15 minutes. > Programming profession is hard and full of rough edges, unfortunately. I agree completely, but I think paper programming exercises produce false positives AND false negatives.
- krisdol 11y agoHow does your team manage to accomplish all these tight deadlines while having to use paper and whiteboards to rewrite stinky code? Do your production servers run A4 or legal? What's your cardstock uptime? I've had trouble switching to glossy for all but the most specialized of tasks, I'd be really curious to hear about your paper stack.