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

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!

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)

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

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

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!