Start daily interview problems; HTTP, APIs, pandas and SQL.

1. 1.Create your problem log

   One row per problem: date, problem, category, difficulty, minutes, solved_unaided, revisit. The Problems page keeps the same log and can export it.

   $ mkdir -p dsa && echo 'date,problem,category,difficulty,minutes,solved_unaided,revisit' > dsa/progress.csv

   Problems page
2. 2.Try #1 Contains Duplicate – untimed, AI-free

   Arrays & Hashing · Easy. Aim for 15–20 minutes. No assistants, no autocomplete.

   Open on LeetCode (opens in a new tab)
3. 3.Stuck at 25 minutes? Use the NeetCode method

   Read or watch the explanation, close it, then re-code the solution from memory.

   NeetCode 150 explanations (opens in a new tab)
4. 4.Write the Big-O

   Add a comment with the time and space complexity, and why.

5. 5.Log it

   Mark it Solved or Revisit, with minutes and whether you solved it unaided.

   Log #1 on the Problems page
6. 6.10 min revision

   One item from reviews/relearn.md.

Companion video

Python for Coding Interviews – Everything you need to KnowNeetCode · Mon

1. 1.Try #2 Valid Anagram – untimed, AI-free

   Arrays & Hashing · Easy. Aim for 15–20 minutes. No assistants, no autocomplete.

   Open on LeetCode (opens in a new tab)
2. 2.Stuck at 25 minutes? Use the NeetCode method

   Read or watch the explanation, close it, then re-code the solution from memory.

   NeetCode 150 explanations (opens in a new tab)
3. 3.Write the Big-O

   Add a comment with the time and space complexity, and why.

4. 4.Log it

   Mark it Solved or Revisit, with minutes and whether you solved it unaided.

   Log #2 on the Problems page
5. 5.10 min revision

   One item from reviews/relearn.md.

1. 1.Try #3 Two Sum – untimed, AI-free

   Arrays & Hashing · Easy. Aim for 15–20 minutes. No assistants, no autocomplete.

   Open on LeetCode (opens in a new tab)
2. 2.Stuck at 25 minutes? Use the NeetCode method

   Read or watch the explanation, close it, then re-code the solution from memory.

   NeetCode 150 explanations (opens in a new tab)
3. 3.Write the Big-O

   Add a comment with the time and space complexity, and why.

4. 4.Log it

   Mark it Solved or Revisit, with minutes and whether you solved it unaided.

   Log #3 on the Problems page
5. 5.10 min revision

   One item from reviews/relearn.md.

1. 1.Work through: MDN – Overview of HTTP

   ≈35 min

   Open (opens in a new tab)
2. 2.Work through: GOV.UK – APIs

   ≈10 min

   Open (opens in a new tab)
3. 3.Do

   Read; then write bank_holidays.py with requests printing the next 3 Scottish bank holidays.

4. 4.Check you’re done

   Done when: Correct holidays printed.

1. 1.Work through: GOV.UK bank holidays JSON

   data

   Open (opens in a new tab)
2. 2.Do

   Handle network errors; add an offline test using a saved sample JSON.

3. 3.Check you’re done

   Done when: Offline test passes.

1. 1.Catch up first

   Finish anything unticked from Mon–Fri this week before stretch work.

   Week 5 sessions
2. 2.Then stretch work

   Re-solve 2 earlier problems in fewer lines; read the Python tutorial on modules.

   Python tutorial §6 – Modules (opens in a new tab)

1. 1.Start with 20 min revision

   Explain a class vs an instance.

2. 2.Work through: Kaggle Learn – Pandas

   ≈2h

   Open (opens in a new tab)
3. 3.Work through: PHS – GP Practice Population Demographics (OGL)

   latest CSV

   Open (opens in a new tab)
4. 4.Do

   Notebook: load, check missing values, answer 5 questions, 2 charts; then 10 questions of your own.

5. 5.Check you’re done

   Done when: Notebook runs top to bottom; README cites the OGL.

6. 6.Commit

   data/phs_explore.ipynb

   $ git add data/phs_explore.ipynb

   $ git commit -m "Week 5: pandas with Scottish health data"

   $ git push

1. 1.Work through: SQLBolt

   lessons 1–8

   Open (opens in a new tab)
2. 2.Do

   SQLBolt 1–8 with every exercise; weekly review.

   SQLBolt (opens in a new tab)
3. 3.Check you’re done

   Done when: Exercises complete; 5 queries saved in sql/notes.sql.

4. 4.Commit

   sql/notes.sql

   $ git add sql/notes.sql

   $ git commit -m "Week 5: SQL basics + review"

   $ git push
5. 5.Weekly review (last 30 min)

   3 wins, 3 confusions, 1 thing to re-learn – written at the bottom of this page and saved with your progress.

   Open the weekly review