Skip to content

Independent study and getting help

Choose your scope

  • Lab sequence: complete Labs 1–7 and each lab's explanations. This is a useful practical route; it is not a claim of completing all course assessments.
  • Full course route: follow the course checklist, including companion discussions and capstone.
  • Enrichment: choose Labs 8–15 after their prerequisites. They are optional.

No LMS account is needed. Save your evidence locally, for example in a private .local folder or a private document directory. Do not publish filled submissions. The University course's credit, grades and enrollment are separate from self-study.

Check whether your answer is sufficient

Aim first for Competent in the assessment descriptors. For each requested explanation, check:

  • I answered the actual question, using the named field, role or model.
  • I identified my observation and explained why it happened.
  • I justified my independent choice with a purpose or assumption.
  • I named one limit and distinguished a proposal from something I executed.

Two or three clear sentences can be sufficient for a short prompt; follow the lab's more specific guidance when provided. Length and polished formatting do not substitute for reasoning. A justified alternative can be valid even if it differs from an example. Use a peer when available, but peer access is not a prerequisite.

Example response from a different scenario

Question: Does a successful library-summary query establish that borrower contact details are protected?

Example: "The library reader could read the summary. That confirms this allowed query, but it does not test access to contact details. I would test a contact-detail query as the same reader and verify the intended permission denial. That second check is proposed; I have not run it."

This answer names the evidence, limits the claim and proposes a specific next check. It is an example of structure, not a result you should claim for the retail labs. For AI reasoning, use the separate fictional decision example.

When you are stuck

  1. Stop at the first unexpected error; save your current file before experimenting.
  2. Check that you are in the repository root and using Ubuntu, then compare the command and expected result with the same lab step.
  3. Follow troubleshooting. A documented 42501 denial can be expected; an unrelated error is not equivalent. Do not delete work to retry.
  4. Write: lab/step, expected result, observed result, what I tried. This often reveals the missing concept and forms a useful help request.

Enrolled students use the instructor's private support route. Independent learners may open a repository issue for a reproducible instruction or software problem, following contribution guidance. Include the Ubuntu version, command, step and a minimal sanitized error. Replace personal paths with <local path>. Share a synthetic example only, not your filled assignment, complete logs, .env, passwords, keys or connection strings.

For a suspected security vulnerability or exposure, use SECURITY.md instead of a public issue. Public issues are not a grading or guaranteed tutoring service; response times and individual support are not promised. If blocked by an administrator-only installation problem, ask your device administrator or use an individual supported Ubuntu VM. You can continue reading and reasoning activities while recording that technical execution remains incomplete.

Author: Isaac K. Nti. Citation and reuse terms.