Expert · Interviews, portfolio and careers · topic 43 of 43 · 20 min
A 30-day revision plan for the whole course
Explanation
How to revise well
- Active recall: close the notes and write what you remember, then check. It feels harder than re-reading and works much better.
- Spaced practice: revisit a topic after a day, then a week. Short, regular sessions beat one long night.
- Code every day: even 20 lines. Type it yourself; do not copy-paste.
- Explain aloud: if you cannot explain IQueryable to a friend in a minute, revise it again.
- Retake the module exams on this site without looking at notes; aim for 85% or more.
Week 1: foundations (days 1 to 7)
| Day | Revise | Do |
|---|---|---|
| 1 | .NET, SDK, CLI, types, conversions | New console app: read two numbers safely with TryParse, print sum, average and integer division results |
| 2 | Decisions and switch expressions | Electricity bill with slabs using a switch expression |
| 3 | Loops | ATM PIN with 3 tries; multiplication table |
| 4 | Methods and parameters | GST helpers with optional and named parameters; one TryParse-style method with out |
| 5 | Arrays and ranges | Marks analysis: average, topper, top 3 with ranges |
| 6 | Strings, StringBuilder, null | Name formatter and mobile-number masker; fix every nullable warning |
| 7 | Mini-project | Menu-driven "class register" console app using everything from week 1 |
Week 2: object-oriented C# (days 8 to 14)
| Day | Revise | Do |
|---|---|---|
| 8 | Classes, constructors | BankAccount with constructor overloads |
| 9 | Properties, init, required | Address with PIN validation in the setter |
| 10 | Encapsulation, static | Wallet with private balance and a static counter |
| 11 | Structs vs classes, boxing | Write and explain the copy-vs-share example from memory |
| 12 | Inheritance, polymorphism | Payment hierarchy with an abstract Fee() |
| 13 | Interfaces, records, patterns | INotifier with two implementations; a record-based discount switch |
| 14 | Mini-project | Library system: books, members and loans as classes and records |
Week 3: collections, LINQ and async (days 15 to 21)
| Day | Revise | Do |
|---|---|---|
| 15 | Collections | Word counter with Dictionary; duplicate finder with HashSet |
| 16 | Generics | Generic Result<T> and Cache<TKey, TValue> |
| 17 | LINQ basics | 10 queries over a student list without looking |
| 18 | LINQ in depth | GroupBy sales report; explain deferred execution with an example |
| 19 | Exceptions, delegates, events | Custom exception; retry helper with Func; low-stock event |
| 20 | async/await, files, JSON | Expense tracker saved as JSON; Task.WhenAll timing demo |
| 21 | Mini-project | Turn the library system into a JSON-backed console app with async file I/O |
Week 4: Web API, testing and interviews (days 22 to 30)
| Day | Revise | Do |
|---|---|---|
| 22 | Minimal APIs, routing, status codes | CRUD API with an in-memory list |
| 23 | Validation, DI | Add validation and move logic into a scoped service |
| 24 | Configuration, middleware | Options pattern plus a timing middleware; user-secrets |
| 25 | EF Core | Switch the API to EF Core with SQLite and migrations |
| 26 | xUnit and test doubles | Ten unit tests for your service with fakes |
| 27 | NuGet, solutions (and Unity if that is your path) | Restructure into Api/Core/Tests; or build the coin-collector scene |
| 28 | Interview questions | Answer the core questions aloud, one minute each; record yourself |
| 29 | Coding practice | Reverse, palindrome, anagram, second largest, FizzBuzz on paper, then run |
| 30 | Final exam and portfolio | Take this course's final exam; polish your README and push your project |
Common mistakes and fixes
- Only watching videos: watching feels like learning but builds little skill. Pause and type the code yourself.
- Skipping the weak topics: start each week with the module exam you scored lowest on.
- Cramming the night before an interview: sleep well; a rested mind explains better.
- Revising without a goal: tie each week to something you can show, like a working mini-project.
Need help?
Stuck on a word or an idea? Search this course, or every course, and jump straight to the explanation or a worked question.
Try:
Watch the lesson
A 30-day revision plan for the whole course · 1/7
In this lesson you will plan 30 days of revision for the whole course.
Prefer a video by a teacher? Find free videos on “how to revise programming effectively active recall spaced repetition” on YouTube ↗
In real life: Revision before a placement season
Four friends in a Pune engineering college used this kind of plan in the month before placements: one hour every evening, coding on their own laptops, and a Sunday call where each explained one topic to the others. By the end, each had a small API on GitHub and could answer the common questions without notes.
var plan = new (int Week, string Focus)[]
{
(1, "Foundations"), (2, "OOP"), (3, "Collections, LINQ, async"), (4, "Web API, tests, interviews")
};
foreach (var (week, focus) in plan)
Console.WriteLine($"Week {week}: {focus}");Practice (0/2 done)
Which revision method is most effective?
Make your own 30-day revision calendar: copy the plan into a spreadsheet or notebook, adjust it to your weak modules (use your module exam scores), and tick off each day. At the end of each week, retake that week's module exams and record your scores.
Quick quiz
Read more (free)
Related help
Before this, learn
This topic builds on these. If something here feels new, open them first.
Related topics
- Your study plan and the job huntData Structures and Algorithms (DSA) for interviews · Interview strategy and mock problems
- Backend interview preparationBackend Development · Choosing a stack and getting hired
- Go careers in India and a 30-day revision planGo Programming (backend and cloud) · Careers and interviews
- What DSA is, and how to learn itData Structures and Algorithms (DSA) for interviews · Thinking in Big-O
- Portfolio, open source and a learning planRust Programming · Rust careers and interviews
- What data science is, and how this course worksData Science, Machine Learning and AI · Python for data
Questions people ask about this
Open a question to see the answer and why. The first ones are this topic's own quiz, so try the quiz above before you peek.
What is spaced practice?
Answer: Revisiting a topic after increasing gaps (a day, a week)
Spacing reviews over time improves memory.
What should a "mistakes notebook" contain?
Answer: One-line rules from each mistake you made
Short rules from real mistakes are the most useful revision notes.
Why end each revision week with a mini-project?
Answer: It combines the week's topics into something working you can show
Building ties the ideas together.
What is spaced revision?Related
Answer: Re-solving the same problem after growing gaps, such as 1 day, 1 week and 3 weeks
Growing gaps between attempts make the memory last much longer than one long session.
Which plan is most likely to work in the month before interviews?Related
Answer: Daily practice of questions aloud, SQL and DSA problems, project polish, and mock interviews
Interviews test speaking, coding and project knowledge together. Steady daily practice and mocks cover all three.
Which of these is a data structure rather than an algorithm?Related
Answer: A queue
A queue is a way of storing items (first in, first out). The others are step-by-step methods, which are algorithms.
Which resource gives small exercises where you fix compiler errors?Related
Answer: Rustlings
Rustlings is designed around small failing programs.
Pass the quiz (60% or more) or mark this topic as done when you are ready.
Your progress is saved on this device only.
Next steps
- This is the last topic of “Interviews, portfolio and careers”. The module exam comes next.
- Module 10 exam: Interviews, portfolio and careers · 10 questions · 15 min, without help. 4 topics of this module still to finish first.
- 43 topics left in the course before the final exam.