TutorTermTell Us What Is StuckGet in Touch

Does documentation actually carry points?

Frequently yes, and students are surprised by how many. Naming, comments that explain why rather than what, and a clear explanation of the approach are all commonly assessed. Working code with no explanation loses a meaningful share on many rubrics.

This comes up on Programming Fundamentals Support, where it is answered in the context of the work itself.

Get My Free QuoteBrowse all questions

More on computer science & it

See all
How ambitious should my capstone be?How do I choose a baseline?How do I get better at debugging?How do I get faster at subnetting?How do I handle class imbalance?How do I justify an architecture choice?How do I model a many-to-many relationship?How do I prepare for the demo?How do I present to a non-technical stakeholder?How do I prove an algorithm is correct?How do I read a paper critically?How do I report uncertainty properly?How do I score risk in an assessment?How do I work out the Big O of my own code?How do I write up a packet capture?How is a thesis different from a large project?How much documentation is expected?How much theory should the report contain?How technical should the executive summary be?I am lost and it is week nine. Where do I start?
Not what you asked?

Ask us the actual question

Send the draft, the rubric or the score report with it. You get a real answer and a price before you commit to anything.

Get My Free Quote[email protected]