Monthly Commit — Normalizing Template Chaos with Pre-Processing
Context — The “Real World” Word Document · Read more...
Latest posts
Refactoring for Contextual Clarity
Context — The “Boy Scout” of Document Processing · Read more...
Resolver Safety: Managing Nulls, Optionals, and Exception Strategies
Thesis — The document is your public API · Read more...
Declarative Testing: Text-to-Template Generation
Thesis — The “Binary Friction” of Document Testing · Read more...
Mastering Nested Document Structures
In document automation, the “what you see is what you get” promise of Word often hides a complex, nested reality. This month, I addressed a long-standing limitation in how OfficeStamper perceives a paragraph. By moving from a flat traversal to... · Read more...
From Walkers to Streams
Sustainable maintenance often starts with deleting code that forces you to lie about your intentions. This month, I finally removed the CoordinatesWalker — a legacy artifact from the original docx-stamper library — and replaced it with functional streams. · Read more...
Modular Reorg on the Path to 2.0
Sustainable agility depends on boundaries you can explain and defend. This month I drew those boundaries explicitly: I introduced an engine module, moved public entry points into intention‑revealing packages, and removed legacy shims. The goal is clear seams: a stable... · Read more...
Package contracts as code
Package‑level contracts, visible to humans and tools. I added package-info.java to state intent and enforce non‑null by default. Clear boundaries: core is internal and volatile, api is the extension surface, preset is a safe bootstrap and living examples. · Read more...
PPTX Stamping Lands Without Touching the Engine Core
PPTX stamping was added as a bounded adapter, proving the engine scales to a new format without touching the core. · Read more...
Unit Tests Don’t Mean What You Think: Characterization Testing WordprocessingML in Office‑stamper
Thesis — “Unit test” doesn’t mean what you think it means · Read more...