move slow and repair things
@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 ยป
move slow and repair things
Wrapping up this @touraine.tech edition with a talk by @permacodeur.fr on Rust for business apps! ๐ฆ
Quite a lot of overlap with the talk I presented with รdouard Siha at the same conference 3 years ago haha, but attendees change, and having different styles is always welcome!
Weโre open-sourcing ecdysis: a Rust library for graceful service restarts. No dropped connections, no manual socket handoffsโjust seamless transitions when you update your code. https://cfl.re/4axycMU
Go go @nick-tune.me @maxsc.bsky.social - now talking about aligning on ubiquitous language and breakthrough at @touraine.tech about aligning on ubiquitous language and breakthrough!
Come & discover how PayFit is finally making sense of terms like employee, collaborator, person, individual or user
We're super lucky to have people like @maxsc.bsky.social , @nick-tune.me and Christina onboad in this journey!
Tackling such transversal challenges and making the whole organisation more efficient is no small task, and takes both lot of time, energy, and smart (& lovely) people like them ๐
Wrapping up with a tool we're exploring to ease communication around terminology, both for business and tech matters: contextive.tech
Of course, Eric Evans is always a great inspirations - with some parts that were discussed here today being mentioned in the model exploration whirlpool
Sneak peek at what may be incoming in the PayFit app for admins, that was largely made easier in its conception by the language breakthrough that allows thinking i nthe scope of Permissions: access profiles, defining permissions.
At least, with my potato-quality camera, we're not teasing too much!
At the end, roles at PayFit are something specific to the permissions domain - working agreements and roles are totally different things.
And making sure everything is well encapsulated makes it so: "Now it's way easier than before to discuss these notions"
Fun fact: with @touraine.tech streaming the event live (that's so cool!), we have fellow PayFiters like Christina (mentioned during the talk!) who are watching - and apparently love what they see and agree with what's presented live!
When @maxsc.bsky.social joined, some things from the Permissions & Identity team standpoint were already striking: some spaces in the app were tied to "roles", while others were not.
For many, a "role" was used to position someone in an organigram - not to grant permissions like in his context
The most striking remaining question after months of summer holidays background discussions on the RFC was: do we consider all kinds of persons a collaborator?
Note: At the end of discussions, always look for how everyone felt with the session - helps identifying remaining clarifications needed
Tip along the way: "Something that works for RFCs is to put all the business vocabulary you'll use in the RFC itself - to contextualize everything"
Workshops are fine, but then what? How do we take actions?
Start small and concrete with a small group on some concrete topics, then share more widely, ending up with company-wide RFC.
Laying out and sharing a summary of options to generate reactions and decisions.
What helped a lot at the beginning of the journey was our DDD open hours to discuss ideas, align, and discover together - for example, around how every domain and team used the "employee", "collaborator", "roles" etc. words in their own context and use cases
Essentially, they'll explain how we got out of the hell that was messy coupling between many different parts of our system - for example the "individual" and "collaborator" relationship
If you're not here at @touraine.tech and attending @nick-tune.me and @maxsc.bsky.social talk about aligning on ubiquitous language and breakthrough, make sure to catch the recording afterward!
Will share a few notes here - with an obvious bias and preexisting knowledge on the matter.
Missed my talk today at @touraine.tech about Diรกtaxis as a documentation framework to ease writing and reading documentation?
While waiting for the recording, here's the content (in ๐ซ๐ท) I shared: s.42l.fr/touraine-tec...
Thanks to attendees who sacrificed part of the lunch break to attend!
Second day of @touraine.tech 2026 starting off with a keynote on Cybersecurity and the evolution of attackers profiles.
For Yubo, the kind exploits and who uses them evolved a lot with AI, and have more social objectives than before.
"It's not a security breach, it's a feature !"
Last talk of the first day of this @touraine.tech 2026 edition before the keynote: the usual Laurent Grangeau, talking about memory protection history (both hardware and software).... with vibe-coded slides ๐
Getting old, I don't even have valgrind installed on my laptop anymore
And now I got a detailed idea of the gTLDs creation process - and their cost!
Who will bet on the .agi TLD ? ๐
Great summary on domain names & TLDs by Benoรฎt Masson & Thรฉo Bougรฉ at @touraine.tech !
Lots of quizzes, where we got quite a lot of answers right with @kobaye.bsky.social. TLDs always amaze me in their usages weirdnesses :D
And TIL that WHOIS has been replaced by RDAP ๐ฎ about.rdap.org
Missed our talk today at @touraine.tech about how we reduced @payfiteng.bsky.social AWS bill by 40% in 3 years, with more business and while staying on AWS?
While waiting for the recording, here's the content (in ๐ซ๐ท) I shared: s.42l.fr/touraine-tec...
See you tomorrow, I'll talk about Diรกtaxis!
Loved the mention of "_feeling_ of self-efficiency" - reminded me of some studies around the "_feeling_ of being more productive with AI for some developers despite the data in these studies (and their context) showing otherwise.
Also, don't focus on velocity, but on user impact (yay agility)
All the stats, even when knowing them, are quite telling, and some are really saddening and frightening at the same time.
Super surprised on the 11% of parents getting "pushed" to provide a mobile phone to their child, with the rest being "the parents themselves pushed it" (for safety/convenience)
Great talk from the awesome Estelle Landry and Emilie Goubin here at @touraine.tech 2026 about how to help children protecting themselves in the digital world they're growing in!
Super nice summary of the talk with a reference timeline from the hiring to the end of the trial period.
With a couple links to dig further on that matter:
- enboarder.com/blog/employe...
- www.strongdm.com/blog/employe...
Properly onboarding someone takes time, energy, and is a team investment
Fifth trap: lack of feedback (not giving enough, and not taking care of actually gathering the newjoiner's one)
โ Take the time to gather the feedback - both technical _and_ human/organisational. It's the opportunity to get some fresh take/view! "What would you change?"
Fourth trap: assigning tasks that are too complex ("the hired person has a lot of experience, they'll be fine!") and without any assistance early on
โ Do peer/mob programming in addition to mentoring! With a pre-refined onboarding backlog.
Taking time in the beginning allows to be faster later on.