In the rush to put AI into everything, we’re losing sight of craftsmanship. For me, being a “Caring Coder” means more than passing tests. It means the governance we build around the tools that make decisions on our behalf.
Craftsmanship as risk management
In high-stakes sectors, “good enough” automation isn’t good enough. If a document generator produces a faulty safety report because an LLM was unconstrained, the coder is responsible, not the model.
Why I keep caring
I’ll keep caring about document generation as AI gets better, because the handover between human intent and machine execution is where the risk lives. Strict Java standards and security-first SpEL patterns aren’t just a library. They’re a safety net for automated decisions.
The discipline doesn’t disappear when a model writes the words. If anything, it matters more, because the model has no idea what it’s being asked to vouch for.