If You Debug With println(), Watch This

preview_player
Показать описание
Follow for more Android & Kotlin tips 🙌
Рекомендации по теме
Комментарии
Автор

I don't debug, I let Crashlytics find the bug 😂

Kalex_sr
Автор

I spray pesticides on my machine to debug my app.

daruiraikage
Автор

Log.d, Log.e etc are what I use.. I have never used a println in an android codebase

afixithei.V
Автор

Where you find that shirt Philip, it look good

neronguyenvn
Автор

It's an escalation process and I pretty much know what it will take to fix a problem before I start. A couple of prntln statements usually does the trick. I created a helper class that I use on all my projects to facilitate that. But sometimes, debugger needs to be part of the process and then I will use it.

philipberthiaume
Автор

It's like asking a carpenter whether they prefer using a hammer or a hand saw. Both are indispensable tools in this line of work, and neither is a replacement for the other.

vibovitold
Автор

Debug points are not reliable in some specific scenarios like coroutines or callbacks, also can cause the android app to crash with ANR if you hold particular debug point waiting for long.

ishubhamsingh
Автор

Timber or debugger with standard, conditional and logging breakpoints.

StingerAJ
Автор

I use Log for most cases and a debugger in some case.

BalaKumaran-gj
Автор

Don't encourage the println.... They should feel bad. These fools will run that println dozens of times when they can try things out with expression or traveling the stacktrace to look at previous state. I believe you people to do the right thing.

biscuitsofdeath
Автор

Didn't know we can use debugger to debug or find the output of code computation at compile time.

abacaabaca
Автор

I usually avoid the debugger because it's simply to slow to be usable. I'm much faster by logging out stuff and run the app normally.

taar
Автор

i debug by constantly staring at my code and hoping it will give up the culprit on its own

pallabbanerjee
Автор

Sometimes I just got lazy typing logt then create a variable for TAG or just supply the two parameters of Log. With println() I could just type quickly🤣If I spot the bug then remove those logging.

simpleelegant
Автор

Hi Philip I’m wondering if you have any videos about socket programming while using the binder in android?

Isagiyochi
Автор

I publish it in production and let the debuggers (client) find the bug for you.

rixclock
Автор

I just found a tiny bug using printLn() 😂

stoyan_vuchev
Автор

Logging, crashlytics, print statements but no debugger most of the time

TechBuddy_
Автор

Println 1
...
Println 2
...
Println 3

Simple way to debug code

ahmadamirudin
Автор

I dont use Toast, println or Log i just guess what the bug might be 💀

brightugwu