Cyril Mottier (@cyrilmottier) 's Twitter Profile
Cyril Mottier

@cyrilmottier

Leadership, Engineering & Product @amoamoamo. ex @zenly (@Snap), @CapitaineTrain. DMs are open.

ID: 82703569

linkhttps://cyrilmottier.com calendar_today15-10-2009 20:20:59

6,6K Tweet

19,19K Followers

405 Following

Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Most think engineering growth is about scaling systems. That’s the easy part. Scaling culture and knowledge sharing is by far the biggest challenge.

Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

When building a product, you sometimes need randomness that is repeatable (e.g. generating textures, shuffling lists). The solution is super simple: seed your random number generator with a fixed value.

When building a product, you sometimes need randomness that is repeatable (e.g. generating textures, shuffling lists).

The solution is super simple: seed your random number generator with a fixed value.
Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Bezier paths are pure magic ✨. This animation appears when your friends interact: smooth curves, vibrant gradient, particles dancing along the curve, sleek 3d effect. All made possible by the power of Bezier paths bringing UI to life.

Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Murphy’s Law is undefeated: your infrastructure will go down. But just because outages happen doesn’t mean your frontend should fall apart. 💥 Designing mesmerizing error states can ease user frustration … and buy engineers time to fix the issue.

Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Investigated a broken internal-only feature this morning. Eventually found out it was actually not in the binary anymore. That's one of the problem of extreme modularity, it is (too?) easy to add/remove a feature from an app. With great power comes great responsibility 🕷️

Investigated a broken internal-only feature this morning. Eventually found out it was actually not in the binary anymore.

That's one of the problem of extreme modularity, it is (too?) easy to add/remove a feature from an app.

With great power comes great responsibility 🕷️
Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

TIL about the 'super<Type>' expression in Kotlin. Reading a programming language grammar is always super insightful even though it's not useful everyday 😅. kotlinlang.org/docs/reference…

TIL about the 'super&lt;Type&gt;' expression in Kotlin. Reading a programming language grammar is always super insightful even though it's not useful everyday 😅.

kotlinlang.org/docs/reference…
Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Super excited today! I just completed the migration to a new cross-platform, type-safe, and modular deeplink framework. I’ve had this in mind for years but never implemented it. An interesting challenge was dealing with modularity and supporting multiple apps.

Super excited today! I just completed the migration to a new cross-platform, type-safe, and modular deeplink framework. I’ve had this in mind for years but never implemented it.
An interesting challenge was dealing with modularity and supporting multiple apps.
Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Is anybody working on function-based DI framework? Most (all?) frameworks are class-based and don't fit well with Compose (function-based). …and yes I know about compositionLocalOf. But it's not checked at compile-time and is generally just for singletons.

Claire Pluvinage (@pluclaire) 's Twitter Profile Photo

Too late to book your ticket to California? No worries, your front-row seat is waiting right here in Paris! 👩‍💻👨‍💻 If you’re an iOS developer, this is your moment to book your place, meet the team, share the experience, and get inspired. Seats are limited so secure your spot!

Too late to book your ticket to California?
No worries, your front-row seat is waiting right here in Paris!

👩‍💻👨‍💻 If you’re an iOS developer, this is your moment to book your place, meet the team, share the experience, and get inspired.

Seats are limited so secure your spot!
Cyril Mottier (@cyrilmottier) 's Twitter Profile Photo

Code consistency is the backbone of scalable tooling. As your codebase grows, inconsistency becomes technical debt that cripples automation, refactoring, and even AI-assisted workflows. Consistency enables tooling, and tooling enables scale. Ignore it at your peril.