This is the most under rated channel on TH-cam when it comes to coding. No BS just straight talk about proper skills to get you ready. I'm glad Google AI recommended this channel to me by spying on all my devices and deducing I am in dire need of some proper coaching 🤣🤣🥺
Consistency is the one really important thing that I've seen people lack. They get tired of programming and switch to either management roles(where most of them fail miserably) or some other non-programmatic roles. One thing where I struggle is: Easily being distracted and if we're stuck on something for a long time, we need to take a break and work on something that you can knock off. So we keep completing our tasks and not just get stuck on something for an infinite amount of time. I know this but still, struggle a lot. Any advice would be really appreciated.
@Rashed Arman Yes it is. I did it in the same way. Follow the following steps: 1. Get a learning path, you can get it online Example: learn git, html, css, javascript/python, build projects using those tech, then go for advanced tech like Angular / React / Vue, build projects in them, learn about mysql/nosql and so on. 2. Keep doing tutorials and get stuck in as many problems that you can, as more the problems more you get familiar with the technology. 3. Interviews: go out for as many interviews as you can, and take it as a learning path. you will learn more in interviews than you can do it on your own. 4. If you can't get a job, join a team for free till you're able to be really good at your skill but make sure to keep applying. Also, you can take freelancing projects or help someone in your community, like a shop around you can get their own website. Build accounting software for someone or some shop who are not tech-savvy. This will help you build a stronger resume. and there are a bunch more, let me know if you want to learn CS as we teach on YT as well as personally
Regarding learning I can just recommend people to use the pomodoro Method (25min learning » 5 min pause) Don't just watch courses and write along. Don't copy paste...not yet atleast. Every course teacher has a different Code Style. Ask behind the things you learn. Learn the basics. Learn by doing. Do Projects, a lot of them. For myself I find my own projects, literally just by looking around for things that could be improved or are intriguing enough to start something.
This is just my experience, but i also recommend you guys to do a lot of "Homework" with the programming languages, such as Python(i like Python more than Java), that will create persistence.
The most important thing is to work on real-world problems, that you truly care to solve, keeping you passionate. Also in the spare time always keep learning new techniques and best practices from tutorials/docs and browse a lot of open source.
@@WebDevSimplified Yup, it's crucial to understand, that becoming a developer is not a destination, but an endless road to walk. Once coding has become your second nature/daily routine, you know you are walking the right direction and all the good things will eventually come.
After two months, your own code will feel like someone else's and you'll be cursing yourself for not leaving comments and meaningful variable names as much as landing in a spaghetti legacy job.
Yep, this video talks about programming for someone else, but I always think of myself returning to this code a year from now. If I imagine I may have some trouble understanding it and modifying it, then I know I need to refactor some more and include more useful comments for the tricky parts.
having a team with all kinds of levels of programmers is what made me improve soooo much. Like not just having someone super experienced, but also some people inbetween and even some people less experienced as yourself. You get many many perspectives and you learn new things and how to improve things every day
Great advice. I learned so much from building my own website. It made concepts that were abstract into things that were practical and useful - examples are learning how to use "async" and "await". Real life projects are a great way of improving one's skills and it forces you to keep pushing and finding answers instead of giving up easily.
My very first job and still my current job for 2 years is actually being a full-stack developer. I'm currently at the stage where I'm looking to become a better developer so I can do my job much much better! And your videos really helping me to become better. Thanks for that!
I so agree we this, I have spent over 3months working on a new version for an npm package for managing a database, it's one of the toughest project I have ever done but I have also learnt a lot from it.
I started learning Web Dev on my own on january. A few weeks ago I started this first project on my own: tracking app, to track shipping status online and display notifications on the smartphone. But I hit a wall: I know I need the mobile app and an API to fetch the information from the courier websites, but the first website I tried does not provide an API so I have to use web scraping to get data. But I want this app to be maintainable and scalable, so I can add more things to it in the future. Some people say that I should start with something simple, but no f*cking way, I want to build something good, that people really use and it's good for my portfolio. Anyway, I won't give up on this. Thank you Kyle. Great channel. Kind regards.
I was going to mention that developers need to work in team, but I see you put that in the end too 👏 Being a developer requires not just coding chops, but also soft skills: you can be the enfant prodigie, but if nobody wants to work with you… you’re not gonna last in the professional world. I would add that you also need stakeholders, as you need the external pressure of delivering on time a good product. Not only that, but to learn to focus on the right things to develop (specs), and manage the communication and expectations. I am wondering and a bit concerned that people might think they can be a great developer by hunkering down for a year or even a few months.
Some brilliant points here. In the real world you don't need to be a algo expert. You should aim for 100% test coverage. Learn what mocking is aswell. Debugging skills are also essential.
Sadly most of job interviews are based on problem solving tasks rather then 'take home' projects etc. and requires you to prepare for job interview if you want to score the job..
This are the best tips I have seen so far, on how to become better in development. I especially agree with the part about the code challenges, I just hope more companies cop on, and don't give out algorithmic code challenges where is not necessary. This way they are loosing potentially great developers in the first step. The part about code reviews as well, In my experience a couple of months of working with a team where proper code review was done, helped me way more, compared to years of working without code reviews.
Just started watching the channel, but so far I love the content. It's less about helping people be better "Coders", and more about helping people be better Developers. Love to see it, and I look forward to binging more of these videos
All beginner level developers can be very grateful that your Fantastic TH-cam channel exists 🙂, Kyle, thank you for the lots of useful tips and tricks, I am recommending your channel to everyone around me.
One more little piece of advice I would like to add is, always read other people's code. If you are a newbie or a mid level dev, you have barely enough time to get something to work and you may not have the time or the skill to make the code more readable and maintainable. So if you read code written by others, you can learn something from how they structured the code, how they made the code more efficient and if they used any new techniques and that will help you write better code. If you read and write code regularly, over time you will definitely get better. Also, you can read queries on stackoverflow to learn how to find solutions for certain problems which will also help you in your coding.
Awesome channel. I'm going thru a lot of depression right now and I'm finding lack of motivation to be something I gotta get thru. Thanks for making these videos!
100% agree with you. However people do have to use codewars or leetcode to practice those so they can get into the door of the company (or their dream companies). So you need to do both. But I don't think practising algorithms alone can make you a good programmer. I think large scale real world like projects where you need to think and hopefully get feedback would do.
Totally agree what you said, when I was in college that time only one thing most of us used to know that just do a lot of ds and algo that's it and you surely place in big tech like Google, Microsoft etc. But in reality when I started working with Apple they really on clean code more than optimization, it's true.
Yes, totally agree with this. The only problem is how you tell them that you're great developer. Most of them is using problem based coding test to decide whether someone is a great developer or not. To be honest, after working for companies for years, I feel like my problem solving/algorithm skill is decreasing, instead I rather learn more about coding best practices, design pattern, etc. You just can't say, "I'm great developer I swear, try me!" after seeing your result is not satisfied. I hope companies can realize this and improve how the way they interview their applicants.
All you said is really really true. But, if you don't know how to solve those leetcode problems you will have a hard time getting a job. I will tell you a story of mine. I applied to a company and because I had all the skills they said that were needed for the position, I was very excited and wanted this job. They said they don't care about degrees and they only care about if the person have necessary skills to do the job. So, they sent me a really long question paper. I was very impressed by the question paper because I enjoyed answering them. They asked very language specific questions and some front end framework related questions. It took me 3 days to answer all of them. Then they invited me to the 2nd phase. They sent me few projects to build and these projects were not simple ones. I worked really hard on the projects and finished the projects in 6 days. I was very confident. They invited me for the last phase which was in-person interview. And guess what they asked? They asked me these leetcode-kind problem solving questions, which obviously I couldn't perform well in and didn't get the job. So, yes, it is very important to solve leetcode questoins.
Completly agreed, especially if a person is new to software development. However- A person who writes well written code but not great at DS&algo = $100k/year A person who is ok at writing well written code but great at DS&Algos= $250k/year
The need for ds&algo is almost negligible in day to day work due to various frameworks and libraries that handle all of that in the background. It's only used mostly in interviews.
This is very helpful, I'm not really good at web programming so I wanted to give up, but now I realize I haven't done most of your tips, I can't give up yet.
I agree with everything you said except that you should be practising leetcode and data structures & algorithms at the same time as this is the bar for technical interview for the top tier companies.
I'm 32 and learning Node ;) -- wish I had learned it at your age! I think it's great that you're interested in web dev and learning it now! Keep up the good work!
yo dawg great video. just wanna say i have the same blinds on my window. they're reallly shit and they broke super quickly. how are they holding up for you?
Exactly. The most valuable virtue is to write a good maintainable codebase. Even if u have to write bit more verbose code at the cost of few milliseconds , plz do so , to save the hours of new developer understanding your code.
Wow, exactly what I was planning, after passing a time learning with courses and tutorials I start thinking about building a large fictional startup product as a Fullstack Developer and creating articles explaining the process
"You more so are writing code for the developer that comes after you and not necessarily for the computer that it's running on" what a god damn wise line dude, wish we got this written on a front wall of every fkin IT company out there
my fellow bootcampers would look at me funny when I'd say I want to focus strongly on writing clean code and testing rather than cramming a bunch of technologies... guess I was on the right track!
Maybe because these companies don't see it just from DS and algorithms point of view but problem solving point of view. If you can solve a problem in 30 minutes with your code while the other person take 3 days for the same problem, there is unprecedented advantage you will have over the other person. Although over the period of time, most of developer's figure it out that bad code won't take them any further.
Yeah god, I really love this video! because there are so many friends trying to practice a lot of Code challenges. It is important though but not more than a readable code. Awesome video!!! Even when they see a new feature enclosed in a Class or in a new module, they tell you that it is totally unnecessary.
Hey Kyle, could you create a series about testing, really find myself struggling with this topic, especially the combination of two frameworks like Jest and Enzyme. Thanks
"You are more so writing code for the developer that comes after you than the computer you're running it on." Preach. I have the benefit of not needing to build what I do in the top 5% most performative things. But what I see ALL the time is either stuff I forgot to comment or inherited work from someone even more forgetful than myself (or just...spaghetti). I don't know how I'd do at a challenge because my "challenge" is so super unique to what I have to handle in a day. It all is. Being good at challenges is being good at that one problem to solve just as if it were another client project. If I have the skill to solve that I am not learning anything new by simply flexing in place.
"People that use Facebook won't care if it is 1% slower...." - You know that these performance inefficiencies add up? With a system degrading over time you are sure to lose users. Users these days doesn't tolerate a slow performing application. You should always, and always try to write more performant code. More so in today's age. With per millisecond billing for some cloud providers you definitely want to save on this. It's not only about the user, it's also about the sponsor for the project.
I gotta be honest - I'm *way* out of practice on data structures and algorithms, and it's almost exclusively being used in technical interviews. I really gotta up my game. Ugh.
![เขามัทรี - เอ็กซ์ ศุภกฤต - จอนนี่มิวสิค [ Official MV ]](http://i.ytimg.com/vi/AS9ufKuQIVs/mqdefault.jpg)
This is the most under rated channel on TH-cam when it comes to coding. No BS just straight talk about proper skills to get you ready. I'm glad Google AI recommended this channel to me by spying on all my devices and deducing I am in dire need of some proper coaching 🤣🤣🥺
Senior dev here: this advice is pure gold
Nicr
Couldn’t agree more!
Mid-dev here, absolutely agreed.
junior newbie dev here: i have to agree :D
@@perveenneha1423 same hehe
Eloquent Javascript was saying the same thing about prioritizing readability over performance. Great to hear you reinforce that idea.
Consistency is the one really important thing that I've seen people lack.
They get tired of programming and switch to either management roles(where most of them fail miserably) or some other non-programmatic roles.
One thing where I struggle is:
Easily being distracted and if we're stuck on something for a long time, we need to take a break and work on something that you can knock off.
So we keep completing our tasks and not just get stuck on something for an infinite amount of time.
I know this but still, struggle a lot.
Any advice would be really appreciated.
See a problem and allot a time/alarm then keep working on it till alarm you can snooze or start a new problem and keep repeating the cycle
@Rashed Arman Yes it is.
I did it in the same way.
Follow the following steps:
1. Get a learning path, you can get it online
Example:
learn git, html, css, javascript/python, build projects using those tech, then go for advanced tech like Angular / React / Vue, build projects in them, learn about mysql/nosql and so on.
2. Keep doing tutorials and get stuck in as many problems that you can, as more the problems more you get familiar with the technology.
3. Interviews: go out for as many interviews as you can, and take it as a learning path.
you will learn more in interviews than you can do it on your own.
4. If you can't get a job, join a team for free till you're able to be really good at your skill but make sure to keep applying. Also, you can take freelancing projects or help someone in your community, like a shop around you can get their own website.
Build accounting software for someone or some shop who are not tech-savvy.
This will help you build a stronger resume.
and there are a bunch more, let me know if you want to learn CS as we teach on YT as well as personally
Regarding learning I can just recommend people to use the pomodoro Method (25min learning » 5 min pause)
Don't just watch courses and write along.
Don't copy paste...not yet atleast.
Every course teacher has a different Code Style.
Ask behind the things you learn. Learn the basics. Learn by doing. Do Projects, a lot of them.
For myself I find my own projects, literally just by looking around for things that could be improved or are intriguing enough to start something.
This is just my experience, but i also recommend you guys to do a lot of "Homework" with the programming languages, such as Python(i like Python more than Java), that will create persistence.
The most important thing is to work on real-world problems, that you truly care to solve, keeping you passionate.
Also in the spare time always keep learning new techniques and best practices from tutorials/docs and browse a lot of open source.
So true. That is exactly what I did to learn web dev.
@@WebDevSimplified Yup, it's crucial to understand, that becoming a developer is not a destination, but an endless road to walk.
Once coding has become your second nature/daily routine, you know you are walking the right direction and all the good things will eventually come.
@911mazda saved screenshot of your last comment. Very well said👍
So true! been searching for docs to learn what are the best practices.
@911mazda
What do you mean by real world problems?
After two months, your own code will feel like someone else's and you'll be cursing yourself for not leaving comments and meaningful variable names as much as landing in a spaghetti legacy job.
Yep, this video talks about programming for someone else, but I always think of myself returning to this code a year from now. If I imagine I may have some trouble understanding it and modifying it, then I know I need to refactor some more and include more useful comments for the tricky parts.
Same happened to me
Good code documents itself
having a team with all kinds of levels of programmers is what made me improve soooo much. Like not just having someone super experienced, but also some people inbetween and even some people less experienced as yourself. You get many many perspectives and you learn new things and how to improve things every day
Great advice. I learned so much from building my own website. It made concepts that were abstract into things that were practical and useful - examples are learning how to use "async" and "await". Real life projects are a great way of improving one's skills and it forces you to keep pushing and finding answers instead of giving up easily.
Thank you beast, I'm gonna open the Design Pattern playlist now! 😍
I hope you enjoy it!
My very first job and still my current job for 2 years is actually being a full-stack developer. I'm currently at the stage where I'm looking to become a better developer so I can do my job much much better! And your videos really helping me to become better. Thanks for that!
I think having someone to review your code is an excellent point. I'm gonna find someone to review my code after here.. Thanks Sir Kyle.
How one can find someone to review their codes
I make sure the let these ads play.
Information like this is very valuable
Thanks Kyle
I so agree we this, I have spent over 3months working on a new version for an npm package for managing a database, it's one of the toughest project I have ever done but I have also learnt a lot from it.
I started learning Web Dev on my own on january. A few weeks ago I started this first project on my own: tracking app, to track shipping status online and display notifications on the smartphone. But I hit a wall: I know I need the mobile app and an API to fetch the information from the courier websites, but the first website I tried does not provide an API so I have to use web scraping to get data. But I want this app to be maintainable and scalable, so I can add more things to it in the future. Some people say that I should start with something simple, but no f*cking way, I want to build something good, that people really use and it's good for my portfolio. Anyway, I won't give up on this. Thank you Kyle. Great channel. Kind regards.
I was going to mention that developers need to work in team, but I see you put that in the end too 👏 Being a developer requires not just coding chops, but also soft skills: you can be the enfant prodigie, but if nobody wants to work with you… you’re not gonna last in the professional world.
I would add that you also need stakeholders, as you need the external pressure of delivering on time a good product. Not only that, but to learn to focus on the right things to develop (specs), and manage the communication and expectations.
I am wondering and a bit concerned that people might think they can be a great developer by hunkering down for a year or even a few months.
Some brilliant points here. In the real world you don't need to be a algo expert.
You should aim for 100% test coverage. Learn what mocking is aswell.
Debugging skills are also essential.
Sadly most of job interviews are based on problem solving tasks rather then 'take home' projects etc. and requires you to prepare for job interview if you want to score the job..
I absolutely agree to this video.
I however can't deny that such coding challenges still help enhancing ones problem solving skills.
This guy is a gem. Just gave me a good start to the day! ❤️
This are the best tips I have seen so far, on how to become better in development. I especially agree with the part about the code challenges, I just hope more companies cop on, and don't give out algorithmic code challenges where is not necessary. This way they are loosing potentially great developers in the first step.
The part about code reviews as well, In my experience a couple of months of working with a team where proper code review was done, helped me way more, compared to years of working without code reviews.
Just started watching the channel, but so far I love the content. It's less about helping people be better "Coders", and more about helping people be better Developers. Love to see it, and I look forward to binging more of these videos
Another great video... thank you for posting 👍🙏
I just realized, that im not subscribed, lol. One of the best web dev channel across the entire universe :D Good job, keep working!
All beginner level developers can be very grateful
that your Fantastic TH-cam channel exists 🙂, Kyle,
thank you for the lots of useful tips and tricks,
I am recommending your channel to everyone around me.
You truly are underrated. Such an informative video! 👊
One more little piece of advice I would like to add is, always read other people's code. If you are a newbie or a mid level dev, you have barely enough time to get something to work and you may not have the time or the skill to make the code more readable and maintainable. So if you read code written by others, you can learn something from how they structured the code, how they made the code more efficient and if they used any new techniques and that will help you write better code. If you read and write code regularly, over time you will definitely get better. Also, you can read queries on stackoverflow to learn how to find solutions for certain problems which will also help you in your coding.
4:48 The hesitation to not make a pun (a solid understanding of the solid designer principles)
Awesome channel. I'm going thru a lot of depression right now and I'm finding lack of motivation to be something I gotta get thru. Thanks for making these videos!
I hope you're feeling better now 💛
You are my true teacher. Thank you
100% agree with you. However people do have to use codewars or leetcode to practice those so they can get into the door of the company (or their dream companies). So you need to do both. But I don't think practising algorithms alone can make you a good programmer. I think large scale real world like projects where you need to think and hopefully get feedback would do.
Totally agree what you said, when I was in college that time only one thing most of us used to know that just do a lot of ds and algo that's it and you surely place in big tech like Google, Microsoft etc. But in reality when I started working with Apple they really on clean code more than optimization, it's true.
Yes, totally agree with this.
The only problem is how you tell them that you're great developer. Most of them is using problem based coding test to decide whether someone is a great developer or not. To be honest, after working for companies for years, I feel like my problem solving/algorithm skill is decreasing, instead I rather learn more about coding best practices, design pattern, etc.
You just can't say, "I'm great developer I swear, try me!" after seeing your result is not satisfied. I hope companies can realize this and improve how the way they interview their applicants.
All you said is really really true. But, if you don't know how to solve those leetcode problems you will have a hard time getting a job. I will tell you a story of mine. I applied to a company and because I had all the skills they said that were needed for the position, I was very excited and wanted this job. They said they don't care about degrees and they only care about if the person have necessary skills to do the job. So, they sent me a really long question paper. I was very impressed by the question paper because I enjoyed answering them. They asked very language specific questions and some front end framework related questions. It took me 3 days to answer all of them. Then they invited me to the 2nd phase. They sent me few projects to build and these projects were not simple ones. I worked really hard on the projects and finished the projects in 6 days. I was very confident. They invited me for the last phase which was in-person interview. And guess what they asked? They asked me these leetcode-kind problem solving questions, which obviously I couldn't perform well in and didn't get the job. So, yes, it is very important to solve leetcode questoins.
What kind of company taking you 9 days to complete a project? Is this normal interview process in your country?
@@khairiyusoff5040 No, every company is different when it comes to hiring.
- Make big real world projects
- Learn SOLID design patterns
- Learn Testing
- Code Review
"if you don't have someone else teaching you, it's gonna be really hard for you to learn"
We have you teaching us tho
And we're thankful for that
Thank you; your videos are genuinely helpful and meticulously well-produced.
Completly agreed, especially if a person is new to software development. However-
A person who writes well written code but not great at DS&algo = $100k/year
A person who is ok at writing well written code but great at DS&Algos= $250k/year
$100k already sounds like a paradise for me
The need for ds&algo is almost negligible in day to day work due to various frameworks and libraries that handle all of that in the background. It's only used mostly in interviews.
Outstanding advice. Bravo.
Thanks man!
This is very helpful, I'm not really good at web programming so I wanted to give up, but now I realize I haven't done most of your tips, I can't give up yet.
1. build complex project
2. write clean code using solid, patterns,
3. write tests,
4. make code review
Thanks for the video! And for the links in the info!
your method of explanation makes you the greater, thanks for the video
I agree with everything you said except that you should be practising leetcode and data structures & algorithms at the same time as this is the bar for technical interview for the top tier companies.
All of this is mentioned in his JavaScript course, highly recommended.
Man your view of looking at things is great.
I can't express how relatable this video....
Hi, Im 12. Im learning Node At The Moment And Am Developing An App, I Just Wanted To Let You Know How Much Of A Help You've Been To Me! Thank You!
Good going. It's great to see you involved in coding from a young age, keep it up 💪🏻
I'm 32 and learning Node ;) -- wish I had learned it at your age! I think it's great that you're interested in web dev and learning it now! Keep up the good work!
@@leahj6214 it's never too late to learn ^-^
When i was 12, i used to eat soil. You are on right track, kid.
I'm 15 and I have learned nodejs , express etc and now I'm making an web app😐
yo dawg great video. just wanna say i have the same blinds on my window. they're reallly shit and they broke super quickly. how are they holding up for you?
They have been working well for me but I generally don't move them up and down often.
John Johnson asking the important questions
Exactly. The most valuable virtue is to write a good maintainable codebase. Even if u have to write bit more verbose code at the cost of few milliseconds , plz do so , to save the hours of new developer understanding your code.
Wow, exactly what I was planning, after passing a time learning with courses and tutorials I start thinking about building a large fictional startup product as a Fullstack Developer and creating articles explaining the process
"You more so are writing code for the developer that comes after you and not necessarily for the computer that it's running on" what a god damn wise line dude, wish we got this written on a front wall of every fkin IT company out there
my fellow bootcampers would look at me funny when I'd say I want to focus strongly on writing clean code and testing rather than cramming a bunch of technologies... guess I was on the right track!
Thank you bro I needed this in my life.
Thanks for the info
Maybe because these companies don't see it just from DS and algorithms point of view but problem solving point of view.
If you can solve a problem in 30 minutes with your code while the other person take 3 days for the same problem, there is unprecedented advantage you will have over the other person. Although over the period of time, most of developer's figure it out that bad code won't take them any further.
Yeah god, I really love this video! because there are so many friends trying to practice a lot of Code challenges. It is important though but not more than a readable code. Awesome video!!!
Even when they see a new feature enclosed in a Class or in a new module, they tell you that it is totally unnecessary.
Very insightful ! Thank you for this great video
Thank you so much for the tips! im lacking so much potential i will def. try this!
thanks!!
Thx for sharing dude 👍🏻
well said........
Thanks Kyle ❤️❤️❤️
This is so good 😍
Hey Kyle, could you create a series about testing, really find myself struggling with this topic, especially the combination of two frameworks like Jest and Enzyme. Thanks
Thanks for mentioning about "Testing", can you please create video about "TDD" and your own experiences with "TDD" ? Thanks in advance. God bless you.
Thanks for sharing
Thanks sir. This video is really helpful. Can you please make a series on react testing.like enzymes or jest. Love and support ❤️
The various types of testing you mentioned, are you planning on doing video tutorials about them?
Thanks, man
always thanks your videos! it is awesome!
Great video, as usual!
Amazing guidence 😎
thanks you, i really want to become great developer, this video is really helped me.
"You are more so writing code for the developer that comes after you than the computer you're running it on."
Preach. I have the benefit of not needing to build what I do in the top 5% most performative things. But what I see ALL the time is either stuff I forgot to comment or inherited work from someone even more forgetful than myself (or just...spaghetti).
I don't know how I'd do at a challenge because my "challenge" is so super unique to what I have to handle in a day. It all is. Being good at challenges is being good at that one problem to solve just as if it were another client project. If I have the skill to solve that I am not learning anything new by simply flexing in place.
"People that use Facebook won't care if it is 1% slower...." - You know that these performance inefficiencies add up? With a system degrading over time you are sure to lose users. Users these days doesn't tolerate a slow performing application. You should always, and always try to write more performant code. More so in today's age. With per millisecond billing for some cloud providers you definitely want to save on this. It's not only about the user, it's also about the sponsor for the project.
I won't even care if FB is totally shut down. 😂
@@j.k.ravshanovich 🤣
I absolutely agree with you!
Great video as usual 👍👍👍
Thank you, this video is what every junior should hear. Uncle bob is not far ^^
Thanks for another great video
As a person going bald, I am just focused on your hair
I’ve lost a lot of hair during this pandemic.
@@teenytinytoons I am bald now
Thanks 😊😊
I'm not good, just ok and want to be good. then want to be great like you bro.
great content! thanks
Thanks, Kyle
what a great video!
good suggestions bro
We should spend more time in building so that we need less time to maintain it.
That is not practically possible. Because the business side doesn't understand what you're saying. To them time to market is way more important.
I agree with you!!
I gotta be honest - I'm *way* out of practice on data structures and algorithms, and it's almost exclusively being used in technical interviews. I really gotta up my game. Ugh.
I accept you as my "Coding Guru" [Guru means dispeller of darkness]
Solving these problems increases thinking skills
I noticed he blinks alot now I can't unsee it.
Thanks
Totally agree with this statement about coding challenges but don’t you think that without leetcode skills getting a job is far more harder ?
Inspired to code aoaoooaooaoooo. You are the best code blogger.
I love your Hair Style Bro 🔰
thanks
Wish this guy was my mentor.
amazing man.
Can someone point me to a good site/vid about writing tests? That's one thing I want to get better at.