jorgecastillo.dev - Profile | ThreadSky | a Reddit-style client for Bluesky

If your job demands your nights, your weekends, and your peace of mind.. it’s not a job. It’s a lifestyle subscription you forgot to cancel 🤷

submitted 6 hours ago • 0 comments

The changed parameter in Compose is not a boolean. It’s a bitmask with 2 bits per parameter to encode whether it’s changed, stable, or unknown. This allows fine-grained recomposition decisions without extra runtime checks.

submitted 10 hours ago • 0 comments

- The power to build from nothing - Freedom to work from anywhere - A global community that shares and helps - Limitless creativity and problem solving - A path to lifelong learning What other industries give you this? We’re lucky. Happy weekend! 🌞

submitted 12 hours ago • 0 comments

Why everyone seems to believe in secret and repeatable formulas for success? That is literally not even a thing. Just a sales pitch from people to sell their courses and coaching programs. Success is built from the ground, it is always genuine and unique. And always happens after lots of failure.

submitted 12 hours ago • 0 comments

It here, about to land! 🇯🇵 Let me know if you want to/can help with promotion in Japan communities/reach 🙏

submitted 1 day ago • 1 comment

The most underrated skill in tech: Closing your laptop when your brain says “enough”. 🔥

submitted 1 day ago • 0 comments

You don’t need a new productivity system. You need to stop checking Slack at 11pm and calling it “ownership” or “accountability”. Time out of work and with your people is what really matters.

submitted 2 days ago • 0 comments

Knowing how Compose injects the Composer, wraps groups, and tracks remember scopes gives you full control over recomposition. It is the difference between hoping your code is efficient and knowing it is. That is the value of understanding internals.

submitted 3 days ago • 1 comment

Most Compose performance issues come from not understanding how recomposition actually works. Not tooling. Not the framework. Just the lack of mental model. Reply with the moment it finally clicked for you.

submitted 3 days ago • 2 comments

Android 16 released yesterday. Best feature: - No glass effect android-developers.googleblog.com/2025/06/andr... Android Developers Blog: Android 16 is here

submitted 3 days ago • 1 comment

You don’t need an emulator or a real device to test Compose UI. You can assert layout, semantics, and interactions, all in milliseconds. Fully headless, blazing fast, CI ready, no flakiness. Yet most teams still don’t do this. I wonder why.

submitted 4 days ago • 1 comment

“My Compose screen is janky” Proceeds to add 12 remembers, 3 LaunchedEffects, and a random derivedStateOf. Still janky. Whats your go-to for Compose performance?

submitted 4 days ago • 1 comment

📌 Jetpack Compose rewrites every Composable into a function that takes a hidden Composer parameter and a changed bitmask. This allows the runtime to skip re-execution of UI code when inputs haven’t changed. Smart UI diffing at the compiler level 🔥

submitted 4 days ago • 0 comments

It's alive ⚙️❤️ composeperformance.com

submitted 4 days ago • 0 comments

Some engineers write code. The rare ones write code and connect teams, unblock people, align efforts, and make everyone move faster. Those are your real 10x engineers.

submitted 5 days ago • 0 comments

Optimizing Compose performance is not about removing recompositions. It’s about scoping them. Recompose the 5% that matters. Not the whole screen.

submitted 5 days ago • 0 comments

I did ~10 years of startups and ~5 in big tech. Startups gave me speed, chaos, pivoting, adapting, ownership, impact. Big tech gave me scale, process, cut through bureaucracy, monitoring, perspective.

submitted 6 days ago • 0 comments

Using remember everywhere will not save you. If you don’t understand recomposition scopes and how the compiler tracks changes, remember becomes useless clutter. Compose performance starts with understanding how it works.

submitted 6 days ago • 0 comments

Gotcha.

submitted 6 days ago • 0 comments

🚨 The Effective Android community is now open for subscription. 🔒 Full access to our private Discord: 500+ advanced Android devs, all course alumni 🎯 Deep discussions on Android+Compose. Me part of them. 💸 Discounts on all courses/books Subscribe here 🔥 buy.stripe.com/aFa4gz5OY5Da...

submitted 6 days ago • 0 comments

