Sean Munson
smunson at uw dot edu
Office hours: M 2:30-3:15p & by appointment
Korn Toongtong
visava at uw dot edu
Office hours: TBD & by appointment
In HCDE 310, we cover identifying opportunities and building interactive systems to solve problems in human centered design & engineering.
We will use the Python programming language, with some of the initial few weeks devoted to reviewing programming concepts and introducing Python's syntax. Over the quarter, you will specify, design, build, and justify design solutions in terms of user experience and technical design choices.
This course has been designed for students with some prior programming experience — such as CSE142 or CSE140 — though it is okay if you are not comfortable or confident with that prior experience. Weekly assignments provide a venue for applying programming concepts. Assignments will focus on data manipulation and the creation of small applications that leverage data and computational resources from larger, publicly available sources. The course culminates in a final project.
If you have substantial prior programming experience, some of this course — particularly the few weeks on key programming concepts — will likely be review. Compared to other UW courses that involve programming, HCDE310 will focus on developing good practices for pulling, processing, and presenting web data, and on building interactive applications using that data.
If you are concerned that you'll be bored with the weekly assignments, there is an option to opt out of weekly assignments (but not the exam!) and work on a larger project in their place. If you think this is right for you, please read this page and then come talk with me.
This course focuses on identifying technical opportunities to build interactive sytems, translating those ideas into application designs, and then building prototypes of those applications. You will gain experience with computer programming, data processing, and software design skills. While other HCDE courses will focus on design from the user, interaction, and visual perspectives, HCDE310 will focus on leveraging existing technical resources to build systems that solve human problems or to enable new activities. You will learn to specify, justify, and build technical systems.
This course should be good preparation for building prototypes of the systems you design in future HCDE classes, for processing data you get from user logs or from surveys (again, useful for other HCDE courses and directed research groups), as well as for the more technical components of courses like HCDE 411.
In the information age, these skills are essential, irrespective of the degree you plan to pursue. Students planning to do work that requires data analysis is required are likely to pick up valuable life-long skills.
We'll be using Python. If you have previously taken CSE142, you'll find that Python is a bit different than Java. Compared to Java, Python is flexible and lets you get away with a lot; this can be wonderful for some and unnerving for others. For example, in Python, the following can be typed and immediately executed:
2 + 3You get
5 printed out as the answer. In C++, the corresponding program has multiple lines and they require much more explanation.
Python is a wonderful language for general applications and prototyping. It has been used extensively for data analysis (more flexible than spreadsheets), data plotting, building dynamic web sites, games, etc. It is used in many organizations, companies, and applications, incuding NASA, Mozilla, Yelp, Pinterest, Path, Reddit, the National Labs, Google (in fact, Google hired the developer of Python), Eve Online, and Civilization IV.
While all computer languages can largely do all tasks that other computer languages can do, sometimes one language is better than another for a specific task (e.g., C programs often provide better performance but Python programs take less time to write and can be more reliable). Thus, it is useful to be exposed to multiple languages if you are going to take multiple computer science classes. Recruiters often look for experience in a variety of languages. Python is a great language to learn. You will find it to be a very versatile language with a good developer community and many resources available that you can use to continue to learn.
It is important that you keep up with the assignments and that you seek help — from the teaching team or your classmates — if you are struggling.
At the end of this course, students should be able to:
We will build these systems using the Python programming language, and so you will also review or learn the following specific programming skills:
Use the two books as references. Zelle is better to get a quick overview of the language. Downey's book is better when it comes to understanding the details. We will refer to both books during the course and point to the readings from the two books. In general, there is significant overlap in the material between the books. We will generally have required reading from one book and optional reading from the other one. Memorization is not required in this course.
The instructional team is supporting a virtual environment in which you will edit programs and run them. For instructions, see the Virtual Machine setup page on Canvas.
As an alternative, you may choose to install Python and a text editor natively on your laptop. It's definitely doable and, for some, preferable. But weeks into the quarter I was finding strange differences in the environments students had set up, and it was very hard to help them when things didn't work as expected.
The instructional team is supporting only the VMWare/Mint environment this quarter. If you try to run things natively, you're on your own for tech support.
If you do decide to do things on your own, we suggest NotePad++ on Windows and TextMate on Mac for editing Python programs. We also like PyCharm if you want an IDE. Standard text editors, such as Notepad or TextEdit, are not good, though they can be used in a pinch. Word processing programs like MS Word will not work because they add lots of unwanted formatting characters.
We will show you how to run your Python programs from a command-line and to edit and debug using Eclipse.
If you have something of a private nature that you don't want to share with the other students, feel free to send a message to one of us individually.
You should bring your laptop to each class session. In class, we will mix lecture, lab, homework, and project time -- you will need your laptop to work on this. Following along with the code in the lecture portions may also help you learn faster.
You may refer to the HCDE laptop policy. If your laptop crashes or you forget yours one day, you can check out a laptop from CSS in Kane Hall for short term use.
The first time you learn technical material it is often challenging. We are going to cover a wide range of topics in the course and we will move quickly between topics. Because it is our goal for you to succeed in the course, we encourage you to get help from anyone you like, especially in the portion of the course before the midterm and even for the completion of assignments.
However, you are responsible for learning the material, and you should make sure that all of the assistance you are getting is focused on gaining knowledge, not just on getting through the assignments. If you receive too much help and/or fail to master the material, you will crash and burn at the exam when all of a sudden you must perform on your own. The final submission of each assignment must be in your own "words."
If you receive assistance on an assignment, please indicate the nature and the amount of assistance you received. If the assignment is computer code, add a comment indicating who helped you and how. Any excerpts from the work of others must be clearly identified as a quotation, and a proper citation provided (e.g., in the comments of the code if it is a code fragment you have borrowed). If you are a more advanced student and are willing to help other students, please feel free to do so. Just remember that your goal is to help teach the material to the student receiving the help. It is acceptable for this class to ask for and provide help on an assignment via the course discussion site, including posting code fragments. Just don't post complete answers. If it seems like you've posted too much, one of the instructional staff will contact you to let you know, so don't worry about it.
Course conduct is governed by the University of Washington Student Conduct Code and the College of Engineering Academic Misconduct Policy. You should also acquaint yourself with the HCDE Plagiarism Policy.
To reiterate, the collaboration policy is as follows. Collaboration in the class is encouraged for assignments — you can get help from anyone as long as it is clearly acknowledged. Collaboration or outside help is not allowed on exams, though you will be allowed to use the book or any other resources for portions of them (including Google and web). Use of solutions from previous quarters is not allowed. The authorship of any assignments must be in your own style and done by you, even if you get help. Any significant help must be acknowledged in writing.
I like a relaxed classroom where everyone feels comfortable. You are welcome to bring drinks or snacks to class (assuming it is allowed in the room we are in). You can (and should) bring your laptop to class. I would rather have you come to class and listen with one ear than not come to class at all. As a courtesy to others, be sure to put your phone on silence/vibrate. Coming late to and/or leaving early from class is okay, as long as you don't disturb your classmates. Ask questions at any time, and if you have some expertise in a particular topic, please to raise you hand and share it with the class.
Our primary purpose in the classroom is to interact and learn from each other. While non-participation (sleeping; checking email) is permitted, we urge you to consider its impact on your fellow students. Class is a lot more fun when everyone is engaged; a few visibly disengaged people can suck the energy out of a room. We reserve the right to ask you a question to try to reengage you if you seem to have checked out, but will try not to do this in an embarrassing way.
There will be assignments throughout the course (pretty much every week and sometimes mini exercises during a lecture). Regular assignments allow you to learn the material in small "chunks" and to keep a close eye on how well you understand the material. In some cases, we will do part or all of the assignments during a lecture, though you will submit it later.
Generally, part of the sessions will be lab time. The teaching staff will be there and will circulate. You can confer with other students and the instructors. This is a great time to work on assignments, and you may be able to finish the weekly assignment in the lab — but don't count on it. The previous assignments are typically discussed in the class and we like some time to review your submissions. For this reason, late assignments will receive a zero. You can submit late assignments to get feedback, but no points will be given for an assignment that is turned in after the deadline, unless you have made prior arrangements.
There will be one project in the last 4-5 weeks of the quarter, where you bring all the skills you have learned to one significant problem solving task. You will learn debugging skills, modularity skills, and testing skills. We think the project will be interesting to do and help you pick up life-long problem solving skills that will be useful even beyond programming.
As a supplement to the project, you will write up a description of an interesting data source or API that other students might want to use in their final project, or an interesting python module or package. More about this later in the quarter. You are free to use any online module or package to talk about, but one list of many of the Python modules can be found at: Python Global Module Index.
There will be one exam, most of the way through the course. The first part is a traditional written exam intended to measure mastery of the course material, including programming knowledge; the second is a practical exam, intended to measure programming skills. The exam will be administered during class to allow approximately 2 hours. The exam date is announced well in advance (see the dates at the end of this document). If you have a conflict, please let me know at least 2 weeks in advance so that I can arrange a different time for you.
There's a chance that I will decide to add in-class quizzes to supplement the exam; if so, the quizzes will be announced in advance.
Class participation, helping others, interacting on the email list and answering questions, asking good questions that lead to interesting discussions, and pointing out corrections to lectures or code will contribute to bonus points, which you can use to help boost your grade.
In addition, there are optional challenge problems at pythonchallenge.com. I encourage you to try to solve the problems there when you have time and discuss approaches or even code on the email list — that all contributes to class participation points. If you are not able to solve them initially, don't worry. Treat them as optional and fun part of the course. The good thing about the Python challenges is that once you submit a solution to a challenge, you can see several solutions to the previous challenge. It is a learning experience to see how other people approached the same problem.
If you think you need an accommodation for a disability, please let us know at your earliest convenience. Some aspects of this course, the assignments, the in-class activities, and the way we teach may be modified to facilitate your participation and progress. To request accommodations due to a disability, please contact the Disability Student Services Office at 206.543.6450 (voice), 206.543.6452 (TTY), 206.685.7264 (fax), or email at dso@u.washington.edu. If you have a letter from the DSS office indicating that you have a disability that requires academic accommodations, please present the letter to me so we can discuss the accommodations that you might need in this class.
The graded work in the course will be weighted roughly as follows to determine a final percentage grade. (Note that bonus points could allow you to get above 100%):
| Weekly Assignments | 40% |
| Project: | 30% |
| Python module/package or data source writeup ("resource writeup") | 5% |
| Exams: (I reserve the option to add quizes, which will reduce exam's weight) | 25% |
| Class Participation: | ±5% |
Also see the HCDE grading policy.
The course effectively consists of two parts. In the first part we march through Python in quick fashion; this is largely reviewing and strengthening your knowledge. In the second part, we will focus on data analysis and other applications. We will keep some flexibility in the schedule. If it seems like we need to spend more time on a particular topic, we will shuffle the schedule. It is important for you to let us know when you are having problems. This will help us pace the material appropriately, cover some material in greater depth, and revisit material if necessary.
The course is designed for students with limited programming experience (e.g., CSE142). If you stick with the course and invest the necessary time, you will be amazed at how much you will learn in 10 weeks and at the doors opened by developing your familiarity with programming and computational thinking.
If you do not have a lot of programming experience, some concepts may take some time to sink in. Do not worry too much if you feel like you are in a fog at times. The assignments are the best way to track your progress through the material.
Usually the biggest problem students encounter in the course is trying to do everything in a few hours right before an assignment is due or right before an exam. If you only think about the course a few hours each week, you will get some of the details but they will not mesh together to provide the big picture. Programming is easy once you get the big picture. The textbook will become an easily scanned reference for you once you know what to look for and why you are looking for it.
Cramming does not work well when dealing with the material in this course. This is because the material in the course is actually fairly straightforward once you "get it" — once you understand some basic principles. No amount of memorization will make up for not having the big picture. Try not to get stuck on any one thing; it is all easy once you "get it." If you do get stuck on something and feel like you are going in circles, ask for help, look at something else, or come at the problem from a different direction. Remember that exam is open notes, and open book for the practical portion.
Good luck and welcome aboard!
| Week | Dates | Topic | Suggested Reading (complementary in parens) | Homework |
|---|---|---|---|---|
| 1 | Sept 30 | Introduction to the Course, Computers, and Python. |
Zelle ch 1 Downey ch 2, 6-7 |
HW0: SW installation; basic string operations |
| 2 | Oct 5, 7 |
Operations on strings and lists. Iteration on sequences. File operations. Version control. |
Zelle ch 3 Zelle ch 7 Zelle 4.5 (Downey ch 5) |
HW1: Count chars, words, lines in a file; setting up a git repository. HW2: File operations. |
| 3 | Oct 12, 14 |
Conditionals Dictionary data structure Functions. Parameter passing and returning values Mashups & APIs |
Zelle ch 3 Zelle ch 7 Zelle 4.5 (Downey ch 5) |
P0: Find an interesting API HW3: Contributor counts |
| 4 | Oct 19, 21 |
Indefinite iteration; nested data structure, and nested iteration JSON processing Introduction to Objects Ideation & Prioritization |
Zelle ch 6 “The Art of Brainstorming” |
HW4: Do more than HW3, with less. Output as .csv files; generate charts in Google Docs, Excel, or D3 P1: Adding value to data |
| 5 | Oct 26, 28 |
Objects and Classes Mid-quarter course feedback URL lib; Try/except; |
Zelle ch 8 Zelle ch 10 Tutorial on urllib2; |
HW5: Calculate likes and comment frequencies from a JSON feed, use classes |
| 6 | Nov 2, 4 |
REST APIs Sorting List comprehensions |
List comprehensions: Wikipedia; another explanation w/ nice examples |
HW6: Fetching and processing a live feed. |
| 7 | Nov 9 No class 11 November |
Google App Engine Intro Note: Sean away 11-15 November |
Severance ch 2; CSS tutorial |
P2: Project proposal. HW7: APIs, Sorting, more data processing. |
| 8 | Nov 16, 18 |
16 Nov: HTML & CSS (briefly), Jinja Templates, working with forms in App Engine. 18 Nov: API Data in App Engine. Review time. Bring questions. |
Review — exercises from books. | HW8: App Engine & APIs Review |
| 9 | Nov 23, 25 |
23 November: Exam in class 25 November: Lab day |
||
| 10 | Nov 30, 2 Dec |
30 Nov: App Engine & OAuth 2 December: App engine Datastore |
||
| 11 | Dec 7, 9 | TBD Map-Reduce |
Map-Reduce: tutorial (don't worry too much about the syntax), App Engine Overview |
R1: Resource writeup |
| F | Dec 17 2:30-4:20p |
P3 & P4: Final projects due / presentations |
This course is based on SI/EECS182 at the University of Michigan, which I redesigned with Paul Resnick in Winter 2009. Chuck Severance, Eytan Bakshy, and Atul Prakash have substantially improved the course before and since, and I have included many of their innovations in this syllabus.