Documentation on Work You Can Explain

Does This Source Actually Support Your Sentence?

Tue, 08 Sep 2026 00:00:00 -0500

A citation supports a sentence only when the source provides evidence for the sentence’s actual meaning. Compare the population, conditions, outcome, and strength of the claim with the relevant passage or result. Revise the sentence when it says more than the evidence allows.

The goal is a sentence you can defend by opening the cited source and explaining the connection. A citation at the end of a paragraph cannot do that reasoning for you.

Find the Original Source Behind a Research Summary

Tue, 08 Sep 2026 00:00:00 -0500

A research summary is a starting point. Follow its references until you reach the study, dataset, historical document, or other material that produced the evidence. Then identify where that source describes the work relevant to your question.

Your first result can be modest: one original source, a stable way to return to it, and a section to read next. You do not need a large bibliography before you can begin checking what a summary means.

Keep Research Notes Connected to Their Sources

Tue, 08 Sep 2026 00:00:00 -0500

Keep enough context in a research note to return to the evidence later: the source’s identity, the relevant location, what the source says, and how you intend to use it. Separate copied wording from paraphrase and personal interpretation as you read.

The useful test is simple. Close the source, reopen it from the note, and recover the passage behind your claim. If you cannot do that, a polished summary is still missing an essential part of the research work.

Verify a Citation Before You Use It

Tue, 08 Sep 2026 00:00:00 -0500

A citation is usable only when you can identify the work it names. Match the reference against an authoritative publication or library record, open the matching work, and check which version you have. Resolve discrepancies before copying the citation into an assignment.

This establishes identity. It does not establish that the work is reliable or supports your sentence. Keep those judgments separate.

Compare the reference with the actual work

Begin with the reference as you received it, whether it came from a class reading, an AI answer, a reference manager, or your own notes. Search the exact title through a publisher, library catalog, or scholarly index. A DOI, when supplied, gives another route to a record.

Handle LMS Course Changes Before They Become Surprises

Fri, 28 Aug 2026 00:00:00 -0500

Most students do not need a course-change register or a weekly LMS audit. Turn on useful LMS and mobile notifications, keep the course information you already received, and pay attention when a new date, file, or instruction conflicts with it.

When a conflict appears, do not silently replace the old information. Check the current course sources and ask the instructor or other person in charge when the answer is still unclear. If the surprise causes a missed deadline, attendance problem, or penalty, preserve enough evidence to explain what happened and request a review.

Build a Course Dashboard in Markdown

Mon, 24 Aug 2026 00:00:00 -0500

A course dashboard is an index, not a second copy of the course. Use one small Markdown file to connect the syllabus register, course folders, milestones, current status, open questions, and next action. Link to the authoritative files and test the links after you move anything.

Why this matters

Students can have complete notes and still lose time locating the current syllabus, next assignment, or unresolved question. A dashboard gives one course a visible current state without requiring a new database or a full rewrite of the source material.

Extract Deadlines and Hard Rules from a Syllabus or LMS

Mon, 24 Aug 2026 00:00:00 -0500

A syllabus or LMS course source is information to verify, not yet a working plan. The practical first step is to preserve or bookmark the original and extract only the dates, rules, and conditions that can change what you do. Keep the source location beside every entry, and mark anything uncertain until you verify it.

Why this matters

Course information is often split across a syllabus, an LMS page, an assignment description, and later announcements. The syllabus may be a PDF, but an LMS activity can be a web page rather than a downloadable file. Copying everything into a new note feels productive but creates a second document that can drift from the course source.

Find AI Information Through Builders, Not Just Influencers

Mon, 24 Aug 2026 00:00:00 -0500

When an AI topic becomes noisy, do not begin by following the loudest account. Use commentators and aggregators to discover questions, find builders or practitioners who have done relevant work, trace the material claim to primary evidence, and record the conditions that limit your conclusion.

“Builder” is a role in relation to a claim, not a popularity score. A researcher, maintainer, operator, educator, or domain practitioner may be a builder when their relevant work can be inspected or described. A confident personal brand is not enough.

Organize LMS Downloads and Lecture Notes into a Clean Course Workspace

Mon, 24 Aug 2026 00:00:00 -0500

Use Downloads as an inbox, not as your course system. For each item, identify the course and responsibility, move it to one canonical location, and verify that the copy opens before deleting anything. Keep the syllabus register and other source-linked records close to the course information they describe.

Why this matters

An LMS is useful for delivery, but browser history and a downloads folder are poor long-term indexes. A file named document (7).pdf does not tell you which course it belongs to, whether it is current, or where its related notes live.

Communicating with Instructors During a Technical Crisis

Wed, 19 Aug 2026 00:00:00 -0500

When a technical problem may affect an assignment, contact the instructor as soon as the risk is clear. The message should make the situation easy to understand: identify the course and assignment, describe what happened, state what you have checked, explain the current risk, and make one specific request.

You do not need to prove the final cause before sending the first message. You do need to be accurate about what you observed and what you have tried.

Emergency Triage for Broken Assignments and Files

Wed, 19 Aug 2026 00:00:00 -0500

When an assignment file disappears or stops opening, your first job is not to fix it. Your first job is to preserve what still exists and understand the situation well enough to choose a safe next step.

Do not keep editing the only copy. Do not reinstall software because one file failed. Do not run a destructive command because an AI assistant suggested it. Make a protected copy, write down the facts, and work from the copy.

Build a Reproducible Linux Setup

Thu, 30 Jul 2026 00:00:00 -0500

A reproducible Linux setup needs a named target. This walkthrough targets Ubuntu 26.04 LTS, not every Linux distribution. It records the packages, selected user configuration, manual decisions, bootstrap order, and verification needed for one course environment.

The repository will not recreate hardware, firmware, disk layout, encrypted data, online accounts, or every historical application. It should restore required capability on the named target and explain its limits.

Define the exact target

Record:

Use a Chatbot to Complete a Complicated Template

Tue, 28 Jul 2026 00:00:00 -0500

A complicated template does not have to be completed as one long writing task. Open a dedicated chatbot thread, paste the template, provide only safe relevant context, and ask the chatbot to collect the information one field at a time. After you review the answers, have it produce the complete document in the required format.

The chatbot may extract, clarify, organize, and format. It must not invent an answer or make the final decision for you.

A College Folder Structure That Can Survive Four Years

Fri, 24 Jul 2026 00:00:00 -0500

A useful college folder structure should answer one question quickly: where would I look for this file? It should not require a complex tagging system or a new organization project every semester.

Start with one academic root. Organize course work by year or term and course, keep administrative records separate, and give substantial projects their own folders. Add another level only after a repeated retrieval problem justifies it.

Use a small stable top level

Create one folder such as Education in a location that fits your device, institutional rules, and backup plan.

A Project README That Lets Someone Else Succeed

Fri, 24 Jul 2026 00:00:00 -0500

A README succeeds when another person can understand the project and reproduce its expected result without reconstructing your memory. State what the project does, what it requires, how to install, run, test, and verify it, and where to get help.

Write for a defined reader

Name the reader and starting state:

These instructions are for a CS 101 student with Git and Python 3.13 installed who has cloned the repository but has not created the environment.

A Project Structure That Encourages Good Habits

Fri, 24 Jul 2026 00:00:00 -0500

A useful project structure makes the next correct action easy to find. Keep source, tests, documentation, scripts, and examples in predictable locations. Start small, name each directory by responsibility, and add complexity only when the project needs it.

The goal is not a universal folder tree. It is a project another person can inspect, run, test, and explain.

Begin at one clear project root

The project root contains the files that describe the project as a unit:

AI Can Be Confident and Wrong

Fri, 24 Jul 2026 00:00:00 -0500

AI confidence is a feature of presentation, not evidence of correctness. Generated output can contain false citations, nonexistent APIs, code that works only for the example, hidden assumptions, or unnecessary complexity.

Break the response into claims. Verify factual claims in primary sources and technical behavior with official documentation and reproducible tests. Mark unsupported claims as uncertain or reject them.

Confabulation can sound specific

NIST’s Generative AI Profile uses confabulation for erroneous or false content that a generative AI system presents confidently. The report notes that output can also contradict the prompt or earlier output.

Before You Ask AI, Write Down What You Know

Fri, 24 Jul 2026 00:00:00 -0500

Before asking AI, write down the task in your own words, what you know, what remains unknown, what you attempted, and what the evidence showed.

This record protects independent reasoning. It also gives the AI less room to invent the problem, select hidden assumptions, or replace the student’s next step.

Start with the task and policy

Record the actual objective:

Task: Explain why my loop skips the last element.
Course boundary: AI may explain errors, but may not write assignment code.
Private material: Do not share the full assignment or student data.

