<p>I don't know if this will help you, but I often find myself in the position of explaining the difference between CS and IT to students / prospective students / parents, and I use the experience of being a one-time emergency medical technician to help.</p>

<p>I compare the difference between CS and IT to the difference between medical doctors and EMTs.  As an EMT, I was required by law to follow the protocols established by physicians, who get to do the experimenting and the researching and the paper-writing.  As an IT worker, you will be handed a set of tools (databases, operating systems, programming languages) and have to work with what the researchers (the Computer Scientists) come up with.  The world needs IT workers as much as they need EMTs, so it isn't less, just different.</p>

<p>It's not perfect, but I teach at a two-year school, so it's enough to get students thinking about which major to choose.</p>

CC BY-SA 3.0
2017-06-30T04:04:53.263Z
It's like you were listening to the original conversation I had at the party! I was an EMT too, and made the exact same analogy! Well, maybe not _exact_ same, but incredibly similar. EMTs follow a pre-written set of protocols, almost "cookbook"-style, whereas doctors are expected to do more thinking. Analysis, synthesis, and creation. In summary, it's the clinician/technician difference. Your answer makes me really happy. I don't know if the _average_ person knows enough about medical infrastructure to really get it though. What responses have you gotten when you've used it?
Piyush Parikh
CC BY-SA 3.0
2017-06-30T12:47:38.127Z
Well, I am still a volunteer firefighter; I just let my cert lapse when I had a kid and didn't have time to refresh.  I'm in an engine company, so it has never been a big deal.  Also, I teach at a community college, where we probably have a higher concentration of FFs and EMTs than at other schools, and the firefighters always seem to find me, so I probably tend to have this conversation with people who understand EMS at a higher rate than others would.
Chris M.
CC BY-SA 3.0
2017-06-30T00:14:36.000Z
2017-06-30T00:14:36.000Z
Chris M.
<p>I regularly have to explain what <em>computer science</em> is to parents, and I have lately settled into this explanation:</p>

<p>Technology keeps changing all the time. You get used to the menus in Microsoft Word, and then they change it to the Ribbon. You learn to program buttons in Java using Applets, and then Applets get removed from every major browser as a security risk.</p>

<p>But there are some things that <em>never</em> change, because they're in the realms of mathematics, or they are fundamental organizing principles.  For instance, computer right now work in binary, 1s and 0s.  The properties of binary numbers themselves aren't going to change no matter what new technology comes around tomorrow.  We might create a computer that's not based on binary, but the properties of binary itself are fixed.  This is the realm of computer science.  Computer science is the foundational stuff that doesn't change.</p>

<p>It's highly mathematical, highly theoretical, and there are a lot of proofs involved, but when you study computer science, you are studying the deeper question in the nature of computation itself, and that's stuff that never gets dated.</p>

