The final point might honestly be the most important. I loved that you mentioned “you need to learn how to learn” because when I finally realized that concept, my ability to grow finally stopped being limited and I was really able to ascend much faster.
Appreciate the joke but if its serious I can say for sure. Even if there are no bugs, there will always be adding new features or changing the way something works.
As experienced developer I can say it is funny how many IT recruitment companies looking for speed when test candidates. Forgetting that in a real world speed is not the main issue. Ability to solve problem best way and code it with high quality is the most important.
I agree 100% with it. Sometimes the hiring team focus in speed, solving some irrelevant leetcode challenges, etc. But it more important code with quality and making clean and understandable code, especially if you are working with a team. Many thinks should be change in the world of programmer recruitment.
Correct. About the third skill, the big mistake most beginner developers make is that they think that they have to learn an entire programming language 100%, but that's just undoable. Rather learn 5 languages at around 40-50% instead of a single one at nearly 100%.
1.Quality - take time to write better quality code that is robust & covers edge cases too, will be helpful in long term. 2.Communication - all big projects are a result of team - so need to communicate effectively with team members. - should be able to explain in technical & non-technical way depending on with whom you're talking to. 3.Learning - learn how to learn quickly & effectively [as developers we learn new things a lot] - when learning something new, don't learn everything, learn just bare minimum essentials to get started. (With 20% core knowledge you can do 70-80% of the things)
As senior software developer, and team lead. I can confirm that this is 100% accurate. I would place communication and learning before quality code. because you can have those 2 before you get to the great quality of code.
Exactly.. the first thing I look for when evaluating new workforce is the passion, communication and personality. I move through the school, previous jobs, etc parts of CV ultra quick.
I agree with all of these 100%. On the communication bit, I recommend for tickets if you can to use a screen recording software and as much screenshots as possible when you are describing problems. It removes potential ambiguity that can come from text messages and makes it easier to be able to communicate to a wide variety of audiences what exactly you're seeing. I also recommend especially when fixing bugs to always go through the steps to reproduce the bug that was given, I cannot tell you how many times I've been given a ticket for the bug to either already be fixed or for the issue described in the ticket to be completely different than what was being described. Non technical people will describe issues they are seeing in a completely different way than what you're level of understanding is, and it is critical to understand this.
Great advice on the last part! Having to learn just the bare minimum will suffice. Being exposed by writing codes will let you learn more about it after some time rather than just reading or listening to courses.
Have not even started watching my top 3 1 teamwork/teamplayer 2 test that give you confidence your code will work in prod first time 3 always up for learning, else be left behind
Your job as a developer isn't to write code, it's to solve business problems. The only thing I don't agree with whole heartedly here is the statement around edge cases. Handle things as best you can but new devs please don't obsess and over engineer because of this. If you work in health or some other critical system then sure, but for most the YAGNI principle applies. I'm confident this is what Kyle means, but I just want to state this for those that are in need of reading it. Keep up the great work Kyle, one of the best RUclipsrs out there on this topic! 👍🏼
After working in the industry for a couple years, this is literally the three things I have put the most of my effort into. 🙏🏽 This is sound advice. This man is not wasting your time
And tech skills beyond programming, such as networks, hardware, multimedia, design, and more. Skills in other areas do give you a significant advantage, that is how I got 3 contracts after 2 years trying to get a job.
good evening pal and thanks for all of your tips and videos . all of it is really helpful , i even started spending more time on the web because of your decent videos
learning new things is so hard as you getting older because after work you really feel burn out if you continue to program something else other than work
1. Discernment: knowing when you need something good enough and fast, and knowing when you need to slow down and ensure reliability and long term use of the code. Many times requirements change over time so that “quality” code you took all that time to write gets completely scraped and rewritten anyway. 2. Ability to Ship: some coders are just really really slow and by the time they solve the problem the business landscape has changed and a newer solution is needed. So you need the ability to write good quality code in a timely manner. It can be done and good coders do it all the time. It’s good and timely. Ultimately it doesn’t matter how bulletproof your code is if you never ship it or ship it way to late to help the business goals. 3. Business Acumen: ultimately your job is to solve business problems, not write the worlds best code. If you can do both great, but remember you are paid to solve problems.
Found the manager lmao. So what I gather from your comment is... 1. Do it fast: because requirements will change, so it doesn't matter how good your code is anyway. 2. Do it fast: because the business landscape will change, so it doesn't matter how good your code is anyway. 3. Do it fast: because solutions are needed now, so it doesn't matter how good your code is anyway. This is in my experience, what the typical mindset of tons of startups looks like, and it's why 99% of their code is _always a freaking mess_ and a nightmare to work on. It's a self-fulfilling prophecy of never having good code because "it doesn't matter, things will change anyway, we need this fast, we'll see later". Hopefully I'll never work in your company, J, since neglecting my own professional growth with quality coding, communication, and learning skills in favor of purely caring about helping "business goals" with bad code seems like a waste for both parties, except for you, it seems.
Communication is easily the most overlooked aspect of a developer. But as far as quality goes: most businesses do not care about code quality. They just want feature delivery. So good luck being the dev who writes tons of unit tests but never delivers anything. Also your advice for just learning the bare minimum of a new technology is kind of inconsistent with your advice on quality. I don't know how many times I've read the into to a piece of tech, implemented and found out that it just doesn't quite suit my needs and I have to do a major refactoring to get it working. As you learn more about the technology you realize how low the quality of your initial implementation was.
I think quality has more to do with better variable names, less states to set and to keep track of, better component composability, and a better reading flow. A few tests are fine, not over-doing them just to cover most cases and ChatGPT can write tests for us now. If there is a bug then another test is needed with the fix. Also documenting what you did on an issues which I guess goes with the communication part. When it comes to Junior Devs, they usually take the long and hard way to do things.
Can you please make a video for building a Chrome Extension with firebase/firestore database? Haven't found any for the new manifest v3 and would be a life saver!
One advice I can give, based on my experience, is to never say that something can't be done. Never say that something can't be done, never. What you can say instead is that the way something is being proposed isn't convenient or that it has implications (which you must explain why it has them)
i LOVE how you didn't mention leetcode or speed, which is something that a lot junior developer thing that is important and really invest a lot of time on that.
I just started learning threejs... Yes it has a lot of bits and pieces but I want to finish it... I am hoping to learn it and become an even better frontend developer
I'm missing skill of giving and receiving a feedback. To me it's essential and in both ways. If there is something wrong you should look forward to know about it and encourage constructive feedback. And as well, if your bosses screencast video has low resolution and bad mic quality, you must let them know about it.
I realize that there are different domains of programming, but knowing how to solve complex leetcode problems on the spot in an interview just feels irrelevant to most work programmers do, and doesn't necessarily speak to the quality of their code. I'd rather have a programmer who understands and communicates effectively with the people around them, understand requirements, understand the important of testable and well-documentet code etc, than someone who writes an inexplainable, seemingly efficient one-liner that's not debugable or even necessary for the product. Also, overengineered code can lead to technical debt like nothing else, for most programming languages you don't have to implement your own data structures, there are standardized libraries and internals that fix most stuff for you in an efficient way. So unless you're working on some cutting edge video rendering software or whatever, there are more than those qualities to look for in a programmer, and it's a shame to turn away great hires for irrelevant reasons.
I'm just starting to learn how to code, learning Javascript right now, what you said about not learning everything all at once, would you recommend beginners do that? or is this something that is just for experienced programmers?
Hello Kyle I learned lot of css and js through your videos.eagerly waiting for your new updated react course to buy.but please make cheaper as I am student form india the price is too high for us to buy for us to learn please make it cheaper so we can buy use of it.and any specific date when you are going to launch your react course?
Hey kayle first of all sorry if i am not spelling your name correctly. Can you make a video like what is testing and how it happens in a industry because many times when i apply for job i see in the description that bug free code okay i do test my code on the browser if i am building a web app but what about mobile app or anything else so can you clear this concept please ad you have experience and you've worked in industries as well because i don't understand that write scripts write tests for your code but question arise like where to write and what technologies. I couldn't find my answers on entire web please make a video on this topic it will be appreciated and a great help as soon as possible. Thank you ❤
I always think that side projects are important. It shows that the person is working with what he/she finds interesting. If that is the case they will be self driven and usually write better code. A lot of people that I interview have the "oh I learned to code because I need a job" attitude. They think they know how to code but they don't.. They piggybacked someone else in a larger project or something similar.
I think side projects are a nice signal, but I don't think they're mandatory for someone to be successful as a developer. I am not talking about course homework projects at uni/bootcamp, but more about passion/toy projects at home. Many people don't want to continue staring at a screen after 8 hours of working at the job and might have other interests they want to devote their limited free time to, but that doesn't mean they're incompetent at their job. So side projects can be a plus, but not a clear measurement of a dev's capabilities at the work place.
Agreed . 100%. Its not all IQ. If you can't even communicate properly or visualize your ideas to explain it to non-tech professionals you're not very useful. They want people who can explain and simplify complex techincal problems for them so that they can focus more on their core business instead of spending hours after hours debugging this new state of the art tech.
Do you share the pessimistic opinions about coding becoming obsolete in 20 years or you share the opinions of many that say that with the advancement of ai the software engineering jobs will bloom even more due to the increasing demand for more complex applications
Hello, Yes, I agree strongly, but is it TRUE about HIRING? Who of the managers or recruiters will hire you based on these conditions? I am sad to say this but close to NONE! The things you are talking about are hard to rely on, because these are not accepted as hard facts about a person. You have to trust someone that even though they do not have high code knowledge they write quality code, precise, but at relatively slow rate, which for solving hard problems is the most important. High code knowledge (knowing every single command stuffed in your mind) does not help you that much when inventing the solution, because solving time can last form 1h to 100h. It mostly depend on how programmer thinks. How fast he accepts and solves new things. But as I said this is not hard fact. HARD FACT when hiring is IN YEARS are you doing the same thing all over again, and HOW MUCH CODE do you have stuffed into your mind. This is unfortunately so wrong in programming in 21. century, especially after the latest acceleration. But what to do, it is how it is, and we have to deal with it...
If you want to learn how to learn, go to university, become at least an engineer or if you want to continue M. A. then if you still want to continue become a Ph. D. Anyway studies will learn you how to learn effociently - at least, of course it depends on you. Why? Well studies forces you to learn a lot of material in a short amount of time. Are there people who achieved tnie in their own? Yes, but rarely. Most people are lazy by default.
Man, it's absolutely FALSE information. Most of the companies are trying to make wastes on personal as low as possible. Not only IT companies, but all around the world. Only probably few of them care about quality, communication and learning. Tell this joke to the fired seniors with massive and experienced background, substituted by 10 cheapest one core brain developers
The final point might honestly be the most important. I loved that you mentioned “you need to learn how to learn” because when I finally realized that concept, my ability to grow finally stopped being limited and I was really able to ascend much faster.
How did you "learn how to learn" ? What are the bullet points?
Yeah. It's really cool and I'm reading a book on exactly this subject.
How else am I going to keep my job if i dont keep introducing bugs 😅
job security right there!
Now that's a great skill I need to work on !
I agree, if there are more bugs then there will be more demand of jobs. Less bugs equals to less demand.
Appreciate the joke but if its serious I can say for sure. Even if there are no bugs, there will always be adding new features or changing the way something works.
big brain moment
As experienced developer I can say it is funny how many IT recruitment companies looking for speed when test candidates. Forgetting that in a real world speed is not the main issue. Ability to solve problem best way and code it with high quality is the most important.
very illuminating, I see that clean code and learning the basics good is essential for improvement
I agree 100% with it. Sometimes the hiring team focus in speed, solving some irrelevant leetcode challenges, etc. But it more important code with quality and making clean and understandable code, especially if you are working with a team. Many thinks should be change in the world of programmer recruitment.
Correct. About the third skill, the big mistake most beginner developers make is that they think that they have to learn an entire programming language 100%, but that's just undoable. Rather learn 5 languages at around 40-50% instead of a single one at nearly 100%.
1.Quality
- take time to write better quality code that is robust & covers edge cases too, will be helpful in long term.
2.Communication
- all big projects are a result of team - so need to communicate effectively with team members.
- should be able to explain in technical & non-technical way depending on with whom you're talking to.
3.Learning
- learn how to learn quickly & effectively [as developers we learn new things a lot]
- when learning something new, don't learn everything, learn just bare minimum essentials to get started. (With 20% core knowledge you can do 70-80% of the things)
Thank you
As senior software developer, and team lead. I can confirm that this is 100% accurate. I would place communication and learning before quality code. because you can have those 2 before you get to the great quality of code.
❤
I wish to have you as my team lead
@@viallymboma9874 Thank you ❤
1. Sleep
2. Water
3. Fresh Air
Exactly.. the first thing I look for when evaluating new workforce is the passion, communication and personality. I move through the school, previous jobs, etc parts of CV ultra quick.
I agree with all of these 100%. On the communication bit, I recommend for tickets if you can to use a screen recording software and as much screenshots as possible when you are describing problems. It removes potential ambiguity that can come from text messages and makes it easier to be able to communicate to a wide variety of audiences what exactly you're seeing. I also recommend especially when fixing bugs to always go through the steps to reproduce the bug that was given, I cannot tell you how many times I've been given a ticket for the bug to either already be fixed or for the issue described in the ticket to be completely different than what was being described. Non technical people will describe issues they are seeing in a completely different way than what you're level of understanding is, and it is critical to understand this.
Great advice on the last part! Having to learn just the bare minimum will suffice. Being exposed by writing codes will let you learn more about it after some time rather than just reading or listening to courses.
Have not even started watching my top 3
1 teamwork/teamplayer
2 test that give you confidence your code will work in prod first time
3 always up for learning, else be left behind
O snap all my points are practically the same
Your job as a developer isn't to write code, it's to solve business problems. The only thing I don't agree with whole heartedly here is the statement around edge cases. Handle things as best you can but new devs please don't obsess and over engineer because of this. If you work in health or some other critical system then sure, but for most the YAGNI principle applies. I'm confident this is what Kyle means, but I just want to state this for those that are in need of reading it. Keep up the great work Kyle, one of the best RUclipsrs out there on this topic! 👍🏼
After working in the industry for a couple years, this is literally the three things I have put the most of my effort into.
🙏🏽 This is sound advice. This man is not wasting your time
And tech skills beyond programming, such as networks, hardware, multimedia, design, and more.
Skills in other areas do give you a significant advantage, that is how I got 3 contracts after 2 years trying to get a job.
good evening pal and thanks for all of your tips and videos . all of it is really helpful , i even started spending more time on the web because of your decent videos
Great video, as always 😁
And this Jackson on your back 👌
learning new things is so hard as you getting older because after work you really feel burn out if you continue to program something else other than work
1. Discernment: knowing when you need something good enough and fast, and knowing when you need to slow down and ensure reliability and long term use of the code. Many times requirements change over time so that “quality” code you took all that time to write gets completely scraped and rewritten anyway.
2. Ability to Ship: some coders are just really really slow and by the time they solve the problem the business landscape has changed and a newer solution is needed. So you need the ability to write good quality code in a timely manner. It can be done and good coders do it all the time. It’s good and timely. Ultimately it doesn’t matter how bulletproof your code is if you never ship it or ship it way to late to help the business goals.
3. Business Acumen: ultimately your job is to solve business problems, not write the worlds best code. If you can do both great, but remember you are paid to solve problems.
Found the manager lmao. So what I gather from your comment is...
1. Do it fast: because requirements will change, so it doesn't matter how good your code is anyway.
2. Do it fast: because the business landscape will change, so it doesn't matter how good your code is anyway.
3. Do it fast: because solutions are needed now, so it doesn't matter how good your code is anyway.
This is in my experience, what the typical mindset of tons of startups looks like, and it's why 99% of their code is _always a freaking mess_ and a nightmare to work on. It's a self-fulfilling prophecy of never having good code because "it doesn't matter, things will change anyway, we need this fast, we'll see later".
Hopefully I'll never work in your company, J, since neglecting my own professional growth with quality coding, communication, and learning skills in favor of purely caring about helping "business goals" with bad code seems like a waste for both parties, except for you, it seems.
@@AbrahamSayago found the guy who constantly misinterprets things, doesn’t understand balance and never shipped any code IRL.
thank for sharing these valuable things!!!
Very very awesome explanation
..hope you will make more videos❤
good content here! for me, i like taking notes in a notebook. I keep a professional journal that i jot down things i think i'll need to know later.
Communication is easily the most overlooked aspect of a developer. But as far as quality goes: most businesses do not care about code quality. They just want feature delivery. So good luck being the dev who writes tons of unit tests but never delivers anything. Also your advice for just learning the bare minimum of a new technology is kind of inconsistent with your advice on quality. I don't know how many times I've read the into to a piece of tech, implemented and found out that it just doesn't quite suit my needs and I have to do a major refactoring to get it working. As you learn more about the technology you realize how low the quality of your initial implementation was.
I think quality has more to do with better variable names, less states to set and to keep track of, better component composability, and a better reading flow. A few tests are fine, not over-doing them just to cover most cases and ChatGPT can write tests for us now. If there is a bug then another test is needed with the fix. Also documenting what you did on an issues which I guess goes with the communication part. When it comes to Junior Devs, they usually take the long and hard way to do things.
I'd love to learn more about quality. How about testing series?
Great content 💚
Can you please make a video for building a Chrome Extension with firebase/firestore database? Haven't found any for the new manifest v3 and would be a life saver!
One advice I can give, based on my experience, is to never say that something can't be done. Never say that something can't be done, never. What you can say instead is that the way something is being proposed isn't convenient or that it has implications (which you must explain why it has them)
i LOVE how you didn't mention leetcode or speed, which is something that a lot junior developer thing that is important and really invest a lot of time on that.
I just started learning threejs... Yes it has a lot of bits and pieces but I want to finish it... I am hoping to learn it and become an even better frontend developer
I agree with this completely. Great video, thanks!
wow
I have an interview right now
this video came in exact time
Thanks for great content!!
Can you make a video on micro front end where react component is connected to redux store and api??
Awesome tips!
Nice explanation khas brekker 😁
4th one , have hairs like this dude
Great speech!
Learning how to learn has been a huge help to me. It got me out of my comfort zone of regurgitating tutorial projects.
How did you learn how to learn
@@skyhappy There was a course on coursera I took, I think it was actually called learning how to learn.
Super cool perspective
This happens with me when client ask me to deliver feature within 2-3 days, I just write what works
I'm missing skill of giving and receiving a feedback. To me it's essential and in both ways. If there is something wrong you should look forward to know about it and encourage constructive feedback. And as well, if your bosses screencast video has low resolution and bad mic quality, you must let them know about it.
Great video, thanks!
Amazing bhai..
Actually, the first list, that you crossed off, is what companies are looking for.
Great video here!
it's both
As of learning the 80/20 rule is very important
keep rocking you are the best
very good video but I fail to memorize concepts If I spend one week without using them... how can deal with that
could you please make us some back-end videos maybe a php course . thanks!
I realize that there are different domains of programming, but knowing how to solve complex leetcode problems on the spot in an interview just feels irrelevant to most work programmers do, and doesn't necessarily speak to the quality of their code. I'd rather have a programmer who understands and communicates effectively with the people around them, understand requirements, understand the important of testable and well-documentet code etc, than someone who writes an inexplainable, seemingly efficient one-liner that's not debugable or even necessary for the product. Also, overengineered code can lead to technical debt like nothing else, for most programming languages you don't have to implement your own data structures, there are standardized libraries and internals that fix most stuff for you in an efficient way. So unless you're working on some cutting edge video rendering software or whatever, there are more than those qualities to look for in a programmer, and it's a shame to turn away great hires for irrelevant reasons.
Thanks for the content ❤❤
Unfortunately in my country, the companies required only one stuck: spring/angular and only that 😢😢
That is not that unfortunate! Just get those down and you'll have endless opportunities!
What a great video 🔥
I'm just starting to learn how to code, learning Javascript right now, what you said about not learning everything all at once, would you recommend beginners do that? or is this something that is just for experienced programmers?
Thanks
Lots of quick output usually means lots of bugs.
Don't think anyone has ever said any of those 4 points except the side projects one lol
Hello Kyle I learned lot of css and js through your videos.eagerly waiting for your new updated react course to buy.but please make cheaper as I am student form india the price is too high for us to buy for us to learn please make it cheaper so we can buy use of it.and any specific date when you are going to launch your react course?
Hey kayle first of all sorry if i am not spelling your name correctly. Can you make a video like what is testing and how it happens in a industry because many times when i apply for job i see in the description that bug free code okay i do test my code on the browser if i am building a web app but what about mobile app or anything else so can you clear this concept please ad you have experience and you've worked in industries as well because i don't understand that write scripts write tests for your code but question arise like where to write and what technologies.
I couldn't find my answers on entire web please make a video on this topic it will be appreciated and a great help as soon as possible. Thank you ❤
"Great developers" work for themselves and not for someone else.
Typing speed is not important at all. You misleadinng people by even mentioning it.
Hey cool guitar
>No one is building large projects on their own
👀
Hey Kyle what is your say for OpenAi
I always think that side projects are important.
It shows that the person is working with what he/she finds interesting. If that is the case they will be self driven and usually write better code.
A lot of people that I interview have the "oh I learned to code because I need a job" attitude.
They think they know how to code but they don't.. They piggybacked someone else in a larger project or something similar.
I think side projects are a nice signal, but I don't think they're mandatory for someone to be successful as a developer. I am not talking about course homework projects at uni/bootcamp, but more about passion/toy projects at home.
Many people don't want to continue staring at a screen after 8 hours of working at the job and might have other interests they want to devote their limited free time to, but that doesn't mean they're incompetent at their job. So side projects can be a plus, but not a clear measurement of a dev's capabilities at the work place.
No hate but the photo of you smiling in the thumbnail reminds me of "Hide the Pain Harold"
Not too non pick, maintainable
Actually, good programming is all about soft skills...
All agree with y
any one here can help me with getting a remote job ?
hey man, this may sound weird but are you guys hiring in your company? haha
im okey with all of that but, communication ?! i became coder to avoid that in fact because i hate ppl
Hello 👋
Agreed . 100%. Its not all IQ. If you can't even communicate properly or visualize your ideas to explain it to non-tech professionals you're not very useful. They want people who can explain and simplify complex techincal problems for them so that they can focus more on their core business instead of spending hours after hours debugging this new state of the art tech.
Do you share the pessimistic opinions about coding becoming obsolete in 20 years or you share the opinions of many that say that with the advancement of ai the software engineering jobs will bloom even more due to the increasing demand for more complex applications
it will make it easier to a point that a project requiring 20 people will require 2
Be willing to work for less. And do as you're told.
Hello,
Yes, I agree strongly, but is it TRUE about HIRING? Who of the managers or recruiters will hire you based on these conditions? I am sad to say this but close to NONE! The things you are talking about are hard to rely on, because these are not accepted as hard facts about a person.
You have to trust someone that even though they do not have high code knowledge they write quality code, precise, but at relatively slow rate, which for solving hard problems is the most important. High code knowledge (knowing every single command stuffed in your mind) does not help you that much when inventing the solution, because solving time can last form 1h to 100h. It mostly depend on how programmer thinks. How fast he accepts and solves new things. But as I said this is not hard fact.
HARD FACT when hiring is IN YEARS are you doing the same thing all over again, and HOW MUCH CODE do you have stuffed into your mind. This is unfortunately so wrong in programming in 21. century, especially after the latest acceleration. But what to do, it is how it is, and we have to deal with it...
Bro enough about programming. Show us about your guitar skills one day.
You have nice hair
If you want to learn how to learn, go to university, become at least an engineer or if you want to continue M. A. then if you still want to continue become a Ph. D. Anyway studies will learn you how to learn effociently - at least, of course it depends on you. Why? Well studies forces you to learn a lot of material in a short amount of time. Are there people who achieved tnie in their own? Yes, but rarely. Most people are lazy by default.
Man, it's absolutely FALSE information.
Most of the companies are trying to make wastes on personal as low as possible. Not only IT companies, but all around the world. Only probably few of them care about quality, communication and learning. Tell this joke to the fired seniors with massive and experienced background, substituted by 10 cheapest one core brain developers
test
2:35 uh oh...typo
AI taking our jobs is imminent, yet we're still discussing how to enhance our employability.
😢😮😮😮
Do you also have to be hot? Or that only works if you wanna get 1,25M RUclips subscribers?
Managed to fail miserably in My Internship with all 3 Qualities, time to take the Buckshot in chest
I would never hire you
Why
Your arguments were substantial 😂
Thanks