• Structure and Interpretation of Computer Programs—2nd Edition . This is the home page for the textbook. Here you can find supporting material for the text, some errata, and other information.
• I often am asked for information on Unix and the basic Unix utilites. I highly recommend the following book:

          Unix for the Impatient (Second Edition)
  	by Paul W. Abrahams and Bruce R. Larson
  	Addison-Wesley, 1997
  

  The book comes with a CD that you might find useful as well. It covers the basics of the typical Unix environments, and also gives a nice short introduction to the Emacs editor, which you should absolutely learn now if you haven't yet—see the note above. To find the best price for this book, go to http://www.addall.com and search for it.
• Basic Unix tutorial. This tutorial was written by Glenn Hoffman from our department, and it has a lot of useful information about our Unix system.

A Note About Written Work (Adapted from Prof. Carl Offner)

An important part of this course is for you to begin to learn how seasoned engineers design and implement projects. To do this, they have to communicate clearly with each other. In almost every assignment, I will ask you to write down some explanations, some thoughts on design, or something similar. I expect these essays to be written clearly, so that I can understand what you are saying. Remember—it is not my job to guess what you mean, any more than it is the computer's job to guess what your programs mean. A significant part of your grade in this class will be determined by this written work.

In particular, you should always run a spell-checker on your written work, and you should look it over for proper grammar and usage. I am going to be pretty serious about this. Spelling errors are easy to catch with a spell checker, and I expect you to use one. A spell checker cannot catch all possible mistakes (e.g. then vs. than, it's vs. its etc.), but I expect you to do your best. When in doubt, google is your friend.

Also, this is written work, not text messaging to your buddies. "u" is not how you spell "you". "2" is not how you spell "to". "thanx" is not how you spell "thanks". You want to be a professional; here is the time to start writing like one.

I understand that there will be students in this class whose first language is not English. I feel your pain, English is my second language as well, but I will do my best to help each of you in any problems you may have expressing yourself clearly—just come to my office hours or send me email, and I'll be glad to help as much as I can.

Gradescope only accepts pdf uploads. You may use any editor, as long as you figure out how to convert to pdf.

Accommodations:  Section 504 of the Americans with Disabilities Act of 1990 offers guidelines for curriculum modifications and adaptations for students with documented disabilities. If applicable, students may obtain adaptation recommendations from the Ross Center for Disability Services, Campus Center, UL Room 211, (617-287-7430). The student must present these recommendations and discuss them with each professor within a reasonable period, preferably by the end of Drop/Add period.

Student Conduct:  Students are required to adhere to the University Policy on Academic Standards and Cheating, to the University Statement on Plagiarism and the Documentation of Written Work, and to the Code of Student Conduct as delineated in the catalog of Undergraduate Programs. The Code is available online at: http://www.umb.edu/life_on_campus/policies/code/

In particular, see note about honesty