'But then I read Bock’s rationale, and that’s when I nearly lose a mouthful of Cheerios: Unlike English—and presumably other non-STEM fields—computer science “signals a rigor in your thinking,” an ability “to think in a formal and logical and structured way.” He said what?'
from this the author decided to read that ONLY CS majors can learn logical thinking, but Bock's statement was really that CS inherently signals this because CS is entirely predicated on this type of thinking no matter where you learn it.
I'm getting sick of these whiny stupid articles popping up on the front page, like there is a decline of logic in the site votership itself. The amazon tantrum yesterday and now this eesh
I assume it's all the English majors.
If you've got your two students, and they're both applying for a software development position, wouldn't you rather have the person who's taken formal CS courses? Even if the English major has worked on some software projects on the side, the CS major probably has some experience with data structures and algorithms, and being able to think about those.
I'm not saying an English major can't do the same things, or that because someone studied CS they're better than anyone else. What I'm trying to get at is that your average B student who studied CS is probably a better candidate for a technical position than your average A student who studied English.
I see this mode of thinking very often in people that I call "mud-minds" (shortly, people incapable of clear, cold, abstract and detached thinking, or at least incapable of performing thinking in a way that exhibits all these 4 attributes simultaneously, without loosing their intuition while they do this), even the well educated ones with probably high IQs: they totally fail to understand the real meaning of a message, and attack strawman ideas or follow dead-end reasoning paths, even if they do this with great skill and intelligence and the arguments they use may actually be very logical.
The sad thing is that seeing someone with a CS and math background think this way destroys my hope that exposing children early on to technical, abstract and logical thinking can prevent them from becoming "mud-minds". This even makes me pessimistic about humanity's future :(
All of which I never see used in a professional capacity for the vast majority of software developers.
What I do see used quite often is the ability to communicate to customers or other engineers in a clear, succinct and enjoyable manner using the English language.
Not just underestimate, even outright condemn. Like the people who defend Linus's form of "communication" on the kernel mailing list as "to the point" or "efficient". Anyone who thinks that's an acceptable style of communication from/to any human being is wrong and a perfect example of why the tech companies in general should probably make their engineers attend a speech and/or social relationships class. Somewhere along the line, "engineering culture" decided any communication protocols outside of TCP, UDP and syscalls are a waste of time.
He's an asshole on occasion, but that's not the same as communicating poorly.
"Ends don't justify the means" kinda thing... but I know I'm not going to convince you in this thread; and you're definitely not going to convince me otherwise. There are too many rude people in tech that don't know how to communicate properly with people. Rudeness has somehow become acceptable in the tech-industry so they can't see the problem they have.... and it _is_ a problem.
Conversely to Linus, someone can be perfectly polite and pleasant but fail to communicate effectively because they don't convey any meaningful information. Such a person would have poor communication skills, but not be an asshole. Linus has good communication skills, but is an asshole.
Anecdotal irony: not 24 hours ago a colleague and I had to reverse engineer a hairy mess of deeply nested if/then/else clauses that should not exist that turned out to be composed mostly of tautologies. I definitely wish to throw books at some people, preferably of the steel-bound, razor sharp edged kind.
Conclusion: you're not drawing Karnaugh tables daily in front of you, but having manipulated the fundamental rules of logic has trained your neural net and makes you much more effective at solving logic problems in a wink and not write crap code, and also simply able to debug stuff efficiently, if at all. I am regularly aghast at people drawing completely invalid conclusions from broken "common sense" logic propositions (A=>B therefore B=>A, or various other syllogisms).
If you're a consultancy that writes CRUD apps I can see emphasizing communication skills over technical skills but you're not Google.
Is it? I've met quite a lot of coders who think they're good communicators but really, really aren't.
Karnaugh Maps: While I love vocab as much as any other kid out there. We're not calling them " colored-truth-tables " which is what the fuck it is. You're advocating that one is more rigorous than the other. However the only thing which is actually being conveyed is usage OF A TRUTH TABLE!
Academics gleefully accept this more specific vocabulary as a proxy for context knowledge.
Its a (fucking) shit workaround.
CS is rooted entirely in the qualities he is looking for. English isn't.
It may be technically true, but the dismissive "english/humanities is easy" narrative that is (or, in my day, was--it seems it still is) extremely popular in the STEM undergraduate community carries a kind of implicit claim of exactly that sort. Stating that something is easy necessarily implies the person making the statement thinks he could, with some relatively lesser effort than he applies to his current focus, achieve comparable results to those who focus on that something.
There's a trend towards convergence, however, and formal logic has had a profound effect on the English curriculum in the last several decades. Hofstadter, Tarski, Quine, Levi-Strauss, et al., are becoming required reading in forward-thinking English curricula. Your typical English course isn't going to touch the type of logic discussed in your typical CS course. But advanced linguistics is, more or less, formal systemics. Unfortunately, you can encounter a fair amount of fluff on the way there.
English education is in need of an overhaul, and it's starting to get one. But there should be no battle between the humanities and the sciences. Instead, we should do a better job bringing the average in the humanities up to par and rigor.
We should also do a better job coaching students on career paths before we ask them to choose majors. If you're studying English because you like reading books, and you have no clue what you want to do when you graduate, you're in for a tough road ahead. If you're studying English because you want to get into Yale Law School, or write for the New York Times, or become the next Michael Lewis, that's great. (But in that case, you'd better be good.)
Ultimately, what matters isn't the content of the two paths, but the application of them. CS is a directly practical degree. You can put to work what you learn almost immediately and unambiguously. You can trace a more or less direct path between the input (education) and the output (skill). English is more indirect. You can learn extremely valuable skills in an English program, but those skills aren't immediately applicable to any particular job. That's because English is a really old curriculum, which predates the modern job market. If you want to make something of an English degree, you'll need to develop skills above and beyond what you learn in the classroom. Generally speaking, schools don't do a great job teaching those ancillary skills. And so the English degree is not, in itself, sufficient for positions to which it's very well suited.
I didn't perceive a slight at all, it seemed like a very fair analogy to me. "Writing a novel" would be the same.
The nice thing about compilers is they tell you when your code has a problem. There's no equivalent barrier to posting awful poetry-drivel on Facebook ;-)
Just wait until you see the headline: "Join our startup to disrupt the poetry industry!"
The companies end up having hiring techniques and processes (and subconscious biases for hiring as result of these) which might work well before but they might do not work for today. This is very hard thing to solve and problems becomes obvious to outside world when companies try to get into new field / area.
Some companies have head of recruiting reporting directly to CEO to fix these kind of problems. Some companies will do acquisitions.
As a third-year undergrad I took a 400-level course on logic from the humanities department. I remember being blown away by how inept the average students there seemed at first. They were simply unprepared for the torrent of proofs, deductions, tautologies, De Morgan's laws, etc. The way of thinking required to get through that class easily was one which most second-year CS students had, but not the student body at large. I came to realize I had been groomed for this class for years already.
In a 200-level CS course we learned to use Karnaugh Maps. This was not optional. There is a difference between analyzing digital logic and writing papers outside CS. Not that one is better than the other, but you don't hear CS folks claiming they're well suited for writing poetry.