Course rules differ. A tutoring interaction allowed in one course can be prohibited in another. If the boundary is unclear, stop and ask the instructor.

Build a Reproducible Windows Setup

Fri, 24 Jul 2026 00:00:00 -0500

A reproducible Windows setup is not a screenshot of installed applications. It is a tested set of source artifacts that explains what the student needs, how to establish it, and how to verify the result.

Create a versioned repository containing package IDs, an inspected WinGet export or configuration, small setup steps, secret-free examples, and a verification script. Begin with current course requirements, not every application installed over the computer’s lifetime.

Build a Small Portfolio with Depth

Fri, 24 Jul 2026 00:00:00 -0500

A strong student portfolio does not need many projects. Select a few pieces that you can explain deeply: the problem, constraints, decisions, implementation, tests, failures, evidence, credits, and what you would improve.

Do not invent users, metrics, test results, deployment status, or independent work. Honest limitations show more judgment than unsupported claims.

Select for depth

Choose a project when you can provide most of this evidence:

a clearly stated problem and audience;
requirements and non-goals;
meaningful decisions with alternatives;
source and reproducible setup;
tests tied to expected behavior;
one investigated failure or revision;
a working demonstration or accurate screenshots;
your specific contribution;
credits and license information; and
reflection based on observed results.

A small class project can be valuable when the reasoning is visible. Ten cloned tutorials with changed colors provide weak evidence.

Don’t Let a Useful AI Conversation Disappear

Fri, 24 Jul 2026 00:00:00 -0500

A useful AI conversation is not durable documentation. It may contain false starts, hidden context, private information, and conclusions that only make sense inside the exchange. Capture the verified lesson in your own record.

Record the problem

State the original objective, starting state, constraints, and exact failure or question. Include software versions, current directory, input shape, and error text only when relevant and safe.

Do not begin with “AI fixed it.” A future reader needs the technical problem.

Files, Folders, Paths, and Extensions Without the Mystery

Fri, 24 Jul 2026 00:00:00 -0500

A recent-file list can open a document without showing where it lives. That convenience becomes a problem when a terminal, programming tool, or error message asks for a path.

You need four connected ideas: a file stores an item, a folder organizes items, a path describes a location, and an extension is part of a filename. Once you connect those ideas to the home and current directories, file operations become more predictable.

How to Make a Useful Commit

Fri, 24 Jul 2026 00:00:00 -0500

A useful commit is a small, understandable checkpoint. It contains one logical change, excludes unrelated files and secrets, records a descriptive message, and follows relevant verification.

Define the change before staging

State the outcome in one sentence:

Add input validation for an empty student name.

If the sentence requires “and” to join unrelated outcomes, consider separate commits. A single logical change may touch code, tests, and documentation when they jointly implement one outcome.

Learn to Ask a Command for Help

Fri, 24 Jul 2026 00:00:00 -0500

You do not need to memorize every command. You need a reliable way to discover what a command does, which inputs it accepts, and how to verify a safe first use. Start with the command’s local help, identify the exact implementation, then consult its official documentation when needed.

Use a command-discovery checklist

For an unfamiliar command:

Identify the command and the shell that will run it.
Confirm where the command comes from.
Open local help.
Read the synopsis or syntax line before the examples.
Separate required inputs from optional ones.
Look up each unfamiliar option or parameter.
Find a read-only example with a small scope.
Predict the output and possible side effects.
Run it on a harmless target.
Check output, exit status, and resulting state.
Use the official online documentation when local help is incomplete.
Record the confirmed form in your working log.

This process is slower than blind copying once and faster than recovering from an unexplained command.

Markdown in 30 Minutes

Fri, 24 Jul 2026 00:00:00 -0500

You do not need a special editor or a complete syntax catalog to write useful Markdown. Start with readable plain text. Add a small set of markers for structure, then check both the source and the rendered result.

In 30 minutes, you can create a README.md that explains a project’s purpose, requirements, setup, and first command.

Five-minute Markdown quick start

If another guide sent you here before showing a Markdown example or template, this section is enough to continue. Markdown is readable plain text with a few markers for structure. A filename ending in .md identifies a Markdown file.

Rebuild a Student Windows PC from Documentation

Fri, 24 Jul 2026 00:00:00 -0500

Test recovery before a device failure, but do not reset a working student computer for practice.

