DDD, local canvas, and caught-up journals
A day of publishing DDD with EventStorming tutorials, reviewing blog images, exploring local canvas tools, and updating the daily journal.
Today connected learning, writing, and tooling. DDD stopped being only a concept and became published material, with examples closer to systems I understand in practice.
Blog and DDD
On the site, I worked on posts about Domain-Driven Design with EventStorming. The editorial line was to explain from the beginning to code: domain, subdomains, domain experts, events, commands, rules, and bounded context.
I also refined titles, descriptions, and post images so the content became clearer before the click. One important adjustment was fixing blog cover framing, avoiding bad crops in images that need to communicate the article idea.
Canvas and visual modeling
Another block was studying local canvas tools. I compared paths like Excalidraw and tldraw, looked at local persistence, SQLite, Docker, and how to keep state without disturbing the main environment.
That research connects directly with EventStorming. If I want to learn DDD while producing software, I need a good place to map events, commands, decisions, and processes, then turn that into code.
Daily journal
I also started catching up the delayed journals. The work required sweeping agent sessions, filtering private content, and turning busy days into useful public records.
I ended the day with a simple thesis: visual modeling only matters when it helps the software move.