|
I feel the title of Software Engineering is misleading because it doesn't quite relate to other fields of engineering. The way Software Engineering is used is more like Software Construction, where the concern is more about programming using building blocks and tools of the trade, along with construction methods: like code organization, deployment, source control, etc. Computer science might best be aimed at: Big Data Analysis, Compiler Writing like HipHop (Php compiler), or Distributed/Parallel Programming, Large Scale Deployment, etc. I agree that writing an LALR recursive descent parser might not make someone an architect, but neither will a 300 hour/8 week course, mainly because I feel experience is the deciding factor. Employers often want to create a repeatable scaleable process -- so yes this would be attractive to an employer. Who says a CS degree is required for admission into development? I've worked at companies where many of the developers didn't have CS degrees, but there is a noticeable difference between those with a degree and those without. Those that don't have a CS degree, but somehow still make it, are often those that could have made it through a 4 year course. Sadly, there are also those with a CS degree, or even a graduate degree, that can't hack it either. So in the end hiring is difficult, and there doesn't seem to be many indicators that some one will be a good developer and eventually an architect. But, when hiring I personally would give preference to a someone who holds a CS AND has the right attitude. Also it's a matter of goals. If your goal is to stand up something cookie-cutter-ish, and then just duplicate that process with varying degrees of style, then sure anyone can probably learn to do that. But, if you need to integrate systems, write parsers to put data into a high-performance data warehouse, organize structures for a custom CMS, etc, would you really go to someone fresh out of a 300hr/8week course, or someone fresh from a CS program, if those were your only 2 choices? |