CC BY-SA 3.0
2017-06-22T09:45:47.713Z
Rather than 'never gets dated', a lot of it becomes more widely relevant as hardware improvements reduce the compute cost (so it's not all abstract).
Sean Houlihane
CC BY-SA 3.0
2017-06-22T10:38:22.287Z
One thing I emphasize with my students, once they're up to algorithms, is that faster hardware and bigger hard drives make a lot of things *worse* instead of better. An $n^2$ algorithm on a faster computer is not really faster if the availability of more data tempts you into a larger $n$.
Ben I.
CC BY-SA 3.0
2017-06-21T19:26:49.723Z
2017-06-21T19:26:49.723Z
Ben I.
<p>I'll attempt a self-answer here, based on hindsight and a few previous experiences where I went in knowing I wanted to do this.</p>
<p>I've found that starting off with an analogy helps a lot of the time. Friends and co-workers have reported similar results in my super unscientific poll. The one we use is along the lines of</p>
<blockquote>
<p>Computer science has as much to do with programming as architecture has to do with bricklaying</p>
</blockquote>
<p>or</p>
<blockquote>
<p>CS is to coding as astronomy is to telescopes</p>
</blockquote>
<p>It can be helpful to try to make the analogy with the listener's own profession, as long as it doesn't backfire by derailing the conversation.</p>
<p>This then leads into</p>
<blockquote>
<p>Computer science is an academic field. It's theoretical. Programming is more practical; it's a tool.</p>
</blockquote>
<p>In my story above, I segued from this into the Halting Problem and efficiency. Looking back, I think that was too big of a jump, at least when presented as abstract concepts. I like the phone book example mentioned in <a href="https://cseducators.stackexchange.com/a/932/1166">Peter's answer</a>. I think I'd modify it this way:</p>
<blockquote>
<p>One big part of computer science is &quot;algorithms,&quot; which is a fancy word for &quot;figuring out a good way to do things.&quot; A good example of this is finding someone's number in the phone book. You could just open the book to random places and hope you get lucky. You could start on page one and start reading straight through until you find the person you want. You could take advantage of the alphabetical sorting and index to see what page the people with similar names start on.</p>
<p>Using the index is clearly smarter than repeatedly picking random pages. Coming up with these better ways to do things; that's computer science. The details get really complicated (and are a big part of the field) but it turns out that what seem like small differences in efficiency, or memory usage, or other factors like that, can make a <strong>huge</strong> difference how good an algorithm is in the real world.</p>
<p>Now, once you have the plan, you might want to tell someone else how to do it. I could tell someone the exact same phone book search plan in English, or Spanish, or Hindi. I could tell a computer how to do it in C++, or Java, or Ruby. Programming is just a way of communicating instructions to a computer, the same way human languages are a way of communicating information to other people.</p>
</blockquote>
<p>The downside of this answer is that it doesn't get into the mathematical foundation of CS, or how CS is about unchanging fundamental concepts. But I'm beginning to think that's not a big problem... such topics might be beyond the scope of a five-minute intro for a complete layperson.</p>

CC BY-SA 3.0
2017-06-22T18:45:59.140Z
"Computer science is an academic field. It's theoretical. Programming is more practical; it's a tool." Beautiful and succinct.
Ben I.
CC BY-SA 3.0
2017-06-22T18:04:46.537Z
2017-06-22T18:04:46.537Z
2020-06-18T08:36:57.023Z
Piyush Parikh
<p>I would explain it like this:</p>

<p>In reality, you have to solve problems on your daily basis. It may be a time problem, like "how do I get these five tasks done it just 1 hour?" or "how can I stack these boxes so that they all fit into the cupboard?".</p>

<p>Computer science is in many ways equal to solving these problems, only that the problems are of a little more mathematical and logical manner.</p>

<p>One rather common problem of computer science is "how do I sort a list of numbers?". When a person is given this task, he or she will most likely pick out the lowest or highest number first, put it onto the sorted list and continue from the start until no numbers remain in the unsorted list. This is one solution for the sorting problem, and computer scientists often have to solve this task too. As you can imagine, like described above, it will take a relatively long time to sort all the numbers, as you will repeatedly look at all numbers to sort out the lowest / highest one. So one person once thought "how could I solve this problem faster?" and maybe created an algorithm to solve the task for example twice as fast as the original approach.</p>

<p>Solving problems, not only using the most intuitive way which often tends to be very slow, but thinking about a more complex and strategical approach, to get a given task done as fast as possible, this is a major part of computer science.</p>

CC BY-SA 3.0
2017-06-22T15:24:42.830Z
Hi Tom! Welcome to CS Educators! This is a really great first answer, thanks for writing it up!
thesecretmaster
CC BY-SA 3.0
2017-06-22T15:10:39.537Z
2017-06-22T15:10:39.537Z
Tom Doodler
<p>Dealing with (my) parents who are not particularly aware of computers or the difference between a server and a database, I believe I have a fairly simple answer for this question.</p>

<p><em>Computer science</em> is the theory and study of how computers work, algorithms (in layman's terms, a process to solve a problem), and how to think like a computer in order to manipulate it to do what you/the client/whoever want.</p>

<p><em>Programming</em> is the actual act of applying the theory and manipulation of the machine. They often get mixed up because programming is such an integral part of CS but is, in fact, only a part of it.</p>

<p>This explanation in some form has had a fairly positive response to me. Or, if you're particularly pressed for time: "Programming is part of computer science, but CS is a lot more focused on the understanding of how the computer works."</p>

CC BY-SA 3.0
2017-06-29T02:16:52.943Z
2017-06-29T02:16:52.943Z
cMcNerlin
<p>Computer science is a discipline of problem solving. I use this phrase from CS50 often (mainly because I teach an adaption of it): </p>

<p><code>inputs -&gt; algorithms -&gt; outputs</code></p>

<p>From <a href="http://docs.cs50.net/2016/fall/notes/0/week0.html" rel="nofollow noreferrer">the official CS50 notes from last year's Week 0 lecture</a>, the following three bullets explain what this phrase means:</p>

<blockquote>
  <ul>
  <li><p>At the end of the day, computer science is about problem solving:
  taking some inputs (the problem we might be trying to solve) and
  creating some outputs (perhaps a solution to the problem).</p></li>
  <li><p>Between those inputs and outputs is what we might call a "black box,"
  something that solves the problem for us even if we might not know or
  care <em>how</em> it solves them.</p></li>
  <li><p><strong>Algorithms</strong> are sets of instructions to solve particular problems.</p></li>
  </ul>
</blockquote>

<p>This is what I use on Day 0 when I welcome students to my class and at Back-to-School Night presentations to parents.</p>

<p>If your "pitch" has enough time for an example, the canonical CS50 example -- one which my students remember vividly from Day 0 since it involves ripping up a phone book -- is to pose the question asking how to find a name in a phone book. You could approach the problem linearly and go page by page (correct but slow). You could look at two pages at a time to double the efficiency (incorrect without checking a potentially skipped-over page). You could divide and conquer by examining the middle page and throwing away the half you no longer need (logarithmic efficiency). Even something as simple as looking up a name in a phone book allows for discussing linear v. binary search, computational complexity, debugging, sorting (since the book comes pre-sorted). </p>

<p>As an alternative to the phone book example (since it's more effective with an actual phone book and not in the abstract), say this: "Think of a number between 1 and 1024. I guarantee I will get it in 10 guesses or fewer." A computer scientist will conquer that challenge every time.</p>

CC BY-SA 3.0
2017-06-21T23:46:52.050Z
2017-06-21T23:46:52.050Z
Peter
<p>I was at a party a few days ago with a doctor (the medical kind, not the research kind) who was thinking about writing a computer program to solve a scheduling problem at work. Someone introduced him to me because I have a CS degree and worked as a software engineer for a few years.</p>

<p>It wasn't long before we moved on from the specific problem he had (for which the answer was "hire a freelancer" or at least "I can't solve this for you just standing here with a beer and without a computer") to talking about computer science in general. To his credit, he asked good questions, picked up on the answers immediately, and asked smart follow-ups. But a lot of stuff that's second nature to us CS people was totally new and surprising to him.</p>

<p>The big one, which isn't surprising in hindsight but which we didn't get to until late in the conversation, was that computer science isn't the same as programming. There was also the fact that complexity/Big-O makes a real difference, and that the Halting Problem/unsolvability exists. It kinda made me feel like I wasn't a great ambassador for CS.</p>

<p>My actual question here is: how do you explain computer science to people when you have not a year or a semester, but just an hour, or even only five minutes?</p>

<p><em>(This question might be a little outside the typical scope for this site, but it's still relatively early in the beta, so I figured let's give it a shot.)</em></p>

CC BY-SA 3.0
2017-06-21T19:00:11.147Z
It's similar in spirit (but different enough to be a different question IMHO) to this question: https://cseducators.stackexchange.com/questions/868/how-to-explain-what-code-is-to-my-parents We used [tag:layperson] there, which would fit here as well. I will add it.
Peter
CC BY-SA 3.0
2017-06-22T01:55:09.517Z
@PiyushParikh Feel free to roll back the title - I'm just trying to massage the question to be more on-topic, but you don't have to accept any changes you disagree with. (To roll back, just click where it says I edited the question, and you will see the edit and have the ability to roll back if you choose)
Ben I.
CC BY-SA 3.0
2017-06-22T09:39:39.643Z
Title might be better comparing CS to coding. Maybe 'the science part of CS'.
Sean Houlihane
CC BY-SA 3.0
2017-06-30T04:15:06.903Z
You're giving me a lot of credit when you should be giving it to my "audience." He was really sharp, and interested. Guess you'd expect that from a doctor.
Piyush Parikh
<cs-theory><layperson>
How can I explain the difference between CS and coding to a layperson?
# How can I explain the difference between CS and coding to a layperson?

(Asked by: username_0 on 2017-06-21)

I was at a party a few days ago with a doctor (the medical kind, not the research kind) who was thinking about writing a computer program to solve a scheduling problem at work. Someone introduced him to me because I have a CS degree and worked as a software engineer for a few years.

It wasn't long before we moved on from the specific problem he had (for which the answer was "hire a freelancer" or at least "I can't solve this for you just standing here with a beer and without a computer") to talking about computer science in general. To his credit, he asked good questions, picked up on the answers immediately, and asked smart follow-ups. But a lot of stuff that's second nature to us CS people was totally new and surprising to him.

The big one, which isn't surprising in hindsight but which we didn't get to until late in the conversation, was that computer science isn't the same as programming. There was also the fact that complexity/Big-O makes a real difference, and that the Halting Problem/unsolvability exists. It kinda made me feel like I wasn't a great ambassador for CS.

My actual question here is: how do you explain computer science to people when you have not a year or a semester, but just an hour, or even only five minutes?

*(This question might be a little outside the typical scope for this site, but it's still relatively early in the beta, so I figured let's give it a shot.)*

**Tags:** cs-theory, layperson

> **Comments:**
> **username_1**: It's similar in spirit (but different enough to be a different question IMHO) to this question: https://cseducators.stackexchange.com/questions/868/how-to-explain-what-code-is-to-my-parents We used [tag:layperson] there, which would fit here as well. I will add it.  
> **username_2**: @PiyushParikh Feel free to roll back the title - I'm just trying to massage the question to be more on-topic, but you don't have to accept any changes you disagree with. (To roll back, just click where it says I edited the question, and you will see the edit and have the ability to roll back if you choose)  
> **username_3**: Title might be better comparing CS to coding. Maybe 'the science part of CS'.  
> **username_0**: You're giving me a lot of credit when you should be giving it to my "audience." He was really sharp, and interested. Guess you'd expect that from a doctor.  

---

## 6 answers

### Answer by username_2 on 2017-06-21. Score: 11

I regularly have to explain what *computer science* is to parents, and I have lately settled into this explanation:

Technology keeps changing all the time. You get used to the menus in Microsoft Word, and then they change it to the Ribbon. You learn to program buttons in Java using Applets, and then Applets get removed from every major browser as a security risk.

But there are some things that *never* change, because they're in the realms of mathematics, or they are fundamental organizing principles. For instance, computer right now work in binary, 1s and 0s. The properties of binary numbers themselves aren't going to change no matter what new technology comes around tomorrow. We might create a computer that's not based on binary, but the properties of binary itself are fixed. This is the realm of computer science. Computer science is the foundational stuff that doesn't change.

It's highly mathematical, highly theoretical, and there are a lot of proofs involved, but when you study computer science, you are studying the deeper question in the nature of computation itself, and that's stuff that never gets dated.

> **Comments:**
> **username_3**: Rather than 'never gets dated', a lot of it becomes more widely relevant as hardware improvements reduce the compute cost (so it's not all abstract).  
> **username_2**: One thing I emphasize with my students, once they're up to algorithms, is that faster hardware and bigger hard drives make a lot of things *worse* instead of better. An $n^2$ algorithm on a faster computer is not really faster if the availability of more data tempts you into a larger $n$.  

---

### Answer by username_0 on 2017-06-22. Score: 6

I'll attempt a self-answer here, based on hindsight and a few previous experiences where I went in knowing I wanted to do this.

I've found that starting off with an analogy helps a lot of the time. Friends and co-workers have reported similar results in my super unscientific poll. The one we use is along the lines of

> Computer science has as much to do with programming as architecture has to do with bricklaying

or

> CS is to coding as astronomy is to telescopes

It can be helpful to try to make the analogy with the listener's own profession, as long as it doesn't backfire by derailing the conversation.

This then leads into

> Computer science is an academic field. It's theoretical. Programming is more practical; it's a tool.

In my story above, I segued from this into the Halting Problem and efficiency. Looking back, I think that was too big of a jump, at least when presented as abstract concepts. I like the phone book example mentioned in [username_1's answer](https://cseducators.stackexchange.com/a/932/1166). I think I'd modify it this way:

> One big part of computer science is "algorithms," which is a fancy word for "figuring out a good way to do things." A good example of this is finding someone's number in the phone book. You could just open the book to random places and hope you get lucky. You could start on page one and start reading straight through until you find the person you want. You could take advantage of the alphabetical sorting and index to see what page the people with similar names start on.
>
> Using the index is clearly smarter than repeatedly picking random pages. Coming up with these better ways to do things; that's computer science. The details get really complicated (and are a big part of the field) but it turns out that what seem like small differences in efficiency, or memory usage, or other factors like that, can make a **huge** difference how good an algorithm is in the real world.
>
> Now, once you have the plan, you might want to tell someone else how to do it. I could tell someone the exact same phone book search plan in English, or Spanish, or Hindi. I could tell a computer how to do it in C++, or Java, or Ruby. Programming is just a way of communicating instructions to a computer, the same way human languages are a way of communicating information to other people.

The downside of this answer is that it doesn't get into the mathematical foundation of CS, or how CS is about unchanging fundamental concepts. But I'm beginning to think that's not a big problem... such topics might be beyond the scope of a five-minute intro for a complete layperson.

> **Comments:**
> **username_2**: "Computer science is an academic field. It's theoretical. Programming is more practical; it's a tool." Beautiful and succinct.  

---

### Answer by username_5 on 2017-06-22. Score: 5

I would explain it like this:

In reality, you have to solve problems on your daily basis. It may be a time problem, like "how do I get these five tasks done it just 1 hour?" or "how can I stack these boxes so that they all fit into the cupboard?".

Computer science is in many ways equal to solving these problems, only that the problems are of a little more mathematical and logical manner.

One rather common problem of computer science is "how do I sort a list of numbers?". When a person is given this task, he or she will most likely pick out the lowest or highest number first, put it onto the sorted list and continue from the start until no numbers remain in the unsorted list. This is one solution for the sorting problem, and computer scientists often have to solve this task too. As you can imagine, like described above, it will take a relatively long time to sort all the numbers, as you will repeatedly look at all numbers to sort out the lowest / highest one. So one person once thought "how could I solve this problem faster?" and maybe created an algorithm to solve the task for example twice as fast as the original approach.

Solving problems, not only using the most intuitive way which often tends to be very slow, but thinking about a more complex and strategical approach, to get a given task done as fast as possible, this is a major part of computer science.

> **Comments:**
> **username_6**: Hi Tom! Welcome to CS Educators! This is a really great first answer, thanks for writing it up!  

---

### Answer by username_7 on 2017-06-29. Score: 4

Dealing with (my) parents who are not particularly aware of computers or the difference between a server and a database, I believe I have a fairly simple answer for this question.

*Computer science* is the theory and study of how computers work, algorithms (in layman's terms, a process to solve a problem), and how to think like a computer in order to manipulate it to do what you/the client/whoever want.

*Programming* is the actual act of applying the theory and manipulation of the machine. They often get mixed up because programming is such an integral part of CS but is, in fact, only a part of it.

This explanation in some form has had a fairly positive response to me. Or, if you're particularly pressed for time: "Programming is part of computer science, but CS is a lot more focused on the understanding of how the computer works."


---

### Answer by username_1 on 2017-06-21. Score: 3

Computer science is a discipline of problem solving. I use this phrase from CS50 often (mainly because I teach an adaption of it):

`inputs -> algorithms -> outputs`

From [the official CS50 notes from last year's Week 0 lecture](http://docs.cs50.net/2016/fall/notes/0/week0.html), the following three bullets explain what this phrase means:

> * At the end of the day, computer science is about problem solving:
>   taking some inputs (the problem we might be trying to solve) and
>   creating some outputs (perhaps a solution to the problem).
> * Between those inputs and outputs is what we might call a "black box,"
>   something that solves the problem for us even if we might not know or
>   care *how* it solves them.
> * **Algorithms** are sets of instructions to solve particular problems.

This is what I use on Day 0 when I welcome students to my class and at Back-to-School Night presentations to parents.

If your "pitch" has enough time for an example, the canonical CS50 example -- one which my students remember vividly from Day 0 since it involves ripping up a phone book -- is to pose the question asking how to find a name in a phone book. You could approach the problem linearly and go page by page (correct but slow). You could look at two pages at a time to double the efficiency (incorrect without checking a potentially skipped-over page). You could divide and conquer by examining the middle page and throwing away the half you no longer need (logarithmic efficiency). Even something as simple as looking up a name in a phone book allows for discussing linear v. binary search, computational complexity, debugging, sorting (since the book comes pre-sorted).

As an alternative to the phone book example (since it's more effective with an actual phone book and not in the abstract), say this: "Think of a number between 1 and 1024. I guarantee I will get it in 10 guesses or fewer." A computer scientist will conquer that challenge every time.


---

### Answer by username_4 on 2017-06-30. Score: 2

I don't know if this will help you, but I often find myself in the position of explaining the difference between CS and IT to students / prospective students / parents, and I use the experience of being a one-time emergency medical technician to help.

I compare the difference between CS and IT to the difference between medical doctors and EMTs. As an EMT, I was required by law to follow the protocols established by physicians, who get to do the experimenting and the researching and the paper-writing. As an IT worker, you will be handed a set of tools (databases, operating systems, programming languages) and have to work with what the researchers (the Computer Scientists) come up with. The world needs IT workers as much as they need EMTs, so it isn't less, just different.

It's not perfect, but I teach at a two-year school, so it's enough to get students thinking about which major to choose.

> **Comments:**
> **username_0**: It's like you were listening to the original conversation I had at the party! I was an EMT too, and made the exact same analogy! Well, maybe not _exact_ same, but incredibly similar. EMTs follow a pre-written set of protocols, almost "cookbook"-style, whereas doctors are expected to do more thinking. Analysis, synthesis, and creation. In summary, it's the clinician/technician difference. Your answer makes me really happy. I don't know if the _average_ person knows enough about medical infrastructure to really get it though. What responses have you gotten when you've used it?  
> **username_4**: Well, I am still a volunteer firefighter; I just let my cert lapse when I had a kid and didn't have time to refresh.  I'm in an engine company, so it has never been a big deal.  Also, I teach at a community college, where we probably have a higher concentration of FFs and EMTs than at other schools, and the firefighters always seem to find me, so I probably tend to have this conversation with people who understand EMS at a higher rate than others would.  

---

