this is when you shouldn't use booleans
Published 1 year ago • 9.8K plays • Length 0:23Download video MP4
Download video MP3
Similar videos
-
10:06
if you think this is a best practice, you're wrong in 99% of the cases...
-
15:53
if you're making these 5 use case mistakes, you haven't understood clean architecture
-
4:12
why i stopped using popbackstack() to navigate back
-
0:15
when you feel down, watch this
-
21:50
when booleans are not enough... state machines?
-
13:43
textfields, buttons & showing snackbars - android jetpack compose - part 7
-
6:21
do you have to learn clean architecture as a beginner? - android development
-
0:26
don't use use cases if...
-
0:58
enum vs. sealed class... this is the difference
-
1:00
avoid this mistake with if statements in kotlin
-
10:19
don't do these fatal mistakes with a multi-module architecture
-
18:15
5 fatal coroutine mistakes nobody tells you about
-
1:00
don't do this jetpack compose mistake 😅
-
1:00
avoid this readability mistake in jetpack compose
-
0:36
don't use baseactivity
-
0:31
why do we use interfaces?
-
0:22
don't learn with documentations like this
-
9:31
if i was to start android again... this is how i would do it!
-
0:46
this is what the out keyword is all about in kotlin
-
0:59
don't use base urls like this in android
-
1:00
this unknown kotlin feature makes your code more readable
-
0:28
when are you industry-ready?