Long-term takeaways: test first, test during, test after, test, test, test when designing algorithms, demand the weakest capabilities (e.g. iterable vs. indexable) when designing containers, provide the strongest capabilities (e.g. indexable vs iterable) build decorators on top of containers, iterators, and functions utilize the benefits of being lazy (i.e. yield) always look for reuse and symmetry in your code collaboration is essential to the quality of your code and to your well-being in producing it How well do you think the course conveyed those takeaways?

What did you do this past week? I finished planning phase III with my team and started working on my tasks. I didn’t do to much SWE work so will have to catch up a bit. What’s in your way? The rest of this project, midterms, other projects, and a 2-day road trip this week. What will you do next week? Finish phase III soon, which on my end means implementing the two user stories and some cleanup.

What did you do this past week? This week my team finished Phase II of the project and are likely to start Phase III very soon. What’s in your way? I have lots of work assigned by other classes and a second wave of midterms is on the way. What will you do next week? Plan and work on Phase III and other projects. If you read it, what did you think of Ethical CS?

What did you do this past week? I completed midterms for this and other classes. I also finished more of my tasks for the project including setting up our database, messing with UML, and creating the groundwork for the UI tests. What’s in your way? Nothing for now, but soon assignments and projects that will inevitably be assigned by other classes. What will you do next week? I will finish the few remaining phase 2 parts of the project and begin planning with my group what we will do for phase 3.