Latest update Jan 4, 2023.

Lab Presentation Checklist

As lab presentations are part of the examination moments in the course, there are some things that you should account for before presenting to make the process smooth for everyone involved. Please check that:

• You are the one who has figured out, designed and written the vast majority of the code being presented. We have strict guidelines related to plagiarism.
• Lab skeletons and code snippets from lectures may of course be used, but it is your responsibility to ensure you understand how they work as part of the solution.
• The guidelines regarding hand-ins for examination have been followed.
• "I just want to see what you think before I upload the solution" is not a valid excuse.
• The code works. It covers all of the functionality asked for in the lab. And it has been tested using automated tests/concrete examples, which must be included in the upload.
• You may use a proper test framework, but you may also have some prepared examples to show. The important thing is to show that you have thought about different cases in your solution.
• You have read and understood the lab instructions. The presentation session is not the right place to start asking such questions.
• If there are doubts about something, please first check the existing course material, or the Q/A documents. If after that you still have issues, feel free to ask in class or by mail. But in the interest of time, please be detailed describing what the issue is and what you have already investigated to solve it.
• You remember the task and what your code is supposed to do.
• Statements like "Let me just read the task quickly, I did this weeks ago" is a clear sign that you have not prepared properly. If this happens, your presentation will likely be moved to the end of the queue, to ensure that you have time to prepare.
• In the interest of time for all parties involved, please take a few minutes to go through and think about how to present the solution in a reasonable and logical way. This includes how to demonstrate that the different functions work.
• You are not afraid to make on-the-spot changes in your code.
• "This worked yesterday, but I just changed something and now it doesn't" should just require you to pull a provably working version from your git history.