The Summer Grind
Timetable
DSA · Aptitude · System Design · Projects · Open Source · Hackathons · Social Life
Deep Work First
Hard topics when brain is fresh
Flexible Buffer
30–60 min carry-forward slots
Social Protected
Evening walks are non-negotiable
Theme Days
Each day has a primary focus
Rotate Topics
Avoid burnout with variety
Monday — Focus: Training + Projects + DSA
Wake Up · Routine
Get ready for training
Training Session
Attend mandatory training
Lunch + Break
No screens — 1 hour full break
Project Development
Build / implement features, full-stack work
Open Source Contribution
Issues, PRs, code reviews, documentation
Google Arcade
Quests, labs, skill badges (Alternate day active)
Evening Walk + Friends
Outdoor walk, call/meet friends — non-negotiable!
Aptitude Practice
Quant + Logical Reasoning — 20 questions
Dinner at Mess / Room
Dinner at college mess / hostel with friends
DSA Deep Work
Arrays, Strings, Trees, DP — 2 problems minimum
Tech Videos / Review
YouTube: system design talks, dev content
Project Coding / Refactoring
Code refinement, clean up, documentation
Plan Tomorrow + Relax
Write tasks for tomorrow, lights out by 02:00
Flexibility & Survival Tips
The Buffer Rule
Every afternoon has a 30–45 min buffer slot. If you miss a task, it moves here — not to tomorrow. This keeps guilt-free momentum.
OSS is Daily, Not Optional
Treat open source like a part-time job. Even 45 mins daily of reviews, comments, or small fixes compounds massively over a summer.
Hackathon Mode Override
When a hackathon weekend hits, Friday evening → Sunday becomes pure hackathon. Don't guilt-trip about skipped DSA — hackathons ARE projects AND learning.
Protect the Walk
The 5:30 PM walk with friends is sacred. It's your mental reset. Missing DSA is recoverable. Missing rest and social connection is not.
Theme Your Main Project
Pick one main project for the whole summer and build features daily. This beats building 5 half-finished apps and makes a great portfolio piece.
Google Arcade = Alternate Days
Arcade labs are scheduled on alternate days (Mon, Wed, Fri, Sun). Use these slots to complete labs and earn badges without letting it eat into daily coding.
DSA is a Daily Habit
Even on heavy project/hackathon days, touch at least 1 DSA problem. Consistency over intensity — 1 problem daily beats 10 problems once a week.
Weekly Review Friday
Every Friday evening (non-hackathon), spend 20 mins reviewing the week. What slipped? What worked? Adjust next week's plan accordingly.
"This timetable is a framework, not a prison. The goal is sustainable progress, not perfection every single day. If you miss 2 hours of DSA, don't compensate by skipping sleep or the walk. Just pick it back up tomorrow."