I'm 5 months in my first coding(MEAN stack) job. My client wanted to create a comment section similar to youtube or twitter with mentions but with single nesting and also able to add an attachment to the comment. I thought I wouldn't be able to do this feature on my own as a fresher but I broke it down into simpler problems and found a solution to those problems. I'm so proud of myself right now. A few months ago, I didn't have the confidence to code but with the help of UA-camrs like you, I was able to build my confidence to give interviews and also my colleagues that mentor and guide me. If you are someone who is new to coding or having any issues, I would suggest just starting coding, follow the tutorial to the teeth but make sure you type it yourself and try to make changes and try to figure out why the code is working or not. Eventually you will get to a point where you will be able to code or at least think what steps I need to plan out to solve a problem. Eat Sleep Code Repeat!
I've recently begun learning web development, and instead of going down traditional tutorial hell, I decided to take a more project-based approach, which started with me following along other's project tutorials. This video has reminded me to specify within my git repositories which projects are from others as to not accidently claim someone else's code as my own. Thank you!
Copying is a thing, copying AND making it yours by integrating, adding or changing parts is totally different. Thanks for pointing it out and raising awareness on this topic! :) On my channel I posted the usual "Tutorial Hell" video but this is a nice addition, I might mention it in one of my future content.
Whenever I do some projects I would try my own ideas or ideas learnt from other projects and mix them up, sometimes I totally rewrite the thing. If you copy other people's solutions and claim them to be your own, it is wrong. I follow online tutorials like this to learn the logic behind the solution. Actually I've learnt more from your videos than from school! Thanks Kyle!
That library part was actually a good example. The reason for libraries is not to reinvent the wheel, and that literally means taking someone else's code.
Your code is immaculate and I've used several blocks which I've customized to my needs and for that I'm ever so grateful. Thankyou so much for all your contributions. )))
Personally, my process was: write the code following line by line the tutorial (trying to understand why each part of the code is there) on the first try don't try anything new until you understand the methods and the data flow > then try to do it again the same protect trying to remember the parts if you don't remember a methods, functions. classes is ok to try using the documentation of the language that you are using (this is going to help you to get a deeper understanding of the method that you want to use) or StackOverflow, if you get completely blocked get back to the code that you did the first time if you can't figure out by that point get back to the video > third time try to add something new or adapt it to other uses (example I did a To Do List and then adapt it to a make my own bookstore reservation system). Don't catch up with just having stuff in your portfolio is going to be useless in the technical interview, your portfolio & projects is only going to open the first door but is not going to keep it open if you don't know how you did it, the important part of building a project is that you learn what is doing and how.
I want to thank you a lot, I learned css and JavaScript from your awesome tutorials. 💚💚 And used that experience to build very simple snake game, but it was first app ever to build from zero without watching any tutorial.
I do small bits of web dev as a hobby. Nearly every bit of code I've done is based on what others have written. Whether I got it by looking at the underlying code on a web page, tutorials on youtube, stack overflow or a host of other sources as you said I had to effectively dismantle it and then put it back together again to work the way I wanted/needed. This process leads to me having a better understanding of exactly how things work which then means I'm more able to consider them for possible future uses. When ever I can I always try to give credit to the person whose code mine is based on as I feel that is not only the right thing to do but anyone looking at my code in the future may want to have a look at where I got my inspiration from.
The voice of reason, thanks for all you do and god bless you for making code so clearly more understandable !! (please never stop, i learn a lot from you)
Yes, That is the great point 🤙 I also go to Google or UA-cam to check the solution from different thoughts and then let my self ready to implement it according to my requirements and modify all the things.
Copying someone is a good skill to have. It's something you should start doing as a beginner if you ain't doing that already. You'll be amazed at how good you'd become over time. Just DON'T COPY-PASTE anyone's code! Write it, line by line. Yes, line by line! Modify it, break it, fix it. Now you're a developer. Congrats 👏
I honestly try my best to learn after copying then editing it to my liking or to the best it can be, otherwise if its straightforward Ill just copy n paste everything
I'd say, to copy code, one should chop pieces off in a few ways to warm up. I'd draw the line where the understanding of copied code is about twice as absolutely necessary for using it in the project. That's both for reusing the code in the future in a different scenario, and for turning functionalities off for the sake of debugging. Thought, I'm not experienced, I might change my mind. And most people don't seem to care.
I actually just finished that Reddit-comment-clone tutorial. I got stuck for like 3 days trying to figure out what killed my DOM while I was still getting the data .... and that debugging process really helped me learn the logic-flow. Never worked with a backend before so now I'm watching all the videos I can on Express/Fastify and Prisma.
I downloaded your node express rest api the other day from your github repo and optimized it a lil bit where i made it look like an MVC pattern (except for the V). I am currently learning node express right now to add a skill to my resume as a dev
I was always under the impression that I have to be able to make something from scratch if I want to use some sort of library/framework because using it without the ability to make it makes me some sort of a liar (impostor syndrome-ish). Currently I'm in a situation at work where I slowed down a production, because I took over someone else's project and didn't make any meaningful progress because I felt like I need to learn all the code and understand it perfectly before doing anything. So yeah, stealing code is bad, but trying to reinvent the wheel might sometimes be even worse.
I'm currently studying towards becoming a full stack developer and the class mates that are most stressed are those that think they need to understand every piece before they start to build something. I start in the other end, find code that solve the same problem (ish) as mine, implement it and after a while I will understand what every single line does.
I needed to hear that. I'm definitely the type of stressed people you described, because I hate being restricted, or feeling stuck when there's a problem. But what I end up doing as I move on with a project is to understand less, anyway. I still have a slither of hope that more technical positions like dev ops will be more satisfying for me. Than this annoyance.
@@betterbehappythannot3605 also what i like to do is take some working code i'm trying to understand and deconstruct it to see what every line or command does
@@focusiam2027 Agree 100%, example is making register and login on node js express, when you do it in every app, it gets annoying after the 30th time :D its 90% the same code, just the auth method may add some different things but you get me.
Even when we started learning how to write when we were kid, we all had to shadow the writing of someone else to learn how to write. Then we dveloped our own style or hand writing. And today we say that it's my handwriting ❤️✋
People that are against copying clearly don't realize that everything revolving software development is using tools, app, and libraries that are already built by someone else. There is no limit when you think about the scope of how much us developers take advantage of instead of building from scratch. What can we truly consider scratch? As a long time developer I am constantly looking up solutions and code. What really matters is the end results and how things are implemented. Productivity is extremely important when it comes to projects. Also GitHub Copilot is a great example of just using pre-built code and improves my productivity massively.
So I love your videos. Probably the best on youtube. ...but... :D I *hated* the variable names you used in your custom select component video - I found it *so* confusing. So I ripped it apart, built it again whilst looking at your code. I can now build that, and other custom input elements. Having to understand someone else's solution and work with it is the best way to learn, so thanks!
Hey man, i love your videos :). Youve inspired me to start learning new things again even though im already working professionally for years! Say what mic do you use? I want to try to learn by teaching by doing some own videos and im looking for a mic like yours. Hope youre having a great day!
we all copy code, not necessarily for resume considerations, but definitely for project scenarios. In fact, no-one should copy code and claim the knowledge for a resume.
I mentioned that while making a sound over on my upcoming video. Like seriously if i am starting out where the hell should i get an idea to code? If you’re following the tut and coding along with it it’s your code.
I would like to have the opportunity to thank you for creating such crisp and fine content and I see this as your USP. Maybe someday I could do the same. An Idol to me!!! :)
I think copying code is the best way to learn how to program new things- as long you're actively trying to LEARN what it is you're doing. I like to talk step-by-step through each element of my code so I can make videos on complex topics like AI that people can hopefully learn from. I wish people would copy my code 😅
Great content as well. Other than that, I just got into the electric guitar. Being a total beginner, do you have any resources and videos you can recommend, lol.
Justin guitar is quite good on UA-cam. It depends a lot on the music you are into as well. I follow quite a few metal guitar teachers as that is what I like to play.
I think that these kind of videos are more like a general idea how to pull something off, or get an idea. I watched a lot of videos from Online Tutorials but I never ever used THEIR code. I usually find something I like or something that looks like something I like, and then I reimplement it my way, or even combine multiple ideas. I suck at designing frontend : (
If you follow a recipe, does that mean you didn't bake the pie? As long as your replication is part of the act of learning a new skill, understanding, adapting and executing code to accomplish your goal, then it is OK to do.
I tried to reuse your code from "perfect project for your resume" video, but it didn't work the way I expected because it relies on React and I couldn't use this dependency and the list of items may be too huge (200 !) to make it convenient to use I recoded it from scratch in pure HTML5 and web component : i encountered many pitfalls but managed to do something quite nice. The result is an input web component with an hidden input (sharing the same name attribute), a div and a tiny input field. When this tiny input value match the "pattern" attribute, the input value is added in the div as an empty anchor link, the hidden input value is computed and the visible input become empty. Activating any link under the div removes itself from the document then recompute the hidden input value. The hidden input value is a comma separated list of entries: it is generated from the text of all the links in the div. The tiny input is greyed out if the list is full, preventing the user to add any new item. The list is full if the maximum length of the hidden input field is below the length of its value + maximum length of the tiny input field. As an exemple the user can easily type any combination of AA to ZZ, automatically stored in a comma separated list as he types it, until he reaches a limit of 90 characters (separator included ! So 90/3 = 30 entries). He can easily remove any entry by clicking on it. I used it as part of a professional project, but I will refine the code a bit and post it to GitHub this weekend.
Copying code makes a lot of sense if you know how to write the code but choose not to because it would save time to build on someone else's work. It's like instead of starting to build a car by building a chassis, a builder just finds a chassis that's already made and modifies it.
It's all just bias towards beginner developers. If you're an aspiring developer trying to land a job, everyone is pedantic about every single line of code you've ever written. However, once you've landed a job, everyone blindly trusts your abilities. You see this in HR, colleagues and acquaintances who know how to code. This is the same phenomenon driviing people to believe that senior developers are superior developers merely because a company gave them that title. Nobody verifies their skill against someone else's. In conclusion, the only thing that matters is if you understand the code you see in your codebase, are able to solve problems in your codebase and are able to improve over time. You're paid to meet the business needs of your employer, not to win a race with other devs on who's best according to a bunch of guys in forum.
I like learn programing watching video tutorial than read documentation. I just don't know how to use eg.function in documentation, after i watch tutorial, i just understand what documentation mean. Maybe my native language is not english, that's why indon't get it. When watching video, i feel have mentor for what i should to do. Sorry for my bad english. I just want comment on every video youtube for practicing how write in english 😁
Over 99.9% of juniors copy & past code then never ever do the effort of deeply understand it or change it a little bit. But... They keep call them self as "developers".
Isn't it normal to copy other code? If I start a project I copy from a lot of code patterns because I can't remember them on my own. For instance if I implement a state pattern in a game I copy the basic structure with some sample classes from other people and then I modify it so that it suits my needs.
Never copy paste. Always type it and explore how it works by making changes. If you don't understand how the code works, you are going to fail at your job.
This. I was going to say pretty much the same thing but basically: // sometimes this assures people I agree with not copying but it can be a little buggy- will need to see what’s causing errors for the next update but it works okay for now. Jeremy Bolonos 8 hours ago. Never copy paste. And always type it and explore how it works by making changes. If you don’t understand how the code works, you are going to fail at your job. Jeremy Bolonos 8 hours ago. Never copy paste. And always type it and explore how it works by making changes. If you don’t understand how the code works, you are going to fail at your job.
@@rosscarnegie393 I taught myself programming in the 90s and now I'm a Sr Software Engineer without any formal programming classes (get my first degree in Dec 🍾). I taught myself by copying other people's work and making it work for me. I find commenting the crap out of helps. I use //- to make sure it's my comment.
copying code should be like making a smoothy, you grab a banana that's already out there, you grab a strawberry that is also out there and mix it together. anyways I'm going to McDonalds to get a strawberry banana smoothie have a nice day!
Those that say they never copy code are full of s***. I mean -> bootstrap & tailwind. I rest my case. All that is, is code copying with less steps. Now put down your rocks and go code something awesome.
You are greatly giving big motivation to the beginner intermediate developers
I'm 5 months in my first coding(MEAN stack) job. My client wanted to create a comment section similar to youtube or twitter with mentions but with single nesting and also able to add an attachment to the comment.
I thought I wouldn't be able to do this feature on my own as a fresher but I broke it down into simpler problems and found a solution to those problems.
I'm so proud of myself right now. A few months ago, I didn't have the confidence to code but with the help of UA-camrs like you, I was able to build my confidence to give interviews and also my colleagues that mentor and guide me.
If you are someone who is new to coding or having any issues, I would suggest just starting coding, follow the tutorial to the teeth but make sure you type it yourself and try to make changes and try to figure out why the code is working or not. Eventually you will get to a point where you will be able to code or at least think what steps I need to plan out to solve a problem. Eat Sleep Code Repeat!
where is hit the gym?
I've recently begun learning web development, and instead of going down traditional tutorial hell, I decided to take a more project-based approach, which started with me following along other's project tutorials. This video has reminded me to specify within my git repositories which projects are from others as to not accidently claim someone else's code as my own. Thank you!
Copying is a thing, copying AND making it yours by integrating, adding or changing parts is totally different.
Thanks for pointing it out and raising awareness on this topic! :)
On my channel I posted the usual "Tutorial Hell" video but this is a nice addition, I might mention it in one of my future content.
Whenever I do some projects I would try my own ideas or ideas learnt from other projects and mix them up, sometimes I totally rewrite the thing. If you copy other people's solutions and claim them to be your own, it is wrong. I follow online tutorials like this to learn the logic behind the solution. Actually I've learnt more from your videos than from school! Thanks Kyle!
That library part was actually a good example. The reason for libraries is not to reinvent the wheel, and that literally means taking someone else's code.
Your code is immaculate and I've used several blocks which I've customized to my needs and for that I'm ever so grateful. Thankyou so much for all your contributions. )))
Great topic. I became a subscriber after finding your channel by reverse searching an applicant's code submission for a senior developer position.
For a senior developer position... damn haha. Good for you though.
Dont be bad with yourself you’ve helped so much people ;) best ❤
Personally, my process was: write the code following line by line the tutorial (trying to understand why each part of the code is there) on the first try don't try anything new until you understand the methods and the data flow > then try to do it again the same protect trying to remember the parts if you don't remember a methods, functions. classes is ok to try using the documentation of the language that you are using (this is going to help you to get a deeper understanding of the method that you want to use) or StackOverflow, if you get completely blocked get back to the code that you did the first time if you can't figure out by that point get back to the video > third time try to add something new or adapt it to other uses (example I did a To Do List and then adapt it to a make my own bookstore reservation system). Don't catch up with just having stuff in your portfolio is going to be useless in the technical interview, your portfolio & projects is only going to open the first door but is not going to keep it open if you don't know how you did it, the important part of building a project is that you learn what is doing and how.
But i will !
Зачем, братиш?
Change my mind😂😂😂👌
😂
You are first
Normal
I Needed to hear this I think many folks need to hear this
I want to thank you a lot, I learned css and JavaScript from your awesome tutorials. 💚💚
And used that experience to build very simple snake game, but it was first app ever to build from zero without watching any tutorial.
I do small bits of web dev as a hobby. Nearly every bit of code I've done is based on what others have written. Whether I got it by looking at the underlying code on a web page, tutorials on youtube, stack overflow or a host of other sources as you said I had to effectively dismantle it and then put it back together again to work the way I wanted/needed. This process leads to me having a better understanding of exactly how things work which then means I'm more able to consider them for possible future uses.
When ever I can I always try to give credit to the person whose code mine is based on as I feel that is not only the right thing to do but anyone looking at my code in the future may want to have a look at where I got my inspiration from.
The voice of reason, thanks for all you do and god bless you for making code so clearly more understandable !! (please never stop, i learn a lot from you)
Yes, That is the great point 🤙 I also go to Google or UA-cam to check the solution from different thoughts and then let my self ready to implement it according to my requirements and modify all the things.
Copying someone is a good skill to have. It's something you should start doing as a beginner if you ain't doing that already. You'll be amazed at how good you'd become over time. Just DON'T COPY-PASTE anyone's code! Write it, line by line. Yes, line by line! Modify it, break it, fix it. Now you're a developer. Congrats 👏
completely right, I love to edit your code to fit my needs,thanks...
I honestly try my best to learn after copying then editing it to my liking or to the best it can be, otherwise if its straightforward Ill just copy n paste everything
100% agreed. That modification where you actually "learn" coding!
thank you for making video like this , a lot of your viewers are in tutorial heel
I'd say, to copy code, one should chop pieces off in a few ways to warm up.
I'd draw the line where the understanding of copied code is about twice as absolutely necessary for using it in the project.
That's both for reusing the code in the future in a different scenario, and for turning functionalities off for the sake of debugging.
Thought, I'm not experienced, I might change my mind.
And most people don't seem to care.
I actually just finished that Reddit-comment-clone tutorial. I got stuck for like 3 days trying to figure out what killed my DOM while I was still getting the data .... and that debugging process really helped me learn the logic-flow. Never worked with a backend before so now I'm watching all the videos I can on Express/Fastify and Prisma.
I downloaded your node express rest api the other day from your github repo and optimized it a lil bit where i made it look like an MVC pattern (except for the V). I am currently learning node express right now to add a skill to my resume as a dev
Thank you!! Love this perspective.
Thank you for reminding everyone that programmers are "... paid to solve problems, not write code from scratch." 🙂
Exactly..this is some great advice 😜 thank you..your support is awesome
Your videos are great. People can't pretend to code!!!!
I remember adding square ,square root ,factorial and changing operator to sime extent in your js calculator
My professor back in the early 90s once said "only good coders can copy code... successfully" ;)
You're completely correct man. Thanks for everything :)
good to know
I did not want to copy another codes
but You are right.. I use too much labrarys :)
so I will not hesitate copy another good example
I was always under the impression that I have to be able to make something from scratch if I want to use some sort of library/framework because using it without the ability to make it makes me some sort of a liar (impostor syndrome-ish).
Currently I'm in a situation at work where I slowed down a production, because I took over someone else's project and didn't make any meaningful progress because I felt like I need to learn all the code and understand it perfectly before doing anything.
So yeah, stealing code is bad, but trying to reinvent the wheel might sometimes be even worse.
I am using them as learning tools and incorporating some ideas in my own projects
I hope you're feeling better, Kyle!
100% right.
I just learn by use others code and make them better or functional the way I need.
great message Thank you Kyle
As someone, somewhere said,
Developers are paid for knowing what to copy, and where to paste it!
I would add: "and how to modify it".
Background music is super good its your own ? the voice also super good we learn a lot from you thanks a alot
I'm currently studying towards becoming a full stack developer and the class mates that are most stressed are those that think they need to understand every piece before they start to build something.
I start in the other end, find code that solve the same problem (ish) as mine, implement it and after a while I will understand what every single line does.
I needed to hear that.
I'm definitely the type of stressed people you described, because I hate being restricted, or feeling stuck when there's a problem. But what I end up doing as I move on with a project is to understand less, anyway.
I still have a slither of hope that more technical positions like dev ops will be more satisfying for me. Than this annoyance.
i dont even think it is possible to understand everything. aslong as you do understand the basics and what does what i think you should be okay.
Thank you for giving the answer immediately
i think copying code isn't a bad thing as long as you understand what the code does
It saves time if you have written that piece of functionality hundreds of times
@@betterbehappythannot3605 also what i like to do is take some working code i'm trying to understand and deconstruct it to see what every line or command does
That's what I do all the time, bad would be if you don't know what it does.
@@focusiam2027 Agree 100%, example is making register and login on node js express, when you do it in every app, it gets annoying after the 30th time :D its 90% the same code, just the auth method may add some different things but you get me.
Even when we started learning how to write when we were kid, we all had to shadow the writing of someone else to learn how to write. Then we dveloped our own style or hand writing. And today we say that it's my handwriting ❤️✋
I couldn't agree more. Well stated. ))
I love this example ✌️
@@Frames_of_Mind-1 🤙🔥
@@colindante5164 🤙🔥
l love your comment
Very good point thanks for sharing..
Great advice! Thank you!
Thanks for the video bro😊
People that are against copying clearly don't realize that everything revolving software development is using tools, app, and libraries that are already built by someone else. There is no limit when you think about the scope of how much us developers take advantage of instead of building from scratch. What can we truly consider scratch? As a long time developer I am constantly looking up solutions and code. What really matters is the end results and how things are implemented. Productivity is extremely important when it comes to projects. Also GitHub Copilot is a great example of just using pre-built code and improves my productivity massively.
So I love your videos. Probably the best on youtube. ...but... :D
I *hated* the variable names you used in your custom select component video - I found it *so* confusing. So I ripped it apart, built it again whilst looking at your code.
I can now build that, and other custom input elements. Having to understand someone else's solution and work with it is the best way to learn, so thanks!
you're back 🎉
Don't copy code! Copy strategies and logical thinking. Thank you!🤗
It gives a new perspective
Hey man, i love your videos :). Youve inspired me to start learning new things again even though im already working professionally for years! Say what mic do you use? I want to try to learn by teaching by doing some own videos and im looking for a mic like yours. Hope youre having a great day!
Thanks for everything :)
we all copy code, not necessarily for resume considerations, but definitely for project scenarios. In fact, no-one should copy code and claim the knowledge for a resume.
I mentioned that while making a sound over on my upcoming video. Like seriously if i am starting out where the hell should i get an idea to code? If you’re following the tut and coding along with it it’s your code.
Again great as always! Btw you look like Kevin de bruyne...
no your tutorials are too good , I'll keep using them 😈
I would like to have the opportunity to thank you for creating such crisp and fine content and I see this as your USP. Maybe someday I could do the same. An Idol to me!!! :)
You just called me out I just did one of your react tutorials today haha.
Thank youu infinitively
I copied your code and modified it to sort stuff to a database and integrated your two node js servers to act as one
I watched your videos just for improving my English but I ended up being a better coder.
@Web Dev Simplified What keyboard do you use?
I think copying code is the best way to learn how to program new things- as long you're actively trying to LEARN what it is you're doing. I like to talk step-by-step through each element of my code so I can make videos on complex topics like AI that people can hopefully learn from. I wish people would copy my code 😅
Great content as well. Other than that, I just got into the electric guitar. Being a total beginner, do you have any resources and videos you can recommend, lol.
Justin guitar is quite good on UA-cam. It depends a lot on the music you are into as well. I follow quite a few metal guitar teachers as that is what I like to play.
@@WebDevSimplified Thank you!! I’m a huge Arctic Monkeys fan, and I want to learn their riffs 😍
@@WebDevSimplified I also love JavaScript 😅
@@WebDevSimplified What keyboard do you use?
Thanks for this.
Ok, time to fork your whole repo
*EVIL LAUGH*
Jokes aside, stay awesome brother, your contribution to the developers community is remarkable
Thank you sir.
You help me conquer my impostor syndrome ! ! !
I think that these kind of videos are more like a general idea how to pull something off, or get an idea. I watched a lot of videos from Online Tutorials but I never ever used THEIR code. I usually find something I like or something that looks like something I like, and then I reimplement it my way, or even combine multiple ideas. I suck at designing frontend : (
I copied your infinite scroll. It was mind blow
If you follow a recipe, does that mean you didn't bake the pie? As long as your replication is part of the act of learning a new skill, understanding, adapting and executing code to accomplish your goal, then it is OK to do.
you're cool there, geetar man... :)
I tried to reuse your code from "perfect project for your resume" video, but it didn't work the way I expected because it relies on React and I couldn't use this dependency and the list of items may be too huge (200 !) to make it convenient to use
I recoded it from scratch in pure HTML5 and web component : i encountered many pitfalls but managed to do something quite nice.
The result is an input web component with an hidden input (sharing the same name attribute), a div and a tiny input field.
When this tiny input value match the "pattern" attribute, the input value is added in the div as an empty anchor link, the hidden input value is computed and the visible input become empty.
Activating any link under the div removes itself from the document then recompute the hidden input value.
The hidden input value is a comma separated list of entries: it is generated from the text of all the links in the div.
The tiny input is greyed out if the list is full, preventing the user to add any new item. The list is full if the maximum length of the hidden input field is below the length of its value + maximum length of the tiny input field.
As an exemple the user can easily type any combination of AA to ZZ, automatically stored in a comma separated list as he types it, until he reaches a limit of 90 characters (separator included ! So 90/3 = 30 entries).
He can easily remove any entry by clicking on it.
I used it as part of a professional project, but I will refine the code a bit and post it to GitHub this weekend.
Once i found code of mp3 player on plain JS. I rewrited it with TS, added some functionality and implemented 2 different variations in my own project
Copying code makes a lot of sense if you know how to write the code but choose not to because it would save time to build on someone else's work. It's like instead of starting to build a car by building a chassis, a builder just finds a chassis that's already made and modifies it.
I use it to learn, just like how I play guitar, I don't use my own song to practice.
It's all just bias towards beginner developers.
If you're an aspiring developer trying to land a job, everyone is pedantic about every single line of code you've ever written.
However, once you've landed a job, everyone blindly trusts your abilities. You see this in HR, colleagues and acquaintances who know how to code. This is the same phenomenon driviing people to believe that senior developers are superior developers merely because a company gave them that title. Nobody verifies their skill against someone else's.
In conclusion, the only thing that matters is if you understand the code you see in your codebase, are able to solve problems in your codebase and are able to improve over time. You're paid to meet the business needs of your employer, not to win a race with other devs on who's best according to a bunch of guys in forum.
This is a good word.
nice guitar. what is brand?
The best way to copy you is copy your code programming concept learn about it and rather than copy your code we can have our own original code
I like learn programing watching video tutorial than read documentation. I just don't know how to use eg.function in documentation, after i watch tutorial, i just understand what documentation mean. Maybe my native language is not english, that's why indon't get it. When watching video, i feel have mentor for what i should to do. Sorry for my bad english. I just want comment on every video youtube for practicing how write in english 😁
Over 99.9% of juniors copy & past code then never ever do the effort of deeply understand it or change it a little bit. But... They keep call them self as "developers".
Isn't it normal to copy other code? If I start a project I copy from a lot of code patterns because I can't remember them on my own.
For instance if I implement a state pattern in a game I copy the basic structure with some sample classes from other people and then I modify it so that it suits my needs.
if it wasnt, stackoverflow wouldn't be as succesfull as it is these days. Its not normal to copy whole projects tho ofcourse
Never copy paste. Always type it and explore how it works by making changes. If you don't understand how the code works, you are going to fail at your job.
This. I was going to say pretty much the same thing but basically:
// sometimes this assures people I agree with not copying but it can be a little buggy- will need to see what’s causing errors for the next update but it works okay for now.
Jeremy Bolonos 8 hours ago.
Never copy paste. And always type it and explore how it works by making changes. If you don’t understand how the code works, you are going to fail at your job. Jeremy Bolonos 8 hours ago. Never copy paste. And always type it and explore how it works by making changes. If you don’t understand how the code works, you are going to fail at your job.
@@rosscarnegie393 I taught myself programming in the 90s and now I'm a Sr Software Engineer without any formal programming classes (get my first degree in Dec 🍾). I taught myself by copying other people's work and making it work for me. I find commenting the crap out of helps. I use //- to make sure it's my comment.
That’s how everything everything evolve
Well said
Interesting question: if i copied code chunks from 2 or more projects, combined them, deleted unnecessary parts and added new stuff is it ok?
Don't mind if I do, *yoink*
I agree
can someone tell me how to make shorts where I can show my browser and code in the same time I find it really very difficult
My view is you can copy any code you understand.. if you dont understand it then copying is a bad idea..
copying code should be like making a smoothy, you grab a banana that's already out there, you grab a strawberry that is also out there and mix it together.
anyways I'm going to McDonalds to get a strawberry banana smoothie have a nice day!
Facts
can you also teach us sth about hairstyle
I don't copy code... I have Github co-pilot to do it for me.
using it as a total template. since not sure where to type the right codes.
Those that say they never copy code are full of s***.
I mean -> bootstrap & tailwind. I rest my case. All that is, is code copying with less steps.
Now put down your rocks and go code something awesome.
Que es copy co
De en español
1:14 Ain't no way bruh 💀 who did this?
Okie