Geoffrey Métais

The journey from (not)REST to GraphQL at scale - The Deezer experience A six-year journey at Deezer: from a tangle of legacy APIs to a unified GraphQL Gateway. A story of cross-team collaboration, Node.js performance tuning, and a few well-deserved slow claps from DevOps. - Download as a PDF or view online for free

Wanna replay the Deezer talk in your head? Here are the slides: www.slideshare.net/slideshow/th...

Martin Bonnin opening the meetup yesterday with a quick recap of the GraphQLConf 2025.

Loic Doubinine presenting his talk "GraphQL chez Deezer : retour d’expérience et défis d’intégration".

Benjamin Rabier during his talk "GraphQL as the API layer for MCP".

Benjamin Coenen explaining how to unlock performance with response caching.

Last night's meetup at our HQ was all about #GraphQL!
Big thanks to @graphql.org and @mbonnin.net for bringing the party to us 🎂, to the speakers (@ztec.fr, Benjamin Rabier & Benjamin Coenen) for the knowledge sharing and the entertainment 🌟, and to all attendees for the questions and exchanges 🙌

In a highly modularized codebase, typing full Gradle task names can be tedious. Gradle supports task name abbreviation: just type the shortest unique prefix. If ambiguous, Gradle suggests candidates.

⚠️ Use locally for speed, but keep codebase references explicit for readability!

I'm excited to announce something I've been building, an open source atproto client heron.tunji.dev!

Its currently available in beta on Google Play for Android devices. Please DM @heron.tunji.dev if you'd like early access.

It will be released to all Android users in the next few weeks!

Do you think it's more efficient than Flutter or React Native?
(Considering the app scope is suitable for those frameworks)

It's a Thread.sleep() study. That explains all this Java boilerplate.

!! What happened to you? :)

Caupain : comment vous aussi, vous pouvez créer un outil open source Caupain est un outil CLI pour garder vos version catalogs à jour. Venez rencontrer l'équipe qui l'a créé !

‪📅 A few months ago, we introduced Caupain, a simple open-source tool to check for dependency updates in a @gradle.com project.
Come meet the team who created it at the next @bordeauxkt.techhub.social.ap.brid.gy meetup in our Bordeaux office on September 11th!

ℹ️ 🎟️ www.eventbrite.fr/e/billets-ca...

Poke @liutikas.net , typical Gradle brainfuck.
How would a junior dev be supposed to manage that?

Arch Components arrived in 2017 too.
They drastically changed the SDK paradigm regarding development, and greatly helped to shift toward reactive programming.

IMHO they changed Android dev as much as Kotlin+Compose.

Skills every software developer should ideally have:

✅ be a good communicator
✅ be a good project manager
✅ understand business aspect of what they're creating
✅ be humble

I'd argue that these are much more critical than being a so called "rockstar" developer!

#Cancer et #acétamipride, clarifions les choses ! ⤵️

Il est FAUX d'affirmer aujourd'hui, scientifiquement parlant, que cet insecticide est cancérogène pour l'homme (dans les conditions d'utilisation habituelles dans l'environnement) et a fortiori qu'il provoque des cancers.
1/5

Probably, I'm not even sure!

It would be more visible and more easily reachable on d.android.com directly IMHO.

Developer guides*, of course.

Like a mini blog post for every common use case/ feature.

Android Mobile App Developer Tools – Android Developers Discover the latest app development tools, platform updates, training, and documentation for developers across every Android device.

My first guess would be "developer guided", for various use cases.

I love dev guides for code in Android documentation, it always greatly helped me.

And, the Gradle doc is not really accessible.

For every use case, the answer is "I should write a blog post for xxx".
Let's do it on d.android.com!

Is next week OK?

I'm on holidays right now.

Totally agree on this 👍

From the androiddev community on Reddit: Gradle 9.0 released Explore this post and more from the androiddev community

Look at Gradle 9 reception on reddit:
www.reddit.com/r/androiddev...

Average devs already struggle to develop correct (regarding architecture and performance) code, imposing an additional time consuming build system maintenance is very detrimental imho.

Of course they add neat features but that's not my point.

They bring breaking changes too often, and too complex APIs also.

How many Android devs know what configuration cache is?
(I'm not even asking how many will handle it correctly).

Slow pace doesn't mean no peace at all.

Slower pace = less friction, and hopefully less unnecessary API changes

It doesn't match the amount of time wasted on clueless buildsystem migrations, by a magnitude.

Why? Slower pace means less Gradle upgrades and more effective work!

Bonne chance Florian 🤞

Provides*

I'm happy with Fortuneo.

BoursoBank is great also, but Fortuneo provided virtual debit cards for online payments.

En même temps, le logique de Bluesky c'est plutôt de bloquer les trolls.

Il n'y a pas que les pilotes concernés.

Forgot the 'NotNull' indeed!

OK I was expecting the compiler to be confused by nullability

There is one nullable String, and the second is not.
It would have made it a List<Any> right?