> Source control is not in the domain of computer science.
Yep. Its not.
And the fact that modern day computer science institutions do not teach it, is a huge failing on the part of these programs, and is something that they should be strongly criticized for.
People go in to CS programs, believing that they are going to be taught basic skills like that, and they are tricked by these unstated lies.
But, if we really want to keep with this "cs"/software engineer distinction, then fine. Lets stop lying to students, and lets, as a society, attempt to convince people to go into software engineering more, because that is what most of these students actually want.
And lets relegate "computer science" to a much less prestigious, and much more "esoteric" field of study, that is looked down upon, in comparison to what students actually want, which is to learn software engineering.
But, unfortunately, modern day "computer science" is currently held up as the "prestigious" field of study, when it actually does not deserve that prestige. It deserves the ridicule, that modern day academics currently put on "software engineering" or "information systems", that are currently looked down upon as the fields of study that people go into, if they can't hack it in CS.
> we apply the concepts that we learn from CS in our jobs.
> that data might be useless by the time you graduate.
I am not sure where this myth comes from, that software engineering is just about some specific language, or tool.
Learning about the "concepts" of source control, or documentation, or working with a team, or writing readable code, or designing good APIs, are things that have little to do with CS, but goes beyond just "learn this specific tool".
Algorithms, and math, while can sometimes be useful, are still only one very small part of what it means to be a software engineer.
Yep. Its not.
And the fact that modern day computer science institutions do not teach it, is a huge failing on the part of these programs, and is something that they should be strongly criticized for.
People go in to CS programs, believing that they are going to be taught basic skills like that, and they are tricked by these unstated lies.
But, if we really want to keep with this "cs"/software engineer distinction, then fine. Lets stop lying to students, and lets, as a society, attempt to convince people to go into software engineering more, because that is what most of these students actually want.
And lets relegate "computer science" to a much less prestigious, and much more "esoteric" field of study, that is looked down upon, in comparison to what students actually want, which is to learn software engineering.
But, unfortunately, modern day "computer science" is currently held up as the "prestigious" field of study, when it actually does not deserve that prestige. It deserves the ridicule, that modern day academics currently put on "software engineering" or "information systems", that are currently looked down upon as the fields of study that people go into, if they can't hack it in CS.
> we apply the concepts that we learn from CS in our jobs.
> that data might be useless by the time you graduate.
I am not sure where this myth comes from, that software engineering is just about some specific language, or tool.
Learning about the "concepts" of source control, or documentation, or working with a team, or writing readable code, or designing good APIs, are things that have little to do with CS, but goes beyond just "learn this specific tool".
Algorithms, and math, while can sometimes be useful, are still only one very small part of what it means to be a software engineer.