https://writober.ewjoach.im/2026/10/03-Miniature/ #inktober #Writever #Writober

https://writober.ewjoach.im/2026/10/02-Relic/ #inktober #Writever #Writober

https://writober.ewjoach.im/2026/10/1-Apple/
#inktober #writober #writever

It's 2026 and I'm still not using match/case.

BTW: stepwise https://docs.pytest.org/en/stable/how-to/cache.html#stepwise <3 my pytest bestie. Pytestie.

The reason blogs have a hydration strategy is that 1/ there are a large set of issues people need to solve when creating websites, some of them common, some of them more specific, and some of them not easily solvable by just applying standard tech, and it would be quite hard to learn whole new stacks for each and every website, so people invent frameworks that are versatile enough to cover as many use-cases as possible, and by doing so, they bring their own constraints and solutions

And 2/ because devs need to practice on using some stacks so they can experiment and learn, so of course their own blogs end up being overengineered.

Yes of course. I'm a backend developer, and aside from the server-side websites I've worked on, the websites I've created for personal purposes are static. I know that :)

My point is neither that the current state of JS is great or that we need all of that to solve the problems worth solving,

but I don't think we get closer to the issue by saying frontend devs are "too clever", that they've lost touch with "clarity, usability, or commercial effectiveness" and all in all, by blaming it all on frontend dev who would have broken the web.

https://github.com/procrastinate-org/procrastinate
Procrastinate is a Python distributed a/sync task processing library, based on PostgreSQL 13+. Probably the project I've spent the most time on, even though I've almost never had the opportunity to use it myself. It's used in production around the world, including in universities, and medical settings.

https://github.com/py-cov-action/python-coverage-comment-action
A GitHub Action that posts coverage comments on pull requests, using the `coverage` tool. It also generates a coverage badge and a coverage report for the repository.

https://github.com/ewjoachim/toml-combine
A small utility to create multiple versions from a single TOML file, useful for configuration management.

https://github.com/ewjoachim/raincoat
I'm working on a complete revamp of Raincoat, a linter for copy-pasted code that tells you when the source of your copy has changed, so you can update your paste accordingly. Get in touch if you want to co-design the new version with me!

https://github.com/ewjoachim/powernap
"A small REST client that recharges your batteries", a.k.a a lightweight Python lib to make REST API clients that look like a proper Python client when it's just a fancy way to send HTTP requests.

https://github.com/ewjoachim/sync-pre-commit-with-uv
A pre-commit hook to sync your pre-commit configuration with the latest version of the `uv` package.

So, I guess I've lost the habit of talking about my open source work in social media. Here are a few toots on my projects that I've worked on in the last months. Maybe a couple of you will find something useful down the list :) Let's say it's "toot-my-own-horn" Sunday!

So, I just wanted to clearly state why I left fosstodon
1/ The admin said/endorsed something that, at least to me is too suspiciously close to "the real fascist are the antifa" for me to be comfortably staying there.

2/ There's been so many missteps in this story that some instances have started defederating fosstodon. This impacts at least a few accounts I was following.

3/ The "no politics" rule in the CoC was naive 10 years ago. It's dangerous today.

I don't want to be second-guessing every mod statement and hope they get better. I'm much better elsewere.

Honnestly, this is explained much better than I could here: https://social.treehouse.systems/@YKantRachelRead/114614842498176337