Joseph Verron — IT Manager, CISO, and software craftsman

Joseph Verron

IT Manager & CISO — Energy Sector, China

Caring Coder · Java Craftsman · Secure AI Document Automation

I’m Joseph Verron. I help software teams build reliable systems and clear documentation. My work sits at the intersection of software craftsmanship and docs‑as‑code: practical techniques, repeatable pipelines, and small improvements that compound over time.

Today, I serve as the IT Manager and CISO for the Chinese subsidiary of a major organization in the energy sector. While my daily focus is on IT leadership and security, I remain a passionate software craftsman. I maintain Office-stamper as a dedicated hobby and partner with fellow self-entrepreneurs in China on small-scale, software-oriented projects.

Professional Philosophy

Caring about the craft is not nostalgia — it is the only sustainable answer to complexity. Security, reliability, and clear documentation are not constraints; they are necessary for a successful product. In an age where AI can scaffold anything in seconds, the differentiator is the engineer who understands why it works, what is about to break, and how to keep the product trustworthy.

Trust & Proof

Office-stamper — Open-Source Java Library

GitHub Stars GitHub Forks Maven Central Issues Closed

Office-stamper is a Java library for generating .docx and .pptx documents from real Word/PowerPoint templates using flexible data sources — safely and testably, while harnessing the full power of a programming language to express complex templates. It is used in energy-sector document automation and by Java teams who need to let business-facing users write the templates.

What users say

“This library saved us weeks of work. The template-based approach is exactly what we needed for our standardized specifications document generation pipeline.” — Oil & Gas enterprise Java team

“The stamping logic is sound, and I had .pptx slides working as expected in a few hours. Shame that the engine doesn’t support more complex template structures.” — Energy-sector independent R&D developer

Certifications & Publications

  • Maintainer of office-stamper — actively maintained since 2022. Forked from docx-stamper.
  • Contributor to the Java craftsmanship community via verron.pro.
  • IT Manager & CISO with hands-on experience securing enterprise infrastructure in the energy sector.

Interests

  • Docs‑as‑Code pipelines and governance.
  • Virtual Team & Automated Bots: Using tools like SonarQube and PIT to enforce quality as a solo maintainer.
  • GenAI for rapid scaffolding: Leveraging AI to accelerate the initial phases of lean tool development.
  • Developer Experience (DevX), automation, and CI/CD.

If you’re curious about what I’m working on, the Projects page highlights recent work; the full list of posts is in the Archive.

Operating Model — Influences and Practices

This section organizes the ideas, practices, and sources that shape my work. My influences are deliberate, complementary, and operational. They translate into repeatable ways of working that reduce delivery risk, make quality observable, and keep documentation, code, and architecture aligned.

Core motivations

  • Make complex work visible early and often. If we can see it, we can steer it.
  • Prefer small, safe steps that ship value continuously.
  • Treat docs, code, and diagrams as one artifact set. Reduce drift by generating and validating where possible.
  • Leave teams with tools and habits they can sustain without me.

Influences I stand on

  • Team Topologies — structure teams for fast flow and clear responsibilities.
  • Virtual Team (SonarQube, PIT) — as a solo maintainer, I rely on automated gatekeepers to catch what a human reviewer would.
  • GenAI Integration — leveraging AI for rapid scaffolding and lean tool development.
  • Docs‑as‑Code and Diagram‑as‑Code — text, versioned, reviewable, automated.
  • BDD and example‑guided development — make intent executable.
  • Conventional Commits and lightweight governance — predictable history, easier automation.

Practices I bring to projects

  1. Docs‑as‑Code foundation: Your documentation, run‑books, and decisions live with your code in Markdown, with CI checks.
  2. Template and document automation: I maintain Office‑stamper, used to generate .docx/.pptx/.xlsx from real templates safely and testably.
  3. Testing as infrastructure: Characterization tests make legacy safer to change; CI pipelines validate deliverables, docs and diagrams.
  4. Developer experience: Git hygiene, commit conventions, and helpful automation.

Resources

I maintain a curated catalog of tools, references, and inspirations that I use in my work. You can find the full list on the standalone Resources page.