Automation on Work You Can Explain

Calendar Event or Task? Choose by What Must Happen

Thu, 03 Sep 2026 00:00:00 -0500

Use a calendar for something that happens at a fixed time or reserves a specific block of time. Use a task list for an action that remains incomplete until you finish it. Use both only when the action and the time reservation serve different purposes.

The distinction prevents two common failures: filling a calendar with flexible work that constantly moves, and leaving fixed appointments in a task list that does not protect the required time.

Automate Due-Date Reminders Without Bloated Apps

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

Automate reminders only after the course milestones are correct. Keep the Markdown dashboard or register as the source, generate a small reminder output, inspect it, test one non-critical event, and record how to replace it when the source changes. Automation should reduce repeated entry, not hide the dates or create another system you must maintain.

Why this matters

Reminder systems fail in two common ways. They contain the wrong date because a source was never checked, or they contain the right date in several places that drift apart. A lightweight workflow starts with one source and makes the generated layer disposable.

Automate Deterministic Work with Code

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

Use code instead of repeated AI prompts when the same explicit inputs should produce defined outputs through known operations. Keep AI at the interpretation boundary: it can help explain an unfamiliar case or draft code, but deterministic execution should be inspectable, tested, and repeatable.

Define the contract

Before scripting, write:

Inputs:
Outputs:
Files or systems changed:
Valid and invalid conditions:
Expected failures:
Verification:
Rollback:

For example, renaming assignment files by a documented convention can be deterministic. Deciding whether a student’s reflection demonstrates understanding requires judgment and should not be hidden in a rename script.

Automation Is the Last Step, Not the First

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

Automate a workflow only after you can perform it manually, explain its decisions, and verify its result. Begin with a working procedure. Document it, move deterministic steps into code, test the code, and add scheduling only when monitoring and recovery are ready.

Automation multiplies the workflow you give it. If the workflow is unclear, automation repeats unclear decisions faster.

Perform the work manually first

Complete the task on a small, representative example. Record:

Pipes and Redirection: The Composable Power of the CLI

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

Command-line tools become composable when they can receive input and produce output through standard interfaces. A pipe connects one command’s normal output to another command’s input. Redirection sends a stream to a file or another destination.

Learn the data flow before memorizing operators. Exact syntax differs among shells, and PowerShell pipelines can pass structured objects rather than only text.

A command can use three standard streams

A process commonly begins with three channels:

Should This Be a Note, Checklist, Script, or Skill?

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

Choose the smallest reusable form that preserves the verified value. Use a note for understanding, a checklist for human judgment, a script for deterministic operations, a project convention for repository-wide behavior, a skill for agentic interpretation, and automation only when a stable trigger should run a known action.

Note: preserve understanding

Use a note when the main value is an explanation, decision, example, or source. A note can answer why a configuration exists or what an error taught you.

Source Files and Generated Files Are Not the Same

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

A project folder can contain files that look equally important but have very different roles. The Markdown document you edit is not the same kind of artifact as the PDF exported from it. Raw measurements are not the same as a chart generated from those measurements.

The practical rule is simple: protect what you cannot reliably recreate, and document how to recreate everything else. This requires more judgment than sorting files by extension.

What Is Plain Text, and Why Should a Student Care?

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

A plain-text file stores characters that a text editor can show directly. It does not require the application that created it to reconstruct a page, workbook, or drawing before you can inspect the underlying content.

Plain text matters because it gives students a simple source that many tools can open, search, compare, and transform. Use it when text can represent the work well. Use a richer format when layout, formulas, media, or a required review workflow is part of the job.

Terminal-First, Text-First, Reusable-by-Default

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

Student computing includes many separate activities: organizing files, writing papers, programming, taking notes, using AI, and recovering from mistakes. Three principles provide a consistent direction across those activities: terminal-first, text-first, and reusable-by-default.

These are preferences, not absolute rules. Each principle makes important work more visible and easier to understand.

Terminal-first makes operations visible

A terminal accepts text commands and displays text output. It exposes details that graphical interfaces often hide: