<<O>>  Difference Topic CodeCritiqueSyllabus (r1.14 - 27 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 26 to 26

You will need to have daily access to the internet. I rely on email and the class’s online journal for communications and assignments, and you will be responsible for checking both regularly.

Deleted:
<
<
Class Schedule
TBD
 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.13 - 27 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 13 to 13

Required Materials
There are no specific required materials for the course, however you should have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie. Bring these to class.
Deleted:
<
<
A laptop computer that you can bring to class is recommended.

Requirements
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Java, Perl, PHP, Actionscript (Flash), JavaScript and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and pd (puredata). Layout languages such as HTML are not applicable. Check with me about other languages.
 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.12 - 27 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 24 to 24

We’ll need to be able to view the code on an overhead projector. Put the code on a website or server that I can get to. Or if the code is on your laptop, you need to make sure ahead of time that your laptop can be connected to the projector.

Changed:
<
<
I will assign reflective essays throughout the term. The essays will be short, typically around 256 words and shouldn’t take more than 32 minutes to write. You will post the essays in the class’s online journal by noon on the due date.
>
>
I may assign reflective essays throughout the term. The essays will be short, typically around 256 words and shouldn’t take more than 32 minutes to write. You will post the essays in the class’s online journal by noon on the due date.

You will need to have daily access to the internet. I rely on email and the class’s online journal for communications and assignments, and you will be responsible for checking both regularly.

Added:
>
>
Class Schedule
TBD
 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.11 - 27 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 28 to 28

You will need to have daily access to the internet. I rely on email and the class’s online journal for communications and assignments, and you will be responsible for checking both regularly.

Deleted:
<
<
Class Schedule
TBD
 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.10 - 25 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Bennington College
Joe Holt jholt@bennington.edu
Changed:
<
<
M 10:15 - 11:45 a.m.
>
>
M 10:30 - noon

VAPA Pod

In this two–credit course you’ll have a chance to workshop software that you’re working on. The software may be projects from another course or things you’re developing on your own, or a mix of the two. Are there better ways to do what you’re doing? What makes one version of an algorithm better than another? How do you keep your large program under control? When is it appropriate to spend time on optimization? How do you optimize for speed? We’ll look at your source code as it evolves over the course of the term and address these and other development issues. Intermediate programming experience required, most programming languages are acceptable.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.9 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 26 to 26

I will assign reflective essays throughout the term. The essays will be short, typically around 256 words and shouldn’t take more than 32 minutes to write. You will post the essays in the class’s online journal by noon on the due date.

Changed:
<
<
You will need to have daily access to the internet. I use email and the class’s online journal almost exclusively for communications and assignments, and you will be responsible for checking both regularly.
>
>
You will need to have daily access to the internet. I rely on email and the class’s online journal for communications and assignments, and you will be responsible for checking both regularly.

Class Schedule
TBD
 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.8 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 20 to 20

You may be asked to give the class a quick introduction to the language you're using.

Changed:
<
<
If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.
>
>
It’s okay if you bring in outside code once in a while. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

We’ll need to be able to view the code on an overhead projector. Put the code on a website or server that I can get to. Or if the code is on your laptop, you need to make sure ahead of time that your laptop can be connected to the projector.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.7 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 11 to 11

In this two–credit course you’ll have a chance to workshop software that you’re working on. The software may be projects from another course or things you’re developing on your own, or a mix of the two. Are there better ways to do what you’re doing? What makes one version of an algorithm better than another? How do you keep your large program under control? When is it appropriate to spend time on optimization? How do you optimize for speed? We’ll look at your source code as it evolves over the course of the term and address these and other development issues. Intermediate programming experience required, most programming languages are acceptable.

Required Materials
Changed:
<
<
There are no required materials for the course, however it’s good to have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie. Bring these to class.
>
>
There are no specific required materials for the course, however you should have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie. Bring these to class.

A laptop computer that you can bring to class is recommended.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.6 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 11 to 11

In this two–credit course you’ll have a chance to workshop software that you’re working on. The software may be projects from another course or things you’re developing on your own, or a mix of the two. Are there better ways to do what you’re doing? What makes one version of an algorithm better than another? How do you keep your large program under control? When is it appropriate to spend time on optimization? How do you optimize for speed? We’ll look at your source code as it evolves over the course of the term and address these and other development issues. Intermediate programming experience required, most programming languages are acceptable.

Required Materials
Changed:
<
<
There are no required materials for the course, however it’s good to have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie.
>
>
There are no required materials for the course, however it’s good to have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie. Bring these to class.

A laptop computer that you can bring to class is recommended.

Requirements
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Java, Perl, PHP, Actionscript (Flash), JavaScript and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and pd (puredata). Layout languages such as HTML are not applicable. Check with me about other languages.
Changed:
<
<
You may be asked to give the class a quick introduction to the language you’re using.
>
>
You may be asked to give the class a quick introduction to the language you're using.

If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.5 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 18 to 18

Requirements
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Java, Perl, PHP, Actionscript (Flash), JavaScript and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and pd (puredata). Layout languages such as HTML are not applicable. Check with me about other languages.
Changed:
<
<
You may be asked to give the class a quick introduction to the language you're using.
>
>
You may be asked to give the class a quick introduction to the language you’re using.

If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.4 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 16 to 16

A laptop computer that you can bring to class is recommended.

Requirements
Changed:
<
<
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Pascal, Perl, PHP, Actionscript (Flash), JavaScript and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and pd (puredata). Layout languages such as HTML are not applicable. Check with me about other languages.
>
>
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Java, Perl, PHP, Actionscript (Flash), JavaScript and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and pd (puredata). Layout languages such as HTML are not applicable. Check with me about other languages.

You may be asked to give the class a quick introduction to the language you're using.


If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.3 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 16 to 16

A laptop computer that you can bring to class is recommended.

Requirements
Changed:
<
<
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Pascal, Perl, PHP, Actionscript (Flash), JavaScript? and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and Pd (Puredata). Layout languages such as HTML are not applicable. Check with me about other languages.
>
>
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Pascal, Perl, PHP, Actionscript (Flash), JavaScript and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and pd (puredata). Layout languages such as HTML are not applicable. Check with me about other languages.

If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.2 - 14 Feb 2006 - JoeHolt)

