Pattern Journal

This is not a textbook. This is a field notebook — patterns I’ve actually used, with dates and context proving they work. Organized by the Aristotelian categories of knowledge: how it’s acquired, how it’s applied, and why it matters.

Philosophy

  • Only real usage — If I haven’t used it, it doesn’t go here

  • Date everything — When did I use this? What was the context?

  • Show the problem — What was I trying to solve?

  • Extract the principle — The transferable wisdom, the arche (ἀρχή)

  • Link to evidence — Trace back to worklogs, projects, case studies

The Organon

Aristotle categorized knowledge not by subject matter, but by how it’s known and applied. This journal follows that structure:

Category Meaning What It Captures

Techne (τέχνη)

Productive knowledge — craft, skill, the art of making

Text processing, shell, vim, git, networking, security, infrastructure, Python, documentation, AI, ISE

Episteme (ἐπιστήμη)

Theoretical knowledge — understanding principles and why

Mathematics, formal reasoning

Phronesis (φρόνησις)

Practical wisdom — judgment in action, knowing when and how much

Career decisions, operational discipline, incident response

Poiesis (ποίησις)

Creative production — bringing something new into being

Language acquisition, music composition, literary analysis

Techne — Technical Arts

Core Tools

Domain Focus

Text Processing

awk, sed, grep, regex, jq, xargs, escaping — the Unix lingua franca

Shell & Process

Process substitution, parameter expansion, error handling, heredocs

Editor Mastery

Registers, macros, substitution, text objects, motions

Version Control

Branching strategies, rebase vs merge, multi-remote workflows

Engineering Domains

Domain Focus

Network Engineering

tcpdump, DNS/dig, wireless/EAP, firewalls, VLAN troubleshooting

Security Engineering

PKI/certificates, Vault operations, EAP-TLS, KQL/Sentinel, secrets management

Systems Engineering

systemd, LUKS/btrfs, KVM/QEMU, Borg backup, Stow/dotfiles

Navigation

USGS topo map reading, MGRS/UTM grids, protractor, compass, field practice

ISE / NAC

Policy sets, profiling, 802.1X troubleshooting

Software & Automation

Domain Focus

API Engineering

REST, curl, netapi, ISE ERS/DataConnect, Vault API, authentication, pagination

Python

CLI scripting, API requests, data processing

Docs-as-Code

AsciiDoc patterns, Antora multi-repo, cross-references

AI Engineering

Claude Code skills, hooks, agents, rules, prompting, orchestration

Episteme — Theoretical Knowledge

Domain Focus

Mathematics

Algebra, notation, problem-solving methods — understanding why the rules work

Phronesis — Practical Wisdom

Domain Focus

Professional Judgment

Incident response, vendor management, project estimation, negotiation

Operational Discipline

Change management, root cause analysis, prioritization

Poiesis — Creative Production

Domain Focus

Language Acquisition

Spanish, Latin — acquisition strategies proven through practice

Musical Craft

LilyPond engraving, music theory applied

Literary Analysis

Don Quijote, close reading methodology

How to Add Entries

Technical Entries (Techne)

== YYYY-MM-DD: Brief Description

**Problem:** What were you trying to do?
**Context:** What project/task? What tools involved?
**The Fix:**
  [source,bash]
  ----
  # WRONG
  command that didn't work

  # RIGHT
  command that worked
  ----
**Rule:** One-line takeaway for future reference
**Worklog:** WRKLOG-YYYY-MM-DD

Wisdom & Creative Entries (Phronesis, Poiesis, Episteme)

== YYYY-MM-DD: Brief Description

**Situation:** What prompted this insight?
**Context:** What domain? What circumstances?
**The Pattern:** What worked (or what failed)?
**Principle:** The transferable wisdom
**Source:** Worklog, book, conversation, lived experience

Codex vs Pattern Journal

Codex Pattern Journal

Reference cards, syntax tables

Dated entries with context

"How does this work?"

"When I hit X, I solved it with Y"

The library

The laboratory notebook

Rarely changes

Grows continuously

Organized by tool

Organized by Aristotelian category

Go to the Codex — generic reference material.

Patterns vs Standards

Patterns are descriptive — "what worked." Standards are prescriptive — "what MUST be done." When a pattern proves itself non-negotiable across contexts, it graduates to a Standard. The pattern remains as historical context; the standard becomes the enforceable rule.

Cross-References

  • Standards Framework — Normative governance documents (prescriptive)

  • CLI Codex — Generic reference (textbook)

  • Education — Curriculum and progress tracking

  • Projects — Where many of these patterns were discovered