Motivation starts the habit; systems keep it. Here's the system.
CS splits between theory you read and skills you only gain by writing code that breaks.
One tip that works: Track 'building' hours separately from 'reading' hours — the ratio should favor building.
A visible unbroken chain you won't want to break.
Set a minutes target; the dashboard ring fills as you study.
Flashcards resurface Computer Science material right before you'd forget it.
Friends and groups see your activity — quiet quitting gets noticed.
Because willpower is a terrible scheduler. External structure — streaks, visible goals, partners — outperforms motivation for every subject, Computer Science included.
Track 'building' hours separately from 'reading' hours — the ratio should favor building.
Most people report the streak 'pulling' them back within two to three weeks — the loss-aversion of breaking it does the heavy lifting.