dsgrue3 said:
Enlighten me. So far as I know the curriculum for CS is focused on software development, not hardware. While I personally had way too much EE and CE courses in conjunction with my curriculum, that's because it was in the college of engineering. I didn't care much for those courses either. |
I wíll.
In Germany, back when I studied, there was a difference between university and "fachhochschule". University is more of a theoretical way of studying while "fachhochschule" focused on real-life stuff.
You could finish University without ever writing any line of code. You were taught the (mathematical) basics and theories on how "computing" works. Algorithms, boolean algebra, concepts of coding (imperative, oo, even functional). A lot of courses were math and algorithmic design (e.g. dynamic programming, randomized algorithms) aswell as automatas (stack-oriented, turing, you know what I mean, hopefully). You weren't trained to be a code-monkey but to know how the basics work. It is of no use to know the java-libs - this is just handwork. If you know how stuff works you can easily learn any language.
When you advanced further in later terms you could specialize in what you seem is interesting to you so I chose hardware-stuff.
I did a lot of computer-architecture courses, wrote a lot of x86- and mips-assembler and wrote my diploma-thesis on the design-flow of fpgas.
So our curriculum was very widespread to enable you later to use your knowledge on the basics so to learn very fast which special things are needed to work at a special job.