Run a non-destructive rehearsal: inventory accounts and recovery access, restore test files to another location, clone a project into a new directory, inspect package manifests, follow setup documentation, and run verification. Record every missing dependency.

An actual Windows reset or reinstall is a separate destructive operation. It requires a real need, complete backup, BitLocker recovery access, official instructions, time, power, network access, and authorization for managed devices.

Stop Naming Files “Final-Final-2”

Fri, 24 Jul 2026 00:00:00 -0500

essay-final-final-2.docx does not tell you which copy is editable, which one a classmate reviewed, or which one you submitted. It records a sequence of uncertain decisions in a place that should identify the file.

Use a stable descriptive name. Add a sortable date or meaningful state only when it answers a real retrieval question. Keep one clear editable source, and use document version history or Git when the work needs actual change history.

The Semester-End Technical Review

Fri, 24 Jul 2026 00:00:00 -0500

End the semester with a bounded technical review. Archive course work without losing context, restore-test important files, remove unjustified tool obligations, update setup documentation, preserve verified repetition, and select portfolio evidence carefully.

Do not begin by deleting. First identify retention rules, final submissions, source material, recovery needs, and private content.

1. Inventory each course

For every course, record:

Course:
Term:
Instructor:
Required retention:
Final submitted artifacts:
Editable source:
Data and code:
Feedback:
Environment or tool requirements:
Private or restricted material:

Confirm institutional and course rules. Some work may need to remain private, and some licensed materials may not belong in a personal archive.

Use `AGENTS.md` to Teach an AI About a Repository

Fri, 24 Jul 2026 00:00:00 -0500

Use AGENTS.md for durable guidance that should apply across many agent tasks in a repository. Put project conventions, reliable setup and verification commands, scope boundaries, and review expectations there. Keep the current objective, temporary context, and one-time preferences in the task prompt.

OpenAI’s current AGENTS.md documentation explains that Codex reads instruction files before working. Instructions closer to the current directory take precedence over broader repository guidance, and an AGENTS.override.md file can replace an AGENTS.md file at the same level. Confirm the files Codex actually loaded before relying on those rules.

Write a Reproducible Bug Report

Fri, 24 Jul 2026 00:00:00 -0500

A useful bug report lets another person reproduce the failure or understand why they cannot. Include the environment, exact steps, expected and actual behavior, complete errors, and the smallest safe example that still fails.

Write a specific title

Use observable behavior:

CSV summary rejects a valid header containing spaces

Avoid “program broken” or a diagnosis you have not established.

Record the environment

Include only relevant facts:

operating system and version;
application, runtime, or library versions;
installation method;
current directory or repository commit;
configuration that changes behavior; and
hardware only when plausibly relevant.

Use commands or application information screens rather than memory. Redact usernames, device names, tokens, internal URLs, and private paths.

Start a Working Log Before You Change Anything

Thu, 23 Jul 2026 00:00:00 -0500

You install a program, change two settings, copy a command from an AI assistant, and finally get an assignment to run. A week later, the same project fails. You remember the general idea, but not the directory, command, error, or setting that mattered.

This is normal. Human memory is not a reliable record of technical work. Start a working log before you change the computer. Your first entry can be one short paragraph. Add more structure only when the work produces details worth preserving.

Start Here: A Practical Student Computing Workflow

Thu, 23 Jul 2026 00:00:00 -0500

Student computing involves more than choosing applications. You need a way to record changes, define requirements, evaluate tools, divide responsibility, and preserve useful work. The Student Computing Foundations collection provides that workflow through short, focused learning paths.

It is written for college students who want more control over their computing environment and for parents or mentors who want to help without permanently managing it for them. You do not need to complete every path or build a complete system now. Start with one working-log entry. Add the other opening practices when a real decision, tool, responsibility, or repeated process makes them useful, then choose the path that matches your current task.

Write a Personal System Charter Before Choosing Tools

Thu, 23 Jul 2026 00:00:00 -0500

A student asks, “Should I use Obsidian, Notion, or OneNote?” The question sounds specific, but it begins too late. Each application solves a different set of problems. Before comparing tools, define the system you need.

A personal system charter is a short Markdown document that records desired outcomes, constraints, non-goals, ownership, and evidence of success. It gives future decisions a stable reference point.

If .md files or Markdown markers are new to you, read the five-minute Markdown quick start before continuing. It explains the source notation used in the example and download below. You can return here without completing the full 30-minute exercise.