Hi everyone,
I want to raise some serious concerns about CSE 442, particularly the course content, grading, and the way it is managed by Professor Matthew Hertz.
Frankly, I find much of what we are being taught outdated and disconnected from the reality of modern software development.
We are living in the age of AI, yet CSE 442 still places enormous emphasis on traditional web development workflows and tedious implementation details. With AI tools fundamentally changing how software is built, spending so much time on repetitive, low-level development processes feels increasingly pointless. Instead of focusing on modern engineering practices, AI-assisted development, system design, or building meaningful software products, we are often stuck dealing with trivial procedural requirements.
The excessive attendance check-ins, lectures of questionable practical value, and assignments filled with unnecessary implementation details only make the situation worse. Many of these tasks feel like busywork rather than meaningful learning experiences.
Another major concern is grading.
I've heard concerns about students who perform well in other upper-level CSE courses but struggle to earn reasonable grades in CSE 442. Students can end up spending an extraordinary amount of time just trying to secure a B or higher, often at the expense of other coursework, research, internships, and professional development.
I've also heard of students taking this course twice or even three times. If these experiences are as widespread as they appear to be, we need to seriously question whether the course's workload, grading standards, and learning objectives are appropriately aligned.
A software engineering course should challenge students to become better engineers, not force them to spend disproportionate amounts of time navigating procedural requirements just to earn an acceptable grade.
To be clear, the problem isn't that web development itself is useless. The problem is how much time we spend on outdated workflows, insignificant implementation details, and administrative requirements without a clear educational purpose, particularly when more relevant skills could be taught.
Students deserve a course that respects their time, uses transparent and reasonable grading standards, and prepares them for modern software engineering.
We are currently working to bring these concerns to the attention of the CSE Department Chair, and we want to hear from as many current and former CSE 442 students as possible.
If you've experienced similar issues, please share your experiences in the comments or DM me privately. We're especially interested in:
- Unreasonable workloads or grading expectations
- Difficulty earning a B or higher despite strong performance in other CSE courses
- Having to retake CSE 442 multiple times
- Excessive attendance requirements and unnecessary assignments
- Outdated course content and inefficient course management
Specific examples and firsthand experiences would be especially helpful. Our goal is to collect student feedback, document these concerns, and advocate for meaningful improvements rather than attack anyone personally.
CSE 442 should be a valuable learning experience, not an unnecessary obstacle to graduation.
If you share these concerns, please speak up. The more students who participate, the stronger our collective voice will be.