4 ms·
They might not care, but in that case this question essentially tests if a person understands what 'GHz' means and can think logically, which is not that much t
by lomereiter 9y ago
They might not care, but in that case this question essentially tests if a person understands what 'GHz' means and can think logically, which is not that much to ask.
- watwut 9y agoWhy would web programmer think about processors and GHz is beyond me. There are jobs where it might matter, but for most of them it is completely irrelevant.
- jrowley 9y agoWhen youre writing a complex SPA app and your performance is dragging on that cheap Android, it's nice to be able to reason about things like clock speed, memory usage, etc.
- deleted 9y ago[deleted]
- js2 9y agoI know we can treat a lot of the technology we use as a black box, but not knowing even the basics of that technology indicates a lack of curiosity. I'd be shocked to find a competent programmer who couldn't answer the question. A similar question: approximately how many IPv4 addresses are there? See also: "Latency Numbers Every Programmer Should Know"
- watwut 9y agoThey might have been curious about different things then you. Or more interested in knowledge that helps build stuff ( still constantly learning, but choices are different).
- pixelp3 9y agoWhat's next? We shouldn't expect programmers to be aware of how characters, integers and floating point numbers work on a computer?
- watwut 9y agoIf they work in high level language that hides all that behind "number", who cares. How floating point numbers are represented is interesting trivia, but hardly useful in most situations. In general, I would expect people to remember things that are used often and be able to learn the rest fast (e.g. understand concepts and have enough knowledge to make further learning easy). The rest is fluff and hidden cultural test: "Do you have the same history as I do?"