I was partnered with that guy for one class in grad school. We were working on a master’s degree in software engineering, and the assignment was analysis and changes to an actual code base, and this mofo was asking questions and/or blanking on things like what you mention. I can’t remember the specifics but it was some basic building block kind of stuff. Like what’s an array, or what’s a function, or how do we send another number into this function. I think the neurons storing that info got pruned to save me the frustrating memories.
I just remember my internal emotional reaction. It was sort of “are you fucking kidding me” but not in the sense that somebody blew off the assignment, was rude, or was wrong about some basic fact. I have ADHD and years ago I went through some pretty bad periods with that and overall mental & physical health. I know the panic of being asked to turn in an assignment you never knew existed, or being asked about some project at work and just have no idea whatsoever how to respond.
This was none of those. This was “holy shit, this guy has never done anything, how did he even end up here?”
Well, computer science is not the science of computers, is it? It’s about using computers (in the sense of programming them), not about making computers. Making computers is electrical engineering.
We all know how great we IT people are at naming things ;)
It wasn’t named by IT people, though. It was named by academics. And it’s not about using computers, it’s about computing. Computer science is older than digital electronics.
Mhm, and those academics were no IT people and had nothing to do with computers?
Let’s fact-check that.
Computer Sciences as an academic course was first created by IBM at the Columbia University in 1946. Because IBM had made their first commercial computer two years prior and wanted to have people who could operate it and who could continue to develop it.
Had a graduate Dev who did not have a fucking clue about anything computer related. How tf he passed his degree I have no idea.
Basic programming principles? No clue. Data structures? Nope.
We were once having a discussion about the limitations of transistors and dude’s like “what’s a transistor?” ~_~#
I’ve met people like that too.
It’s called cheating, lots of people do it.
Most worthless dev I’ve met was a graduate of comp sci who couldn’t hold a candle compared to a guy that did a dev boot camp.
The best dev I’ve met so far didn’t even have any credentials whatsoever, second next best did 2yr associates.
Tie for 3rd best with associate’s and 4yr degree.
I was partnered with that guy for one class in grad school. We were working on a master’s degree in software engineering, and the assignment was analysis and changes to an actual code base, and this mofo was asking questions and/or blanking on things like what you mention. I can’t remember the specifics but it was some basic building block kind of stuff. Like what’s an array, or what’s a function, or how do we send another number into this function. I think the neurons storing that info got pruned to save me the frustrating memories.
I just remember my internal emotional reaction. It was sort of “are you fucking kidding me” but not in the sense that somebody blew off the assignment, was rude, or was wrong about some basic fact. I have ADHD and years ago I went through some pretty bad periods with that and overall mental & physical health. I know the panic of being asked to turn in an assignment you never knew existed, or being asked about some project at work and just have no idea whatsoever how to respond.
This was none of those. This was “holy shit, this guy has never done anything, how did he even end up here?”
Tbh, as a dev knowledge of transistors is about as essential as knowledge about screws for a car driver.
It’s common knowledge and in general maybe a little shameful to not know, but it’s really not in any way relevant for the task at hand.
Maybe for dev knowledge, but computer science? The science of computers?
Well, computer science is not the science of computers, is it? It’s about using computers (in the sense of programming them), not about making computers. Making computers is electrical engineering.
We all know how great we IT people are at naming things ;)
It wasn’t named by IT people, though. It was named by academics. And it’s not about using computers, it’s about computing. Computer science is older than digital electronics.
Mhm, and those academics were no IT people and had nothing to do with computers?
Let’s fact-check that.
Computer Sciences as an academic course was first created by IBM at the Columbia University in 1946. Because IBM had made their first commercial computer two years prior and wanted to have people who could operate it and who could continue to develop it.