Table of Contents
Why should I hire a software engineer if I can just copy and paste from Stack Overflow?
You should hire a software engineer because you obviously don’t know anything at all about how software is developed, and you need to hire someone who does. To convince yourself of this, think about how you might implement the Amazon.com website out of stuff patched together from StackOverflow queries.
Do programmers just copy and paste?
Most programmers do it, but that doesn’t mean you should One of my programming mantras is: “If I am copying and pasting code, I am doing something wrong”.
Is copying code a good way to learn?
Typing code instead of copy-pasting it provides a better learning ROI because we’re practicing instead of just reading. When we copy code without understanding it, we run the risk of breaking something by overwriting variable names, function names, or classes.
Why I should be hired as a software engineer?
Another reason a software engineering career is a great choice is because the field is so broad and encompasses a variety of roles related to both computer applications and systems. You can also work in most any industry because they all use software to some extent.
Is it okay for programmers to cut and paste code?
Most programmers cut and paste code in this capacity. They might find a previous project or something online and copy/paste it exactly or copy/paste and make changes to it. I think this practice is typically fine.
Is it bad to copy and paste from a past project?
(Examples: Some sort of utility object from a past project that worked well, or possibly from a blog with few changes needed). Where this can be bad, is when you are copying code that you don’t understand, or where the code is poor, or where there is a much better alternative solution than the code that you are pasting.
Can I copy and paste code straight into my own work?
The idea of copying and pasting code straight into my own work seems alien. If nothing else, it would at least need to be refactored to use my variable naming conventions or put into a class or method or something instead of being bare code.
Should I repeat work I’ve done in the past?
IE, don’t repeat work you’ve already done in the past. If you have taken the time to write a section of code, debug, test it, and it’s proven to work in a production codebase; you’d be dumb not to re-use it.