Top 3 Clean Code Practices

Follow for more Android & Kotlin tips 🙌

[Yodigity]

My tip: Take note of how many times you say "I'll sort that part out later..." The more you say it, the lower the chance of actually sorting it out 😅

[otoS]

Tip: Be careful with making function names short, because with clean code principles function should have one responsibility. The function can be considered to be following this principle, if the function name covers the whole idea of function and function does not do something that can't be guessed from the name.

[mrjackson]

That's should be written on a sticker of a monitor of every developer!

[mesutemrecelenk]

Don't implement interface for callback if using Kotlin 😅

[Flutter_Senpai]

Comments are great but they should explain why something is happening and not what is happening because the code itself should be self explanatory! 👌👌

[erayagdogan]

Let a method do only one job. If your method do more than one job create new methods for these jobs and use them in the original method. Trust me, it will increase the readability A

[rummusLoL]

This is extremely basic advice and not at all interesting. How about sharing some interesting viewpoints that might help good programmers?

[vibovitold]

most of the time comments shouldn't be necessary at all. if the code is hard to understand, roll up your sleeves and rewrite the code instead of just slapping a comment on it.

[PostMeridianLyf]

Don't erase code when refactoring. Comment it out or make another copy of the feature to begin modifying.