|
CompE or CS? By Joel Jordan
For many beginning students, the distinction between electrical/computer engineering and computer science is quite fuzzy. Since the classes you take now will invariably determine the career path you're stuck with for the rest of your life (assuming of course, that your career as a professional kazoo player fails to take off), I've prepared a short quiz that can help you determine whether you should be taking ECE classes or CS classes. Try to answer all the questions immediately without thinking about the answers too much.
1) A virtual machine is:
An abstraction of an underlying computer architecture that lets us create beautiful, portable programs. An evil, bloated program that sits on top of the dazzling intricacies of the computer itself to provide stale, boring interfaces. Something that can't be soldered, and therefore not worth knowing about.
2) The x86 instruction set is:
Is that like MIPS? Stack-based floating point unit? Stack-based floating point unit? The book I use to prop up my oscilloscope.
3) A good way to store data for fast access is:
Using a B-tree implemented in C++. Using blocks of SRAM cache on the processor core. Using large pads of green graph paper.
4) The best programming language is:
C/C++. Assembly. Solder.
5) Object-oriented programming is:
A convenient way to make programs more modular and code more reusable, while providing for better conceptual understanding. Slow, bloated, and inefficient compared to my assembly code. Not as fun as drawing Smith Charts.
6) A digital signal processor is:
Is that like MIPS? A chip with an extremely parallel architecture, allowing for fast memory accesses and multiply-accumulates. A fancy way of doing this better suited for op-amps.
7) What is Moore's Law?
Every eighteen months, code becomes more abstract and beautiful. Every eighteen months, the number of transistors on chips doubles. What makes programmers lazier than me.
|
|