It is honestly impossible to imagine copy-pasting code and getting it to work without knowing what you're doing.
I had an acquaintance at uni who got a job at a software company by taking credit for a friend's work and basically being the hack & fraud that the person in this post thinks they are - although I didn't realise this at the time. He asked me to help him write some code that was needed for a presentation the next day. I decided to try to help, and I took a look.
It was a bug that required a little epsilon value to be tolerant of small changes in input in order to not constantly fire. I wrote that tiny bit of code and gave it back to him. Then he told me it wasn't working and could I look at it again. I did, and there were two epsilon values with different names in it. I asked him about that and he said he had gotten help from another friend.
He had literally attempted to merge our two functions that did the same thing into one grotesque chimeric piece of code that would only have worked if he had accidentally made one or the other of our snippets inoperative. This was like a 20 line function. It was basic, easy shit. The guy didn't know anything.
I didn't explain this. I told him I couldn't keep troubleshooting this for him and left him to it. To my understanding he was fired and cost that company a lot of money. But really if they couldn't figure out that the programmer they hired couldn't actually program then it's really hard to feel that sorry for them. It seemed like everyone was flying by the seat of their pants.
I think you could definitely read and bugfix code without ever learning to "write" code. Code intentionally reads kind of like a language, it's possible that this guy was just doing very simple tasks and the most he would have to change are variable names and values. Maybe he knows how to fix errors reported by the code and knows how to look for variables.
It's a fine line between that and knowing how to code, but that's kinda the joke of this post I guess.
I believe so. I have some roles in my team I'm hiring for, that have reading code and fixing small bugs as one of the requirements, but not developing code from scratch. (It's a sort-of field engineering role).
We do test for both things (treating the "developing code from scratch" as bonus points rather than a strict pass/fail) and some people can find and fix bugs in a couple minutes, but are incapable of writing some basic python to iterate through prime numbers and store them in an array.
You have been in this council for 9 years and we will grant you the rank of master.
*copy and paste you the rank
As long as you know what you need to be googling, you've got about ten times the programming knowledge that your company's CEO probably has.
Yeah I'm just a gamer and learned about pc just to make my games work but that's how I became so good at googling. Never learned how java works but I sure can find which arguments to set on my launcher to make my modded Minecraft run better.
As a half-joking response to this half-joking admission, I got started with the Usborne programming books as a kid, and they laid some excellent foundations for my later study. They're all available online for free these days, so grab an emulator and user manual for your 80s 8-bit home computer of choice, and dive in!
Modern programming languages and IDE's are so complex it's enough to put a lot of people off ever learning to program - it seems such a massive learning curve. There's something to be said for learning Basic then assembly on an 8-bit computer, where everything is so much sampler and direct. Writing a value to memory and seeing a blotch of pixels change on the screen gives such a direct understanding of what's going on inside the machine. And if you only have 48k of memory, you can genuinely understand everything the computer is doing.
Me too, buddy. Me too.
Obviously... use an LLM that does that for you and magically removes those sticky legal/plagiarism issues. /sarcasm