META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Line: 13 to 13

Required Materials
There are no required materials for the course, however it’s good to have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie.
Changed:
<
<
A laptop computer that you can bring to class is highly recommended.
>
>
A laptop computer that you can bring to class is recommended.

Requirements
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Pascal, Perl, PHP, Actionscript (Flash), JavaScript? and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and Pd (Puredata). Layout languages such as HTML are not applicable. Check with me about other languages.

If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

Changed:
<
<
We'll need to be able to view the code on an overhead projector. Put the code on a website or server that I can get to. Or if the code is on your laptop, you need to make sure ahead of time that your laptop can be connected to the projector.
>
>
We’ll need to be able to view the code on an overhead projector. Put the code on a website or server that I can get to. Or if the code is on your laptop, you need to make sure ahead of time that your laptop can be connected to the projector.

Changed:
<
<
I will assign reflective essays throughout the term. The essays are short, typically around 256 words and shouldn’t take more than 32 minutes to write. You will post the essays in the class’s online journal by noon on the due date.
>
>
I will assign reflective essays throughout the term. The essays will be short, typically around 256 words and shouldn’t take more than 32 minutes to write. You will post the essays in the class’s online journal by noon on the due date.

You will need to have daily access to the internet. I use email and the class’s online journal almost exclusively for communications and assignments, and you will be responsible for checking both regularly.

 <<O>>  Difference Topic CodeCritiqueSyllabus (r1.1 - 14 Feb 2006 - JoeHolt)
Line: 1 to 1
Added:
>
>
META TOPICPARENT CodeCritique
Code Critique
Spring 2006
Bennington College
Joe Holt jholt@bennington.edu

M 10:15 - 11:45 a.m.
VAPA Pod

In this two–credit course you’ll have a chance to workshop software that you’re working on. The software may be projects from another course or things you’re developing on your own, or a mix of the two. Are there better ways to do what you’re doing? What makes one version of an algorithm better than another? How do you keep your large program under control? When is it appropriate to spend time on optimization? How do you optimize for speed? We’ll look at your source code as it evolves over the course of the term and address these and other development issues. Intermediate programming experience required, most programming languages are acceptable.

Required Materials
There are no required materials for the course, however it’s good to have on–hand the reference manuals for whatever programming language and technologies you’re using. For example, if you’re using C then you should have a copy of The C Programming Language (2nd Edition) by Brian Kernighan and Dennis Ritchie.

A laptop computer that you can bring to class is highly recommended.

Requirements
You will need to bring to class a section of code to critique every week. Preferably the code will be a project that you’re working on. The code may be written in just about any programming language. For example, C, C++, Objective–C, Pascal, Perl, PHP, Actionscript (Flash), JavaScript? and Visual Basic are acceptable, as well as graphical languages such as Max/MSP and Pd (Puredata). Layout languages such as HTML are not applicable. Check with me about other languages.

If you can’t bring your own code one week, third party (open source) code will be accepted. Perhaps you saw some code online that you’d like to discuss. For most of the course, however, the code should be your own.

We'll need to be able to view the code on an overhead projector. Put the code on a website or server that I can get to. Or if the code is on your laptop, you need to make sure ahead of time that your laptop can be connected to the projector.

I will assign reflective essays throughout the term. The essays are short, typically around 256 words and shouldn’t take more than 32 minutes to write. You will post the essays in the class’s online journal by noon on the due date.

You will need to have daily access to the internet. I use email and the class’s online journal almost exclusively for communications and assignments, and you will be responsible for checking both regularly.

Class Schedule
TBD
Revision r1.1 - 14 Feb 2006 - 07:16 - JoeHolt
Revision r1.14 - 27 Feb 2006 - 08:37 - JoeHolt