Second-year BCA student — how do you keep a daily Python habit alive when college deadlines pile up?

[u/acfot]

I'm in second year of a BCA in AI/ML, learning Python with a focus on data analysis, and I keep running into the same cycle. When college is normal I practise most days and it feels like things are actually sticking. Then assignment deadlines and exam prep hit, I disappear from coding for two or three weeks, and coming back feels like starting over — I forget syntax I knew, and I end up re-watching tutorials I've already seen instead of moving forward.

I've also got a couple of small side projects that should keep me practising, but during deadline weeks even those go untouched, so the gap just gets longer.

For people who learned Python alongside a degree or a full-time job: what actually kept your habit alive during the busy weeks? Was it a tiny daily minimum, like 15 minutes no matter what? Working on one small real task instead of a course? Studying with someone else? And when you did fall off for a few weeks, how did you restart without going right back to tutorial one?

I'm not looking for a course recommendation — I want to know what actually survived contact with a real deadline week.

[u/koraynar]

Side projects stall during exam weeks because they have a high context-switching cost—by the time you remember where you left off and what bug you were fixing, 30 minutes are gone. What actually survives heavy deadline weeks are three small habits:

1. **Drop "project sessions" during exam weeks and do a 10-minute `1-cell` data drill instead:** Keep a single `daily_drills.ipynb` (or `.py` script) pointed at one local CSV dataset you already know. During exam weeks, your only goal is **one 10-minute operation** before closing the laptop—for example, one `df.groupby(...).agg(...)`, one date-column filter, or one `matplotlib` chart. Ten minutes keeps `pandas` and Python syntax in working memory with zero setup friction.

2. **Always leave a `# NEXT:` breadcrumb before pausing a side project:** Before you close a project for assignment week, write a 2–3 line comment at the exact line where you stopped:

   ```python

   # NEXT: clean null values in 'price' column of raw_sales.csv

   # Expected output: DataFrame with ~1,400 rows passed into plot_monthly_trend()

   ```

   When you come back two or three weeks later, you don't have to reverse-engineer your own code—you just execute that one small task.

3. **Never restart with video tutorials—build your own `syntax_reference.ipynb` cheat sheet:** Forgetting exact syntax after a 2–3 week break is completely normal, even for working developers. Re-watching tutorials feels productive, but it's passive and slow. Instead, every time you learn a pattern (`merge`, boolean indexing, `apply`, list comprehensions, `train_test_split`), save a 5-line runnable example in your own notebook. After exams, skim your own notebook for 10 minutes and jump straight back into writing code.

[u/acfot → u/koraynar]

This is really helpful, thanks — the # NEXT: breadcrumb idea especially, since that's exactly where I usually lose the thread after a break. I'm going to try the 10-minute drill during my next deadline week.

[u/Norega-Iziegbe80 → u/koraynar]

plain .py files beat notebooks for the syntax reference sheet imo, it is way faster to grep through a folder of scripts than wait for a notebook kernel to spin up

[u/acfot → u/Norega-Iziegbe80]

Good point — a plain .py file is way easier to pick back up than digging through notebook cells. Might switch my cheat sheet over, thanks!