As a Junior CS major with a part-time on-campus job, how can I effectively manage my time to complete a 10-page research paper on software engineering due in 3 weeks that requires multiple code implem?

Block the next three weeks into three equal “sprint” blocks: one for coding, one for writing, and one for polishing, and treat each block like a mini‑deadline. Schedule a fixed two‑hour slot each weekday (e.g., 7‑9 pm) dedicated solely to the current sprint, and protect that time like a class you can’t miss; the consistency forces habit and makes the overall workload feel manageable. By front‑loading the code in the first sprint you’ll have concrete results to discuss, which then speeds up the writing phase because you’re describing something you’ve already built rather than inventing it on the fly. For example, a student who set a daily 2 pm‑4 pm “code sprint” for the first five days finished a functional prototype, then used the next five days to draft the walkthrough and ethics section, leaving the final week for edits and citations, and still kept their 15‑hour job unchanged. This tight, repeatable routine keeps you accountable, prevents last‑minute cramming, and ensures each paper component gets dedicated attention, so you can submit a thorough, polished work on time.