Phase 1–2 · first half-year · 15 h/week
During exams, reduce to an 8-hour maintenance week: 3h CP, 2h Flutter, 2h current university/CS, 1h Java/English alternating. Return to normal after exams without “catch-up debt.”
Personal engineering operating system · September 2026 → September 2028
Build the engineer.
Not just the résumé.
Mahmoud's assessment-based 24-month path: master production Flutter, learn Java and Spring Boot, strengthen computer science through competitive programming, and graduate ready to demonstrate engineering depth in international interviews.
Flutter / DartJava / Spring BootC++ / CPCS foundationsEnglish + career
How saving works: checkboxes, month notes, CP counters and weekly reflections save automatically in this browser. To move devices or browsers, use Export progress → Import progress. The HTML works without internet; the learning material links need internet. Back up monthly, and avoid using private browsing for long-term tracking.
01 / Baseline
What we're improving
Based on your written answers in September 2026. These are informal observations, not job-level labels; the practical booking assignment will refine them.
6 / 10Dart & async · improve Futures, streams, isolates, error propagation
4.5 / 10Flutter framework · improve lifecycle, keys, testing and profiling
6 / 10Architecture · strong payment intuition, improve DI/DIP & CI/CD
3 / 10CS written test · graph algorithms, OS, networking and DB concurrency
9 / 10OOP written concepts · demonstrate through Java code
5 / 10Technical English · structure, accuracy and spoken explanation
Not a beginner reset. You already have practical Flutter, BLoC, Supabase and payment experience. Focus on internal mechanics, testable implementations and proof. The Spring Boot baseline is unassessed; Java starts with language fundamentals. Your production code has not yet been evaluated.
02 / Sustainable pace
Your study operating system
Keep an achievable baseline around university and work. Shift allocation over time; do not add all new technologies at once.
From Spring Boot onward · suggested 15 h/week
| CP / algorithms | 3h |
| Flutter & capstone | 3h |
| Java & Spring Boot | 5h |
| CS / databases / systems | 3h |
| English / career | 1h |
In 2028, reallocate some project hours to coding mocks, communication, and applications.
Learning loop for every topic
Learn → predict → implement → test → explain → revisit.
Example: read about streams, predict output, build a wallet event feed, test cancellation and errors, explain it aloud, retry one week later without notes.
Evidence, not just checkmarks
Mark a topic finished only after producing the specified application: a test, trace, code sample, CP solution, diagram, or coherent explanation. Add links or brief notes under the month.
Keep one error notebook for wrong CP patterns, race conditions, performance mistakes and confusing CS concepts.
03 / Overview
Six phases, one graduation target
Each phase has a deliverable. Follow readiness gates before introducing more complexity.
04 / Core curriculum
24-month detailed roadmap
Open a month to see what to learn, where to learn it, and what to implement. Its checkboxes and CP numbers save automatically.
05 / Execution
105-week tracker
Weeks start Monday, from 28 September 2026 to 25 September 2028. The first 12 weeks have custom assignments; later weeks distribute the matching month's topics into four repeatable study actions. Week 1 is a kickoff week for October's curriculum.
06 / Evidence
Projects to build while learning
These are staged projects, not eight unrelated tutorial apps. Keep production Salonly separate from learning experiments and never publish sensitive customer or payment data.
07 / DSA applied as CP
Competitive programming practice rules
DSA application = solve and explain problems, not building unnecessary data-structure apps. Use C++ as your default CP language; use Java occasionally in 2028 for interview fluency.
The weekly CP loop
1. Study one pattern (30–60 min), write its invariant and complexity.
2. Solve 3–5 fresh topic-aligned problems independently.
3. Join or replay a timed contest (aim ~2 per month).
4. Upsolve at least two missed problems; retry without editorial after 3–7 days.
5. Log failure reason: modeling, bug, implementation, math or time.
How to progress in difficulty
Use success rate, contest performance, and repeat mistakes to choose your next set—not a guaranteed rating timetable.
Early: basics, arrays, hashing, two pointers, binary search.
Middle: graphs, DP, trees, DSU, shortest paths.
Later: range queries, advanced DP, mixed unseen interview problems.
Fresh solves ≠ upsolves. Track both so weak topics don't disappear behind problem counts.
Where to practice
Monthly cards specify sample CSES tasks and topic emphasis. Use CSES and USACO for topic sets, Codeforces for contests and upsolving, and MIT for fundamentals.
Your CP totals
0
new problems solved0
upsolved problems0
contests / virtual contestsThese totals use the monthly CP counter fields. Don't double-count the same problem as a new solve.
08 / Sources
Curated learning materials
Official docs and university/author-hosted learning materials first. Each month's tasks also link directly to relevant references. Links are online; the tracker itself is offline.
09 / Review
Your personal engineering journal
Use these fields weekly. They save automatically in your browser and in exported progress files.
10 / Career execution
International engineering readiness
Be eligible and application-ready without assuming a specific company offers a position on a fixed date.
Throughout 2027
Maintain one-page CV, document internship eligibility and opening dates from official job boards, apply to fitting internships, write technical case studies in English and ask for code reviews.
Throughout 2028
Prepare timed coding interviews, CS oral questions, backend/mobile walkthroughs and behavioral examples. Track applications, work authorization and location requirements in a separate private sheet.
An interview roadmap increases preparedness; it cannot guarantee an offer or a particular company outcome.