Computer Science vs. Business Analytics

I’ve been asked enough times by current or prospective students about how the Business Analytics concentration in the business school compares with Computer Science (C.S.) that I thought it was time to post about it to make the answer easily accessible. I will first give (very terse) definitions of C.S. and Business Analytics, and then compare them.

C.S. is the science and art of writing high-quality code, usually to solve problems or build applications at a “production quality” level, i.e. good enough to be deployed for many people to use in many ways. (I’m no defining “good”, “quality”, “many”, etc., since that would require a book, not a post; I’m also ignoring the hardware side of C.S.)

Business Analytics (as the very name implies) is designed to give people headed into a business career the tools to consume data and make better business decisions. These skills are critical in any data-driven industry, e.g. finance, marketing, retail, logistics, sports, etc. (I personally think it would be foolish for anyone to pursue a career on the business side of any of these industries without acquiring the skills that the Business Analytics concentration provides. As one director in a top financial firm put it to me, “Python is the new Excel.”)

In terms of how they compare to one another, consider the following analogy: a writer of fiction and a scientist writing a research paper both use the same exact tool, i.e. the written word. However, it is not meaningful to ask which written work – a given novel or a given paper – is “better”, since they are fundamentally different in nature. Similarly, a computer scientist and one who studies business analytics may both write code, but the nature and use of their code are as far away from one another as the scientist’s paper and the writer's prose are. (This analogy does break down when one considers if one person could or could not do the other’s job if necessary, since the analyst’s coding skills are a tiny subset of those of the software engineer, but for purposes of a post the analogy is “good enough”.)

One who studies business analytics is acquiring a critical business skill, i.e. the ability to make well-informed data-driven decisions, and is not different in kind from someone who mastered Excel 20 years ago. (And, as an aside, the strengths and dangers of user developed applications have not significantly changed since Excel spreadsheets began to be shared around businesses so many years ago.)

One who studies computer science, on the other hand, is learning how to create high-quality software of all types and in all contexts, from end user applications (e.g. Photoshop) to internet-scale web sites like google.com to high frequency trading systems to cyber warfare tools to self-driving cars, etc.

The bottom line is that business analytics and computer science are both great things, but have very little to do with each other in terms of career paths. If one wants a career as a business person in any data-driven industry, it would be foolish not to study business analytics. If one wants to be a software engineer of any type, one must study Computer Science.

Popular posts from this blog

Confessions of an Imperfect Student and a Demanding Professor

by, Judah Diament We have seen time and again that public figures, no matter how hard they try, can’t hide past mistakes. When you take on a public role, eventually the truth will come out. As the chair of the Department of Computer Science, I am no longer a private citizen, so it is safe to assume that my skeletons will eventually be made public. As such, I thought it wise to preemptively release the information and get ahead of the news cycle. So, here is my first confession: when I was an undergraduate student at YU, I received a C in Medieval Jewish History, a C+ in Intermediate Hebrew II, and a C- in Calculus 1. It was not the professors’ fault in any one of those cases; I had wonderful professors (Rabbi Dr. Bernard Rosensweig, Dr. Richard Steiner, and Dr. Norman Rosenfeld a”h , respectively.) I simply failed to perform at an adequate level. I know it is hard to imagine that someone who claims to be competent in any field could have possibly received multiple grades lower
Read more

The Exceptional Moral Character of YU Students

by,  Judah Diament Rav Yisroel Meir Kagan is known popularly as “The Chofetz Chaim ”, after his famous work by the same name. In klal 10:1-2 of Sefer Chofetz Chaim , he codifies the rules regarding when one is allowed to share negative or damaging facts about another Jew in order to achieve a positive goal, such as correcting an improper behavior. The first rule of the seven is that one must have witnessed the incident or behavior in question firsthand, and must not have only heard about if from someone else. The fourth rule is that one may not exaggerate the facts, even though his intention in doing so is to achieve something good. Since arriving in Yeshiva College as a professor of Computer Science in 2016, on multiple occasions I have heard or read claims that cheating is “widespread” in YU. Like any other decent person, I was and am deeply disturbed by the idea that YU students would cheat. Equally disturbing, however, is the complete lack of rigor and care with which I hav
Read more

You Will Have Meetings. Lots of Them.

by,  Judah Diament Periodically someone asks me if Software Engineers (SE) spend their days sitting in front of their computers, or if they interact with other people. There are two assumptions, both wrong, that go into the question, and it's important to address both assumptions so that students in all majors/fields have a more accurate understanding of what the working world is like. This will be a brief post because it's a really simple point, albeit a fundamental one. It is often assumed that an SE sits in front of his computer all day writing code. It is equally assumed that people on other career paths (law, accounting, finance, human resources, marketing, etc.) do not spend hours a day sitting in front of their computers. Both of these assumptions are wrong. Collaborating with others: If you work in a large company, no matter what your career/role/field is, you will collaborate with many people, sit in many meetings, and make many presentations. The more junior yo
Read more