Editing Software Engineering (Fall 2025) (section)

== Note about this Syllabus ==

You should expect this syllabus to be a dynamic document (not a 'contract'). Although the core expectations for this class are fixed, the details of projects, readings, and assignments ''will'' shift based on how the class goes, guest speakers that I arrange, my own readings in this area, etc. As a result, there are four important things to keep in mind:

* Although details on this syllabus will change, I will try to ensure that I never change readings more than six days before they are due. This means that if I don't fill in a reading marked "{{tbd}}" six days before it's due, it is dropped. If I don't change something marked "{{tentative}}" before the deadline, then it is assigned. This also means that if you plan to read more than six days ahead, contact me first.
* Because this syllabus is a wiki, you will be able to track every change by clicking the history button on this page when I make changes. I will summarize these changes in the weekly announcement on Canvas] sent that will be emailed to everybody in the class. Closely monitor your email or the announcements section on the course website on Canvas to make sure you don't miss these announcements.
* I will ask the class for voluntary anonymous feedback frequently — especially toward the beginning of the quarter. Please let me know what is working and what can be improved. In the past, I have made many adjustments to courses that I teach while the quarter progressed based on this feedback.
* Many readings are marked as "''[Available through UW libraries]''". Most of these will be accessible to anybody who connects from the UW network. This means that if you're on campus, it will likely work. Although you can go through the UW libraries website to get most of these, the easiest way to get things using the [https://www.lib.washington.edu/help/connect/tools UW library proxy bookmarklet]. This is a little button you can drag-and-drop onto your bookmarks toolbar on your browser. When you press the button, it will ask you to log in using your UW NetID and then will automatically send your traffic through UW libraries. You can also use the other tools on [https://www.lib.washington.edu/help/connect this UW libraries webpage].
<!--
=== Special Note for Online Synchronous Course Delivery ===

Online courses can seem easier than face-to-face courses, but they are in some ways more challenging. 

Showing up in a classroom means you set aside time to travel and be present, and you find yourself surrounded by others who have made the same commitment. This generates a shared context that nudges us towards engaging, and the more we engage, the more we benefit, in an upward spiral. Online courses seem attractive for their flexibility, but can pose a downward spiral: we must wrangle our own technology and a silent place from which to attend and push ourselves to focus. Instead of being surrounded by other students who have made the same commitment to attend, we are surrounded by distractions: a stocked fridge, a pile of laundry needing attention, a cozy bed, and friends and family who are perhaps not on the same schedule. It becomes easy to disengage, and the less we engage, the less benefit we receive from the course.

To fight this downward spiral, we must make a plan. My commitment to you is that I will hold you accountable to engage in class work, I will work to keep class lively and interactive, and I will offer breaks. Your commitment to yourself and to our class as a learning community needs to be that you will come to class ready to engage and work. That means, with microphone and headset functioning, fingers at the keyboard, with class prep work complete (including readings, videos, code, etc.) The more you engage, the more you will learn from this class, and the more you will enjoy it!
-->
<!-- == Organization ==

This course addresses topics at macro, meso, and micro levels. We'll start broad, work our way down through middle layers to a detailed level, and finish the quarter by stepping back up to a macro layer again. My style of teaching is to infuse historical perspectives, current research, security, and ethics into each topic, although the total clock-time of each of these elements will vary.

=== Theme 1: Macro ===
* Software Development Lifecycle
* Collecting and Evaluating Evidence
* Systems, Infrastructures, and Supply Chains

=== Theme 2: Meso ===
* Patterns for Organizing Work
* Patterns for Design and Architecture

=== Theme 3: Micro ===
* Metrics
* Tools
* Tactics
-->