How I moved monthly data refreshes, audits and a daily AI review off a laptop that was often closed, onto GitHub Actions: measuring access first, secrets that never pass through the assistant, one lock and a tested calendar, state kept in git, and the risk review that should have come before the merge.
Between January and September 2026, I led the upgrade of an editorial application’s rich-text editor from CKEditor 5 v26 to v47.3: about 55 in-house plugins, 53 sub-PRs and 683 files. Here is what we learned, from the bare-editor strategy to the bugs only real typing revealed, the AI tooling that made it repeatable, and the two CKEditor issues it led to.
Two Git commands that saved me from critical mistakes at work: git reflog to recover lost commits, and git rebase -i to rewrite history cleanly before a PR.
When we are working alone or as a team on a project and care about quality and security of our…
What is the hexagonal architecture? The hexagonal architecture is a case of application of DDD (Domain Driven Design). It allows…