Assignment

Work as part of a professional software development team for 10 full-time weeks (or equivalent). Your main challenges are to get up to speed with the development workflow that the team is using, and to learn the technology stack. Generally, you'll want to strive to get your first commit approved into the main branch (or similar) as early in your internship as you can.

Internship report

During your internship you will want to work on your internship report. Don't worry though: the report doesn't need to be very wordy, and it's structure is described in the sections below and templated in the provided report.md file.

1 → The basics

2 → Journal

Provide a journal for at least 45 working days at the company. For each day, the following questions should be answered:

1. Accomplished: What have you accomplished today?
2. Learned: What are the most important things you learned today?
3. Next: What are the most important questions you still have at the moment and/or what will be your next steps?

On average, your answers should combine to about 100 words per day.

3 → Tech stack

For each of the languages, frameworks, libraries, tools and design/architectural patterns you encounter during your internship, list the following:

• Name.
• Description: Description of the tech.
• Company usage: How it's used within the company.
• My usage: What you personally did with this tech during your internship.
• Curriculum: If this tech was covered in the curriculum, describe to what extend it's usage within the company is similar to what you've learned, and in what ways it was different. If not, describe which aspect(s) of the curriculum is/are most close related, and how this is different.
• Opinion: Your personal opinion on this tech. Would you use it again? In what situations? Why (not)?

This list may be long! Besides the obvious, think of all kinds of build tools, databases, container tech, orchestrators, linters, issue trackers, code review tools, analytics tools, monitoring tools, cloud services, coding techniques, etc. Mention all technologies you've had to actually work with (for a bit) yourself.

4 → Your contributions

Describe everything you did/accomplished during your internship. This can range from tiny bug fixes, to documentation improvements up to whole new features/products. For each:

• What: Explain what you did.
• Learning: Explain what new things, if any, you needed to learn in order to do this.
• Duration: An estimate for how much time this took, including any learning.
• Team work: Describe what kind of help and/or reviews you received and/or how you collaborated with other roles.
• Demo: If at all possible, include a screenshot or screen capture showing your work. In some cases, this may also just be console output. If your change is hard to spot, you may consider including a before/after comparison, or adding an arrow pointing out the change.
• Source code: A link to the full source code of your contribution, including version history. In case the contribution is a small project you made by yourself, please provide the full (git?) repository. If, more likely, you've contributed to a larger project, it suffices to provide the patches for all commits you created towards this contribution. When using git, you should be able to do something like this from a feature branch:

git log --author="$(git config user.name)" --patch origin/main..HEAD > feature_name.patch

• Status: What has happened with your contribution after you were done working on it? Has it been rolled out, or ...?

IMPORTANT: Create this documentation immediately after completing (including any review stages) a contribution. If you do it later, it may be a lot harder to produce the source code patches, create screen captures, and describe the contribution accurately.

5 → Roles

6 → Development process

Wrapping up

First internship retakes

An internship can be a daunting learning experience, especially the first time. Therefore, some leniency is provided in the rules for the first internship:

• If, while approaching the end of your internship you think (and your Saxion study coach agrees) that you don't have enough to show for it to pass this exam, you may consider requesting a five week internship extension. This is of course only possible if your company supervisor agrees to this. Please put your request for extension in an email to your company supervisor and your Saxion study coach, and make sure you receive written agreement from both.
• In case of special circumstances, you can file a request for (further) extension with the examination board.
• In case you receive a failing grade for your internship, you may (together with out study coach) choose between these three forms of retake:
  1. Start a new internship at a different company.
  2. Improve and resubmit your report, based on the grading feedback you received. The new deadline for the report is two week after you received your grade.
  3. Get a five week internship extension like described above, if the internship wasn't extended already, and then improve and resubmit your report. Please note that this will probably be more difficult to arrange with the company once you've ended your internship.
• You may choose retake option 2 or 3 only once per internship.
• As usual, you are entitled to do two attempts (meaning one retake of any kind) per academic year. In case you require an additional retake, you can file a request with the examination board, which would normally be granted without much fuss.

Second internship retakes

During the second internship, you will need to demonstrate your skills within the stated time in one go.

• Extensions are not allowed, except due to special circumstances, in which case you can file a request with the examination board.
• In case you receive a failing grade, you will need to start a new internship at a different company.
• As usual, you are entitled to do two attempts (meaning one retake) per academic year. In case you require an additional retake, you can file a request with the examination board, which would normally be granted without much fuss.

Rubrics mapping and grading