Work You Can Explain
Practical AI, computing, and learning for students
term
A practical recovery path for students dealing with damaged files, lost code, broken tools, missed deadlines, and the work of preventing a repeat.
Use this path when a technical problem threatens school work. Start by preserving the current state and recording the facts. Then recover the work, communicate clearly if a deadline is at risk, and turn the incident into one tested improvement.
Use the ordered guides as a recommended route. Begin with the first guide for a systematic introduction, or enter where your current task begins and follow prerequisite links as needed.
Articles
A calm, evidence-first protocol for protecting files, assessing damage, and choosing the next recovery step when student work breaks near a deadline.
Articles
Learn how to inspect local Git history, reflogs, and recovery copies without rewriting the repository before you know which version is correct.
Articles
Write a short, honest, evidence-backed message when a technical problem may affect an assignment, deadline, or submission.
Articles
Turn a technical incident into a small, tested improvement to your files, backups, documentation, or recovery workflow.
