2/5 Is CS 162 considered one of the more difficult UCB CS courses? I
remember everyone being afraid of CS 150.
\_ In the old days, 150 was a pain in the butt because of breadboards.
One can easily spend 1/2 a day only to realize a wire is
missing or popped off during transport. The fact that you gotta
wire everything based on TTL/CMOS chips and having to go through
cookbooks, makes it a total pain and error prone. Nowadays,
CS150 is done mostly via Xilinx tools. You use some tool to
wire components, then let the compiler route, then program
your FPGA, and voila! Well, it's not THAT simple, but at least
much more pleasant than breadboards. So, yes 150 used to be the
project everyone feared. Nowadays, 162 is THE feared project
as well as 164.
as well as 164. -TA who taught during the breadboard
to new Xilinx tools transition during the
mid-90s when the tools really sucked back
then but has improved a lot since then.
\_ Wow you guys are wimps these days. Esp. if you fear 164.
Unless things have changed dramatically in the last say,
5 years, which I doubt.
\_ It's "more difficult" in the sense that the project is more work
than the typical CS class. Same with 150, though projects there
probably are even more work than 162, esp. since the groups are
smaller.
\_ 162 was a lot of work, but it seemed to flow together logically.
It wasn't that hard, but it was time consuming. For some people
in my class it was pretty obvious they never "got" it, but really
those people should have taken it as a sign that they needed a
new major.
\_ From my ancient experience (15 yrs ago) CS 150 was much more
difficult than any other CS class by a LOT.
\_ Difficult because it was TIME CONSUMING. Not as theoretically
difficult as theory or math, for example. Who taught 150
15 years ago?
\_ Difficult both by the subject matter and the insane
amount of time you had to invest
\_ Wow, I remember it as 160. The projects were big, especially if
your group bailed on you. However, when I took the class, we used
NACHOS, not BSD. |