D0013E labs with Git (Reflection of first lab week)
General hints • New/separate project in Git for each lab (we are not checking the old ones for new content) • Upload screenshots with the reviews (Git issue) • Upload the .objdump file • Substantial content in reviews • Lab1a: don’t forget the stack diagram in the code as comment • Upload all project files into your repos (linker_script, Makefile, …)
Delayed submission(s)? It is your duty to inform us and seek for a solution!
Lab assessment • Code works and implements the specification • Received review incorporated • Requires that you received one (inform us if not!) • Proper review done • Substantial enough • No complaint of code owner about arrival
Reviews • Adherence to the specification • Recursion vs looping • Subprocedures vs. branching • Stack usage • … • Comments • Calling convention ($a…, $v…, …)
Review example: good
Review example: good
Review example: good
Review example: good
Review example: good
Review example: good
Review example: insufficient
Comments examples: good
Comments examples: less helpful
Recommend
More recommend