COMP2310: Difference between revisions

From Hitchhiker's Guide to CS
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:COMP2310: Systems, Networks and Concurrency}}
{{DISPLAYTITLE:COMP2310: Systems, Networks and Concurrency}}


'''''NOTE:''' since this course in its current form was run by Uwe Zimmer who has left the ANU. Many aspects of the course may change in 2022 semester 2.''
'''''NOTE:''' this course has recently changed hands and is rumoured to change hands again. Many aspects of the course may change in 2022 semester 2.''


So far you’ve been writing self-contained programs, which solve a problem one step at a time. That’s cute, but if you want to interact with other programs running on different computers, use multiple cores to (safely!) improve performance, or write programs that interact with the physical world, you’ll have to start thinking differently.
So far you’ve been writing self-contained programs, which solve a problem one step at a time. That’s cute, but if you want to interact with other programs running on different computers, use multiple cores to (safely!) improve performance, or write programs that interact with the physical world, you’ll have to start thinking differently.
Line 7: Line 7:
2310 throws everyone in the deep end when it comes to this paradigm shift. The lectures are fast-paced and interactive, and the labs require a deep understanding of the content. Both are crucial for keeping on top of things and asking questions to the lecturer and the tutors - so skip either at your peril. Make sure to ask questions, or ask for help or clarification, as soon as you notice something doesn’t make sense.
2310 throws everyone in the deep end when it comes to this paradigm shift. The lectures are fast-paced and interactive, and the labs require a deep understanding of the content. Both are crucial for keeping on top of things and asking questions to the lecturer and the tutors - so skip either at your peril. Make sure to ask questions, or ask for help or clarification, as soon as you notice something doesn’t make sense.


Like 2300, this course has an oral hurdle in the week 4 labs. This follows the same structure as in 2300 - the tutors sit down with each student for a few minutes and ask questions about the content so far. Anyone who seems to be struggling is sent to the lecturer for a second interview.
Like [[COMP2300]], this course has an oral hurdle in the week 4 labs. This follows the same structure as in 2300 - the tutors sit down with each student for a few minutes and ask questions about the content so far. Anyone who seems to be struggling is sent to the lecturer for a second interview.


Otherwise, there are two assignments, and a midsem and final exam. Both assignments focus on managing distributed systems (in different ways). Usually a framework is provided in several languages for the second assignment.
Otherwise, there are two assignments, and a midsem and final exam. Both assignments focus on managing distributed systems (in different ways). Usually a framework is provided in several languages for the second assignment.

Latest revision as of 13:54, 9 January 2022


NOTE: this course has recently changed hands and is rumoured to change hands again. Many aspects of the course may change in 2022 semester 2.

So far you’ve been writing self-contained programs, which solve a problem one step at a time. That’s cute, but if you want to interact with other programs running on different computers, use multiple cores to (safely!) improve performance, or write programs that interact with the physical world, you’ll have to start thinking differently.

2310 throws everyone in the deep end when it comes to this paradigm shift. The lectures are fast-paced and interactive, and the labs require a deep understanding of the content. Both are crucial for keeping on top of things and asking questions to the lecturer and the tutors - so skip either at your peril. Make sure to ask questions, or ask for help or clarification, as soon as you notice something doesn’t make sense.

Like COMP2300, this course has an oral hurdle in the week 4 labs. This follows the same structure as in 2300 - the tutors sit down with each student for a few minutes and ask questions about the content so far. Anyone who seems to be struggling is sent to the lecturer for a second interview.

Otherwise, there are two assignments, and a midsem and final exam. Both assignments focus on managing distributed systems (in different ways). Usually a framework is provided in several languages for the second assignment.