I created interactive experiences to show what really happens behind actions that seem simple
A cookie accepted with one click, two systems connected through an API, a task to automate, user authentication, or even a Factur-X invoice.
From the outside, many technical actions look simple.
And that's perfectly normal.
Users see the result, not necessarily everything that needs to happen behind the scenes for that result to work properly.
Of course, these mechanisms can be explained through articles, documentation, or diagrams, but not everyone wants to read several pages to understand a topic, some simply don't have the time, while others understand things better when they can visually follow what is happening.
That's why I started creating a series of interactive experiences.
Understand in just a few clicks
The principle is intentionally simple.
Each experience starts with an action or idea that seems straightforward, then gradually reveals what is actually happening behind the scenes.
Let's take automation.
A request can start with something as simple as:
"Could we automate this task?"
For the person making the request, it really is just one task.
But integrating it properly into a system may require analyzing the existing process, defining business rules, validating data, anticipating errors, securing execution, handling repeated runs, testing different scenarios, and making sure the system remains stable over time.
The experience isn't designed to turn visitors into developers, it simply makes this part of the work visible.
Showing what the interface doesn't show
That's the common thread throughout the collection.
An API can make it look like two systems are simply exchanging data, yet behind a single request there may be authentication, validation, processing, response codes, errors, timeouts, and retries.
A user login may look like nothing more than an email address and a password, while a properly built application needs to perform several checks before granting access.
A Factur-X invoice looks like a PDF, but it also contains structured XML data, and both representations need to tell the same story.
A cookie may seem insignificant, yet it can become the starting point of a much larger chain involving data collection and profiling.
The goal isn't to make these topics seem artificially complicated or alarming, but to show that between a visible action and its result, there is often an entire system the user never sees.
Another way to talk about technology
I like technical articles and documentation, and I publish those too, but I wanted to add a different format.
Something you can explore quickly, without requiring any particular technical background, where a few clicks are enough to understand an idea.
The experiences are therefore intentionally short, visual, and progressive.
Today, the collection covers several areas:
- systems and architecture, with from-scratch development, APIs, and automation
- security and data, with application authentication, cookies, and personal data
- electronic invoicing, with Factur-X
More experiences will be added to the collection, because there are still plenty of technical mechanisms worth making visible this way.
Explore the interactive experiences
If you'd rather experience something than read a long explanation, or if you simply want to discover what happens behind some of the mechanisms we use every day, the full collection is available here:
Explore the interactive experiences
A few clicks are enough, then it's up to you to decide how far you want to follow the journey.
Top comments (0)