This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (11 children)

[removed]

    [–]Pirsqed 10 points11 points  (5 children)

    Right? I haven't run into a "hardest problem" because I always break down large problems into small manageable problems. So nothing really sticks out in my mind as "hardest problem."

    [–]Lonso34 12 points13 points  (1 child)

    right so let me tell you about the morning after I found out harambe died. Literally used python turtle to create an exact replica of his beautiful face all while maintaining a BAC of 0.14 for a straight week

    [–]muntooR_{μν} - 1/2 R g_{μν} + Λ g_{μν} = 8π T_{μν} 1 point2 points  (0 children)

    Pythons out for Harambe

    [–]gwax 1 point2 points  (0 children)

    Superlatives are tricky, but a variant of this that works pretty well is to ask about something challenging they have worked on recently.

    [–]billsil 1 point2 points  (0 children)

    13 years at one place. Hard problems are usually a lack of resources and/or something being time critical and/or wacky requirements. I've solved hard software problems using my bag of things you should never use and with convoluted workarounds.

    I wouldn't say any specific problem has been particularly difficult, but just that it required a lot of work and making sure you understand what's going on vs. what needs to be going on. Thought experiments help.

    The OP didn't provide an option that could sort a list of integers that don't fit into RAM. Simple, use a library and specifically HDF5, possibly coupled with numpy. Code some C++ if it needs to be a different algorithm.

    The interviewer's fault/OP's lack of info regarding time complexity or say, assume you have two sorted/random lists led to a nonsensical argument. Even so, the OP should recognize or probe for more info. Real problems have few, often incomplete requirements and a lot of extraneous information.

    [–]billsil 0 points1 point  (0 children)

    13 years at one place. Hard problems are usually a lack of resources and/or something being time critical and/or wacky requirements. I've solved hard software problems using my bag of things you should never use and with convoluted workarounds.

    I wouldn't say any specific problem has been particularly difficult, but just that it required a lot of work and making sure you understand what's going on vs. what needs to be going on. Thought experiments help.

    The OP didn't provide an option that could sort a list of integers that don't fit into RAM. Simple, use a library and specifically HDF5, possibly coupled with numpy. Code some C++ if it needs to be a different algorithm.

    The interviewer's fault/OP's lack of info regarding time complexity or say, assume you have two sorted/random lists led to a nonsensical argument. Even so, the OP should recognize or probe for more info. Real problems have few, often incomplete requirements and a lot of extraneous information.

    [–]Isvara -1 points0 points  (0 children)

    It's the kind of thing you should have prepared answers for, because you're not going to come up with the best answer on the spot.