To my English readers: this post talks about electronic voting and how it impacts democracies. Even if this thinking can be applied to other countries, I wanted to remain focus on the French context. That’s why I exceptionally decided to write in French.

This blog post is the last of a series where we’re using The Elm Architecture (TEA). If you haven’t, I strongly recommend reading the previous articles first.

So far we’ve learned how to build an application and run side effects. But as our programs grow, we may feel the need to break things down. Today we’ll see how to split our page in different modules. This can be for isolating some logic and reduce cognitive load, favor views composition or allow reusability.

This blog post is part of a series where we’re using The Elm Architecture (TEA). If you haven’t, I strongly recommend reading the previous articles first.

In the previous post, we’ve introduced the Elm Architecture (TEA) and then wrote a PReact component to implement this pattern. Today it’s time to use it! If you haven’t, I recommend that you read the first post before continuing on this one.

A few months ago in my post Reaching a limit of Reactive Programming, I’ve mentioned the MVU (Model-View-Update) pattern could be a solution to the problems I was encountering at that time. I’m now using MVU since a few months on other projects and I want to write my own article where I present this pattern in more details.

If you’re working in IT, you’ve probably already encountered the “No deployments on Friday” mantra/dogma. It’s so ubiquitous that they’re many memes about it on the internet.

I’ve recently finished reading Real-World Event Sourcing. It was a fun reading, but I found the book unclear on a very specific point and I want to express my thoughts on it in this blog post. I may have misinterpreted the author’s explanations but this doesn’t invalidate the following reflection.

In my career, I had (and still have) many opportunities to develop UIs on desktop and web applications using various technologies. With these experiences I’ve been using two main patterns: MVVM (Model-View-ViewModel) and a Reactive approach.

In a previous post, I’ve mentioned I’ve read the book Programming Elixir 1.6.

As I was planning to read Real-World Event Sourcing, I chose to conduct a second reading because my limited knowledge and skills with Elixir were eroded over time. I took time to take many notes which are available on a dedicated repository.

A few weeks ago, I’ve published a post where I described improvements for various architectures, following a logical path from a CRUD architecture to a CQRS/ES implementation.

Since then, I participated in Lyon Craft 2025, a local conference focusing on the software craftsmanship mindset and practices. For this edition, we had the pleasure to invite Jérémie Chassaing for an event-sourcing workshop. I had the opportunity to discuss with him and attend his workshop.