Alexis "Horgix" Chotard

GitHub - conference-hall/conference-hall: Open SaaS platform to manage CFPs Open SaaS platform to manage CFPs. Contribute to conference-hall/conference-hall development by creating an account on GitHub.

Thank you @horgix.fr for sponsoring Conference Hall and Open Source projects. It helps us a lot!

github.com/conference-h...

Been using it as a speaker a lot, and wish I had it at hand when I still organized conference a few years ago so... it's my pleasure to do so 😊 We're pretty lucky in France to get so many great tech conference, and with such a handy tools combo that Conference Hall + OpenFeedback is!

Funny how we force engineers to write ADRs for every trade‑off, yet billion‑dollar strategic bets live in hallway whispers and fluffy slide decks.

What if we treated business decisions like architecture? Context, options, trade‑offs, metrics, all in a repo, version‑controlled and reviewed?

🎬 Les vidéos du #Breizhcamp2025 sont là !
Tous les trésors du code enfin dévoilés 💎
Pas besoin de fouet, juste d'un clic
www.breizhcamp.org/conference/p...
Ou directement :
youtube.com/playlist?lis...

An interesting undocumented API just hit my automation. Looks like AWS is planning a Vector DB for S3? Or some kind of storage Vector storage offering? Operations include:
- QueryVectors
- PutVectors
- PutVectorBucketPolicy
- ListVectors
- ListVectorBuckets

Introducing OpenCLI Patrik Svensson's blog

Introducing OpenCLI

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)

GitHub - tramhao/termusic: Music Player TUI written in Rust Music Player TUI written in Rust. Contribute to tramhao/termusic development by creating an account on GitHub.

C'est cool ouaip, mais le truc cool c'est surtout la spec derrière je trouve (specifications.freedesktop.org/mpris-spec/l...) !

Je m'en servais avant de passer sur github.com/tramhao/term... (qui d'ailleurs est compatible MPRIS lui-même) qui fait déjà tout ce que je veux dans mon terminal au final

Lies we tell ourselves to keep using Golang In the two years since I’ve posted I want off Mr Golang’s Wild Ride, it’s made the rounds time and time again, on Reddit, on Lobste.rs, on HackerNews, and elsewhere. And every time, it elicits the ...

Lies we tell ourselves to keep using #Golang

Arch Linux - News: linux-firmware >= 20250613.12fe085f-5 upgrade requires manual intervention 2025-06-21 - Jan Alexander Steffens

One more day of "damn I love Arch Linux". I get an error while updating approximately once every 2 years - and it happened today. First reflex: check archlinux.org - and here we go without surprise, it's documented on the frontpage with the fix 💙 (archlinux.org/news/linux-f...). 20sec resolution.

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! :)

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!

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

Missed my talk today at @breizhcamp.org about Diátaxis applied to platform documentation (theory + experience feedback from @payfiteng.bsky.social) ?

While waiting for the recording, here's the content (in 🇫🇷) I presented: s.42l.fr/breizhcamp20...

25min was short, so shoot questions here on Bsky 🙂

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

Easy to use, low overhead, open source Java APM Glowroot helps you get to the root of application performance issues.

We're in 2025, you got observability means & tools everywhere:

- Debuguers
- Profilers
- APM
- OpenTelemetry
- Glowroot (glowroot.org - didn't know about it!)
- ...

They usually lack on legacy software, but are a good place to start regaining control

Glad to see the "ops" patterns that can help manage the risk mentioned :D

- Canary deployments
- Feature flipping
- A/B testing
- Traffic mirroring

... help controlling deployments and reducing impact in case the legacy refactoring breaks something.

And vouching for multi-competence teams <3

Don't fear refactoring through exploration and risking breaking things if you _know_ you risk breaking them and are fully ready to rollback.

Actively inline-refactor things to reduce useless parameters while keeping things safe. Your IDE will do everything by itself.

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!

Generate the missing documentation.

Plantuml and MermaidJS are cool because they generate visuals from text, and it's easy to generate text based on existing code.

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.

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

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.

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

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)

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 :)

Interested to learn about Diátaxis (diataxis.fr) and how we applied it to our internal developer platform's doc (and more) at @payfiteng.bsky.social ?

I'll be presenting it this afternoon at @breizhcamp.org at 17:35 in Amphi E, and I'll keep you awake for the last talk of the day !

Arf, si j'avais vu plutôt j'aurais pu t'en ramener un à BreizhCamp, j'en ai en rab' :)

Si jamais tu ne le retrouves jamais et que tu en veux un, n'hésites pas à faire signe, je dois avoir ça quelque part !

GitHub - Nuclear-Squid/ergol: A Colemak-style keyboard layout for French-speaking typists and programmers. A Colemak-style keyboard layout for French-speaking typists and programmers. - Nuclear-Squid/ergol

Oh, and I definitely have to check github.com/Nuclear-Squi... out 👀