Yep. A wise emeritus professor once told me that grad school is a time to learn how to learn. It's a good idea to get as broad a base there as you can so that you're "conversant" in a subject, enabling you to read up on it quickly to get acquainted with it in more depth in the future as your research/teaching requires. This has really paid off for me and I highly recommend it, even if it means you'll graduate a semester later (which is effectively what I did by unofficially auditing 4-5 courses).My grad program had a 'breadth requirement' for courses, you had to take them from diverse groups (all Comp Sci though), their idea was to get breadth from courses, and specialize via thesis research. Makes sense, although it made me miss some good courses as auditing a course can quickly lose priority to other stuff. Similarly here, I think taking some other courses makes sense to make you more complete, but only if you're not going to delve into them too deeply, most m.sc/ph.d. oriented grad programs don't place much significance on courses anyway, at least that was the case with me.
Yep, depends on your learning style. I get a lot out of being lectured to, whereas others can do just as well reading a textbook on a subject. I can usually get the same information out of a book, but I pick it up a lot quicker during a lecture, then can get the details later on from the literature as necessary.Auditing or sitting in is a good idea. It's always good to expand your horizons into any related fields, and I think most advisors would like that too, but at the same time you don't want to get bogged down in coursework after you have started your thesis work.
Of course, you can also just get some books and read up on various topics on your own, without bothering with courses (which often don't exist in advanced fields anyway). This is basically what I've been doing.
Yep, depends on your learning style. I get a lot out of being lectured to, whereas others can do just as well reading a textbook on a subject. I can usually get the same information out of a book, but I pick it up a lot quicker during a lecture, then can get the details later on from the literature as necessary.
What's your opinion on this? I like embedded hardware, signal processing, and computational E&M. I would like to delve into at least 2 of the 3 topics. How would an advisor react to this?
My grad program had a 'breadth requirement' for courses, you had to take them from diverse groups (all Comp Sci though), their idea was to get breadth from courses, and specialize via thesis research. Makes sense, although it made me miss some good courses as auditing a course can quickly lose priority to other stuff. Similarly here, I think taking some other courses makes sense to make you more complete, but only if you're not going to delve into them too deeply, most m.sc/ph.d. oriented grad programs don't place much significance on courses anyway, at least that was the case with me.