Re:Poll: How many programmers don't know about bit-wise oper...
by jcr on Monday April 08, 2013 @12:20AM
(#5509964)
When I take a step back for wider perspective, your question "Why?" is a
surprisingly good, and oddly enough, and it keeps working across the
various knowledge "areas". For example, should an assembly coder know
HDL (verilog/vhdl) and understand the basics of chip circuits, limits,
and timing well enough to leverage them in assembly code?
Whether you're looking "down" the stack to the details of saving a
"file" on a piece of rotating rust, or looking "up" the stack to the
details of browsers, the question of "Why?" one should know the details
of the other parts/levels is still poignant.
The most fair answer is unfortunately a wishy-washy "yes and no". There
are times when having both deep and wide knowledge is extremely
important, potentially even a requirement, but there are other times
when the task is simple enough for it to be accomplished without
extensive knowledge.
Another way to look at it is through abstractions. The entire point of
abstraction is to hide enough details to make things easier. The trouble
is, when abstractions fail, you really do need to know those hidden
details.
Though you can often accomplish your goals without knowing all the
details of the other layers, you are still better prepared by knowing
them, and can be more efficient by knowing them.
BTW, Excellent link on the basic issues with XOR swapping on modern
systems, but it leaves out a lot of details. ;-)
Whether you're looking "down" the stack to the details of saving a "file" on a piece of rotating rust, or looking "up" the stack to the details of browsers, the question of "Why?" one should know the details of the other parts/levels is still poignant.
The most fair answer is unfortunately a wishy-washy "yes and no". There are times when having both deep and wide knowledge is extremely important, potentially even a requirement, but there are other times when the task is simple enough for it to be accomplished without extensive knowledge.
Another way to look at it is through abstractions. The entire point of abstraction is to hide enough details to make things easier. The trouble is, when abstractions fail, you really do need to know those hidden details.
Though you can often accomplish your goals without knowing all the details of the other layers, you are still better prepared by knowing them, and can be more efficient by knowing them.
BTW, Excellent link on the basic issues with XOR swapping on modern systems, but it leaves out a lot of details. ;-)