DON’T Make These 5 Coding Mistakes…

Most of you are making at least 1 of these 5 dumb coding mistakes. Today in this video I am going to show you what they are, why you should fix them, and how you can fix them.

🎓 Premium Courses 🎓

🎓 Free Courses 🎓

⏳ Timestamps ⏳
00:00 | Introduction
00:10 | Mistake #1
02:57 | Mistake #2
03:38 | Mistake #3
05:57 | Mistake #4
08:11 | Mistake #5
09:04 | Mistake #6

🔗 Socials 🔗

🔗 Support 🔗

🔖 Tags 🔖
- Python debugging tutorial
- Python coding errors
- Common Python mistakes

Hashtags
#techwithtim
#coding
#pythonprogramming

[Chad.The.Flornadian]

I recommend using a linter like pylint and a formatter like black. They will force you to follow the official Python style guide and have consistent code.

[jerryjohnthomas]

Hi Tim, i just came to a video just to see if ur still making videos. Nice to see an old friend still kicking. Beard looks good on you btw. Rock on

[funkykong]

This was a great review of some ideas to help devs write more readable and maintainable code. I'd love to see more future videos like this. Thank you!

[sukhresswarun]

serverless, monoliths, kubernets, microservices, etc ... . looking forward to see video on these topics

[superbombyman]

I didn't see what's wrong with the codes when I paused the video until Tim pointed them out.😅
I guess I really need to practice more.

[simonhylander]

Will your course teach me about spacing?

[DucciVinci]

Really good video!
I way too often fall into mistake #3 because why would anyone ever want to change that value which is just for some inner mechanics anyway? Which is of course a terrible approach.

I often don't agree with #4 though. Five lines of code can be really long and at first somewhat difficult to read, but at least they are still only five lines. Clean object oriented code tends to be at least twice as long as it would have needed to be and I still get the many long function and variable names mixed up anyway. Clicking through 10 different files also doesn't help in understanding what is actually being accomplished here.

[daveruble]

Always engaging. Well done, sir!

I am dangerously close to possibly almost understanding this.


My failure; not yours.

All my best.

[chamsseddin]

make more videos from this type, it's really helpful

[JohnDoe-ckun]

got some more.
don't use abbreviations. they are hard to understand after some time. (e.g. vel for velocitiy)
spezial for python: if you want to change the type of a variable, give it a new name instead. this is hard to comprehend.
love your videos. they helped me a lot.

[tonnypedersen]

conventions is only there to make easier for others to read you code, so if you are the only one that going to read it, then you can just throw the conventions out the window if they don't fit you coding style.

[none-one]

please pause the video and try to find the best move as Mato Jelic said :D

[vaishakhgk]

Who created Go took mistake 4( unused import ) too seriously

[thewhiteoaktree]

The only mistake is watching this video

[jonbig]

Every time I watch one of these I have to go edit my code 😂

[malcolmanderson]

Calling these "mistakes" feels wrong. These are things that beginners do in their code. But if the code runs it's not a mistake.
Now as a tool to evaluate code quality this video is gold.