Two projects, one methodology - AI collaboration at scale
Documentation is one of the most time-consuming tasks in systems administration. It requires deep technical knowledge, clear writing, consistent formatting, and the patience to cover every detail - sometimes hundreds of times across hundreds of commands, concepts, and procedures.
This page documents two real AI collaboration projects that tackled documentation at very different scales and for very different purposes. Together they demonstrate that AI collaboration isn't a trick that works in one narrow situation - it's a general methodology that adapts to the work.
Knowledge transfer documentation for a 26-year Unix/Linux career
After 26 years as a Systems Administrator at Binghamton University, Craig faces a common challenge in IT: how do you transfer 40+ years of accumulated knowledge before you leave? Not just the what, but the why - the reasoning, the gotchas, the real-world context that never makes it into man pages.
The goal: build a comprehensive HTML reference library covering Linux commands, system administration concepts, networking tools, and enterprise procedures - documentation detailed enough that a replacement administrator could hit the ground running.
Building a public teaching resource about AI - using AI to build it
The second project is this website itself. Craig wanted to create an educational resource about AI for colleagues, family, and anyone curious about how AI tools actually work in practice. The meta-twist: using AI collaboration to build a site about AI collaboration.
Unlike the command reference library - which was repetitive by design - the education site required creative decision-making, evolving structure, and continuous judgment calls about what to include, how to explain it, and how to make it genuinely useful.
| Aspect | Linux Reference Library | AI Education Site |
|---|---|---|
| Work type | Repetitive, structured | Creative, evolving |
| Primary challenge | Volume and consistency | Structure and direction |
| Craig's main role | Subject matter expert | Architect and editor |
| Claude's main role | Consistent page generator | Builder and problem-solver |
| Context management | Template-driven | Daily diary uploads |
| Quality control | Technical accuracy checks | Design and content reviews |
Despite their differences, both projects succeed for the same fundamental reasons:
In both cases, Craig's domain knowledge - 40 years of Unix/Linux experience for the reference library, years of teaching and systems thinking for the education site - is what makes the output valuable. AI provides capability and speed. The human provides the knowledge and judgment that make it worth reading.
Both projects use consistent patterns: a page template for the reference library, a session diary workflow for the education site. Structure lets you work at scale without losing coherence.
Neither project accepts first drafts. Every page, every section goes through review and refinement. The efficiency gain comes from AI handling the initial heavy lifting - not from skipping quality control.
Across both projects, the estimated efficiency multiplier is approximately 9x - meaning work that would take 9 hours solo gets done in roughly 1 hour with AI collaboration. This isn't a marketing claim. It's a measured observation from hundreds of hours of real work. See the 9x Efficiency Multiplier case study for the full methodology.
Before writing page one, decide what every page will contain. Headers, sections, standard elements. Give Claude the template and say "build every page like this." Consistency is free when AI does the formatting.
Your job is to know what needs to be said - the real-world gotchas, the institutional knowledge, the edge cases from 20 years of experience. Let AI handle turning that knowledge into well-formatted, complete documentation.
For ongoing projects, keep a running document that captures decisions, standards, and context. Upload it at the start of each session. This is the difference between starting cold every time and picking up exactly where you left off.
AI is excellent at structure, explanation, and completeness. It is not always right about specific syntax, version differences, or platform-specific behavior. Your expert eye is the final quality gate - don't skip it.