RenderNode is Android’s low level display list builder. It records draw commands (like drawRect, drawText) into a GPU friendly buffer. The system can replay and composite these without calling your code again. Massive perf win. Yes, Compose uses it, esp. for GraphicsLayer.

submitted 6 days ago • 1 comment

📦 Ever wondered how the Compose compiler rewrites your Composables? A real example:

submitted 6 days ago • 0 comments

Once you understand how the Compose compiler rewrites your code, how the Composer tracks invalidations, and how recomposition works, you stop coding by trial and error. You start making deliberate performance decisions. That is why I wrote Compose Internals, and Compose Performance now.

submitted 7 days ago • 0 comments

I remember my first time using Compose. It looked clean. Declarative. Reactive. But under the surface? A huge amount of complexity hidden by a single annotation. Yet almost no official docs that explained how it really worked. This why I wanted to write about it.

submitted 7 days ago • 0 comments

Your adaptive layout works beautifully on a foldable. Shame is nobody owns one. Same goes for chromebooks and tablets. People just use phones. Massively.

submitted 7 days ago • 3 comments

So often devs are way too purist to be practical.

submitted 7 days ago • 0 comments

MaterialExpressiveTheme hits alpha. github.com/JetBrains/co...

submitted 7 days ago • 0 comments

Most users only ever use 2 or 3 features per app. Many times, only 1. Yet I’ve never found a company that prioritised identifying and removing features that aren’t used enough.

submitted 8 days ago • 1 comment

The Jetpack Compose and internals cohort course starts today 🔥 For the next 7 weeks, we will dive deep into the guts of Compose, learning to master it and to use it efficiently. This is the content we are learning together this week. You are still in time: composeinternals.com

submitted 12 days ago • 0 comments

We made it to 500 members in the Effective Android community Discord today 🎆👏👏

submitted 13 days ago • 0 comments

Android devs, pitch yourself. – 5 bold words – Link to app, repo, or profile 100k+ people got this on their timeline last time we did it. 🚀 This is how it starts 👀 Be seen or be silent!

submitted 14 days ago • 13 comments

Starting next Monday 🔥🚀 This is your last chance. Now or never! open.substack.com/pub/effectiv...

submitted 15 days ago • 0 comments

Talking to some really interesting potential co authors for the Jetpack Compose performance book. I want this book to be especially useful. The people I’m contacting are the most knowledgeable ones I know in this topic. Link to be noticed once it releases leanpub.com/composeperfo...

submitted 16 days ago • 0 comments

Best library for zoom interactions on images in Jetpack Compose is Telephoto, by @saket.me github.com/saket/teleph...

submitted 16 days ago • 1 comment

If you could whisper one Android dev secret to every junior starting today, what would it be? Quote tweet this. Let’s build the Android wisdom tree 🌱

submitted 17 days ago • 3 comments

Vector/path rendering (directly using drawing APIs or formats like SVG) is incredibly powerful. But don't forget that sometimes a simple bitmap is the easiest, cheapest, fastest, and overall best solution 😀

submitted 17 days ago • 1 comment

Only 1 week left. The new cohort of Jetpack Compose & Internals is about to begin. No fluff. Just deep insights, real-world knowledge, and everything you wish someone had taught you earlier. Seats are almost gone. Book now or miss out. Last call! 🗣️ book your seat here 👇 composeinternals.com

submitted 19 days ago • 0 comments

Told Cursor that I miss findViewById()

submitted 20 days ago • 1 comment

If you were rebuilding your Android app from scratch in 2025, what would you not use again? A library, a pattern, a tool, whatever. Let’s make this brutally honest.

submitted 20 days ago • 15 comments

A pattern is only useful until it gets in your way. Over the years I’ve seen way too many devs defending ideas only because they were written in a book. Be open minded.

submitted 20 days ago • 0 comments

Mocking network responses in Macrobenchmark tests 👇 That is ok and I recommend it if you are benchmarking UI performance, layout, recomposition, scroll smoothness, frame times etc In those scenarios loading times don’t provide relevant info, they’re actually noise and a source of flakiness.

submitted 21 days ago • 1 comment