undefined | Better HN

0 pointsMisterSandman3y ago0 comments

This comment is far from reality. It's difficult to measure what a "good" programmer is, but regardless of decision I am confident that it will have no correlation with whether you learned Verilog or what a D Flip Flop is.

0 comments

1 comments · 1 top-level

musicale3y ago

Missing the forest for the trees. Computer architecture courses often expose you to things like: caches, memory and storage hierarchies, I/O, software/hardware interface, parallelism, Amdahl's law, pipelining, vector processing, prefetching, speculation, synchronization, clocking, interrupts, vector processing, data encoding, stream processing, virtual memory, general virtualization, isolation etc., etc..

If you care about execution time, responsiveness, efficiency, or reliability, these things matter.

If you're doing systems programming, they are essential.

j / k navigate · click thread line to collapse