@neronguyenvn2
tip 3 is legendary
@Rainatorii
I've only been coding for a month LOl every single day I listen to a lot of videos while they're shorts or not talking about coding and tips for new coders and blah blah blah but these are actually legit especially number 3 I really do have to agree with that because I'm doing a python course on Kodi and we're being taught your comment is what you're doing not why you're doing it you know right now I can look back on comments that I've done in small beginner projects and it's like I'm doing this but what I should have put their was maybe because I am such a beginner like it has to be 5 not 5.0 which yes it's just a small time things now but I know that soon it won't be LOL
@Indently
Test case names have entered the chat
@otoS97
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.
@kishanpmevada
Tip 3 💥💥
@mrjackson9137
That's should be written on a sticker of a monitor of every developer!
@mesutemrecelenk5447
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! 👌👌
@erayagdogan3389
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 LOOOOOOOT.
@rummusLoL
This is extremely basic advice and not at all interesting. How about sharing some interesting viewpoints that might help good programmers?
@PostMeridianLyf
Don't erase code when refactoring. Comment it out or make another copy of the feature to begin modifying.
@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.
@Yodigity