Fall '26 Week 4

Resources

• Slides

Edited Transcript

00:00 Hello and welcome to the week four announcements video for CC 410 in fall 2026. So this week you should be wrapping up the second restaurant milestone, which is all about documentation, unit testing, and adding a UML diagram for your project. Hopefully that’s going well. This one is definitely one of the milestones that I spend a lot of time grading and giving feedback on the style and content of your unit tests. So just be aware that it may take me a couple of days to get all the feedback put in. But as always, if you have any questions or concerns or anything, please let me know. So as far as grading in this class, hopefully you saw with the first milestone. What I do is I fill out a rubric in Canvas that has the point values. And then for anything I think I need to leave detailed feedback for, I make feedback in the feedback pull request in GitHub. That pull request we’re going to use throughout the semester. So don’t merge that pull request after you read through the feedback. Just leave it as is, and I’ll keep adding to it. And then one other big thing for these milestones is remember to make use of talks and especially MyPy to test all of your code.

01:03 You also now have unit tests that you can run. And then at the end of the next milestone, you should be running your style checker and your documentation tool, just like we did for the Hello real world project. So make sure you’re doing those things. A lot of students miss points on these projects because the my pie does not pass a type check. So make sure that you’re working on that and checking all of those things. This week, we’re going to shift gears a little bit, we’re going to talk a little bit about inheritance and polymorphism, which are some of the cooler features of object-oriented programming. You’ll do a quick example to explore some inheritance, and then you’ll also have a chance to do a start-stop-continue survey. It’s just a very informal teaching evaluation for me. It gives you a chance to say one thing you’d like me to start doing that I’m not doing, one thing you’d like me to stop doing that I am doing. And one thing you’d like me to continue doing because you like that I do it. I take all of that into account. I may not always be able to do the things you ask me to do, but I do read all of that feedback and I do consider it very carefully. You’ll also have some time this week to think about your final project and maybe start ideating some project ideas because we’ll meet again here in a couple weeks to actually talk about your final project in this class. So coming up next after this, we’re going to have another example on debugging, logging, and lambda expressions. You’ll do a quick logging example. One thing I will tell you is when you run the debugger in Codio, there is an error. You can just ignore that error. The only thing is instead of being able to see your local variables, you’ll have to create watch expressions for those.

02:26 I believe the video shows how to do that, but it should be pretty straightforward. So you can just ignore that Codio error that you get when you launch the debugger. Then you’ll work on the third restaurant project, and you’ll also be scheduling your second final project check-in. So other big thing to remember for milestone three that’s going to be due, not this week, but next week, is that we’re going to require all the general requirements, which means you’ll need to add unit tests, do an updated UML diagram, you’ll be refactoring some classes. This milestone is a lot smaller than the other two milestones, but it’s a lot more involved because you’re making a lot of little delicate changes to the code so that you can refactor it and make the new and inheritance parts take place. As always, with all the assignments in this class, if there’s anything unclear, feel free to ask me questions. I’m always open to feedback on ways that I can make these assignments a little bit clearer as you go through them. So other big hint for milestone three, make sure you work in very small chunks. It’s very tempting to try and do everything in one shot. Maybe try and do just one thing. Maybe look at the sides or the drinks first and get that working before you start working on the rest of the project. Also make sure you’re committing early and often to GitHub. You might even try things like test-driven developments. So you’re actually writing your unit tests before you write your code. Another big hint that I always have to give people on this one is we have that item. I think we don’t call it order item anymore. I think we call it item.

03:43 We have that item interface that we’re going to create. You’ll inherit that on your base class. So like the base drink and the base side class, you won’t inherit that on each individual drink or side class. And then, of course, especially with this one, we’re doing some object-oriented programming in Python that may have some strange syntax. So if anything doesn’t make sense or doesn’t seem to work, feel free to ask me questions. I’d be happy to help you out. Looking ahead after this week, we’ve got some work on inheritance debugging, and then we’re going to talk about design patterns and test doubles, which I think are really important. That will get us through about mid-October when we’ll switch over and start talking about user interfaces and web APIs. Hopefully things are going well. It’s week four in the semester, so hopefully it doesn’t feel like everything’s on fire, but if it is, you just keep plugging away at it and you’ll get over it soon. As always, if you have any questions, please let me know. I’m always available to help answer questions in this class. Otherwise, best of luck and I will see you again next week.