Tim, I just wanted to thank you! Your videos help me a lot, I increased a lot my programing skills watching your videos! You present everything in a clear and logical way, keep it going!
3:29 avoiding bugs 5:15 restructuring & designing code frequently 5:53 come up with a plan 9:59 don't read documentation or trying something new 11:37 is the project is possible to do? don't jump into masive project, plan and understand the the basics/small part of the project
"Younger programmers will write crazy convoluted code or methods to show what they know." Yep, that's it. I'm certainly not doing it because I have no idea what I'm doing 😏
@@clementsiow176 Hi, Just wanted to ask a random question among other programmers. When starting off wold you recommend focusing on one language at a time?or multiple modern language use today?
@@jaydenrussell7491 One language. It's almost one year since I've started coding, and every time I try to learn a new language, I just... can't understand it. So I'd say stick with one language, and then in the future when you get good with it, move on to others.
@@jaydenrussell7491 Master one language well. Now you may need to dabble in more than one language if you're working on a project. But still, if you want progress as a developer, and not spin your wheels endlessly, you need to know at least one language really well.
You should have mentioned keyboard shortcuts. You can save 100s of hours by not scrolling around a page. Also if you get good at keyboard shortcuts it forces you to use good naming conventions so you can quickly jump to that section by using the keywords. Jump to pages , jump to functions , multi line edit, copy paste history, chrome keyboard short cuts jump between mobile and desktop view jump to network tab jump to address bar. I have short cuts to open every program I use regularly, browser, calculator, python shell, note taking ect. I also enjoy reading documentation because when I'm finding something I have a note pad out and write a basic how to use the program find everything I might find useful later. Pop it on my home with keywords as the title then I can quickly search for it on my file system. How to deploy on gcloud for example. Using chrome from the command line. I have 100s of these documents. So when I have the same problem again I can find the answer faster. You will never memories everything but your memory can just be a pointer to where the info is stored . Much more efficient. I also write and store util functions
Yes I do that too but in google docs! Each topic is connected to a table of contents that you can click and it’ll scroll down for you. really helps when I get an obscure git error then I just save it to the doc and I don’t have to spend time searching next time
I was into the social science field doing social work but I had a change of heart and now I’m a first semester sophomore studying cybersecurity. I recently came across your videos and it inspired me even more to learn more especially python🔥🔥
One big slowdown I've personally experienced and seen many others experienced as well is getting to code too early before truly understanding the requirements and the domain. Eventually coding will be second nature, but solving problems will always be what pays the bills, yet people sometimes focus more on the code than the problem.
Coding is not only coding but it is also a lot of thinking, reading and ensuring that you did not fail unit / integration testing somwhere where you did not expect. Pure coding is a minority of work.
Here are my tips 1. Take baby steps: make one or a small change, then build it and run. 2. Make a note of the bug and all possibilities of fixing it. 3. Add logger statements for all possibilities added in step2. 4.Repeat steps 1 to 3 till the issue is resolved
Many greetings from germany! Your UA-cam channel is great. Didactically very well structured and well explained (without too much ballast). I learn a lot from you and it is always fun.
Great Video! I destroyed the like button! The biggest Takeaway for me: Design and think about your project before you start implementing. Thanks for your videos Tim, they are amazing!
#5, yes, even after programmong for a long time, if I am getting into something new to me, like passing data into Cuda, using pybind in C++, or getting web socket servers working in C++
I literally almost cried for joy to hear the tremendous advice in this video!!! It is almost a polar opposite to so much of the hideously destructive accepted "wisdom" infesting the programming profession in the 21st Century due to a seemingly endless parade of wildly overrated "gurus.". It is such a pleasure to finally see someone understand, to see someone get at the essence of software quality! Maybe there is finally hope! Maybe there is a way out of the current dispiriting and depressing Dark Age of Software. Thank you! You just earned yourself a new subscriber.
I think you Tim forgot about one important point to increase the personal productivity. One should subscribe your channel and watch your outstanding videos and series! Thanks!
good tip for debugging is to use breakpoints at key sections of the code and inspect the variable values. Or alternatively just add some print statements and let the program run and try to figure out from the print statements (they are really debug logs) what the problem is. In real job I would assume that there would be debug logging in similar way, and in development process you would also practice writing the testcases and run the tests obviously
well I was short in time, one morning I started my work at 6:00am and finished it at 21:00pm. at the end I was like holly crap my eyes hurts like heck. but my job was done without a major bug. that was my craziest day.
Uncle Bob says: "The only way to go fast, is to go well". Invest your time in learning Test Driven Development and setting up a decent continuous integration pipeline. Only when you've mastered that dive into how to use the debugger.
1) start early 2 or 3 hours before your colleagues get there! You’ll get a ton done. 2) Don’t go to the office, it’s a soul sucking, meeting and coffee drinking inefficient environment. 3) Do as much yourself as possible so you don’t need to wait for others. 4) Avoid company professed they are there to slow things down. 5) Avoid meetings!!!
Well, coding in Python is easy. I would like to see you coding a parallel scan algorithm for multi-core setup with SSE vector instructions and MOVNTQ loads.
@@brutalbutler ahahhahaha! I would need like 1 month to explain to a python programmer why speed is important. But you can google phrases like "hpc", "parallel programming" , "gpu clustering" and get a clue. But the usual document all the python, javascript , perl and php developers read and get excited is this one: people.freebsd.org/~lstewart/articles/cpumemory.pdf (dated 13 years ago btw) And then they feel like "a door to a new universe has opened" I can't explain you in a youtube comment, but basically it is: the World has many dimensions and web development is only a tiny fraction of it
My top 3 tips: 1. High Salary 2. You should literally know what your doing 3. Dont bother with your workmate who ask you to fix every error he encounters
Think before you code...oh yes! I have so many, many, many times just start coding some crap and then many hours later, even 10 hours later...I discover that the solution is complex because it was not fully thought through, and does not work well enough and then I start to rethink...and you know what? The rethinked solution would have save me like 5 hours at least! Iam so glad that iam not alone and iam still doing that!!! Shame on me... Time to change. He talks about design issues, its actually many great methods out there that could help a lot. I mean people are always thinking about how they can make their software better so why not learn from them? I want to piint that out that UML is just one of many methods to make software diagrams. There are plenty of methods out there. I can code for three hours straight and I dont even know that these three hours are done until I look at the clock. Yes, documentation is for people to look up in not to memorize, programming is about solving problems, not to memorize syntax.
Could you possibly provide tips on typing faster/efficient. I need help in this category. I see programmers type lightening fast and not sure how they're changing the code so fast! ... thanks
Just get to practicing typing using 10fastfingers, keybr or typreracer. I'd suggest start with 10fastfingers. Treat it as a fun activity, because you're primarily training your muscle memory. Give it time, and it'll definitely go up. Oh and also, have a fun keyboard to type with! I dont use mechnical keyboards because my macbook pro 2021 keyboard has really tactile keys already.
When you want to build your software in a structured way and find and fix bugs, do test driven development. Do not waste your time manually testing your code all the time. I even learn new languages by writing tests.
One of the problems with programmers is that they overengineer the code so bad and simply screw the working code. A good programming that works for me all the time is firstly know what you wanna do, secondly make a ui research about similar programs or make one of yours or maybe you have a designer that designs the ui for you, second step make a structure on a piece of paper of all of the design. For example the comment bar is a column with a sizedbox a row and a sizedbox, the row contains a thumbnail image, a textbox, a submit button which are all in a container for easy layout(currently using flutter, for other languages know your language). Make all the skeleton of the program that you are going to write, then make yourself a hierarchy with folders and files, and actually name your stuff, for example put your functons or methods inside a folder named functions, put your pages on a folder called pages, put the items that is the key of that page into a folder called items etc. Seperate the code to multiple files so that you wouldn't need to read 1000 lines for a simple function you are trying to find, never make a single file for especially a huge page. Nextly, don't code with non-understandable variable names and in an unnecessarily complex way, this will reduce efficiency and increase complexity of the software. If you do all of these and still code slow, then you should know what to google or how to google and stackoverflow becomes a helping hand out there waiting for you
Here's a simple function for bug fixes: def isBug(p, q, r, n=30): """ Checks pre condition p and post condition r for closure q """ bugCount = 0 for x in range(0,n): if not p(): print("Precondition failed") bugCount++ continue q() if not r(): print("Post condition failed") bugCount++ if not bugCount: print('Congrats! {P}Q{R} is successful. More test runs can be issued to verify the issue.) else: print('Sadly, the given {P}Q{R} has {0}/{1} failures'.format(bugCount, n))
long hours focus is bad for health. People before 40 may not notice the negative side effect becuase of body's fast regeneration. But once they health drop to certain level, they start to experience all kind of disese. There has to be a way to do coding in multiple short periods.
I would never recommend coding without a break for long hours. Not only is this bad for your health overall (think: eyes and spine) but it will also slow you down, not to mention you'll be making silly mistakes you'd never make if you were fresh and rested. Many a time have I had a situation where I came to work after long hours of coding only to find out that I had made really *silly* mistakes the day before. In a word: never do that if you want to enjoy your life and work until a very old age and still be able to do what you did when you were young. If you neglect your body, one day it'll neglect you. Do you want this? I don't think so. A wise man knows one has to have everything in moderation. If you go to extremes and force your body into abnormalities, you'll be sorry sooner rather than later. So, the advice to code for 12-18 hours is not only ridiculous but also a very dangerous one. One last thing... Bear in mind that the latest research shows one can effectively focus for about 45 minutes. So, do yourself a favour and take frequent breaks when coding. When you don't code, do something completely unrelated to coding. You'll thank me later.
I agree with everything you’ve said. I apologize if I made it sound as though I endorse coding for 12-18 hours... I DO NOT. I am simply trying to illustrate that focus is important and the ability to focus for long periods of time in my experience increases efficiency. Of course you need to take breaks and of course your body is #1 priority. I am simply trying to say that most people I know can’t focus for even 20 minutes and that is not ideal when working on complex problems. Anyways I apologize to anyone that’s taken the video the wrong way, I’ll make sure to be more articulate in the future.
@@TechWithTim No worries, mate :) No need to apologize, either. Later in the vid you are kind of correcting the view. But you know... after all, people will do what they want anyway :) It's a pity, though, that very often bad habits tell on you later in your life, not right away. Many of us have to learn the proper way the hard way. By the way, the tip at the beginning about "kite" was a very good one. Every day something new. Thanks.
Tim, do u recomend a desktop over laptop for coding ? I’m using a 15’ laptop and it feels so cramped everything is annoying. Do u think i should get a desktop ?
Yes I personally feel much more efficient on a desktop. However if you’re coding on the go a lot then obviously laptop will be a much better option. I personally have two laptops and a desktop. I’ll always use my desktop when it’s available because of the massive screen size (27 and 24 inch monitors) also I really like mechanical keyboards
Tech With Tim i’m just borrowing the laptop from my sister i swear its really annoying she block me from doing anything that make changes to the system and i’m also limited by time too! I can only use it for a period of time and the laptop will kick me out when times out. So im thinking of getting a pc soon, i have been thinking a lot ! First i was thinking between using laptop + external monitor and a desktop but i find laptops with high specs are way too expensive and cheap gaming laptops are ugly and low battery. So i guess im gonna go with desktop ! Btw i love mechanical keyboards too, which switch are you using ? P/s : you just motivate me back with coding :D i just gave up for few weeks because of too much stress from family and schools.... thanks alot
12 hours 😅 Yes, you can do that and then you will rest two days doesn't looks good for me in a long term view, after years I realize that's just not possible to work hard every day, the result is just burnout, procrastination, and demotivation Guys take your time for rest really if you want to work more than 3-4 years in IT
Download kite and speed up your coding! kite.com/download/?
please change your background . make video in different place
@@erfanghofrani3342 that will be difficult to do! I'm filming in my room which is pretty much the only place I can...
@@TechWithTim Yeah i understand . it not bad i just said if you can . you are good enough with any background :)
@@TechWithTim make video about debuggers please
Tim, I just wanted to thank you! Your videos help me a lot, I increased a lot my programing skills watching your videos! You present everything in a clear and logical way, keep it going!
3:29 avoiding bugs
5:15 restructuring & designing code frequently
5:53 come up with a plan
9:59 don't read documentation or trying something new
11:37 is the project is possible to do? don't jump into masive project, plan and understand the the basics/small part of the project
"Younger programmers will write crazy convoluted code or methods to show what they know."
Yep, that's it. I'm certainly not doing it because I have no idea what I'm doing 😏
You’ll get there dw
wait we are supposed to know what we are doing?
I would love a debugger tutorial! I was never taught to use one and feel like that would save me a lot of time debugging. Love your videos!
I love programming but after years i still have no idea what debugging is.
@@SilverVolo debugging is fixing bugs
@@clementsiow176 Hi, Just wanted to ask a random question among other programmers. When starting off wold you recommend focusing on one language at a time?or multiple modern language use today?
@@jaydenrussell7491 One language. It's almost one year since I've started coding, and every time I try to learn a new language, I just... can't understand it. So I'd say stick with one language, and then in the future when you get good with it, move on to others.
@@jaydenrussell7491 Master one language well. Now you may need to dabble in more than one language if you're working on a project. But still, if you want progress as a developer, and not spin your wheels endlessly, you need to know at least one language really well.
You should have mentioned keyboard shortcuts. You can save 100s of hours by not scrolling around a page. Also if you get good at keyboard shortcuts it forces you to use good naming conventions so you can quickly jump to that section by using the keywords. Jump to pages , jump to functions , multi line edit, copy paste history, chrome keyboard short cuts jump between mobile and desktop view jump to network tab jump to address bar. I have short cuts to open every program I use regularly, browser, calculator, python shell, note taking ect. I also enjoy reading documentation because when I'm finding something I have a note pad out and write a basic how to use the program find everything I might find useful later. Pop it on my home with keywords as the title then I can quickly search for it on my file system. How to deploy on gcloud for example. Using chrome from the command line. I have 100s of these documents. So when I have the same problem again I can find the answer faster. You will never memories everything but your memory can just be a pointer to where the info is stored . Much more efficient. I also write and store util functions
Damn I need to start doing that!
How will I learn that,plz explain
Yes I do that too but in google docs! Each topic is connected to a table of contents that you can click and it’ll scroll down for you. really helps when I get an obscure git error then I just save it to the doc and I don’t have to spend time searching next time
you just described the zettelkasten 2nd brain method
@@tigana google the zettelkasten 2nd brain method
I was into the social science field doing social work but I had a change of heart and now I’m a first semester sophomore studying cybersecurity. I recently came across your videos and it inspired me even more to learn more especially python🔥🔥
If you can spend 12 hours straight programming, it means that you like programming
Madman
One big slowdown I've personally experienced and seen many others experienced as well is getting to code too early before truly understanding the requirements and the domain. Eventually coding will be second nature, but solving problems will always be what pays the bills, yet people sometimes focus more on the code than the problem.
Also OOP overuse. It obfuscates the code flow, which amplifies all the problems mentioned in this video
Coding is not only coding but it is also a lot of thinking, reading and ensuring that you did not fail unit / integration testing somwhere where you did not expect.
Pure coding is a minority of work.
Here are my tips
1. Take baby steps: make one or a small change, then build it and run.
2. Make a note of the bug and all possibilities of fixing it.
3. Add logger statements for all possibilities added in step2.
4.Repeat steps 1 to 3 till the issue is resolved
pls tell us about freelancing on python, learning at the same time earning ..pls make a video on this topic, Thanks!!
AAkil Ahmed There has been an episode about just that a few weeks back on the “Talk Python to me”-Podcast. Was a good one!
@@johanneszwilling Thanks! i would love to go for it 🙂
I've noticed that setting up my project skeleton (or design) and then writing my test cases makes me go alot faster when i actually start.
Your videos are always useful thanks !!!!!!
Thank you Tim for your videos, hope to see more content and keep up the good work
Many greetings from germany! Your UA-cam channel is great. Didactically very well structured and well explained (without too much ballast). I learn a lot from you and it is always fun.
I'm not sure I agree with staying in front of the computer for hours and hours without taking a break but otherwise greats tips from Tim.
Great Video! I destroyed the like button! The biggest Takeaway for me: Design and think about your project before you start implementing. Thanks for your videos Tim, they are amazing!
#5, yes, even after programmong for a long time, if I am getting into something new to me, like passing data into Cuda, using pybind in C++, or getting web socket servers working in C++
I literally almost cried for joy to hear the tremendous advice in this video!!! It is almost a polar opposite to so much of the hideously destructive accepted "wisdom" infesting the programming profession in the 21st Century due to a seemingly endless parade of wildly overrated "gurus.". It is such a pleasure to finally see someone understand, to see someone get at the essence of software quality! Maybe there is finally hope! Maybe there is a way out of the current dispiriting and depressing Dark Age of Software. Thank you! You just earned yourself a new subscriber.
Really great advice bro you're almost covered all the flaws of a newbie programmer
I think you Tim forgot about one important point to increase the personal productivity. One should subscribe your channel and watch your outstanding videos and series! Thanks!
That is a very important point, didn’t mention it because it should be common knowledge;)
Funny
Also, I would add "Don't apply a number of changes at a time" to avoid bugs
good tip for debugging is to use breakpoints at key sections of the code and inspect the variable values. Or alternatively just add some print statements and let the program run and try to figure out from the print statements (they are really debug logs) what the problem is. In real job I would assume that there would be debug logging in similar way, and in development process you would also practice writing the testcases and run the tests obviously
Everything is spot on in this video. Excellent work Tim.
Keep it up.
👍 thanks !
well I was short in time, one morning I started my work at 6:00am and finished it at 21:00pm. at the end I was like holly crap my eyes hurts like heck. but my job was done without a major bug. that was my craziest day.
In fact i cant stop watching and liking ur awsome tutorials and tips....thank you very much bud✌
Tim this video was extremely helpful! I'm a beginner programmer and this helps me a lot in how to work and prepper to actually coding, thanx!
The real term to been 'wired in' is called the 'flow state'. I recommend to UA-cam it if you're not aware of it.
Thanks! I was not aware of I but it’s definition is exactly what I was trying to describe
@@TechWithTim Glad I could help :)
Man, this is literally what slow me down 99% of the times
vim vim vim
Great general points for efficient engineering mate thanks
I hited like 👍and than when the video finished I tried to hit like again but no I can't I realy enjoyed with your videos TIM😘😘😘
HOLY! You said people work at 50% effectivity ALL THE TIME?!?! You need to get me in touch with those people I want to hire them all.
Uncle Bob says: "The only way to go fast, is to go well". Invest your time in learning Test Driven Development and setting up a decent continuous integration pipeline. Only when you've mastered that dive into how to use the debugger.
1) start early 2 or 3 hours before your colleagues get there! You’ll get a ton done.
2) Don’t go to the office, it’s a soul sucking, meeting and coffee drinking inefficient environment.
3) Do as much yourself as possible so you don’t need to wait for others.
4) Avoid company professed they are there to slow things down.
5) Avoid meetings!!!
Starting to use Kite, so far so good!
Glad to hear!!
Well, coding in Python is easy. I would like to see you coding a parallel scan algorithm for multi-core setup with SSE vector instructions and MOVNTQ loads.
Absolute Zero what would the point in tht be? sound like a bitter boomer
@@brutalbutler ahahhahaha! I would need like 1 month to explain to a python programmer why speed is important. But you can google phrases like "hpc", "parallel programming" , "gpu clustering" and get a clue. But the usual document all the python, javascript , perl and php developers read and get excited is this one: people.freebsd.org/~lstewart/articles/cpumemory.pdf
(dated 13 years ago btw)
And then they feel like "a door to a new universe has opened"
I can't explain you in a youtube comment, but basically it is: the World has many dimensions and web development is only a tiny fraction of it
What are you trying to prove?
@@absolute___zero what was the point of these comments?
None of this is new to me, but I suddenly feel like I know what I should be doing now... So thanks!
My top 3 tips:
1. High Salary
2. You should literally know what your doing
3. Dont bother with your workmate who ask you to fix every error he encounters
really important suggestions .I'm watching your videos carefully .Thank you Tim
somewhat obvious but still good stuff
also
planning + testing (with the inversion of control in mind)
is vital
Hi, thank you for this video. I would appreciate knowing your position about unit testing the code.
Think before you code...oh yes! I have so many, many, many times just start coding some crap and then many hours later, even 10 hours later...I discover that the solution is complex because it was not fully thought through, and does not work well enough and then I start to rethink...and you know what? The rethinked solution would have save me like 5 hours at least! Iam so glad that iam not alone and iam still doing that!!! Shame on me...
Time to change.
He talks about design issues, its actually many great methods out there that could help a lot. I mean people are always thinking about how they can make their software better so why not learn from them?
I want to piint that out that UML is just one of many methods to make software diagrams. There are plenty of methods out there.
I can code for three hours straight and I dont even know that these three hours are done until I look at the clock.
Yes, documentation is for people to look up in not to memorize, programming is about solving problems, not to memorize syntax.
You are awesome Tim!! Thanks for all the content! Brasilian fan.
You are awesome too! Thanks for watching
Great points
Thanks man ✌🙏
Could you possibly provide tips on typing faster/efficient. I need help in this category. I see programmers type lightening fast and not sure how they're changing the code so fast! ... thanks
Just get to practicing typing using 10fastfingers, keybr or typreracer. I'd suggest start with 10fastfingers. Treat it as a fun activity, because you're primarily training your muscle memory. Give it time, and it'll definitely go up. Oh and also, have a fun keyboard to type with! I dont use mechnical keyboards because my macbook pro 2021 keyboard has really tactile keys already.
I am trying to productive when by looking youtube video about productivity
Gotta go fast!
When you want to build your software in a structured way and find and fix bugs, do test driven development. Do not waste your time manually testing your code all the time. I even learn new languages by writing tests.
Yes but that's typically the kind of things the senior programmers will tell you will cost time that customers are not willing to pay for.
@@bra5081 If your customer is not interested in the quality of its Software, he has poor Managers and therefore not much of a future. Try to run.
I am a newbie.I didn't get your point.Can you plz explain it for me
These things which u've mentioned. Are Gems. Seriously thank you. I've personally experienced all these n have realised many of these mistakes.
The flashing lights on your PC are so distracting lol
started to use kite on pycharm
So to find a bug one must think like a bug. Embrace it. Become one!
Thumbs up for just saying no to memorising syntax
good work
keep it up
Do competitive programming with code chef
One of the problems with programmers is that they overengineer the code so bad and simply screw the working code. A good programming that works for me all the time is firstly know what you wanna do, secondly make a ui research about similar programs or make one of yours or maybe you have a designer that designs the ui for you, second step make a structure on a piece of paper of all of the design. For example the comment bar is a column with a sizedbox a row and a sizedbox, the row contains a thumbnail image, a textbox, a submit button which are all in a container for easy layout(currently using flutter, for other languages know your language). Make all the skeleton of the program that you are going to write, then make yourself a hierarchy with folders and files, and actually name your stuff, for example put your functons or methods inside a folder named functions, put your pages on a folder called pages, put the items that is the key of that page into a folder called items etc. Seperate the code to multiple files so that you wouldn't need to read 1000 lines for a simple function you are trying to find, never make a single file for especially a huge page. Nextly, don't code with non-understandable variable names and in an unnecessarily complex way, this will reduce efficiency and increase complexity of the software. If you do all of these and still code slow, then you should know what to google or how to google and stackoverflow becomes a helping hand out there waiting for you
Agreed bro I have been coding for 8 years by now an all you mentioned is the worse night mare and for me, UA-cam is my worst night mare
Tim what's ur best coding editor
he uses sublime or kite. try both are good
Thanks.
Here's a simple function for bug fixes:
def isBug(p, q, r, n=30):
""" Checks pre condition p and post condition r for closure q """
bugCount = 0
for x in range(0,n):
if not p():
print("Precondition failed")
bugCount++
continue
q()
if not r():
print("Post condition failed")
bugCount++
if not bugCount:
print('Congrats! {P}Q{R} is successful. More test runs can be issued to verify the issue.)
else:
print('Sadly, the given {P}Q{R} has {0}/{1} failures'.format(bugCount, n))
Every line u spoke is true💯👈
Appreciate it 👌
thankyou TWT
I think taking breaks are really important as it will prevent from burnout
Keep feeding us with you experiences, your videos are really helpful, thanks a lot .
Subscribed Pro
i love you jim, i am following your kivy vids atm.
Do you have any tips while making an app in kivy?
If you love me so much you should learn how to spell my name!! xD
Tech With Tim 😅
long hours focus is bad for health. People before 40 may not notice the negative side effect becuase of body's fast regeneration. But once they health drop to certain level, they start to experience all kind of disese.
There has to be a way to do coding in multiple short periods.
Thank u
Np!
Yes 6years and coding still slow me down
Once you add libraries and api's you realize it's almost impossible to memorize syntax.
Bro Give a try to competitive programming!
I’m actually trying to get into it!
Do you think vim is worth the time investment?
How is named that color of your syntax? It looks cool
Honestly couldn’t tell you :/ sorry!
The camera doesnt focus on you, and that makes me cry
I am a beginner I am struggling to type fast when coding and in general ! Can you please help me out Tim !
You can reply anytime 👍🏿
1st solution to "fix" bugs: Avoid code smells.
2nd solution: Write unit-tests.
3rd solution: Use automated CI/CD.
what is that thing on the top of his screen ?
I would never recommend coding without a break for long hours. Not only is this bad for your health overall (think: eyes and spine) but it will also slow you down, not to mention you'll be making silly mistakes you'd never make if you were fresh and rested. Many a time have I had a situation where I came to work after long hours of coding only to find out that I had made really *silly* mistakes the day before. In a word: never do that if you want to enjoy your life and work until a very old age and still be able to do what you did when you were young. If you neglect your body, one day it'll neglect you. Do you want this? I don't think so. A wise man knows one has to have everything in moderation. If you go to extremes and force your body into abnormalities, you'll be sorry sooner rather than later. So, the advice to code for 12-18 hours is not only ridiculous but also a very dangerous one. One last thing... Bear in mind that the latest research shows one can effectively focus for about 45 minutes. So, do yourself a favour and take frequent breaks when coding. When you don't code, do something completely unrelated to coding. You'll thank me later.
I agree with everything you’ve said. I apologize if I made it sound as though I endorse coding for 12-18 hours... I DO NOT. I am simply trying to illustrate that focus is important and the ability to focus for long periods of time in my experience increases efficiency. Of course you need to take breaks and of course your body is #1 priority. I am simply trying to say that most people I know can’t focus for even 20 minutes and that is not ideal when working on complex problems. Anyways I apologize to anyone that’s taken the video the wrong way, I’ll make sure to be more articulate in the future.
@@TechWithTim No worries, mate :) No need to apologize, either. Later in the vid you are kind of correcting the view. But you know... after all, people will do what they want anyway :) It's a pity, though, that very often bad habits tell on you later in your life, not right away. Many of us have to learn the proper way the hard way. By the way, the tip at the beginning about "kite" was a very good one. Every day something new. Thanks.
Testdriven Development
first 3 reasons, debugging, debugging, debugging
Tim , did yoy get an offer from Microsoft or not?
After I code i'm afraid to close the file because I feel like i'm gonna forget everything I wrote which I always do. T_T
Use comments or docstrings will take longer but you will remember
Does anyone already used KITE ?? I´m wondering to use it .... thanks in advance
I thought typing speed could be one of the factors.. maybe because I’m a beginner....
How do I type my code faster?
Tim, do u recomend a desktop over laptop for coding ? I’m using a 15’ laptop and it feels so cramped everything is annoying. Do u think i should get a desktop ?
Yes I personally feel much more efficient on a desktop. However if you’re coding on the go a lot then obviously laptop will be a much better option. I personally have two laptops and a desktop. I’ll always use my desktop when it’s available because of the massive screen size (27 and 24 inch monitors) also I really like mechanical keyboards
Tech With Tim i’m just borrowing the laptop from my sister i swear its really annoying she block me from doing anything that make changes to the system and i’m also limited by time too! I can only use it for a period of time and the laptop will kick me out when times out. So im thinking of getting a pc soon, i have been thinking a lot ! First i was thinking between using laptop + external monitor and a desktop but i find laptops with high specs are way too expensive and cheap gaming laptops are ugly and low battery. So i guess im gonna go with desktop ! Btw i love mechanical keyboards too, which switch are you using ?
P/s : you just motivate me back with coding :D i just gave up for few weeks because of too much stress from family and schools.... thanks alot
Tim , teach us python for free bro please :(
I have over 300 videos covering python! For free
I don't think that telling people to plan and not get distracted is very insightful at all.
I wouldn't get anything done with that flashing going in.
12 hours 😅 Yes, you can do that and then you will rest two days doesn't looks good for me in a long term view, after years I realize that's just not possible to work hard every day, the result is just burnout, procrastination, and demotivation Guys take your time for rest really if you want to work more than 3-4 years in IT
You can't code faster if you don't know what you're coding tim.
That’s very true EnergyCC
lol just 12 hours ? at microsoft we call this half time job xD
:0
Code
👀😊
Someone give me a run down of he’s list, just don’t have time to watch it all.
"sTAck OvERFLoW"
No it’s my fucking type speed and accuracy
How to bug, the bug.
In my opinion you're fans are changing colors too quick, it's distracting me ^^ am I the only one?
Yes