3 ms·
The field is very young. If you want to build bridges, you major in Civil Engineering. You have to learn a lot of physics along the way, but make no mistake: th
by scott_s 18y ago
The field is very young. If you want to build bridges, you major in Civil Engineering. You have to learn a lot of physics along the way, but make no mistake: the point of your education is to prepare you to build things.
Computer Science is a mish-mash of many things, and only part of that is how to build software. Sure, just about anything outside of pure CS theory requires programming, but producing the working program is not the end in itself. A big problem is that we really don't know how to build good software. This does not mean good software does not exist. It means that we don't have reliable methodology to produce good software. In contrast, we have reliable methodologies to build good bridges.
The ACM studied this with the IEEE in 2000, and came to this conclusion (http://www.cs.wm.edu/~coppit/csci690-spring2004/papers/selep_main.pdf http://www.cs.wm.edu/~coppit/csci690-spring2004/papers/selep...): "Following a study by a blue ribbon panel of prominent software engineers,
the ACM Council decided in May 1999 that it could not support licensing of software engineers. ACM's position is that our state of knowledge and practice in software engineering is too immature to warrant licensing."
I think it's important to differentiate between Computer Science and Software Engineering. That is, the difference between someone whose goal is contributing to the base of knowledge in their field, and someone whose goal is a stable, working system. There is, of course, overlap, but I think the distinction is still there.
I think that in the future, there will be separate CS and SE degrees. Much of what they learn will be the same, but the focus will be different. A CS education will prepare you to be a researcher; a SE education will prepare you to build software. (I know SE degrees exist, but most schools only have a CS program.) I don't think this split will happen until SE is mature enough to be licensed.
What does this have to do with your question?
We don't have reliable methodologies to build good software, and the only formal education people receive that involves building software isn't necessarily focused on actually building software. This is a nice way of saying "we don't know what we're doing." If even the best people in the field don't know what we're doing, then you can learn that on your own.
Personally, I still think a CS degree is the best preparation right now to be a professional SE. You will probably be exposed to more things than you would find on your own. But I also recognize that there are probably many professional developers without degrees who are better at what they do than people with degrees.
Also note that if you actually want to do research, then you need to get a degree.
- tjpick 18y agoYou are right about distinguishing between CS & SE. At least here in New Zealand there is a distinction between the two. I have a BE (software eng), which is internationally accredited, rather than a BSc (CS). The SE degree involves general engineering courses, and has a reasonable focus on reliabiliy, quality, safety etc. A degree like this makes you eligible for the professional engineering body IPENZ. There is a mismatch between the education and what employers seem to look for. You see jobs titled "software engineer" that really only want an html/js coder or someone to set up a wiki, requesting CS degrees or equivalent experience. Jobs that really do demand rigourous software practices will hire anything they can get, but again mainly looking for CS degrees. > Personally, I still think a CS degree is the best preparation right now to be a professional SE. I have to disagree. The best prep for a professional SE career is a professional SE degree, and then joining a professional body. Sure you can get a CS degree and become a programmer, that's fine. But you aren't really a professional engineer are you? I'd say that there are reliable methodologies to build software but a lot of times these are not executed in any meaningful fashion. For the price people are willing to pay, and the time they will wait, quality software is not what they want. They may say they want quality, but they don't really. They really want something delivered yesterday, for free or cheap, that works most of the time and does most of the things they want. And this is what cowboys (uh... I mean "software engineers") deliver. I don't really like the bridges analogy. The complexity and environment are too different for it to be meaningful when compared to software. Thing is, bridges have a well defined function, the banks don't move, the load is generally known (vehicles, people, etc) and so a stable structure can be delivered. And besides, plenty of bridges collapse. If there is an earthquake, or they are overloaded, or they get old, they topple.
- scott_s 18y agoMy comment about a CS degree being the best preparation for a SE career was assuming a SE degree is not an option. At most colleges and universities in the US - as far as I know - it's not.