docs: add CLAUDE.md and README.md
Introduce CLAUDE.md with guidelines for AI assistance in article writing and repository conventions. Add README.md with an overview of published articles, drafts, and repository structure.
This commit is contained in:
Gregory Gauthier
parent
f9a3674abd
commit
0c17c3ed55
47
CLAUDE.md
47
CLAUDE.md
@ -0,0 +1,47 @@
|
|||||||
|
# CLAUDE.md
|
||||||
|
|
||||||
|
## What This Repository Is
|
||||||
|
|
||||||
|
This is a personal blog of long-form articles written by Gregory Gauthier, a software tester and automation engineer. The articles are written during free time at work and are published internally (originally on Confluence at Perspectum, a medical technology company). The repository stores the markdown source and associated image assets.
|
||||||
|
|
||||||
|
## Writing Style and Voice
|
||||||
|
|
||||||
|
Gregory's articles have a distinctive style that Claude should understand and respect, but never attempt to replicate wholesale. The voice is his own. Key characteristics:
|
||||||
|
|
||||||
|
- **Philosophical grounding**: Articles regularly draw on formal philosophy — Aristotle (telos, phronesis, hexis, techne), epistemology, formal logic (modus ponens, modus tollens), and philosophy of science. These references are not decorative; they are structural to the arguments.
|
||||||
|
- **Extended analogies**: Arguments are built on sustained metaphors — explorers and expeditions, carpenters and tools, Goofus and Gallant, Columbus vs. Lewis and Clark. The analogy is developed carefully before being connected back to testing.
|
||||||
|
- **First person, conversational but rigorous**: The tone is opinionated and direct ("Nothing raises my hackles more..."), self-deprecating where appropriate ("Before I puff myself up too much..."), and intellectually honest about counterarguments.
|
||||||
|
- **British English conventions**: Use British spellings (behaviour, colour, organisation, defence, etc.).
|
||||||
|
- **Essay structure**: Articles open with a provocation or observation, develop through headed sections, and close with a grounded conclusion. They do not end with generic summary paragraphs or calls to action.
|
||||||
|
- **Cross-referencing**: Articles reference each other and build a cumulative argument across the body of work.
|
||||||
|
|
||||||
|
## How Claude Can Help
|
||||||
|
|
||||||
|
### Brainstorming and Ideation
|
||||||
|
- Suggest connections between testing concepts and ideas from other disciplines (philosophy, science, history, mathematics) that could seed new articles.
|
||||||
|
- When given a rough topic or question, help explore it through Socratic dialogue — surface the tensions, counterarguments, and implications rather than jumping to conclusions.
|
||||||
|
- Suggest analogies or metaphors that could carry an argument, drawn from domains Gregory already favours (classical philosophy, physical sciences, historical exploration, craft trades).
|
||||||
|
|
||||||
|
### Research Assistance
|
||||||
|
- Look up and summarise academic or technical sources relevant to a topic under exploration.
|
||||||
|
- Verify claims, quotations, and attributions before they go into a draft.
|
||||||
|
- Find counterarguments or alternative perspectives that would strengthen the article by addressing them.
|
||||||
|
|
||||||
|
### Drafting Support
|
||||||
|
- Help expand outline notes (like those in `articles/drafts/`) into fuller prose, but always as raw material for Gregory to rewrite in his own voice — never as finished text to publish directly.
|
||||||
|
- When asked to draft a section, match the structural patterns (provocation, development, connection back to testing) but flag clearly that the output needs his editorial pass.
|
||||||
|
- Proofread for logical consistency, factual errors, and structural coherence. Do not "fix" stylistic choices or voice.
|
||||||
|
|
||||||
|
### What Claude Should NOT Do
|
||||||
|
- Do not generate complete articles and present them as ready to publish. Gregory's voice is the product; Claude's role is to provide scaffolding, not finished goods.
|
||||||
|
- Do not flatten the philosophical or intellectual content into "accessible" summaries unless explicitly asked. The audience is technical colleagues who can handle the complexity.
|
||||||
|
- Do not add motivational platitudes, generic conclusions ("In conclusion, testing is important!"), or marketing-style calls to action.
|
||||||
|
- Do not suggest topics that are purely trend-chasing (e.g., "Top 10 AI Testing Tools in 2026"). The blog is reflective and argumentative, not listicle-driven.
|
||||||
|
- Do not sanitise opinions. The articles take positions and defend them. Hedging everything into bland neutrality defeats the purpose.
|
||||||
|
|
||||||
|
## Repository Conventions
|
||||||
|
|
||||||
|
- Published articles go in `articles/published/`
|
||||||
|
- Work-in-progress goes in `articles/drafts/`
|
||||||
|
- Images and assets are organised by type under `assets/` (clipart, general, memes)
|
||||||
|
- Articles are written in Markdown with inline image references and hyperlinks
|
||||||
36
README.md
36
README.md
@ -0,0 +1,36 @@
|
|||||||
|
# Work Blog
|
||||||
|
|
||||||
|
A collection of articles on software testing, test engineering, and Agile methodology by Gregory Gauthier.
|
||||||
|
|
||||||
|
## Published Articles
|
||||||
|
|
||||||
|
| Article | Topic |
|
||||||
|
|---------|-------|
|
||||||
|
| [Testers As Explorers](articles/published/Testers-As-Explorers.md) | Exploratory testing as chartered expedition, not aimless wandering |
|
||||||
|
| [Agile, Or Whatever You Call It](articles/published/Agile-Or-Whatever-You-Call-It.md) | The case for Agile practices beyond the buzzword |
|
||||||
|
| [The Various Uses Of Vegetable Condiments In Testing](articles/published/The-Various-Uses-Of-Vegetable-Condiments-In-Testing.md) | BDD, Gherkin, and the proper use of Cucumber |
|
||||||
|
| [Five Essential Lessons](articles/published/five-essential-lessons.md) | Key takeaways from *Lessons Learned In Software Testing* |
|
||||||
|
| [The Categories Of Testing](articles/published/the-categories-of-testing.md) | Categorising tests by the kinds of facts they discover |
|
||||||
|
| [The Perturbation Theory Of Exploratory Testing](articles/published/the-perturbation-theory-of-exploratory-testing.md) | Applying perturbation theory concepts to exploratory testing |
|
||||||
|
| [What Is A Competent Tester?](articles/published/what-is-a-competent-tester.md) | Joel Spolsky on the distinction between testers and failed programmers |
|
||||||
|
| [The Logic Of Software Testing](articles/published/the-logic-of-software-testing.md) | Formal reasoning methods testers use: modus ponens, modus tollens, induction, and abduction |
|
||||||
|
| [Perfection And Testing](articles/published/perfection-and-testing.md) | Why testing is about managing risk and confidence, not chasing perfection |
|
||||||
|
| [Resources For Testers](articles/published/resources-for-testers.md) | Recommended books, blogs, and learning resources for software testers |
|
||||||
|
| [What Makes Us Better](articles/published/what-makes-us-better.md) | Whether AI tools like Claude change the *kind* of craft, not just the speed |
|
||||||
|
|
||||||
|
## Drafts
|
||||||
|
|
||||||
|
- [The Uses and Abuses of Test Automation](articles/drafts/uses-and-abuses.md)
|
||||||
|
- [Agile Stories](articles/drafts/agile-stories.md)
|
||||||
|
|
||||||
|
## Structure
|
||||||
|
|
||||||
|
```
|
||||||
|
articles/
|
||||||
|
published/ # Completed articles
|
||||||
|
drafts/ # Work in progress
|
||||||
|
assets/
|
||||||
|
clipart/ # Illustrative clipart
|
||||||
|
general/ # Screenshots and diagrams
|
||||||
|
memes/ # Memes referenced in articles
|
||||||
|
```
|
||||||
Loading…
Reference in New Issue
Block a user