7.1.0.2

Week 14 Memo Inspection Results

Like all memos, the final two memos were graded with a focus on basic structural details: delivery instructions, format, organization, grammar, and spelling. If a sentence was blatantly wrong, we may have deducted a point on content (extremely rare, this happened perhaps once or twice).

Having said that, I graded only my section this time, and I was surprised at the lack of reflection in some of the memos. I will take the freedom to post some anonymized quotes on the courses web page tonight as the end note. – Matthias

Every team in CS4500 has a row in the table. To find your row, check your email inbox for a message with the subject:

cs4500 team identification number

and use the 4-digit PIN in that message to locate your row.

DO NOT SHARE your 4-digit PIN with another team.

The Memo column shows your memo score.
  • 20 = max score

If your team submitted one personal reflection, then your team’s score is an integer between 0 and 20.

If your team submitted two personal reflections, then your team’s score is a pair of integers separated by a hyphen. Here’s how to find your score:
  • if your team’s github repo is named aaaa-bbbb,

  • and your team’s score is NN-MM,

  • and your real-life name is "similar" to bbbb,

  • then your memo score is MM.

Email Ben if are not sure how to find your score.

PIN

  

Memo

9497

  

18

6996

  

18

5998

  

20

2735

  

20

3352

  

18

2035

  

18

2189

  

18

9398

  

20

5476

  

18

7156

  

20

1033

  

20-20

2355

  

19

8940

  

19

6636

  

20

2392

  

20

5134

  

20

4705

  

18

2760

  

20

6835

  

18

5611

  

17

5492

  

18-17

6192

  

19

4704

  

20

4871

  

16

7846

  

19

4063

  

19

8239

  

18

8358

  

20

5647

  

20

3555

  

19

4579

  

14

4412

  

18

4527

  

19

6666

  

20

8209

  

18

2756

  

20

5090

  

20

5691

  

20

5003

  

19

1083

  

19

9670

  

19-19

1124

  

20

3227

  

20

6374

  

19