Looks like Senior StackOverflow Developer is not a joke after all. As StackOverflow themselves confirms, one of every four visitors copies a piece of code off the website, within 5 minutes of their visit. During mere two weeks between March and April this year, there were over 40 million CTRL+C keystrokes recorded on StackOverflow.
We all see this happening all the time. But the scale of this phenomenon is, quite frankly, shocking. Availability of this vast trove of free code snippets is too often seen as an excuse to no longer learn things for yourself.
While copying a code snippet off StackOverflow isn’t bad in itself, it’s rarely followed by genuine effort to actually understand, how the snippet works. Whether it’s a good way to go. Whether there are better alternatives. Whether the code is safe and secure. And the ultimate question: what is lacking in my knowledge, that I again found myself recycling someone else’s code?
Well why? If it works, it must be all fine! Next ticket please, team metrics up, big success!
Two concerns come to mind here:
- QA teams: brace for impact, this is getting worse by each year!
- Senior StackOverflow Developers: beware. It is precisely this kind of “work” that’s easiest to automate by machine learning. I can see drastic career changes coming for many ;-)
Author Tomasz Waraksa
© Tomasz Waraksa, letsdebug.it
This article is not promoting any of the described products, services or vendors. We don't have any commercial interest nor associations with them. We're not trying to suggest that these products or services are best for you, nor promising that your experience will be the same.
In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website and any information presented on it.
Through this website you are able to link to other websites which are not under our control. We have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them.
Permission is hereby granted, free of charge, to any person obtaining a copy of software published on this website and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions, unless stated explicitly otherwise:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
The software is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.