helmet91

I'm looking for book recommendations in the topics mentioned in title.

I often find myself feeling down and not being able to accomplish anything, and the tendency has been increasing.

I cannot even work on my hobby projects, because I'm just staring at the screen and my brain is not functioning, which leads to launching a game or watching YouTube videos and waste time.

I cannot find the way out of this madness, and my last resort is to find some books that might help with my issue.

I don't wanna rely on search results on the internet, because I don't trust random compilations of "read these 10 books to be productive".

Well, this is optional, but in case the book you recommend indeed helped you, I'd be curious how permanent the impact was for you, if that makes sense. I know mostly it depends on the person; it's me who has to make the effort, not the book. But I'd be curious how easy it is for you to consistently maintain what you learned from the book.

Regarding the format, it has to be in epub. And I'd very much prefer DRM-free books, price doesn't matter. If the only good books are all DRM-enshittified, that sucks, but I'll consider that too if I have no other choice.

Thanks in advance if anyone can help with recommendations!

Scrum is an agile framework that, if applied properly, can boost the efficiency of teamwork. It is known to be versatile enough, so it could be applied in basically any sort of productive teamwork, even beyond IT (e.g. bakeries, government organizations, etc.)

However, I've never ever seen it being used anywhere else other than in software development, therefore I've always been curious if Scrum is actually being used outside of IT somewhere.

Hi everyone,

As I've been developing my Android app, I've quickly found myself in a situation, where all my @Composable functions are quite hectic, not really maintainable.

I am wondering, is there any guide for best practices regarding @Composable functions?

Thinking in Compose is a straightforward article, and it all makes sense - until I want to build something other than Hello World. Something more complex, I mean.

What I understand from the article is, that I should keep the logic out of these functions as much as possible, and pass only primitive types as parameters. Behavior should be kept in callback functions. This is very nice and clean, I like it, but then what should I do, when I have quite a lot of functions nested?

For example, on MainActivity I have a Scaffold, within that a NavHost with four different tabs, each with completely different content, some of them with a BottomSheet, which are also completely different for each tab (that has one), and some of the BottomSheets can call a Dialog, which again, has a form in it, and so on. So the hierarchy has quite a level of nesting. And if I understand the recommendation correctly from the article mentioned above, then I am supposed to keep the states and callback function definitions somewhere in MainActivity (or ViewModel), and pass everything through the entire hierarchy. Everything. The value of every single Text (those that cannot be hardcoded), all the list items to DropdownMenus, all the list items for Lists, literally everything. And then, according to the article, the renderer is smart enough to only recompose those elements that really changed.

To me this sounds tedious. I've also seen recommendations to just pass the ViewModel itself in order to reduce the number of parameters. But if I do that, then how would I make a @Preview out of it? Probably it's possible, but it wouldn't be convenient at all.

So what's a clean approach for designing a good @Composable function hierarchy?