· 6 min read
A UoPeople Study Schedule That Fits a Full-Time Dev Job
A UoPeople study schedule that plans each learning week backwards from the Wednesday deadline, so a CS degree fits around a full-time job.
A UoPeople study schedule looks easy on paper. There are no lectures at fixed times, so you can study whenever you want. That freedom is the trap. I study for a BSc in Computer Science at University of the People while working full-time as a mobile developer, and with a full workday behind you, "whenever I want" easily turns into "Wednesday night". This post shows one technique that keeps that from happening: plan each learning week backwards from its deadline, and give every task a fixed day.
How a UoPeople learning week works
Before you can plan a week, you need to know its shape. The rules below come from the UoPeople catalog.
- A course runs for a nine-week term: eight learning units, then the final exam week.
- A learning week starts on Thursday at 12:05 am and ends on Wednesday at 11:55 pm, UoPeople Time (GMT-5).
- Each week usually has a discussion assignment, a written assignment, a learning journal entry and quizzes. The exact mix depends on the course.
- In the discussion forum you post your own answer, then reply to and rate at least three classmates.
- Peer assessment happens in the week after you submit an assignment. You grade three of your classmates' papers.
Two details matter more than they seem. First, the discussion forum only works if people post early: you cannot reply to classmates who have not posted yet. Second, peer assessment means every week carries a small task from the week before. A week is never just one week.
Convert the deadline to your own time zone
Start by writing the deadline down in your own time. "Wednesday 11:55 pm GMT-5" is a different moment depending on where you live.
In GMT+4, for example, it lands on Thursday at 8:55 am. That sounds like a gift: an extra night. It is not. If you count on that night, you will spend it studying after a full workday, and you will start the next week tired. It works better to treat your own Wednesday evening as the real deadline and keep the extra hours as a buffer for when work runs late.
If you live west of GMT-5, the deadline comes earlier than you think. Check it once, put it in your calendar with the right time zone, and stop doing the math in your head every week.
A UoPeople study schedule, planned backwards
Here is the core idea. Do not start the week by opening the learning guide and seeing how you feel. Start from the deadline and work back. Each task gets a fixed day, chosen by what it depends on.
A weekly plan for a working developer can look like this:
| Day | Task | Why this day |
|---|---|---|
| Thursday | Read the learning guide, skim the unit, do the self-quiz | The week just opened; know what is coming |
| Friday | Write and post the discussion answer | Classmates need something to reply to |
| Saturday | Main block: written assignment draft, readings | The only long block in a work week |
| Sunday | Peer assessments for last week's assignment | Get last week's debt out of the way |
| Monday | Finish and submit the written assignment | Leaves two days of slack |
| Tuesday | Reply to and rate three classmates' posts | By now most of them have posted |
| Wednesday | Learning journal, graded quiz, buffer | Small tasks only; nothing big due today |
Your days will differ. The order is the point, not the exact days. There are three rules behind it.
Rule 1: Post first, reply last
Your own discussion post goes up early in the week. Your replies to classmates go up late. If you reply on Friday, you choose from two or three posts. If you reply on Tuesday, you choose from the whole class and can pick the posts where you have something real to add.
Rule 2: The big task gets the big block
A full-time job leaves you short evening slots on weekdays. The written assignment needs focus, so it goes into the one long block of the week. Everything that fits into 30 to 45 minutes goes into the evenings: quizzes, journal entries, forum replies.
Rule 3: Nothing large on deadline day
Wednesday is for small tasks and for whatever went wrong. A production bug, a release that slipped, a sick day: something will happen. When it does, it should eat your buffer, not your assignment.
Treat it like a sprint, not like homework
This is where my day job helps. A UoPeople learning week behaves a lot like a one-week sprint:
- Fixed timebox. The week ends at a known moment, no matter what.
- Known backlog. The learning guide lists every task on Thursday.
- Dependencies. Replies depend on other people's posts. Peer assessment depends on last week's submissions.
- Carry-over. Peer assessment is work from the previous week that lands in this one.
So plan it the same way you plan work. On Thursday, read the learning guide and put each of the week's tasks into your calendar or task list, each one with its day. If a task has no day, it does not exist yet.
The sprint view also helps when you choose how many courses to take in a term. Before you add a second course, ask the question you would ask at work: do I have the capacity for this, every week, for nine weeks? Not on a good week. On a normal one, with a release in the middle.
What breaks the plan, and what to do
Plans break. These are the common ways, and the fix for each.
A work crunch eats your weekend block. Move the written assignment draft to two weekday evenings and drop the extras: optional readings and the course forum. Keep the graded tasks. Missing an assignment also means you lose that peer assessment round the following week, so a weak submission still beats none.
You fall behind on readings. Read for the assignment, not for completeness. Open the task first, then read the parts of the unit that it asks about. Catch up on the rest when a lighter week comes.
The final exam week. Week 9 has no new unit, but the exam window is only four days, from Thursday to Sunday. The catalog advises finishing early in that period, and make-up exams are not allowed except in exceptional cases. Put the exam in your calendar on day one of the window, not day four.
Motivation drops in the middle of the term. It will. A fixed day for each task means you do not have to decide anything when you are tired. You just open the calendar and do what is there.
Takeaways
- Learn the shape of the week first: Thursday to Wednesday, UoPeople Time (GMT-5), with peer assessment spilling into the next week.
- Convert the deadline to your time zone once, and set your own earlier deadline.
- Post your discussion answer early and reply to classmates late.
- Give the written assignment your one long block, and keep deadline day for small tasks and surprises.
- Plan the learning week like a sprint: fixed timebox, known backlog, and a day for every task.