Coding Best Practices With Examples | Code Review Best Practices

[@codebasics]

Do you want to learn technology from me? Check codebasics.io/ for my affordable video courses.

[@darshanabhuyan5896]

This guy is literally taught me much more than my professors.. Thanks a lot

[@Dakshita-cd4yo]

1. Use the right data structure 2. Don’t use unnecessary variables 3. Write more compact code 4. Come up with a good variable names (avoid abbreviations) 5. Don’t over complicate your code 6. Don’t nest your code too much 7. Be consistent with your naming conventions (stick to either snake/camel case)

[@soupnoodles]

Excellent video, I rarely see videos covering the importance of best practices & efficiency, which is crucial for a slower programming language such as Python. 0:59 Regarding this, sets don't exactly implement the `append` method, instead, you could do a set comprehension like so: `unique_countries = {customer['country'] for customer in customers}` 6:11 This is true, Altho, the `even_squares` method would be better of being a generator object, since it is only being iterated over once per function call. It is more memory efficient & faster `even_squares = (i*i for i in input if i % 2 == 0)` Using tuple parenthesis creates a generator object Great video overall, the first time I'm seeing a video from this channel, makes me want to check out more :)

[@FurbnMax]

Awesome tutorial, will have my first code review during my application process in a few days and am currently preparing. Much apprecheated!

[@codebasics]

Glad it helped!

[@NeedforSpeedGamesforpc]

I loved the 1st one which is use of Sets! Its been so long i have been coding but always underestimated power of sets.

[@raghuvardhansaripalli9636]

Thanks Brother and it really helps me during the interviews. This video helps every developer and Sr. management as well. Now a days this is a common question in all the interviews from developer to Senior Engineering managers level. God bless you. !!!

[@codebasics]

Great to hear raghu!

[@jaleeluddin9223]

So glad I discovered this accidently! Really good stuff

[@workflop4117]

Really good advices! Plus they are explained in detail! Many thanks.

[@codebasics]

Glad it was helpful!

[@user-wr4yl7tx3w]

wow, great to see more videos like this.

[@terrabyte-techy]

Excellent job. Thanks for the upload, it really helps.

[@codebasics]

Glad it helped!

[@sumitbabel5415]

Very well discussed and really practical, hats off dear

[@codebasics]

Glad you enjoyed it

[@kitsurubami]

what about for i in range(100): return condition_1 and condition_2 and condition_3 and condition_4 ?

[@StyleTrick]

Great content, keeping code simple =)

[@codebasics]

Always!

[@jaleeluddin9223]

Good stuff..Do you have many other similar videos?

[@pratikpawar05]

Sir plz complete the data structure series as soon as possible. Because it is helping me a lot to learn data structure in better way. Also thank you for being such a nice teacher ❤️😍

[@codebasics]

Sure pratik. I am going to upload a tutorial on queue data structure in next few days. Stay tuned.

[@RiyaSharma-gm5om]

Great video...just what I was looking for. thanks for clubbing all this in a video.

[@codebasics]

👍☺️

[@tagorerahul]

Really good vedio on code review

[@joelbrighton2819]

"Write compact code" (1:10) This is questionable advice. We should write code that meets functional/non-functional requirements but is easy to read. Do you want to spend 2 minutes trying to understand 1 line of code or 15 seconds understanding 5 lines of code? (This is actually discussed later in the video). "phone_info is not used in multiple places" (2:55) Correct, but it **is** used when stepping through code (which is generally a good idea). You can't see what's in phone_info if you return it directly. For the sake of one temporary variable you make debugging easier without having to re-write the code. The other advice is great!

[@GameMakerRob]

This was pretty good info

[@nmana9759]

Very good explanation! Thank you!

[@codebasics]

Glad you enjoyed it!

[@mdjohir9996]

@@codebasicsyou

[@Kingkiyan24]

Awesome tutorial.. thank you so much it was very helpful

[@codebasics]

You're welcome!

[@davidobber6788]

Nice video, more or less this is written in the wonderful Clean Code (by Robert Martin). But sometimes I prefer to store the output of a function on a variable just for debugging purposes, or to store something on a temporary variable to avoid train wagons (i.e. multiple rows with getA().getB().get(C).setXXX(), I prefer to declare C c = getA().getB())

[@codebasics]

Got it, I also use the same technique to avoid train wagons.

[@user-wc7em8kf9d]

Thanks. Superb content!!!

[@codebasics]

My pleasure!

[@mahanirvaantantra]

I slightly disagree with the process_numbers function review. I would prefer list and dict compression, for they improve the performance of code. Please let me know if someone disagrees with me. Along with their explanation.

[@joelbrighton2819]

My view... use whatever approach meets the performance requirements of the application and is understandable and readable by other Developers (including yourself in 6 months)! When considering making a performance related change always ask whether the benefits are _really_ needed by the end users (or whether you just want to make the application a little bit faster for no tangible user benefit). 🙂

[@atulpatil2289]

Thank you sir... Sir, can you plz tell which resource or anything I can follow to improve my coding practices?....as I'm learning everything alone so don't have anyone to review my code.

[@alxx736]

Coding Best Practices vs Code Smell ? Which is the difference? Could you give me both definitions? Thanks

[@pabloestrada9114]

Gracias! Muy bueno!

[@MadForCs16]

very helpful. thank you.

[@codebasics]

Glad it was helpful!

[@sauravadhikari8842]

10:03 you can do nothing in java without class and object

[@akashbadgujar5825]

What he meant is you can keep multiple methods in the same class. Why always create new classes when not needed. Using SOLID without understanding can be harmful.

[@ashutoshpatra440]

Thank you sir.....

[@codebasics]

Most welcome

[@savansanghavi7465]

Now this was cool

[@codebasics]

I am happy this was helpful to you.

[@bloodylyons]

Compact code does not always mean it is more readable