As I've had the opportunity to interview developers for various positions over the years, I've noticed there are two distinct types of "programmers". Those that can actually program from scratch in an IDE/editor (or on a white board as we ask them to do in interviews), and those that can Google and press Ctrl-C, Ctrl-V very effectively.
With the explosion of Q&A sites focusing on providing quick and ready to copy and paste answers and code, the Copy & Paste Programmer is alive and well.
Unfortunately for the first group of developers who can actually write code and don't spend all their days trying to make someone elses code work, the Copy & Paste Programmer has created quite a problem. Taking away jobs, perpetuating a culture of unmaintanable, and undocumented code that the Copy & Paste Programmer never understood to begin with.
At Dream.In.Code, we're often criticized for asking members to put forth a little effort and try to actually learn a little and understand what it is they are doing. This is apparently too much to ask for the countless lazy students and young professionals that would rather be handed 100 lines of code they can pass off as their own than spend a few extra minutes learning how to actually solve a problem. What's sad is, this used to be limited to academic settings, but as those individuals graduate and enter the work force, we're seeing more and more questions from "professionals" who need someone to write their code for them. This is disgusting, and it's being supported by other programmers who will gladly do their work for them.
While there is nothing wrong with doing some research and finding a snippet or two to help you complete an application, if you find yourself assembling programs entirely from code copied from forums, Q&A sites, etc. You are a Copy & Paste Programmer and you are not only hurting yourself, but you're hurting your entire industry.
Dream.In.Code does not and will not support a culture in which programmers can not write code from scratch or complete basic troubleshooting and debugging. This is why we encourage discussion, learning, and a good faith effort from everyone receiving help. It may not be the easy or popular thing to do, but for those genuinely interested in having a successful career as a programmer, it's the right thing to do.
No comments:
Post a Comment