For several reasons I use this site rather than Blackboard, this Wiki page will host all class material, including:
I started writing an introduction to programming book some years ago, and while I haven't gotten around to finishing it, some other classes have found it a useful supplement to the class lectures, particularly for people just starting with programming. For that reason I'm making the current (very incomplete) draft of the book available to you:
Note that this class now uses Python 3.5 via a free distribution called Anaconda available for Linux, Max and Windows. By using a common environment, it is easier to deal with the differences between Python on different platforms. The default Python available on Linux and Mac is still Python 2.7. Please make sure you set up Anaconda 3.5 and use that instead.
The class project will count for 1/2 of your grade in the class, and will be scored on both your presentation and the program itself. You will likely have only ~5 minutes to present your projects when the time comes, but that shouldn't limit their complexity or your ambitions. It is a good idea to select a project which is somewhat ambitious but has some fallback positions in case you don't succeed in everything you had planned to do. Your initial project plan will not be a factor in your final grade. If the program meets the criteria below, even if it's very different than your original aim, you will still receive full credit.
Each person will, over the course of the term, write a program, and briefly present it at the end of the term. The sole requirements for the program are: 1. It must do something useful not easily completed with existing freely available tools 2. Not be completely trivial. The complexity of your project is expected to correspond somewhat to your level of past programming experience.
This class attracts people with widely varying backgrounds and skill levels. Since the course is supposed to be accessible to people with little to no programming experience, the bar for achieving an acceptable grade (B) in the class is set fairly low. If you make a reasonable attempt at all of the homework assignments, even if not completely successful, and complete a class project of some sort, you can expect to get at least a B in the class. This does not mean you can slip through without making an effort at all. Particularly if you have no programming experience at all, the class WILL take a significant effort on your part. Those who don't make a reasonable attempt at virtually every assignment may not achieve a B. Turning in something incomplete is better than turning in nothing.
Homework will be assigned each class, due before the next class, at least for the first 2/3 of the term, and is handed in via email to the class TA, James (Michael) Bell James.Bell@bcm.edu, with a cc to sludtke@bcm.edu. We will go over solutions to homework assignments in-class. Since the class is offered for credit, homework will be graded, but on a lenient scale:
3. Homework turned in, something attempted, but not functional 4. A good effort, but with major flaws 5. Largely correct solution, but with some flaws 6. Program does what it should, with minimal flaws
Auditors are welcome, but if possible (all students, and some others) please formally audit the class, rather than just showing up. 1) this means you have at least a small commitment to actually attend and 2) if you don't formally audit, the GS has no record of your interest and they may give me a very small room to teach in next time (not that we need N315).