Repair foundations
Spend 60–90 minutes daily on core prerequisites. Stop tool hopping.
Recovery route
You cannot recover three years in three weeks.
But you can stop losing the next three months. Shame is not a useful plan. A narrow target, honest audit, one project and feedback are.
The first 48 hours
Reduce decisions. Increase signal.
Do not wait for a perfect career choice. Choose a provisional target for the next 12 weeks.
- 01
Read two career guides and choose one provisional target.
- 02
Write an honest audit of programming, Git, DSA, projects and communication.
- 03
Find your current stage on the target roadmap—in your notebook, not as tracked progress here.
- 04
Scope one small project that can finish in six weeks.
A 12-week recovery
Foundation → Build → Feedback → Apply
One end-to-end project
Include a README, errors, tests, Git history and a deployable result. Avoid a clone-only project.
Feedback and refactor
Get peer or mentor review. Improve one design pain with tests.
Present the evidence
Explain the project, update your CV/portfolio, rehearse a technical conversation and apply with focus.
The uncomfortable part
You will not close every gap at once.
Close the relevant gaps. Job-ready does not mean knowing everything; it means solving, explaining, learning and improving useful problems with growing independence.
Mentor note
If comparison blocks action, close the timeline and read code for 25 minutes. Someone else’s timeline will not fix your compiler error.