Alexis "Horgix" Chotard
@horgix.fr
Staff SRE at @payfiteng.bsky.social & Maître Raclettier — Mostly posting about conferences & tech — 🔧 Automation, ❤️ Open-Source, ⚙️ Rust, 📣🎙️ Conferences {organizer, speaker, frequent attendee}
— Mandatory « I use Arch btw »
— Mandatory « I use Arch btw »
This dynamic definitely resonate with what were doing with DDD and event-driven architecture at PayFit !
October 16, 2025 at 2:46 PM
This dynamic definitely resonate with what were doing with DDD and event-driven architecture at PayFit !
Super interesting view and the room for learning with platforms. I truly think this was a missing piece in my understanding of platform trade-offs, I always got the feeling that abstracting everything away was introducing issues around that
October 16, 2025 at 2:46 PM
Super interesting view and the room for learning with platforms. I truly think this was a missing piece in my understanding of platform trade-offs, I always got the feeling that abstracting everything away was introducing issues around that
From Gregor Hohpe and Jean-Francois Landreau at #PlatformCon :
- Building compliance into the platform helps with adoption
- Guardrails for absolute emergencies, but otherwise, fast feedback and shifting left
- Don't mandate using your platform
- Reduce cognitive load without servicing
- Building compliance into the platform helps with adoption
- Guardrails for absolute emergencies, but otherwise, fast feedback and shifting left
- Don't mandate using your platform
- Reduce cognitive load without servicing
October 16, 2025 at 2:46 PM
From Gregor Hohpe and Jean-Francois Landreau at #PlatformCon :
- Building compliance into the platform helps with adoption
- Guardrails for absolute emergencies, but otherwise, fast feedback and shifting left
- Don't mandate using your platform
- Reduce cognitive load without servicing
- Building compliance into the platform helps with adoption
- Guardrails for absolute emergencies, but otherwise, fast feedback and shifting left
- Don't mandate using your platform
- Reduce cognitive load without servicing
As always, too much interesting things in a @kelseyhightower.com talk to list them all live from the #PlatformCon ; the gist of it:
- Learn to scale down
- You gotta understand the foundation (<3)
- Finish what you start
- Be intentional, not just reaction
- Read Promise Theory
With great humor :)
- Learn to scale down
- You gotta understand the foundation (<3)
- Finish what you start
- Be intentional, not just reaction
- Read Promise Theory
With great humor :)
October 16, 2025 at 8:26 AM
As always, too much interesting things in a @kelseyhightower.com talk to list them all live from the #PlatformCon ; the gist of it:
- Learn to scale down
- You gotta understand the foundation (<3)
- Finish what you start
- Be intentional, not just reaction
- Read Promise Theory
With great humor :)
- Learn to scale down
- You gotta understand the foundation (<3)
- Finish what you start
- Be intentional, not just reaction
- Read Promise Theory
With great humor :)
Can't wait for tomorrow: I'll be speaking at the #PlatformCon in Paris, along in the agenda with incredible people like @kelseyhightower.com, Gregor Hohpe and other - how lucky I am!
Come and listen about what Platform Engineering looks like behind the scene at @payfiteng.bsky.social at 14:30 :)
Come and listen about what Platform Engineering looks like behind the scene at @payfiteng.bsky.social at 14:30 :)
October 15, 2025 at 3:15 PM
Can't wait for tomorrow: I'll be speaking at the #PlatformCon in Paris, along in the agenda with incredible people like @kelseyhightower.com, Gregor Hohpe and other - how lucky I am!
Come and listen about what Platform Engineering looks like behind the scene at @payfiteng.bsky.social at 14:30 :)
Come and listen about what Platform Engineering looks like behind the scene at @payfiteng.bsky.social at 14:30 :)
Oh I can definitely relate 🙈
The fact I have an extension to even count tabs is a sign in itself that it went too far a long time ago already. I even had a Prometheus exporter for that at some point in order to be able to graph my tab count and motivate me to clean them up (guess what, it failed)
The fact I have an extension to even count tabs is a sign in itself that it went too far a long time ago already. I even had a Prometheus exporter for that at some point in order to be able to graph my tab count and motivate me to clean them up (guess what, it failed)
July 11, 2025 at 8:04 AM
Oh I can definitely relate 🙈
The fact I have an extension to even count tabs is a sign in itself that it went too far a long time ago already. I even had a Prometheus exporter for that at some point in order to be able to graph my tab count and motivate me to clean them up (guess what, it failed)
The fact I have an extension to even count tabs is a sign in itself that it went too far a long time ago already. I even had a Prometheus exporter for that at some point in order to be able to graph my tab count and motivate me to clean them up (guess what, it failed)
Interested to learn about what it (literally) costs to build a unicorn scale-up such as @payfiteng.bsky.social on top of (a lot of) third parties?
I'll be sharing our bills and analyzing them at @breizhcamp.org this afternoon at 16:00 in Amphi A, and will to my best to wrap the event nicely! :)
I'll be sharing our bills and analyzing them at @breizhcamp.org this afternoon at 16:00 in Amphi A, and will to my best to wrap the event nicely! :)
June 27, 2025 at 12:24 PM
Interested to learn about what it (literally) costs to build a unicorn scale-up such as @payfiteng.bsky.social on top of (a lot of) third parties?
I'll be sharing our bills and analyzing them at @breizhcamp.org this afternoon at 16:00 in Amphi A, and will to my best to wrap the event nicely! :)
I'll be sharing our bills and analyzing them at @breizhcamp.org this afternoon at 16:00 in Amphi A, and will to my best to wrap the event nicely! :)
Name a more iconic duo than @julientopcu.com & @tpierrain.bsky.social to talk about architecture patterns & modularity at @breizhcamp.org 🤩 Let's see what Hive looks like :)
Time to sit back & listen rather than taking notes - if you can't wait for the recording → bsky.app/profile/juli... I guess!
Time to sit back & listen rather than taking notes - if you can't wait for the recording → bsky.app/profile/juli... I guess!
June 27, 2025 at 11:59 AM
Name a more iconic duo than @julientopcu.com & @tpierrain.bsky.social to talk about architecture patterns & modularity at @breizhcamp.org 🤩 Let's see what Hive looks like :)
Time to sit back & listen rather than taking notes - if you can't wait for the recording → bsky.app/profile/juli... I guess!
Time to sit back & listen rather than taking notes - if you can't wait for the recording → bsky.app/profile/juli... I guess!
Last day of @breizhcamp.org opening with a talk on the wizardry of speedrunning Paper Mario!
It's always amazing how far they go to find glitches and exploit them; 5 years of work to find a way to do arbitrary code execution, and so many steps to then do it!
Glad we have @speedons.fr in France :D
It's always amazing how far they go to find glitches and exploit them; 5 years of work to find a way to do arbitrary code execution, and so many steps to then do it!
Glad we have @speedons.fr in France :D
June 27, 2025 at 8:13 AM
Last day of @breizhcamp.org opening with a talk on the wizardry of speedrunning Paper Mario!
It's always amazing how far they go to find glitches and exploit them; 5 years of work to find a way to do arbitrary code execution, and so many steps to then do it!
Glad we have @speedons.fr in France :D
It's always amazing how far they go to find glitches and exploit them; 5 years of work to find a way to do arbitrary code execution, and so many steps to then do it!
Glad we have @speedons.fr in France :D
Welp, that's a wrap, with an on-point closing word, and as usual with @rluta.bsky.social , that was an astonishingly great talk :) Recommend watching to anyone!
Plus, exploring legacy code with such bravery is definitely in itself in the theme (indiana Jones) of @breizhcamp.org this year :D
Plus, exploring legacy code with such bravery is definitely in itself in the theme (indiana Jones) of @breizhcamp.org this year :D
June 26, 2025 at 12:27 PM
Welp, that's a wrap, with an on-point closing word, and as usual with @rluta.bsky.social , that was an astonishingly great talk :) Recommend watching to anyone!
Plus, exploring legacy code with such bravery is definitely in itself in the theme (indiana Jones) of @breizhcamp.org this year :D
Plus, exploring legacy code with such bravery is definitely in itself in the theme (indiana Jones) of @breizhcamp.org this year :D
Glad to see "Working Effectively with legacy code" mentioned - it's actually one of the books we have on the shelves at @payfiteng.bsky.social :D
But it's now obsolete and doesn't work in many cases.
"Refactoring" by @martinfowler.com is great - and I actually have it on my own bookshelf!
But it's now obsolete and doesn't work in many cases.
"Refactoring" by @martinfowler.com is great - and I actually have it on my own bookshelf!
June 26, 2025 at 12:27 PM
Glad to see "Working Effectively with legacy code" mentioned - it's actually one of the books we have on the shelves at @payfiteng.bsky.social :D
But it's now obsolete and doesn't work in many cases.
"Refactoring" by @martinfowler.com is great - and I actually have it on my own bookshelf!
But it's now obsolete and doesn't work in many cases.
"Refactoring" by @martinfowler.com is great - and I actually have it on my own bookshelf!
The dependency map of IntelliJ helps identifying which parts of the codebase depends on which the most.
It even eases finding the parts that are not relied upon by anything, nor rely on anything, and therefore... can just be removed.
It even eases finding the parts that are not relied upon by anything, nor rely on anything, and therefore... can just be removed.
June 26, 2025 at 12:27 PM
The dependency map of IntelliJ helps identifying which parts of the codebase depends on which the most.
It even eases finding the parts that are not relied upon by anything, nor rely on anything, and therefore... can just be removed.
It even eases finding the parts that are not relied upon by anything, nor rely on anything, and therefore... can just be removed.
Analysis of version control history leads interesting bits:
- Software life over time
- What part of the system/code were changed the most
- What files the "core historical contributors" touched the most
It allows isolating the bits of the codebase that are most likely the most sound
- Software life over time
- What part of the system/code were changed the most
- What files the "core historical contributors" touched the most
It allows isolating the bits of the codebase that are most likely the most sound
June 26, 2025 at 12:27 PM
Analysis of version control history leads interesting bits:
- Software life over time
- What part of the system/code were changed the most
- What files the "core historical contributors" touched the most
It allows isolating the bits of the codebase that are most likely the most sound
- Software life over time
- What part of the system/code were changed the most
- What files the "core historical contributors" touched the most
It allows isolating the bits of the codebase that are most likely the most sound
We have software that handles wider range of cases with better performances than 15 years ago. We also have way better hardware. Some things that were impossible to handle "as-is" before and required layers to mitigate can now be handled "live".
June 26, 2025 at 12:27 PM
We have software that handles wider range of cases with better performances than 15 years ago. We also have way better hardware. Some things that were impossible to handle "as-is" before and required layers to mitigate can now be handled "live".
Only strong recommendation for this talk: know your migration path. Know that you can rollback if you have an issue. 80% of the work will be figuring out that migration path, with usual patterns (e.g. strangler pattern).
Having a "v2" that implies changes on client is usually a hell, avoid it.
Having a "v2" that implies changes on client is usually a hell, avoid it.
June 26, 2025 at 12:27 PM
Only strong recommendation for this talk: know your migration path. Know that you can rollback if you have an issue. 80% of the work will be figuring out that migration path, with usual patterns (e.g. strangler pattern).
Having a "v2" that implies changes on client is usually a hell, avoid it.
Having a "v2" that implies changes on client is usually a hell, avoid it.
Even if some things can seem complex and have been dreading for long (upgrading runtime/platform), they're good candidates to start with - same for config cleanup, build updates, etc.
And these do _not_ require to understand business at first! Purely technical, yet gains
Also, docs.openrewrite.org
And these do _not_ require to understand business at first! Purely technical, yet gains
Also, docs.openrewrite.org
June 26, 2025 at 12:27 PM
Even if some things can seem complex and have been dreading for long (upgrading runtime/platform), they're good candidates to start with - same for config cleanup, build updates, etc.
And these do _not_ require to understand business at first! Purely technical, yet gains
Also, docs.openrewrite.org
And these do _not_ require to understand business at first! Purely technical, yet gains
Also, docs.openrewrite.org
Reminder of the 3 axis to evaluate software:
- Functional (features, user doc)
- Operational (perf, security, resiliency, support doc)
- Developmental (tech debt, DORA metrics, dev doc)
- Functional (features, user doc)
- Operational (perf, security, resiliency, support doc)
- Developmental (tech debt, DORA metrics, dev doc)
June 26, 2025 at 12:27 PM
Reminder of the 3 axis to evaluate software:
- Functional (features, user doc)
- Operational (perf, security, resiliency, support doc)
- Developmental (tech debt, DORA metrics, dev doc)
- Functional (features, user doc)
- Operational (perf, security, resiliency, support doc)
- Developmental (tech debt, DORA metrics, dev doc)
I'm a simple man - I see a talk with @rluta.bsky.social speaking on the agenda of @breizhcamp.org, I go there :D
Let's find out some tips on how to evolve legacy software painlessly!
I frequently share his talk on performance (www.youtube.com/watch?v=nEye...) to people - hopefully this one too :)
Let's find out some tips on how to evolve legacy software painlessly!
I frequently share his talk on performance (www.youtube.com/watch?v=nEye...) to people - hopefully this one too :)
June 26, 2025 at 11:30 AM
I'm a simple man - I see a talk with @rluta.bsky.social speaking on the agenda of @breizhcamp.org, I go there :D
Let's find out some tips on how to evolve legacy software painlessly!
I frequently share his talk on performance (www.youtube.com/watch?v=nEye...) to people - hopefully this one too :)
Let's find out some tips on how to evolve legacy software painlessly!
I frequently share his talk on performance (www.youtube.com/watch?v=nEye...) to people - hopefully this one too :)
Especially loved the speakers (David Blanchet & Romain Blazeix) personal feedback on their experience with mechanical keyboards: how they got into it, what they built and why, what they found easy and hard, how much it costed to them, etc.
Really brings something more than "just" theory!
Really brings something more than "just" theory!
June 26, 2025 at 9:27 AM
Especially loved the speakers (David Blanchet & Romain Blazeix) personal feedback on their experience with mechanical keyboards: how they got into it, what they built and why, what they found easy and hard, how much it costed to them, etc.
Really brings something more than "just" theory!
Really brings something more than "just" theory!
Actuation mechanisms, physical layouts, keycaps profiles/materials/shape, switch types, supplementary hardware weirdnesses, joke keyboards, key matrixes, firmwares, kits, ... super complete, wholeheartedly recommend the recording to anyone looking to know more about mech keyboards! :)
June 26, 2025 at 9:27 AM
Actuation mechanisms, physical layouts, keycaps profiles/materials/shape, switch types, supplementary hardware weirdnesses, joke keyboards, key matrixes, firmwares, kits, ... super complete, wholeheartedly recommend the recording to anyone looking to know more about mech keyboards! :)
A talk about mechanical keyboard at @breizhcamp.org ? Of course count me in! Can't wait to see what they cover - as someone already neck-deep in the rabbit hole of mech keyboards, I even contemplated submitting such a talk a while back 😅
I wonder if the Mechanical Keyboards Paris meetup still exist
I wonder if the Mechanical Keyboards Paris meetup still exist
June 26, 2025 at 8:44 AM
A talk about mechanical keyboard at @breizhcamp.org ? Of course count me in! Can't wait to see what they cover - as someone already neck-deep in the rabbit hole of mech keyboards, I even contemplated submitting such a talk a while back 😅
I wonder if the Mechanical Keyboards Paris meetup still exist
I wonder if the Mechanical Keyboards Paris meetup still exist
2nd day of @breizhcamp.org opening with a keynote by @jbriault.fr about the now almost famous "Cloud des Restos du Coeurr" 💜 Even if by now I know most of the content (but it keeps getting updated!), I keep being amazed by the completeness of their work
Super cool choice for a keynote :)
Super cool choice for a keynote :)
June 26, 2025 at 8:39 AM
2nd day of @breizhcamp.org opening with a keynote by @jbriault.fr about the now almost famous "Cloud des Restos du Coeurr" 💜 Even if by now I know most of the content (but it keeps getting updated!), I keep being amazed by the completeness of their work
Super cool choice for a keynote :)
Super cool choice for a keynote :)
Oh yes, there's so many tools out there for whatever around CI/CD - this almost looks like the @cncf.bsky.social lanscape ! (landscape.cncf.io)
No wonder some people specialize in CI/CD pipelines design & implementation I guess.
Featuring my fat fingers that is in none of these landscapes though
No wonder some people specialize in CI/CD pipelines design & implementation I guess.
Featuring my fat fingers that is in none of these landscapes though
June 25, 2025 at 1:20 PM
Oh yes, there's so many tools out there for whatever around CI/CD - this almost looks like the @cncf.bsky.social lanscape ! (landscape.cncf.io)
No wonder some people specialize in CI/CD pipelines design & implementation I guess.
Featuring my fat fingers that is in none of these landscapes though
No wonder some people specialize in CI/CD pipelines design & implementation I guess.
Featuring my fat fingers that is in none of these landscapes though
Went through the "classic" (most common stages, tests pyramid, etc.) that I won't re-share here, but I'm happy to see a mention of the differences between continuous delivery and continuous deployment that is too frequently overlooked usually!
Also happy to see dynamic/review apps/envs mentioned!
Also happy to see dynamic/review apps/envs mentioned!
June 25, 2025 at 1:20 PM
Went through the "classic" (most common stages, tests pyramid, etc.) that I won't re-share here, but I'm happy to see a mention of the differences between continuous delivery and continuous deployment that is too frequently overlooked usually!
Also happy to see dynamic/review apps/envs mentioned!
Also happy to see dynamic/review apps/envs mentioned!
And now at @breizhcamp.org : Hafsa El Maizi from @shodo.io, about CI/CD pipelines concepts
I can already related with the "as a developer, I noticed that CI/CD pipelines are often obscure for devs" introduction — (sadly) heard/saw that so many times recently
I can already related with the "as a developer, I noticed that CI/CD pipelines are often obscure for devs" introduction — (sadly) heard/saw that so many times recently
June 25, 2025 at 1:20 PM
And now at @breizhcamp.org : Hafsa El Maizi from @shodo.io, about CI/CD pipelines concepts
I can already related with the "as a developer, I noticed that CI/CD pipelines are often obscure for devs" introduction — (sadly) heard/saw that so many times recently
I can already related with the "as a developer, I noticed that CI/CD pipelines are often obscure for devs" introduction — (sadly) heard/saw that so many times recently