Skip to content

Week 12: Review, a portfolio page, and choosing a track

~9 min

This week's goal

This week you look back over the twelve weeks, collect your work into one public page on GitHub, and write down the track you want to follow next. You do not learn a new topic this week. You fix gaps, tidy your repositories, and make a decision. The track choice is a starting point and you can change it later.

The main texts are the choose a track page and the git and GitHub page.

Day-by-day (about 1.5-2 hours per day)

Day 1. Go through your notes from all twelve weeks. Make a list with one line per week: what you learned, what is still unclear, and which deliverable you finished. Mark each week as done, partly done, or not started. Do not rush this step. The list tells you where to spend the rest of the week.

Day 2. Fix one gap. Pick the week with the most unclear points and redo its deliverable from the start, without copying your old code. Use the lesson or the official docs to check each step. Save the new version as a commit in the right repository, with a message that says what changed.

Day 3. Tidy your repositories. Check that each one has a README.md with a short description, how to run it, and what it needs. Check that the commit messages make sense and that no file that should be private is in the repository, such as a password or a local database with personal data. Remove files that you no longer need.

Day 4. Create a GitHub profile README. GitHub shows a special repository named after your username as the top of your profile. Read the profile README guide and follow its steps. Write a short introduction, a list of your projects with one line for each, and the languages you used.

Day 5. Read the choose a track page. It describes four tracks: software development and products, systems and backend, data and AI or machine learning, and government and bank exams. Read the section for each track that interests you. Write down what you would do in the next semester for your top choice, and what you would do for your second choice.

Day 6. Write your track choice in one page of notes. Include the track you picked, the reason in two or three sentences, one thing you will learn next, and one thing you will check before you decide again. Then add a short section to your profile README that links to the track page, or simply names the track you chose. Review the README once in the browser, and push the final version.

Day 7 is a rest day.

Deliverable

A public GitHub profile README that lists your projects with a one-line description each, links to the repositories from weeks 6 to 10, and names the track you chose. Also a private or public note with your track choice, the reason, and one thing you will do next.

Check yourself

  1. What is the difference between a profile README and an ordinary repository README?
  2. Why is it useful to redo one deliverable from scratch?
  3. What should you check before you publish a repository on GitHub?
  4. How many tracks does the track page describe, and what are they?
  5. Why is it fine to change your track later?
Answers
  1. A profile README is a repository named after your username, and GitHub shows it at the top of your profile page. An ordinary README is the front page of one repository, shown when someone opens that repository.
  2. Redoing the work from scratch shows which steps you understood and which you copied. It is a quick way to find the gaps you should fill before you move on.
  3. Check that the repository has no passwords, keys, or personal data, and that the README explains how to run the code. Remove anything you do not want public.
  4. Four: software development and products, systems and backend, data and AI or machine learning, and government and bank exams.
  5. The first year gives you a base that all tracks share. A track is a direction for the next steps, and you can move between tracks as you learn more about what you enjoy.

Sources