A lot of the points in the talk could sound obvious or maybe were already implicitly learned by working with Compose code, but having the most important things all in one place and structured nicely was very engaging to watch. I've also learned a few things I didn't know.

2nd and 3rd parts of the story from 2021 and 2023:

- developer.squareup.com/blog/herding...
- developer.squareup.com/blog/stamped...

Mmmm
The statement that the AI E2E tests will be less flaky than the hand-written ones is a bit too optimistic.

Hand-written tests are easy to monitor, debug and fix. Who fixes Gemini, when it suddently stops finding the right image or button in an app, or is just down?

wow

Maybe I'm dead wrong then, because this phrase seemed unnecessarily overcomplicated to me, like LLM like to generate 🙈

What do you mean?
Sorry I don't understand

🫂

This strategy can be very useful when we want to measure performance during a high-load system state, when tasks queues are full and an additional thread switch (measuredFunction giving control to the original thread) could take too much time, making metrics from users unreliable.

In the snippet above:
- uptimeMillis is first called on the thread which will invoke measuredFunction
- after measuredFunction returns, the execution is still within the measuredFunction's thread
- so we measure the time it takes to switch to the thread of measuredFunction and for it to get executed

Personal opinion: although the Unconfined dispatcher could be tricky, it's quite useful when one wants to measure performance of suspending function in "real life", on user devices:

I bet this talk would be of a great usefulness for someone, who just received an objective to improve the Jetpack Compose performance of some code base. It gives several good ideas of what to look at and where to start.

I almost haven't worked with Jetpack Compose professionally yet so I learn about such nice changes a bit too late after they come out. It's nice seeing how Compose gets more and more mature with each year though.
But I still wish it used much less magic under the good.

Another #AndroidDev talk on Preview-Driven-Development. From Sergio Sastre Florez, who is unfortunately not on Bluesky yet.

www.youtube.com/watch?v=cDqd...

This is probably the best guide on PDD that I've seen. It's really good at explaining the first steps one could follow to try this approach.

now*

The company I worked at in 2023 one day started to apply a very similar approach to the modules structure.

I was in an entirely unrelated team so I didn't ask questions, but now I wonder if maybe this talk has influenced the transformation.