4 ms·
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 correlat
by MisterSandman 4y ago
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.
- musicale 4y agoMissing 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.