I'm building an app. I'm in my second year of a CS diploma. I'm trying to get better at coding, stay consistent on GitHub, keep up with college academics, and not completely fall apart physically.
If you're reading this on Dev.to, there's a good chance you're doing something similar — too many goals, not enough time, and a productivity system that works great for three days before quietly dying.
This is what actually worked for me.
The real problem isn't discipline
I used to think I just needed more willpower. Wake up earlier, push harder, stop wasting time.
That wasn't it.
The real problem was decision fatigue. Every single day I had to decide: what do I work on first? How long? What counts as enough? When do I switch? By the time I'd figured out the answers I'd burned through the mental energy I needed for the actual work.
The fix wasn't discipline. It was eliminating the decision entirely.
The 10-Task Day
Here's the system: 10 fixed task slots, same categories every day, decided in advance forever. You don't choose what kind of day you're having. You open the list and start.
My current 10:
Primary skill study — the most important technical thing I'm building right now
Secondary skill / new tool — currently React Native
Coding practice — one DSA problem or code exercise
Personal project — my app, minimum 20 minutes of real work
GitHub commit — push something, anything
College / diploma study — actual syllabus material
Creative practice — I draw, yours might be something else
Listening / passive learning — podcast, tech talk, something running in the background
Exercise — minimum is a 20 minute walk
New language or framework concept — one thing understood and written in my own words
The categories don't change. What I do inside them changes daily.
The minimum rule — the thing that makes it actually stick
Every task has a minimum. The absolute floor version that still counts as completing it.
The minimum exists for one reason: so you have no excuse to skip entirely.
"I only have 15 minutes" is no longer valid. That's three minimums right there. A bad day where you hit all 10 minimums is infinitely better than a skipped day — because the habit stays alive.
On good days you go well beyond the minimum. On hard days it's a lifeline.
The four zones
After running this for a while I noticed the 10 tasks naturally fall into four zones. When all four are active, everything feels stable. When one zone drops for 3+ days, something starts feeling off even if you can't name it.
Build — coding practice, personal project, GitHub commits. This is where your future is being built. Don't cut this zone during exam season. Even one commit a day keeps the mental model alive.
Learn — primary study, secondary skill, new tool, passive listening. Active learning (producing notes, writing code) vs passive learning (listening, watching) — both matter, don't confuse them.
Foundation — college academics, exercise. Not exciting, totally load-bearing. Your diploma is the floor beneath your career. Your body is the hardware running all of this.
Expression — whatever creative thing you do. This one gets dropped first when things get busy. It shouldn't. Creative work processes the pressure that builds up from pure input and productivity. Students who cut expression for months feel increasingly flat even when they're technically productive.
What happens when everything falls apart
Exam weeks: don't abandon the system, compress it. Every task drops to minimum level. A compressed day takes about 90 minutes. When exams end, step back up — no momentum lost.
Destroyed days: complete five tasks at minimum, any five. That's your floor. Not zero. Five.
After a gap: don't try to catch up. There's no catching up. Days that are gone are gone. Do today's 10 tasks at minimum levels. Three normal days later, do a quick review.
The weekly review (10 minutes, that's it)
Every Sunday. Five questions:
How many days did I complete all 10?
Which task did I skip most?
Which zone was weakest?
One thing to adjust next week?
What made the best day work?
Write the answers. Don't just think them. This is the only maintenance the system needs.
Why this works when other systems don't
Most productivity systems give you a method but leave the daily decisions to you. This one pre-makes the decisions. The structure is fixed. The effort goes into the work, not into figuring out what work to do.
It's also honest about what a student's life actually looks like — unpredictable, fragmented, full of obligations you didn't choose. The minimums exist because perfect days are rare. The four zones exist because you have more than one goal. The compression protocol exists because exams are real.
If you want the full version — complete task template, sample daily schedules, zone framework breakdown, exam protocol, and a guide to designing your own personal 10-task list — I wrote it up as a short ebook.
It's called The 10-Task Day and it's $9 on Gumroad: https://yeeshitc.gumroad.com/l/10-task-day
It's short, no fluff, written for people who code and study at the same time. If this article was useful the ebook covers everything in proper depth.
Currently building AutoDox — a document automation app. Writing about productivity and coding as a student along the way.
Top comments (0)