This is a bad habit. Unless it's something really basic, like boilerplate HTML or filler text, copying code robs you of deliberate practice of constructing logic from scratch, and the process of taking the steps of solving a problem.
But...
I think it's ok from time to time provided that you take the time to learn and deeply understand what the copied code is doing. The last thing you want to do as a developer is pick up habits that erode your ability to work through a problem step by step, especially when it's difficult.
Writing a code without understanding what it does is not something that I can let my self do it , the point is that we often found a task in a project that has nothing new to us , for example BREAD operations , if a developer tooks too much time making it , it won't be so benefit .
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a bad habit. Unless it's something really basic, like boilerplate HTML or filler text, copying code robs you of deliberate practice of constructing logic from scratch, and the process of taking the steps of solving a problem.
But...
I think it's ok from time to time provided that you take the time to learn and deeply understand what the copied code is doing. The last thing you want to do as a developer is pick up habits that erode your ability to work through a problem step by step, especially when it's difficult.
Writing a code without understanding what it does is not something that I can let my self do it , the point is that we often found a task in a project that has nothing new to us , for example BREAD operations , if a developer tooks too much time making it , it won't be so benefit .