I'm Buddhist but all I can think to say right now is… Godspeed, America.
May the country to which and the values for which my family immigrated 50 years ago endure.
Monkey code, monkey break, monkey debug, monkey iterate.
Computer engineer. Android developer.
Co-host of "Android Faithful"
Independent Staff Android Eng. Formerly Trello, Adobe.
| Website | https://randomlytyping.com/ |
| Podcast | https://www.androidfaithful.com/podcast |
I'm Buddhist but all I can think to say right now is… Godspeed, America.
May the country to which and the values for which my family immigrated 50 years ago endure.
Here's our @androidfaithful interview with Jonathan Petit-Frere, Senior Software Engineer at Netflix, joining me and @MishaalRahman to talk about Android Widgets, why they are so hard to build, and what we need to make more and better widgets for our users: https://youtu.be/3eQnL0n6xXc
Check out JP's Droidcon NYC talk here: https://www.droidcon.com/2024/10/17/building-modern-responsive-widgets-with-jetpack-glance/
@bentrengrove You have done more to save me from recompositions than anyone else. My YouTube downloads are FULL of your talks from the last several years about Compose performance, and they STAY in Downloads as a reference. I'm sure I've awkwardly said it before, but I think you're overdue for another THANK YOU.
Just this last weekend, I managed to work through some really funky stuff that I only worked through because of leads from the aforementioned talks.
Does anyone know who I can personally thank and HUG for the "Recomposition State" in Android Studio?
I know I've been complaining about needing it for years now, and I want to give proper credit to whoever just saved my sanity. I might have missed it before, but I noticed it in Ladybug Canary 6.
It helped me find a tricky "why is this recomposing" issue related to using a `data class` for a `ModifierNodeElement` with a function type property. OMG.
Thank you for making me smarter.
Thank you for just making me randomly shed a tear while I'm mindlessly scrolling YT.
But I mean, there is no better person for whom to do that. 💜 Hadi. We'll miss seeing you as much in our Kotlin things, but we'll be even more looking forward to the times we do.
Edit: BTW @hhariri is going to be leading the Open Source department and turning over the reigns of the Advocacy Team at Jetbrains to @maartenballiauw. The "I'm leaving" is I assume specific to Talking Kotlin.