Dec20-07, 05:08 PM
The Art of Computer Programming is literally the bible of computer science. If you know the stuff between its covers, you know 90% of what's really important about programming a computer.
Being a computer scientist is not about knowing lots of programming languages, or being able to use Visual Studio to make graphical applications, or being able to download and use a math library.
Being a computer scientist means understanding the deep, important subjects that underly all computer programming -- data structures, algorithms, and trade-offs. Those three topics literally define computer science. All the rest that goes on top of it (PHP, Visual Basic, etc.) is fluff. The fluff is easy to learn, and changes yearly -- that's why Microsoft would rather hire programmers who have ignored the fluff and studied only the deep magic.
This is why I think this entire thread is misguided, rudinreader. You seem to be mistaking pretty graphical interfaces, network applications, layers of abstraction on top of the hardware, rapid application development languages, etc. as computer science, but they aren't.
In the same vein, interior design is not architecture.
|Register to reply|
|Difference between "Identical", "Equal", "Equivalent"||Calculus & Beyond Homework||9|
|how to preserve "date modified" when burning to a CD||Computing & Technology||2|
|The "Sith" is coming, and it's a...||General Discussion||11|
|"Dragons are coming"||Biology||7|