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?

The most effective way to manage a project of this scale is to decouple your coding tasks from your drafting process, treating them as distinct, sequential phases rather than trying to juggle both simultaneously. Since you have three weeks, dedicate the first week entirely to finalizing your code implementations and documenting your walkthroughs. By front-loading the technical work, you ensure that your writing is grounded in concrete results, which prevents the frustration of having to rewrite sections because your code didn't behave as expected. Trying to write the narrative while debugging is a common trap that leads to fragmented focus and poor output. When you struggle to stick to a rigid calendar, it’s often because the tasks listed are too vague or intimidating. Instead of scheduling "work on paper," break your remaining time into high-intensity blocks focused on specific deliverables, like "write the ethical implications section" or "draft the code walkthrough." If your job consumes 15 hours a week, don't try to squeeze in writing sessions on those days; accept that your energy will be depleted and use those days for low-cognitive tasks like formatting references or proofreading. Treat your research as a part-time job itself, setting a fixed, non-negotiable two-hour block on your off-days to make consistent, measurable progress. Regarding the ethical implications section, don't leave it for the very end as an afterthought. Use this as a mental break from the technical coding work. When you hit a wall with your implementation, switch gears to drafting the ethical analysis. This keeps your momentum going without requiring the same level of logical precision as debugging. If you find yourself overwhelmed by the scope, remember that a ten-page paper is essentially five two-page mini-essays. Focus on completing one section at a time rather than staring at the document as a whole. By the time you reach the final week, your primary focus should be solely on synthesis and polish, which will alleviate the anxiety of a looming deadline. You’ll find that having a completed technical foundation makes the final narrative flow much more naturally.