Examination

πŸ” OVERVIEW

The exam is set up to get you familiar with the key concepts, show you what's good to practice, and give you a chance to dive into some hands-on work. To give you an opportunity to get your feet wet. While you will get feedback, it is not graded, and you do not pass/fail.

The examination goes through all topics from different weeks, and mostly consists of practical exercises that you will be asked to screenshot.

Some exercises will provide you with the commands needed for an action, while others won't. There's a reason for this. The idea is for you to start practicing googling solutions and asking ChatGPT for help. This skill is invaluable as a programmer - Often, the people around you might not have a solution to the problem, so it's up to you to work together to find one. This means searching online, asking questions on forums, and exploring other resources.

PLEASE DO NOT BE ALARAMED by the length of the Examination PDF. IT IS NOT LONG BECAUSE THE ASSIGNMENTS ARE DIFFICULT, OR BECASUE THERE IS A LOT TO DO. It's lengthy because the assignments are extremely detailed, explanatory, and comprehensive, often giving you step-by-step instructions on what to do.

There is also a guide on how to use git to hand in your assignments called Examination Help - How to use Git for Hand-ins provided.

If you encounter any issues or think the workload might be too much, please let me know on Slack!

πŸ—“οΈ DEADLINE

Week 1

  • A Markdown document with formatting requierement and answering some questions
  • Breaking the ice - asking question on SLack and ChatGPY

Week 2

  • Following 2 tutorials - Tutorial 2 - The Terminal & Tutorial 3 - File systems plus doing a screenshot of each
  • Downloading node.js and npm and checking in the terminal if it has been installed and doing a screenshot
  • Navigation and file operations in the terminal and doing a screenshot

Week 3

  • Writing you first "Hello, World!" on Replit
  • Some short coding exercises - declaring variables, playing around with booleans (true/false), numbers and strings, using console.log() to print your results when your code is run, and writing some if-statements.
  • Downloading VSCode, plus an extension, and practicing using git to upload your work from you local machine.

Week 4

  • Pending.

πŸ“š MATERIALS