5 ms·
To be honest 95% of large corporate software development doesn't require a computer science degree. They are usually one form of another of CRUD application. Th
by cm2187 11y ago
To be honest 95% of large corporate software development doesn't require a computer science degree. They are usually one form of another of CRUD application. The novelty is only that they need to support more than one platform or be web based. It's not exactly rocket science. And even scaling problems are basically common sense, not advanced maths.
To me this lack of training is more concerning from a quality point of view, and in software who says quality says security. But I am not convinced a formal computer science education teaches coding best practices either (but not having done one myself it is hard to judge).
- ethanbond 11y agoYou're kind of off-base. A formal computer science education doesn't really teach coding at all. You'll learn how to write code (hopefully) as a corollary to learning how computation works. At least in my program, there isn't any single course that's oriented around the act of writing code.
- cm2187 11y agoYeah but someone doesn't understand a database unless they understand what a hashtable or a binary tree is. But none of that is very complex.
- ken47 11y agoBut hash tables and binary trees are CS concepts. Even though you don't have a CS degree, it sounds like you've taken the time to learn some basic CS.
- tptacek 11y agoThat may be true but it's not responsive to his real point, which is that you don't need to understand computation to build a typical line-of-business application. Companies used to build LOB apps in Microsoft Access, and nobody believed you needed a degree to use Access (plenty of business people figured it out for themselves, just like Excel). Now nobody uses Access anymore, but the web frameworks that replaced it aren't that much harder to use, and don't really involve a lot of complexity theory or parser generators.
- gaius 11y agoIn some ways understanding computation actually undermines you. Here's a true story, a few years ago I was a DBA on a large-ish Oracle database (~50T) supporting many users. One guy would run his report, and it would time out (in his client software, Business Objects I think). So he would run it again and it would time out. But on the 4th or 5th attempt, it would work! Why was this? I was curious enough to investigate and what was happening was he was gradually getting more and more of his working set into the cache, and eventually he had enough in-memory that his query could complete in time. Let me tell you for sure, that guy did not have any mental model of computation that led him to discover this. He just tried it and it worked. Would a guy with a classic CS education have done this?
- paulryanrogers 11y agoWhile his solution worked for him, it also revealed a flaw that could've been a deal breaker if sales were demoing the system. Of course what constitutes a significant problem is often up to a nontechnical department.
- toomuchtodo 11y agoIf sales was demoing it, they would've pre-warmed the cache by running the report until it no longer fails before the demo. Not that I've seen sales people do such activities before...
- hibikir 11y agoIt really depends. Mine had a whole lot of classes that focused more on the theoretical CS, but I had two different assembly language classes, for very different processor architectures, and I had a class on OO that, fr all intents and purposes, was about teaching practical programming. Different schools do different things. One thing seems pretty clear to me though: If you let people that can't write code graduate, you are doing them, and your program, a disservice. The most theory driven industry jobs I have ever seen, and I have seen many, require coding competence.
- Retric 11y agoIMO, the rate of failure for software projects suggests it's harder than you might think. A degree is not a requirement, but required and useful are two seperate things. Even "Best Practices" are very fluid. it's easy to add a lot of overhead that's unnessisary or to shrink past the point where current overhead is a good idea.
- mjevans 11y agoMy belief is that the failure rate shows an immaturity of the field in general. For example, history is littered with many attempts at flight that today we find foolish and laughable, but back in that time they were probably genuine attempts. Much error eventually lead to sound principles that are applied today with great precision. However I think that software probably falls in to two general categories: * Stuff so generic that everyone needs one even if it isn't an exact fit. (Think houses, and standard things in houses <> Operating systems, basic information processing software of various types.) * Stuff that is custom made or otherwise fabricated to an exact need out of an otherwise generic template. (Artisan works, and knowledge of customizing things that are more difficult to do correctly without basic concepts.) Open source software as a public service (and a thing that academic institutions should be contributing with completely open patent free work) really fills the first of those categories. Security audits and security code should also be a government service (with multiple governments as well as public entities working in the open with audit-able logic for every security decision as a web of interlocking watchers).
- ken47 11y agoThat depends on your criteria. If one of them is to minimize the running cost of a program in production, then knowledge of CS will definitely help you achieve your goal. If you don't care about the running cost, then sure, lots of bozos can throw together a program that happens to achieve the business objective. Also, let's separate the notion of the CS degree from the notion of CS knowledge. They are not one and the same. Many good software developers do not have a CS degree, but have taken the time to accumulate CS knowledge.
- wtbob 11y ago> To be honest 95% of large corporate software development doesn't require a computer science degree. They are usually one form of another of CRUD application. And that's exactly the sort of work which will eventually be easily automated away. The only real reason that it still uses people even now is that someone needs to select the refactoring menu items in a Java IDE. A smart company will use a better language, and have six developers delivering the impact of hundreds of IDE monkeys.