Accessibility isn't just about ramps and screen readers.

It's about creating environments where everyone, regardless of ability, can thrive.

Let's make accessibility a priority in everything we do.

To be honest, I am only here because it's a habit, and I like playing around with my website. It's fine to write about your life and other such interests. My favourite blogs to follow do exactly that, but it's absolutely understandable if you don't want to do that.

Every couple of years in software development, the meta changes. Libraries and frameworks are rotated in and out of popularity, languages evolve and best practices change. These are some of my personal beliefs1 on what the current meta is, and what parts are worth adopting.

Now is better than never.
Although never is often better than right now.

1. Use statically typed languages over dynamically typed languages
2. Use automatic formatting
3. Parse, don’t validate
4. Use union types
5. Parse, don't validate
6. Avoid abstracting too early
7. Be aware of monads and functors
8. Accept that generative AI is here to stay
9. Prefer integration tests over unit tests
10. Be kind during code reviews
11. Respect a candidate’s time
12. Pair or mob program frequently
13. Pick a git commit format and stick to it
14. Use Dependabot and friends for dependency maintenance
15. Write infrastructure-as-code
16. Use platforms that allow developers to focus on the code
17. Use queues as data sources

If regular traveling has taught me anything, it’s that you can never depend on circumstance. You can only depend on yourself. And if there’s one writing skill that’s overlooked, then it’s the ability to just write as and when you choose, regardless of where you are, the time of day, or how comfortable you feel (and I mean that in a physical and symbolic sense).

Doctorow states in his own words:
“I learned to write crammed into coach seats with my laptop keyboard practically vertical, my wrists bent back at an agonizing angle. Between flights, I’d write crouched on the floor under the water fountain between the toilets in the departure lounge, nailing the only outlet and plugging in my travel power strip to share with others. […] I have written so much in so many places that the desk and the comfy chair and the big monitor are largely aspirational for me — the kind of place I’d like to be writing in, but rarely the place where I end up writing.”

TL;DR? Write how and where you want to write. And if you can’t, write anyway.

How to fill the gap left by the GOAT css tricks?

Look, the dream goal is Piccalilli fills a hole that’s been left by Digital Ocean and their mis-handling of CSS-Tricks.

If I were ever to make an RSS service like Feedbin, I’d probably add a feature which would delay some items until a specific day of the week. Some posts I get feel more suitable for weekend reading.

Strange, isn't it, that the values of real people — the things most of us truly care about — are not reflected at ALL in the values of our hegemonic capitalist consumerist culture...

The real luxuries:

• a good night's sleep
• slow mornings
• freedom to choose
• time for fun and play
• listening to birds singing
• long walks
• a good book
• favorite home-cooked meal
• colorful sunsets
• ability to freely express yourself
• day naps
• a good conversation

What is the maintainable way to build things?

For CSS, how do you structure tokens?

1. Naming things: --umap-color-darkBlue?
2. Give a meaning to names: --color-primary: var(--umap-color-darkBlue);

Lorsqu’on envisage un commun sur ces 10 prochaines années, comment trouver une stratégie maintenable qui s’inscrira dans la durée avec enthousiasme ?

Le contraire de Tailwind :/

Every new user being shocked that DMs aren’t actually private is kinda scary because it means that everybody just assumes DMs on other platforms are private

because they aren’t. The only difference between fedi and other social media is that fedi admins don’t have a vested interest in making you think DMs are private

💯

If you implemented this, and then you deleted all but one of the call sites, would you be tempted to inline the abstraction? If yes, you shouldn’t do it.

I don't have this problem, iterating over patches, minor majors versions. When it follows SemVer then everything is good.

Réduire ses ambitions quitte à planifier les versions 3 et 4 par la même occasion est un moyen de faire baisser la pression de ses propres attentes. Ce n’est plus l’évènement mais un évènement parmi les suivants qui vient s’intégrer dans une dynamique plus globale.

Il y a une forme de violence à dire — de manière plus ou moins directe — à des personnes que les outils numériques qu’elles utilisent ne sont pas appropriés. D’autant plus en ne proposant pas d’alternative réellement utilisable :

• dans le contexte de littératie numérique de la personne,
• dans le contexte culturel du groupe de travail autour de la personne,
• dans les priorités actuelles du groupe pour lequel l’informatique reste un outil et/ou
• dans la situation de détresse en cours.

Si la ré-action est inappropriée, c’est peut-être que l’action initiale ne l’était pas non plus…

« ça marche sur ma machine »

Évidemment, c’est frustrant de recevoir cette réponse, parce que ça ne fournit aucune solution, mais ça ressemble aussi très fort à « je ne vois pas le problème, donc ce problème n’existe pas »

En généralisant aux utilisateurs,

ça marche pour suffisamment d’autres personnes, donc on ne va pas s’intéresser à votre situation particulière

Le validisme, ça parle aussi de comment des personnes sont systématiquement le 1% de personnes qui voient mal l’écran pendant une présentation
ou le 1% avec un fauteuil roulant dans la pièce etc.

Putting it another way, your work can only be as interesting as your problems.

The authors seems to use valid arguments. I don't know someone who uses Opera anymore.

Parsing increases the information in the type system. A list can be of type NonEmpty, i.e. there is at least one element.

Use a data structure that makes illegal states unrepresentable.
Push the burden of proof upward as far as possible, but no further.

and awesome guidelines to follow.

So parse "data" and return the closest type instead of only validate them.