You can get 2 extra credit points by thoughtfully and reflectively filling out this peer- and self- evaluation and emailing it to me with subject line “CPSC 240 peer- and self- evaluation turn-in.”
If you liked the Blueprints textbook this semester, I’d sure appreciate an Amazon review! (Note: I get no royalties from sales of this book; I’m just trying to make it as widely available as possible for as low a cost as possible.)
I mentioned in class a useful tool for compiling statistics on a git repo, so you can tell who wrote how many lines, who the main contributors were to each file, and so forth. To do this:
- Run “sudo apt-get install gitinspector” on your Google Cloud, give your password when prompted, and say “Y” for “yes I really want to install this” when prompted.
- From anywhere in your git workspace, type: “gitinspector -rwH” and you’ll see output like:
Author Commits Insertions Deletions % of changes Tony Stark 50 657 193 18.03 Natasha Romanova 36 913 115 21.81 Bruce Banner 72 2216 620 60.16
and other useful tidbits.
Michelle mentioned on the last day of class that she’s put together some of her notes on the parallelism/concurrency material, and is willing to share those with the class. So here they are!
Disclaimer: I make no promises that everything written in here is complete or correct; I can only vouch for Michelle being a generally cool and smart gal. So I share her notes with you in case you find them useful.
The final exam has been posted to Canvas, and will appear in the “Files” tab at noon tomorrow.
A few very important notes:
- I don’t want people to be overly stressed about the time, so I made the time limit 4 hours instead of the original 2½. This does not mean I actually expect it to take you that long; I just want to err on the safe side.
- Do keep up a good pace. There are some hard and/or long questions, and I’m confident you’ll be able to get through it all if you stay focused. But don’t let yourself get dragged down into any mental rat holes.
- Do not look at the exam until you’re ready to print it and take it. Once you download the file and open it in your PDF reader, your timer starts!
- Finally, we talked today on Zoom about typing your answers instead of writing them. That’s fine, I still agree to let you do that. But just to be crystal clear, even though you will be typing some code, you are NOT allowed to compile it or run it! It would probably be best for you to type your code in Word or Google Docs, instead of in vim or Eclipse/NetBeans/IntelliJ, just to avoid the reflex temptation to compile regularly as your type (which of course is what you do when you’re actually doing software development, as opposed to answering exam questions.)
Here’s a histogram of the quiz #6 scores:
Yikes! Seems like about 2/3rds of the class is really shaky on the concepts we’ve covered over the past two weeks. Heads-up: this topic is likely to make a loud appearance on the final exam!
The fifth and last team assignment has been posted. It is due July 25th. Good luck, and be creative!!
Here’s the page that has all of Dan Grossman’s parallelism and concurrency materials, which we’re using these last two weeks. If you scroll down to the “Lecture slides” section, you’ll find links to the Power Points we’ve been going through — we will cover 1, 2, and 4 this week and next.
My westeros++.zork test file had an error in it until just now: I accidentally extended the message for the dragonglass’s “throw” verb beyond a single line. I’ve deleted the offending newline now. And for the record, no, you are not required to handle item-specific command messages that are longer than a single line.
Sorry for the confusion!
As someone has pointed out, my stephenIII.git Zork solution didn’t have “take all” or “drop all” implemented. Those are there now (Canvas “Files” tab).
To roll these changes into your code:
- One team member should download the new stephenIII.git afresh from Canvas and put it on his/her GC instance, somewhere outside his/her repo. (/tmp is a good place.)
- That team member should make sure he/she has a clean workspace (git status reports clean).
- That team member should cd run:
$ git pull /tmp/stephenIII.git
or wherever the path is to your copy of the stephenIII.git file.