killermonkeys
Joined 14 years ago
Joined 14 years ago
One thing I do see is that it hasn't yet been tested on real networks, only synthetic networks. It will be interesting to see if it provides real gains across the range of conditions, particularly in hyper optimized data centers.
SF has historically shoddy construction due to the gold rush, mail order housing bought sight unseen, and a mild climate.
If I built a house in the US I would have it designed by a European.
"Monopoly" is a perfect example of a brain teaser and anyone using that would be treated pretty harshly by the committee that reviews interview feedback. Estimate questions are not: there's no expectation of a "right answer" and the important fact is the working.
Some programming questions border on brain teasers to non programmers but that doesn't matter because you are asking programmers and again, it's the working that matters.
Finally different roles get different types of interviews. I worked in PM and there were analytical (these questions), product (design a better x) and technical (basic engineering interviews). The behavioral type was not one I encountered in PM or eng but maybe used elsewhere.
Usually type designers consider the legibility of 3, 6, 8, 9, 0 (particularly 8 and 0) to be more important than between O and 0. But for coders, the ambiguity between O and 0 is a big problem, so a designer would consider that.
An example for pilots: you are heading 180 and radio it as "one zero eight". Even if you immediately correct yourself, it's a problem.